Steering committee
A scheduled forum with a pack, decisions required, and an owner for each action. Cadence is agreed in the plan—typically monthly for executives, more often when the program is in cutover.
Loading page
How we deliverGovernance
How we deliver
Not a monthly slide. A weekly rhythm of decisions, RAID, and reporting that executives, delivery leads, and client counterparts can all use.
A scheduled forum with a pack, decisions required, and an owner for each action. Cadence is agreed in the plan—typically monthly for executives, more often when the program is in cutover.
Design and delivery decisions that should not wait for steering. Terms of reference state what they can decide and what they must escalate.
Who can change scope, architecture, or go-live. Recorded. If it is not written, it will be rediscovered in a crisis.
Time-bound paths for blocked decisions, security findings, and commercial issues. Silence is not a control.
Risks, assumptions, issues, and dependencies with owners, dates, and residual rating. Reviewed weekly, summarized for steering.
External teams, vendors, environments, and freeze windows mapped early. A dependency without an owner is a hidden critical path.
Weekly delivery update for the working team. Executive status that can be read in five minutes: outcome, variance, decisions needed.
Burn against the agreed commercial model. No surprise invoices that steering has not already seen as a forecast.
Change requests with impact on time, cost, risk, and quality. Informal ‘while you’re here’ work is how programs lose their shape.
Next step
We will walk through the structure with sample data. We will not invent a client logo to decorate it.