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 illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration of several people silently writing ideas and passing sheets around with arrows.
Innovation
Brainwriting
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 Design Charrette with its method-specific working model.
Innovation
Design Charrette
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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.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.In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-3 h15-30 min3–4 h for initial assessment; preparation and deeper analysis additionalHalber Tag bis mehrere Tage
Participantsdifferent
3-123-121 or a small team; particularly suitable for 3–4 people10-50
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanIdea sheets, Expanded concepts, Prioritized listLean 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 checksSketches and Concepts, Consolidated Solution Sketch, Prioritized Direction
Tagsno overlap
KnowledgeMappingRisk
BrainstormingCollaborationInclusionIdeas
ArchitectureQualityRiskAssessmentLean
BrainstormingWorkshopCollaborationIdeation
Add more methods