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 of Pretotyping with its method-specific working model.
Product Discovery
Pretotyping
Paper illustration of several people silently writing ideas and passing sheets around with arrows.
Innovation
Brainwriting
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data.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.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.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.
Complexitydifferent
LowLowMediumMedium
Timedifferent
Stunden bis wenige Tage15-30 minOngoing2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-43-122-20Designers, developers as users, and facilitation
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Pretotyping sketch, Test setup, Conversion data, Go or no-go decisionIdea sheets, Expanded concepts, Prioritized listChat Transcript, Action Log, AutomationsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
ValidationDemandMVP
BrainstormingCollaborationInclusionIdeas
CollaborationEngineeringIncident
ArchitectureEngineeringFeedbackValidationTasks
Add more methods