Four cases
You are not managing people. You are managing the invisible architecture that stops them from moving.
Four cases. Each one looks like a people problem. None of them is.
Productive Stasis
"They're both working.
There are calls, updates, slides.
The project is not moving."
"I put two solid people on this. They show up, they communicate, they produce material. Three months in, we're in the same place."
He had checked everything. The right people, the right setup, the right level of autonomy. Nothing was wrong. That was exactly what he couldn't explain.
The project wasn't stalling. It was running perfectly — just without an end.Every exchange generated the next one. Every update reopened the process instead of narrowing it. Every draft became a conversation. Neither of them resisted the work — the collaboration depended on both of them staying fully engaged. Nothing inside the collaboration forced either of them to take the final position. The structure only produced continuation. Never commitment.
Structural Absence
"They work well together when she leads.
When she steps back,
he disappears."
"She's fast, she frames everything before the meeting starts. He's capable but only shows up fully once she's set the ground. I need two people who can build together, not one who leads and one who follows."
He wasn't disengaged. He wasn't waiting to be told what to do. He was waiting for the specific moment when his contribution would be necessary — and that moment never arrived.
Her way of moving consistently removed the moment in which he would have had to create momentum himself.She wasn't dominating. She was doing what she did well — framing fast, removing ambiguity, creating the conditions for the work to start. And in doing it precisely, she made his full participation structurally unnecessary. The asymmetry wasn't in their capabilities. It was in the sequence. She always moved first. The structure never required him to.
Filtered Signals
"I always find out too late.
By the time I know there's a problem,
it's already a crisis."
"I keep asking. They give me exactly what I need to hear. Three months later, I find out the situation was completely different."
She had done everything right. Open door, direct questions, explicit asks for the real picture. The answers were always fine. The situation never was.
She thought the problem was that her team didn't communicate. The actual problem was that they communicated perfectly — they had just learned to communicate only what the structure could receive.The point of failure wasn't the team's silence. It was the specific way she reacted when reality didn't match her map — interrupting, reframing, resolving before the other person had finished — and how the system had reorganized itself to avoid putting her in that position again.
Ownership Shifting
"Something went wrong.
Everyone was involved.
Nobody owned it."
"I can't find where the decision lived. They all worked on it, they all knew what was happening. But when I ask who was responsible, I get four different answers and none of them is 'me'."
He had been there for all of it. So had everyone else. That was the problem he couldn't name.
Nobody was lying. Nobody was evading. The manager had explained the rationale so completely that the outcome no longer felt like a decision she owned. The senior had been fully invested — until the moment it failed, when her investment disappeared and the context took the blame. The juniors had executed exactly what they were given, which meant they had never made a decision that could be traced back to them.
Responsibility circulated perfectly. Which is why nobody ever held it.Most teams try to solve these behaviorally.
That's usually why the pattern survives.