The thing no one in the room can say out loud

Ryan Tindall · Grantic Operations

A program is late. Everyone knows it is late. The status meeting happens anyway.

The reports are careful. One workstream is green. Two are amber, which everyone understands to mean red. Someone says they are waiting on inputs. Someone else says the vendor has been slow. A date gets moved out three weeks, and nobody argues, because arguing would mean saying the part that is actually true.

The meeting ends on time. Everyone is polite. Nothing changed.

I have sat in a lot of those meetings. In motorsport, where a deadline is a green flag and cannot move. In a factory, where a line is either running or it is not. In a software company, where the release date was promised to a customer who is now calling the chief executive. The industries were different. The meeting was the same.

Work that has stalled is almost never stalled for the reason on the slide.

The reason on the slide is usually a symptom

Late programs get described as schedule problems. Add resources, extend the date, work the weekend. Sometimes that is right. Most of the time it is not, because the schedule is not what broke.

What actually broke is usually one of four things.

Two people who need each other are not speaking, and everyone has quietly designed around the gap.

A decision was never actually made. It was discussed, everyone left assuming a different outcome, and the work split into two versions of the plan.

Nobody owns the part that spans two groups. Each side believes the other has it. The work sits in the space between them, where it is nobody’s fault and nobody’s job.

Or somebody knows this will not work and has decided the cost of saying so is higher than the cost of being right later.

None of those show up in a status report. All of them show up in a room, if you are watching the room instead of the slides.

What I watch

I watch who talks first, because it is usually the person with the least at risk.

I watch who defers. When a capable person suddenly says that is really a question for the other team, they are not routing the question. They are avoiding it.

I listen for hedging. Not the ordinary kind. The specific kind, where a person who normally speaks in clear sentences starts using the passive voice. It was decided. The requirements were understood to be. People do that when they are describing something they do not want their name attached to.

I notice the question nobody asks. Every stuck program has one. It is obvious, it is simple, and it hangs in the air for an hour while everybody talks around it.

And I pay attention to what happens after the meeting. The real conversation is in the corridor, in the car park, in the message that starts can I call you. If three people separately find a reason to tell me the same thing privately, that thing is the actual problem, and nobody is going to say it with all of them in the room.

Why it stays unsaid

Not cowardice. Arithmetic.

In most organizations, the person who names the problem inherits it. They also become the person who made a colleague look bad in front of the boss. The personal cost of speaking is immediate and certain. The cost of staying quiet is shared, delayed, and belongs to everyone, which means it belongs to no one.

Smart people do that arithmetic in about two seconds, and they get it right. Staying quiet is the rational move. That is exactly why the problem survives contact with a room full of intelligent, well-intentioned professionals for months at a time.

What actually moves it

You cannot solve this by asking people to be braver. You solve it by changing the arithmetic.

I say the thing myself. I am the outsider. I have no reporting line, no history with anyone, and nothing to protect. When I name it, nobody in the room had to pay for it. That alone unsticks more programs than any process I have ever installed.

I say it without blame. Two groups are building to different assumptions is a fact people can work with. Engineering ignored the brief is an accusation people have to defend against, and defending takes weeks.

I put it in writing the same day. One page. What was decided, who owns it, by when. Half of what goes wrong in complicated work is that decisions evaporate between the meeting and Monday.

I put a name on every open item, including the ones that sit between two groups. Shared ownership is not ownership. Someone’s name goes on it, and that person is allowed to ask for what they need.

Then I make honesty cheap. If the first person to report bad news gets helped instead of blamed, the second one comes faster. That is the whole cultural intervention. It is not a value on a wall; it is what visibly happens to the first person who tries it.

How you know it worked

Not by the plan looking better. Plans always look better after someone has had a go at them.

You know it worked when the work starts moving again within about two weeks, and when the next piece of bad news arrives early enough to do something about it.

And when it is over, the story inside the company is not about the outside person who came in. It is about the team that got it done. That is the correct outcome, and it is not modesty. A recovery that depends on me being in the room has not recovered. It has been supervised.

The group takes the credit, because by then the group has earned it.