Part 2 of a series on leadership styles in real workplaces
It's the most misunderstood leadership style in the room. People mistake it for democracy. It isn't. Here's what it actually is, when it works, and when it quietly demotivates your best people.
Picture this. You are the project director on a large mixed-use development in Riyadh — say, a residential and retail complex rising off King Fahd Road. It is Tuesday morning, and you have just learned that one of your major concrete suppliers cannot deliver on schedule. Pouring is meant to start in 48 hours. Your client is sensitive. Your team is watching.
You call your senior site engineer and your procurement lead into your office. You ask them: what do you think we should do? You listen carefully. They each give their view. One suggests switching to a backup supplier even though the cost will be higher. The other suggests delaying the pour by three days and renegotiating with the original supplier.
You thank them. They leave. Then, alone at your desk, you make the call yourself.
This — exactly this — is the consultative management style. And whether you realise it or not, this is probably the way most decisions get made at workplaces.
So what is consultative leadership, really?
The idea is simple. The manager invites input from employees — but only when the manager asks for it. Employees aren't expected to walk in unprompted with suggestions; they wait to be consulted. And once the input is gathered, the manager makes the decision themselves. Sometimes that decision goes against the advice given. That is part of the style.
It is not democratic leadership. It is not delegation. It is a style where the manager keeps the final authority but actively pulls expertise from the team before using that authority.
“The team is asked. The team is heard. But the team does not decide. That is the bargain — and people need to know they are in it.”
When this style actually works well
Consultative leadership is not a fallback. It has its moments — situations where it is genuinely the right approach. Think of it as a tool you reach for in specific conditions:
→ When you are preparing for a big decision and need the perspectives before you commit
→ When problems pop up during the execution phase of a project
→ In topic-specific or project review meetings
→ When you yourself are being managed by a more senior leader who needs your input
→ When line and staff functions need to coordinate across a structure
It works best when your employees have average professional qualifications and a relatively low level of maturity in their roles — meaning they can contribute useful information, but they are not yet ready to own the full decision. It also helps when you, as the manager, have strong technical knowledge of what your team actually does. You need to understand their input to weigh it properly.
And critically — it shines in turbulent situations where decisions must be made quickly. On a construction site, fast decisions are routine. You don't have three weeks to build consensus when the concrete truck is two hours away.
A RIYADH SITE STORY
Back to the King Fahd Road project
The project director went with the backup supplier — not because his engineer suggested it, but because he had spotted in the procurement lead's comments that the original supplier had quietly been late twice in the last two months. That insight wasn't in either recommendation; it surfaced because he had listened carefully to how they spoke about the situation.
He made the call himself, in under twenty minutes, on his own authority. The pour happened on schedule. This is consultative leadership doing exactly what it is designed to do — gather signal, then decide fast.
The trade-offs nobody warns you about
Every leadership style has a cost. Consultative leadership is no exception. The trick is to know its real strengths and its hidden weaknesses before you commit to using it as your default.
|
+ WHAT YOU GAIN |
− WHAT IT COSTS YOU |
|
▸ Employees are encouraged to think along with you ▸ Decisions become more consistent over time ▸ Your people develop sharper professional judgment ▸ Motivation rises when people feel genuinely consulted ▸ Decisions get made faster than in consensus models ▸ You, the manager, end up better informed than you would alone |
▸ Responsibility can quietly shift onto employees who didn't actually decide ▸ Your most qualified people may feel sidelined — they want to own decisions, not just feed them ▸ It does not build teams. It builds one-to-one channels with the manager ▸ Employee-driven initiatives rarely get encouraged here |
The danger with your best people
Here is the part that catches most leaders off guard. The consultative style works beautifully with employees who are still developing. But your senior engineers, your most experienced site managers, your sharpest specialists — they often hate this style.
Why? Because being asked for input and then watching someone else decide feels, after a while, like being treated as a junior. A highly qualified employee wants ownership of decisions in their area of expertise. When you consistently consult them and then override or ignore their input, you slowly erode their motivation. They start to disengage. The best ones eventually leave.
“Your best people don't want to be consulted. They want to be trusted with the decision.”
It works best in centralised structures
One more practical condition matters. The consultative style fits naturally into organisations with a centralised structure — where authority flows clearly from the top, and the manager is genuinely the person who should make the final call. In flatter, more distributed organisations, it can feel uncomfortable or even paternalistic.
Many organizations in Asian continent operate exactly this way. There is a clear hierarchy. The project director or partner holds the authority. Consultation flows up. Decisions flow down. Within that structure, this style is a natural fit — provided it is used thoughtfully.
A stepping stone, not a destination
Here is something worth knowing. Consultative leadership is best understood as a preliminary stage. It is what you practise on the way to more developed leadership styles — particularly the cooperative and delegative styles where employees genuinely co-own decisions.
If you find yourself stuck in consultative mode forever, even with mature teams who have proven themselves over years, you are probably holding back your organisation. The whole point of consulting people is to develop them — to grow their judgment, their confidence, and eventually their authority. If you never let go of the final decision, you have used the style as a permanent crutch instead of as a stage of growth.
So when should you use it?
Use it when speed matters, when your team is still developing, when the organisation is structured around clear authority lines, and when you genuinely have better technical insight than your team does. Use it for specific decisions where you want input but the responsibility must clearly stay with you.
Don't use it as your everyday default — particularly not with senior, highly qualified specialists. Don't use it as a substitute for actually trusting your people. And don't use it forever. Use it as a stage, then move beyond it.
Back at the King Fahd Road site, the project director got the pour done on time. But the more important question is what happened the next time. Did he consult the same engineers again? Did he start trusting them with smaller calls of their own? Did he grow them — or keep them on the consultation seat indefinitely?
That answer, more than any single decision, defines whether consultative leadership is a strength of your management — or a quiet ceiling on it.
Leadership style is not a personality. It is a choice — made fresh for each decision, each team, and each season of the work.
