One of the most powerful traits in effective leaders isn’t just decisiveness or vision—it’s the ability to adapt. In my own leadership journey, I’ve realized that different situations, teams, and even individuals need different things from a leader. You don’t become a better leader by always taking charge. Sometimes, you do it by stepping back.
- Tanya Rehman

The Tannenbaum and Schmidt Leadership Continuum models leadership not as a fixed trait, but as a sliding scale of authority and freedom. It illustrates seven leadership styles ranging from manager-centered to team-centered.

This model is especially helpful for engineers and tech leads transitioning into Staff-plus roles, where leadership is increasingly about influence and adaptability, not command-and-control.

The full continuum

Below is a breakdown of the seven styles from the Tannenbaum-Schmidt model:

This continuum shows that leadership is not binary instead, it's a matter of how much control you retain versus how much freedom you grant.

Why leadership flexibility matters

Rigid leadership (always using one style) can stifle innovation or create friction. Conversely, flexing your approach based on urgency, team experience, and risk level leads to better outcomes and healthier team dynamics.

For example:

• Use Tells during incidents or high-risk decisions.

• Use Joins or Delegates during long-term planning or innovation projects.

• Use Consults or Suggests when trust is being built or expertise is uneven.

In Staff-plus roles, your ability to pick the right style at the right time is as critical as technical execution.

Internal leadership visibility

Being a flexible leader only matters if people can see and understand it. To create internal visibility:

• Explain your decision-making style choices in project kickoffs or retros.

• Share leadership shifts in internal documentation or postmortems.

• Use team rituals (like demos or syncs) to showcase inclusive decision-making.

• Show how you’ve helped team members grow into decision-makers by gradually shifting toward Delegates or Abdicates.

Documenting how and when you apply the continuum demonstrates self-awareness and emotional intelligence key traits for Staff-plus leaders.

Executive visibility

Executives value scalable leadership. That means:

• Empowering others to make good decisions.

• Creating clarity without micromanaging.

• Knowing when not to lead directly.

Use your promotion packet to showcase times you've moved along the continuum—especially toward Joins, Delegates, and Abdicates to develop leadership in others.

You can also:

• Include reasoning behind your style in planning docs.

• Share how shifting leadership led to improved outcomes.

• Reflect on leadership balance during strategy reviews with your manager's manager.

External visibility

You can strengthen your external credibility by teaching this framework through:

• Blog posts analyzing how you led differently across projects.

• Conference talks about leading distributed or high-autonomy teams.

• Podcasts on decision-making and psychological safety.

• Case studies or internal playbooks demonstrating leadership transitions.

Sharing how you've moved across the continuum not only elevates your voice it helps others grow into thoughtful leaders.

Should you focus on leadership style flexibility?

If you're always leading from the same position on the continuum, you're missing opportunities to empower your team and grow yourself.

Ask yourself:

• Have I ever fully delegated or abdicated a decision?

• Do I involve the team more now than I did a year ago?

• Am I stuck in "Tells" mode because it feels safer?

Flexing along the continuum builds trust, resilience, and scale exactly what organizations look for in Staff-plus engineers.

🧠 "Leadership is about reading the room and then choosing the tone."
The Tannenbaum-Schmidt Continuum gives you the vocabulary and structure to do that intentionally.

Let’s break it down.

What Is Delegation?

Delegation is the process of assigning responsibility and authority to someone else to complete a task, while the leader retains ultimate accountability.

It’s not just about doing less—it’s about doing the right things, and helping others grow in the process.

When Should You Delegate?

Great leaders don’t wait until they’re overwhelmed to delegate. Here are ideal moments to consider it:

1. When a task is repeatable or operational

Routine tasks that don’t require your direct input are great candidates for delegation.

2. When someone else has (or can build) the skill

If someone on your team is equipped—or eager—to learn, give them the opportunity.

3. When it’s a growth opportunity

Delegation can stretch team members and expose them to decision-making, cross-functional work, or new technologies.

4. When it frees you to focus on strategic work

Leadership requires space for vision, culture, and innovation. Delegate to gain that space.

🚫 When Not to Delegate

• Critical tasks that require your unique expertise or judgment

• Tasks involving sensitive personal issues (e.g., performance reviews)

• Work for which the delegatee lacks capacity or readiness, without time to support them

How to Delegate Effectively

1. Choose the Right Person

Match the task to the team member’s skills, interest, and development level (think Situational Leadership).

2. Clearly Define the Outcome

Explain:

• What success looks like

• Deadlines

• Key deliverables

Avoid vague expectations clarity upfront saves time later.

3. Give Context, Not Just Tasks

Let them know why the task matters. This builds ownership and aligns their approach with the bigger picture.

4. Set Checkpoints, Not Micromanagement

Schedule light touch-ins for alignment and support, especially early on. Too much oversight kills initiative; too little may lead to missed goals.

5. Support Without Taking Over

Be available to guide, but resist the urge to "just fix it" yourself. Let them learn, even if it means a small delay.

6. Recognize and Reflect

Acknowledge the work publicly, offer feedback, and discuss what went well or could improve next time.

🧠 Framework: The 5 Levels of Delegation

