Opinions are cheap. Evidence is rare. The difference between a team that grows and a team that just moves is whether they can tell which one of their opinions is correct. Experimentationis the discipline that turns “I think” into “we tested.” It is the most important habit a small company can build, and the one that, once you have it, makes everything earlier in this series feel like a warm-up.
This is the last lesson in the prerequisite series. The next thing in front of you is the digital marketing field guide, where the channels, the analytics, and the operator playbooks live. Everything in there assumes you understand what an experiment is and why you would bother running one. This lesson is the bridge.
// 01Why opinion-driven growth fails
It is easy to spot in retrospect. Every team that has ever lost a year to a bad bet did the same three things, in roughly the same order.
- A confident person made a confident claim: Sometimes a founder, sometimes a new hire, sometimes a consultant. The claim was specific enough to act on but not specific enough to verify.
- The team executed the claim: They built the feature, ran the campaign, hired the role. Nobody wrote down what success or failure would look like, because nobody asked.
- The result was ambiguous: Some numbers went up, some went down, some stayed the same. The original claim was now interpreted to fit whatever happened. Nobody learned anything. The next confident claim got the same treatment.
// 02What an experiment actually is
An experiment is a written agreement with yourself, in advance of doing anything, about what you expect to happen and how you will know if you are wrong. It has four parts. Together they are sometimes called the experiment contract.
- A hypothesis: A claim about cause and effect, in plain language. "If we change the homepage hero from feature-led to outcome-led, paid signups will increase from 2.4% to over 3.0% within four weeks."
- A metric: The single number that will tell you whether the hypothesis was right. One metric, not five. The easiest experiments to read are the ones with the fewest moving parts.
- A success threshold and a kill threshold: The values of the metric that mean "ship it" and "stop now." Set in advance, before any results are visible.
- An end date: A specific day on the calendar. Without one, experiments drift; the team keeps watching numbers move and never decides anything.
Each of those is unremarkable on its own. Together they are the difference between running an experiment and being busy. A team that writes these down before they act, and reads them back when the results arrive, makes better decisions than a team that does not, regardless of how smart either team is.
// 03The contract is the whole point
It is tempting to think the experiment is the change you made: the new homepage, the new ad creative, the new pricing page. The change is not the experiment. The contract is the experiment. The change is the bet you are placing.
- It forces honesty up front: When you have to commit to a kill threshold before any data exists, you will catch yourself in any unconscious wishful thinking. Most teams discover their hypothesis was vaguer than they realized as soon as they try to write the threshold.
- It removes politics from the verdict: The decision to ship or kill is not a meeting. It is a comparison between a number and a value you wrote down two weeks ago. People can disagree about strategy; they cannot disagree with arithmetic.
- It compounds: A team that has run thirty experiments knows things a team running its first one cannot know, no matter how clever they are. The contract is what makes the learning bankable.
// 04The difference between testing and trying
Most teams describe themselves as “testing things.” In practice almost all of what they are doing is trying things. The two look identical from the outside and feel identical for the first few weeks. The difference shows up later.
- Trying produces motion: You change something, watch the dashboards, form an opinion, change something else. Activity is high. Learning per unit of activity is low. After a year, the same arguments come back; nothing has been settled.
- Testing produces evidence: You write down what you expect, run the change, read the result against what you said in advance, and make a clean decision. After a year, a list of resolved questions has accumulated. Each new experiment can stand on the ones that came before.
The bar for being able to call something a test is low: write down the four parts of the contract before you start. The bar is also surprisingly hard to clear, because it requires you to be specific about something you would rather keep flexible.
// 05Why experimentation gets harder, not easier, as you grow
It is worth knowing this in advance, because it is counterintuitive. Once a company has revenue, customers, and a brand, the cost of changing things goes up. The number of people with opinions also goes up. Without a habit of running experiments, decisions get slower and worse over time, not faster and better.
- More to lose: A redesign at five customers is fun. A redesign at five thousand customers is a project with stakeholders. Without a contract, the project becomes a negotiation; with a contract, it stays a question.
- More opinions to coordinate: Sales has a view, marketing has a view, product has a view. The contract is the only way to give those views something to disagree about that does not waste a quarter.
- More noise to read through: The numbers move on their own at scale. You will see swings that have nothing to do with what you changed. The threshold-set-in-advance is what protects you from reading meaning into noise.
// 06Where to go next
You have the prerequisites. The rest of the resources at Xi assume you know what an experiment is, why an experiment contract matters, and why running them on purpose beats guessing. Two next steps are worth taking, in either order.
- The digital marketing field guide: Ten in-depth lessons on channels, analytics, buyer psychology, SEO, email, paid ads, social, GTM, conversion optimization, and the marketing layer for product managers. Each one ends with one or two experiments you can run today.
- Your first experiment in Xi: The product is built around the contract: hypothesis, metric, success and kill thresholds, end date. Picking a single change you have been considering and committing to one as a real experiment is the fastest way to feel the difference between testing and trying.
// 07Five things to carry forward
- 01: Opinions are cheap. The team that grows is the team that knows how to tell which of its opinions are correct.
- 02: An experiment is a written contract with four parts: a hypothesis, a metric, success and kill thresholds, and an end date. Set before any change is made.
- 03: The contract is the experiment, not the change. The change is the bet. The contract is what turns the bet into evidence.
- 04: Testing and trying look the same for two weeks and different forever after. The difference is whether the team has a habit of writing down what they expect.
- 05: Start small and start now. The earlier the habit forms, the more it compounds. Every later decision in your career becomes easier the longer you have been running real experiments.
That is the prerequisite. Everything from here is the actual work: picking a channel, writing the copy, running the campaign, reading the result, deciding what to do next. Done with discipline, the work is honest, slow, and almost embarrassingly effective. Done without it, it is a treadmill at any size of company. The two next steps in the box below pick up exactly where this leaves off.
You have the fundamentals. Now do the work.
Two next steps. The field guide goes deeper on every channel. The product lets you pick a hypothesis and run a real experiment in under five minutes.