We keep having the same meeting and never deciding anything.

What to do when you keep having the same meeting and never decide

Late two-thousands. A small startup is building a favourites-management app called MyFavorites.

The team — small, frugal, the founder among them — has been arguing for months about a single design question. Should users tag what they save with simple category labels, or with full sentence-structured phrases?

The argument is detailed. Each side has reasoning. The meetings are well-attended. Every fortnight, the team reaches the same conclusion: more discussion needed.

The product has not shipped.

It cannot ship, as it happens, because the answer depends on how real users behave — and there are no real users, because the product has not shipped.

The meetings continue. They feel productive, in the way detailed meetings can feel productive when nobody in the room has had to defend a position to a paying user. The argument cannot be resolved from inside the room.

The founder eventually shuts the company down. He never launches.

The post-mortem he writes a year later is unusually clear. The team had been having the meeting that should have been the launch. Every position internally consistent, every fortnight an opportunity to refine, no contact with the only thing that could end the argument.

The lesson is harder to take than it sounds. A meeting that cannot end is not the work. It can feel like the work. It can occupy the time of the work. But if there is nothing outside the room that could resolve it, the room is not where the work is.

So let's go to the office and work through it.

"We keep having the same meeting and never deciding anything."

The feeling is trapped.

You're walking into a room where the arguments are familiar, the positions are familiar, the people on each side are the same people on the same sides — and you already know how it ends. With the room agreeing it needs another meeting.

First tell a comfortable argument from a hidden contradiction

Two choices. They look identical when you walk in. They need different first moves.

When the debate has hardened into habit

Choice one: the team is comfortable in the argument. The meeting has become a ritual. Each position is internally coherent; each fortnight is an opportunity to refine; the cost of attending is roughly the cost of any other recurring meeting on the calendar. The argument has been repeating because, in any week of the year so far, repeating has cost less than concluding.

If that's the trap, the move is to change the cost structure. Schedule the next session as four hours, no break, in a room with no windows and no snacks. Not as punishment — as a cost. The meeting has been repeating because it has been cheap. Make it expensive in the legs and the bladder, and the decision turns out to have been available all along. Parkinson's Law, run backwards.

When a paradox is hiding underneath the debate

Choice two: there is a contradiction underneath the argument and naming it has been costing more than continuing it. The team has been circling a paradox — we need to ship every two weeks and we need zero regressions; we need to cut the budget and keep the team intact; we need this product to be enterprise-grade and consumer-simple — and the argument has been the team's way of pretending the paradox is a question with a right answer.

If that's the trap, the move is to put the paradox on the wall, written down, in one sentence. The argument tends to collapse the moment the contradiction is visible, because it turns out everyone in the room had already been working with it and pretending not to. Naming the trade-off is what lets the trade-off be made.

Cost, or contradiction. Same recurring meeting, two different first moves.

How to name what the room keeps avoiding

Three tools. The discipline is to surface what the meeting has been circling around.

Name the trade-off as a trade-off, not a question

The first is

Wicked Questions.

Wicked Questions comes from Liberating Structures, the facilitation pattern library codified by Henri Lipmanowicz and Keith McCandless in their two thousand and fourteen book of the same name. The lineage runs back through Harrison Owen's Open Space practice of the nineteen-eighties and a longer tradition in adult-education group work.

The reason Wicked Questions exists is that recurring meetings get stuck when the team is circling a real paradox without admitting that it is one. Each side argues for one half of the trade-off. Each side is right about their half. The standard meeting tools — agendas, decision logs, action items — are built for problems with answers. They aren't built for paradoxes.

The unique insight is the sentence form. How can we X and Y at the same time? — where X and Y are both things the team is committed to and they appear, on the surface, to contradict each other. How can we ship every two weeks and have zero regressions? How can we cut the budget and keep the team intact? The form does the work. It names the trade-off as a trade-off and refuses to pretend the question has an answer the team has been failing to find.

What you get is the recurring argument collapsing — because it turns out everyone in the room knew the contradiction was there. They had been pretending not to.

So. How to run it.

Frame. On the board, in one sentence, in the X and Y form. Both halves must be things the team is genuinely committed to. The form matters more than the wording — the question must contain both halves, side by side.

Open. Two minutes silent. Each person writes one or two sentences in response. Silent matters — the first voice typically narrows the room toward their reading of the paradox.

Name. Round the room, one contribution each. The facilitator's job is to keep the tension alive — to refuse the early offer of well, obviously the answer is X. The point is not to solve the paradox. The point is to acknowledge that the paradox is the territory.

The argument stops being about whether X or Y. It becomes about how the team carries both.

The second is

Put the real process on the wall, step by step

Event Storming.

Alberto Brandolini wrote up Event Storming in two thousand and thirteen as a software-design discipline — a way for engineering teams to model how a system actually works rather than how the architecture diagram says it should work. It has since travelled out of software, because the underlying problem is general.

Recurring meetings about how something works around here get stuck because the team has been describing the same step differently for months without noticing. Each person has a true description of their piece. Nobody has the whole. The argument continues because everybody is right about the part they touch.

