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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Team Topologies Interaction Modes with its method-specific working model.
Team Design
Team Topologies Interaction Modes
Paper illustration for Team Charter.
Facilitation
Team Charter
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Purposedifferent
ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additionalHalf day2-4 h45-90 min
Participantsdifferent
Designers, developers as users, and facilitationTeam-Leads plus Architecture3-123-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsInteraction Heat Map, Agreements per PairTeam Charter, Working Norms, Role NotesExpectation Map, Alignment Notes, Agreements
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
TeamAlignmentCollaborationOrganization
TeamAlignmentCollaboration
AlignmentStakeholdersTeam
Add more methods