Nothing went wrong in that meeting

The Tuesday exec sync. Eight people, all senior, all prepared. The agenda gets covered. Two people disagree about sequencing and it’s settled inside ninety seconds. Someone raises a risk and it’s noted. The room laughs once. It ends three minutes early.

The notes are accurate. Six actions, six owners, a date against each one. Nobody dominated. Nobody was talked over. Nobody left annoyed.

Look at the six actions. Every one of them is something the owner was already doing. The question the meeting existed to settle is sitting in exactly the position it was in at nine o’clock. Nothing said in that room redirected anything.

Now try to write the complaint.

Not a feeling — a sentence. Something you could put in an email to the person who chairs it. What would it say? That everyone was too reasonable? That the disagreement was resolved too quickly? That the actions went to the people who already owned them?

You don’t have it. There is nothing to point at.

The failure that leaves no trace

Most failure leaves something behind. The bad meeting certainly does. It runs forty minutes over. Someone gets cut off and doesn’t come back in. Two directors argue about a thing that isn’t the thing. People walk out irritated, and by lunchtime three of them have said so to someone.

That meeting is unpleasant. It is also legible. You can name what happened, and some of it you can fix.

The Tuesday sync leaves nothing. No overrun, no conflict, no dead air. It produces a clean and accurate record of a conversation that didn’t move — and a clean, accurate record is indistinguishable from a good meeting.

So nobody complains. And because nobody complains, nothing gets recorded. The most frequent failure in leadership conversations is the one that leaves your organisation no evidence it ever happened.

The invisibility isn’t a side effect of this pattern. It’s the reason the pattern lasts. Nothing looks broken, so nothing gets fixed.

What the meeting research actually reports

A widely cited set of figures comes from a 2017 Harvard Business Review article by Leslie Perlow, Constance Noonan Hadley and Eunice Eun, reporting a survey of 182 senior managers across a range of industries. Seventy-one per cent said meetings were unproductive and inefficient. The figure gets quoted everywhere as proof that meetings are broken.

Look at the other findings in the same article. Sixty-five per cent said meetings kept them from completing their own work. Sixty-four per cent said meetings came at the expense of deep thinking. Sixty-two per cent said meetings missed the chance to bring the team closer together.

Every one of those reports what the meeting displaced, or how it felt to sit through. None of them reports whether the question the group met to settle moved.

Irritation is easy to ask about. Everyone has a view on it, and everyone’s view is available to them the moment you ask.

A flat meeting produces no irritation to report. It’s well run. It ends on time. Nobody is annoyed by it. Ask the eight people in that Tuesday sync how it went and most of them will say fine, and mean it. Whether it moved anything is a different question. These findings cannot answer it.

So the number the field uses to size the problem is pointed at the version of it that hurts, not the version that costs. That isn’t a flaw in the research. It is what happens when attention stays on how the hour felt and what it displaced.

It was competently produced

In September 1986, Chris Argyris published a piece in Harvard Business Review about how senior managers behave with each other and called what he found skilled incompetence: practised, routine behaviour — real skill — producing outcomes nobody in the room intended. Skilled in the sense that riding a bicycle is skilled. You do it without attending to it.

Top executives, he observed, tend to take some pride in being good at avoiding conflict. And they are good at it. Senior people are extremely good at raising a difficult point in a form that can’t be acted on. At agreeing in a way that commits them to nothing in particular. At converting a disagreement about substance into a question about sequencing — which is a smaller question, and a solvable one, and gets solved, which feels like progress.

Argyris asked executives to construct a difficult conversation in two columns. On the right, what they would actually say and how the exchange might continue. On the left, the thoughts and feelings they would withhold. The columns exposed the gap between the conversation being performed and the assumptions shaping it. Across the cases, the private reasoning looked remarkably similar.

None of this is bad faith and none of it is a deficiency in your particular team. Each of those moves is a reasonable thing for a competent adult to do in a room containing their peers, their boss and a decision that isn’t fully theirs. You made two or three of them on Tuesday, at speed, and you would struggle to say when.

