CORE COURSE / 053

Testing an Idea Before Making a Big Commitment

Design a small, honest experiment that tests the riskiest assumption before you invest heavily in an idea.

What you will learn

  • Identify one assumption whose failure would undermine the idea.
  • Choose a test with a budget, deadline, and observable result.
  • Interpret outcomes without moving the success criteria afterward.

Find the uncertainty that matters most

An idea may depend on several assumptions: people experience the problem, they will choose your offer, you can deliver it, and the price can support the costs. List these assumptions separately. Ask which uncertain one would most seriously undermine the plan if false. Testing logo preferences is of little use if you do not know whether anyone needs the service. Choose one question for the next experiment. A focused test will not validate the entire business, but it can resolve an important uncertainty. Write the hypothesis in observable terms, including the kind of customer and the action you expect.

Choose the smallest honest test

The test should resemble the real decision or use closely enough to teach you something. You might manually deliver a service to a few people, demonstrate a simple prototype, or ask for a clearly described pilot commitment. Be transparent about what exists and what remains experimental. Do not pretend that a mockup is a working product or take payment for something you cannot responsibly deliver. Explain timing, scope, and any cancellation arrangements. The smallest useful test is not necessarily the cheapest-looking version of the whole product. It is the simplest way to observe the behavior relevant to your chosen assumption.

Set limits and criteria in advance

Write the time limit, maximum cost, intended participants, and decision rule before starting. For a hypothetical service trial, you might seek three completed sessions from eight suitable people contacted over two weeks. Those numbers are a local learning rule, not a universal benchmark. Define what counts as completion and what additional evidence you will collect, such as delivery time and participant use afterward. Limit the potential harm and inconvenience of failure. Avoid testing important health, legal, financial, or safety claims through casual experiments. Some ideas require professional review and formal processes before real-world use can be appropriate.

Learn without declaring premature victory

Review the result against the original rule, then examine why it happened. Interest without participation may reveal friction, weak need, unclear trust, or a poor invitation. A positive result among friends may not generalize to unfamiliar customers. Delivery success may conceal excessive manual effort that would make the service unsustainable. Record both outcome and limitations. Choose one of three actions: repeat with a specific improvement, investigate a different assumption, or stop. Do not quietly lower the threshold after disappointing results just to preserve enthusiasm. Equally, one small negative test does not prove that every version of the underlying idea is worthless.

Preserve the simplest record that another person could understand: who was eligible, what was offered, what happened, and what changed afterward. This makes the learning inspectable and reduces selective memory. You do not need a complicated dashboard; a dated table with clear definitions can be enough for a small, bounded experiment.

FICTIONAL PRACTICE CASE

Fictional case: Sam tests a service manually

Sam wants to build an app that organizes neighborhood pickup requests. Before paying for development, he tests whether a small group will follow a shared collection schedule. He explains that the trial is manual, lasts two weeks, and covers only a few ordinary items. His success rule requires three completed pickups without repeated reminders. Four people express interest, but only one follows through. Sam records the result instead of counting compliments as success. Conversations reveal that the fixed pickup time is inconvenient. He chooses one revised schedule test, with the same spending cap, before making a larger commitment.

Write a one-page experiment

  1. List your major assumptions and select the riskiest uncertain one.
  2. Define a small transparent test and the behavior you will observe.
  3. Set a time limit, spending cap, participant criteria, and decision rule.
  4. Afterward, record the result, limitations, and whether to revise, proceed, or stop.

Check your understanding

Your test misses its stated threshold, but participants compliment the idea. What should you do?

Further reading

My notebook