The unique insight is the format. Orange post-its. Past tense. One event per post-it — the customer paid, the order entered the queue, the manager approved the discount. The room places the post-its on a wall in time order. That is the entire structural move. Past tense forces specificity. One event per post-it forces granularity. The wall makes the process visible to the whole room at once.

What you get is the place in the process where two people have been describing the same step differently. Once it's on the wall, it cannot be argued. The disagreement was real, and was hidden by everyone using the same words for different things.

So. How to run it.

Events. A long wall, a stack of orange post-its, ninety minutes. State the process you're modelling. Each person writes the events they touch, past tense, one per post-it — user signed up, email verified, place order, order placed — and places them on the wall.

Time. The post-its go up in roughly the time order things happen. Left to right. Quietly. No discussion yet.

Replay. The team walks the wall left to right. Disagreements surface as duplicate events under different language, missing events nobody owns, or events placed by two people in different positions.

No one person holds the whole story — the wall does. Disagreements that cannot be resolved on the wall become the next conversation — smaller and more specific than the recurring one.

The recurring meeting was about a process the team had not yet agreed to.

The third is

Estimate at once to expose two versions of the work

Planning Poker.

James Grenning formalised Planning Poker in a two thousand and two paper, refining Barry Boehm's Wideband Delphi from the nineteen-eighties. Boehm's technique came out of older expert-estimation work at the RAND Corporation; the current form lands during the Agile movement of the mid two-thousands.

Recurring meetings sometimes look like they're about direction but are actually about effort. The team argues about whether to do thing A or thing B; what they're privately disagreeing on is how much each one will take. The conversation cannot resolve because each person is estimating against a different mental picture of the work.

The unique insight is simultaneity. Each person picks a card from a modified Fibonacci deck — one, two, three, five, eight, thirteen, twenty — face down. On the count, everyone reveals at once. No anchoring. No senior voice steering the room toward their number. No junior estimate adjusting upward to match.

What you get is the spread. If everyone shows a five, the room agrees. A wide spread — half show three, half show thirteen — means the room has not been estimating the same thing. The spread, not the average, is the diagnostic. A team that holds the same work as both three and thirteen has been carrying two different versions of the work in the same conversation. That has been the conversation blocking the decision.

So. How to run it.

Pick. Each person has a deck of modified Fibonacci cards — one, two, three, five, eight. Read the work item out loud, briefly. No long discussion before the round — the discussion is what the technique is replacing. Each picks privately.

Reveal. All reveal together. Wait. Count. Reveal simultaneously.

Discuss. If the spread is narrow, the work is well understood; the room moves on. If the spread is wide, the outliers explain their thinking — not to be argued with, but so the room hears the different versions of the work that have been in play. Re-estimate.

Independent guesses surface what group debate buries. The decision the recurring meeting was blocking turns out to have been the conversation about what the work actually is.

That's the toolkit. One more story before we close.

The MyFavorites story we opened with is about a team holding a meeting that should have been the launch — the work was outside the room and the room had no way of getting to it. The story we close with is one move further. The work was no longer in the meeting; the meeting was still happening; the move was to close it down.

A precedent: cancelling the meeting nobody could justify

Mid two-thousands. Patty McCord is Chief Talent Officer at Netflix, working with Reed Hastings as the company transitions from DVD-by-mail to streaming.

The annual performance review cycle has been running for years. Managers spend weeks preparing each cycle — written summaries, ratings, calibration sessions, formal one-to-ones. Employees dread it. The written outputs sit in the HR system, where almost nobody reads them.

McCord's question to Hastings is the simple one. What is this for?

When the two of them look honestly at the previous several years — at promotions, salary adjustments, performance-improvement plans, departures — they cannot point to a single decision that came out of the formal review process that would not have been made anyway, from informal conversation. The reviews have been documenting decisions made elsewhere. The reviews have not been the place where the decisions were made.

The move is not to redesign the review process. The move is to cancel it. The annual review is closed down. The forms are retired. The calibration sessions stop.

The harder part is the relocation. The review meeting had been notionally handling the feedback that good people management actually requires — telling people clearly how they are doing, what would have to change for them to advance. That feedback now has to live somewhere. McCord's move is to relocate it into the continuous conversations between managers and people that had, in fact, been carrying it all along.

The Netflix Culture Deck, public from two thousand and nine, becomes the more famous artefact. Closing down the review cycle is the underneath move that made the deck possible.

So.

The MyFavorites team had been holding the meeting that should have been the launch. The work was outside the room, and the room had no way of getting to it. McCord's move is the inverse. The work had relocated; the meeting was still happening; the move was to close the meeting down.

Both moves come from asking the same question, honestly. What has this meeting been producing? Both teams were willing to take the answer.

The recurring meeting that never decides anything is almost always asking the wrong question. Or asking it of the wrong room. Or asking it after the room has stopped being where decisions actually happen.

So. Your Next Move from this playbook.

Which argument does your team have over and over again without resolving?

And what's the paradox underneath it that nobody has bothered to name?