The Strategic Reporting Paradox

Spending a considerable time in corporate/established businesses has taught me something uncomfortable:

The strategic reporting system isn't broken because people can't report well. It's broken because we have built it that way.

I've sat in business review sessions data that doesn't quite add up is presented. The narrative is thin. The outlook is vague. The numbers are late - or worse, they're on time but clearly massaged to look better.

Here's what nobody says out loud: We designed strategic operating systems that demand precision, timeliness, and insight from teams that have neither the tools, the time, nor the trust to deliver any of those things.

My challenge today is that this is not a “reporting problem”. This is a design problem.

Think about it:

• If you are asked for monthly reports on initiatives that only show meaningful progress quarterly…that’s a design problem.

• If you are required to have real-time dashboards from teams working with data that takes three weeks to clean…design problem.

• If you are required to produce forward-looking analysis and still manually compiling last month's actuals in Excel at 11 PM…design problem.

We've created reporting rhythms that are divorced from the actual rhythm of the work being reported on.

And then—here's the paradox— instead of reporting being insightful it becomes performative.  This creates executives that start "managing the narrative" instead of sharing the truth. When the data shows green but everyone in the room knows the initiative is bleeding red.

The system doesn't just fail to get good data. It actively incentivizes bad data.

I've watched brilliant executives—people with impeccable track records—start to unravel when they hit an organization with dysfunctional reporting infrastructure. Not because they suddenly forgot how to lead. But because they were trying to feed a strategic operating system that demands what it makes nearly impossible to deliver.

Your credibility gets built in these moments. Not in the big presentations. Not in the strategy documents. But in whether your colleagues believe the information you provide them.

So if you're an executive consistently struggling with reporting, ask yourself the following and advocate for change:

• Is it the system? Then advocate loudly for fixing it. Make the invisible visible.

• Is it your team's capability? Then invest in building it. Reporting infrastructure isn't someone else's problem.

• Is it your own prioritization? Then that's the real issue. Address it before it defines your reputation.

Because here's the truth: When the system is broken, the people trying to work within it start looking broken too.

We're heading into year-end reviews and Q1 planning cycles. The pressure on reporting is about to intensify.

Maybe this is the year we start building systems that deserve good reporting.

-

What's one reporting demand you have experienced to be structurally impossible to meet well?