Prototypes Before Meetings

I had an hour between meetings today and I shipped a working prototype. Real URL. Real enough that someone could click it and react. By the time my next meeting started, people were already leaving comments on it.

A year ago that sequence would have been a two-week project. A brief to agree on the problem. A kickoff to agree on the direction. A couple rounds of mocks. A review. Another review. Each meeting a negotiation. Each negotiation a little leak of the original energy. By the time the thing landed in front of people, the idea had been sanded down into something nobody felt strongly about.

I think most design orgs are still operating on a broken assumption: that meetings are where decisions get made. They never really were. Decisions get made the moment someone can touch the thing and react to it. The reason meetings used to feel like the decision point is that the thing didn't exist yet. You couldn't walk into a room with a working version. You walked in with a deck, or a mockup, or a sketch of what you thought it could be. So the room argued about the representation of the thing. That's all there was to argue about.

Now the thing exists before the meeting. You build it in the morning, ship a URL in Slack, and the debate is over before anyone prints an agenda. Opinions are cheap when there's nothing real to engage with. The moment there's something real, opinions have to get their hands dirty. Most opinions don't survive the contact.

This is the part most design leaders haven't fully internalized. They'll say they believe in "prototype-driven decisions." They'll nod along at the right moments. But look at their calendar and you'll see six hours of reviews a week. Look at their team's process and you'll see mocks as inputs to meetings, not mocks as decisions. The prototype is still treated as preparation. It's not. The prototype is the decision. The meeting is where you ratify it.

Once I started seeing it this way, my week changed. I spend less time arguing for ideas and more time making them real. My calendar has fewer reviews and more building sessions. I'd rather ship a rough version in the wrong direction and have the team correct it than talk through three directions and commit to the wrong one by consensus. The feedback loop is faster, the decisions are better, and the team trusts each other more because everyone's reacting to the same real thing instead of their own imagined version of it.

The hardest part isn't the skill to build things quickly. That part is getting cheap. The hard part is giving up the comfort of the meeting. The illusion that getting everyone in a room with a deck is the same thing as making a decision. It isn't. It never was.

Build the thing first. Show it. Let the thing do the arguing for you. The leaders who figure this out are going to run circles around the ones who don't.