There’s a common instinct that testing and evidence are the careful, slow option, and moving fast means skipping them. In practice, it’s usually the other way round. Testing early is what prevents the slowest possible outcome: building the wrong thing all the way to launch.

Where the “testing is slow” idea comes from

It’s usually based on a bad experience with testing done badly: a lengthy formal research phase, a report nobody reads, a round of user interviews that confirms what everyone already believed. That kind of testing is slow, and it does hold things up. It’s also not what evidence-led actually means.

What fast, evidence-led testing looks like

  • A prototype in front of five real users this week, not a research report in six weeks.
  • A single, sharp question being tested (will this specific person complete this specific task), not an open-ended “what do you think” session.
  • Evidence used to kill bad options early, when killing them is cheap, rather than discovering they were wrong after they’ve been built.
  • A decision made the same day the evidence comes in, not filed for a later review meeting.

The actual trade-off

The real choice isn’t fast versus evidence-led. It’s: find out early, cheaply, whether an idea works, or find out late, expensively, after it’s been fully built. The second path feels faster at the start, because nothing is slowing down the build. It’s almost always slower overall, because the cost of being wrong lands after the most expensive work is already done.

Why this is how we work

This is the actual logic behind the two pillars we build every engagement around: make real progress fast, and make decisions with evidence, not opinion. They’re not in tension. Evidence gathered fast is what lets you move fast with confidence, instead of moving fast and hoping.

Want to test a real idea properly, without losing months to it? Get in touch.

← Back to all insights