TThe Diary of a CEO
← All frameworks
Leadership

Small Autonomous Team Design

Build engagement through small teams, real agency, and shared accomplishment

Difficulty
Advanced
Time to result
~months to results
Steps
6
Confidence
95%

Daisley links engagement to control, influence, and the experience of solving problems with other people. His design starts with a shared outcome, gives a small group responsibility for meaningful parts of it, and allows members to influence how the result is achieved. Progress and contribution must be visible enough to create accomplishment and pride. As an organization grows, he argues that preserving one large group's former atmosphere is unrealistic; dividing it into smaller teams with distinct goals can retain familiarity and cohesion. The mechanism trades some economies of scale for what he calls economies of engagement. This is not autonomy without boundaries: leaders still define outcomes and responsibilities, while teams receive genuine room to decide and contribute inside them.

Origin

Extracted from The Diary of a CEO

Core principles

  • 01Agency increases motivation
  • 02Shared accomplishment strengthens cohesion
  • 03Small groups preserve familiarity better than one expanding group
  • 04Responsibility should be real rather than symbolic

How to run it

  1. 1

    Choose the shared outcome

    Give the group a result it can understand and pursue together rather than a collection of unrelated tasks.

    Pro tip State the outcome in language the team can use to make trade-offs.

    Watch out A vague aspiration does not create useful ownership.

  2. 2

    Set the team boundary

    Keep the group small enough for members to know one another and understand how their work connects.

    Pro tip Use cohesion and coordination evidence rather than treating 100 as a universal cutoff.

    Watch out Daisley's size example is guidance, not a fixed scientific threshold for every organization.

  3. 3

    Assign real responsibility

    Give the team ownership of specific decisions and deliverables rather than asking for input that leaders routinely ignore.

    Pro tip Name decisions the team can make without escalation.

    Watch out Responsibility without authority produces frustration.

  4. 4

    Invite influence

    Let members help solve the problem and shape the method, especially when conditions change.

    Pro tip Ask for proposed approaches before prescribing one.

  5. 5

    Show progress together

    Review visible movement toward the shared outcome and connect individual contributions to it.

    Pro tip Celebrate completed progress rather than busyness.

    Watch out Competition between teams should not undermine the wider organization.

  6. 6

    Split when cohesion fades

    When scale makes familiarity and shared responsibility weaker, create smaller teams around distinct but coordinated goals.

    Pro tip Define interfaces between the new teams before dividing them.

    Watch out Splitting without coordination can replace disengagement with silos.

In the wild

Engagement during lockdown problem-solving

Daisley says engagement initially rose when organizations suddenly had to equip remote workers and invent new ways of operating. Employees were collaborating on unfamiliar problems and felt they had influence over solutions.

Agency and shared problem-solving temporarily increased engagement despite difficult circumstances.

Two teams instead of one oversized group

Daisley recommends considering a split when a company grows beyond the point where one group can preserve familiarity. Each smaller team receives a separate goal while remaining part of the same organization.

Smaller boundaries can preserve cohesion and make contribution easier to see.

Common mistakes

Keeping control at the top

Telling people exactly what to do while withholding influence removes the agency at the centre of the method.

Making autonomy symbolic

Teams cannot own an outcome if every consequential decision still requires approval.

Splitting without interfaces

Smaller groups still need clear coordination or cohesion inside each team will create silos across the organization.

Is it for you?

Best for

It is best for organizations that can delegate meaningful outcomes to identifiable teams.

Not ideal for

It is not ideal when responsibilities cannot be safely delegated or when splitting teams would create damaging duplication and coordination costs.

From the transcript

the more that people feel that they can have an impact in their job

Bruce Daisley · (36:30)

how can i make teams feel small and teams feel like they've got a shared sense of accomplishment

Bruce Daisley · (37:00)

From the episode

The Secret To Loving Your Work with Bruce Daisley