A leadership team tells me something they’ve been noticing.
Every department seems busy.
Projects are moving.
People care about their work.
Individually, many teams are performing well.
And yet, the organization doesn’t seem to move with the same confidence as its people.
The natural questions follow.
Do we need better communication?
Should we restructure teams?
Are roles and responsibilities clear enough?
Those are all reasonable questions.
They just aren’t where I’d begin.
At this point, I’d have questions.
Quite a few of them.
How does information actually move through the organization?
Where do people naturally collaborate?
Where do they stop collaborating?
Which teams have quietly developed better ways of working?
Which teams are constantly reinventing the same solutions?
How does leadership learn what each team is experiencing?
And just as importantly, how do individual teams understand what leadership is trying to accomplish?
Because communication isn’t simply about sending information.
It’s about developing shared understanding.
Then I’d begin looking at the organization differently.
Not simply as one system.
But as a system made up of many smaller systems.
Every department develops its own habits.
Its own language.
Its own priorities.
Its own ways of solving problems.
Sometimes that’s exactly what helps teams excel.
But sometimes those local optimizations make it harder for the organization to learn as a whole.
A healthy organization doesn’t make every team identical.
It creates conditions where different teams can learn from one another.
That raises another interesting question.
When one team discovers a better way of working, how does the rest of the organization benefit?
Perhaps it doesn’t.
Perhaps valuable knowledge quietly remains where it was created.
Perhaps another team spends months solving the same problem independently.
Perhaps leadership never realizes that one part of the organization has already found an answer another part is searching for.
Those opportunities are easy to miss when every team is viewed in isolation.
Only after understanding how knowledge moves through the organization would I begin suggesting experiments.
Perhaps teams begin sharing not only outcomes, but how they arrived there.
Perhaps recurring conversations emerge between departments that rarely interact.
Perhaps leadership develops new ways of listening as well as communicating.
Perhaps the organization becomes better at learning from itself.
The goal isn’t simply to improve communication.
It’s to help the organization function more like a connected learning system.
Every organization is unique.
The situation you’ve just read isn’t a template.
It’s an example of how I approach complexity.
My goal isn’t to arrive with predetermined answers.
It’s to help your organization better understand itself before deciding what comes next.