The magic in the meeting

I once had a mentor who used to say, “The magic is in the meeting.”

I was working at an advertising agency at the time, and he had been around long enough to have lived through a very different version of the industry. Maybe not exactly the golden age of advertising, but certainly an age when the creative process still had a kind of mythology around it. The creatives sat around together. They argued over ideas. They sketched campaigns. They pushed each other. They found the thing hiding underneath the obvious thing.

He was not anti-technology, he was passionate about it. He understood that digital tools were changing the work, and in many ways making the work better. But he believed very deeply that the computer was not where the idea happened.

The meeting was where the idea happened.

The computer was where you made the thing, refined the thing, distributed the thing, and measured the thing. But the strange human process of figuring out what the thing should be still happened when the right people got in a room and did that thing called brainstorming.

I have been thinking about that line a lot more in the age of AI, because I think it is more true now than it was when he first said it to me. We have more powerful execution tools than ever. We can generate copy, code, designs, workflows, research summaries, prototypes, and product ideas at a speed that would have seemed absurd even a few years ago.

But the danger of cheap execution is that it can trick us into skipping the part where we decide whether the thing is actually worth executing.

That is the trap. AI will happily help you build the wrong thing. It may even make the wrong thing look polished enough that everyone feels like progress has been made. But a well-executed bad idea is still a bad idea. In fact, it might be more dangerous now because the cost of building it has dropped so much that teams feel less pressure to stop and ask whether they are solving the right problem in the first place.

But do you know what’s worse than bad ideas. Almost good ideas. The ideas that seem good enough to ship. The ideas that are nearly there but nobody is there to say we’re close, but we’re not there yet.

This came up for me recently in a sprint planning meeting.

A client had asked us to build something. They wrote a ticket and on the surface, it was clear enough. There was a requested behavior, a proposed flow, and a desired outcome. But as I read it, something felt off. It was not that the request was impossible. It was not even technically difficult. With today’s tools, we could have built it pretty quickly.

That was actually part of the problem.

I said something like, “I can give this to my coding tools and build whatever you want. It will do what you are asking. But something about this does not feel right. The product experience feels off. The user experience feels, unexpected. I think we need to push on this before we build it.”

And then the truth came out. The client had already met about it. A group of them had debated it for a while. They were not thrilled with the solution either. It was simply the best they had been able to come up with from their vantage point, given the constraints, the time frame, and the context they had. They ended the meeting on time, but without feeling good about where they were at.

That detail matters, because this was not a case of a client being careless. They had done the work. They had sat with the problem. They had debated the options. They had come to the best conclusion they could reach with the people who were in the room with the time they gave themselves to think about it.

But the person missing from that room was the product and UX person.

That was the gap. Not intelligence. Not effort. Not concern for the user. The gap was vantage point. They understood the business situation and the operational need, but they could not quite conceive of the right product flow from where they were standing. They could describe the pain. They could describe the edge case. They could describe what they thought the platform needed to do. But they needed someone in the room who could translate that pain into a cleaner product experience.

That is where the meeting became valuable.

We did not say, “Okay, this is good enough, let’s just build it.” We decided to stay inside the idea until it felt right. If that meant extending the meeting, we would extend the meeting. If that meant calling another meeting, we would call another meeting. The important thing was that we were not going to take an awkward solution, wrap it in a ticket, and throw it over the fence just because the execution was easy.

This is one of the biggest traps in the AI world. There is not always enough pain in the build process anymore to force the hard conversation. In the past, if something was going to take three weeks, cost real money, and require a whole team to implement, people had more incentive to stop and ask, “Are we sure this is right?” Now the answer can be, “Well, let’s just have the AI build it and see.” That sounds harmless, but it can quietly train teams to accept half-baked thinking because the cost of implementation feels low.

But the cost is still there. It just moved.

The cost shows up in the product. It shows up in the user experience. It shows up in the maintenance burden. It shows up when the next edge case arrives and the team has to stack another awkward flow on top of the first one. It shows up when the product starts to feel less like something designed and more like something accumulated.

So we stayed with it.

We started with the situation, not the proposed solution. What was actually happening? Who was being invited? Why did this case exist? How often would it happen? What would break if we did nothing? Was this even a problem we needed to solve inside the product, or was it a rare enough case that the cleanest answer was to leave it alone?

That is always the first place I want to start: is this really a problem?

But the meeting is not only valuable because it helps you identify the real problem. That is part of it, but it is not the whole thing. The real magic is that, once the right people are in the room, the group can start creating answers that no single person could have created from their own vantage point.

That is what happened here. The client understood the business situation. They knew why the edge case mattered. They understood the operational pressure that had created the request in the first place. I understood the product patterns, the platform, and the UX tradeoffs. Someone else understood how the users were likely to encounter the flow in the real world. Each person had a piece of the truth, but no one had the whole thing.

That is why good meetings are not just status updates. They are creative instruments.

One person says, “Here is the problem.” Another person says, “That solution feels too heavy.” Someone else says, “But we still need to account for this edge case.” Then someone throws out a rough idea, someone else sharpens it, someone else breaks it, and someone else finds the simpler version hiding underneath it. The solution emerges through the bounce. It is not brainstorm theater. It is not everyone putting sticky notes on a wall so we can pretend collaboration happened. It is the real collision of perspectives.

