LEXSHIFT BLOG SERIES: THE GOVERNANCE INVESTMENT: PLANNING AND FUNDING FOR THE YEAR AHEAD
Week 9 of 12
A year of consistent measurement gives a governance program useful evidence for the next planning cycle. The funding request needs to explain what that evidence means for the decisions ahead. Leadership should be able to see what the current investment delivered, what still requires attention, and which resources the program needs to sustain or extend its work.
The previous article addressed how to select, define, and review metrics. This article focuses on using those results in an investment discussion. The task is to connect performance to a specific request, explain the available choices, and make the consequences of those choices clear.
Connect Results to the Decision
Start with the decision leadership needs to make. A request to maintain current service levels needs different evidence from a proposal to extend retention controls to additional systems. Select the results that help evaluate that decision, then keep the supporting detail available for questions. A concise report can still be complete enough to support an informed choice.
For each selected result, explain the intended outcome, what happened, and why it matters. Use the baseline and target established in the business case, and retain the definitions used in regular reporting. If the scope or measurement method changed during the year, explain how that affects the comparison. A summary should preserve the qualifications that make the underlying evidence reliable.
For example, a reduction in overdue exceptions may support a conclusion that the resolution process is improving. The report should also show whether the workload changed, whether higher-risk cases remain open, and whether the improvement depends on temporary staffing. Those details help leadership assess whether the result can be sustained with the resources proposed for next year.
Include results that fell short of expectations and explain what the team learned. If the expected benefit has not yet appeared, distinguish a delay in implementation from a problem with the original assumption. Avoid attributing every improvement to the governance investment when other changes may have contributed. Credible reporting makes the basis for each conclusion visible.
Tie the Request to the Work Ahead
Use the roadmap developed earlier in this series to connect the request to the next stage of work. Identify the remaining gap, the proposed action, and the outcome the investment is intended to support. Review whether the roadmap still reflects current conditions. Changes in business priorities, systems, or workload may require a different sequence from the one originally approved.
A measure below target does not automatically establish a need for more funding. If adoption remains low, investigate the cause before proposing additional capacity. Employees may lack time, the process may be difficult to use, or responsibilities may be unclear. The request should explain why the proposed response fits the problem and what evidence supports that judgment.
Suppose retention controls were implemented in two repositories, while three remain outside the program. The next request should identify which repository will be addressed first, why it takes priority, and what implementation requires. Include dependencies such as business-owner decisions, legal review, technical configuration, and testing. This makes the proposed scope and the resources needed to deliver it easier to assess.
State how progress will be evaluated after approval. Name the accountable owner, the major delivery milestones, and the measures that will show whether the work is producing the expected result. Where costs or benefits remain uncertain, explain the assumptions and identify when they can be validated. Leadership can then evaluate both the request and the plan for managing it.
Separate Ongoing Operations From Expansion
Distinguish the resources needed to sustain current operations from those needed to extend the program. Ongoing costs may include staff time, exception handling, policy maintenance, system administration, and recurring technology fees. Expansion may involve additional repositories, business units, or capabilities. Show implementation costs and any recurring costs the expansion will add.
Use a consistent baseline so the same cost is not counted in both categories. Shared staff or technology may support several activities, so explain how those costs are allocated. Also identify work currently supported by temporary funding or unbudgeted staff time. A program that appears inexpensive may depend on resources that will not be available in the next planning cycle.
Explain what different funding levels would mean in operational terms. If leadership approves ongoing operations but defers expansion, identify the work that continues and the gap that remains. If current funding is reduced, describe the expected effect on service levels, control coverage, or delivery dates. Avoid treating every reduction as equally damaging; identify the priorities and dependencies that drive the consequences.
Make the Request Easy to Evaluate
Organize the report around the people making the decision and the questions they need answered. Finance may need the cost assumptions and recurring commitments. Business leaders may focus on operational effects and competing demands on their teams. Legal and technology stakeholders may need to assess obligations, dependencies, and feasibility. Confirm these needs before finalizing the request.
Lead with the decision requested, the resources involved, and the reason for acting in the proposed period. Follow with the evidence, delivery plan, and consequences of deferral. Keep detailed calculations and operational reports available as supporting material. Use the same figures and definitions throughout so readers can trace a summary statement back to its basis.
Be explicit about what approval includes. A technology purchase may also require implementation support, business participation, and ongoing administration. If those commitments are essential, include them in the request. Record the decision, any conditions attached to it, and the resulting changes to scope or timing so the program can plan against what was actually approved.
A useful investment report connects the year’s results to a defined course of action. It explains what should continue, what should change, and what each choice requires. That gives leadership a clear basis for evaluating the request and gives the program a practical starting point for the next planning cycle.
Next in the series: When the Budget Gets Pushback: Responding to Cuts Without Losing the Program’s Momentum.
The information you obtain at this site, or this blog is not, nor is it intended to be, legal or consulting advice. You should consult with a professional regarding your individual situation. We invite you to contact us through the website, email, phone, or through LinkedIn.