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 Team Cognitive Load Assessment with its method-specific working model.
Team Design
Team Cognitive Load Assessment
Paper illustration for Accountability Ladder
Operations
Accountability Ladder
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
When a team juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list.With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitydifferent
MediumLowLowLow
Timedifferent
60-90 min20-45 min45-90 min45-90 min
Participantsdifferent
3-121-83-104-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Cognitive Load Profile, Action ListOwnership Reflection, Action Commitment, Coaching NotesDelegation Board, Decision Boundaries, Role AgreementsSailboat Board, Risks, Improvement Actions
Tags1 shared
TeamComplexityImprovementDiagnosis
ResponsibilityLeadershipTeam
AutonomyRolesTeam
RetrospectiveTeamImprovement
Add more methods