Milestone map
3 milestones
Map current governance structure and identify execution gaps
3 weeks
Map the current governance structure of the organisation or team — decision rights, escalation paths, accountability assignments, and reporting lines — and identify at least three specific gaps where governance decisions are not being executed as intended. Gaps may include: decisions made at the wrong level, accountability assigned to a role that lacks the authority to execute it, escalation paths that bypass the intended decision-makers, or governance outputs (board resolutions, committee decisions) that do not translate into operational action.
Proof required
Submit a governance map (diagram or table) showing the current decision rights and reporting lines, and a written analysis of at least 500 words identifying three specific governance execution gaps. Each gap must be described with: what governance mechanism was designed to do, what is actually happening in practice, and the operational impact of the gap. ADVERSARIAL VERIFICATION: a named governance, legal, or senior operations professional (5+ years experience in governance or board-level work) must read the map and analysis and provide written confirmation that the gaps identified are substantive execution failures, not just aspirational improvements.
What gets checked
Common mistakes
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
You'll sign in first, then come straight back here.
Design and implement governance execution improvements
8 weeks
Design and implement interventions to address at least two of the three governance execution gaps identified in M1. Interventions may include: clarifying accountability assignments, creating decision logs that are distributed to operational leads, redesigning escalation pathways, establishing a governance-to-operations translation mechanism (who receives governance outputs and is accountable for implementing them), or running a governance effectiveness review session. Each intervention must be documented before implementation and measured for 6–8 weeks after.
Proof required
Submit a governance execution improvement report covering: (1) the two interventions designed and the governance execution gaps they address; (2) evidence that each intervention was implemented (a resolution, email, policy update, or process change, with date); (3) evidence of operation under the new governance arrangement for at least 6 weeks (meeting notes, decision logs, updated accountability matrix, or equivalent). ADVERSARIAL VERIFICATION: your named governance reviewer reads the intervention design before implementation and provides written feedback confirming the interventions address the execution mechanism rather than creating new documentation that will also not be followed.
What gets checked
Common mistakes
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
You'll sign in first, then come straight back here.
Present governance improvement outcomes with practitioner challenge
2 weeks
Compile a governance execution improvement report covering the M1 gap analysis, M2 intervention results, and a forward recommendation covering which governance execution gaps remain and what a next improvement cycle should address. Present the report in a live session of at least 30 minutes to a panel that includes your named governance reviewer plus at least one additional governance, legal, or board-level professional. The panel poses adversarial challenges on your causal claims, your measurement approach, and the sustainability of the improvements.
Proof required
Submit your governance execution improvement report and a record of the challenge session: names and professional roles of all panellists (≥2), date and duration (≥30 minutes), and notes on at least three challenges posed and your responses. A written statement from the primary governance reviewer (50+ words) confirming that the improvements represent genuine execution changes rather than documentation additions. ADVERSARIAL VERIFICATION RULE Level 2: live session required.
What gets checked
Common mistakes
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
You'll sign in first, then come straight back here.