View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation How Might We |  Architecture Architecture Decision Record |  Architecture Quality Attribute Workshop |  Architecture arc42 |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30–45 min | 15-45 min | 2-4 h | 1-2 Tage |
Participantsdifferent | 1-10 | 1-3 | 5-15 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | ADR File, Decision Log, Rationale | Quality Scenarios, Priority List, Architecture Concerns | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | FramingOpportunityIdeationQuestions | ArchitectureRationaleDocumentationGovernance | RequirementsArchitectureWorkshop | ArchitectureDocumentationCommunication |