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 mind map with a central course onboarding question, colored main branches, keywords and cross-links.
Facilitation
Mind Mapping
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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 of several people silently writing ideas and passing sheets around with arrows.
Innovation
Brainwriting
Purposedifferent
When a topic is still unclear and too many thoughts surface at once, Mind Mapping creates an open surface for ordering them. It makes connections, subtopics, and starting points visible without fixing them too early.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
15-45 min45-90 min3–4 h for initial assessment; preparation and deeper analysis additional15-30 min
Participantsdifferent
1-102-81 or a small team; particularly suitable for 3–4 people3-12
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Mind Map, Topic Clusters, Open QuestionsAssumption List, Critical Assumptions, Learning PlanLean 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 checksIdea sheets, Expanded concepts, Prioritized list
Tagsno overlap
BrainstormingIdeasMappingStructureFacilitation
AssumptionsRiskDecisionDiscovery
ArchitectureQualityRiskAssessmentLean
BrainstormingCollaborationInclusionIdeas
Add more methods