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 Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
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.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.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 h1-3 Wochen vom Draft bis zur Entscheidung2-4 h60-120 min
Participantsdifferent
3-103-20 Reviewer4-102-8
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Customer Journey Canvas, Pain Points, Experience OpportunitiesRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsJourney Map, Pain-point List, Opportunity BacklogCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
JourneyCustomerService designCanvas
ArchitectureDecisionAsyncGovernance
JourneyServiceService design
ArchitectureCommunicationStakeholdersCanvas
Add more methods