Case studies

Case studies · How we check a case

How we check a case.

Every case here is MindPalace’s own output on one business’s data, checked before it is written up. This page says where the numbers come from, what we check, and what the marks in a case mean.

Where the numbers come from

Each case rests on runs of the product whose every response was saved as it came back: the series, each part’s change with its 95% interval, the queries, the product’s confidence and its reasons, and whether a person had reviewed the definition. A tool reads the saved responses, checks them and writes each case’s figures to a file; the pages show only what those files hold.

What we check before a case is written

What the marks mean

The kinds of statement in a case, told apart by form. A figure carries at most one mark; plain means the run returned it.

Observed

What the run returned, as the record has it. The default, so it carries no mark.

Calculated

Worked out from figures the runs returned, such as what churn took for every $100 of new revenue. The working is in the case’s full analysis; the double rule is the total’s.

Checked against a source

Confirmed independently: an independent count of the same data, the parts adding up, or the product’s own definitions.

might be zero

Uncertain

Still open: a change whose 95% interval crosses zero, or a figure that rests on one.

the joins follow

Ours, not data

Pencil: a note of ours, such as where a query is cut short. Never a figure.

"severe retention cliff"

Written by the product’s AI

The product’s own summaries and proposals, quoted as they are: written after the numbers, never checked against them.

approved

A person decided

Brass, and only where the record shows a person decided: here, approving what a metric counts.

Proposed decision

Proposed, not taken

What we’d decide from the evidence, dashed and never brass, because no person has taken it.

The data behind these cases

Nimbus is a company the team generated for demos, with subscriptions on Starter, Pro and Enterprise plans. Its data describes no real company: what holds in it is a fact about that data, not evidence about a market.

AdventureWorks is Microsoft’s sample database of a bicycle maker. Its figures, and its dates, are the sample’s own; Microsoft’s public copy moves the dates later, and for our follow-up we moved them back.

No case here uses a customer’s data yet. A customer story will need the customer’s figures, their consent, and a person who decided something.

Corrections

When a case turns out to be wrong, we correct it on its page and say what changed and when.