So You Just Became a Tech Lead /Manager— Now What?
Stakeholders are cheering, LinkedIn is on fire, and your imposter‑syndrome is whispering in 120 FPS Dolby Atmos.
Welcome to leadership!
Below is a distilled survival guide built from battle‑scars, late‑night stand‑ups, and the voice notes you just listened to. Grab a coffee (or cigar — keto‑friendly, of course) and let’s jump in.
You did it — Software Engineering Lead/Manager/Head! 🎉 But before you buckle down into back-to-back meetings, let me pull back the curtain on what really helped me survive those first few sleepless weeks (literally). Picture this: I’m lying in bed at 2 AM, staring at the ceiling, my mind racing through OKRs and sprint backlogs. I’d pop a sleeping pill, only to wake up at dawn thinking, “Did I really call that function async?!” If you’ve ever been there, read on — I’ve gathered the hard-earned lessons (and a few embarrassing confessions) so you don’t have to learn them the hard way.
1 🔥Don’t Set Yourself on Fire to Keep the Team Warm
Yes, the promotion feels huge, yes you’re binge‑reading leadership books, yes Udemy keeps spamming “70% OFF Agile Guru Mega‑Bundle”.
Breathe.
Leadership, like engineering, has grades — junior lead, senior lead, manager, senior manager, etc. You’re not expected to debug humanity on day one.
Quick sanity loop
if (workload > capacity) {
delegate();
renegotiate_scope();
sleep(7_hours);
}Burn‑out fixes nothing; it just produces crispy managers.
You don’t spawn at C‑level wisdom just because your email signature says so.
Your team needs a rested brain, not a heroic corpse.
Checkpoint:
If your Apple Watch congratulates you for standing at 3 a.m., close the laptop, not another JIRA ticket.
2 🤝Scrum Is More Than Daily Stand‑Ups
You already run 80–90 % Scrum — nice! Now refine the edges:
Pro‑tip: Small‑talk is compounding interest for hard talks later.
3 👂Listen Like Your Sprint Depends on It (Because It Does)
Some teammates ship code; some dodge JIRA like Neo. Patterns emerge only if you pay attention. During 1‑1s ask:
- “What’s one thing draining your energy right now?”
- “Which tasks light you up?”
- “Anything outside work that might bite our timeline?”
Record insights, but respect privacy. Not everyone loves being quoted verbatim in your notebook.
The Listening Trifecta: Ears, Notes, and Silence
Early on, a senior dev whispered to me: “I feel like you write everything I say; makes me nervous.”
Fair. I switched from notebook‑in‑face to:
- Signal permission — “Mind if I jot a bullet so I don’t forget?”
- Summarize back — “So the Docker build time is what’s killing you, right?”
- Zip it — 3‑second pause before responding. (Feels like forever; works wonders.)
4 🛠️Design for Collaboration, Not Heroics
Pair programming, PR reviews, Friday “choose‑your‑own‑task” mini‑hackathons — anything that spreads context and kills single‑points‑of‑failure. Rotate domains (front‑end folks take a back‑end ticket occasionally) so vacations ≠ velocity‑freefall.
Pair Fridays & Tiny Experiments
We shrank our formal sprint to four days. Every Friday afternoon:
- Each dev grabs a 1‑pointer of their choice — tech debt, refactor, AI POC, whatever.
- We pair/mob for two hours, cross‑pollinating domains.
- Outcome posted in #friday‑demos with GIFs.
Morale ↑, silos ↓, and vacation coverage suddenly painless.
Transparency ≠ sharing every Slack rant. Give macro‑status, surface risks early, keep surprises to birthdays.
5 🥋Stakeholder Kung‑Fu: Buffer, Broadcast, Bravo
Developers estimate with optimism; calendars count with cruelty.
My rule of thumb: add 25 % before any external commitment. When we deliver early, we’re ninjas; when we slip, we’re merely on time.
Template
team_best_guess = X days
buffered_estimate = X * 1.25
communicate(buffered_estimate)
deliver(< estimated_days)
celebrate!And yes — celebrate publicly when someone beats the clock. My team’s Slack has a 🎉‑emoji alias called :under‑promise‑over‑deliver: (Reasonably of course!)
6 📈Retrospectives: The Real Continuous Integration
Protect that hour like prod‑data. Celebrate wins aloud. Slap post‑its on pain‑points. Convert complaints into action items with owners and due dates. Then… actually follow up.
Delegation Is Not Dumping — It’s Growth Hacking
The first sprint, I secretly rewrote a junior’s failing tests at 1 a.m. (remember the pill?). He never learned, I lost sleep, and the defect resurfaced two weeks later.
Now I ask: “What’s your next step?”
If they shrug, we craft it together. If they nail it, I broadcast the win. Either way, I keep fingers off the keyboard unless pairing.
7 🧑💻Manager vs. Maker: Declare Your Path
If you love code: stay hands‑on, own architecture reviews, mentor via PRs.
If you crave org‑charts: push responsibility outward — don’t secretly finish lagging tickets. Instead, craft growth plans: courses, brown‑bag talks, safe “training” tasks.
Either way, spotlight team wins publicly. People repeat what gets celebrated.
8 🧪Change Is a Versioned API — Increment, Don’t Rewrite
“Congrats, I’m boss now — let’s refactor the entire process by Monday!” 🛑
Change Management: The One‑Knob Rule
I once drafted a Notion doc titled “50 Immediate Process Improvements.” Guess how many shipped? Zero.
Now I enforce the One‑Knob Rule: tweak a single system knob per sprint — max. Show value, then twist another.
Ship improvements in thin vertical slices:
- Pick one friction (e.g., flaky CI).
- Prototype fix with a volunteer squad.
- Socialize results, iterate, then roll wider.
Your credibility curve is an S‑curve; pace yourself.
9 🧘♂️Personal Learning Without Meltdowns
Reading ten leadership books in a week ≠ leadership; ten leadership books half‑read help no one. It’s procrastination with better lighting. My cadence:
- Pick one skill per quarter (e.g., advanced metrics dashboards).
- Allocate 90‑minute block Thursday mornings for study.
- Apply within two sprints or drop it.
Deep > wide. Always.
Guard Your Curiosity Bandwidth.
Choose a couple of focus areas per quarter — advanced Scrum facilitation or AI team metrics, not both plus Kubernetes the‑hard‑way.
Depth > diffusion.
10 🏆Remember: Outcomes Are Collective
If a sprint tanks, it’s a team failure, not your personal villain‑origin story. Own the process, share the lessons, move on.
When Insomnia Creeps Back…
These days, if my mind revs past midnight I:
- Jot the thought into a Notes App.
- Close every glowing screen.
- Brew chamomile (decaf, promise).
- No pills, no coffee.
Because the best gift to your team is a conscious leader at 9 a.m., not a zombie clutching Red Bull.
✅TL;DR Epilogue: Your Turn at the Mic
Leadership isn’t a course you finish; it’s a codec you keep updating. You’ll blow estimates, misread people, maybe even reach for your own dubious pill‑and‑coffee combo. It’s fine. Iterate.
☐ Sleep ≥ 7 h/night
☐ Daily stand‑up ≤ 15 min
☐ 1‑1s booked for every team‑mate this sprint
☐ Buffer added to all stakeholder estimates
☐ At least one public team win celebrated this week
☐ One small process experiment in flight
☐ Personal learning target scoped and visible
Action queue for Monday:
☐ Schedule 1‑1s for the next two weeks.
☐ Add 25 % buffer to any date you owe Product.
☐ Plan one “Friday Freedom” ticket.
☐ Choose a single process knob to tweak.
☐ Close laptop by midnight — no pharmacology required.
See you at the retrospective — bright‑eyed, well‑rested, and possibly over‑caffeinated (but pill‑free). 💙
📖Further Reading & Listening🎧
- “Scrum Mastery: From Good to Great Servant‑Leadership” — Geoff Watts
- “Managing Humans” — Michael Lopp
- “The Manager’s Path” — Camille Fournier
- “Software Estimation: Demystifying the Black Art” (Steve McConnell)
- Atlassian Guide: Retrospectives: Sprint Retrospective: How to Hold an Effective Meeting | Atlassian
Take it easy, stay curious, and never forget: great leaders ship code — mental, organizational, or otherwise — one small commit at a time.
Special thanks to my dear friend Mahmoud Joumaa whom I dedicate this work to :)
