How to test an idea

Before you start

You're probably testing already: a pricing page, an onboarding change, an outreach channel, a pilot. What breaks is usually around the test, not the test itself:

Success criteria get set after the results come in.
Tests live in docs, spreadsheets and chat, so nobody can see what's running.
Nobody remembers why a call was made, and the same idea comes back a quarter later.

This method gives every test the same four steps. They work with a spreadsheet; SwiftCNS drafts each step, you make every call, and it keeps the record. Use it when an idea would cost real time or money: a feature, a price, a channel, a quarter's roadmap. Skip it for choices that are cheap to reverse.

Steps

Find the assumption
Every idea depends on something being true. Write down the one that would sink the idea if it turned out false. Read more.
Set the success criteria
Decide what result counts as success, a number to reach in a set sample and time, before anything runs. Don't change it once results come in. Read more.
Run the smallest experiment
Test the assumption on a slice: a few customers, one market, a few weeks. Cheap enough to run now, real enough that a miss would change your mind. Read more.
Decide, and record why
Say whether the result met the criteria and what you learned. Then a person decides what happens next, and writes down why. Read more.

Who does what

Step	SwiftCNS proposes	You decide
1. Find the assumption	Assumptions scored for importance and evidence; hypotheses with provisional success criteria	Which assumption and which hypothesis to test
2. Set the success criteria	Experiment designs scored for setup, run time, cost and data reliability, each with success criteria	Which design, who owns it, by when; approving it fixes the criteria
3. Run the smallest experiment	What one tracker row should be, and its columns	Running it, logging the evidence, completing the tracker
4. Decide, and record why	Observations and insights from the evidence	The result (Met, Not met or Unclear), what you learned, and the decision

SwiftCNS suggests where to start when it proposes options, and drafts an assessment of the evidence. It never sets the result or the decision for you: neither is chosen until you choose it, and the decision form shows no recommendation. Your AI tool is where you ask; it acts on your behalf only for what you tell it to do.

What you get

One worked example runs through every step page: a SaaS company deciding whether to build a $79/month Team plan. It's sample data from a real SwiftCNS run. The result was Met, and the team chose Move forward.

Done when

You can name the four steps and what each one produces.
You know which step your current idea is stuck on.

Common mistakes

Testing the comfortable assumption. The one you're sure of teaches you nothing.
"We shipped it" as evidence. Shipping is an activity, not a result.
No end date. Experiments without one drift into "still running".