View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Brainwriting |  Product Discovery Assumption Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|
Purposedifferent | When loud voices or hierarchy distort the idea search, the method creates a quiet entry into joint development. It gives everyone thinking space and gathers contributions without social brakes, making diversity more visible and easier to build on. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 15-30 min | 45-60 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 3-12 | 2-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Idea sheets, Expanded concepts, Prioritized list | Assumption map, Test backlog, Risk ranking | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks |
Tagsno overlap | BrainstormingCollaborationInclusionIdeas | AssumptionsRiskExperimentsValidation | ArchitectureQualityRiskAssessmentLean |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
