Governance and funding are where your business case becomes a managed commitment rather than a hopeful story. This chapter is about making the decision explicit, tying money to control points, and ensuring that benefits actually have owners. Done well, this section gives executives confidence that they are not signing a blank cheque, that risks will be surfaced early, and that value will be tracked and protected over time.
15.1 Decision Rights, Thresholds, and Stage Gates
Before you ask for approval, you must be clear who actually has the right to say yes or no, what thresholds apply, and how the decision will be sequenced through stage gates.
Decision rights
Decision rights define who approves what. In many organizations, these are codified in a delegation of authority or investment policy, but in practice they can still be murky. For your case, you should make them concrete:
- Who is the formal approver for this decision? (Line manager, ExCo, Board committee, investment committee, CFO, etc.)
- Who are the recommenders? (Sponsor, steering committee, portfolio board, architecture council.)
- Who holds veto rights on specific aspects? (Security, Compliance, Legal, Safety, Data Privacy, Architecture.)
In the business case, you don’t need a full RACI matrix, but you should be explicit in one short section:
- “Approval sought from [body] for Option B.”
- “Finance, Risk, Architecture, and Legal have review rights; CISO has veto on cyber controls; CCO has veto on conduct risks.”
If there is ambiguity—say, because the spend is cross-functional or cross-entity—sort it out before submission. Cases often stall not on content but on “whose decision is this, actually?” battles.
Thresholds
Most organizations apply thresholds by:
- Amount – total investment, annualized OpEx, Capex line items
- Risk – e.g., “material change in risk profile,” “regulatory exposure,” “information security posture.”
- Strategic impact – changes to core strategy, new markets, divestments.
For your case, note which thresholds you trigger:
- Investment size: “Total investment of $X triggers ExCo review and Board notification.”
- Risk category: “Material change to customer data handling triggers Data Privacy review and risk committee visibility.”
- Strategic scope: “Entry into new geography Y triggers Board strategy committee review.”
Stating this removes surprises when someone later claims, “This should have gone to the Board.”
Stage gates
Stage gates separate discovery, pilot, scale, and sustain. They are the backbone of governance and funding release.
A simple, reusable pattern:
- Gate 0 – Concept / Discovery approval
- Purpose: Release limited funds to validate the problem and options, reduce key uncertainties.
- Typical outputs: Validated baseline, refined value case, initial architecture concept, risk scan, pilot design.
- Gate 1 – Pilot / MVP approval
- Purpose: Fund a real-world test that can demonstrate value and expose risks.
- Typical outputs: Pilot KPIs with before/after comparison, operational readiness, updated economics.
- Gate 2 – Scale-up approval
- Purpose: Commit the bulk of investment to broader rollout.
- Typical outputs: Proven solution, stable platform, refined risk controls, resource plan and capacity confirmed.
- Purpose: Commit the bulk of investment to broader rollout.
- Gate 3 – Sustain / BAU transition
- Purpose: Confirm that the initiative has transitioned to BAU and is delivering benefits; close the project phase.
- Typical outputs: Benefits tracking in BAU routines, residual risk profile stable, handover complete.
In the business case, you should show:
- Which gates apply to this initiative (not all are needed for smaller decisions).
- What decisions will be made at each gate.
- How funding (see 15.2) will be tied to gates.
This turns a single “all or nothing” decision into a sequence of controlled commitments.
15.2 Funding Mechanisms and Release Schedules
The funding section should answer three questions clearly:
- How much money is being requested in total?
- How will that funding be staged over time?
- What conditions (gates, evidence, controls) must be met for each release?
Funding mechanisms
Depending on your context, you’ll typically see:
- Project-based funding
- A defined budget for the initiative, broken down by year or by phase.
- Common for transformation programs, major Capex, platform replacements.
- Portfolio or envelope funding
- A pool of funds allocated to a portfolio (e.g., “Digital transformation,” “Risk & Compliance”) with the steering group deciding which cases to fund from it.
- Your case asks for a share of that envelope.
- Run-budget funding with incremental line items
- For smaller or incremental initiatives: adding budget to an existing cost center or program.
- The case argues for an increase in OpEx or headcount rather than a new project.
- Self-funded or reallocated
- Savings or revenue from within the initiative or program pay for the investment.
- Requires careful timing, because costs usually precede savings.
Your business case should make the mechanism explicit and confirm alignment with finance:
- “We request project-based funding under the Group Investment policy.”
- “We request allocation of $X from the approved Digital envelope for FY26–28.”
- “We request a $Y increase in the Z function’s run budget to support BAU and new platform operations.”
Release schedules and tranches
Avoid single, lump-sum approvals for anything non-trivial. Instead, propose tranches aligned with gates:
Example (for a 3-year initiative with pilot and scale):
- Tranche 1 – Discovery & Design: $2m
- Release at Gate 0.
- Conditions: Approved problem statement, baseline validated by finance, agreed scope and options, initial risk assessment.
- Tranche 2 – Pilot: $5m
- Release at Gate 1.
- Conditions: Signed vendor contracts, detailed design and test plan, data migration strategy validated, risk controls designed, key roles staffed.
- Tranche 3 – Scale-up: $20m
- Release at Gate 2.
- Conditions: Pilot meets defined KPIs (e.g., process cycle time, customer satisfaction, error rates), no major incidents, independent review of economics, readiness confirmed.
- Tranche 4 – Stabilization and optimization: $3m
- Release at Gate 3 (may be partly contingency).
- Conditions: Successful go-live, stable operations, benefits tracking embedded.
For each tranche:
- State amount, time window, what it funds (e.g., design vs build vs rollout), and gate conditions.
- Clarify who approves the tranche release (sometimes a lower-level body can release smaller tranches once the Board has approved the overall program envelope).
Handling contingencies and overruns
No executive believes that everything will go exactly as planned. Address this directly:
- Identify a contingency reserve (e.g., 10–20% of relevant cost categories) and show how it is governed (who can authorize its use, for what).
- State clear rules for scope changes and budget overruns (e.g., “Up to X% variance can be approved by sponsor; beyond that, return to steering/ExCo.”).
- Link major risk scenarios to potential need for extra funding or re-phasing.
This reassures approvers that you have thought about “what ifs” and that they will have visibility when they matter.
15.3 Benefits Ownership and Accountability
Governance and funding are only half of the story; the other half is who owns the value. Benefits that belong to “the project” rarely materialize; benefits owned by specific leaders with metrics and reporting stand a far better chance.
Benefit owners vs project owners
Differentiate:
- Project/initiative owner: Accountable for delivering the solution on time, on budget, to scope and quality.
- Benefit owner: Accountable for realizing specific benefits in their P&L, customer base, or risk profile.
In many cases:
- The sponsor is both initiative owner and benefit owner for the top-line or cost outcomes.
- Other executives or managers own specific benefit streams (e.g., Operations director for FTE savings, Sales lead for cross-sell revenue).
In the business case, include a compact table (or narrative) that indicates:
- Benefit theme → Metric → Target → Benefit owner (title) → First reporting date.
You do not need names if they might change; roles and functions are enough.
Linking benefits to performance routines
Make sure benefits are not just tracked in a project report but in BAU performance management:
- Integrate key benefit KPIs into relevant scorecards and reviews (e.g., monthly business reviews, frontline dashboards).
- Agree with finance how benefits will be measured and validated (baseline, attribution, leakage).
- Define a benefits review cadence (e.g., quarterly for 2–3 years after go-live) and which forum owns it (e.g., ExCo, portfolio board, BU performance review).
Your governance section should include a paragraph along the lines of:
- “Benefit owners will report progress on KPIs A, B, C in the quarterly business review, with finance validating actual vs planned benefits and updating the enterprise benefits register.”
Handling shortfalls and re-forecasts
No benefit plan survives first contact with reality. What matters is how you respond:
- Define how variance will be handled: at what point (e.g., 10–20% deviation) does the sponsor need to trigger an escalated discussion.
- Clarify who can re-forecast benefits and under what conditions (e.g., structural market changes vs execution shortfalls).
- If benefits materially underperform, outline possible actions: course corrections, additional investment, scope reduction, or, if needed, stopping the initiative.
This is less about punishment and more about transparent management of value over time.
15.4 Step-by-Step Decision Pack Assembly Guide
By the time you reach governance and funding, you are close to the finish line. The “decision pack” is what actually goes to the approvers: a tight bundle of materials that lets them read, reflect, and decide.
Here is a practical assembly sequence.
Step 1 – Confirm the decision and forum
Write this down explicitly:
- What decision is needed (approve/deny/revise, which option, which funding).
- Which body will take it (line manager, ExCo, Board committee, investment committee, regulator).
- When the decision meeting is scheduled and when pre-reads are due.
If there are multiple forums (e.g., ExCo then Board), clarify the sequence and purpose of each.
Step 2 – Freeze the economics and risk views
Before packaging:
- Freeze a decision version of the financial model (from Chapter 12).
- Freeze the risk register and top risks summary (Chapter 13).
- Check consistency across all references in drafts.
Late, uncoordinated edits to numbers are one of the fastest ways to lose credibility.
Step 3 – Draft and lock the executive summary
From Chapter 7:
- Make sure the ask, headlines, economics, risks, and implementation overview all align with the latest model and plan.
- Tailor emphasis to the forum (more risk and assurance for Board; more portfolio context for ExCo; more execution focus for line leaders).
Once stakeholders are aligned, treat the executive summary as the anchor for the entire pack.
Step 4 – Build the core deck or memo structure
Whether you use slides or a document, the decision pack should:
- Start with the executive summary.
- Follow the canonical structure you defined earlier (problem/context, options, economics, risks, implementation, governance & funding, ask).
- Keep each section to the level of detail appropriate for the forum:
- Board: 8–15 high-signal pages.
- ExCo: 15–25 pages.
- Line or portfolio committees: 20–30 pages plus appendices.
Strip out anything not strictly needed for the decision. Detail lives in appendices.
Step 5 – Attach the right appendices
Common appendices:
- Assumptions log.
- Detailed financial model outputs.
- Risk register and control designs.
- Technical architecture notes.
- Vendor proposals and commercial analysis.
- Regulatory, security, or privacy assessments.
- Benefits register and tracking plan.
- Implementation roadmap detail (beyond the high-level view in the main body).
Reference appendices from the main sections (“see Appendix B for detailed costing”) but avoid requiring readers to chase detail to understand the recommendation.
Step 6 – Tailor for each decision forum
You may need variants of the pack:
- For ExCo: Emphasize portfolio fit, strategic trade-offs, capacity, and dependencies with other initiatives.
- For Board: Emphasize risk, resilience, downside scenarios, governance, and assurance.
- For regulators: Emphasize compliance, controls, customer impact, and monitoring.
Keep the core data and conclusions identical. Tailoring is about ordering and emphasis, not changing numbers.
Step 7 – Build the meeting flow and speaking roles
Plan the decision meeting, not just the documents:
- Agenda:
- 2–3 minutes: Sponsor states the ask and headlines.
- 5–10 minutes: Case lead walks through problem, options, and economics.
- 5–10 minutes: Risk/Compliance and Finance give assurance.
- Remaining time: Q&A and decision.
- Speaking roles:
- Sponsor opens and closes (ask, framing, commitment).
- Case lead handles details and logic.
- Finance answers on numbers and modeling.
- Risk/Compliance and CISO (if applicable) speak to risk posture and controls.
Agree up front who will answer which types of questions and rehearse responses to likely challenges.
Step 8 – Run final QA and alignment
Before sending:
- Confirm consistency of numbers across summary, body, exhibits, and appendices.
- Confirm names and titles of roles are current.
- Confirm version control: every file has a version and date; links in emails point to the right version.
- Circulate to sponsor and core reviewers for a final, tight loop (not re-opening fundamental debates).
Only then distribute the pack to the decision body, with clear instructions on what decision is sought and what pre-reads should focus on.
15.5 Governance & Funding Checklist
Use this checklist as your final gate on governance, decision, and funding before submission.
Decision and rights
- The decision(s) required are clearly stated (approve/deny, which option, funding envelope, stage gates).
- The decision body (or bodies) is explicitly named.
- Any veto powers (e.g., Security, Compliance, Legal) are identified.
- Thresholds that drive escalation (e.g., to ExCo or Board) are acknowledged and respected.
Stage gates and controls
- A stage-gated path (concept, pilot, scale, sustain) is defined, or a clear rationale is given if not used.
- Each gate has a small set of exit criteria linked to value (benefits) and risk (controls, readiness).
- Gate decisions and approvers are clear (who can release which gate).
Funding and tranches
- Total funding requested is clear and reconciles with the cost model.
- Funding is broken into tranches aligned to phases/gates where appropriate.
- Conditions for releasing each tranche are defined (evidence, milestones, approvals).
- Contingency reserves and rules for using them are explicit.
- Rules for handling overruns and scope changes are described.
Governance structure
- Sponsor, initiative lead, and workstream leads are identified (by role).
- Governance forums (steering, design authority, risk reviews) and their cadence are defined.
- Decision rights for scope changes, design choices, and vendor selection are clear.
- Integration with existing portfolio or program governance is explained.
Benefits ownership and accountability
- Each major benefit stream has a named owner (role/title) outside the project team.
- Benefit KPIs, baselines, and targets are defined and linked to performance routines.
- A benefits tracking plan exists, with cadence and forum (e.g., quarterly business review).
- There is a mechanism to address benefit shortfalls (course correction, re-forecast, or stop).
Documentation and decision pack
- The executive summary, economics, risk, and implementation sections all tell the same story (no contradictions).
- Appendices include the key artifacts (model, risk register, architecture, vendor analysis, benefits register).
- The pack is tailored to the decision forum’s needs (risk for Board, portfolio for ExCo, execution detail for line leaders).
- Version control is clean; the “decision version” is clearly marked.
Readiness to decide
- Key stakeholders (finance, risk, architecture, legal, key business owners) have been pre-wired and do not have unaddressed fundamental objections.
- There is a clear recommendation, not merely a neutral presentation of options.
- The consequences of “do nothing” are explicit, so the choice is framed against reality, not a blank slate.
If you can honestly tick these items, your Governance, Decision & Funding section should give executives the confidence that the recommendation is not only analytically sound and executable, but also properly controlled, funded in a staged way, and wired into the organization’s accountability mechanisms.
