Not Everything at Once: How to Prioritize Governance Investments
LEXSHIFT BLOG SERIES: THE GOVERNANCE INVESTMENT: PLANNING AND FUNDING FOR THE YEAR AHEAD Week 4 of 12 The third article in this series put a number on the cost of the status quo: over-retention, manual effort, risk exposure, and storage spend that keeps growing. That number makes the case for action. It can also create pressure to fix everything at once. Before asking for funding, governance leaders need to decide which investments deserve to move first, what the organization can realistically deliver, and which gaps can wait. A credible answer gives leadership a reason to approve the first phase and confidence that the rest has been considered. The Cost of Taking on Too Much A governance program with a dozen legitimate gaps is not one problem. It is a dozen problems competing for the same budget, staff, and window of leadership attention. Proposing to address all of them in the same cycle produces a plan that looks comprehensive on paper and struggles when it meets a real calendar. The same information governance manager may be needed to validate schedules, support a migration, and review a new tool. Funding each project does not create more of that person’s time. When resources are spread too thin, updates show partial progress across several workstreams while the underlying gaps remain open. Sequencing makes the ambition more credible. It identifies the work that can start now, the preparation needed for later investments, and the results leadership should expect at each stage. The full scope remains visible, but the immediate commitment fits the organization’s capacity to execute. Two Questions That Guide the Decision Prioritization does not require a complex scoring model to be useful. Start with two questions applied consistently across the gaps identified in the maturity assessment. How much risk or cost does this gap carry if it stays unaddressed? How much value would closing it deliver relative to the effort required? Together, those questions connect the cost baseline to a practical investment decision. High risk and high value generally deserve early attention. Low risk and limited value can usually wait. The harder calls sit in between. A moderate-risk gap that is inexpensive to close may be a sensible early investment alongside the foundational work for a more serious problem. A high-risk gap with little immediate financial return may still need to lead. An approaching deadline or an exposure leadership cannot accept should be treated as a constraint before discretionary projects are ranked. Keep the initial comparison simple. Record the consequence of waiting, the expected improvement, and the evidence behind each estimate. A high, medium, or low rating can be sufficient if everyone uses the same definitions. The discussion becomes useful when teams can explain why two investments received different ratings and what new information would change the order. Weighing Risk and Value Honestly Risk and value are easy to score generously when the person scoring them owns the workstream. Use the cost baseline established in the previous article and review assumptions across legal, IT, records management, and finance. The retention gap legal has been flagging for two years deserves the same rigor as the data visibility gap IT just surfaced. Time spent on someone’s list is not evidence of urgency. For risk, consider the information involved, the likelihood and consequence of a control failing, and the protection already in place. For value, describe the actual change: less manual review, lower spending, or a capability the organization currently lacks. Keep those benefits distinct. Hours returned to a team create capacity, but they do not automatically reduce its budget. A proposed storage reduction needs an explanation of when it will affect the bill. Avoid counting the same benefit under several projects. Make uncertainty visible as well. If an estimate rests on a small sample or incomplete inventory, state that and identify the work needed to improve it. An uncertain estimate may justify a limited discovery phase before a larger commitment. It should not receive the same confidence as a benefit supported by an established baseline and a clear way to measure the result. Accounting for Effort and Dependencies Value has to be weighed against the full effort required to deliver it. Include internal staff time, integration work, and the changes business teams will need to make. Someone also has to maintain the control after launch. A tool that can be purchased this quarter may still depend on decisions about ownership or retention that will take longer to resolve. Those dependencies belong in the investment discussion from the start. Consider unstructured data with no retention controls alongside a records management system that already enforces schedules consistently. The unstructured environment may offer greater value, but the team first needs to understand what it contains and who is responsible for it. A practical first investment could establish ownership and test the proposed controls in one defined area. That work gives the team evidence for the wider rollout and a more credible estimate of its cost. Check dependencies across proposals, too. Several projects may need the same inventory or system integration. Treating that work as a shared investment can prevent duplicate effort. It can also explain why a modest-looking foundational task belongs near the top of the list: completing it allows several higher-value improvements to proceed. Test the proposed sequence against actual availability. Ask the people expected to do the work what they would have to postpone to take it on. If two priorities need the same specialist during the same month, the plan needs a different sequence or additional capacity. Include the time business owners need to review and approve changes. A project can be affordable and still be impossible to staff on the proposed schedule. Choosing Early Wins That Prove Value A prioritized plan should include an improvement that can be delivered quickly and visibly, provided it does not displace urgent work. Early results give leadership evidence to assess before committing to the next phase. Choose an outcome that supports the wider program, such as reducing a