Fictional Case Study: Recovering a Delayed Training Launch

Fictional learning scenario

This is an original RDE teaching case. The organisation, records, observations and outcomes are invented for learning. It is not a client case, testimonial or report of real results.

Context and decision to make

A fictional team plans an online training launch in ten working days. The status board shows most cards completed, but the registration journey and welcome pack are not ready. The sponsor asks whether the advertised date can still be met.

Evidence available in the scenario

The scenario begins on working day 1. The remaining tasks are: approve course copy, two days; configure registration after that approval, two days; test registration after configuration, two days; assemble the welcome pack, two days in parallel; and complete a final readiness review after testing and the pack, one day. Estimates are invented and assume the named people are available. A previous draft plan counted only configuration and ignored its prerequisites.

Approach and interpretation

The project manager redraws the remaining sequence and asks each owner to confirm the handover and evidence of completion. The copy-to-registration-to-test-to-review chain takes seven working days if started immediately. The welcome pack can finish earlier without shortening that chain. A completed design card does not remove the need to test the actual registration flow.

Options and decision

The sponsor considers three options: add optional launch features; open registration without testing; or freeze optional scope and protect the seven-day readiness sequence. The sponsor chooses the third. Course copy has a named approver, testing has a protected slot and any missed handover triggers a same-day sponsor decision. Opening untested registration is rejected because it would conceal the main uncertainty rather than remove it.

Outcome within the fictional scenario

In the fictional outcome, copy approval finishes at the end of day 2, configuration at the end of day 4 and testing at the end of day 6. The pack finishes on day 3. The day 7 review finds a broken confirmation link and withholds readiness. The fix and retest take day 8, leaving days 9 and 10 available before the planned launch. Optional reminder automation remains deferred and is recorded in the follow-up plan.

Limitations and next checks

The original launch date is retained in this scenario, with readiness approved only after the link is retested. The result depends on the assumed availability and task estimates. It is not evidence that every delayed launch can be recovered in eight days. If the correction had exceeded the remaining time, the sponsor would have needed to change the date or scope explicitly.

Apply the case

Allow about 20 minutes. Identify the decision, extract the evidence and write down one assumption that needs checking. Separate the observed or stipulated figures from the explanation proposed by the team.

1. What would the seven-day sequence hide if staff were unavailable?
2. Why does completion of the welcome pack not shorten the registration chain?
3. Which evidence should the sponsor require before approving readiness?

Check your learning

Report the remaining dependency chain and readiness evidence. A busy board or a high completion percentage cannot establish that the launch is safe to proceed.

A useful response names the unit being measured, tests the proposed explanation against the available evidence and proposes a next check that could change the decision. Avoid claiming a general result from the small fictional sample.

Use and attribution

Original educational scenario by Jefferson Otonbara Imgbi. Version 1.0, 8 October 2026. No real customer records, organisation identities or endorsements are used. Personal and internal organisational learning use permitted with author credit retained.

Further reading on the method

These sources provide general method guidance. They are not sources for the invented organisations, figures or outcomes in this case.

APM: project planning

Cover image: AI-generated illustrative scene created specifically for this resource.