From engineer to lead, what actually changed
The uncomfortable, useful shifts in how I spend attention after moving from writing code to leading the people who write it.
The first thing nobody tells you is that your output becomes invisible. You end a week having shipped nothing you can point at, and you have to learn to measure yourself differently.
Your job is decision quality, not decision volume
Most decisions do not need you. The ones that do are the ones that are hard to reverse. Spending your attention proportional to reversibility is the single highest-leverage habit I picked up.
Context is the product you ship
A team with good context makes good decisions without you in the room. Most of what looks like a performance problem is actually a context problem, someone optimizing correctly for the wrong goal because nobody told them the real one.
Stay close enough to the code to be useful
- Read pull requests, even when you do not comment.
- Keep one small thing you own end to end, so you feel the friction the team feels.
- Never take the critical path, your calendar will break it.
The trade is real, you give up depth for reach. It is worth it on the weeks when a team of eight ships something none of them could have shipped alone.