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 for Standard Work Analysis.
Operations
Standard Work Analysis
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 h90-180 min3–4 h for initial assessment; preparation and deeper analysis additional1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
2-64-121 or a small team; particularly suitable for 3–4 people3-20 Reviewer
Formatdifferent
WorkshopWorkshopWorkshop + asyncAsync
Outputdifferent
Standard Work Sheet, Deviation List, Improved Standard, Training NeedsDecision Rights Matrix, AgreementLean 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 checksRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
LeanProcessQuality
DecisionGovernanceAlignmentResponsibility
ArchitectureQualityRiskAssessmentLean
ArchitectureDecisionAsyncGovernance
Add more methods