The Tech Lead Who Never Let Go of the Keyboard

Stay technical while your team gets rewritten under you.

For: Engineering Managers, Directors, Tech Leads moving into managementFormat: 45-60 min keynote
Marian Kamenistak presenting on the real role of Staff and Principal developers at an ELC engineering leadership meetup.

Why does a tech lead become the bottleneck when they hold onto the keyboard?

You took the lead role and kept the keyboard. Two years on, the codebase moved without you, the team routes around you on technical calls, and you are the bottleneck on both sides. The trap is not staying technical. It is never deciding which technical.

You leave with the Team Lead Readiness Test: seventeen questions, six dimensions, a straight verdict and your top two gaps. Three minutes, and it will tell you things your manager has not.

Why this talk, not a generic version of it

Most management-transition talks tell tech leads to stop coding. This one argues that's the wrong instruction: the trap isn't staying technical, it's failing to decide which technical stays yours. Two years into the role, that seat turns into the bottleneck on both sides, and the person in it rarely notices exactly when it started.

It's aimed at tech leads and engineering managers who kept the keyboard and are starting to feel the codebase move without them. The close is the Team Lead Readiness Test, seventeen questions across six dimensions, a straight verdict, and the two gaps worth fixing first, run live in under three minutes.

What the room walks out with:

Take the readiness test →

Quick answers

Who is "The Tech Lead Who Never Let Go of the Keyboard" for?
Engineering Managers, Directors, Tech Leads moving into management
What format is it delivered in?
45-60 min keynote

More talks

← Back to all talks