APIS LAB
Home/Lab/Evidence map: stop confusing confidence with fact
← All research
Lab / research note

Evidence map: stop confusing confidence with fact

A statement such as “we are 80% sure” is weak unless the team can show what evidence supports it, how strong that evidence is, what the cost of being wrong would be and which observation could change the decision.

Why “80% confident” means almost nothing by itself

Confidence is a mental state. Evidence is an observable basis for a decision. People can be highly confident because of experience, hierarchy, recent success or a persuasive presentation. That does not make the underlying claim stronger. An evidence map separates the claim from the source and records whether the support is a document, repeated observation, market signal or internal hypothesis.

Connect evidence directly to decisions

Do not build a research library that sits separately from management choices. Every important decision should show the assumptions it depends on, the current evidence level and the next proof required. This makes it possible to see which parts of the strategy are robust and which are still fragile.

The cost of error determines research depth

A reversible, low-cost decision can proceed with weaker evidence. A decision involving a large capital commitment, regulatory risk or long lock-in needs a higher evidence standard. This prevents two common mistakes: over-researching trivial choices and under-researching expensive ones.

Know when to stop researching

Research should stop when additional evidence is unlikely to change the decision enough to justify its cost. This is different from “we know everything”. Set an evidence threshold relative to the next action. A small pilot may require only enough proof to justify learning; a full rollout requires much more.

Use a simple evidence scale

One practical scale is: hypothesis — internal view without external confirmation; signal — one meaningful market response; observation — a pattern repeated across several cases; fact — a document, actual transaction, system data or authoritative requirement. The scale is deliberately simple so teams can use it during real decisions rather than in an academic exercise.

Practical case: changing an owner-level strategy discussion

A leadership team debates whether Market A is “clearly better”. An evidence map shows that the perceived advantage depends on two assumptions with no direct market confirmation, while Market B has a slightly lower score but stronger buyer-access proof. The discussion changes from persuasion to research design: what must be checked before the investment committee can responsibly approve the next budget gate?

30-day protocol

  • List the 10–20 claims that the current strategy depends on.
  • Label each claim by evidence strength and owner.
  • Add the cost of being wrong and the reversibility of the next decision.
  • Select the small set of claims where weak evidence meets high error cost.
  • Design one observation or test for each and update the decision log after the cycle.

When evidence maps become governance

At investment or board level, the map can become part of the decision record. It clarifies which conclusions were supported at the time, which assumptions were knowingly accepted and what future information should trigger a review. This improves accountability without pretending that management decisions can ever be free of uncertainty.

How to use the map in an investment committee

Show the decision, the critical assumptions, evidence strength, downside of error, next proof and the proposed budget gate. The committee can then challenge the reasoning instead of arguing over presentation quality. If a large investment rests on several low-evidence claims, the right output may be a smaller validation budget rather than approval or rejection.

Practical check

  • Is the claim written clearly enough to be falsified?
  • Is the evidence external or only internal opinion?
  • Is the source current and relevant to the same segment?
  • Would new evidence actually change the decision?
  • Is the research effort proportionate to the cost of error?

Decision note

Main principle

A strong analysis makes its assumptions visible, connects evidence to a decision and defines the next observation that can confirm, weaken or close the hypothesis.

Main takeaway

The purpose of this note is not to make uncertainty disappear. It is to make the assumptions visible, connect them to a decision and define the next evidence step.