Flip 360 Commission Platform
PMO learn pack · ADKAR change-management framework

How to operate under PMO governance — get it right first time.

Steerco asked for best-practice instruction in PMO governance. The Prosci ADKAR model is the global standard for getting humans through an operating-model change — used by McKinsey, Accenture, Deloitte and every Tier-1 consultancy on every Tier-1 transformation. This pack walks the five stages, ends with a worked example, and is the artefact Carla refers to in the first two-pair-written fortnights with each Workstream Lead.

Live board Workstream ops Registers Steerco papers Scoping · CRM CRM · truth doc CRM · features map CRM design · Contact 360° Deal room Hardening backlog Learn (ADKAR) Framework
Source Vol 1 Ch 8 · Programme Governance & Cadence  |  Vol 1 Ch 10 · The Future-State PMO  |  Vol 4 Ch 12 · PMO Structure · the six workstreams
A
Awareness
D
Desire
K
Knowledge
A
Ability
R
Reinforcement
A

Awareness

Why PMO discipline exists at all.
Answers: "Why do we need this overhead?"

Flip 360 is not a side project. It is a programme that will, within five years, either flip to a Series A raise of $5–15M, or be acquired, or list on the ASX. The standard of governance has to match the standard of ambition. That is the entire reason PMO discipline exists at all.

Read nine case studies on /the-deal: AirBnB, Uber, WeWork, Theranos, AirTasker, Canva, Afterpay, Atlassian, Zoom. Three patterns:

  • Atlassian, Canva, Afterpay built PMO discipline from day one. The audit trail at IPO was clean. Founders kept control. Multi-billion-dollar outcomes.
  • WeWork, Theranos ran storytelling instead of governance. The audit trail collapsed in due diligence. Founders lost control. Multi-billion-dollar losses.
  • AirBnB, Uber, AirTasker, Zoom bolted PMO on later. Survived — but paid for it in dilution, founder time, and re-papering.

Flip 360 is being built to the Atlassian/Canva/Afterpay standard from day one. That is what this PMO is. That is what these fortnightly Steercos are. That is why your two weeks of work each fortnight have to be captured the right way — so that on the day Mathew sits in the Series A diligence room, every decision since Steerco #1 is traceable to a register entry, every claim is backed by an artefact, and the auditor has zero gaps to ask about.

The PMO answer to "is this overhead?" It's not overhead. It's the only insurance policy against the WeWork and Theranos outcomes. Two hours a fortnight of disciplined reporting is the difference between a clean IPO and a collapsed valuation.
D

Desire

What's in it for Corrina and Mathew personally.
Answers: "Why should I care, personally?"

For Corrina: as WS1 Lead, your fortnightly status report is the single artefact that proves your workstream is in control. When the Series A diligence room asks "who runs the acquisition engine?" Mathew's answer is "Corrina, WS1 Lead — and here are her 13 fortnightly status reports across Phase 1 and Phase 2 BAU." That is the credential. That is what makes you the embedded CMO at exit.

For Mathew: Steerco is the only fortnight where you get the complete state of the programme in one sitting. No back-and-forth Slack threads, no half-remembered conversations, no "I think Carla said something about counsel". One paper. Done · Doing · Next per workstream. RAID escalations. Decisions to sign. Three hours. Then you go back to product strategy and capital raising for the next two weeks knowing exactly what's been resolved and what hasn't.

What you personally walk away with
  • Decision velocity — at Steerco we make decisions, not discuss them
  • Audit trail — at investor diligence, the registers tell your story for you
  • Sleep at night — no Sunday-night panic about what slipped this week
  • Career artefact — 13 fortnightly status reports is a CV item investors recognise
K

Knowledge

What a workstream report contains, with worked example.
Answers: "What am I actually filling out?"

A workstream status report has five sections. Five. No more. Each takes one paragraph or one bullet list. The total artefact is one screen long — readable in under three minutes by everyone at Steerco.

  1. Done — what was committed at the previous Steerco and is now complete. Each bullet references a backlog ID and the evidence (a URL on cosaiflip360.org).
  2. Doing — what's actively being worked this fortnight. The Mon-Sun sprint window. Each item has % complete, owner, and blocker note if any.
  3. Next — what's committed for the next fortnight. Pulled from the backlog into "next-up" status.
  4. RAID — open Risks, Assumptions, Issues, Dependencies attributed to this workstream. Anything Red or Amber that the Steerco needs to act on.
  5. Health — a single colour (Green/Amber/Red) with a one-sentence justification. Honest, not optimistic.

