The Rounds Journal · Management & leadership

Healthcare leadership styles: choosing an approach for the situation

Compare directive, collaborative and coaching approaches through practical healthcare management situations. Choose an approach for the decision, not a label for yourself.

Written byThe Rounds editorial team
Published
Reading time5 min read

A useful way to think about leadership styles is to ask what the situation requires: a clear instruction, a shared decision, a learning conversation or coordination across several teams. A manager can use more than one approach. The test is whether people understand the decision, their responsibilities and when to raise a concern.

A directive approach: clarity when discretion is limited

A directive approach states what must happen, who is responsible and the boundaries of the task. It may be appropriate when a required process is already established or a deadline leaves little room to redesign the work. Explain the reason and the escalation route. Clear direction should not prevent people from reporting a problem.

For safety-critical work, use the organization’s approved procedures and escalation arrangements. A general leadership article cannot tell a team which clinical instruction to give.

A collaborative approach: improve a process with the people doing it

Imagine a department revising its administrative rota. Colleagues understand practical constraints that a spreadsheet may hide. Invite their input on a defined question, such as how to cover a predictable workload within agreed hours. Say what is open to change and what is fixed.

Consultation becomes frustrating when people believe they are deciding something that has already been settled. Be explicit about who will make the final decision and how competing preferences will be handled.

A coaching approach: build someone’s judgment

When a colleague is learning to prepare a service report, ask them to explain the question, the evidence and the decision they think it supports. Give feedback on the work and agree what they will try next. Taking the report back and completing it yourself may solve today’s deadline while leaving the development need untouched.

Coaching still needs boundaries. Define which decisions the colleague can make, what needs checking and when they should seek help.

A strategic approach: connect separate teams to one aim

A service change may involve staff, technology, finance and operations. Explain the problem the change is meant to solve, the evidence behind it and the tradeoffs. A compelling aim is useful only if someone can turn it into responsibilities and measures.

For a worked approach to measures, see the quality-improvement guide. A new initiative needs a way to detect unintended effects as well as progress.

Review your approach after the decision

  • Did people know what was expected?
  • Did the people with relevant information get a chance to contribute?
  • Was the final decision and its owner clear?
  • Could colleagues raise a concern without uncertainty about the route?
  • Did the approach develop judgment, or leave every decision with you?

These questions are an editorial reflection exercise, not a validated leadership assessment. They can help you bring a specific development question to supervision, mentoring or further study.

Continue with team communication and the move into management.

Explore study around your background and goals →

Match the style to what the team needs to decide

Imagine a service has scheduled a trial of a new process for routing routine facilities requests. On the first morning, several staff members are unsure which queue to use. A manager could give a direct instruction about the agreed queue and name the person to contact if anything looks wrong. Once staff have had time to try it, the manager could ask them to identify which requests are handled well and which are being returned. That later conversation calls for a style that makes it easy for staff to raise problems and shape the next decision.

Suppose one coordinator wants to learn how to run the review. Agree which decisions they will own, set a review date and ask them to explain how they will gather input from each shift. Give feedback on their plan and let them run the discussion with the agreed support. Coaching is more useful when the person gets to practise a responsibility and can tell how they did. If they are still new to the process, provide a clear starting structure and check their understanding first.

Switch styles without making the boundary confusing

Tell people which parts of the decision are open. For example, an agreed approval step may be fixed while the team is free to suggest a better way of gathering the information needed for approval. If the team is being consulted, say who will make the decision and when. If you delegate it, confirm who has authority, what constraints apply and how an exception will be raised. This prevents colleagues from investing effort in a decision they thought was theirs to make and later learning that someone else held the authority.

After the change, ask what people understood, where they felt able to contribute and where they waited for a decision. Compare the responses from staff with different roles and shifts. If colleagues understood the goal but repeatedly checked small details with you, clarify what they may decide themselves. If they had discretion but lacked information, work on the information flow before changing how much control you delegate.

Keep a short record of what you tried and revisit it when the team or the situation changes. The same colleague may need clear direction in an unfamiliar task and room to lead a process they understand well.

Explore more resources →