Insights

How to Separate Facts from Assumptions in a Business Decision

Most bad business decisions aren't caused by bad facts. They're caused by assumptions that quietly get treated as facts — repeated often enough, by confident enough people, that no one stops to ask where they actually came from.

Why this happens

In conversation, a stated belief and a verified fact sound identical. "Growth is accelerating" and "MRR grew from €10K to €15K over 90 days" can appear in the same sentence with equal confidence, but only one of them is checkable. Once a belief enters a discussion unchallenged, it tends to get treated as settled — especially under time pressure, which is exactly when high-stakes decisions get made.

Example. "Our churn is fine because customers seem happy" is an assumption. "Monthly churn was 4.2% over the last quarter, per billing records" is a fact. Both might get stated with the same tone in a meeting — but only one holds up if someone asks for the source.

A simple test

For any claim driving a decision, ask: could I point to where this came from? A specific document, a data export, a dated conversation. If the honest answer is "it's just what I've been assuming" or "that's what it feels like" — it's an assumption, not a fact, and should be labeled as one before the decision is made.

Why the distinction matters more under pressure

Assumptions aren't inherently bad — every decision requires some. The problem is when they're invisible. A decision built on five facts and three unlabeled assumptions looks identical, on the surface, to one built on eight solid facts. Only one of them should carry the same confidence.

A practical process

This is the same discipline Ascendra applies automatically to every decision report: every claim is tagged to its source or explicitly marked as inference, so nothing is presented as fact unless it's sourced. See it applied to a real hiring decision or a real investment decision.