Business Experiment Template (A4 Workshop Sheet)
A printable A4 sheet for designing a business experiment: the assumption, hypotheses with targets, the decision rule, the test, then the result. CC BY-SA 4.0.
Join free to downloadInnovation Toolkit / Business Experiment Template
The Business Experiment Template
A structured framework for designing controlled experiments that test critical hypotheses with real users in real conditions, before committing significant resources. Surface silent assumptions, collect real-world evidence, and make informed go/no-go decisions. It works as an experiment plan and a test card in one: the assumption, the hypotheses with their targets and the decision rule, written before any data arrives.
Free PDF · Perpetual licence on the editable toolkit · Students and educators: claim your academic licence
What Is a Business Experiment?
A business experiment is a structured method for testing predefined hypotheses through data collected via a controlled, repeatable process involving a defined audience. Business experiments involve actual customers interacting with realistic prototypes in real market conditions. The objective is to produce evidence-based conclusions that inform decisions about whether to pursue, pivot, or park an opportunity.
Innovation Needs Novelty: and Novelty Brings Unknowns
Uncertainty and risk are, by definition, at the core of the innovation process. Even carefully evaluated opportunities carry known or unknown "unknowns" that can prove to be critical success factors. Projects and initiatives often embed silent assumptions, beliefs and certainties that things will work in a particular way, adopted as obvious without being challenged or tested. These manifest as unchallenged statements about the effectiveness of a solution, the demand for a product, user behaviour, pricing models, or adoption patterns.
When assumptions are left unaddressed, a decision to build a product without testing them can lead to failure that incurs financial, cultural, and opportunity costs. Business experiments flip this sequence: identify the riskiest assumptions, convert them into testable hypotheses, and gather real-world data that reduces uncertainty, before committing significant resources. This is the validation node of the innovation lifecycle: the bridge between a promising business idea and a development-ready product concept.
Created by George Krasadakis, the Business Experiment Template is a central element in the corporate innovation function and a thinking framework at the core of the experimentation mindset. It is one of the frameworks used in innovation advisory and AI strategy engagements with global companies. A successful business experiment provides clarity through real-world data and informs important decisions, regardless of whether the decision is positive or negative.
Six Elements of a Well-Designed Business Experiment
The template guides teams through six essential components that together form a sound, repeatable experiment design. Each element has a specific purpose: surface assumptions, define learning goals, choose the testing vehicle, recruit a valid audience, set guardrails, and pre-commit to decisions.
01
Experiment Identifiers
The signature of the experiment: a unique identifier, informative title, codename, description, and ownership. The experiment owner is accountable for the design, execution, and reporting of results. Establishes what and who owns it.
02
Learning Goals
What the team is trying to learn, stated as a narrative and a structured list of hypotheses. Each hypothesis includes a name, description, and threshold metrics representing the belief being tested. Also defines success criteria: when the experiment as a learning mechanism delivered on its purpose, regardless of whether hypotheses are validated or invalidated.
03
Form Factor
The type of experience served to the audience, what participants will interact with. Options include a landing page (measuring visitor engagement), a clickable prototype (testing usability), a functional prototype (capturing interaction data), a physical prototype (hands-on testing), or a proof of concept (demonstrating technical feasibility). Establishes the vehicle.
04
Audience
A carefully designed list of demographics, each with a communication channel and target sample size. The audience must be representative enough for results to be meaningful and actionable. Establishes the who participates and how they are acquired.
05
Planning
The experiment timeline: launch checklist, launch date, end date, and end conditions: a set of conditions over specific performance metrics that signal early termination. For example, when engagement falls below thresholds even after intervention. Establishes the when and the guardrails.
06
Decisions
Think a few steps ahead: what should happen on success or failure? A description of potential next steps for each primary outcome, along with key stakeholders. Pre-defining decisions brings alignment and clarity before results arrive, preventing political escalation when data is uncomfortable. Establishes the so what.
In-Product vs. Out-of-Product Experiments
Business experiments fall into two broad categories depending on whether they run inside an existing live product or independently. The distinction matters because each category has different recruitment, instrumentation, and decision-making implications.
In-Product Experiments
Delivered from within a live product to a subset of users. The system tracks engagement statistics to identify winning variants. Includes A/B testing (two or more versions of a feature), multivariate testing (evaluating multiple elements simultaneously), feature experiments (adding or removing features for specific user segments), and pricing experiments (testing different price points or models).
Out-of-Product Experiments
Conducted independently: either because the product doesn’t exist yet or to avoid disrupting a live product. Includes functional prototypes (realistic implementations designed to test hypotheses), smoke testing (landing pages measuring interest before building), and service simulation methods like Wizard of Oz (simulating functionality manually) and Concierge Testing (transparent human-delivered service).
The Template in Action: Four Innovation Experiments
Each example demonstrates how the six-element framework converts silent assumptions into structured, testable hypotheses, producing the real-world evidence teams need to make informed decisions. These experiments typically follow a well-described business idea that has passed initial evaluation.
Validating Demand for an AI-Powered Expense Categorisation Feature
Learning GoalsThe silent assumption: finance teams will prefer AI auto-categorisation over manual expense coding. Learning objective: determine whether mid-market finance teams would adopt the feature, and whether it reduces processing time enough to justify integration effort. Hypothesis: if teams are shown AI-categorised expenses with 90%+ accuracy, at least 60% will prefer the automated workflow. Success criteria: the experiment delivers a clear signal on adoption intent and time savings, regardless of whether the hypothesis is validated.
Form Factor & AudienceOut-of-product experiment using a Wizard-of-Oz approach: participants submit 5 real expense reports through a clickable prototype interface; categorisation is performed by a human analyst using the proposed algorithm logic, presented as automated. 40 finance professionals from 12 mid-market companies (200–2,000 employees), recruited through existing customer relationships. Within-subjects design comparing automated vs. manual workflows.
Metrics & End ConditionsPrimary metrics: categorisation acceptance rate (% of suggestions accepted without override), time-per-report (automated vs. manual), and post-task preference score. Threshold: 60%+ acceptance rate and 50%+ time reduction signals "go." Below 30% acceptance at any accuracy level signals "kill." End condition: early termination if first 15 participants show less than 20% acceptance: the hypothesis is clearly invalidated.
DecisionsOn success: advance to product concept definition and scope the MVP with ERP integration. On failure: investigate whether the objection is trust-based (fixable with explainability features) or fundamental (users prefer control). On ambiguous results: design a second experiment with a functional prototype and longer engagement period.
Testing Willingness to Pay for a Real-Time Sustainability Dashboard
Learning GoalsThe silent assumption: sustainability managers will pay a premium for real-time carbon tracking over annual audit-based reports. Learning objective: validate the pricing hypothesis and identify the price sensitivity threshold before building the full product concept. Hypothesis: at least 40% of sustainability managers will express purchase intent at €75K/year after seeing a demo of real-time vs. annual reporting. Success criteria: a clear price sensitivity curve and at least 5 pilot commitments.
Form Factor & AudienceOut-of-product experiment using a clickable prototype and structured pricing interviews. 25 sustainability managers and supply chain directors at consumer goods companies ($500M+ revenue), recruited through targeted LinkedIn outreach and industry conference networking. Each session: 30-minute interactive demo followed by Van Westendorp price sensitivity analysis and a concrete commitment ask for a paid pilot.
Metrics & End ConditionsPrimary metrics: stated purchase intent (% at each price tier), paid pilot commitment rate, and Van Westendorp acceptable price range. Success threshold: 40%+ intent at €75K, 25%+ pilot commitment. End condition: if first 10 interviews show less than 15% intent at any price, pause and redesign the value proposition before continuing. Planning: 6-week experiment window, 3 interviews per week.
DecisionsOn success: proceed with functional prototype development targeting the validated price tier. On partial success (interest but price resistance): test a lower price point with expanded feature scope in a follow-up experiment. On failure: pivot the offering toward regulatory compliance use case (EU CSRD mandates) rather than voluntary adoption. Key stakeholders: product lead, CFO, head of partnerships.
Measuring Engagement with AI-Personalised Learning Paths
Learning GoalsThe silent assumption: AI-personalised learning paths will improve completion and skill acquisition in corporate training. Learning objective: determine whether personalisation translates into measurable learning outcomes, not just engagement vanity metrics. Hypothesis: AI-personalised paths will increase course completion by at least 30% and assessment scores by 15% vs. the standard curriculum. Success criteria: statistically significant differences between treatment and control cohorts.
Form Factor & AudienceIn-product A/B test running within the enterprise client’s existing LMS. 200 employees across 4 business units, split into matched cohorts (100 treatment, 100 control) based on role, tenure, and prior training participation. Treatment group receives AI-personalised paths generated from HR data, skill assessments, and learning history. Control group receives the standard curriculum through the same LMS interface. Duration: 8 weeks.
Metrics & End ConditionsPrimary metrics: course completion rate (%), time-to-completion (days), post-module assessment scores (%), and learner satisfaction NPS. Secondary: optional resource access rate and manager-reported skill application at 30 days. End condition: if week-4 completion rates show less than 10% difference between cohorts, extend to 12 weeks before concluding. Planning: launch checklist includes LMS tracking configuration, cohort randomisation, and baseline assessment completion.
DecisionsOn success: build the personalisation engine as a standalone product for enterprise L&D and begin product concept development. On partial success (engagement up but scores flat): investigate whether content quality, not delivery format, is the bottleneck. On failure: the personalisation approach doesn’t justify infrastructure investment, pivot to lighter-weight recommendation features. Key stakeholders: L&D director, CHRO, product team.
Validating a Subscription Model for On-Demand Innovation Workshops
Learning GoalsThe silent assumption: innovation managers would prefer a subscription model for facilitated workshops over one-off project-based pricing. Learning objective: test whether the subscription model generates higher lifetime value and whether usage patterns sustain beyond the novelty period. Hypothesis: at least 35% of prospects will prefer subscription (€2,500/month for up to 4 sessions) over per-session pricing (€3,000/session), and subscribers will book 3+ sessions/month on average.
Form Factor & AudienceOut-of-product concierge experiment: participants select their preferred pricing model on a landing page, and the first 10 subscribers receive 2 months of actual facilitated innovation workshops delivered manually, no platform needed. 30 innovation managers and R&D heads at companies with 1,000+ employees, recruited from the Innovation Mode newsletter and LinkedIn network. Post-experiment interviews capture satisfaction and renewal intent.
Metrics & End ConditionsPrimary metrics: model preference split (% subscription vs. one-off), session booking frequency per subscriber, NPS at 60 days, and renewal intent. End condition: if landing page generates fewer than 5 subscription sign-ups in the first 3 weeks, revise the value proposition and re-launch. Planning: 10-week total, 2 weeks acquisition, 8 weeks delivery.
DecisionsOn success: build the scheduling and delivery platform and scale the subscription offering. On partial success (preference exists but usage drops after month 1): test a lighter commitment tier (2 sessions/month at lower price). On failure: retain the one-off model and invest in upselling multi-session packages instead. Key stakeholders: founder, head of advisory, finance.
Hypothetical experiments written to illustrate how the six-element framework applies across industries, not based on any specific company or engagement.
Notice how each experiment defines success and failure criteria before running, not after. The hypothesis includes a specific threshold below which the team changes direction. An experiment that provides strong real-world evidence to "kill" an opportunity is a successful one: it saves the organisation from a costly misdirection. Once validated, ideas progress to a full product concept.
From Silent Assumption to Validated Learning
The Business Experiment Template is used after an idea has been described and evaluated, but before significant development resources are committed. A typical process:
1
Surface the silent assumptions. Review the "Big Unknowns" from the Business Idea. Identify beliefs that are adopted as given without being challenged. Convert them into testable hypotheses with specific thresholds.
2
Design the experiment. Fill in all six sections: identifiers, learning goals with hypotheses, form factor, audience, planning with end conditions, and pre-defined decisions for each outcome.
3
Run, measure, decide. Execute the experiment, collect real-world evidence against your predefined metrics, and make a clear go/no-go decision. Validated ideas progress to the Product Concept stage.
Organisations that adopt a culture of structured experimentation make better investment decisions, kill bad ideas earlier, and reach product-market fit faster. The Business Experiment Template makes experimentation repeatable (not ad hoc) ensuring every test produces learning, not just activity. The experimentation approach changes the perception of "failure" within the company: people are encouraged to test new ideas, and gradually accept failure simply as an outcome that didn’t make it to the next stage, due to clear and objective justification.
About the Business Experiment Template
Common questions on innovation experimentation, drawn from practitioner experience and the methodology in Innovation Mode, Chapter 7.
What is a business experiment in innovation?
A business experiment is a structured method for testing predefined hypotheses through data collected via a controlled, repeatable process involving a defined audience. It involves actual customers interacting with realistic prototypes in real market conditions. The objective is to produce evidence-based conclusions that inform go/no-go decisions about innovation opportunities, before committing significant resources to development.
What are silent assumptions and why are they dangerous?
Silent assumptions are beliefs and certainties embedded in innovation projects that are adopted as given without being challenged or tested. They manifest as unchallenged statements about user behaviour, market demand, pricing models, or adoption patterns. When left unaddressed, they introduce hidden risks that can lead to costly failures. Business experiments convert silent assumptions into testable hypotheses, turning hidden risk into measured, manageable uncertainty.
What are the six elements of the Business Experiment Template?
The template covers six elements: (1) Experiment Identifiers: title, codename, ownership; (2) Learning Goals: objectives, structured hypothesis list with thresholds, success criteria; (3) Form Factor: the experience served to participants (landing page, prototype, PoC); (4) Audience: demographics, channels, sample sizes; (5) Planning: dates, launch checklist, end conditions; (6) Decisions: pre-defined next steps for each outcome.
What types of business experiments can I run?
Business experiments fall into two categories. In-product experiments run within a live product: A/B testing, multivariate testing, feature experiments, and pricing experiments. Out-of-product experiments run independently: functional prototypes, smoke testing (landing pages), and service simulation methods like Wizard of Oz and Concierge Testing. The right type depends on the hypothesis, the audience access, and whether the product exists.
How is this different from Lean Startup or Strategyzer’s Test Cards?
The structured-experimentation space includes Lean Startup (Eric Ries), Strategyzer’s Test Cards (Alex Osterwalder), Pretotyping (Alberto Savoia), and Continuous Discovery (Teresa Torres), all valuable frameworks. The Business Experiment Template is complementary, with three specific differences: (1) integration into a complete innovation lifecycle: it is the validation node between the Business Idea and Product Concept templates, not a standalone tool; (2) corporate enterprise positioning: built for innovation managers inside large organisations, with explicit stakeholder accountability and pre-defined decision paths that protect against political escalation; (3) published methodology grounding in Innovation Mode, which makes it suitable for environments that require credentialed frameworks (consulting, executive education, regulated industries). Use whichever framework fits: the principles overlap; the templates differ in tone and integration.
What makes a business experiment successful?
A business experiment is successful when it serves its purpose: providing clarity through real-world data and informing important decisions, regardless of whether the decision is positive or negative. An experiment that produces strong evidence to kill an opportunity is a successful one, as it saves the organisation from costly misdirection and frees resources for higher-potential opportunities. The wrong question is "did the hypothesis validate?" The right question is "did we learn enough to decide?"
How does the Business Experiment Template fit into the innovation lifecycle?
The Business Experiment sits between idea evaluation and product concept definition, it validates that an opportunity deserves to become a product. Teams first define the challenge using the Problem Statement Template, generate ideas using the Business Idea Template, score and rank them using the IM-9 Idea Assessment Model, then validate the riskiest assumptions through structured experiments. Only ideas with validated hypotheses progress to full Product Concept development.
The Validation Node Between Ideas and Products
The Business Experiment is the bridge from a promising idea to a development-ready product concept. It validates that an opportunity deserves to be built, before significant resources are committed.
Download the Business Experiment Template
Two ways to use this template: pick the one that fits how you’ll deploy it.
The methodology behind this template. Chapter 7 of Innovation Mode covers the complete opportunity validation process, from distinguishing risks vs. uncertainties, to the Business Experiment Framing Template, to building prototypes and producing validation reports. The book provides the full framework: silent assumptions, experiment types, the validation team, and the six-step validation process. 434 pages. Innovation Mode Publishing, 2026. By George Krasadakis.
Innovation Toolkit
The templates, and the worked case that shows them in use.
- The worked case: nine sample documents carrying one problem from brief to decision, with the reasoning in the margins.
- Eight editable templates: five Word documents, two PowerPoint canvases and the IM-9 Excel workbook.
- Quick Start Guide: 17 slides on the documents, the flow and daily practice.
- AI prompt kit: Markdown versions of the templates and 20 prompts, for any AI assistant.
In the toolkit this document is the Experiment Design template.
€249 one-time payment · Licensed to your whole organisation · Instant download
Designed by
Members only
From the members' library.
Membership brings you The Innovation Mode Newsletter once a month and every PDF in our library. Join free with LinkedIn
From the blog
Insights on product discovery, MVPs and prototyping
Product, MVPs and prototyping
Your Startup Idea Has Three Types of Unknowns. You're Probably Only Testing One.
Most startup post-mortems blame money, timing, or competition. But the real killer is building something nobody wants - and most of it is preventable. This article introduces the three types of unknowns every startup idea carries (risks, uncertainties, and silent assumptions), explains why most validation methods fail, and describes the Innovation Mode approach to systematic idea validation - from the Nine-Dimension Idea Assessment Model to the discipline of knowing when to stop validating and start building.
Product, MVPs and prototyping
How to Set Up and Lead a Great Product Development Team
As a product leader, you need an inspired, talented team, to believe in your product vision and work with passion towards the shared goal: a great product satisfying all the predefined success criteria, plus one more: to make the entire team proud of the outcome.
Product, MVPs and prototyping
From Deterministic to Probabilistic: Rethinking Product Requirements for the AI Era
AI products break every assumption traditional PRDs are built on. From probabilistic outputs to autonomous agents, here's why your product specification needs surgery - and what more than 25 years of building data and AI systems taught me about fixing it.