Framework
The 90-day execution brief
A short sequence of initiatives with owners, metrics and a reason to stop — instead of a roadmap that only grows.
A long roadmap is comforting and usually unread. The execution brief is the opposite: few initiatives, each one small enough to finish or kill inside a quarter.
What goes on it
Every line has the same fields. The friction it attacks. The move (buy, build, integrate, or stop). The owner, who is a person, not a department. The dependency that would block it. The metric. The date the leadership team will look again and decide to continue or cut.
Initiatives that cannot fill those fields are not “later.” They are not on the brief. Parking them in a backlog is how a company pretends to prioritize.
Cadence
The brief is reviewed on a fixed rhythm, short enough that a stuck item cannot hide for a month. The meeting is not a status tour. It is a decision meeting: what changed, what is blocked, what should stop.
Used this way, technology work becomes legible to a founder or a board. They can see sequence, risk and the cost of adding one more idea. That legibility is the product. The tools are downstream of it.