Season 2, Episode 2: Clarity as the Catalyst for Accountability: Why Ownership Begins with Understanding

Before organizations can improve accountability, strengthen governance, or optimize technology investments, they need a clear understanding of what they have, why it exists, and who owns it.

In this episode of The Insight-Driven CIO Podcast, Mark Søndergaard explores why accountability begins with clarity—not responsibility. Through a real-world executive scenario, he explains how fragmented information, unclear ownership, and limited visibility quietly increase operational complexity, unnecessary costs, and business risk.

This episode is for CIOs, Technology Advisors, MSPs, and business leaders who want to think differently about accountability, operational clarity, and executive decision-making.

 Follow EnTelegent Solutions on LinkedIn for updates.

 © EnTelegent Solutions – The Insight-Driven CIO Podcast. 

Transcript

SPEAKER_00 0:00

Picture the scene. It's a quarterly executive review. The kind of meeting where everyone comes prepared, slides are polished, and the agenda is tight. And then someone, usually the CFO, sometimes the CEO, stops the room with a question that wasn't on the agenda. What is this line item? It's a number on the financial report. Not a large number necessarily, but it's been there for a while. And the question isn't really about the number. The question is, does anyone in this room actually know what this is? The silence that follows that question? That's what this episode is about. Welcome to the Insight Driven CIO podcast. I'm Mark Sundegaard, channel chief and VP of Sales at Intelligent Solutions. This show exists for one reason. To have honest, grounded conversations that help technology and business leaders make better decisions. Because technology changes constantly. Leadership doesn't. I've sat in a lot of rooms with technology and operations leaders over the years, and one thing I keep seeing across industries, across company sizes, is this. The environment grows faster than the understanding of it. Not because people aren't paying attention. They are. But every quarter, something new gets added. A contract renews, a project spins up and pulls in a new service. And somewhere in that motion, the question of who owns what, who's accountable for what, quietly gets deferred. Nobody decides to lose track. It just happens. Gradually and then all at once. And by the time someone asks a hard question in a room full of smart people, the honest answer is we're not entirely sure. I want to tell you about a specific situation. The details have been changed, but the shape of it. I've seen versions of this more times than I can count. An organization is in its quarterly executive review. Finance has flagged a telecom expense that's been appearing on the monthly financial report for years. Not a massive number, but consistent. And the CFO wants to understand it. So the question goes around the table. IT looks at operations, operations looks at the business unit that originally requested the service. That business unit has turned over twice since the contract was signed. Nobody in the room can say with confidence what the service is for, who requested it, or whether it's still being used. What happens next is the part that sticks with me. It takes weeks to get an answer. Not because the organization is dysfunctional, it isn't. But because the information is scattered. Contracts are in one system. Provisioning records are somewhere else. The original project documentation, if it exists at all, is buried in an email thread from three years ago. Someone eventually tracks down a retired employee who remembers the context. The service had been provisioned for a project that wrapped up 18 months prior. It was never canceled, not out of negligence, just because no one had a clear view of the full environment, and no one had been explicitly assigned to watch for it. But here's the part that really matters. Once they started pulling that thread, they found more. Not one orphan service, several. Contracts that had auto renewed without review. Services that had been duplicated across departments because no one knew the other team had already solved for it. Vendors being paid for capacity that hadn't been touched in over a year. One question in one meeting opened a window into something much larger. The organization didn't have a spending problem, it had a visibility problem, and the visibility problem had been quietly compounding for years. Then I think about what actually went wrong in that situation. It's tempting to say it was a process failure or a governance failure. And maybe it was, technically, but I keep coming back to something more fundamental. Nobody in that room could explain the environment they were operating in. Not completely. And if you can't explain it, if you can't say with confidence what you have, why you have it, and who's responsible for it, then you're not really managing it. You're just coexisting with it. Accountability is one of those words that gets used a lot in organizations. Usually in the context of assigning blame or clarifying roles after something goes wrong. But I think that's backwards. Accountability doesn't start with responsibility. It starts with clarity. When everyone is working from the same complete picture of the environment, ownership becomes obvious, decisions get faster, renewals get reviewed, redundancies get caught before they compound. Not because someone issued a mandate, but because the information makes the right action visible. The organizations I've seen get this right aren't necessarily the ones with the most sophisticated governance frameworks. They're the ones where nobody has to guess. Where the answer to who owns this is a lookup, not an investigation. Operational control starts with understanding, not oversight. Most organizations approach this the other way around. They build approval workflows, escalation paths, review committees, and those things have value. But if the underlying data is incomplete or fragmented, the oversight layer is just managing noise. You can have all the governance structure in the world and still not be able to answer a basic question about your own environment. I've seen it. The structure exists, the clarity doesn't. Understanding has to come first. What do we have? What are we paying for it? What's it connected to? Who requested it and does that need still exist? When you can answer those questions consistently from a single source, oversight becomes almost automatic because the gaps become visible before they become problems. And when ownership is unclear, costs and complexity don't stay flat, they grow. This is the part that surprises people when they first see it clearly. It's not that unclear ownership causes one problem, it causes a category of problems that tend to reinforce each other. A service with no clear owner doesn't get reviewed at renewal. A contract with no clear owner gets auto-renewed. A vendor relationship with no clear owner doesn't get renegotiated. And because each of those things happens quietly, no alarm, no flag, no meeting, the compounding effect is invisible until someone asks the wrong question at the right moment. The CFO's question in that executive review wasn't unusual. What was unusual was that it got asked out loud, in a room where people had to respond. Most of the time those questions never get asked, and the costs just keep accumulating. The organizations that get this right have something in common, and it's simpler than most people expect. Everyone is working from the same information. Not the same spreadsheet that someone updates manually every quarter. Not a report that IT polls when someone asks for it. A live, shared, authoritative view of the environment. What exists, what it costs, what it's for, and who owns it. When that exists, accountability isn't something you have to enforce. It's something that emerges naturally. Because when the information is visible to everyone, the right questions get asked earlier. Renewals get flagged before they auto execute. Redundancies get caught before they multiply. And when a CFO asks about a line item in a quarterly review, someone in the room can actually answer. That's not a technology outcome. That's a leadership outcome. The technology just makes it possible. You can't manage what you can't explain. I mean that literally. Not as a principle, not as a framework, as a practical test you can apply to your own organization right now. Pick any major technology service your organization is paying for today. Can you explain it clearly, completely, without hedging to your CFO? Can you say who owns it, why it exists, what it would cost to eliminate it, and what would break if you did? If the answer is yes, you're in good shape. If the answer involves a few phone calls and some digging, that's worth paying attention to. Because the gap between what you're paying for and what you can explain is exactly where operational accountability breaks down. So here's the question I want to leave you with, and I want you to take it seriously. Not as a thought experiment, but as something you could actually be asked. If your executive team asks today, in your next meeting, without advance notice, who owns every major technology service your organization is paying for, how many of those answers would be based on certainty? Not assumption, not I think it's probably, or that would fall under certainty. Someone's name, a clear purpose, a documented owner. Because the distance between the number you just thought of and the total number of services you're paying for, that's the gap. That's where the risk lives. That's where the unnecessary costs are accumulating. And that's where operational accountability either exists or it doesn't. I genuinely hope this conversation sparks something for you. Whether it confirms something you already suspected or surfaced a question you've been sitting with. Thanks for listening to the Insight Driven CIO podcast. I'm Mark Sundergard. Until next time. Technology changes constantly, leadership doesn't.