Start at the End

The best plans are written backwards

Most plans are written forwards. They start where the author is standing - the idea, the tool, the thing someone already wants to build - and work outwards from there, accumulating detail until a destination is eventually implied. It is the natural way to write, and it is why so many plans arrive heavy, confident, and pointed at nothing in particular.

The better plans are written backwards. They start at the end - the outcome the work is meant to produce - and everything else earns its place only by moving toward it. The difference sounds small. It is the difference between a document that can be steered and one that can only be finished.

I learned this backwards, by doing it forwards for years. Early in my career I mistook thoroughness for rigour and volume for progress, and I confused being busy with being clear. I wrote the heavy plans, led with the solution, and reverse-engineered the case for it. It took me longer than I would like to admit to see the pattern: that the quality of a plan is set almost entirely by where it starts, and that the best place to start is the end.

The trap of speed and volume

Modern organisations reward two things that feel like progress and are frequently its enemy: speed and volume. Move fast. Ship more. Fill the pack. Produce the deck by Thursday. The pressure is real and rarely questioned, because both are easy to measure and both photograph well in a status report.

But speed and volume are proxies, and poor ones. They measure activity, not direction. A team can move at extraordinary pace toward the wrong outcome, and produce an enormous body of work in service of a question no one ever settled. The faster you move before you have defined success, the more expensive the eventual correction - and the correction always comes.

The discipline that separates senior operators from busy ones is the willingness to slow down at exactly the moment everyone else is speeding up. Not to slow the work. To slow the start. To spend the first hour on the question that governs the other hundred: what outcome are we actually chasing, and how will we know we reached it?

There is an old piece of wisdom that captures it. Give someone six hours to fell a tree and the wise ones spend the first four sharpening the axe. It sounds like procrastination and it is the opposite. The one who sharpens has assessed the tool, judged its condition, and invested deliberately so the cutting, when it starts, goes fast and clean. The one who skips it and swings immediately looks productive from the first minute - chips are flying, effort is visible, progress appears to be delivered. But a blunt axe does not fell a tree slowly. Often it does not fell it at all. It just exhausts the person swinging, while everyone watching mistakes the motion for headway. Most failed plans are blunt-axe plans: enormous energy spent, real activity on display, and a tree still standing at dusk.

Begin with the outcome

Starting at the end means writing the destination before the route. Before the recommendation, before the cost, before the plan - name the outcome the work is meant to produce, in one plain line.

What are we actually trying to achieve? What needle are we trying to move, and in which direction? What would make this a success six months from now, in terms a sceptical stakeholder would accept? These are the same question from different angles, and until they are answered, nothing downstream can be judged, because there is no standard to judge it against.

And it must be the real outcome, not a stand-in. “Roll out the new platform” is an activity, not a result. “Reduce the time it takes a customer to get paid” is a result. The distinction is not pedantry; an activity can only be completed, while an outcome can be aimed at, measured, and course-corrected toward. Leaders reach for the solution far too early - it feels decisive, it feels like progress - and a plan that opens with a solution has quietly answered a question the room never agreed to ask.

State the outcome first, plainly, and everything after it acquires a purpose. Every cost, every risk, every option can now be weighed against a single question: does this move us toward the end we named? Skip it, and the whole enterprise becomes motion without a compass - fast, voluminous, and lost.

The plan on a page

This discipline needs a physical form, or it stays an intention. That form is a single page.

Not a page to summarise the work after the fact. A page to begin the work - the first artefact you create, before the deck exists, before the document has a title. A plan on a page. One side, plain prose, built in order from the outcome down.

It answers a short and unforgiving list. The outcome, first and above all. Then: what are we being asked to decide? What do we recommend? What will it cost, in money and in attention? What are the risks, honestly, including the one we are most reluctant to name? What alternatives did we weigh, and why did they lose? And what happens if we do nothing - because doing nothing is always an option, and a plan that cannot beat it has not earned the meeting.

That is the whole plan. Everything else an organisation later produces - the board deck, the executive summary, the project brief, the stakeholder note - is an extract from it, cut to fit its audience. The exec summary is not written fresh; it is lifted from the page. The agenda slide is the page’s outcome line, restated. The document is the page with its evidence reattached. Get the page right and every downstream artefact writes itself, consistent with all the others because they share a single source. Get it wrong, and no amount of formatting downstream will hide that the plan was never really made.

Which reframes what the deck and the document are. They are not the thinking. They are the packaging of thinking that was already finished on the page. The analysis - the models, the appendices, the working - sits behind the page, available to anyone who wants to test it, and read by almost no one. That is as it should be. The page is the plan. The rest is evidence.

The difficulty is the point

Here is what makes the page worth the discomfort: it is hard to write. Far harder than the long version.

Anyone can include everything; inclusion requires no decisions. The page requires hundreds of them. Every line that survives is a judgement that something else mattered less, and every omission is a position the author must be prepared to defend. Writing the page is not tidying up after the thinking. It is the last and most demanding stage of the thinking - which is exactly why a finished page is such a reliable signal. It cannot be faked, and it cannot be delegated to formatting.

So what the exercise really measures is not writing. It is clarity of intent. When a plan will not compress to a page, the honest reason is rarely that the subject is too complex. It is that the outcome was never fixed - that the work set off before anyone decided where it was going. The page refuses to resolve until the thinking does, and it is far cheaper to discover that at your own desk than in front of the board.

Put it to the test

Take the plan you are building right now - the proposal you owe someone, the strategy stuck in draft, the initiative that has grown to thirty slides and no verdict. Set the deck aside. Write the page instead, and start at the end: the outcome you are chasing, the needle you intend to move, stated in one line you would be willing to be measured against.

Then work back. The parts you can write in one clean line are the parts you have decided. The parts you get stuck on are the parts you haven't - the outcome you keep softening into an activity, the option you cannot quite rule out, the cost you would rather not put on paper. Each one marks a decision you have not actually made yet. Written forwards in a deck, the volume hides those gaps. Written backwards on a page, there is nowhere to put them but in front of you. So write the page. Find the gaps. Then go and make the decisions the plan has been avoiding.