Across the Agile community, a quiet but significant shift is underway.

After years of scaling frameworks, expanding structures, and optimising coordination across ever-larger systems, many organisations are now experimenting with something that looks deceptively simple: Tiny Teams.

Not scaled-down versions of big teams.
Not “delivery units” with fewer people.

But small, focused groups — often two to five people — designed for speed, ownership, and clarity, operating within much larger organisational systems.

So why now? And what are we noticing as this way of working gains momentum?

Why Tiny Teams Are Emerging — and Why Now

Agile organisations are under pressure from multiple directions:

• Faster decision-making cycles

• Increasing complexity and uncertainty

• Reduced tolerance for heavy governance and coordination overhead

• A growing desire for meaningful ownership rather than role compliance

And increasingly, there’s another force at play:

AI has changed what coordination looks like.

Where large teams once existed to manage handovers, dependencies, and information flow, much of that work is now handled — or accelerated — by technology. AI systems can coordinate, track, surface insights, and automate in ways that reduce the need for large, meeting-heavy structures.

This has opened up a different design question:

What if we reduced the size of the human system — and let digital systems carry more of the coordination load?

Tiny Teams are one response to that question.

They prioritise:

• Clear purpose

• Tight feedback loops

• High autonomy

• Strong accountability

• Rapid learning and adaptation

In theory, they offer focus and flow.
In practice, they also surface something else — relationships.

What Are Tiny Teams (Really)?

Drawing on emerging practice in the Agile community, Tiny Teams are typically:

• Very small (often 2–5 people)

• Highly autonomous within clear boundaries

• Purpose-driven, with a specific outcome they own

• Fluid — forming, evolving, and dissolving as work changes

• Light on hierarchy, heavy on trust

Crucially, Tiny Teams are not just smaller teams.

They operate differently because they are embedded in larger systems — platforms, guardrails, shared standards, and increasingly, AI-enabled coordination tools.

The big system provides stability and alignment.
The tiny team provides speed, creativity, and ownership.

With fewer people:

• Communication is more direct

• Accountability is more visible

• Patterns emerge faster

• There’s nowhere to hide

Which is both their strength — and their challenge.

What We’re Noticing in Tiny Teams

When teams get smaller, the relational dynamics intensify.

In Tiny Teams:

• Leadership shows up immediately (formal or informal)

• Conflict is felt more personally

• Silence carries more weight

• Differences in style, power, and decision-making become highly visible

What might take months to surface in a larger group can emerge within days.

AI may reduce coordination overhead — but it doesn’t reduce human complexity.
If anything, it amplifies it.

As technical systems handle more of the “what” and “when,” the human system is left holding more of the “how” and “who.”

Where Tiny Teams Tend to Succeed

Tiny Teams thrive when:

• Purpose is explicit and genuinely shared

• Working agreements are clear and revisited

• Psychological safety is actively cultivated

• Tension is addressed early, not avoided

• Roles flex without ego or defensiveness

When these conditions are present, Tiny Teams can be remarkably effective — fast, creative, and deeply engaged.

They feel less like units of delivery and more like living systems.

Where Tiny Teams Often Struggle

At the same time, Tiny Teams can struggle when:

• Conflict becomes personal rather than systemic

• Power dynamics remain unspoken

• Decisions default to the loudest voice

• Avoidance masquerades as harmony

• There’s no shared language for what’s happening between people

In larger teams, these dynamics can be diluted or absorbed by structure.

In Tiny Teams, they are concentrated.

As one agile practitioner put it:

“The smaller the team, the more human everything becomes.”

A Systems Insight

One of the most important insights we’re seeing is this:

Tiny Teams don’t reduce complexity — they relocate it.

They shift complexity:

• Away from coordination structures

• Away from process-heavy governance

• And into the relationship system itself

The unit of performance is no longer the individual — or even the process.

It’s the quality of relationship.

This means:

• Technical skill alone isn’t enough

• Process clarity helps — but doesn’t resolve relational tension

• The ability to notice, name, and work with patterns becomes critical

Tiny Teams ask more of our relational capacity, not less — especially in an AI-accelerated environment.

Looking Ahead

Tiny Teams aren’t a silver bullet.
They are an invitation.

An invitation to:

• Work at human scale within complex systems

• Develop deeper relational awareness

• Build teams that can self-correct, not just self-organise

• Invest in skills that help people stay in relationship under pressure

The question isn’t whether Tiny Teams are “the right model.”

The deeper question is:
Are we equipped to support them well?

In our next article, we’ll explore how systems coaching — and specifically ORSC — helps agilists, coaches, and leaders build the relational capability Tiny Teams need to truly thrive.