What Is a Capability-Centered Team?
A capability-centered team is organized around a durable business capability, an outcome the organization needs to keep producing, rather than around a fixed function, department, or reporting line. Membership, tools, and structure adapt as the work itself and the technology available to do it change, instead of staying locked to a headcount or an org chart box.
How it's different from a functional or project team
Most org charts are built around one of two logics:
Functional teams are organized by discipline (marketing, finance, operations, etc) and stay fixed regardless of what work is actually flowing through the business.
Project teams are organized around a single initiative, assembled temporarily, then dissolved when the project ends.
A capability-centered team is organized around neither. It's built around a standing outcome the business needs, say, "customer onboarding" or "pricing decisions," and the team's composition flexes to match what that outcome currently requires. That composition increasingly includes AI agents alongside people, treated as capacity to route work to, not just tools people use.
Why this matters now
Agentic AI can absorb meaningful pieces of a workflow that used to require a dedicated role. When teams are built strictly around fixed functions or fixed headcount, that shift creates friction. Work doesn't have anywhere to go except the same boxes it's always occupied, even when a person, an agent, or some combination of both would now serve the outcome better.
A capability-centered structure gives an organization somewhere to put that flexibility. It's the same principle behind Drift Club's name: the ground underneath an organization is always shifting, even when the surface structure looks unchanged. Capability-centered design is what lets the surface move with it instead of cracking.
How Drift Club applies this
Capability-centered team design is a core lens in Drift Club's full-day "Reimagining Work" Session and in longer Engagement and Partnership work, used to diagnose where current team structures are absorbing change poorly, and to redesign around the capabilities that actually need to flex.
Frequently asked questions
Is a capability-centered team the same as a cross-functional team? No. A cross-functional team pulls people from different departments together but is still assembled around a project or initiative. A capability-centered team is organized around a standing outcome the business needs indefinitely, so it persists and reshapes, rather than disbanding.
Does adopting this model mean reorganizing the whole company? No. Most organizations start by identifying one or two capabilities where the current structure is creating the most friction, and redesigning around those before considering a broader shift.