The job of this console
Read the pack for steering, click through to fix red items, return. Do not maintain RAG only in slides.
Projects · Governance
Governance
Steering pack: RAG across milestones, risks, issues — composed from those registers, not a slide deck as source.
Scroll to Flowcharts. Scenario: Run a governance pack from live RAID.
Steering pack
RAG assembled from RAID you already keep
Governance composes milestones, risks, and issues into a pack. It is not a third copy of the RAID log.
Projects → Governance
Route
/project/governance
Org flag governanceEnabled
Project Manager · Executive · Admin
Seat at the table
PMs, executives, admins. Contributors update tasks; they may not own the pack.
The working rhythm
Open pack, drill red, fix child register, refresh.
Moments that bring you here
Steering committee. Audit. After a red risk. Month-end delivery review.
ⓘ
Composed view
Writers are milestones, risks, issues (and related). Portfolio is the multi-project tower.
Flowcharts
1 — Pack then fix sources
Read RAG, open the red register, correct it.
flowchart TD
A[Open Governance] --> B[Read RAG]
B --> C{Red area?}
C -->|Milestone| D[Milestones]
C -->|Risk| E[Risks]
C -->|Issue| F[Issues]
D --> G[Pack refreshes]
E --> G
F --> G
- 1OpenProjects → Governance.
- 2ReadComposed RAG.
- 3Fix sourceMilestone, risk, or issue.
- 4RefreshPack follows.
Overview
Governance is the pack. Child consoles are the writers. Portfolio is multi-project. NPD gates are product process.
How to use
1. Composed, not typed
Change RAID, not a fake RAG cell if the product computes it.
2. Exec time
Keep comments on the records.
3. Sign-off
Use whatever the product stores — not email as the only approval.