How the tech leads track is organised

This track is written for the person doing the lead role, whether or not the title is on the org chart. It is short by design: three topics and this note.

Reading order

Start with what a technical lead is accountable for. It sets the three headings the rest of the track uses.
Then read the skills inventory and mark the two rows you would most like to change.
Read getting value out of being coached last, when you have something specific to bring.

How it relates to the coaches track

The coaches track covers the same ground from the other chair: how a session is run, the model it follows, and the mechanics that keep a series of sessions honest. Reading across the two tracks is worthwhile even if you only ever sit in one of the chairs, because it makes the shape of the conversation predictable.

A note on scope

These guides deal with leadership practice, not with any particular technology stack, and not with employment, contractual or compensation questions. Where a situation turns on those, it belongs with the people in your organisation who are equipped to handle it.