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 JTBD interview notebook with a decision timeline, forces of change and a concise job hypothesis.
Product Discovery
Jobs to Be Done
Paper illustration for Communication Plan
Delivery
Communication Plan
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)
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Purposedifferent
When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought.When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.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.The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 Wochen45-90 min3–4 h for initial assessment; preparation and deeper analysis additional1-4 h
Participantsdifferent
5-12 Interviews2-61 or a small team; particularly suitable for 3–4 people1-5
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Job Stories, Outcome Statements, Opportunity ListCommunication Plan, Channel Matrix, Message CadenceLean 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 checksContext Diagram, Container Diagram, Component Diagram
Tagsno overlap
CustomerOutcomesNeeds
CommunicationStakeholdersDeliveryPlanning
ArchitectureQualityRiskAssessmentLean
ArchitectureCommunicationVisualization
Add more methods