Your Best Engineer Might Be Your Worst Manager: The 2025 Surton Leadership Transition Playbook

At Surton, we’ve guided more than 50 engineers through the transition to management—and we’ve seen nearly as many fail. The pattern is consistent: companies promote their top technical performer, assume management skill will emerge, and watch both the individual and team struggle. The tragedy is that this is entirely preventable with the right selection, training, and support.

This guide is our complete leadership transition playbook. It includes the assessment frameworks we use to identify management potential, 90-day training curricula tailored to different engineer profiles, and real case studies of successful and failed transitions.

Quick Take

Your best engineer (by technical output) is often your worst management candidate—they’re optimized for individual contribution, not team enablement. The transition succeeds when you: (1) Select based on coaching potential, not just coding skill, (2) Train management as a distinct discipline with concrete frameworks, (3) Match development to their natural wiring—technical obsessives need systems thinking, empathetic engineers need decisiveness training, and (4) Provide a dual-track ladder so management isn’t the only path to advancement. Plan 12-24 months for full management competence—treat it like becoming a senior engineer, not a weekend workshop.

The Real Cost of Failed Management Transitions

When engineer-to-manager transitions fail, costs cascade:

Cost Category	First 6 Months	Year 1	Year 2+
Manager struggling	20% productivity loss	40% loss, possible demotion	Replacement hiring
Team suffering	Velocity decline, morale drop	Attrition (1-2 engineers)	Team rebuild
Lost IC contribution	No technical output	Still minimal	Possibly permanent
Organizational debt	None yet	Pattern of failed managers	Culture of fear around management
Total cost	$50k-100k	$200k-400k	$500k-1M+

Surton Data: 2024 Management Transition Study

We tracked 50 engineer-to-manager transitions across our client companies:

Outcome	% of Transitions	Root Cause
Thrived	35%	Right selection + structured training
Survived	30%	Adequate support, took 12-18 months to competence
Struggled	25%	Poor selection or insufficient training
Failed/Rolled back	10%	Wrong person for role, no IC alternative

Key finding: 65% of transitions could be improved or saved with better selection and training processes. The 10% failure rate is largely due to promoting the wrong person—often the top technical performer who never wanted to manage people.

The Selection Problem: How to Identify Real Management Potential

Why Technical Excellence Misleads

The engineer who ships the most code, solves the hardest problems, or knows the system best is often the worst management candidate. Here’s why:

Technical Top Performer	Ideal Manager Candidate
Optimized for speed and depth	Optimized for clarity and breadth
Outshines others technically	Amplifies others’ output
Solves problems directly	Coaches others to solve
Drawn to technical challenges	Drawn to people and system challenges
Wants to be right	Wants team to succeed
Measures own output	Measures team’s growth

The Surton “3rd-5th Place” Observation:

In our data, the most successful new managers often ranked 3rd-5th on pure technical metrics within their cohort, but excelled at:

• Communicating complex ideas simply
• Handling ambiguity with judgment
• Mentoring junior engineers voluntarily
• Navigating conflict without escalation
• Connecting technical work to business outcomes

The Manager Readiness Assessment

Score the candidate 1-5 on each dimension. Weight based on your team’s needs.

Dimension	What to Look For	Weight	Score
Coaching instinct	Voluntarily mentors, gives constructive feedback, celebrates others’ wins	25%
Communication clarity	Explains simply, checks understanding, adapts to audience	20%
Judgment under ambiguity	Makes reasonable calls with incomplete info, admits uncertainty	20%
Conflict navigation	Handles disagreement directly, doesn’t escalate unnecessarily, maintains relationships	15%
Stakeholder management	Builds trust with non-technical partners, manages expectations	15%
Growth orientation	Seeks feedback, learns from mistakes, develops others	5%
Total		100%

Minimum threshold: 3.5 weighted average with no dimension below 3.

Critical question to ask directly:

“Management means trading personal technical output for team output. Your metric becomes ‘are my people growing and shipping?’ not ‘did I ship?’ Are you genuinely drawn to that, or would you miss the technical work too much?”

Listen for enthusiasm or hesitation. The wrong answer is “I guess I’ll manage because that’s how you advance.”

The Two Engineer Profiles: Different Paths to Management

Most engineers fall into two broad profiles. Each has different management superpowers and risks.

Profile 1: The Deep Technical Operator

Strengths:

• Relentless problem-solver
• High analytical rigor
• Persistent in complex systems
• Commands technical respect

Management Superpower: Can build engineering culture of excellence. Sets high technical standards. Creates systems and frameworks that outlast individuals.

Management Risks:

• Retreats to solving instead of coaching
• Views meetings as distractions from “real work”
• Optimizes for technical correctness over team health
• Impatient with “slower” learners

