Redback · Project governance
Project governance
Decision-making structures sized to the work — light where it can be, firm where it must be.

Designing the decisions first
We begin by listing the decisions your project will need over its life: approving scope changes, releasing budget, choosing between suppliers, accepting deliverables, going live. For each, we agree who decides, what evidence they need, and how quickly. The meetings and documents follow from that list, not the other way round.
Typical components
Two-page governance model
Roles, decision rights, escalation paths and meeting cadence on two pages anyone can read in five minutes.
Evidence-based reporting
A one-page report built on measures that are hard to dress up: items accepted, defects found and fixed, forecast based on actual throughput, decisions pending.
Stage gates with real criteria
Where your organisation needs formal gates, we write entry criteria that can genuinely fail, so a gate means something.
RAID that lives
Risks, assumptions, issues and dependencies kept in a format small enough to review weekly, each with an owner and next action.
Trade-offs
More governance buys visibility at the cost of team time. We will tell you what we would remove, as well as what we would add.