Skip to lesson
Exit
Leadership, Behavioral & Why Cursor1 / 3

2 min lesson

Hold top performers while you fix the bottom

Work through the cases in "Hold top performers while you fix the bottom", pairing each signal with the move that fits.

Step 1 of 3

Hold top performers while you fix the bottom

Your best engineers leave when underperformance goes unaddressed, because they end up covering for it. Addressing the bottom is partly how you retain the top.

Retain the top

Give them the hard, high-impact problems - the agent backend redesign, the auth migration - and the autonomy to own them.

Be visibly fair: they trust you more when they see you handle the hard case, not less.

Address the bottom

Move with care and speed; a slow, vague process is worse for the person than a clear one.

Keep it private and respectful - the team should see fairness, not a public correction.

Learn more

Full explanation

Drive decisions without authority

Drive decisions without authority

In a consensus-leaning org you rarely win by deciding; you win by persuading. Conflict with product, infra or security gets resolved with evidence and a reversible bet, not a mandate.

Cross-functional conflict, resolved without rank
With product
Reframe the tradeoff in their currency: 'this auth shortcut ships the feature this week but costs us a revocation gap; here's the safe version that lands next week'
With infra
Bring the SLO and the cost number; argue the contract boundary on data, not on territory
With security
Treat them as a partner on token rotation and signing, not a gate to route around; co-own the risk
When you disagree
Make the smallest reversible decision that produces evidence, then let the data settle it
Say it like this

“One of my senior engineers was missing commitments and the team had started quietly working around him. I sat down and named it plainly: here are the three things that slipped and I want to understand why. It turned out he was stuck on an ambiguous part of the webhook redesign and embarrassed to ask. We re-scoped it, set two-week milestones and paired him with someone for the first sprint. He hit them. The lesson for me was that I'd read 'unclear scope' as 'underperformance' for a month longer than I should have and I should have diagnosed before I judged.”

Watch out

Avoiding the hard conversation is the most common real failure and interviewers can smell when a story skips it. If your underperformance story has no actual confrontation in it - just coaching that quietly worked - it reads as either fiction or avoidance. The discomfort is the proof you were there.