View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:C4 ModelAffinity DiagrammingLASR (Lightweight Approach for Software Reviews)Failure Mode and Effects Analysis
| Criterion |  Architecture C4 Model |  UX Research Affinity Diagramming |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | 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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 1-4 h | 45–90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 2-6 h |
Participantsdifferent | 1-5 | 3-10 | 1 or a small team; particularly suitable for 3–4 people | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Theme clusters, Insight statements, Opportunity areas | Lean 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 | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | ArchitectureCommunicationVisualization | SynthesisQualitativeRoot cause | ArchitectureQualityRiskAssessmentLean | RiskQualityOperationsRoot cause |