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
Paper illustration of VRIO Framework with its method-specific working model.
Business Strategy
VRIO Framework
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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 Value Chain Analysis with its method-specific working model.
Business Strategy
Value Chain Analysis
Purposedifferent
The VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions.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.Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
90-180 min60-120 min3–4 h for initial assessment; preparation and deeper analysis additionalHalf day
Participantsdifferent
3-62-81 or a small team; particularly suitable for 3–4 people3-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
VRIO Table, Strategic ActionsCommunication Canvas, Stakeholder Messages, Architecture Communication PlanLean 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 checksValue Chain Map, Lever List
Tagsno overlap
StrategyDiagnosisBusiness modelCapability
ArchitectureCommunicationStakeholdersCanvas
ArchitectureQualityRiskAssessmentLean
StrategyBusiness modelDiagnosisAnalysis
Add more methods