Leadership
Situational leadership: choose the right support
Use situational leadership carefully: assess the specific task, agree useful support and review it without turning people into fixed categories.
An experienced colleague asks for help with a new task. You can read the request as a loss of confidence, or recognise that experience in one domain does not remove uncertainty in another.
Situational leadership is useful as a prompt to vary guidance and support according to the work. It becomes less useful when a manager assigns a permanent category to a person and treats that category as an explanation for every task.
The practical approach in this guide is modest: describe the task, establish the evidence of capability, agree the support and review the arrangement. Treat the choice as a hypothesis you can revise, not a formula that guarantees the right leadership style.
Understand the model’s evidence boundary
Popular situational leadership models organise managerial behaviour around different combinations of guidance and support. Their central intuition is attractive: one style is unlikely to suit every situation.
That does not mean every prescription in the models has strong empirical support. Graeff’s critical review raised conceptual problems. Thompson and Vecchio’s test of three versions did not provide clear support for the tested prescriptions.
Use the idea to ask a better question about a task. Do not claim that a four-box classification accurately predicts what every employee needs.
The worksheet below is an original work-planning aid. It is not a validated psychological instrument, a licensed training assessment or a reproduction of a proprietary development-level test.
Assess the task before assessing readiness
Write the outcome, the required standard and the decisions involved. “Handle the launch” can contain several different tasks: coordinate dependencies, approve copy, check data and respond to an incident.
A person may be capable of one and unfamiliar with another. Discuss the parts separately. Which decisions can they already make? Which need specialist authority? Which information or practice is missing?
Ask for evidence appropriate to the task: previous work, a draft, a demonstration or an explanation of the method. A broad reputation for competence is useful context but does not establish every skill.
Also examine resources. A person who cannot complete a task because access is missing does not need more direction on how to work. They need the access or a revised scope. Delegation and accountability helps make that distinction explicit.
Separate unfamiliarity from unwillingness
A colleague who hesitates may need an example, a clearer decision boundary or time to practise. They may also disagree with the task’s value or be overloaded. These explanations require different responses.
Ask what makes the next action difficult. Invite an example rather than interpreting the person’s manner. A quiet response does not demonstrate low commitment; a confident answer does not establish competence.
If the person objects to the task, discuss the reason. Explain what is fixed and where their judgement can influence the method. A legitimate quality concern should not be coded as poor readiness.
When the issue concerns effort or a repeated breach of an agreed expectation, address the observable behaviour through the appropriate management process. Avoid turning a support conversation into an informal diagnosis of motivation.
Choose guidance that answers a real uncertainty
Guidance can include a worked example, an explanation of the acceptance criteria or a step-by-step demonstration of an unfamiliar process. The value is the uncertainty it resolves.
Make the instruction specific enough to use. “Be more strategic” does not help someone decide which evidence to include in a proposal. “Compare these options against the agreed customer outcome and operating constraint” points to an action.
Avoid giving instructions that merely reproduce your personal preferences. If several methods can meet the criteria safely, explain the constraint and let the person choose.
When a task requires expert approval, name that requirement. A manager’s confidence cannot replace technical competence or formal authority. Support should help the colleague reach the correct reviewer, not bypass the review.
Offer support without quietly taking back ownership
Support may mean discussing options, reviewing a draft or removing a dependency. It does not necessarily mean deciding everything yourself.
Before a review, agree what feedback is needed. The person might want a check of the reasoning rather than a complete rewrite. Explain what meets the standard, what remains uncertain and which change is necessary.
If you repeatedly take over, ask what the arrangement teaches. The colleague may learn that asking for help transfers the task back to you. Keeping ownership visible lets a question remain a question.
The difficult feedback guide helps separate an observation, its impact and a next agreement. Use that discipline in supportive reviews as well as corrective conversations.
A hypothetical analyst taking on a new responsibility
Imagine an analyst who usually prepares commercial reports and is now asked to lead a data-quality review. This is a hypothetical example. They understand the data but have not coordinated approval across functions.
The manager initially proposes frequent checks of the analysis. A task discussion reveals that the real uncertainty concerns who can approve definitions and when an unresolved discrepancy should pause the review.
They keep the analytical work with the analyst and provide a worked example of the approval record. The relevant data owner explains the escalation criteria. A first draft review focuses on the cross-functional decision rather than rechecking every calculation.
At the agreed point, they examine whether the analyst can identify unresolved issues and route them appropriately. If so, the support can become less frequent. If a new type of data introduces uncertainty, a targeted review remains available.
The example describes a possible adjustment, not a claimed success. It shows why task-specific support may be more useful than deciding that the person has entered a different permanent development category.
Use a task-support worksheet
Complete this together before an unfamiliar or important task.
Swipe or use the arrow keys to see every column.
| Field | What to establish | How to make it usable |
|---|---|---|
| Task | Outcome and acceptance criteria | Describe the work, not a general role label |
| Existing capability | What the person can already demonstrate | Use relevant evidence or a draft |
| Unfamiliar part | What they have not done before | Identify the decision or step precisely |
| Authority | What they can decide and what requires approval | Name the boundary and reviewer |
| Guidance | Which uncertainty needs an explanation | Provide an example or explicit criterion |
| Support | What help stays available | Agree a review or access to a specialist |
| Review trigger | When the arrangement should change | A completed task stage or new risk |
Add available time and competing commitments. The worksheet should expose missing conditions. It should not make the employee responsible for solving a capacity conflict that only the manager can authorise.
Agree how support will become lighter
Support can become habitual even when the task no longer requires it. Set a review point from the beginning and define what would justify reducing the checks.
Use evidence connected to the work. Can the person apply the criteria, recognise an exception and explain their decision? Have the important dependencies been resolved? Does the remaining risk require review by someone else?
Reducing support should not remove access to help. Clarify what can proceed independently and which new conditions should bring the task back for discussion.
Do not treat a request for help after a period of independence as regression. The task may have changed. The leadership guide explains how to keep responsibility stable while adjusting the operating arrangement.
Recognise the cases where a style change is insufficient
If objectives conflict, nobody has decision authority or the workload is unreasonable, changing your conversational style will leave the main problem intact.
A person may also need structured training, supervised practice or specialist support beyond what you can provide. A leadership model does not make you qualified to assess every capability.
For serious interpersonal issues, use the relevant organisational route. Do not reinterpret harmful behaviour as a mismatch between your preferred style and someone’s development level.
The organisational psychology guide examines person, task and system together. Its wider frame helps prevent the manager from locating every difficulty inside the employee.
Keep support clear during a manager handover
If the manager or specialist changes, share the current task agreement before the next review. Describe the criteria, the support still needed and the decisions already transferred. Do not pass on a vague label about the employee’s readiness.
Invite the person doing the work to explain the agreement too. A new reviewer may prefer a different method without having identified a new risk. Discuss that preference against the existing criteria before adding checks. The purpose of the handover is to preserve useful context while allowing a reasoned change, rather than restarting supervision because the manager is unfamiliar with the task.
Review the result without confusing it with proof of the model
A completed task can support a practical decision about the next assignment. It does not establish that the whole situational leadership model is correct.
Compare what you expected with what happened. Which uncertainty was resolved? Which support was used? What work needed revision? Which external condition changed?
Include the colleague’s account. A task may look smooth because they privately absorbed an unreasonable amount of effort. Your review needs enough context to distinguish growing capability from hidden extra work.
This is similar to the distinction between an observation and its explanation in consumer psychology. An outcome can be real while your account of its cause remains uncertain.
Choose one task this week. Replace a general judgement about readiness with a concrete agreement about capability, guidance and review. Keep the agreement open to new evidence.
If a digital project is caught between overchecking and unsupported delegation, tell me which task needs a clearer support boundary. We can define the outcome, authority and review the work actually requires.
Apply this to your project
Tell me the decision you are facing, the constraints and what you have already tried.
Keep exploring
Delegation and accountability: clarify who decides
Delegate with a clear outcome, decision authority and review points, so accountability helps the work instead of creating another approval queue.
Decision-making under uncertainty: expose assumptions
Make a work decision with incomplete evidence. Separate facts from assumptions, compare options and define a review trigger with a practical record.
Difficult feedback: prepare a useful conversation
Prepare difficult feedback with observable behaviour, fair questions and a clear next agreement. Use a practical worksheet without labelling the person.