methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Porter’s five competitive forces
Business Strategy
Porter Five Forces
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
Purposedifferent
ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.Porter Five Forces analyzes the forces that shape competitive pressure and profitability in a market. The view of market structure goes beyond individual competitors and reveals systemic pressure points.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 Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional1-3 h3–4 h for initial assessment; preparation and deeper analysis additional45-90 min
Participantsdifferent
Designers, developers as users, and facilitation2-81 or a small team; particularly suitable for 3–4 people2-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsFive Forces Analysis, Competitive Risks, Strategic OptionsLean 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 checksAnsoff Matrix, Growth Options, Risk Notes
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
StrategyCompetitionMarket
ArchitectureQualityRiskAssessmentLean
GrowthStrategyMarketPortfolio
Add more methods