The Hardest Shift Isn't Technical
Most devs promoted to tech lead expect harder problems. Wrong. Hardest part: **stopping yourself from coding everything**.
Old job: ship features, fix bugs, optimize queries. New job: unblock others, align stakeholders, make decisions with incomplete data. Same codebase. Different game.
What Changes Day-to-Day
Time allocation flips.
| Before | After |
|--------|-------|
| 80% coding | 20% coding |
| 20% meetings | 50% meetings |
| 0% mentoring | 30% mentoring |
First 3 months feel unproductive. Normal. Output now measured through **team velocity**, not personal commits.
Three Skills to Build Immediately
1. Delegation without micromanagement
Assign tasks. Define acceptance criteria. Step back. Check progress at milestones, not hourly. Trust builds when you resist urge to rewrite their code.
2. Technical decision-making at scale
Stop optimizing for "best" solution. Optimize for **team-maintainable** solution. Document trade-offs. Record decisions in ADRs (Architecture Decision Records).
3. Stakeholder translation
Product says "make it faster." Translate: "Reduce p95 latency from 800ms to 200ms by Q3." Bridge between business language and engineering reality.
Common Traps
Keep Technical Credibility
Stay in codebase. Review PRs. Pair program occasionally. But **choose battles**: focus on architecture, not implementation details.
Read system design docs. Ask "why" in design reviews. Technical depth earns respect; hands-on coding does not.
Practical Takeaway
First 90 days: observe, listen, map team dynamics. Identify one bottleneck. Fix it. Then repeat.
Success metric: **team ships faster without you coding**. That's the job now.