Write a benefits realization plan for a program
Links program outputs to measurable benefits, with baselines, owners, timing, and how benefits will be tracked after delivery.
The prompt
Help me write a benefits realization plan for my program.
Program and its outputs: [WHAT will be delivered - systems, processes, products]
Benefits promised in the business case: [LIST - e.g. "reduce order processing time by 30%", "save $400K a year"]
Current baselines: [today's measures, if known]
Who will own each benefit after the program closes: [business owners]
Program end date and when benefits are expected: [DATES]
Build the plan:
1. Benefits map: output > capability > business change needed > benefit > strategic objective. Make the business change explicit, because outputs alone rarely produce benefits.
2. Benefit profiles for each benefit: description, measure and formula, baseline, target, timing (when it starts and when it reaches full value), data source, owner, and dependencies.
3. Financial vs. non-financial: separate cash-releasing, non-cash efficiency, and qualitative benefits, and avoid counting the same benefit twice.
4. Dis-benefits: negative effects (e.g. temporary productivity dip, higher running costs) to be tracked honestly.
5. Tracking plan: review frequency, who reports, and what happens if a benefit falls behind.
6. Handover: how responsibility moves from the program to business owners at closure.
Rules: do not invent baselines or targets; use [BASELINE NEEDED] and [TARGET TO CONFIRM]. Flag any benefit with no clear measure or owner as at risk.
Return the plan with a benefits register table and a one-paragraph summary for the sponsor.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- WHAT will be delivered - systems, processes, products
- today's measures, if known
- business owners
- DATES
- BASELINE NEEDED
- TARGET TO CONFIRM
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Price and document a change order before doing extra workA change order with cost breakdown, schedule impact, and justification that the owner or GC can approve quickly.
- Write an after-action report and improvement planAn after-action report that rates performance against each objective, finds root causes, and produces a tracked improvement plan.
- Write a control plan for a production processA control plan that turns my product and process characteristics into what to check, how, how often, and what to do when it fails.
- Prepare a PPAP submission package for my customerA checklist of every PPAP element at my submission level, the status of each, and a plan to close gaps before the due date.