# Durable and Distributed Teams

Preserve context through durable teams and make distributed work explicit through agreements, asynchronous updates, and one visible board.

Duration: 11 min

Durable teams keep context, trust, and the reasons behind earlier decisions. They remain present when consequences arrive, so delivery can become learning rather than a handoff followed by dispersal.

Distributed teams make formerly implicit norms visible. Write routine updates asynchronously, reserve synchronous time for conversations that need it, co-author working agreements, and maintain one current board as the shared state of the work.

## fmap-m2-l6-v1

No survey statistic is narrated or treated as verified. The local animation draft remains separate from learner delivery. Keep this atom in review until final media and human-reviewed captions are approved.

## fmap-m2-l6-digest

### Teams built to last—wherever they sit

A project team is assembled for one endeavor and dispersed when the project is called done. Every dispersal can lose shared context, accumulated trust, and the memory of why earlier decisions were made. The next group then pays the forming cost again.

A **durable team** is a stable, cross-functional group that owns a product or value stream over time. A pickup game may contain talent; a sports team also develops shared plays. Durable teams remain present when consequences arrive. Project teams can ship and scatter; durable teams ship and find out.

Distribution makes formerly invisible coordination explicit. The Manifesto's preference for face-to-face conversation can be applied as a preference for the highest-bandwidth communication available: use synchronous conversation for difficult, emotional, or ambiguous work, and durable writing for information that does not require everyone to be present at once.

Three practices support that translation:

1. **Async-first standup.** Each person posts what moved, what is next, and what is blocked by their own mid-morning. Meet synchronously only when a knot genuinely needs it.
2. **Explicit working agreements.** Co-write overlap hours, response expectations, urgent channels, and where decisions are recorded. Revisit the agreements; do not impose them once and call the work done.
3. **One visible board.** The board becomes the shared room. Everyone updates it before ending their day. A stale board is confident misinformation.

Trust also requires deliberate maintenance. Include safety check-ins in Retrospectives and make some space for the informal human contact that a shared office may otherwise provide accidentally.

Agile does not require co-location. Distribution requires spoken norms to become written agreements, wall glances to become a shared board, and accidental contact to become intentional connection. Making the implicit explicit can improve co-located teams too.

## fmap-m2-l6-r1

### Working-agreements starter

Write these agreements together. Each answer should name the behavior, channel, or time window clearly enough that a new teammate could follow it. Revisit the page at Retrospectives.

1. **Overlap:** Which hours, if any, will everyone protect for live collaboration?
2. **Response expectations:** How quickly do we normally respond in each channel?
3. **Urgency:** What truly counts as urgent, and which channel signals it?
4. **Decisions:** Where do final decisions and their reasons get recorded?
5. **Async update:** By when does each person post moved / next / blocked, and where?
6. **Meeting threshold:** Which conversations need voice or video rather than more messages?
7. **Board truth:** Who updates the shared board, by when, and how do we flag stale state?
8. **Safety and repair:** How will we surface misunderstandings, check safety, and revise an agreement that is not working?

**Filled example:** “Routine chat receives a response within one working day. Use the urgent channel only for a blocked live service or a decision needed within two hours. The decision log records the outcome, owner, date, and why. Everyone updates the board before their local end of day.”

Agreements are agreed, not imposed. Leave room for time zones, accessibility needs, caring responsibilities, and focused work.

## fmap-m2-q1

This check is formative. It records no professional competence and does not create certificate eligibility. The module's principle is **safety before speed**: truthful information is a precondition for useful inspection and sustainable performance.