Paul Hersey and Ken Blanchard developed Situational Leadership in the late 1960s. The model proposes that effective leadership depends on the readiness of the follower relative to a specific task. Readiness is defined by two dimensions: competence and commitment. Competence covers the knowledge and skills an engineer brings to a task. Commitment covers the motivation and confidence to complete it. By combining these two dimensions, the model identifies four development levels: D1 (low competence, high commitment), D2 (some competence, low commitment), D3 (high competence, variable commitment), and D4 (high competence, high commitment). Leaders respond with four corresponding styles that vary the amount of directive behavior (telling what and how) and supportive behavior (listening and encouraging): Directing (S1), Coaching (S2), Supporting (S3), and Delegating (S4).

The model is not a one time classification. You reassess development levels for each new task or project, and you shift your style as the engineer gains competence or as commitment fluctuates. The goal is to move engineers toward D4 independence over time.

Assessing Development Level on Real Work

You cannot rely on job title or years of experience to determine a development level. Instead, observe behavior on specific tasks. To assess competence, ask: Does the engineer finish this type of work without repeated guidance? Do they produce code that meets standards without extensive code review comments? Have they done this type of work before? To assess commitment, ask: Do they volunteer for similar tasks? Do they bring ideas or concerns? Do they seem engaged during planning or execution?

Use each one on one meeting to discuss a recent task and gauge both dimensions. You can also ask the engineer to self assess: “How confident do you feel owning this feature? What would help you execute it without my oversight?” The most accurate assessment combines your observation with their own perception of their readiness.

Matching Your Style to the Engineer’s Needs

Once you have identified the development level for a specific task, choose the style that provides the appropriate balance of direction and support.

Directing (S1) – High Directive, Low Supportive

Apply this style when the engineer is at D1: new to the task, eager, but lacking competence. Your job is to define the work clearly, break it into small steps, specify how success looks, and review progress often. For example, a junior engineer writing their first microservice needs instructions on which patterns to follow, how to set up the environment, and what quality standards to meet. They also need you to explain the business context so they see the purpose, but the primary mode is teach and verify. The risk is not in over directing but in assuming they will “figure it out”. Avoid skipping the basics.

Coaching (S2) – High Directive, High Supportive

At D2, the engineer has some competence but their commitment wavers. They may have done similar work before but lost confidence after a failure, or they are competent but bored. Use directive behavior to guide the approach, but add supportive behavior: explain the reasoning, ask for input, provide encouragement, and pair on tricky parts. For instance, an engineer who struggled with a performance issue may need you to pair debug once, then let them drive the next step. Give them space to make decisions but be ready to correct course early. Your aim is to build confidence and provisional competence.

Supporting (S3) – Low Directive, High Supportive

At D3, the engineer possesses high competence but low or variable commitment. They might be burned out, frustrated with the product direction, or simply unchallenged. Your style must shift to low directive: avoid telling them how to do the work. Instead, use supportive behavior: listen actively, facilitate decisions, remove obstacles, and co create solutions. For example, a senior engineer who is capable of designing an architecture but lacks enthusiasm for the current direction needs to feel heard. Ask open ended questions, bring them into design discussions, and give them influence over the approach. Your role is to reignite motivation by providing autonomy and a sense of purpose.

Delegating (S4) – Low Directive, Low Supportive

At D4, the engineer is both competent and committed on the task. They can plan, execute, and self correct. Your job is to set clear outcomes and boundaries, then get out of the way. Provide resources when asked, shield them from external noise, and check in only at agreed milestones. For instance, a staff level engineer leading a major initiative should not need to report step wise progress. Trust them to handle the how. If you start giving instructions or frequent status checks, you risk demotivating them. The phrase “I trust you to handle it” is powerful and sufficient.

Practical Guidelines for Day to Day Application

Use the Model Per Task, Not Per Person

The same engineer will land at different development levels depending on the type of work. A senior backend developer might be D4 on API design but D2 on frontend work or project management. You must calibrate your style for each assignment. Avoid the mental shortcut of labeling someone “junior” or “senior” and applying a fixed style. Re assess regularly and especially when the context changes, such as a new technology stack, a new team member, or after a major incident.

Explain Your Style Changes

Engineers notice when you change how you manage them. If you have been hands on and then pull away without explanation, they may wonder if you are upset or if they have done something wrong. Similarly, if you start being more directive after granting autonomy, they may feel disempowered. Communicate your reasoning: “I’m stepping back because I think you can own this feature. I’m still here if you need help, but I trust your judgment.” Or “I need to be more involved in this phase because the compliance requirements are high. Let’s work through this together.” This transparency builds trust and helps the engineer understand the intent behind your behavior.

Watch for Feedback Loops

Situational Leadership is not a prescription to impose a style and forget it. You must continuously observe the results of your actions. If an engineer under S3 (supporting) continues to flounder in execution, you may need to increase direction temporarily. Conversely, if an engineer under S1 (directing) starts showing initiative and understanding, you can reduce direction and add support. The model suggests a developmental sequence from S1 to S4, but you may need to loop back. Treat it as a dynamic adjustment rather than a linear progression.

Avoid Common Mismatches

The most frequent mismatches are:

  • Using S1 (directing) on an engineer who is actually D3 or D4. This causes frustration and kills motivation.
  • Using S4 (delegating) on an engineer at D1. They feel abandoned and anxious.
  • Staying in S2 (coaching) too long even after competence rises, which stalls the move to autonomy.
  • Using S3 (supporting) when the engineer needs direction, leading to confusion and missed targets.

To avoid these, err on the side of providing slightly more direction than needed if you are uncertain, but check explicitly: “Would you like more guidance or more freedom on this task?” Their answer will often reveal the right style.

Situational Leadership in Common Engineering Scenarios

Here are three typical situations where the model helps you choose a style quickly.

Onboarding a new engineer. A new hire with industry experience may still be D1 on your stack and process. Applying S1 for the first setup guides them through the mechanics. As they complete initial tickets, you move to S2 to build independent troubleshooting skills. After a few months, reassess and decide if they are ready for S3 or S4 on routine tasks.

Dealing with a post incident reaction. After a production incident, the engineer involved may drop from D4 to D2 in confidence. They possess the competence but their commitment wavers from fear or embarrassment. Use S2 coaching to rebuild confidence: pair on the fix, discuss what they did well, and gradually restore autonomy. Avoid S4 delegation which may feel like a test, and avoid S1 direction which may feel like punishment.

Managing a bored senior engineer. A staff engineer who has been stable for years can become D3: high competence, low commitment due to lack of challenge. Apply S3 supporting: involve them in strategic decisions, give them space to propose new initiatives, and listen to their frustrations. If that fails to raise commitment, you may need to revisit their role or project assignments.

In each scenario, the model gives you a structured way to choose your behavior rather than reacting emotionally or uniformly. Over time, the framework becomes intuitive and you will naturally adjust your style moment to moment.

The real value of Situational Leadership for engineering managers is not in the labels but in the deliberate practice of adapting to each engineer’s current needs. It frees you from the trap of “my management style” and lets you become the leader your team actually requires.


Leave a Reply

Your email address will not be published. Required fields are marked *