Leadership asks a basic question and nobody has a clean answer. The reflex is a new report or a new dashboard. The problem usually sits three layers below that.
Data & Reporting
The Sentence I Hear Most Often
It isn't dramatic. It's usually just tired: "I feel like we should be able to answer this by now." What follows is different in every business: maybe it's how much we actually made last quarter, whether we have the capacity for the initiative everyone's excited about, or why the last launch took twice as long as it should have. The specifics change; the shape doesn't. Leadership asks. Nobody has a clean answer.
The Three Layers Underneath
That's the tip of the iceberg, the one visible piece above the waterline. Most people think the problem stops there, so they go looking for a report, a dashboard, or an analyst to own it. That usually doesn't fix it, because the real problem sits underneath, in layers most people never look at directly. They're not strictly sequential, and most situations are some mix of all three.
One, the data was never captured in the first place. Not necessarily because anyone dropped the ball. Often there was no bandwidth to capture it at the time, or the business wasn't big enough for the answer to need to live anywhere outside one person's head. That's not neglect. That's just what the early stage looks like.
Two, it was captured, but it doesn't live in a real system. It's in someone's inbox, a spreadsheet on their desktop, or their memory, which means it's one departure away from disappearing.
Or three, it lives in a system, but nothing says who keeps it current. It goes stale, and people quietly stop trusting it.
The Question Nobody Asks Out Loud
And underneath all three, there's usually a question nobody has asked out loud: did anyone ever define what "revenue," "done," "active," or "at risk" actually means here? And one level further down: which questions does the business actually need to be able to answer, and what data would it take to answer them? Sometimes the definitions exist but the system was never built to reflect them. Either way, no tool fixes that, because the tool was never the thing that was broken.
The tool was never the thing that was broken.
This is the part that gets skipped. Most fixes aim at the visible piece: a new report, a new hire, a new tool. All reasonable moves, and all treating a symptom that tends to come back if the layers underneath stay unresolved.
The actual fix starts at the bottom. Decide which questions you need to be able to answer. Define the terms inside them. Decide who owns each answer, where it lives, and who keeps it current. The dashboard, if you still want one, comes after.
It Probably Wasn't the Report's Fault
If you've been down this road before and the fix didn't hold, it probably wasn't the report's fault. If there's a question your business should be able to answer by now and can't, the useful first step is figuring out which layer the answer is stuck in. That's a conversation that we can have.
