Leadership Styles & Situational Leadership

The Core Styles — A Working Taxonomy

Most leadership style frameworks converge on a handful of archetypes. The names vary across authors (Goleman, Burns, Greenleaf, Hersey-Blanchard), but the underlying behaviors cluster reliably.

Style	Core Behavior	Best When	Failure Mode
Directive / Commanding	Clear instructions, tight control, explicit expectations	Crisis, new hires, safety-critical, compliance-heavy	Learned helplessness, talent flight, bottleneck on leader
Coaching	Develop the person through questions, stretch assignments, feedback loops	Mid-maturity ICs, high-potentials, skill-building phases	Slow when speed matters, frustrating for experts
Democratic / Participative	Seek input broadly, build consensus, shared ownership	Experienced teams, complex problems needing diverse perspectives	Decision paralysis, slowness, “design by committee”
Visionary / Transformational	Paint a compelling future, inspire, connect work to meaning	New direction, organizational change, motivating through ambiguity	Empty if not backed by execution, can become personality cult
Servant	Remove blockers, serve the team, prioritize team needs over personal glory	Mature teams, knowledge work, high-trust environments	Gets exploited, leader burns out, lacks direction if taken too far
Affiliative	Harmony-first, emotional bonds, conflict avoidance	Team healing after crisis, morale repair, onboarding	Poor performance tolerated, avoids hard conversations
Pacesetting	Lead by example, set high bar, expect self-direction	Expert teams, short sprints, technical proof-of-concepts	Burns out team, no development, micromanagement by implication
Laissez-faire	Hands-off, full autonomy, minimal oversight	Senior/staff+ engineers, research, creative work	Neglect disguised as trust, no accountability, drift

What Most Frameworks Get Wrong

The typical mistake is treating these as personality types (“I’m a servant leader”). They are not identities — they are tools. The question is never “what kind of leader am I?” but “what does this person/team/situation need from me right now?”

Goleman’s research (Harvard Business Review, 2000) showed that the most effective leaders deploy four or more styles depending on context. Leaders who rely on only one or two styles — regardless of which ones — consistently underperform.

---

Hersey-Blanchard Situational Leadership Model

The most practically useful model for day-to-day engineering management. It maps leadership style to follower readiness (a combination of competence and commitment).

The Four Quadrants

Readiness Level	Competence	Commitment	Recommended Style	Leader Behavior
R1 — Unable, Insecure	Low	Low	S1: Telling (Directing)	High task, low relationship. Give specific instructions. Check frequently.
R2 — Unable, Willing	Low	High	S2: Selling (Coaching)	High task, high relationship. Explain decisions, provide guidance, encourage.
R3 — Able, Insecure	High	Low/Variable	S3: Participating (Supporting)	Low task, high relationship. Share decision-making, listen, facilitate.
R4 — Able, Confident	High	High	S4: Delegating	Low task, low relationship. Hand off responsibility. Monitor outcomes, not process.

Reading Readiness — Practical Signals

This is where most managers fail. They assess readiness once and never update, or they assess the person globally instead of per-task.

Key principle: Readiness is task-specific, not person-specific. A Staff Engineer (R4 for system design) might be R1 for people management when they first take on a tech lead role. A senior backend engineer (R4 for Java services) might be R2 for a new Kotlin migration.

Signals of each readiness level in engineering teams:

Signal	R1	R2	R3	R4
Asks questions	Doesn’t know what to ask	Asks many questions, eager	Asks for validation, not information	Rarely asks — brings solutions
Handles ambiguity	Freezes or thrashes	Gets overwhelmed but tries	Can navigate but second-guesses	Comfortable, makes judgment calls
Owns outcomes	Needs handholding	Takes ownership of tasks, not outcomes	Owns outcomes but hesitates on decisions	Full ownership, escalates strategically
Response to feedback	Needs specific, immediate correction	Welcomes feedback, applies it	Sensitive to feedback, may withdraw	Seeks feedback proactively, debates constructively

Transitions and Common Traps

The R2-to-R3 dip: This is the most dangerous transition and the one most managers mishandle. An engineer who was enthusiastic (R2) gains enough competence to see how hard the problem really is, and their confidence drops. They become R3 — able but insecure. If you respond by reverting to S1 (directing), you signal distrust and make the dip worse. The correct move is S3 (supporting) — share the decision, validate their competence, let them struggle productively.

