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 Strategy Execution Loop with its method-specific working model.
Business Strategy
Strategy Execution Loop
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration of Strategic-Tactical-Operational Planning with its method-specific working model.
Business Strategy
Strategic, Tactical and Operational Planning
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
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.The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.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.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
HighLowMediumMedium
Timedifferent
Initial 3-6 h, then monthly or quarterly reviews1-4 h90-180 min1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
5-121-54-123-20 Reviewer
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Execution Loop, Review Cadence, Strategic Learning LogContext Diagram, Container Diagram, Component DiagramPlanning Levels Map, Cadence Model, Planning Artifact InventoryRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
ExecutionCadenceLearningGovernance
ArchitectureCommunicationVisualization
CadenceGovernanceExecution
ArchitectureDecisionAsyncGovernance
Add more methods