Surton Case Study: The Technical Operator Success

Engineer: Senior backend engineer, #1 contributor by commits, known for fixing impossible bugs.

Selection signals:

• Had mentored 3 junior engineers to promotion
• Wrote extensive documentation voluntarily
• Expressed frustration with “bad code” but also framed it as “we need better systems”

Training approach:

• Taught management as systems optimization: “Your team is a system you can improve”
• Provided concrete frameworks for 1:1s, feedback, sprint planning
• Connected team health metrics (velocity, quality, retention) to business outcomes
• Set expectation: 50% technical contribution in Year 1, declining to 30% by Year 2

Result after 18 months:

• Team of 6 engineers, 90th percentile velocity
• Zero voluntary attrition
• Maintains technical credibility (reviews architecture, handles critical bugs)
• Quote: “I finally see management as engineering the team, not just engineering the code”

Profile 2: The Heads-Up Team Stabilizer

Strengths:

• Reads room tension quickly
• Creates clarity from chaos
• Builds trust naturally
• Translates between technical and business

Management Superpower: Can navigate complex human dynamics. Builds resilient, collaborative teams. Handles ambiguity with calm.

Management Risks:

• Avoids hard feedback to preserve harmony
• Absorbs too much emotional labor
• Confuses empathy with agreement
• Struggles with decisions that disappoint

Surton Case Study: The Stabilizer Success

Engineer: Mid-level full-stack, not top contributor, but “the person everyone asks for help.”

Selection signals:

• Mediated multiple team conflicts without management asking
• Noticed and elevated a struggling teammate before it became crisis
• Expressed interest in “helping team work better together”

Training approach:

• Focused on “steadiness”: direct feedback, clear boundaries, decision-making
• Taught that “strong management is clarity with care, not just care”
• Practiced performance conversations with role-play
• Set expectation: “Your empathy is an asset, but outcomes matter too”

Result after 18 months:

• Team of 5 engineers, highest engagement scores in company
• Successfully handled 2 performance management situations
• Built cross-functional relationships that unblock work
• Quote: “I learned that kindness without clarity isn’t kindness—it’s avoidance”

Profile 3: The Misaligned High Performer (Don’t Promote)

Profile: Top technical performer who wants influence but not people management.

Why they seem like good candidates:

• Ships constantly
• Knows everything
• Others ask them questions
• Wants to advance

Why they fail:

• Wants to be the best engineer, not enable others
• Impatient with “slower” team members
• Views management overhead as beneath them
• Will outshine team, creating resentment

Surton Case Study: The Expensive Mistake

Engineer: Staff engineer, #1 by every technical metric, brilliant problem-solver.

Red flags (in retrospect):

• Said “I guess I have to manage to get to Principal”
• Frequently complained about “junior engineer quality”
• Preferred working alone on hard problems
• Saw mentorship as distraction

Result:

• 6 months: Team frustrated, felt micromanaged and outshined
• 9 months: 2 team departures (cited “can’t grow with [X] as manager”)
• 12 months: Rolled back to IC role, demoralized
• 18 months: Left company

Cost: $400k+ in lost productivity, attrition, replacement hiring.

What should have happened: Create Staff/Principal IC track with equivalent pay and influence.

The 90-Day Training Curricula: Profile-Specific Development

Management competence develops over 12-24 months, but the first 90 days set the trajectory. Here are profile-specific training plans.

Technical Operator Curriculum (Days 1-90)

Theme: “Management is a system you can engineer”

Week 1-2: Foundations

• Read: “The Manager’s Path” by Camille Fournier (Chapters 1-3)
• Meet: 1:1 with each team member (intro, learn their goals)
• Observe: Shadow experienced manager in 3 meetings
• Establish: Weekly 1:1 rhythm with each report

Week 3-4: Systems Thinking

• Learn: 1:1 framework (status, blockers, growth, personal)
• Practice: First week of 1:1s using framework
• Analyze: Team velocity data—identify one bottleneck
• Build: First process improvement (sprint planning, code review, etc.)

Month 2: Delegation & Feedback

• Delegate: First substantial project to team member
• Practice: SBI feedback model (Situation-Behavior-Impact)
• Conduct: First performance conversation (positive or corrective)
• Shadow: Senior manager handling difficult feedback

Month 3: Strategic View

• Connect: Team work to quarterly business goals
• Measure: Establish team health dashboard (velocity, quality, morale)
• Present: Team progress to leadership
• Plan: First quarterly team goals

Key Insight for Technical Operators: Your technical credibility is an asset—use it to teach, not to solve. When tempted to take over a problem, ask: “What would I want my best engineer to do here?” Then coach them to do that.