The premature S4 trap: Promoting someone to a new role and immediately delegating fully because “they earned it.” They may be R4 in their old role but R1 or R2 in the new one. A new engineering manager who was a great IC still needs S2 (coaching) for people management.

The stuck-on-S1 anti-pattern: Some managers default to directing because it feels productive and safe. The team never develops. When the manager goes on vacation, everything breaks.

---

Transformational vs. Transactional Leadership

Burns (1978) and Bass (1985) drew the foundational distinction.

Transformational Leadership

Operates on intrinsic motivation. The leader raises the team’s aspirations and connects daily work to something larger.

The Four I’s (Bass):

1. Idealized Influence — The leader models the behavior they expect. They take risks alongside the team, not from a safe distance. Walk the talk, but literally — join on-call rotations, review code, sit in customer support shadowing.
2. Inspirational Motivation — Articulate a compelling vision of the future state. Not corporate platitudes — concrete, vivid descriptions of what success looks like and why it matters.
3. Intellectual Stimulation — Challenge assumptions, encourage experimentation, make it safe to propose radical alternatives. Ask “what if we did the opposite?” or “what would we build if we started from scratch?”
4. Individualized Consideration — Treat each person as a unique individual with distinct motivations, growth edges, and constraints. The same stretch assignment that energizes one person overwhelms another.

When transformational leadership fails:

• When the vision is disconnected from reality (no execution path)
• When the leader confuses inspiration with performance management (you still need to set expectations and hold people accountable)
• When it becomes personality-dependent — the team cannot function without the charismatic leader

Transactional Leadership

Operates on extrinsic exchanges: clear expectations, defined rewards, consequences for non-performance. Often dismissed as “old school” but essential in certain contexts.

When transactional is the right call:

• Compliance and regulatory environments (SOX, GDPR, PCI-DSS)
• Establishing baseline expectations with a team that has drifted
• Crisis stabilization before transformational change
• Clear metrics-driven execution (SLO targets, sprint commitments)

The integration: The best engineering leaders are primarily transformational with a transactional floor. You inspire and develop, but you also set non-negotiable standards and enforce them. You cannot coach someone out of consistently missing deadlines without accountability.

---

Servant Leadership — Beyond the Buzzword

Robert Greenleaf (1970) coined the term, but it has been diluted into “be nice to your team.” The actual model is more demanding than directive leadership, not less.

What Servant Leadership Actually Means

The servant leader’s primary question: “What do my people need to succeed, and how do I provide it?”

This includes:

• Removing organizational friction — Shielding the team from unnecessary meetings, process overhead, political nonsense
• Building capability — Not just delivering results today but ensuring the team can deliver harder results tomorrow
• Speaking truth to power — Advocating for the team upward, even when it is uncomfortable
• Holding high standards — Serving the team does not mean accepting mediocrity. A servant leader who avoids hard feedback is failing their people.

The Servant Leadership Paradox in Engineering

Servant leadership works exceptionally well with mature, skilled teams (R3-R4). It fails badly when:

• The team lacks clear direction and needs a decisive leader (R1 situations)
• Performance issues require direct confrontation
• The organization rewards visible heroics over quiet enablement (the servant leader gets overlooked for promotion)
• The leader uses “servant leadership” as an excuse to avoid making hard calls

L. David Marquet’s “Turn the Ship Around” (2012) offers the best engineering-applicable version: push authority to where the information lives, but build competence and clarity simultaneously. His formula: Control + Competence + Clarity = Leadership. Increase control (autonomy) only as fast as you increase competence and clarity. Otherwise you get chaos.

---

Applying Styles in Engineering Contexts

Scenario: New Team, Inherited Codebase

You join as EM for a team of 8 with a legacy monolith, no tests, and high attrition. Team morale is low. Trust is near zero.

Phase 1 (Weeks 1-4): Affiliative + Directive Listen. Build emotional bonds. Understand the pain. Simultaneously, establish basic operational hygiene — standups, on-call rotation, incident response. Do not try to transform anything yet.

Phase 2 (Months 2-3): Coaching + Democratic Start 1:1s focused on individual growth. Involve the team in deciding the first technical improvements. Let them choose the first refactoring target. This builds ownership.

