My youngest tech lead asked why nobody warned him the role sucks
He was right to ask. The promotion confiscates the scoreboard an engineer can read and hands them one they can't. The Scoreboard Swap, and the unglamorous weeks of prep that keep a new tech lead from breaking.
My youngest tech lead came to me a few weeks into the job and asked why nobody had the decency to warn him the role sucks.
He was right about the role. Wrong about the nobody. Somebody was supposed to warn him, and that somebody was me.
This is the warning he should have gotten.
We did what most companies do. We took someone happy and good at writing code, handed him a title, and acted surprised when the title turned out to be a different job.
A tech lead still writes code. Far less of it. The rest of the time he's a project manager, a part-time architect, a mentor, and a news anchor, translating the project's reality up and down at the same time.
All of it runs on influence and zero formal authority. He can't make anyone do anything. He can only be right often enough, and decent enough, that people choose to follow. That's the hardest currency in the building to earn. One bad month spends it to zero.
The Scoreboard Swap
The workload doesn't sink a new tech lead. The Scoreboard Swap does.
For a decade this person has been winning on a scoreboard they can see and trust. Lines shipped. Hard bugs killed. The gnarly thing nobody else could crack. Every signal on that board is fast, personal, and objective. The compiler doesn't flatter anyone.
The title quietly confiscates that scoreboard and hands them one they can't read yet.
The new board pays out in other people's output. It updates in quarters, not minutes. Nothing on it compiles. Their best day might be one where they wrote no code at all, unblocked four people, and killed a doomed project before it started.
On the old scoreboard, that day is a zero.
So most new leads spend their first quarter privately convinced they're failing. They're still measuring themselves on the old scoreboard while being paid for the new one.
Prep them for the calendar and the meetings all you like. If you don't tell them the old scoreboard is gone for good, and that losing it is going to hurt, they'll spiral quietly while telling you they're fine.
Nobody showed me the numbers either
I first did this in 2008. My coding time fell from roughly 95% to 50%. My meetings went the other way, just as hard. The slice of my day I actually controlled dropped to about nothing. The calendar stops being yours the day the title lands.
Nobody warned me those numbers were coming. I learned them slowly, and at other people's expense.
That last part is the real bill. A new lead's learning curve is paid by the team underneath them.
Whether leads are born or made is a separate fight, and not this post's. This one owns the making.
The prep nobody does
Not a training course. A few unglamorous weeks before the title ever lands.
Tell them what is coming. Spend the run-up in extra 1:1s. Cover the good and the genuinely irritating, weighted about three to one so you don't scare them off. Don't promise it will be easy.
Rehearse the conversations they've only ever received. They've taken plenty of hard feedback. Delivering it to a friend is a different sport.
The same goes for requirements. They have years of muttering about vague specs and have never once looked a product manager in the eye to say "not like this."
Run those conversations out loud while the stakes are pretend. The first real one arrives with the adrenaline up, and that's the worst possible time to be improvising.
Pick the first project like it matters. It does. Make it winnable.
The cursed legacy system held together by one person and a prayer isn't a starter project, however satisfying it would be to finally hand it off. The first project writes the team's first story about the new lead. Choose the story.
The first quarter is yours too
Then show up. Hardest when they're flailing.
More 1:1s, not fewer. The instinct after a promotion is to step back and give room. Wrong direction. The room is exactly where they drown.
Let them vent at you. Your office is a better place for it than their peers or your manager. Venting to peers is the team watching its lead wobble. Venting to your manager is the promotion case getting re-litigated. Venting at you is free.
Let them make the mistakes you can still quietly clean up behind. And never bench a panicking new lead. Coming back from the bench is worse than the panic was, because now there's a story about them.
One rule above all
You have authority. They do not.
So never fix their problem by pulling a string only your seniority can pull.
It works, which is the trap. The blocker dies in one phone call and everyone goes home happy. But you've helped them once and undercut them twice.
The team has now seen that the real power still lives with you. Every escalation after that routes around the lead by default, because you just taught everyone where the strings are.
Hold the string. Coach them to solve it at their own altitude, even when it takes a week longer.
The week is the tuition.
The warning
Skip the prep and you find out, somewhere around month three, that you traded one of your best engineers for one of your worst-supported managers.
Warn them before the title lands. Stay close while they learn the new scoreboard. Never make their authority look borrowed by solving the problem from your altitude.
My youngest tech lead asked why nobody warned him. Fair question.
The next engineer I promote gets this post before the title does.