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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration of Design Charrette with its method-specific working model.
Innovation
Design Charrette
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 Reverse Brainstorming
Innovation
Reverse Brainstorming
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.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.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 persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
OngoingHalber Tag bis mehrere Tage3–4 h for initial assessment; preparation and deeper analysis additional30-60 min
Participantsdifferent
2-2010-501 or a small team; particularly suitable for 3–4 people3-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Chat Transcript, Action Log, AutomationsSketches and Concepts, Consolidated Solution Sketch, Prioritized DirectionLean 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 checksReverse Ideas, Risk Themes, Solution Ideas
Tagsno overlap
CollaborationEngineeringIncident
BrainstormingWorkshopCollaborationIdeation
ArchitectureQualityRiskAssessmentLean
BrainstormingIdeationCreativityRisk
Add more methods