Adapted from leadership expert Michael Hyatt, these levels help you communicate the degree of autonomy:

1. Do exactly what I say.

2. Research and report back.

3. Research, recommend, and let me decide.

4. Make a decision, but inform me.

5. Own the decision—no need to report unless there's a problem.

This helps align expectations and builds trust progressively.

Example in Engineering Leadership

Scenario:

You’re a tech lead, and a new platform initiative is starting. You’re already at capacity.

Instead of owning the entire spec yourself:

• Delegate research and architecture drafting to a senior engineer (Level 3)

• Review their proposal, refine it together

• Gradually delegate execution and decision-making (Levels 4–5)

Result: You focus on team alignment and stakeholder communication while your engineer grows as a technical leader.

Common Pitfalls to Avoid

• “It’s faster if I do it myself” mindset
  Short-term yes, but long-term you stunt team growth.

• Delegating without context
  People need to understand why the task matters to truly own it.

• Overchecking or underchecking
  Too much = micromanagement; too little = abandonment.

Summary: Best Practices

Understanding and mastering this distinction is not just semantic it’s strategic.

Definitions

Responsibility

Responsibility is about task ownership. It refers to the obligations, duties, or roles someone is assigned or accepts. A responsible person is expected to follow through and execute.

• You can delegate responsibilities.

• They can be shared among multiple people.

• They are typically execution-focused.

Example: A backend engineer is responsible for implementing an API endpoint by the end of the sprint.

Accountability

Accountability is about outcome ownership. It means being answerable for results, regardless of who does the work.

• Accountability is singular only one person is ultimately accountable.

• It cannot be delegated, though it can (and should) empower others.

• It’s focused on results, not activity.

Example: The engineering manager is accountable for delivering a functional, performant product feature even though the work is distributed among several engineers.

The Crucial Difference

Understanding the difference becomes particularly important as you transition to Staff-plus or leadership roles.

From Doer to Enabler: Navigating the Shift

As a senior engineer or technical leader, the shift from being responsible for execution to accountable for direction and outcomes is critical but also uncomfortable.

It’s easy to default to doing the work yourself. After all, that’s what got you here. But long-term success means your team succeeds without your constant involvement. The goal is to build capability, not dependency.

"At this point, I spend less time advocating for specific technologies or programs and more time empowering others to advocate for the technologies and programs that they think are important."
— Michelle Bu

Applying Responsibility and Accountability in Practice

Discussions: Shift from Voice to Facilitator

When you're optimizing for impact, it's tempting to dominate conversations with answers and opinions. But when you're focused on accountability, you realize that the real power lies in creating space for others to lead.

Techniques to try:

• Ask questions instead of giving answers. Guide the team to uncover solutions on their own.

• Pull others into the conversation. Especially those who are quiet but have context or potential.

• Take notes. Model humility and free others to contribute more vocally.

• Notice absences. If someone with key context is missing, ensure they’re included next time.

A good discussion is one where you didn’t need to speak not because you were disengaged, but because you made others feel safe and empowered to contribute meaningfully.

Decisions: Move from Direction to Delegation

Being accountable doesn’t mean you must make every decision. It means you’re responsible for building decision-makers.

Techniques to empower others:

• Write down your decision-making rationale. Help others learn your thinking, not just your outcomes.

• Circulate early. Invite feedback before your ideas harden—model openness.

• Avoid style feedback. Focus on substance, and trust others' stylistic choices.

• Let go of ego. Don't offer input just to “show value.” Prioritize impact over impression.

• Change your mind. Demonstrating adaptability models respect and maturity.

"Initially, I was thinking, ‘I’ll break it into twenty pieces, assign out eighteen, and keep the two hardest for myself.’ And my manager pushed me to delegate the hard pieces to stretch the team."
— Ritu Vincent

Sponsorship: Giving Away the Work

Sponsorship is the ultimate act of accountability without responsibility. It’s choosing to grow others by giving them the opportunity to lead the kind of projects that once made your career.

How to sponsor effectively:

1. Identify growth opportunities. When work comes to you, ask, “Who could grow by doing this?”

2. Scaffold early. Share your thought process, stakeholders, risks, and context.

3. Support, don’t steer. Let them lead. Advise without controlling.

4. Celebrate their wins. Let them receive the credit, even if you seeded the idea.

It may be uncomfortable to hand over critical work but if your organization depends on you, it’s fragile. If it thrives without you, that’s the legacy of a truly accountable leader.

What Happens If You Don’t?

You might become the bottleneck.

If your value is rooted solely in doing and deciding, the organization will stagnate when you step back. The short-term wins of being the “go-to” person eventually become long-term liabilities.

"The only way to remain a long-term leader of a genuinely successful company is to continually create space for others to take the recognition, reward, and work that got you to where you’re currently sitting."

Final Thoughts

Both responsibility and accountability are crucial, but they’re not interchangeable. Responsibility is about doing the work. Accountability is about growing others to do it and enabling them to succeed without you.

Your highest leverage as a Staff-plus engineer or leader isn’t in the code you write, but in the leaders you develop, the trust you earn, and the space you create.

Make the shift. Create the space. Share the ownership.

“The best sign of leadership is that the organization grows because of you, not around you.”