1 · What they claim — one thread

The central diagnosis, quoted: the findings "are not separate problems — they are different manifestations of a single architectural condition… the organisation has evolved faster than its enterprise architecture."

The sharpest line: "acquiring an application in response to each business requirement has not improved capability and has made the underlying position worse."

Investment vs need: $84.7M across 81 initiatives, Modern ERP $65.5M. ~99% of capability-aligned spend sits in asset delivery, while Data & Information, Strategy/Planning and Review/Risk carry 84% of documented need and ~1% of the spend. Process maturity averages ~1.8 on CMMI; several core capabilities score 0.

Where it lands: this is now "a design and sequencing exercise rather than a strategy exercise." Readiness Report verdict: Proceed with Conditions · high confidence · "strategy ready, capacity constrained" (Leadership/Governance/Business HIGH; Technology MODERATE; Information & Change DEVELOPING).

2 · Where the endorsement risk sits

Analytically finished — the insight boxes are full prose, not placeholders. Unfinished is sign-off, and that's the live risk this phase.

• Not approved. Cherie Davis and Heath Williams both read "To be added"; PWG endorsement is a placeholder; Addendum A is "0.3 Draft, SME endorsement pending." Findings can't feed board/funding decisions until SME validation + governance endorsement land.
• Everything is "derived and indicative" — mixed-confidence rules-based mappings, "presented to make the current state legible and challengeable rather than final." Lowest confidence: asset-class alignment 30%, capability-maturity data 35%.
• Two fault lines: RAID R4 is "manage the ICT-vs-business focus"; R18 is "depth of analysis is too deep."

3 · Where you add value fastest

The CSA lists what it left undone — that's your backlog. Highest-leverage, lowest-politics first:

• The reconciliations it calls prerequisites: map information-asset ownership (currently by org unit) to the capability model; give the 159 apps missing an L1/L2 a capability assignment; chase the 20 unknown owners. "A prerequisite for enterprise information governance."
• The data-remediation backlog: the 6 unclassified + 4 unrated assets, and those that are mission-critical, hold PII, and sit below required quality.
• The off-system/manual-process inventory Stage 2 explicitly wants (hazmat/asbestos obligations, off-system work assignment, EAM↔Finance asset creation) — nobody's done it, and your elicitation background is the tool.
• Extend the integration register — the 10 unrecorded systems and the ~third of interfaces with no recorded payload — a precondition for the S/4HANA cutover.
• Re-weight the "need" data and split out the EAM share of Modern ERP so the investment argument survives a board. The most board-visible fix on the list.

Low-effort early credibility: it's a to-be-approved document with visible typos ("KEY SIGHTS" for KEY INSIGHTS, a stray date). Flagging those quietly in review gets noticed.

4 · This is your Level-Up Cycle 1, made real

Cycle 1 — Current State & Systems — with the mock clinic swapped for the live case. Pick one well-evidenced asset class (pavements or fleet) and write your five-lens note straight off the CSA. The reading lands with force: the CSA's own thesis (one architectural condition, fragmentation reproducing itself) is Senge almost verbatim, and the apps-up-capability-flat finding is textbook local optimisation — busy, not capable — out of Goldratt. Boss-fight spine: the operating-system map, with r = +0.74 as the punchline.

→ Development · Cycle 1 · → Live Tracker · → Orientation Hub