Your CMO sends the monthly marketing report. You scan it. Thirty-two slides. Revenue attribution. Funnel metrics. Channel performance. CAC by segment.
You close it feeling slightly more informed and no more certain about what to do.
So you reply: „Can we get more details on the pipeline numbers?” Your team builds another report. Someone schedules another meeting. Another week passes without a decision.
A leadership habit disguised as diligence.
Reporting as a Comfort Mechanism
Most executive data requests are comfort-focused, not decision-focused.
You feel uncertain about marketing, so you ask for a marketing report. The report arrives. You scan it. The uncertainty remains because nobody designed the report to resolve it. The team designed it to describe what happened. Describing and resolving are different things.
So you ask for more detail. More granularity. A breakout by region. A comparison to last quarter. Each request feels productive. None of them moves you closer to a decision because none of them started with one.
Wavestone’s AI & Data Leadership Executive Benchmark Survey (2025) tracked 125 Fortune 1000 organizations. Nearly all of them, 98.4%, increased their data and AI investments that year. Yet only a minority reported having established a data-driven culture. The barrier, according to 92% of C-suite respondents: people and organizational resistance. Technology ranked last.
The instinct is to blame the tools. As I explored in „Your Martech Stack is a Frankenstack,” tool sprawl creates real operational damage. But the tools work fine individually. The problem is that nobody defined what the data was supposed to decide.
When you ask for a report without knowing what decision it informs, you’re not managing. You’re self-soothing with spreadsheets.
The Difference Between Describing and Deciding
There’s a question that separates useful reporting from expensive decoration:
What decision will this data inform?
If you can’t answer that before the report gets built, the report will describe activity without enabling action. It will show you what happened. It won’t tell you what to do about it.
Compare two requests:
Vague: „How is marketing performing?” Performing against what? By which measure? Over what time period? Compared to what alternative? This question is too broad to inform any specific action. So the team builds a broad report. You scan it. You ask follow-up questions. The cycle restarts.
Focused: „I need to decide whether to increase marketing spend next quarter. What data would help me make that decision?” Now the team knows what to build. Current CAC. Pipeline generated per dollar spent. Revenue attributed to marketing. Comparison to what reallocation would look like. The report has a job. It can succeed or fail at that job. Either way, you get a decision.
Every report should answer a question or support a recurring decision. If it doesn’t map to a specific decision, it’s decoration. Expensive decoration that consumes attention and creates the illusion of being informed.
Why Narrative Beats Numbers
Jeff Bezos banned PowerPoint at Amazon in favor of six-page narrative memos. People frequently cite this as an efficiency move. It’s actually a decision-quality move.
A dashboard presents numbers. A memo has to argue a point. It has to say: here is what’s happening, here is why it matters, and here is what I recommend we do. The discipline of writing forces the author to think through the logic, surface assumptions, and commit to a conclusion.
Dashboards don’t do this. They show trends and leave interpretation to the viewer. Ten executives can look at the same dashboard and draw ten different conclusions. A Rorschach test with better typography.
Warren Buffett reads annual reports cover to cover. Jason Fried at Basecamp replaces status meetings with asynchronous written updates. Same principle: force the thinking into written form before the conversation starts, so the conversation becomes about the decision rather than the data.
Most marketing teams do the opposite. They build the dashboard, present it in a meeting, and hope the discussion produces a conclusion. It rarely does. It produces follow-up questions, which produce follow-up reports, which produce follow-up meetings.
Writing forces a point of view. Dashboards allow everyone to avoid one.
The Decision Framework Nobody Uses
Fewer reports tied to clearer decisions. Five principles that sound simple and almost nobody follows:
Start with the decision, not the data. Before building any report, write down the decision it’s meant to inform. If you can’t articulate the decision, you don’t need the report. This single filter eliminates most reporting requests before they start.
One number per decision. For any given decision, identify the single metric that matters most. Other metrics provide context, but one metric decides. When everything is equally important, nothing is important. If your team can’t agree on a single number, you haven’t agreed on what you’re optimizing for.
Narrative over numbers. Require your team to write a one-page memo for every major report: what’s happening, why it matters, what we should do about it. A memo with a recommendation is worth more than twenty dashboards with trends. If the team can’t write the memo, they don’t understand the data well enough to present it.
Decision cadence, not reporting cadence. Match your data rhythm to your decision rhythm. If you make budget decisions quarterly, you don’t need weekly budget reports. You need a quarterly budget analysis delivered two weeks before the decision meeting, with a written recommendation. Weekly reports for quarterly decisions just create fifty weeks of noise.
Kill the zombie reports. Audit which reports people actually use. If nobody has opened a report in 90 days, delete it. Not archive it. Delete it. The cost of maintaining unused reports is attention fragmentation, not infrastructure. Every report that exists is a report someone might feel obligated to check.
More Data Is Still Better
The response to this is usually: „But what if we need that data later?„
You won’t. The report that nobody opened for 90 days is not going to suddenly become critical. And if a genuinely new question arises, you can build a new report in a fraction of the time it takes to maintain a library of reports nobody reads.
Being data-driven and being data-performative are different things. One uses data to make decisions. The other collects data to feel like decisions are being made.
Good decisions require good data. But good decisions also require knowing what question you’re answering, having the authority to act on the answer, and actually making the call instead of asking for one more report.
The goal: data with a job description.
The Bottom Line
You don’t need a new dashboard. You need a decision.
The companies that move fastest are the ones where leadership defined what they’re deciding, assigned the right data to inform that decision, and gave someone authority to make the call.
The next time you’re about to request a report, write down the decision first. If you can’t, close the laptop. Go talk to a customer. Read an industry report. Do something that actually reduces uncertainty instead of deferring it.
Requesting data you don’t know how to use is procrastination with better optics.
Pick a question. Get the answer. Make the decision. Move on.
