Skip to content
Start with one team

Field guide

Six questions every team keeps answering.

Who decides, who does what, what counts as done, who needs to know: each guide takes one question, shows where it usually breaks, and leaves you with a page you can write today.

The six guides

  1. 01

    GuidelinesWhat can we do without asking?

    A team should not have to renegotiate itself every day.

    ReplacesNorms nobody wrote down; the same debate every month · 4 min read

  2. 02

    Decision rightsWho decides?

    Know who decides before the choice becomes urgent.

    ReplacesThe RACI in a slide deck; the meeting to find out who can approve · 5 min read

  3. 03

    RolesWho does what, and what fills it?

    When someone leaves, their work should not leave with them.

    ReplacesJob titles and job descriptions · 4 min read

  4. 04

    MeasuresIs the work working?

    Know whether the work is working without another dashboard nobody reads.

    ReplacesThe dashboard nobody opens; the engagement survey · 4 min read

  5. 05

    Network of teamsWho depends on whom?

    The org chart shows reporting. The network shows work.

    ReplacesThe org chart · 5 min read

  6. 06

    AgentsWhere does software fit?

    Machine-readable should not mean machine-governed.

    ReplacesA bot with access to everything and no job · 5 min read

Start where it hurts

You don’t have to read them in order.

Most teams arrive with a sentence, not a framework. Find the one you’ve heard this week.

Who can actually sign this off?Decision rights We had this exact debate last month.Guidelines Everything stopped when Priya left.Roles We have a dashboard. Nobody opens it.Measures Nobody told us they were changing that.Network of teams The bot can see everything. What is it for?Agents

One charter is useful. Many become a model of the company.

Start with the team that keeps getting stuck. Link the next one when it earns it.

Start with one teamSee the product