Phase 3 (Months 4-6): Visionary + Servant Now paint the picture: “Here is where we are going. Here are the first three steps. I will remove the blockers — you drive the execution.” Shift to servant mode as trust and competence grow.

Scenario: High-Performing Senior Team

You lead 4 Staff Engineers building an AI platform. They are all R4 for their domains.

Default: Laissez-faire + Servant. Set direction, remove blockers, stay out of the way. Your job is alignment (are they working on the right things?) and air cover (are they protected from organizational noise?).

Exception: Switch to Directive when a production incident requires coordinated response, or when a strategic decision needs to be made and the team is stuck in analysis paralysis. “I’ve heard all perspectives. Here is what we are doing. Move.”

Scenario: Performance Problem on an Otherwise Strong Team

One engineer is consistently underperforming. The rest of the team knows it and is watching how you handle it.

Do not default to affiliative (avoiding the issue) or democratic (asking the team how to handle it — that is your job). Use coaching first (S2): set clear expectations, provide specific feedback, offer support. If that fails, shift to directive (S1): explicit improvement plan with milestones and consequences. This is uncomfortable but necessary. The team’s trust in you depends on it.

---

Anti-Patterns

Anti-Pattern	What It Looks Like	Why It Happens	The Fix
Style rigidity	Using one style regardless of context	Comfort zone, lack of awareness	Practice the style you are weakest at. Ask for feedback on adaptability.
Style mismatch	Delegating to R1, directing R4	Poor readiness assessment	Assess readiness per task, not per person. Reassess frequently.
Whiplash	Switching styles unpredictably within the same situation	Stress, lack of self-awareness	Be explicit about why you are shifting: “This situation calls for a faster decision, so I’m going to be more directive here.”
Abdication as delegation	“I trust you, figure it out” to someone who needs guidance	Confusing trust with support	Delegation has levels (see Delegation & Empowerment). Match the level to readiness.
Consensus addiction	Every decision goes through the team	Conflict avoidance, fear of being wrong	Classify decisions by reversibility and stakes. Not everything needs consensus.
Performance avoidance	Using affiliative/servant style to avoid hard conversations	People-pleasing, fear of conflict	Reframe: avoiding the conversation is not kind — it lets the person fail slowly.

---

Key Takeaways for Senior Engineering Leaders

1. Style fluency > style preference. Develop range. The best leaders move between 4-6 styles fluidly within a single week.
2. Assess readiness per task, not per person. A Staff Engineer can be R1 for a new domain. A junior can be R4 for their specialty.
3. The default for mature engineering teams is servant + coaching. But always be ready to shift to directive when the situation demands it.
4. Transformational leadership without transactional foundations is just motivation without accountability. You need both.
5. Name your style shifts explicitly. Teams handle style changes well when you explain why. They handle unpredictable changes poorly.

---

References

• Burns, J.M. (1978). Leadership. Harper & Row. — Foundational work on transformational vs. transactional leadership.
• Bass, B.M. (1985). Leadership and Performance Beyond Expectations. Free Press. — Extended Burns’ work with the Four I’s model.
• Goleman, D. (2000). “Leadership That Gets Results.” Harvard Business Review. — Six leadership styles and the research showing effective leaders use 4+.
• Hersey, P. & Blanchard, K.H. (1969). Management of Organizational Behavior. Prentice-Hall. — Situational leadership model (readiness levels + styles).
• Greenleaf, R.K. (1970). The Servant as Leader. Robert K. Greenleaf Center. — Original servant leadership essay.
• Marquet, L.D. (2012). Turn the Ship Around! Portfolio. — Intent-based leadership; pushing authority to information. Best practical application of servant leadership.
• Grove, A.S. (1983). High Output Management. Random House. — Task-relevant maturity concept, directly maps to Hersey-Blanchard.
• Camille Fournier (2017). The Manager’s Path. O’Reilly. — Engineering-specific leadership progression from tech lead to CTO.
• Kim Scott (2017). Radical Candor. St. Martin’s Press. — Care personally + challenge directly as a leadership style integration.
• Will Larson (2019). An Elegant Puzzle. Stripe Press. — Systems thinking applied to engineering management.