Validation

Brings problem space, prototype, and test findings together in a few days, enabling a well-founded decision.

Core question: Can a prototype test the riskiest assumption with target users?

• 4-5 Tage
• 5-8

Places tasks, sessions, and problems side by side to spot friction points and prioritize fixes.

Core question: Can relevant users complete their important tasks with the current design on their own?

• 1-2 h je Session
• Based on research question

Sorts assumptions by uncertainty and leverage so the riskiest hypotheses get tested first.

Core question: Which assumptions are critical to the idea and have the least supporting evidence?

• 45-60 min
• 2-8

Tests variants under controlled conditions, keeps the decision log clean, and summarizes results in a learning summary.

Core question: Does B produce the pre-defined meaningful effect over A without breaching guardrails?

• 1-4 Wochen
• 1-6

Analyzes the first clicks on a screen or wireframe and quickly shows whether orientation and expectation match.

Core question: Where do target users first click for this task, and what does that reveal about findability?

• 1-2 Tage
• 10-30

Collects answers in a scalable format and condenses them into results, charts, and segment insights.

Core question: What can this population reliably report that informs the stated decision?

• 3-14 Tage
• 50+

Clarifies customer problems, solution ideas, and evidence by framing problem hypotheses, recruiting the target group, and assessing problem risk.

Core question: Which real problem matters enough to this target group that they already act on it?

• 30-60 min je Interview
• 5-12 Interviews

Clarifies customer problems, solution ideas, and evidence by preparing a solution concept, recruiting target customers, and deriving risks and next tests.

Core question: Does the person understand the approach, and what evidenced progress could it enable in their actual context?

• 30-60 min je Interview
• 5-10 Interviews

Measures real interest in an idea that has not been built yet, through clicks, sign-ups, or other interest signals.

Core question: How many relevant people actually try to access this specific offer?

• 1-5 Tage
• Nutzertraffic

Simulates a solution manually to test value, effort, and user reaction before technical implementation.

Core question: How do people use this interaction when the missing technology is simulated under controlled conditions?

• 2-10 Tage
• 5-20 Nutzer

Personally guides early users through the service and shows which steps should later be automated.

Core question: Which value do people actually use when we deliver it personally?

• 1-4 Wochen
• 3-10 Kunden

Tests demand with minimal effort, reads conversion signals, and turns them into a clear learning note.

Core question: Does the defined audience choose the promised next action under realistic conditions?

• 1-5 Tage
• Nutzertraffic

Tests value proposition and offering through a landing page, so conversion data supports early product decisions.

Core question: Which variant produces the predefined action more often for the same audience?

• 1-5 Tage
• Nutzertraffic

Moves architecture context, options, and consequences toward a concrete result through "place the architecture diagram or plan in the center", "set risk categories such as technical, organizational, and external", and "assign an owner and next steps for each top risk".

Core question: Which concrete failure scenarios sit where in the architecture, which matter collectively, and how will we reduce or test them?

• 60-90 min
• 4-12

Moves customer problem, solution idea, and evidence toward a concrete result through "clarify the learning goal and the assumption to test", "formulate the hypothesis as an if-then statement", and "define the decision rule after the test".

Core question: Which critical assumption will we test through what observable behaviour, and which pre-set threshold decides?

• 30-60 min
• 1-5

Moves customer problem, solution idea, and evidence toward a concrete result through "collect assumptions explicitly", "rate uncertainty and leverage for each assumption", and "decide to pivot, persevere, or stop".

Core question: Which assumption would damage the idea most if false and currently has the weakest credible evidence?

• 1-2 Wochen pro Iteration
• 2-6

Moves customer problem, solution idea, and evidence toward a concrete result through "list assumptions", "map assumptions to dimensions", and "derive the test plan".

Core question: Which smallest test provides enough evidence for each critical assumption to support the next investment decision?

• 45-75 min
• 2-8

Validation shapes define required classes, properties, and constraints before graph data enters production pipelines.

Core question: Which RDF structure must hold for the use case, and how is each violation reported?

• Halber Tag pro Domain Slice
• 1-4

Build Measure Learn cycles turn risky assumptions into experiments that support persevere, pivot, or stop decisions.

Core question: What smallest experiment creates decision-ready learning about the riskiest assumption?

• Wochen bis Monate je Lernzyklus
• 2-8

Tests a market claim with the smallest fitting precursor and makes real interest measurable.

Core question: Does the target audience show real behaviour for this idea before we build it?

• Stunden bis wenige Tage
• 1-4

A fast venture-style triage that tests whether an idea has a clear problem, paying customer, differentiated solution, and plausible market.

Core question: Is the venture thesis understandable in five minutes, and where is decision-relevant evidence missing?

• 5-15 min
• 1-5

Condenses hypothesis, test, metric, and success threshold onto one card before execution.

Core question: How will we test this critical assumption with a clear test, a suitable metric, and a success threshold set in advance?

• 20-35 min
• 1-5

Separates hypothesis, observation, insight, and next action into four fields after a test.

Core question: What did we actually observe from this test, what may we learn from it, and what action follows?

• 25-40 min
• 1-5

Developers try a preliminary technical design through typical tasks, showing what makes it easy or difficult to use.

Core question: Can developers accomplish their important tasks using this preliminary design?

• 2–4 h review as a planning range; preparation and evaluation additional
• Designers, developers as users, and facilitation