Strategy notes: turning intent into priorities
A practical strategy document does not need to be long. What it must do is reduce interpretive wiggle-room: define a target, specify what is out of scope, and state the trade-offs you are willing to make. This note walks through a one-page strategy brief and explains how to write assumptions in plain language so they can be tested later.
Suggested output: a one-page strategy brief with three sections—context, priorities, and constraints—plus a short list of assumptions that would change your plan if proven wrong.