Which is the point. The flat meeting isn’t a badly run meeting. It’s a competently produced one. Eight people each did something skilful and the sum of it was a conversation that went nowhere.

The team is running a theory it can’t see

Twelve years earlier, Argyris and Donald Schön had drawn the distinction that explains why this is so hard to catch from inside. People hold two theories of action. The espoused theory is the one they’d give you if you asked — sincerely, and usually an accurate account of what they value. The theory-in-use is the one their behaviour actually follows. The gap between the two isn’t hypocrisy. It’s mostly invisible to the person, which is exactly why it’s stable.

Teams have both. Ask a leadership team how its exec sync works and you’ll get something close to: we put the disagreement on the table early, we make the call, we commit. Nobody is lying.

Reconstruct the theory-in-use from Tuesday and it reads differently. Keep it moving. Don’t take a position you can’t walk back. Don’t open the thing that costs forty minutes. Let the person whose call it is make the call.

Both are real. Only one of them ran the meeting.

And then the loop closes, because the espoused theory is also what the team judges the meeting against afterwards. Assessed against we surface disagreement and commit, the Tuesday sync passes cleanly. There was disagreement. It got resolved. Actions were assigned. The team grades the meeting using the theory the meeting wasn’t following, and the meeting comes back fine.

Every instrument you have reports it as fine

Widen out from the team’s own judgement to everything else in the room, and the finding doesn’t change.

The calendar records that it happened, on time, with everyone present. The recording and the summary produce an accurate account of what was said. The action list has six items and six owners. Attendance is full. The pulse survey shows nobody was annoyed. The decision log shows a decision was logged.

Every one of those is measuring one of two things. The container of the meeting — how long it ran, who came, whether it held to the agenda. Or the record of it — the sequence of what was said. Both are real, both are worth having, and a team is better off with them than without them.

Neither is pointed at what determines whether a leadership conversation moves: what the group is producing while it is producing it. Whether the question changed position. Whether the disagreement that was in the room got into the room. Whether what people agreed to is what they’ll do about it on Monday. None of that is in the container. None of it is in the record. It happens between people while they are still in the conversation, and it is never written down.

So the meeting comes back fine. Not because the diagnostics are failing. Because fine is the answer they are built to produce.

One shape of a larger condition

This is the shape the condition takes most often, and the one nobody catches at the time. Another looks like its opposite: three hours, genuine effort, every angle examined, no direction chosen. Nobody misses that one. Everyone in the room can feel it while it’s running.

Underneath, the condition is the same. A group worked on a consequential question and the question did not move. The shapes differ in whether anyone notices. They do not differ in the result.

The flat version concentrates in the rhythms that recur — the weekly exec sync, the project review, the strategy check-in. It also runs in rooms where the decisions are largest and the stakes are highest. There, the same invisible non-move costs a great deal more.

Thursday

There’s a meeting on your calendar this week that will go like this. Not a difficult one. A regular one, with people you trust, on a question that actually matters.

It will start on time and cover what it was called to cover. Someone will disagree briefly and it will be resolved. The notes will be accurate and the actions will be assigned to the people who already own them. Afterwards, everyone will describe it as a decent use of an hour, and they will believe it, and nothing in the room will contradict them.

Nothing will go wrong in it.

Sources

Chris Argyris, “Skilled Incompetence,” Harvard Business Review 64(5), September–October 1986.

Chris Argyris and Donald A. Schön, Theory in Practice: Increasing Professional Effectiveness (Jossey-Bass, 1974), on espoused theory and theory-in-use.

Leslie A. Perlow, Constance Noonan Hadley and Eunice Eun, “Stop the Meeting Madness: How to Free Up Time for Meaningful Work,” Harvard Business Review 95(4), July–August 2017: 62–69. Survey of 182 senior managers across a range of industries.