In almost every technology company, career progression follows a familiar pattern: you become the go-to Senior Engineer who writes the cleanest code, debugs the gnarliest production outages, and ships complex features faster than anyone else on the squad. As a reward, leadership promotes you to Tech Lead or Engineering Manager.
Six months later, you are exhausted. You are in meetings from 9:00 AM to 4:00 PM, coding until midnight so you don't "fall behind," and frustrated that your teammates aren't building things the way you would. At Crack The Stack, we coach dozens of newly promoted technical leaders through this exact transition. The secret is realizing that leadership isn't a promotion on the same track—it is a career change that requires unlearning the habits that made you a star individual contributor.
Habit #1 to Unlearn: Being the Hero on the Critical Path
As a Senior Dev, taking the hardest, highest-risk ticket in the sprint made you invaluable. As a Tech Lead, taking the hardest ticket makes you a single point of failure. Because your calendar is fragmented by architectural reviews, stakeholder syncs, and 1-on-1s, putting yourself on the critical path guarantees the sprint will stall whenever you get pulled into an urgent meeting.
The New Habit: Delegate the complex, high-growth tickets to mid-level and senior engineers on your squad, and act as their architectural sounding board and pair-programming partner.
Habit #2 to Unlearn: Measuring Your Worth by Commits Merged
When you spend all Tuesday unblocking a cross-team API dependency, mentoring a junior developer through a tricky test suite, and refining next sprint’s epics with your Product Manager, it is easy to look at GitHub at 5:00 PM and feel like you "got nothing done today."
The New Habit: Redefine your unit of output. As a Tech Lead, your compiler is no longer just the codebase—your output is the velocity, clarity, and quality of your entire squad. If five engineers ship 30% faster because you cleared their architectural ambiguity on Monday, you had a massive week.
Habit #3 to Unlearn: Rewriting Teammates’ Code in PR Reviews
Nothing crushes a team's psychological safety and autonomy faster than a Tech Lead who leaves 45 nitpicky comments on every Pull Request—or worse, pulls down the branch at 10:00 PM and rewrites it "because it was faster to just do it myself."
The New Habit: Distinguish between architectural safety (security flaws, N+1 database queries, broken contracts) and personal stylistic preference. Automate formatting and linting in CI so humans never argue about syntax, and let teammates own their implementation choices even if it’s 10% different from how you would have written it.
Habit #4 to Unlearn: Shielding the Team From Business Context
Some well-meaning Tech Leads try to "protect" their developers by attending all product discovery meetings alone and handing the team pre-digested technical tasks. The unintended consequence? Engineers become disconnected ticket-takers who build the wrong edge cases because they don't understand the customer problem.
The New Habit: Bring engineers directly into user story mapping and backlog refinement. Lead with Commander’s Intent—explaining the why and the business constraints—so your developers can propose creative, simpler technical solutions.
3 Questions to Ask Yourself Every Friday
- "If I took an unexpected two-week vacation starting Monday, which part of our sprint or deployment pipeline would halt?" (Whatever that is, make it your #1 priority to document and cross-train next week.)
- "Did I solve problems FOR my team this week, or did I coach them to solve the problems?"
- "Do every one of my engineers know how their current ticket connects to our quarterly business goal?"
Habit #5 to Unlearn: Avoiding Difficult Interpersonal Feedback
Compilers give instant, objective error messages; humans don't. Many technical leaders avoid addressing a teammate's chronic late PR reviews or dismissive tone in standups because they fear awkward conflict. Left unaddressed, that friction quietly drives your best performers to quit.
The New Habit: Practice radical candor early and privately in 1-on-1s—focusing on observable behavior and its impact on the squad rather than personality labels.
Accelerate Your Engineering Leaders & Tech Careers
Whether you are upskilling newly promoted Tech Leads across your organization or looking to break barriers in your own tech career, Crack The Stack offers tailored leadership and career workshops.
Continue the Conversation on Facebook
Follow Crack The Stack on Facebook for weekly Agile clinic breakdowns, engineering leadership playbooks, and live Q&As with our coaching team.
Follow @crackthestack on Facebook