How I lead
The habits I hold myself to and ask of the people I work with. None of them are new. The hard part is doing them every week.
People first, then process
Most teams are limited by how fast their people grow, not by their tools. I give everyone a written development goal, pair juniors with seniors on real work, and put engineers in front of customers early so they learn to explain trade-offs.
Write it down
Remote teams run on writing. Decisions, plans and incident reviews should be readable by someone who was not in the meeting. I keep design documents to one shape: the problem, the options, the choice and its trade-offs.
Quality is a system
Small changes merged often, tests in the same change as the code, a pipeline that enforces the definition of done, and incident reviews that end in a change. The architecture gets the credit; these habits do most of the work.
Say the hard thing early
Feedback goes out early and in private, praise goes out specific and in public. Underperformance gets a clear, time-boxed plan and a follow-through. I would rather hear bad news first, and I try to be the manager people can bring it to.
Product and engineering own the outcome together
Product owns the problem and the priority. Engineering owns the solution and the estimate. Both own the result, and both should be in the room when a customer gives feedback.
The rhythm of a well-run team
- Daily
- A short sync about blockers, not status. Pull requests reviewed the same day.
- Weekly
- One-to-ones with every report, with the agenda theirs. Planning, a demo of what shipped, a look at alerts and error budgets.
- Monthly
- A retrospective with at least one real change. A review of on-call load and incident trends.
- Quarterly
- Roadmap and capacity with product. Written feedback for everyone. A deliberate decision about what we stop doing.
A manager who cannot read the pull request cannot judge whether the date is real.
So I still review designs and code and debug production with my teams.