When leaders inherit a function, control is the trap

Few leadership transitions are as challenging as stepping into a team that has recently been through change. The leader is new, the team is adjusting and everyone is trying to work out what comes next.

It's a time when many leaders feel they need to prove themselves quickly. That can lead to an understandable but risky habit: becoming involved in every decision, every process and every piece of work before they've fully understood how the function operates.

The intention is usually positive. The outcome is often very different. Employees who were trusted to do their jobs can start feeling second-guessed, and a team that was performing well can become less confident and less engaged.

What usually goes wrong

One of the first traps is confusing visibility with understanding.

A leader inherits a new function and wants to get across everything quickly. They start joining more meetings, asking for frequent updates, reviewing every piece of work or stepping into decisions that the team used to own. It feels responsible. It looks proactive.

But from the team’s perspective, it often feels like a lack of trust.

Over time, a few patterns tend to emerge:

• decisions slow down because everything needs approval
• the leader becomes the bottleneck
• team members stop using their judgment and start waiting to be told what to do
• more time is spent reporting on work than actually doing it.

It is a subtle shift but an important one. The leader moves from enabling the work to sitting on top of it.

Why it happens

Most leaders do not set out to micromanage. It usually comes from a mix of pressure and uncertainty.

There is often a strong desire to prove value quickly, especially after a restructure. The stakes can feel high. There is also the discomfort of not yet knowing what “good” looks like in a new technical area.

That uncertainty creates a natural instinct to get closer to the detail. To double check. To stay across everything.

There can also be a fear of missing something important. If something goes wrong, the leader does not want to be caught off guard. So, they tighten their grip.

The irony is that the tighter the grip, the less visibility they actually get. People stop surfacing issues early. Conversations become more guarded. The leader sees more activity but less of what really matters.

The impact on the team

Micromanagement is not just frustrating. It changes how people behave at work.

When employees feel closely monitored or second guessed, they tend to:

• hold back ideas or concerns
• avoid taking initiative
• become overly cautious in decision making
• disengage from the work.

Psychological safety drops. People stop speaking up because it does not feel worth it or safe to do so.

Performance also takes a hit. Not because people are not capable but because the environment no longer supports good performance. Work slows down, ownership weakens and energy shifts from delivering outcomes to managing upwards.

Trust is often the first thing to go and once it is gone everything becomes harder.

Building understanding without taking over

The goal is not to step back completely. It is to build understanding in a way that does not smother the team.

A few practical shifts make a big difference.

Start with structured listening

Before making changes, take the time to understand how the work actually happens. What is working well? Where are the pressure points? What does the team wish others understood about their function? What sort of leadership works best for them?

Observe before you redesign

Sit in on key meetings or workflows, not to control them but to learn. Look for how decisions are made, where delays occur and how the team interacts with stakeholders.

Map the stakeholders

Most functions are shaped by others around them. Understanding who influences the work and where competing priorities sit will give far better insight than reviewing more reports.

Ask better questions

Small shifts in language matter.
Instead of “What is the status?” try:

• “What is getting in the way?”
• “What options have you considered?”
• “What support do you need from me?”

These questions build understanding while still encouraging ownership.

Set clarity without controlling the method

Be clear on priorities, timelines, risks and what success looks like. Then step back. Let the team work out how to get there.

This is the difference between accountability and micromanagement. One creates clarity. The other creates dependency.

Resetting when it has already started

If micromanagement has already crept in, it is not too late to reset.

The first step is acknowledging it. Most teams will have already noticed the change in behaviour. Naming it openly can go a long way in rebuilding trust.

From there, the reset needs to be visible:

• reduce unnecessary check ins or approvals
• agree on a more realistic cadence for updates
• clarify what decisions sit with the team
• ask what would help them do their best work.

It is also worth reflecting on what is driving the behaviour. Is it a real risk issue or just discomfort with not knowing?

Leaders who can be honest about that tend to rebuild trust much faster.

A simple example

A leader inherits a specialist team in an area they have not worked in before. Wanting to stay across everything, they ask to review all outputs, request frequent updates and join most team discussions.

Within a few weeks, things slow down. The team becomes cautious. Decisions get pushed up rather than made.

The leader realises they have become the bottleneck.

They reset by holding one on one conversations, asking the team to walk them through key processes and agreeing on clear priorities for the next quarter. They move to weekly check ins focused on risks and support rather than status updates.

The shift is noticeable. The team starts taking ownership again and the leader gains a clearer understanding of the function without needing to sit in every detail.

Getting the balance right

Inheriting a new function does not require becoming the technical expert overnight but it does require resisting the pull toward control when things feel uncertain. Micromanagement often starts with good intent, but it quickly erodes trust, slows performance and reduces ownership across the team.

The real shift for leaders is learning how to build understanding without taking over the work. That comes from listening well, observing how things actually operate, asking better questions and being clear on outcomes rather than every step along the way. And if trust has already taken a hit, it can be rebuilt through honest conversations and visible changes in how the leader shows up day to day.

Ultimately, leading a new function requires a different way of thinking. Strong leaders do not need to know every detail to lead effectively. They need to create the conditions where people can do their best work and feel trusted to do it. If you've been asked to lead a new function, chances are it wasn't because you know every process better than the team. It was because someone saw your ability to lead people, make good decisions and bring out the best in others.

Trusting your team is not stepping back from leadership. It is leadership.

Further information

For assistance with your workplace matters, members of Australian Industry Group can contact us or call our Workplace Advice Line on 1300 55 66 77 for further information. Australian Industry Group has an extensive range of training courses to support employers on their learning and development journey.