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 Strategic-Tactical-Operational Planning with its method-specific working model.
Business Strategy
Strategic, Tactical and Operational Planning
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of Strategy Execution Loop with its method-specific working model.
Business Strategy
Strategy Execution Loop
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning.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
MediumLowHighMedium
Timedifferent
90-180 min1-2 TageInitial 3-6 h, then monthly or quarterly reviews1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
4-121-45-123-20 Reviewer
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Planning Levels Map, Cadence Model, Planning Artifact InventoryArchitecture Document, Context View, Runtime View, Deployment ViewExecution Loop, Review Cadence, Strategic Learning LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
CadenceGovernanceExecution
ArchitectureDocumentationCommunication
ExecutionCadenceLearningGovernance
ArchitectureDecisionAsyncGovernance
Add more methods