Team Stabilizer Curriculum (Days 1-90)

Theme: “Strength is clarity with care”

Week 1-2: Foundations

• Read: “Radical Candor” by Kim Scott (Chapters 1-4)
• Meet: 1:1 with each team member (build trust, learn concerns)
• Observe: Shadow experienced manager giving direct feedback
• Establish: Weekly 1:1 rhythm

Week 3-4: Direct Communication

• Practice: Delivering difficult feedback with clarity
• Role-play: Performance management conversation with mentor
• Set: Clear expectations and boundaries (availability, response times)
• Analyze: One team conflict—practice direct resolution

Month 2: Decisiveness & Outcomes

• Make: Decision that disappoints someone (scope cut, priority shift)
• Practice: Explaining “why” without over-apologizing
• Delegate: Project with clear success criteria (avoid over-checking)
• Review: Team outcomes vs. team happiness (both matter)

Month 3: Strategic Influence

• Navigate: Cross-functional conflict or negotiation
• Present: Team needs to leadership with data
• Hire: First interview loop (practice decisiveness in selection)
• Plan: Quarterly goals with clear accountability

Key Insight for Stabilizers: Your empathy builds trust—that’s your superpower. But trust requires outcomes. Team members need to know you’ll tell them hard truths, make tough calls, and hold them accountable. Care without clarity creates dependency, not growth.

The Dual-Track Career Ladder: Creating an Alternative Path

The best way to improve management transitions is to make management optional for advancement. Here’s the dual-track ladder Surton recommends:

Individual Contributor Track

Level	Title	Scope	Compensation Range
IC4	Senior Engineer	Feature/Subsystem	$150k-200k
IC5	Staff Engineer	Domain/Area	$180k-250k
IC6	Principal Engineer	Multiple Teams/Org	$220k-320k
IC7	Distinguished Engineer	Company-Wide/Industry	$300k-500k+

Management Track

Level	Title	Scope	Compensation Range
M1	Engineering Lead	Team (4-8 engineers)	$160k-220k
M2	Engineering Manager	Multiple Teams	$200k-280k
M3	Director of Engineering	Department	$280k-400k
M4	VP of Engineering	Organization	$350k-600k+

Key Principle: IC5 ≈ M1, IC6 ≈ M2, IC7 ≈ M3 in compensation and organizational influence. Technical excellence and people leadership are equally valued paths.

Signs You Need a Better IC Track:

• Engineers asking “how do I advance without managing?”
• Top performers leaving for “senior” titles elsewhere
• People taking management roles they don’t want
• Technical decisions suffering because best engineers became managers

When to Roll Back: Graceful Exits from Management

Sometimes the right answer is to move someone back to IC work. Do this quickly, supportively, and without stigma.

Signs It’s Time:

• Team morale declining after 6+ months
• Manager expressing misery or burnout
• Technical work suffering because they’re stretched
• Better fit available (someone else ready to manage)

How to Handle It:

1. Private conversation: “Management doesn’t seem to be bringing out your best. What do you think?”
2. Normalize it: “Many great engineers try management and return to IC work. Both are valuable.”
3. Create soft landing: Move to Staff/Principal IC role with equivalent pay
4. Public framing: “[Name] is moving to focus on deep technical work where they excel”
5. Celebrate expertise: “We’re lucky to have their technical leadership”

Surton Case Study: The Graceful Rollback

Engineer promoted to manager, struggled for 8 months, team unhappy.

Intervention:

• Private conversation acknowledged mismatch
• Moved to Staff Engineer role (same compensation)
• Gave high-visibility technical project
• Framed publicly as “doubling down on technical expertise”

Result:

• Engineer thrived, became top technical contributor
• Team recovered with new manager
• No stigma—engineer later mentored others on “finding your path”

When Surton Can Help

If you’re facing:

• Repeated failed management transitions
• Uncertainty about who to promote
• Need for dual-track career ladder design
• Training curriculum development
• Coaching for new managers
• Rolling someone back from management gracefully

Surton offers Leadership Development services where we:

1. Assess management candidates using proven frameworks
2. Design 90-day training curricula
3. Coach new managers through transition
4. Build dual-track career ladders
5. Develop internal management training programs

Typical engagement: 3-6 months, $30k-60k
Typical ROI: Avoid $200k-500k in failed transition costs, build sustainable leadership pipeline

---

Related Resources

• How to Actually Hire Great Engineers — Hiring managers is step 1
• Developer Onboarding is Your Most Expensive Product Failure — Onboarding new managers
• Your Best Engineer Might Be Your Worst Manager (Original) — The Blueprint edition

---

This is Surton’s definitive 2025 leadership transition playbook. For the original newsletter version, see The Blueprint.