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 Rolestorming | ![]() Innovation Brainstorming | ![]() Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|
Purposedifferent | When a search for ideas stalls, switching roles helps people step outside their own perspective and activate new logics of action. The method reduces habit because contributions arise from a different stance. This brings unfamiliar, often fitting solution approaches into play. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | 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 | Low | Medium |
Timedifferent | 30-60 min | 30-60 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 3-12 | 4-12 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Rollenkarten, Ideenpool pro Rolle, Konsolidierte Shortlist | Idea pool, Theme clusters, Shortlist | 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 | BrainstormingIdeationCreativity | BrainstormingIdeationCreativityWorkshopDivergence | ArchitectureQualityRiskAssessmentLean |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






