Notes on governance and delivery
Practical perspectives on the decisions, processes and controls that shape how work gets done.
Elland Advisory perspectives
Governance
When governance creates work instead of control
Governance should make decision authority clear and apply controls proportionate to risk.
If every issue goes to the same committee, the committee becomes the bottleneck. If every project carries the same approval burden, low-risk work spends time satisfying controls designed for something much larger.
Start with the decision. Define who owns it, what evidence they need and when it must be made. Match the control to the value and risk involved. Then remove duplicate approvals and reports that serve no clear purpose.
Ask of every control: what decision does this support, and what happens if we remove it?
Reporting
Reporting needs a route to action
Visibility is only valuable when somebody can act on it.
A dashboard can be full of accurate numbers and still leave its reader uncertain about what needs attention. Reporting becomes an administrative burden when teams collect data without a clear route to action.
Focus on exceptions, their consequences, an accountable owner and the next decision. Keep definitions consistent so that leaders can compare performance without first decoding the report.
For each red or amber item, can the reader see the action, owner and decision needed?
Capital planning
A capital plan needs to reflect delivery capacity
Funding is one constraint. People, readiness and dependencies matter too.
Approving more projects does not create more capacity to deliver them. When the plan ignores design readiness, procurement lead times or competing resource demands, commitments become fragile.
Bring delivery constraints into prioritisation. Look at sequencing, dependencies and the availability of the teams that must deliver the work. Revisit the plan when assumptions change.
Which approved projects are genuinely ready to move, and what is preventing the others?