Guidance · No. 06
The Team Performance Model
Most organizations have a handful of teams that everyone agrees are exceptional. They deliver quickly without cutting corners, recover well when something breaks, and earn the trust of the business. The problem is that almost no one can reproduce them.
When key people leave, performance often drops. When teams grow or are reorganized, results fragment. And when leaders try to intervene, the effect is hard to predict and even harder to prove.
This is the question the Team Performance Model was designed to answer.
The challenge is explaining performance, not measuring activity
Most organizations are not short of data about their teams. Dashboards and metrics are everywhere, modern practices are widely adopted, and frameworks are well established. Yet performance still varies dramatically from one team to the next.
The uncomfortable truth is that most organizations cannot explain, in clear operational terms, why one team becomes elite while another does not. This is not caused by a lack of talent, inadequate tooling, or the wrong framework. It is caused by the absence of a model that explains performance as a system. Without that understanding, elite performance stays accidental: it appears in pockets, resists copying, and disappears when conditions change.
What it is
The Team Performance Model is a structured way to make team performance visible, measurable, and improvable. It translates modern ways of working into a defined set of capabilities that leaders can actively steer over time.
Its purpose is not to assess abstract maturity or optimize isolated metrics. It is to explain what makes a team perform at an elite level, consistently and sustainably, and to show where intervention will meaningfully affect outcomes. Rather than asking whether a team follows a particular framework, it asks the more useful question: which capabilities determine whether a team can perform well, and where are they strong or weak today?
To do this, the model connects three layers that are usually treated separately: business and delivery outcomes, team-level capabilities, and individual behaviors and habits. Linking these layers is what allows it to explain not only what is happening, but why it is happening and how it can be influenced.
The model does not replace the tools or methods a team already uses. It is framework-inclusive by design, working alongside Scrum, Kanban, SAFe, Team Topologies, or a custom hybrid, and it measures the effectiveness of the practices already in place rather than imposing new ones.
Frameworks tell you whether a team follows good practice. This model tells you whether a team can perform at an elite level, consistently and sustainably.
The shift it represents
Traditional approaches to team performance focus on adopting practices, running maturity assessments, and tracking individual metrics. Where they fall short is in explaining performance and showing leaders where to act. The model changes the orientation accordingly:
| From | To |
|---|---|
| Following a framework | Building measurable capabilities |
| Maturity assessments | Performance and outcomes |
| Isolated metrics | Performance as an interconnected system |
| Hoping for elite teams | Building them by design |
Elite teams are not defined by speed alone. They remain predictable without becoming rigid, maintain quality without slowing delivery, and stay engaged without burning out. What truly differentiates them is balance: their performance emerges from a coherent set of capabilities that reinforce one another, where strength in one area cannot indefinitely compensate for weakness in another. The strongest teams tend to be resilient, agile, empowered, innovative, and sustainable at the same time, and this model is built to make those qualities visible and actionable.
Where it sits
Performance in a modern organization is created through digital value streams: the end-to-end flows of work, decisions, systems, and people that design, build, operate, and improve a product or service. The Team Performance Model assesses the team layer of that system, and it operates as one layer in a nested performance system. Each layer answers a distinct question, and each influences the layers above and below it:
This structure matters because team performance is often shaped by forces outside the team. A team that appears slow may be absorbing unstable priorities from the portfolio layer or constrained by dependencies elsewhere in the value stream. Read together, the layers reveal not only how a team is performing, but why, and whether the right intervention is at the team level or somewhere upstream.
How it is structured
The model is built from twelve dimensions, grouped into two types so that it can stay both comprehensive and adaptable. Eight core capabilities apply to every digital team. Four context families adapt the picture to different kinds of teams. Beneath them sit the personal drivers that move performance day to day, and above them sit the business drivers that connect performance to outcomes leaders care about.
Core capabilities
The eight core capabilities are the universal foundation of elite performance. They apply to every digital team regardless of domain, technology, or delivery approach, and when a team is weak in any one of them, performance eventually plateaus or regresses.
| Capability | What it describes |
|---|---|
| Flow efficiency | How effectively work moves from start to finish with minimal waiting, handoffs, and rework |
| Predictability and planning accuracy | The ability to make realistic commitments and consistently deliver on them |
| Quality and engineering excellence | The practices that prevent defects, enable safe change, and reduce long-term cost |
| Team collaboration and knowledge sharing | How effectively knowledge flows across roles so the team avoids bottlenecks |
| Psychological safety | The degree to which people feel safe to speak up, surface risks, and learn from mistakes |
| Engagement and morale | The energy and sustainability that let teams perform without burning out |
| Continuous improvement and learning | How effectively reflection and experimentation turn into lasting capability gains |
| Customer value focus | How clearly the team connects its work to customer outcomes and business impact |
Context families
The four context families adapt elite performance to different team types. A stream-aligned product team, a reliability team, and a platform team all create value differently, and these dimensions adjust the measurement so teams can be understood fairly rather than forced into a single mold.
| Context family | What it describes |
|---|---|
| Change and release velocity | How frequently and safely a team moves changes into use |
| Reliability and stability | How well a team maintains dependable systems and recovers from failure |
| Operational autonomy and automation | The degree to which a team operates independently through self-service and automation |
| Practitioner experience and flow | The friction or flow practitioners feel in daily work, affecting focus, speed, and retention |
Personal drivers
Team performance does not change through dashboards alone. It changes when individual behavior shifts in the right places, at the right time. The personal drivers describe the observable habits that most influence performance, translating team-level capability gaps into concrete day-to-day actions. They are grouped into four clusters.
| Cluster | What it influences |
|---|---|
| Communication and collaboration | How information, decisions, and learning flow across the team and its boundaries |
| Personal growth and engagement | Learning, resilience, and motivation that sustain performance over time |
| Execution and productivity | Whether the team reliably turns intent into delivered results |
| Quality and craftsmanship | The long-term sustainability that reinforces quality, reliability, and customer value |
Business drivers
Team performance only matters insofar as it supports the business. The model connects capabilities to eight strategic drivers, giving leaders the evidence to steer strategy and demonstrate the return on improvement.
| Business driver | What it covers |
|---|---|
| Financial performance | Cost efficiency, margin protection, and predictable delivery of value |
| Customer experience and value | Reliability, usability, and responsiveness to feedback |
| Operational efficiency | Stable operations, efficient flow, and low coordination overhead |
| Innovation and growth | Fast learning cycles, experimentation, and adaptability |
| Risk management and compliance | Quality practices, resilience, and safeguards against failure |
| Employee engagement and productivity | Autonomy, safety, and meaningful work for practitioners |
| Sustainability and long-term viability | Balancing speed with craftsmanship and maintaining team health |
| Strategic agility | Sensing change early and pivoting effectively when conditions shift |
How it works
The model draws on two kinds of signals and presents them through two complementary views.
System signals come from the tools teams already use, including delivery, engineering, and operations tooling. They indicate how work flows, how reliably it is delivered, and where quality or stability is at risk. Human signals are captured through brief, role-specific prompts. They indicate how the work is experienced, including whether people feel safe to speak up, whether collaboration is effective, and whether the team is sustainable. Many performance issues surface in human signals first, such as eroding safety or morale, before they appear in delivery data.
These signals are presented through one shared structure and two experiences. Leaders use a team view to diagnose systemic constraints, compare teams fairly, and decide where investment and attention will have the most effect. Individuals use a personal view that translates team goals into role-aware habits and learning moments. The same underlying model serves both, which keeps strategy and daily work connected rather than trapped in executive dashboards.
The model is a living engine rather than a static report. As teams change, as people rotate, and as new members join, it adapts and continues to provide current guidance. It is also designed to begin with limited data: a starting set of delivery signals and a few human pulses is enough to surface where capability is strong or weak, with confidence increasing as more signal becomes available. As AI agents increasingly work alongside people, an optional agentic overlay extends the model to human-and-agent collaboration, so measurement reflects the effectiveness and safety of a hybrid team rather than human output alone.
What this looks like in practice
Consider a team that leadership has flagged as underperforming because delivery feels slow. The instinct is to push for more speed or to question the team’s capability.
The model indicates a different cause. Flow is being constrained by dependencies the team does not control, predictability is low because commitments are repeatedly reforecast, and human signals show that psychological safety has eroded, so risks are surfaced late rather than early. The team is not short of effort or talent; its performance is being suppressed by a small number of specific capability gaps, some of which originate outside the team.
That reframing changes the conversation. Instead of generic pressure to go faster, it points to targeted action: resolving the external dependency, rebuilding the conditions for people to raise risks early, and supporting a few concrete individual habits that improve collaboration and planning. Leaders act on the capability gap while the team moves performance through the personal drivers.
From insight to action
The model is designed to guide action, not just to report. Its value is a learning loop that improves with each cycle:
It detects where a team is close to elite performance and why, and where capability gaps are limiting outcomes. It recommends where coaching, platform investment, or leadership attention will have the greatest effect. It tracks what is done and what changes as a result. And it retains that result, so each recommendation is better informed than the last.
A clear division of responsibility makes this sustainable. Leaders steer at the capability level, while teams move performance through the personal drivers. This enables continuous improvement without micromanagement.
Who uses it, and when
The model is a leadership instrument as much as a team one, used in the moments where performance is steered: team reviews, capability and investment decisions, coaching conversations, and transformation assessments.
| User | Primary use |
|---|---|
| Engineering & technology leaders | Which teams are close to elite performance, and where investment will have the most effect |
| Team leads | Where a team’s capability gaps are, and how to close them |
| Individual practitioners | How team goals translate into concrete day-to-day habits and learning |
| C-level / Enterprise | How team performance connects to business outcomes and the return on transformation |
Why it matters
As organizations become more digital and more AI-enabled, the cost of producing software falls and output rises. In that environment, advantage no longer comes from individual heroics or from adopting more practices. It comes from building teams that perform at a high level by design, and from being able to explain and reproduce that performance as people, tools, and even AI teammates change.
That is the purpose of the Team Performance Model. By making performance explainable, repeatable, and scalable, it enables leaders to move from hoping for elite teams to building them intentionally, and to connect everyday behavior to the outcomes the business depends on.
Frameworks measure whether a team follows good practice. This model reveals whether a team can perform at an elite level, and shows leaders exactly where to act.
