In partnership with
Wake up to better business news
Some business news reads like a lullaby.
Morning Brew is the opposite.
A free daily newsletter that breaks down what’s happening in business and culture — clearly, quickly, and with enough personality to keep things interesting.
Each morning brings a sharp, easy-to-read rundown of what matters, why it matters, and what it means to you. Plus, there’s daily brain games everyone’s playing.
Business news, minus the snooze. Read by over 4 million people every morning.
Now back to this week’s Data Drop…
There’s a moment I’ve seen play out over and over again.
A business question is on the table. Not abstract. Real. Time-bound. Impactful.
Should we invest?
Should we ship?
Should we change course?
Analytics gets pulled in (as it should). A dashboard gets spun up.
Someone asks a good question.
Then another.
Then a request for a different cut.
A longer timeframe. A cleaner cohort. “One more week, just to be safe.”
At some point, you realize something subtle has shifted -
Data isn’t helping the decision anymore.
It’s postponing it.
And no one ever says that out loud.
WHAT’S ACTUALLY HAPPENING IN THESE MOMENTS
If teams keep asking for more data, it’s rarely because the data is broken.
It’s usually because the decision hasn’t been operationalized.
When you slow it down, you’ll often find one of a few gaps underneath the surface:
The decision is still vaguely framed. Are we deciding whether to act, how much to invest, or when to move? Those are different analyses.
No one agreed in advance what outcome would justify action. Without a pre-committed threshold, every result invites reinterpretation.
Ownership is distributed but not defined. If no single person is accountable for the call, the safest default is to continue analyzing.
The required confidence level keeps drifting. What started as “directional signal” quietly becomes “statistically bulletproof.”
Without those commitments, every additional analysis feels reasonable. Every refinement feels necessary. And because there’s no agreed stopping point, there’s always a defensible argument for one more layer.
At that point, analytics isn’t clarifying the decision — it’s absorbing the ambiguity around it.
WHY “WAITING FOR DATA” OFTEN SEEMS LIKE THE RIGHT MOVE
To be clear: asking for more data is often reasonable - Rigor matters. Context matters.
Avoiding preventable mistakes matters.
The problem is that “more data” carries very little social downside. It signals diligence. It protects against being accused of rushing. It distributes responsibility across the group instead of concentrating it in a single call.
In ambiguous situations, that safety is attractive.
But if the implicit bar becomes certainty, analytics will always feel unfinished.
Data doesn’t eliminate uncertainty, it defines its boundaries. If the team has not agreed on what level of uncertainty is acceptable, the work can continue indefinitely.
There will always be another cut. Another cohort. Another lens.
Eventually, the issue isn’t whether the data is sufficient. It’s whether the group is ready to commit.
WHAT STRONG ANALYTICS PARTNERSHIP LOOKS LIKE INSTEAD
When analytics is operating at a high level, the goal isn’t to produce exhaustive analysis.
It’s to drive business decisions, even under uncertainty.
That shift shows up in a few ways:
1. The decision is framed before the data is pulled.
Not just “should we do this?” but -
What exactly is the call? What range of outcomes changes it? What is reversible?
2. A confidence threshold is discussed explicitly.
Not in statistical jargon. In business terms.
Is directional signal enough? Or is this a high-cost, hard-to-reverse decision?
3. Tradeoffs are articulated, not hidden.
If we act now, here’s the likely upside and the measurable risk.
If we wait, here’s the opportunity cost and what we expect to learn.
Notice what’s missing: perfection.
Analytics at its best doesn’t eliminate judgment. It informs it.
When the expectations are set correctly upfront, analysis helps narrow opinions to ultimately land on the decision that needs to be made.
High-performing organizations don’t wait for perfect information.
They build systems that allow them to move with incomplete information, intentionally.
That requires discipline - agreeing on what “enough” looks like, defining who decides, accepting that some uncertainty is structural.
Analytics supports that system. It doesn’t replace it.
Until next Tuesday,
- Michelle