A one-page technical strategy your executives will read
Most engineering strategies are lists of goals. How to write one that makes real choices, fits on a page and gets a decision from the people who fund it.
Notes on leading technical teams
Practical articles for engineering and technical managers, from your first one-on-one to multi-year strategy. Each one is marked with the stage of the certification path it's written for. New posts every Tuesday and Friday.
Earlier posts
-
One-on-ones that engineers don't dread
A practical setup for one-on-ones: who owns the agenda, a running-doc template, a question bank for when things go quiet, and the habits that ruin them.
-
Getting another team to deliver what your team depends on
How to find cross-team dependencies early, ask for them in a way the other team can say yes to, track them weekly and escalate without burning bridges.
-
Engineer to manager: what actually changes in your week
The switch to management changes how your output is measured, how fast you get feedback and where your time goes. What to expect, and how to test it first.
No posts for this level yet.