Don't use busyness to prove management competence

In many working environments, especially in construction, busyness is easily read as proof of competence.

The person who has the most meetings is important.

The person who replies to messages late at night is dedicated.

The person who is always in a rush is the one taking responsibility.

The person who has to approve everything is indispensable.

But the more projects I work on, the more I see:

A system that constantly needs one person in the middle to handle everything is not necessarily a good system.

Sometimes it is a sign that the system is depending too much on one individual.

Busy is not the same as effective

A manager can be very busy and the team still slow.

Because the issue is not whether the manager is doing a lot.

The issue is whether the team operates more clearly after each intervention.

If the manager solves one issue today but the team faces the same kind of issue again tomorrow, that is not effective management.

That is just firefighting.

Firefighting is sometimes necessary.

But when firefighting becomes the main management style, the team becomes addicted to the lead's presence.

Everything needs to be asked.

Every decision needs to wait.

Every risk gets pushed up to one person.

The result is that the manager is busier, the team is slower, and the system is weaker.

A good manager makes themselves less necessary in small things

To me, one sign of good management is this:

The repeated tasks no longer need much intervention from the manager.

Not because the manager has neglected the team.

But because the manager has clarified the process.

Cleaned up the template.

Standardised the naming.

Written a usable guideline.

Set the boundaries.

Made the escalation path clear.

Empowered the right people to the right extent.

When that is in place, the team runs better on its own.

The manager has time to look further ahead.

And the lead's energy goes to the problems that actually need judgement, not the repeated questions caused by a vague system.

Don't turn yourself into a bottleneck

In construction, bottlenecks are not only technical.

They also exist in the way decisions are made.

If everyone has to wait for one person to approve, that person is a bottleneck.

If everyone has to ask one person about the template, that person is a bottleneck.

If every problem has to pass through one person, the team is not really empowered.

Some managers enjoy the feeling of being needed.

That is very human.

But if the lead always wants to be at the centre of every decision, the team has a hard time growing.

Good leadership is not about making other people feel they cannot do without you.

Good leadership is about building a system so that other people can do better without having to wait for you on every little thing.

Calmness is a management skill

I respect leads who can keep a project calm.

Not because the project has no problems.

A construction project always has problems.

But a good lead does not turn every problem into a crisis.

They sort them:

• Which one needs immediate action.
• Which one needs clarification.
• Which one only needs an assumption noted down.
• Which one should be handled by the team within their own boundary.
• Which one truly needs escalation.

This calmness does not come from knowing everything.

It comes from a clear system, enough experience, and the ability to not overreact to every signal.

Closing

Don't use busyness to prove management competence.

A good manager is not necessarily the one with the fullest calendar.

A good manager is the one who makes the team guess less, wait less, and firefight less.

In construction, where pressure is normal, the value of leadership is not in creating more motion.

The value is in creating clarity.

Because once clarity is good enough, the team does not need to run around chaotically to prove that they are working.

The team can just do the right thing, at the right time, with a lighter mind.