Blog

Measurement

Ten articles on what turns a number into a decision — prediction, attribution, timing, and the discipline of measuring on the same cycle as everything else.

01

A metric without a prediction is just a number

4% engagement means nothing on its own — good, bad, or ordinary all depend on what was expected going in. A metric only becomes information once it's compared against a prediction made before the result arrived.

That's the entire reason a hypothesis has to name a number before execution starts, not after.

02

Why vanity metrics survive longer than they should

Impressions and likes are easy to measure and reliably go up with volume, which makes them satisfying to report even when they don't move the number that actually matters. They survive because they always look like progress, not because they usually are.

03

What "underperformed" should always answer: why

A result logged as "underperformed" without a reason attached teaches nothing — the next hypothesis has no way to avoid the same mistake if the mistake was never named. "Underperformed because the angle didn't match what the segment's reviews show they care about" is a learning. The number alone isn't.

04

Attribution across a funnel that spans six channels

A sale rarely traces to one touchpoint when a brand is active across six channels — someone saw a post, later clicked an ad, eventually converted from an email. Perfect attribution is usually impossible; directionally useful attribution — which channels tend to open the funnel versus close it — is achievable and far more actionable.

05

The metric that matters changes with the goal

A brand-awareness push and a direct-response campaign shouldn't be judged by the same number. Reach matters for one, conversion for the other — measuring both by the same yardstick makes one of them look like it's failing when it's simply doing a different job.

06

Reading a flat result correctly — flat isn't always failure

A result that matches the baseline instead of beating it isn't automatically a loss. Sometimes it confirms a ceiling worth knowing about; sometimes it rules out an angle cleanly, which is its own kind of useful. The verdict depends on what the hypothesis actually predicted, not on whether the number went up.

07

Why measurement has to happen on the same cycle as execution

Results reviewed months after publishing arrive too late to inform the strategy that's already moved on to something else. Measurement synced to the same cadence as execution is what keeps a learning relevant to the hypothesis that's actually being written next.

08

Dashboards vs decisions: the gap most tools leave open

A dashboard can show exactly what happened and still leave the hardest question unanswered: what should change because of it. That translation — from a number to a decision — is usually manual work most tools stop just short of doing.

09

Setting a success threshold before the test runs, not after

A threshold set after seeing the result isn't a threshold — it's a rationalization. Deciding what counts as a win before the data arrives is what keeps the verdict honest, even when the honest verdict is disappointing.

10

What a landing page's numbers reveal that a post's can't

A post's engagement measures attention. A landing page's conversion rate measures whether the offer itself actually holds up once someone's paying full attention. The two numbers answer different questions, and a strong post with a weak landing page usually means the offer, not the hook, needs the work.