methodatlas
Playbook

Establish Team Alignment

Move from unspoken expectations to clear roles, agreements, and decision pathways.

Outcome

A Team Charter with work agreements, role clarity, and next review date.

At the end you have

Team CharterExpectation MapWorking AgreementsDelegation Board

Decision point

You can decide which working style, roles, and decision levels the team uses consistently.

Next step

Test working agreements in daily team life and schedule the review date for adjustments.

Ideal for

  • New teams
  • Teams after reorganization
  • Recurring collaboration friction

Not good for

  • Acute conflicts without willingness to talk
  • purely technical architecture work
Preparation

What should be clear before you start

Roles

  • Whole team
  • Team Lead or facilitator
  • key interface roles as needed

Inputs

  • team mandate and goals
  • known frictions or unmet expectations
  • typical decision situations

Setup

  • Create a psychologically safe frame
  • Clarify team boundaries
  • Reserve a review date for agreements in advance
Flow

Method path

0 methods
    Completion criteria
    Templates

    Artifacts for this playbook

    Artifacts stay collapsed until you actually need them.

    MarkdownShow template

    Team Charter

    Template for team purpose, roles, ways of working, interfaces, and review date.

    # Team Charter
    
    ## Purpose
    
    Why does this team exist?
    
    ## Goals
    
    - ...
    
    ## Roles
    
    | Role | Person | Responsibility |
    |---|---|---|
    
    ## Ways of working
    
    - Meetings:
    - Communication channels:
    - Decision paths:
    
    ## Interfaces
    
    Which teams do we work with, and how?
    
    ## Review
    
    When do we review the charter?
    ChecklistShow template

    Working Agreements Checklist

    Checklist for concrete, testable team working agreements.

    - [ ] Agreement is phrased in an observable way
    - [ ] Applies to everyone on the team
    - [ ] Contains no pure statements of intent
    - [ ] Conflict case is described
    - [ ] Review date is set
    - [ ] Owner for maintenance is named