A$60–120 million programme funding · Fictional case · Months from programme start
Rules-based prototype · No live AI
NORTH STARReduce average case handling time by 30%
ORIGINAL FUNDINGA$120m
ORIGINAL TARGETMonth 36
Illustrative case, not live client data. Explore the overview, change a constraint, then record a response. No connection to the working spreadsheet or AI services.
Organisation-wide target. Baseline and realised benefit are not measured in this case.
Hypothesis · Evidence neededFUNDINGPlanning envelope · Not actual spendDELIVERYCalculated estimate · Not a forecast
REQUIRES ATTENTION
What has changed?
EVIDENCE TO REQUEST
What would improve confidence?
Service owner: measured handling-time baseline.
Finance lead: validated costs and funding authority.
Data lead: readiness and quality assessment.
Change lead: adoption capacity and benefit measures.
Suggested roles only; no requests have been sent.
DECISION LOG
No provisional decisions recorded
Records remain in this page session only. Download each record to keep it; leaving or reloading clears the log. Recording does not approve funding or change the north star.
Decision workspace
02 / Compare possible responses
Benefits are hypotheses
Follow the dependency
Full and phased delivery share the same core sequence. A late data foundation moves the earliest operational delivery date.
Inspect the model and its assumptions
Full scope: data A$25m + workflow A$45m + adoption A$20m + analytics A$30m = A$120m. Hypothesised handling-time reduction: 30%.
Phase analytics: commit A$90m to the core service change. Defer A$30m of analytics; total scope remains A$120m before any re-estimation. First-phase benefit hypothesis: 25%.
Focused pilot: bounded first tranche of A$8m (data A$2m, workflow A$4m, adoption A$2m). Hypothesised 12% reduction within one team. Wider rollout cost and impact are unknown; unused programme funding is not a saving.
Timing: data 9 months plus delay, then workflow 18 months and adoption 6 months. Full and phased delivery take 33 months plus delay. Analytics runs for 12 months after data, in parallel. Pilot: limited data 3 months plus the same delay, workflow 6 months, adoption 3 months = 12 months plus delay.
Model boundaries: no contingency, inflation, cost of delay, resource contention or delivery uncertainty is included. Costs are fixed scope estimates. Finishing by the deadline does not demonstrate benefits.
Evidence needed: a measured handling-time baseline, validated effort and cost estimates, a data quality assessment and an adoption capacity check. None is available in this fictional case.
03 / Record a provisional decision
Select an option above to start a decision record.