Governance
Governance in the flow, not at the gate.
Most governance was designed to control a plan. Today it controls the flow of work: teams wait for approval, decisions are taken two levels above the information, and every stakeholder has a channel into the backlog. Agile governance is not less control. It is clear constraints and explicit decision mechanisms, so execution can be decentralised without anyone losing oversight.
What it looks like from the inside
- Teams iterate every two weeks. The budget changes once a year.
- An architecture change passes three approval layers, each with its own calendar.
- Priorities come from several stakeholders, none of whom see the others’ requests.
- Compliance arrives at the end, as a gate, and finds what a gate finds.
- Management measures utilisation and output. The strategy is written in outcomes.
Six things we design together
Direction
Strategy, outcomes and investment intent
What the organisation is trying to achieve for its customers and itself, in outcomes a team can test, and how much it is willing to invest to find out.
Decision rights
Decide where the information is
Take decisions at the lowest level where the best information sits, as late as responsibly possible, on evidence rather than the highest-paid opinion. Don’t converge early to put minds at ease, and don’t flatten complexity; run parallel experiments and decide on what they show. Guardrails say what is decided locally and when a decision moves up, so nobody waits for permission they never needed.
Flow
How work and decisions move
The cadence is built around the quarterly business review: a transparent inspection of the value delivered — what changed for customers and the business, what we learned, where we adjust. That inspection pulls the cycle: it feeds big room planning and portfolio and epic sync, not the other way round. Each event has one question, the right participants and a decision that leaves the room.
Funding
Money that follows value
Funding value streams and capacity instead of fixed project scope, so a changed insight does not need a new business case.
Control
Risk, compliance and architecture inside delivery
ISO or COBIT control objectives mapped onto the way the teams already work, with evidence produced by the work itself rather than assembled afterwards for an audit.
Learning
How the system inspects itself
Results reviewed against what changed for customers and the business, and the operating system adjusted on that evidence, not on the next reorganisation.
Questions clients ask
How do you balance flexibility with control?
By separating the two questions most organisations merge. Control is about evidence and accountability; flexibility is about how late you can still change your mind. Explicit decision rights and outcome-based reporting tighten the first without losing the second.
Can we stay compliant without slowing teams down?
Yes, if the controls are built into the flow of work rather than bolted on as a review gate. Most compliance pain comes from evidence being collected twice: once by the team, once by a control function.
Where does accountability sit in an agile organisation?
With the role that owns the outcome, not the role that owns the plan. That is a redesign of roles rather than a reallocation of blame, which is why governance work and leadership coaching belong together.
Want a read on your governance?
A short review of where decisions, priorities and funding get stuck. You keep the findings whether or not we work together.