View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture Quality Attribute Workshop | ![]() Innovation Lean Startup | ![]() Product Discovery Pretotyping |
|---|---|---|---|
Purposedifferent | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 2-4 h | Wochen bis Monate je Lernzyklus | Stunden bis wenige Tage |
Participantsdifferent | 5-15 | 2-8 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision |
Tagsno overlap | RequirementsArchitectureWorkshop | LeanStartupValidationMVP | ValidationDemandMVP |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






