Tech Lead Guide
The first-90-days playbook for new tech leads and engineering managers — written by someone who learned it the hard way so you don't have to.
Tech Lead Guide
A field manual for new tech leads: first-month diagnosis, delivery control, coaching, planning, architecture judgment, incidents, stakeholder communication, delegation, and sustainable execution.
First 30 Days
Use the first month to learn the real system, build trust, and publish a grounded operating readout before you start changing the team around you.
The first month is reconnaissance, not performance theater
New tech leads often come in wanting to prove range immediately. Resist that urge. In the first month your leverage comes from learning the real system: where delivery is already fragile, which decisions are actually political, and which people are carrying invisible load for everyone else.
The first month is for building an accurate model of the team, not showcasing how much process you can rewrite.
What to learn fast
- Which commitments are genuinely critical this quarter.
- Which engineers or partners hold the unofficial context map.
- Which recurring incidents or escalations still shape team behavior.
Understand the system before you optimize it
Read roadmap history, incidents, and open escalations
Identify owners, dependencies, and overloaded people
Confirm 30 60 90 day expectations with your manager
Make one or two changes with a clear reason and low blast radius
If you need a structure for the memo you publish at day 30, start with a simple ADR-style template and write down the operating facts plainly.
Sample artifact: first-month operating readout
Use the full chapter's readout template to produce a short memo with current commitments, delivery risks, ownership gaps, reliability concerns, and the rituals you plan to change first. The paid guide includes the full interview map, red-flag checklist, stakeholder questions, and operating memo format.
1:1s, Coaching, and Expectations
A lead creates leverage through repeated expectation-setting, direct coaching, and follow-through. Good 1:1s are where that operating loop becomes visible.
A good 1:1 is not a status meeting in disguise
You already have issue trackers, standups, and docs for status. A 1:1 is where you learn how a person is experiencing the work: where they feel blocked, where they are stretching, and where your own leadership may be creating drag without you noticing.
If every 1:1 sounds like a project update, you are paying for a coaching surface and using it as a reporting surface.
A useful 1:1 rhythm
- Start with what changed since the last conversation.
- Separate delivery blockers from growth and role clarity.
- Leave with one concrete follow-up on each side.
A useful conversation balances delivery, growth, and clarity
- Blockers and operating friction
- Growth and feedback
- Role clarity and scope
- Project status details
For feedback language that is both direct and humane, Radical Candor is still a useful reference point.
Sample artifact: 1:1 continuity note
The full chapter includes a reusable 1:1 note structure, coaching patterns for four common situations, expectation reset language, and a monthly growth review checklist so the conversation creates follow-through instead of just status.