Module: Executive Command Centre
Source: Jira Epic GOV-E4 — "One aggregate, four role layouts; KPIs, trend, coverage, board pack". Generated per LEARN-STD-002 from authoritative artefacts: the Epic is this module, its Stories are the lessons, and each Story's acceptance criteria are the lessons' learning outcomes and knowledge checks.
The story of this journey
The Command Centre is one aggregate rendered four ways — the same governed truth shaped for the Governance Lead, Executive Sponsor, System Owner, and Auditor — culminating in a signed board pack.
Who this is for
Primary: Product Manager. Also relevant to: CTO / CIO, Auditor / Compliance Officer, Platform Administrator.
Flow
Lessons (in sequence)
| # | Lesson (source Story) | Pts | Why it matters |
|---|---|---|---|
| 1 | GOV-140 — Role-shaped aggregate endpoint | 8 | Four dashboards from one source keeps everyone on the same truth. |
| 2 | GOV-141 — Governance Lead operating console | 8 | The Lead drives the programme; the console surfaces what needs action. |
| 3 | GOV-142 — Executive Sponsor altitude dashboard and sign-off | 5 | Executives approve, they don't edit tasks; sign-off must be attributable. |
| 4 | GOV-143 — System Owner scoped dashboard | 5 | Owners need their slice and a fast path to act. |
| 5 | GOV-144 — Auditor read-only trail and export | 5 | Auditor independence requires zero write access and verifiable evidence. |
| 6 | GOV-145 — Signed board pack | 5 | Boards need a defensible, point-in-time snapshot they can trust. |
How this maps (LEARN-STD-002)
- Epic GOV-E4 → this Module.
- Each Story → a Lesson (
source_artifact: jira_story), sequenced byprerequisites. - Acceptance Criteria → learning outcomes + scenario knowledge checks — quoted, not paraphrased.
Assessment & certification
Passing all 6 scenario knowledge checks completes the module. Certification (learner-progress store) is deferred to Phase 3; until then completion is tracked informally and no metrics are fabricated.