This is where creative solutions come from. Not always from one genius having one perfect thought, but from many capable people bringing their partial views into the same room and letting those views interact. Sometimes the result is simply a cleaner solution to the problem in front of you. Other times, if the group is good and the room has enough trust, you find something genuinely novel. You find a flow, a campaign, a product move, or a strategic angle that nobody could quite see until everyone started working it together.

Once we talked through the invite flow from that angle, the right answer became almost obvious. It was not obvious before because the conversation had been happening from the wrong altitude. They were trying to invent the interface from the business problem. My job was to help them stay with the business problem long enough to discover the interface that actually belonged to it.

That is the kind of thing that does not happen when everyone is working in silos. It does not happen when a product discussion gets flattened into a ticket. It does not happen when the team treats the AI tool as the missing collaborator. AI can help produce versions, mockups, flows, and code, but it cannot replace the moment where the right people get in the room, bounce their perspectives off one another, and collectively discover an answer none of them had when the meeting started.

That is the magic in the meeting.

Remote Work Has Made This Harder

One of the hidden costs of remote work is that we do not gather the way we used to.

I am not saying every company needs to be in person all the time. Remote work has real benefits. Deep work matters. Flexibility matters. Not every conversation deserves a meeting. But some problems absolutely do.

Some problems need a room.

Sometimes that room is physical. Sometimes it is a video call that everyone agrees to let run long. But the principle is the same: we need focused, shared attention. The trouble with remote work is not simply that people are in different places. The trouble is that everyone is fragmented.

Someone has another call at the top of the hour. Someone is half-listening while answering Slack. Someone is waiting for the document. Someone else is interpreting the ticket differently. Someone is asking AI to generate options without ever forcing the real conversation to happen.

And slowly, the work becomes siloed.

People stop solving problems together and start throwing artifacts over the fence. A ticket becomes a substitute for a conversation. A mockup becomes a substitute for strategy. A generated implementation becomes a substitute for judgment.

That is how teams lose the magic.

The War Room Is Coming Back

This is why I have been thinking more seriously about the idea of the war room.

Not as some performative business cliché. I mean an actual focused working session where the right people gather, clear the distractions, and stay with the problem until something breaks open.

For my own company, this has become an important concept. Sometimes we need to be in person. Sometimes we need to immerse ourselves in a product for a day, or several days. Sometimes we need to say, “This is what we are solving this week. We are not scattering our attention across ten calls, twenty Slack threads, and a graveyard of half-written tickets. We are going to sit with this until we understand it.”

That kind of focus is increasingly rare.

Which makes it increasingly valuable.

The war room is not about rejecting modern tools. It is the opposite. The tools make the war room more powerful.

In the past, a meeting might end with a whiteboard, a few sketches, and a list of next steps. Today, with AI and modern prototyping tools, a meeting can end with real artifacts. Mock ups. Flows. Copy. Code. Data models. Working prototypes. Multiple directions explored in real time.

That is incredible.

But the tool is not the magic.

The meeting is still the magic.

The tool just lets the magic become tangible faster.

AI Is the New Execution Machine

For years, a lot of companies treated outsourced teams as execution machines.

The thinking was simple: we will decide what needs to be built, write it down, send it across time zones, and get back the implementation. Sometimes that works for well-defined tasks. But it rarely works for ambiguous product problems.

The reason is simple: outsourced execution teams are often structurally removed from the magic. They are not in the room. They do not have the full context. They are not part of the debate. They are handed decisions after the most important thinking has supposedly already happened.

Now AI gives everyone an execution machine.

A much faster one.

Which means the question becomes even sharper: if execution is no longer the bottleneck, what is?

The answer is people.

Not in a negative sense. People are not the problem because they are slow or inefficient. People are the bottleneck because judgment, taste, context, prioritization, and product intuition still live with people.

So the way to remove the bottleneck is not to remove the people. It is to focus them. We have to stop thinking in terms of bottlenecks and remember that the people are the point! We build for the benefit of people.

Get them in the room. Give them the context. Let them challenge the premise. Let them use the tools in real time. Let them make decisions while the problem is still alive, instead of waiting three weeks for someone to interpret a stale ticket.

The Future Belongs to Better Meetings

I know meetings have a bad reputation. Most of that reputation is earned.

Bad meetings are expensive. Status meetings are often wasteful. Recurring meetings with no decisions, no tension, and no real purpose can drain the life out of a team. But that is not an argument against meetings. It is an argument against bad meetings.

A great meeting is not a calendar event. It is a compression chamber for understanding and creativity.

It brings the right people into contact with the real problem. It creates enough friction for weak ideas to fall apart. It creates enough trust for people to say, “This does not feel right.” It creates enough focus for the obvious solution to finally become obvious. And sometimes, when the group is really working, it creates the conditions for a solution nobody walked in with.

In the age of AI, this matters more, not less.

Because we are going to be able to make more things faster than ever before. The winners will not be the teams that can generate the most output. The winners will be the teams that can decide what is worth making, and then bring the right minds together long enough to make it better than any one person could have made it alone.

Those decisions will not come from isolated prompts, scattered tickets, or one person quietly asking a machine to validate their first idea.

They will come from people gathering around a problem with enough focus, humility, and taste to get to the truth.

The magic is still in the meeting.

Only now, when the meeting is good enough, you can leave the room with the idea, the plan, and the first version already in your hands.