--- title: Innovation experiments description: "## Why this feature is needed Innovation work always involves uncertainty. Teams need to test assumptions, validate problems, assess [Solution](https://www.acceptmission.com/de/encyclopedia/solution/) directions, and reduce risks before moving forward with confidence. Without structured experiments, teams may rely too much on discussion or…" url: "https://www.acceptmission.com/de/knowledge/innovation-experiments/" updated: "2026-09-01" category: Innovation Studio / Innovation Intelligence (Work) --- # Innovation experiments ## Why this feature is needed Innovation work always involves uncertainty. Teams need to test assumptions, validate problems, assess [Solution](https://www.acceptmission.com/de/encyclopedia/solution/) directions, and reduce risks before moving forward with confidence. Without structured experiments, teams may rely too much on discussion or intuition. Innovation experiments help teams move from uncertainty to evidence by making validation work visible, structured, and connected to the innovation itself. ## What this feature is Innovation experiments in [Accept Mission](https://www.acceptmission.com/de/encyclopedia/accept-mission/) are part of the broader innovation intelligence feature and help teams design, plan, and track the experiments needed to validate an innovation. This feature can be used for both ideas and projects. It allows users to register all experiments related to the innovation, define what should be tested, plan when the [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) should happen, and track which [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) is the most important at a given stage. Experiments can also be connected to other innovation intelligence items such as assumptions, problems, risks, decisions, and canvases. This helps teams make sure that every [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) serves a clear purpose in the innovation process. ## Access level [Power User](https://www.acceptmission.com/de/encyclopedia/power-user/) You need access to the relevant idea or project in the Innovation Studio to work with innovation experiments. ## Navigation path Navigation path: Innovation Studio → Ideas → Open funnel → Open idea → Work → Experiments ## How to use this feature Innovation experiments are used inside ideas and projects to structure the validation work around an innovation. Teams can register experiments, define what they want to learn, plan when to run them, and connect them to the uncertainties they are meant to address. This makes it easier to focus on the right validation work and keep the innovation process evidence-based instead of [Assumption](https://www.acceptmission.com/de/encyclopedia/assumption/)-based. ### Step by step instructions 1. Open **Innovation Studio**. 2. Choose whether you want to work inside an **idea** or a **project**. 3. Open the relevant idea or project. 4. Go to the **Work** tab. 5. Open the **Experiments** tab. 6. Add a new [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/). 7. Enter the [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) title. 8. Describe what you want to test or learn. 9. Set the timing or planning details if needed. 10. Save the [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/). 11. Repeat this for all relevant experiments connected to the innovation. 12. Select which [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) should be marked as the **primary [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/)**. 13. Connect the [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) to related innovation intelligence items where relevant. ![image](http://www.acceptmission.com/wp-content/uploads/2026/04/image-43.png) ## What you can do with innovation experiments Within the Experiments tab, teams can: - **Register all experiments** related to an innovation - **Define what should be tested or learned** - **Plan when experiments should be executed** - **Track [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) progress** - **Mark the most important [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/)** as the primary [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) - **Connect experiments** to other innovation intelligence items This creates a clear overview of how uncertainty is being addressed throughout the innovation process. ## Primary [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) Not all experiments have the same importance. Some are exploratory, while others are critical for deciding whether the innovation should move forward at all. That is why you can define one [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) as the **primary [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/)**. This helps the team focus on the validation activity that delivers the most important insight at that moment. ![image](http://www.acceptmission.com/wp-content/uploads/2026/04/image-44.png) ## Connecting experiments to other items A key strength of this feature is that experiments can be linked to other innovation intelligence elements, such as assumptions, problems, risks, decisions, and canvases. This creates a connected workflow where experiments are directly tied to what needs to be validated. For example: - An [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) can validate a critical [Assumption](https://www.acceptmission.com/de/encyclopedia/assumption/) - An [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) can test whether a [Problem](https://www.acceptmission.com/de/encyclopedia/problem/) is real and relevant - An [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) can reduce a specific [Risk](https://www.acceptmission.com/de/encyclopedia/risk/) - An [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) can support a [Decision](https://www.acceptmission.com/de/encyclopedia/decision/) on whether to proceed This connected structure improves traceability and ensures experiments are always purposeful. ![image](http://www.acceptmission.com/wp-content/uploads/2026/04/image-45.png) ## Examples of experiments Common types of experiments include: - **Customer interviews** - **Surveys** - **Prototype testing** - **A/B testing** - **Pilot implementations** - **Landing page tests** - **Desk research** Each [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) should be designed to answer a specific question or validate a specific uncertainty. ## How this supports the team Innovation experiments help teams move from assumptions to evidence. This is especially useful for: - **Structuring validation efforts** - **Focusing on the most critical uncertainties** - **Avoiding solutions built on untested ideas** - **Improving the quality of [Decision](https://www.acceptmission.com/de/encyclopedia/decision/)-making** - **Maintaining momentum** by turning uncertainty into clear next steps ## Innovation intelligence feature page Innovation experiments are one of the tools within the broader [Innovation intelligence](http://www.acceptmission.com/support/innovation-intelligence/) feature. This broader feature helps teams capture structure, insights, decisions, and learning directly inside ideas and projects. ## Configuration and adjustments Innovation experiments are available in both ideas and projects, which means the same structured validation approach can be used during exploration and during execution. To work with this feature in ideas, follow this path: **Navigation path: Innovation Studio → Ideas → Open funnel → Open idea → Work → Experiments** To work with this feature in projects, follow this path: **Navigation path: Innovation Studio → Projects → Open project → Work → Experiments** To keep this feature useful, teams should define experiments with a clear learning goal and connect them to the [Assumption](https://www.acceptmission.com/de/encyclopedia/assumption/), [Problem](https://www.acceptmission.com/de/encyclopedia/problem/), [Risk](https://www.acceptmission.com/de/encyclopedia/risk/), or [Decision](https://www.acceptmission.com/de/encyclopedia/decision/) they are meant to support. This improves focus and makes the validation process easier to review later. ## Practical example – Innovationlands Innovationlands is exploring a new guest experience concept for reducing frustration in park queues. The team has identified several assumptions about guest behavior, a few important risks around adoption, and different possible [Solution](https://www.acceptmission.com/de/encyclopedia/solution/) directions. Inside the idea, the team opens the **Experiments** tab in the **Work** area and registers a set of experiments, including guest interviews, a simple prototype test, and a small pilot with one attraction queue. They decide that the prototype test is the most important activity at this stage and mark it as the **primary [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/)**. The team also connects this [Experiment](https://www.acceptmission.com/de/encyclopedia/experiment/) to the main [Assumption](https://www.acceptmission.com/de/encyclopedia/assumption/) about guest willingness to use the concept and to a [Risk](https://www.acceptmission.com/de/encyclopedia/risk/) about operational feasibility. This helps Innovationlands keep its validation work focused and evidence-based before deciding whether the innovation should move into a larger pilot or project phase.