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
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.
Complexitydifferent
HighLowLowLow
Timedifferent
1-4 h20-40 min initial, dann laufend60–90 min30 min Setup, dann laufend
Participantsdifferent
3-83-152-81-3 maintaining, briefing for everyone
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Challenge Findings, Risk Register, Mitigation PlanROAM Board, Owner ListStakeholder Map, Engagement Plan, Risk NotesRAID Log, Status Report Source
Tagsno overlap
RiskDecisionSensemaking
RiskAgileTrackingAlignment
StakeholdersAlignmentFacilitationChange
RiskTrackingStakeholdersGovernance
Add more methods