Ask for the counterargument
Everyone in the room loved the concept. That should have been the first warning sign, not the finish line.
The concept review went great. Heads nodded, someone said “love it,” and the deck closed to a warm murmur of agreement. We’ve sat through a hundred versions of that meeting, and here’s the uncomfortable truth about it: nothing happened in there. Not because the idea was bad. Because nobody in the room was looking for the way it might be.
Confirmation bias isn’t a character flaw. It’s the factory setting. The moment we fall for a concept, we start curating the evidence, and we do it without noticing: the supportive comment gets remembered word for word, the raised eyebrow gets explained away as someone having a rough morning.
Teams don’t gather feedback so much as they gather agreement, and agreement feels exactly like validation from the inside.
Darwin’s rule
Charles Darwin knew this about himself. He kept a personal rule: whenever he ran into an observation that contradicted his theory, he wrote it down immediately, because he’d learned from experience that inconvenient facts slipped out of his memory far faster than convenient ones. Think about that. One of the most careful observers who ever lived didn’t trust his own mind to hold onto disagreement. The rest of us are working with the same hardware and less humility.
Karl Popper pushed the idea further: a theory you can’t argue against isn’t a strong theory, it’s an untestable one. Swap “theory” for “concept” and the sentence still holds. If there’s no version of events where your brilliant campaign idea turns out wrong, you haven’t found a great idea. You’ve found one you haven’t examined.
Assign the critic
So we borrowed a practice from people who take being wrong seriously, and it’s blunt: before a concept we love goes anywhere near a client, someone on the team is assigned to argue against it. Assigned, out loud, by name. Not invited to share concerns if any come to mind. Given the job.
The assignment matters more than it sounds like it should. Volunteering criticism of a beloved idea carries social cost: you’re the person raining on the thing everyone just clapped for. Making it a role removes the cost. The critic isn’t being difficult; the critic is doing their job, the way a structural engineer isn’t being negative about your building.
A few rules keep it honest.
- Real, not theater. “Some might say it’s too bold” is a compliment wearing a disguise, and we treat it as a forfeit.
- The bar: the argument should be one we’d be embarrassed to hear for the first time from the client.
- The role rotates, because the same skeptic every time becomes furniture, and furniture gets ignored.
What survives the meeting
What we’ve noticed is that the concepts rarely die in these sessions. Mostly they change shape. A weak flank gets reinforced before anyone outside the building ever sees it. Occasionally the counterargument wins outright, and that stings for about a day, which is a bargain compared to what it costs to learn the same thing in market.
There’s a deeper effect, too, and it took us longer to spot. When disagreement becomes a scheduled part of the process instead of an act of courage, people stop bracing against it, and the whole team gets looser about being wrong in small ways early rather than being wrong in one large way late.
Applause is pleasant. It’s also nutritionally empty; it tells you the room likes you, which you presumably already knew. Friction is where the information lives.
The strongest concept we shipped last year was the one that survived the meeting where we genuinely tried to kill it. It walked out with a limp and a much better second act.
