methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper matrix with seven SCAMPER rows, operator prompts and variations for a course portal.
Innovation
SCAMPER
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
A paper-based illustration representing Brainstorming with its core stages and visible working result.
Innovation
Brainstorming
Purposedifferent
For an existing solution under pressure to change, the method deliberately opens space for systematic variants. It directs attention to rebuilding, combining, and repurposing rather than only new basic ideas. This produces concrete evolution paths for products, offerings, or workflows.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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.
Complexitydifferent
LowMediumHighLow
Timedifferent
30-60 min3–4 h for initial assessment; preparation and deeper analysis additional2-6 h30-60 min
Participantsdifferent
2-101 or a small team; particularly suitable for 3–4 people3-104-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
SCAMPER Idea List, Concept Shortlist, Variation NotesLean 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 checksFMEA Table, Risk Priority, Mitigation ActionsIdea pool, Theme clusters, Shortlist
Tagsno overlap
BrainstormingIdeationCreativityReframingInnovation
ArchitectureQualityRiskAssessmentLean
RiskQualityOperationsRoot cause
BrainstormingIdeationCreativityWorkshopDivergence
Add more methods