That's it. Five sections. The format is locked so Steerco doesn't have to re-learn the shape every fortnight. Worked example: open Corrina's WS1 live ops page and read the Done / Doing / Next blocks at the top. That's the artefact. That's all you're filling out.

The PMO rule on writing the report Every bullet must point to evidence on cosaiflip360.org. If you can't link a bullet to a URL, a screencast, a D1 row, or a commit SHA — the bullet doesn't go in the report. This is the discipline that turns marketing copy into evidence.
A

Ability

How to actually do it — the worked walkthrough.
Answers: "What do I do step-by-step?"

The walkthrough at /engagement/pmo/learn/walkthrough is a screen-by-screen, click-by-click worked example of what Corrina does every two weeks for her WS1 report. Open it, follow it, copy the pattern.

The TL;DR is six steps:

  1. Open your workstream ops page — for Corrina that's /engagement/pmo/workstream/WS1/ops. This is your home base.
  2. Review what was committed last Steerco — open the previous Steerco paper and find your workstream's "Next" section. Anything still incomplete is amber.
  3. Move backlog items between states — Done items go to "done". In-flight items go to "in-sprint". Next-fortnight items go to "next-up". Blocked items get a "blocked by" link.
  4. Draft your Done · Doing · Next paragraphs — one paragraph each, three bullets max per paragraph, every bullet linked to evidence.
  5. Update your RAID — any new risks, any items now closed.
  6. Set your health colour — Green / Amber / Red with one sentence of honest justification.

Then commit the change. The artefact updates on cosaiflip360.org. Steerco opens the URL the morning of the meeting and reads it. No PDFs. No PowerPoint. No "I'll send it through after". The URL is the report.

First fortnight discipline Carla will pair-write the first two fortnightly reports with each Workstream Lead. The third, the Lead writes solo and Carla reviews. By the fourth, the discipline is internalised. This is deliberate scaffolding — the pattern Atlassian and Canva used for new operating leads.
R

Reinforcement

The cadence that locks the habit in.
Answers: "How do we keep doing this?"

Habits don't form from training. They form from cadence. The PMO has a strict fortnightly Steerco rhythm — six meetings across Phase 1 (8 Jun → 17 Aug 2026), then continuous fortnightly Steercos through Phase 2 BAU. The reinforcement is the cadence itself.

The reinforcement loop:

  • Monday of Steerco week — Carla pings each WS Lead with a 1-line "your report is due Friday 5pm". The URL of the workstream ops page is in the message. Click. Fill. Done.
  • Friday 5pm — every WS Lead's ops page is current. Carla runs the rollup into the Steerco paper. Decisions to be tabled get auto-pulled from the pending decisions register.
  • Steerco morning — Mathew opens cosaiflip360.org, reads the paper, signs the decisions. Carla minutes the resolutions. The decisions register updates immediately.
  • Steerco + 1 — Carla pings each WS Lead with their delta: what got approved, what was deferred, what new items dropped into their backlog as a result. Fortnight starts.

14 days × 6 Steercos × 7 Workstream Leads = 84 disciplined reporting events in Phase 1. That's how the habit forms. Not by being told it's important. By doing it 84 times.

The discipline rule Missed reports don't get accepted with apologies. They get logged as an Issue in the RAID register attributed to the missing WS Lead, with a one-fortnight remediation plan. This is not punitive — it's how you protect the integrity of every other report. The whole programme runs on this.
Now: do it once

Open the worked walkthrough.

A complete, screen-by-screen, click-by-click worked example of what Corrina does every two weeks for her WS1 report — from opening the workstream ops page on a Tuesday morning to committing the updated artefact to cosaiflip360.org by Friday 5pm. The pattern is identical for every other Workstream Lead and identical for every fortnight of Phase 1 and Phase 2.

Open the walkthrough Or jump straight to WS1 live ops