Phase two shouldn't cost what phase one did

A developer completes a successful first phase, moves to the second, and quietly starts over. New vendor search, new timeline built from nothing, new decisions made about questions that were already answered eighteen months earlier. The second launch takes nearly as long and costs nearly as much as the first.

This is rarely a competence problem. It happens because the first launch was never documented while it was happening, and the people who held the sequence in their heads have moved on to other projects — or out of the company.

Lead time is the real cost

The money spent re-procuring is visible and measurable. The lead time is neither, and it is larger. Months between the decision to launch and the ability to open sales are months of carrying cost against no revenue, and they are almost entirely avoidable.

Most of that time is not spent doing work. It is spent making decisions that have already been made once: which agency, what scope, what the approval thresholds are, when the show suite has to be finished relative to opening, who signs off on pricing.

The second launch should be an execution problem. If it is still a decision problem, nothing from the first one was captured.

What belongs in a playbook

A phase playbook is an operating document, not a case study. Written properly it should be usable by someone who was not present for the first phase:

• The launch calendar as a template, with real durations from what actually happened
• A vendor roster with pre-negotiated scopes and the contacts attached
• An asset checklist covering everything that had to exist before opening
• Approval thresholds and who holds them
• The reporting cadence and format, including who receives what and when
• A record of what went wrong and the decision that resolved it

That last item is the one most often skipped and most often needed. The value is not in the successes — those repeat naturally. It is in the two or three problems that consumed weeks, so they consume hours next time.

Write it during, or reconstruct it after

The cheapest version is written while phase one is running, by someone whose job includes writing it. Nobody does this, because during a launch every hour has a more urgent claim on it.

The realistic alternative is to reconstruct it immediately after the phase closes, while the people are still available and the calendar entries still exist. It takes a few weeks and it is worth doing even if phase two is a year out — particularly then, because a year is long enough for the details to disappear.

The test

Hand the document to someone in the business who was not involved and ask them to describe what happens in week six. If they can, the playbook works. If they need to ask someone, you have written a summary rather than an operating document, and phase three will cost what phase one did.