Good management reduces unnecessary decisions for the team
In construction projects, many teams are not slow because they lack capability. They are slow because every day they have to guess too many small things that the management system should have made clear from the start.
In construction, I have seen many teams that are not actually slow because they lack capability.
They are slow because every day they have to decide too many small things on their own:
- Which file is the latest version?
- Is this view for review or for issuing?
- Is this model reliable enough?
- If I see a clash, who should I tell?
- Has this detail been confirmed by the engineer, or is it still just an assumption?
Each question on its own looks small.
But when you add them up across a project with many disciplines, many deadlines, and many people editing the same model, it becomes a very heavy kind of friction.
And the dangerous thing about this friction is that it usually does not appear in any report.
It shows up only as:
- The people doing the work get tired.
- The reviewer has to ask again.
- New joiners do not dare to decide.
- The experienced people get pulled into every small thing.
- The manager thinks the team is not proactive, when in fact the system is forcing the team to guess too much.
Management is not about deciding for everyone
A good manager does not need to decide everything.
But a good manager has to design an environment where other people can decide correctly within their own scope.
For example, in BIM delivery, if a modeller always has to ask:
"Which template should I use for this?"
"Is this naming following the standard?"
"Is this view going to be used for sheet output?"
then the problem is not only with the modeller.
The problem is that the system is not clear enough.
The person doing the work does not need more pressure.
They need boundaries.
They need to know:
- Which decisions they are allowed to make on their own.
- Which decisions must be escalated.
- Where the source of truth is.
- Which level of completeness is enough at each stage.
When the boundary is clear, the team does not need to ask permission for every small thing.
And that is what real speed looks like.
More rules does not necessarily mean more professional
Some teams believe that good control requires many rules.
More folders.
More naming conventions.
More checklists.
More approval layers.
But if a rule does not help the person doing the work decide faster, it is just another layer of pressure.
A good rule has to answer one question:
"Who does this save from guessing?"
If it cannot answer that, the rule may exist only because we are afraid of losing control.
In construction projects, complexity is unavoidable.
But the way we manage should not make it more complex than it already is.
A good system is not one that has a lot of things.
It is one that lets the right role see the right information, at the right time, with the right level of reliability.
Reducing unnecessary decisions is a form of leadership
Leadership is not always about standing in front of the team and saying inspiring things.
Sometimes leadership is sitting down and cleaning up a messy template.
It is renaming a view so it is clearer.
It is writing a short guideline instead of a 40-page document nobody reads.
It is removing an approval step that does not add value.
It is making clear who is responsible for what before the deadline arrives.
These things are not glamorous.
But they make the team feel lighter.
And in a high-pressure industry like construction, making other people feel lighter is a very large contribution.
Closing
I do not believe good management is about controlling every action of the team.
I believe good management is about reducing the number of unnecessary decisions, so the team has energy left for the decisions that really matter.
When the system is clear, people are more confident.
When people are more confident, they are more proactive.
And when the team no longer has to guess in silence, the quality of delivery improves on its own.