Revision 7T · Full Tutorial Edition · Updated 1 September 2026
PWR-120 · SELF GUIDED full tutorial
Backcast a fictional project, expose dependencies and rehearse one disruption
Strategic planning links a legitimate goal with milestones, assumptions, dependencies, resources, contingencies, execution and review. A polished plan is not the outcome. This lesson uses a fictional community-room open day and stops before real implementation. The learner works backwards, marks assumptions, assigns trigger-based contingencies, rehearses one disruption and states who could approve, change or retire the plan.
What you will produceThe learner creates a fictional strategy with a measurable outcome, backward milestones, dependencies, assumptions, one disruption rehearsal, review triggers and a retirement rule.
Full step-by-step individual tutorial · TLU-PWR-120
The learner creates a fictional strategy with a measurable outcome, backward milestones, dependencies, assumptions, one disruption rehearsal, review triggers and a retirement rule.
Plan supplied fictional or learner-owned inconsequential projects.
Record affected roles and limits of personal authority.
Qualified help is required for
Real organisational, clinical, political, security, employment or high-resource strategy.
Plans affecting communities or other people without legitimate participation and approval.
Never do this from the page alone
Rehearse coercion, competition, surveillance or harm against real people.
Treat plan quality as evidence of execution, legitimacy or impact.
2 · Get ready
Gather what you need and check the starting conditions
What you need
Exact fictional open-day brief: Friday 15:00 event for 40 visitors; room manager owns the plan; £300 ceiling; four volunteers; 40 chairs; step-free entry and a 1.2 m clear path are hard constraints. Ground-floor room confirmation is due Wednesday 12:00; the two-hour accessible-layout check ends Thursday 10:00; the one-hour volunteer briefing ends Thursday 16:00; baseline printing arrives Friday 10:00, material staging takes three hours, and final setup takes two hours and requires staged materials plus briefing. Thus printing→staging→setup exactly fills Friday 10:00–15:00 and has zero slack. Disruption cards: lift unavailable, two volunteers withdraw, or printing arrives Friday 14:30.
Backward milestone sheet, dependency map, assumption log and trigger table.
A timing worksheet with planned start, duration, earliest finish, required finish, latest start and slack. For this fixed-clock fixture, calculate earliest finish = planned start + duration, latest start = required finish − duration, and slack = latest start − planned start; a zero-slack predecessor moves the event deadline if it slips.
Version and outcome-review record.
Before you start
Mark the fixture fictional and name the legitimate owner supplied by the case.
State the intended outcome, affected roles and hard access/safety constraints.
Set a planning horizon and stop before real outreach, spending or implementation.
3 · The method
Follow these steps in order
Define outcome and legitimacy
Write a measurable fictional outcome, deadline, owner, affected roles and non-goals.
Why: A goal can be clear yet illegitimate or overbroad.
Check: The outcome includes who authorises it and what is excluded.
Backcast milestones
Start at the deadline and work backwards through the minimum observable milestones needed.
Why: Backward planning exposes prerequisites that forward wish lists miss.
Check: Every milestone has a latest completion point and evidence.
Map dependencies and resources
For each milestone, name people, permission, material, information and predecessor tasks it relies on.
Why: Plans fail at interfaces and missing resources, not just intentions.
Check: Every critical milestone has at least one dependency and resource.
Find the critical sequence
Fill the timing worksheet from the Friday 15:00 event backwards. For each task compute earliest finish from its planned start and duration, latest start from the successor's required time minus duration, then slack as latest start minus planned start. Trace the connected zero-slack tasks as the critical sequence.
Why: A list of deadlines does not show which delay actually controls delivery.
Check: The sheet shows printing 10:00–10:00, staging 10:00–13:00 and setup 13:00–15:00 as a five-hour Friday chain with zero slack, while non-critical timing margins are written separately.
Specify each handoff
For every critical transition, name who produces what, who receives it, the acceptance check and what happens when the handoff is late or incomplete.
Why: Many strategies fail between tasks even when each task appears assigned.
Check: The critical chain contains no anonymous handoff, and each receiver has an observable acceptance rule.
Expose assumptions
Write what must be true, how uncertain it is and what observation would test it.
Why: Invisible assumptions become surprise failures.
Check: The three highest-risk assumptions have tests or review dates.
Build trigger contingencies
For each major failure branch, write an observable trigger, fallback action, decision owner and communication route.
Why: A contingency is useful only when its activation rule is clear.
Check: At least two branches have trigger, action, owner and notice.
Rehearse one disruption
Draw a supplied disruption card, walk the plan from that point and record delays, harms, excluded people and new dependencies.
Why: A rehearsal tests adaptability without real-world consequences.
Check: The revised version shows exactly what changed and why.
Separate execution and retire
List the direct outcome measures, burdens and harms that would be checked during execution, plus a rule for pausing or retiring the plan.
Why: Plan coherence cannot substitute for observed implementation.
Check: The final page distinguishes plan-quality checks from outcome checks.
4 · Worked example
See the whole method used once
Scenario
A fictional community room plans an open day for 40 visitors, with step-free access and a £300 resource ceiling.
Walkthrough
Sofia writes the fictional manager as owner, 40 accessible places as outcome and no real booking as a non-goal.
Working backward from Friday 15:00, she places two-hour setup at 13:00–15:00 and three-hour staging at 10:00–13:00 because setup cannot start until staging ends.
Printing arrives at 10:00, so latest start equals planned start for all three Friday tasks: 15:00 minus two hours gives 13:00 for setup, then 13:00 minus three hours gives 10:00 for staging; slack is zero at both handoffs.
She records the Thursday 16:00 briefing as a setup predecessor with 21 elapsed hours before Friday 13:00, but does not transfer that margin to the separate printing chain.
The printing-14:30 card leaves only 30 minutes before the event although staging plus setup still needs five hours. She marks the original outcome infeasible rather than compressing the 1.2 m access check or pretending parallel work removes a dependency.
Her trigger row says ‘printing absent Friday 10:00 → notify room manager → use a pre-authorised no-print paper fixture if one exists; otherwise retire the open-day version.’ The fictional manager, not Sofia, owns that scope decision.
She keeps the baseline schedule beside the disrupted version and records missed deadline, protected access constraint and owner decision as separate fields.
Result
The calculation exposes a five-hour requirement against a 30-minute window, so Sofia can explain exactly why the original Friday plan must change or retire. The exercise has not implemented an event or demonstrated strategic impact.
5 · Right and wrong
Compare correct or safer execution with the common wrong version
Right and wrong comparison
Moment
Right / safer
Wrong / riskier
Why it matters
Goal
Name owner, affected roles and non-goals.
Optimise attendance without asking who has authority or access.
A clear metric can still encode an illegitimate goal.
Milestone
Attach evidence and deadline.
Write “prepare logistics.”
Vague activity cannot be tracked or backcast.
Contingency
Use an observable trigger and named owner.
Say “be flexible if things go wrong.”
Unspecified flexibility arrives too late.
Evaluation
Measure execution, outcome, burden and harm.
Declare success because the plan document is complete.
Planning quality is not implementation or impact.
6 · Common mistakes
Spot the error and apply the correction
Common mistakes and corrections
Mistake
Fix
Assumptions are written as facts.
Move uncertain dependencies to the assumption log with a test.
Every task is called critical.
Mark only tasks that change the deadline or protected constraint.
Fallback harms the excluded group.
Run each contingency through affected-role and access checks.
The old plan is overwritten.
Keep version number, disruption, author and change reason.
7 · Practice
Turn the steps into a usable skill
First session
Frame Friday 15:00, 40 accessible places, £300, the room manager and the no-booking boundary.
Backcast room confirmation, layout check, volunteer briefing and material staging from their supplied deadlines.
Draw predecessors, four-volunteer and room dependencies; mark the critical sequence and any genuine slack.
Write trigger–fallback–owner–notice rows for lift loss and volunteer withdrawal without weakening the 1.2 m path.
Draw one disruption card, update the dated version and test whether the Friday 15:00 outcome must hold, change or retire.
Repeat plan
Use three different fictional project briefs over three weeks. On the final week, another learner draws the disruption card and audits whether the trigger, authority and protected constraints survive.
Progress when
Milestones are observable and correctly ordered.
High-risk assumptions have tests or holds.
A disruption produces a traceable revision without violating protected constraints.
Do not progress when
The plan affects real people, funds or institutional action.
Stakeholder labels substitute for actual participation.
The learner cannot name a pause or retirement condition.
8 · Check the result
Measure what changed
Audit completeness and disruption response of one fictional strategic plan.
How: Audit goal legitimacy, milestones, dependencies, resources, assumptions, tests, contingencies, triggers, owners, communication, outcome measures, harms and retirement rule. Separately verify every timing row by recomputing earliest finish, latest start and slack; a dependency or arithmetic error is corrected before the disruption is interpreted.
Good result: All 13 features are present and a supplied disruption leads to a consistent versioned adaptation without breaching a protected constraint.
This does not prove: It does not show implementation, causal impact, leadership ability or legitimate authority over a real system.
Self-check
Can you name the fictional room manager, Friday 15:00 deadline, 40-place outcome, £300 ceiling and 1.2 m access constraint?
Which predecessor must finish before Thursday’s layout check, and which delay would move the Friday event rather than consume slack?
When the lift-unavailable card appears, does the plan select an accessible ground-floor room or retire instead of asking visitors to cope?
Who receives the late-material notice at 14:30, what acceptance check remains, and which retirement trigger prevents an untraceable last-minute workaround?
9 · Stop, adapt or get help
Keep the safety boundary practical
Stop and get help
Stop before any real spending, outreach, staffing, surveillance or operational action.
Stop if a real affected group is represented without participation or a protected right is traded away.
Seek accountable organisational, legal, safety and affected-person review before a real strategy.
Accessibility and adaptations
Use a linear milestone table instead of a network diagram.
Offer easy-read task cards, icons and a narrated dependency review.
Build access needs into hard constraints rather than treating them as late accommodations.
10 · Evidence and limits
Why these instructions are here
primary research
In an obstetric simulation programme, only 58.8% of local strategic goals were achieved and achievement was not associated with knowledge, self-efficacy or teamwork scores.
Progress is saved only in this browser on this device.
Step-by-step learner mode
Each activity includes its success check, a nearby accessible alternative and an “I’m stuck” correction path. Alternatives preserve the target where possible; when they change the task, Titan labels them as related rather than equivalent.
01
Define outcome and legitimacy
Write a measurable fictional outcome, deadline, owner, affected roles and non-goals.
Why this step exists
A goal can be clear yet illegitimate or overbroad.
Success check
The outcome includes who authorises it and what is excluded.
I’m stuck on this step
Reset: Re-read this authored instruction — “Write a measurable fictional outcome, deadline, owner, affected roles and non-goals.” — and its success check, then attempt only this step.
Possible snag: The result from “Write a measurable fictional outcome, deadline, owner, affected roles and non-goals.” does not yet meet this declared check: The outcome includes who authorises it and what is excluded.
Correction: Return to the start of “Define outcome and legitimacy”, reduce complexity or pace, and repeat only the part needed to satisfy: “The outcome includes who authorises it and what is excluded.”
Stop / get help: Stop before any real spending, outreach, staffing, surveillance or operational action.
02
Backcast milestones
Start at the deadline and work backwards through the minimum observable milestones needed.
Why this step exists
Backward planning exposes prerequisites that forward wish lists miss.
Success check
Every milestone has a latest completion point and evidence.
I’m stuck on this step
Reset: Re-read this authored instruction — “Start at the deadline and work backwards through the minimum observable milestones needed.” — and its success check, then attempt only this step.
Possible snag: The result from “Start at the deadline and work backwards through the minimum observable milestones needed.” does not yet meet this declared check: Every milestone has a latest completion point and evidence.
Correction: Return to the start of “Backcast milestones”, reduce complexity or pace, and repeat only the part needed to satisfy: “Every milestone has a latest completion point and evidence.”
Stop / get help: Stop before any real spending, outreach, staffing, surveillance or operational action.
03
Map dependencies and resources
For each milestone, name people, permission, material, information and predecessor tasks it relies on.
Why this step exists
Plans fail at interfaces and missing resources, not just intentions.
Success check
Every critical milestone has at least one dependency and resource.
I’m stuck on this step
Reset: Re-read this authored instruction — “For each milestone, name people, permission, material, information and predecessor tasks it relies on.” — and its success check, then attempt only this step.
Possible snag: The result from “For each milestone, name people, permission, material, information and predecessor tasks it relies on.” does not yet meet this declared check: Every critical milestone has at least one dependency and resource.
Correction: Return to the start of “Map dependencies and resources”, reduce complexity or pace, and repeat only the part needed to satisfy: “Every critical milestone has at least one dependency and resource.”
Stop / get help: Stop before any real spending, outreach, staffing, surveillance or operational action.
04
Find the critical sequence
Fill the timing worksheet from the Friday 15:00 event backwards. For each task compute earliest finish from its planned start and duration, latest start from the successor's required time minus duration, then slack as latest start minus planned start. Trace the connected zero-slack tasks as the critical sequence.
Why this step exists
A list of deadlines does not show which delay actually controls delivery.
Success check
The sheet shows printing 10:00–10:00, staging 10:00–13:00 and setup 13:00–15:00 as a five-hour Friday chain with zero slack, while non-critical timing margins are written separately.
I’m stuck on this step
Reset: Re-read this authored instruction — “Fill the timing worksheet from the Friday 15:00 event backwards. For each task compute earliest finish from its planned start and duration, latest start from the successor's required time minus duration, then slack as latest start minus planned start. Trace the connected zero-slack tasks as the critical sequence.” — and its success check, then attempt only this step.
Possible snag: Every task is called critical.
Correction: Mark only tasks that change the deadline or protected constraint.
Stop / get help: Stop before any real spending, outreach, staffing, surveillance or operational action.
05
Specify each handoff
For every critical transition, name who produces what, who receives it, the acceptance check and what happens when the handoff is late or incomplete.
Why this step exists
Many strategies fail between tasks even when each task appears assigned.
Success check
The critical chain contains no anonymous handoff, and each receiver has an observable acceptance rule.
I’m stuck on this step
Reset: Re-read this authored instruction — “For every critical transition, name who produces what, who receives it, the acceptance check and what happens when the handoff is late or incomplete.” — and its success check, then attempt only this step.
Possible snag: The result from “For every critical transition, name who produces what, who receives it, the acceptance check and what happens when the handoff is late or incomplete.” does not yet meet this declared check: The critical chain contains no anonymous handoff, and each receiver has an observable acceptance rule.
Correction: Return to the start of “Specify each handoff”, reduce complexity or pace, and repeat only the part needed to satisfy: “The critical chain contains no anonymous handoff, and each receiver has an observable acceptance rule.”
Stop / get help: Stop before any real spending, outreach, staffing, surveillance or operational action.
06
Expose assumptions
Write what must be true, how uncertain it is and what observation would test it.
Why this step exists
Invisible assumptions become surprise failures.
Success check
The three highest-risk assumptions have tests or review dates.
I’m stuck on this step
Reset: Re-read this authored instruction — “Write what must be true, how uncertain it is and what observation would test it.” — and its success check, then attempt only this step.
Possible snag: Assumptions are written as facts.
Correction: Move uncertain dependencies to the assumption log with a test.
Stop / get help: Stop before any real spending, outreach, staffing, surveillance or operational action.
07
Build trigger contingencies
For each major failure branch, write an observable trigger, fallback action, decision owner and communication route.
Why this step exists
A contingency is useful only when its activation rule is clear.
Success check
At least two branches have trigger, action, owner and notice.
I’m stuck on this step
Reset: Re-read this authored instruction — “For each major failure branch, write an observable trigger, fallback action, decision owner and communication route.” — and its success check, then attempt only this step.
Possible snag: Fallback harms the excluded group.
Correction: Run each contingency through affected-role and access checks.
Stop / get help: Stop before any real spending, outreach, staffing, surveillance or operational action.
08
Rehearse one disruption
Draw a supplied disruption card, walk the plan from that point and record delays, harms, excluded people and new dependencies.
Why this step exists
A rehearsal tests adaptability without real-world consequences.
Success check
The revised version shows exactly what changed and why.
I’m stuck on this step
Reset: Re-read this authored instruction — “Draw a supplied disruption card, walk the plan from that point and record delays, harms, excluded people and new dependencies.” — and its success check, then attempt only this step.
Possible snag: The old plan is overwritten.
Correction: Keep version number, disruption, author and change reason.
Stop / get help: Stop before any real spending, outreach, staffing, surveillance or operational action.
09
Separate execution and retire
List the direct outcome measures, burdens and harms that would be checked during execution, plus a rule for pausing or retiring the plan.
Why this step exists
Plan coherence cannot substitute for observed implementation.
Success check
The final page distinguishes plan-quality checks from outcome checks.
I’m stuck on this step
Reset: Re-read this authored instruction — “List the direct outcome measures, burdens and harms that would be checked during execution, plus a rule for pausing or retiring the plan.” — and its success check, then attempt only this step.
Possible snag: The result from “List the direct outcome measures, burdens and harms that would be checked during execution, plus a rule for pausing or retiring the plan.” does not yet meet this declared check: The final page distinguishes plan-quality checks from outcome checks.
Correction: Return to the start of “Separate execution and retire”, reduce complexity or pace, and repeat only the part needed to satisfy: “The final page distinguishes plan-quality checks from outcome checks.”
Stop / get help: Stop before any real spending, outreach, staffing, surveillance or operational action.
Correct versus incorrect execution
These accessible process diagrams are built from the tutorial’s own right/wrong teaching. They are not anatomical illustrations and do not add technique beyond the canonical tutorial.
Goal — A clear metric can still encode an illegitimate goal.
Correct / safer
Name owner, affected roles and non-goals.
Wrong / riskier
Optimise attendance without asking who has authority or access.
Milestone — Vague activity cannot be tracked or backcast.
Correct / safer
Attach evidence and deadline.
Wrong / riskier
Write “prepare logistics.”
Contingency — Unspecified flexibility arrives too late.
Correct / safer
Use an observable trigger and named owner.
Wrong / riskier
Say “be flexible if things go wrong.”
Evaluation — Planning quality is not implementation or impact.
Correct / safer
Measure execution, outcome, burden and harm.
Wrong / riskier
Declare success because the plan document is complete.
Method-structure checklist
10 of 10 structural checks present
✓ Ordered, Power-specific instructions — present
✓ Every activity has a success check — present
✓ Materials or supplied records are declared — present
✓ Measurement or assessment rule is present — present
✓ Tutorial-specific troubleshooting is present — present
✓ Stopping or escalation boundary is present — present
✓ Every activity has an adjacent alternative — present
✓ Correct-versus-incorrect comparison is present — present
✓ Evidence context is bound to the Power record — present
✓ Planning metadata is present — present
The method-readiness band and presence checklist assess tutorial presentation and are separate from evidence quality for the underlying Power. They are automated editorial aids, not human approval.
Manual editorial sign-off: Pending. This tutorial must not display a human-approved state until an identified editor signs the exact content hash.