What Corrina does every two weeks — step by step.
An 8-step worked walkthrough of the fortnightly WS1 status report — from Carla's Monday-morning ping through to Mathew reading it on Steerco morning. This is exactly the pattern every Workstream Lead follows every fortnight — for the next 13 fortnights of Phase 1, and for every fortnight of Phase 2 BAU.
The walkthrough follows Corrina across one full fortnight: Monday-of-Steerco-week to next-Monday's-Steerco. Eight checkpoints, each showing what the screen looks like and what's happening in Corrina's head. Read once. Then do it.
Monday morning ping from PMO
Carla sends a 1-line message: "WS1 fortnightly status report due Friday 5pm. Workstream ops page: /engagement/pmo/workstream/WS1/ops. Anything blocked, ping me by Wednesday."
Open your workstream ops page
Corrina opens /engagement/pmo/workstream/WS1/ops in a browser tab. This is her single source of truth for WS1 for the next four days. Done/Doing/Next blocks at the top, sprint cards below, backlog cards under that, RAID slice and decisions at the bottom.
Review what was committed last Steerco
Open the previous Steerco paper at /engagement/pmo/steerco/[N-1] in a second tab. Find the "Next" bullets for WS1. Compare to current backlog state. Anything that was on "Next" two weeks ago and is now done → goes in this fortnight's "Done". Anything still in-flight → "Doing". Anything not started → either rolled to next fortnight or flagged as a Risk in RAID.
- Six-channel pilot launch
- TEDx pitch deck v1
- Attribution model wired
- Six-channel pilot — in-sprint (60%)
- TEDx pitch — next-up
- Attribution — blocked by WS2-B003
Move backlog items between states
For each WS1 backlog item, set its status: done | in-sprint | next-up | backlog | blocked. Done items: write the evidence URL (the page on cosaiflip360.org that proves it). Blocked items: write the "blocked by" backlog ID and the unblock condition. New items raised this fortnight get added (id auto-incremented).
{
id: 'WS1-B001',
title: 'Capture baseline acquisition KPIs',
status: 'in-sprint', // ← was 'next-up'
owner: 'Corrina McGowan',
acceptanceTest: 'Dashboard signed by Corrina',
}
Draft Done · Doing · Next
Three paragraphs. Each: one headline + three bullets max. Every bullet ends in a URL or a backlog ID. No filler. No "we worked on" — only "we shipped" or "we are sprinting on" or "we are committing to". The PMO standard is "every bullet is a claim; every claim is evidenced".
Update RAID + set health colour
Open the WS1 slice of the RAID register. Add any new risk that emerged this fortnight. Close any item that has been mitigated. For each remaining item, refresh the mitigation language. Then set the health colour: Green (on track), Amber (delivery at risk without action), Red (delivery blocked). One sentence of justification.
Commit and push
For the first two fortnights, Carla pair-writes the report alongside Corrina via screen share. By the third fortnight Corrina edits the TypeScript constants in pmo-ops.tsx directly (or via the upcoming D1-backed admin UI). Carla reviews. Git commit. Push. cosaiflip360.org rebuilds. The report is now live and globally visible at the same URL Steerco will open Monday morning.
Steerco Monday: Mathew reads
Mathew opens cosaiflip360.org/engagement/pmo on his laptop. The live board shows the maturity ladder, the seven workstream health colours, the pending decisions, and the open RAID. Three minutes per workstream = 21 minutes of reading. Then Steerco starts at 11am — Mathew has the full state in his head.
- 9:00am — coffee, open
/engagement/pmo - 9:05am — scan the health strip (7 workstream colours)
- 9:08am — read each Done·Doing·Next (21 min)
- 9:30am — scan RAID escalations
- 9:40am — read pending decisions
- 11:00am — Steerco starts with everyone aligned
Do this 13 times. We win the Series A.
Phase 1 has 13 fortnights. Six Steercos. Seven Workstream Leads. 91 fortnightly status reports. Every one of them committed to git, signed by its author, anchored to a URL on cosaiflip360.org, and traceable from the decisions register all the way back to the backlog item that triggered the work.
That is the audit trail an investor walks into the diligence room and asks for. That is the audit trail Atlassian had at IPO. That is the audit trail WeWork did not. That is the difference between a billion-dollar exit and a vapourised valuation.
Two hours a fortnight. 13 times. The most valuable insurance policy on the programme.