Are people the cause, or are they absorbing a system that makes good work difficult?
What is happening
Everyone sees the problem. Each person may be seeing a different part of it.
How to use this page
You do not need a perfect match.
- 01
Choose the sentence that creates a pause, even if you cannot explain why yet.
- 02
See which different system tensions could produce the same visible pattern.
- 03
Keep the evidence questions before deciding what to change.
Eight recurring realities
Where a problem appears may not be where it is produced.
Work moves. Decisions do not.
“Everyone has a role, but no one can make the decision that actually moves the work.”
Adding approval layers, replacing a manager, or redesigning the workflow before seeing where authority and consequence diverge.
The organization depends on people who quietly hold it together.
“The system works because particular people remember, translate, chase, soothe, and catch what the formal process misses.”
Promoting, replacing, or documenting around the person without understanding the load the system has silently transferred to them.
Leaders become the exception desk for the whole organization.
“The team is working harder, but anything unclear, consequential, or politically sensitive still returns to me.”
Coaching the leader or telling the team to be more autonomous before designing how exceptions, information, and consequence should move.
New tools make the old confusion move faster.
“The system did not remove the ambiguity. It made more people encounter it, more quickly.”
Expanding licenses, replacing the tool, or automating more of the workflow before the organization can explain ownership and exceptions.
The structure changes. Authority does not.
“The organization chart is new, but everyone still knows where the real permission lives.”
Reorganizing again or changing personnel before tracing how permission, information, veto, and consequence actually move.
Every function sees the same problem differently.
“Every explanation is reasonable inside its own function. None explains what the organization is living through as a whole.”
Choosing one function's explanation as the organizational diagnosis because it is the clearest or most urgent.
A good design is being rewritten during implementation.
“Each local change looks reasonable. Together, they are removing the decision the design was built to protect.”
Accepting milestones based on output completion when the material question is whether the operating decision still holds.
Growth exposes operating debt that used to stay hidden.
“What looked like agility at a smaller scale depended on memory, proximity, and people absorbing the gaps.”
Adding process, management layers, or enterprise systems without identifying which informal capabilities must be preserved and which dependencies must end.
If nothing fits cleanly
That may be useful information—not a failure to explain.
You do not need to force the problem into a category. Share what is happening, what has been tried, and which decision is approaching.
Share what is happening →