Pain statement
The team looks stable, but everything still depends on one strong manager to keep things moving.
Squads Depend on One Strong Manager
The team looks stable, but everything still depends on one strong manager to keep things moving.
Three daily scenes
- The squad only seems fast when the manager is involved.
- Decisions wait until the manager weighs in.
- The team can execute, but not independently.
What you probably tried
- Pushing ownership without changing the path of escalation.
- Adding more ceremonies to spread the load.
- Trusting time to fix the dependency by itself.
Why it did not solve it
A strong manager can hide the dependency instead of removing it.
The Push diagnosis
This is the Player Trap again: strength creates the bottleneck that the team has learned to route through.
Evidence block
Single CTA
Decide whether the team needs coaching, diagnosis, or a different starting point.
Related frameworks
Invisible ExecutorShows the hidden dependency pattern behind the team.
Related clusters
Coach for Engineering Managers Stuck as the BottleneckDirectly names the bottleneck pattern.