Every quarter, many teams write a planning document that runs to twenty pages. It takes two weeks to write, gets read once, and is out of date by the second sprint. A one-page plan is harder to write, because it forces choices, but it is the plan people actually use.
Start with one outcome, not a feature list
Write a single sentence that describes how things will be different at the end of the quarter. “Launch the mobile app” is a project. “New customers can manage their tasks from their phone on day one” is an outcome. Outcomes make it easier to cut work that does not serve them.
If you cannot pick one, pick at most three, and rank them. A ranking settles arguments in week eight that a flat list never will.
Fill in the page
Our one-page plan has five parts. Each fits in a few lines:
| Section | What goes in it | Length |
|---|---|---|
| Outcome | The one sentence above | 1 line |
| Bets | Three to five projects you believe will get you there | 5 lines |
| Not doing | Good ideas you are choosing to skip this quarter | 3 to 5 lines |
| Measures | How you will know it worked | 2 to 3 numbers |
| Risks | What could stop you, and who watches it | 3 lines |
The “Not doing” list is the most useful part of the page. It tells everyone, including the people asking for those ideas, that the decision was made on purpose.
Turn bets into milestones
A bet like “Rebuild onboarding” is too large to track. Break each bet into two to four milestones that each end in something you can show: a prototype, a beta with five customers, a public launch. Put each milestone on the shared calendar with an owner and a date.
Milestones turn a quarter into a series of short finish lines. Teams that hit a milestone every two or three weeks keep momentum far better than teams that aim for a single big release at the end.
Review it every two weeks
A plan is a guess. Every second Friday, spend twenty minutes on these questions:
- Are we still working on the bets on the page?
- Did any milestone slip, and do we know why?
- Has something changed that should move a bet to “Not doing”?
Update the page in place and note what changed and why at the bottom. By the end of the quarter, that short log is the most honest retrospective you will have.
If your plan never changes, you are not reading it. If it changes every week, you are not planning.
Share it everywhere
Pin the page at the top of your project space, link it from your weekly sync notes, and read the outcome sentence out loud at the start of each planning meeting. The goal is simple: anyone on the team should be able to explain what the quarter is about in one sentence, without looking it up.
