What a start delivers
A builder-lead engagement of two to three months ends with two things in your hands. The bounded part of the roadmap it shipped, and a written plan for what a pod would deliver next. This is the shape of that plan. It is constructed to show the format and is not a client document.
Why the plan matters
It is the proof a pod needs before it starts. There is work to do, written as deliverables with dates, and the people who would do it have already shipped something of yours. It uses the same grammar as the weekly report, so the person who reads one can read the other. It can be passed up as it is.
There is no amber in it. An item between red and green is red, and the sentence says why.
A sample plan
Constructed. Every bracket is a placeholder for something a real plan takes from your title and your data. No figure here is from any client.
1. The answer in four lines
| Question | Status | One sentence |
|---|---|---|
| Did the slice ship on the dates agreed? | Green | Shipped to cert on the date agreed; one scope change, agreed in writing in week six. |
| Is the work the next slice depends on owned? | Red | Two of the five roadmap items it depends on have no owner on your side and no date. The plan below names them. |
| Where does the risk to the next slice sit? | Named | Telemetry: the data the slice is steered by arrives [n] days after the event it describes. Each decision in the slice is taken that much late. |
| Should a pod take the next slice as planned? | Yes, if | Yes, if decision 1 below is taken before the start date. Without it the pod would spend its first month finding its scope. |
2. What the engagement shipped
| Deliverable | Date agreed | Status | One sentence |
|---|---|---|---|
| [Feature] for the season build | [date] | Green | Delivered to cert; your team ran the release unaided. |
| [System] tooling handover | [date] | Green | Documentation and one supervised run; your producer owns it from [date]. |
| [Change] held for the first patch | [date] | Green | Scope change agreed by [role] on [date]; the season date held. |
3. The slice a pod would own next
Two quarters, written as the contract would state them: a scope description per quarter and deliverables with dates. Nothing on your roadmap that is not in this table is the pod's responsibility, and the table says who on your side owns the rest.
| Deliverable | Date | Who in the pod | Done when |
|---|---|---|---|
| Q[n]: [system] rebalance and the event cadence behind it | [date] | Lead and one senior | Rebalance live; two events run on the new cadence with your team in the loop. |
| Q[n]: [feature] for the next season | [date] | Two seniors | In cert on the date agreed; the first red, if any, named in the report at least four weeks before. |
| Q[n] and Q[n+1]: live operations on the slice | Weekly | Live-ops profile | Events, patches and the data read for the slice, reported every week. |
4. Risks, each with an owner and a date
| Risk | Owner | Decision needed by | If no decision |
|---|---|---|---|
| Telemetry lag of [n] days | Your head of live | [date] | The pod steers by the same late data as everyone else, and the roadmap keeps landing late by that much. |
| Platform certification window for the next season build | Your release manager | [date] | The season date moves by one submission cycle. |
| Two roadmap items with no owner on your side | Your studio director | [date] | They are not in the pod’s slice and stay unowned. |
5. Decisions needed before a pod starts
- Name the owner and the date for the two roadmap items in red above, or take them off the roadmap. Either answer lets the pod’s slice be written; no answer does not.
- Confirm the start date for the pod and who receives the weekly report after your reorganization on [date].
6. What is at stake
A slip of [weeks] on the next season moves [amount] of expected month-one revenue by the same interval. The figures are the title's own, from the last two seasons. The arithmetic is shown once and reused in every weekly report until the data changes.
7. The pod
- Lead
- The same person who led this engagement. Owns scope, priorities and the report to you, and builds hands-on.
- Two seniors
- Named in the proposal; [discipline] and [discipline], working AI-first.
- One live-ops profile
- Named in the proposal; covers live operations on the slice.
Start date: within thirty days of signing, with the items that could move it listed beside it. How an engagement starts.
Constructed sample. A real plan carries your title's own deliverables, dates and figures, and is filed under an engagement code, never under your name.