From Wish List to Roadmap: Sequencing a Governance Program

LEXSHIFT BLOG SERIES: THE GOVERNANCE INVESTMENT: PLANNING AND FUNDING FOR THE YEAR AHEAD Week 6 of 12 The fourth article in this series examined which governance investments deserve attention and what the organization can realistically deliver. The fifth developed the business case, connecting that work to the costs, expected benefits, and assumptions leadership needs to […]
Building the Business Case for Governance

LEXSHIFT BLOG SERIES: THE GOVERNANCE INVESTMENT: PLANNING AND FUNDING FOR THE YEAR AHEAD Week 5 of 12 The fourth article in this series focused on prioritizing governance gaps rather than trying to close them all at once. A prioritized list identifies where attention is needed and why. A business case takes the next step: explaining […]
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 […]
The Real Cost of the Status Quo

LEXSHIFT BLOG SERIES: THE GOVERNANCE INVESTMENT: PLANNING AND FUNDING FOR THE YEAR AHEAD Week 3 of 12 The second article in this series focused on the value of an honest maturity assessment before developing a governance plan. Once the gaps are understood, the next question is practical: what does leaving them unaddressed cost the organization? […]
Know Where You Stand: Assessing Governance Maturity Before You Plan

LEXSHIFT BLOG SERIES: THE GOVERNANCE INVESTMENT: PLANNING AND FUNDING FOR THE YEAR AHEAD Week 2 of 12 The first article in this series made the case for funding governance proactively, during planning season, instead of reactively, after an incident forces the conversation. That case only works if it starts from an honest picture of where […]
The Governance Conversation Nobody Schedules Until It’s Too Late

LEXSHIFT BLOG SERIES: THE GOVERNANCE INVESTMENT: PLANNING AND FUNDING FOR THE YEAR AHEAD Week 1 of 12 Most governance programs are not planned. They are triggered. An audit finding surfaces a retention gap that should have closed years ago. A breach investigation reveals that nobody can say with confidence what data exists, where it lives, or why […]
Why Late Summer Is the Right Time to Plan for Governance

We recently closed a series with a simple idea. Retention, and operational governance more broadly, is becoming infrastructure. Foundational, continuous, and something the rest of the business depends on. Infrastructure has one defining characteristic that is easy to overlook. It is planned. It is budgeted. It is built on purpose, ahead of need, rather than assembled in […]
Defensible Disposition: Proving Deletion Was Correct, Not Just That It Happened

Most governance programs are built around a single question: what should we keep, and for how long. That question matters, but it’s only half the job. The other half, the one that gets far less attention, is what happens when the retention period ends. Deleting the content isn’t the hard part. Being able to prove, later, that the deletion was correct, is. […]
You Do Not Have Governance, You Have Documentation

Ask most organizations with an IG program if they have governance over their information, and the answer is yes. There’s a policy. There’s a retention schedule. There’s a framework, usually well written, sometimes benchmarked against a recognized standard, occasionally reviewed by outside counsel. By any reasonable definition of “having governance in place,” the box gets checked. None of that is governance. It’s documentation. Governance […]
Legacy Systems Don’t Just Store Data, They Accumulate Risk

Every organization has at least one system nobody wants to touch. A legacy repository built for a platform that’s no longer supported. An old file share that survived three reorganizations. An on-prem archive that outlived the department that created it. These systems don’t sit quietly in the background while the rest of the organization modernizes around them. They accumulate […]