There was a time earlier in my career when a structural change in our organisation felt deeply frustrating. At the time, my team worked closely with consultants from the United Kingdom. The relationship was direct and efficient. If we needed clarification, we reached out. If they needed updates, they contacted us. Decisions moved quickly because communication flowed freely.
Then a new director joined the organisation.
One of the first changes she implemented was simple but significant: all communication with the consultants would now go through her.
She became the window.
No more direct requests. No more direct discussions. Everything had to pass through her before reaching the consultants, and everything from the consultants came through her before reaching us.
We did not take this well.
To us, it felt like a loss of autonomy. We had been trusted to handle our work, to communicate professionally, and to manage relationships directly. Suddenly, the system felt slower and more controlled. We wondered why something that worked perfectly well had to change.
Looking back, I realise that our reaction was natural. From where we stood, the change looked like unnecessary control. But years later, sitting in a different role within another organisation, I found myself standing in a similar place.
And the view from the middle looked very different.
When Autonomy Feels Like Trust
In most professional environments, autonomy is closely tied to trust. When people are allowed to communicate directly with stakeholders, make decisions, and manage their own requests, it signals confidence in their capability. It gives individuals a sense of ownership over their work and a feeling that their expertise is recognised.
This is particularly true in knowledge-based environments such as education, banking, consulting, or technology. Much of the work depends on judgment, collaboration, and continuous dialogue.
When autonomy is suddenly reduced, the first emotional response is often not operational but psychological.
It raises quiet questions in people’s minds.
- Do they not trust us anymore?
- Did we do something wrong?
- Why are we suddenly being filtered?
These reactions are understandable. People care deeply about their professional identity, and autonomy often feels like a reflection of their competence. But organisational structures are rarely designed only around individual psychology. They are usually responding to something else.
Something less visible.
The Invisible Problem of Unstructured Requests
One of the things I have learned over time is that informal systems often work well—until they do not.
When communication flows freely between many different people, work can move quickly. Problems get solved faster because fewer layers are involved. Conversations feel natural rather than procedural. However, informal systems also carry hidden risks.
- Requests come from multiple directions.
- Decisions are made without shared visibility.
- Different people respond in slightly different ways.
- Workloads become uneven without anyone noticing.
Over time, these small inconsistencies accumulate.
From an individual perspective, each interaction might make sense. But from an organisational perspective, the overall picture becomes harder to manage.
- Who approved this request?
- Why did one faculty receive a different response than another?
- How much time is the team spending on these requests?
Without a central point of visibility, it becomes difficult to answer these questions. This is often the moment when leaders introduce structure.
Not because people are incapable, but because the organisation needs a clearer system.
The Function of the Middle
Middle management is one of the most misunderstood layers in organisations.
When people think about leadership, they often imagine senior executives setting direction or frontline teams executing the work. The middle layer sits between these two worlds, translating strategy into operational reality.
But this role is rarely visible from either side.
- From the top, middle managers are expected to deliver results, maintain consistency, and ensure that work aligns with organisational priorities.
- From the team’s perspective, middle managers can sometimes appear as barriers or gatekeepers.
In reality, their role is often something else entirely.
They absorb complexity.
- They filter competing demands from different stakeholders.
- They negotiate expectations upward and downward.
- They create structure where none previously existed.
Much of this work happens quietly. When it is done well, the team experiences fewer disruptions and clearer direction. But because the work is invisible, it can easily be misunderstood.
What looks like control from the outside is sometimes simply coordination.
Seeing the System Differently
Recently, I found myself reflecting on this dynamic again.
Within my own team, there was a shift in how requests from faculty would be handled. Previously, team members had more autonomy to communicate directly and manage requests independently. Under the new structure, requests would now pass through a central point before being assigned.
The reaction from the team was familiar.
They were not happy.
It reminded me immediately of that earlier moment in my career when a director had introduced a similar system. Back then, I had stood firmly on the other side of the conversation.
But this time, I noticed something else.
The centralisation of requests actually reduced the burden on the team. Instead of responding to constant ad-hoc messages, they could focus on the work itself. Instead of negotiating scope with different stakeholders, someone else managed those conversations.
The structure created breathing space.
It allowed the team to concentrate on execution while someone else handled coordination.
In other words, the system did not remove their capability.
It redistributed responsibility.
Growth as Perspective
Career growth is often described in terms of promotions, titles, or expanded responsibilities.
But one of the most meaningful forms of growth is perspective.
As professionals move through different roles, they begin to see the same organisational dynamics from multiple vantage points. Situations that once felt frustrating start to reveal their underlying logic.
What once looked like unnecessary control begins to resemble coordination.
What once looked like hierarchy begins to resemble accountability.
This does not mean that every organisational decision is perfect. Structures can certainly become overly rigid or bureaucratic. But many systems exist for reasons that are not immediately visible from a single position.
Understanding this is part of leadership maturity.
It requires the ability to step outside one’s own experience and consider how the system functions as a whole.
The Balance Between Structure and Autonomy
Of course, centralisation should not become permanent rigidity.
Healthy organisations eventually move toward balanced systems where routine matters are decentralised while strategic or sensitive decisions remain coordinated.
In practice, this means that once patterns become clearer, certain requests can be handled directly by team members without requiring escalation. Structure provides the initial visibility needed to identify these patterns.
The goal is not control for its own sake.
The goal is clarity.
When people understand the boundaries of their authority and the processes that support their work, they can operate with confidence and consistency.
Structure, when designed well, does not remove autonomy. It makes autonomy sustainable.
The Quiet Work of Leadership
Perhaps the most surprising realisation in this journey is that leadership often involves work that others never see.
It involves sitting between different expectations and trying to reconcile them. It involves absorbing pressure from multiple directions while ensuring that the team remains focused on their work.
Sometimes it means becoming the point through which information flows.
Not to restrict others, but to stabilise the system.
This kind of leadership rarely feels glamorous. It is less about bold decisions and more about quiet coordination.
Yet it is often the difference between organisations that function smoothly and those that struggle with constant friction.
Looking Back
If I could return to that earlier moment in my career, when my team first reacted with frustration to the new director’s communication structure, I would probably still feel the same initial reaction.
After all, autonomy matters.
But I would also recognise something I did not see then.
Leadership sometimes requires stepping into the middle of a system—not to control it, but to hold it together. And when you stand in the middle long enough, you begin to understand something important.
The view changes.
What once felt like limitation begins to reveal its purpose.
And growth, more often than not, is simply the moment when you realise that the system you once resisted is the same one you are now responsible for sustaining.
Leave a Reply