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 Lean Canvas with nine fields, notes, and one highlighted learning risk.
Product Strategy
Lean Canvas
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
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)
Purposedifferent
When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable.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.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
45-90 min1-4 h45-90 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
1-61-52-61 or a small team; particularly suitable for 3–4 people
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Lean Canvas, Core Assumptions, Experiment BacklogContext Diagram, Container Diagram, Component DiagramCommunication 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 checks
Tagsno overlap
StartupLeanAssumptionsBusiness model
ArchitectureCommunicationVisualization
CommunicationStakeholdersDeliveryPlanning
ArchitectureQualityRiskAssessmentLean
Add more methods