View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Expectation MappingATAM (Architecture Tradeoff Analysis Method)Team Topologies Interaction ModesLASR (Lightweight Approach for Software Reviews)
| Criterion |  Facilitation Expectation Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Team Design Team Topologies Interaction Modes |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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 | Low | High | Medium | Medium |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | Half day | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 3-12 | Evaluation team, architects, and relevant stakeholders | Team-Leads plus Architecture | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Interaction Heat Map, Agreements per Pair | 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 |
Tagsno overlap | AlignmentStakeholdersTeam | ArchitectureQualityRiskTradeoffsStakeholders | TeamAlignmentCollaborationOrganization | ArchitectureQualityRiskAssessmentLean |