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 |  Innovation Design Charrette |  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. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. | 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 | Halber Tag bis mehrere Tage | 1-2 Tage |
Participantsdifferent | 1-10 | 1-3 | 10-50 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | HMW Questions, Challenge Framing, Idea Prompts | ADR File, Decision Log, Rationale | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | FramingOpportunityIdeationQuestions | ArchitectureRationaleDocumentationGovernance | BrainstormingWorkshopCollaborationIdeation | ArchitectureDocumentationCommunication |