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
A paper-based illustration representing Product Canvas with its core stages and visible working result.
Product Strategy
Product Canvas
Paper illustration for RAPID
Decision Making
RAPID
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
When product goal and feature scope don't yet fit cleanly together, it creates a shared working picture. It connects need, core features, and assumptions into a solid starting point.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-2 h45-90 min1-2 h1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
2-83-123-83-20 Reviewer
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Product Canvas, Product Assumptions, Scope NotesRAPID Role Map, Recommendation, Decision LogInception Canvas, Risks, Goal List, Open QuestionsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
CanvasDiscoveryScope
DecisionRolesGovernance
AlignmentArchitectureCanvas
ArchitectureDecisionAsyncGovernance
Add more methods