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 a journey map with four connected phases, several experience lanes and a point marked for closer investigation.
UX Research
Customer Journey Mapping
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
A paper-based illustration representing Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
Purposedifferent
When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear.
Complexitysame
MediumMediumMediumMedium
Timedifferent
2-4 h1-3 Wochen vom Draft bis zur Entscheidung60-120 min1-3 h
Participantsdifferent
4-103-20 Reviewer2-83-10
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsCommunication Canvas, Stakeholder Messages, Architecture Communication PlanCustomer Journey Canvas, Pain Points, Experience Opportunities
Tagsno overlap
JourneyServiceService design
ArchitectureDecisionAsyncGovernance
ArchitectureCommunicationStakeholdersCanvas
JourneyCustomerService designCanvas
Add more methods