> ## Content Index
> Fetch the complete content index at: https://playbooksforleaders.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Agile Team Onion
- URL: https://playbooksforleaders.com/team-people/048-agile-team-onion/
- Published: 2026-07-11T14:49:51.000Z
- Updated: 2026-11-16T17:48:05.000Z
- Description: Emily Webber's model visualises stakeholder relationships as concentric circles around the core team.
- Author: Will Rowan
- Tags: #team-people, #lang-en

## What is the Agile Team Onion?

The Agile Team Onion is Emily Webber's technique for visualising stakeholder proximity. You draw concentric circles: delivery team at the centre, then immediate collaborators, wider organisational stakeholders, and external parties. Each ring has its own communication cadence and decision-making involvement.

Everyone wants to be in the room. Half of them don't need to be. The team is drowning in updates for people three layers removed from the work.

![Concentric rings labelled from the centre outward - delivery team (daily contact), immediate collaborators (weekly cadence), wider organisation (monthly updates), and external (quarterly or by-event) - titled Agile Team Onion, under the banner 'not everyone needs the same depth. codify the rings.'](https://playbooksforleaders.com/assets/img/tool-visuals/048-agile-team-onion.svg)

Method visual: Agile Team Onion

## When should you use the Agile Team Onion?

The model makes explicit what most teams sense but never codify: not everyone needs the same depth of information or frequency of contact. That clarity is its unique strength. It stops teams oscillating between over-communication that exhausts and under-communication that blindsides.

Reach for it when forming a new team, onboarding a wave of stakeholders, or when too many people are weighing in on decisions they shouldn't touch. It falls short for very small teams where everyone is in the inner ring, and it goes stale fast if you don't revisit it as the stakeholder landscape shifts.

**Your next move:** *Which stakeholder is currently sitting in the inner ring of your team's attention who should be three layers out, and whose work are they crowding out by being there?*

## Which Playbooks use the Agile Team Onion?

You use the Agile Team Onion in the Plan of one Playbook:

- [A new starter joined on Monday and I haven't onboarded them.](https://playbooksforleaders.com/team-people/new-starter/)

## What works well with the Agile Team Onion?

Pair the Agile Team Onion with [Stakeholder Mapping](https://playbooksforleaders.com/team-people/068-stakeholder-mapping/) and [Communication Planning](https://playbooksforleaders.com/team-people/053-communication-planning/).

## When shouldn't you use the Agile Team Onion?

For a very small team, where everyone is in the inner ring, skip the Agile Team Onion. If you won't revisit it as your stakeholders change, it goes stale fast.

## How long does the Agile Team Onion take?

About 30 minutes. You come away with a picture you can show people.

**Where it comes from:** [Emily Webber, The Team Onion, 2016](https://teamonion.works/book?ref=playbooksforleaders.com)

**Learn more:** [Emily Webber: Agile Team Onion](https://public.digital/pd-insights/signals/signals-2/the-team-onion?ref=playbooksforleaders.com)