I’ve spent years sitting in architecture meetings that could have been two sentences and a whiteboard. I’ve also seen teams build entire systems with no discussion at all — and then wonder why everything falls apart.

This talk is about how to strike the balance. I’ll walk through the communication patterns I use with engineering teams to make faster, clearer technical decisions without drowning in meetings. We’ll talk about how to get the right people in the room, how to ask questions that uncover hidden landmines, and how to avoid the “HIPPO problem” where the Highest-Paid Person makes all the choices.

You’ll learn how to evaluate options without analysis paralysis, when to document decisions, and how to keep moving even when you don’t have perfect information. I’ll also show you how to use PHP-specific examples — migrations, API changes, infrastructure choices — to illustrate these patterns in your own team.

Better decisions aren’t about being smarter. They’re about communicating better.