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 Golden Path
Engineering
Golden Path
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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 teams need a reliable default path for frequent use, sprawl quickly emerges without any guiding logic. Golden Path bundles the preferred path so good practice becomes easy and deviation becomes deliberate.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-3 Tage Setup, laufend45-90 min3–4 h for initial assessment; preparation and deeper analysis additional1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
2-82-81 or a small team; particularly suitable for 3–4 people3-20 Reviewer
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Golden Path Guide, Templates, Quality ChecksAssumption List, Critical Assumptions, Learning 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 checksRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
EngineeringProductivityGovernance
AssumptionsRiskDecisionDiscovery
ArchitectureQualityRiskAssessmentLean
ArchitectureDecisionAsyncGovernance
Add more methods