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 Team Charter.
Facilitation
Team Charter
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Purposedifferent
When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
2-4 h45-90 min30 min Setup, dann laufend20-40 min initial, dann laufend
Participantsdifferent
3-123-121-3 maintaining, briefing for everyone3-15
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Team Charter, Working Norms, Role NotesExpectation Map, Alignment Notes, AgreementsRAID Log, Status Report SourceROAM Board, Owner List
Tagsno overlap
TeamAlignmentCollaboration
AlignmentStakeholdersTeam
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
Add more methods