View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:How Might WeArchitecture Communication CanvasLASR (Lightweight Approach for Software Reviews)C4 Model
| Criterion | ![]() Innovation How Might We | ![]() Architecture Architecture Communication Canvas | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | With a stuck problem carrying many implicit assumptions, the method translates observations into open, workable questions. It sharpens the problem frame without pre-thinking the solution, turning frustration or fuzziness into a search space with clear direction. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Low | Medium | Medium | Low |
Timedifferent | 30–45 min | 60-120 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-4 h |
Participantsdifferent | 1-10 | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | 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 | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | FramingOpportunityIdeationQuestions | ArchitectureCommunicationStakeholdersCanvas | ArchitectureQualityRiskAssessmentLean | ArchitectureCommunicationVisualization |



