What is a T-Shape Team?
A T-Shape Team consists of members with a T-shaped skill profile: broad in general capabilities and deep in one specialty, so the team can collaborate flexibly and cover for each other.
DEFINITION
The T-Shape model describes a skill profile with two dimensions: the horizontal bar of the T stands for broad foundational knowledge in adjacent areas, such as design, testing, or business understanding. The vertical bar stands for deep expertise in one specialty, such as backend development or UX research. Tim Brown of IDEO popularised the T-Shape concept as an ideal type for creative teams. A T-Shape Team consists of such T-shaped professionals. It combines depth for excellence with breadth for collaboration. T-Shape Teams are more resilient than I-Shape Teams, where each member has only narrow expertise and bottlenecks arise when someone is unavailable. In agile teams, breadth enables cross-functional work: developers understand UX, designers understand technical constraints. This reduces handoffs and increases speed. A related model is the M-Shape or Pi-Shape profile with two depths and even more breadth.
CONNECTIONS
Leadership
Leaders shape T-Shape Teams through targeted personal development: fostering specialist knowledge AND insight into adjacent areas — for example through rotation, pair work, and interdisciplinary projects.
Project Management
T-Shape Teams reduce dependencies and ease the critical path. When several team members can take on similar tasks, the risk from bottlenecks and absences decreases.
Artificial Intelligence
In AI projects, the team needs both data science depth and breadth in UX, ethics, and business. T-shaped members bridge the communication gap between business units and AI teams.
KEY POINTS
- T-Shape: horizontal breadth in adjacent areas plus vertical depth in one specialty.
- Tim Brown of IDEO made the T-Shape profile known as a trait of creative professionals.
- T-Shape Teams are resilient: members can cover for each other.
- Cross-functional work works better when everyone brings a basic understanding of neighbouring disciplines.
- M-Shape or Pi-Shape extend the model with a second depth.
EXAMPLE
An agile product team is developing a mobile app. The developer has deep expertise in iOS development. She also understands UX fundamentals well enough to review designs for feasibility. The UX designer has deep expertise in user research. He also understands API basics well enough to discuss feasibility questions directly. Everyone can take on quality assurance tasks when needed. The team delivers complete, tested features in every iteration without external dependencies.
MISCONCEPTIONS
Does T-Shape mean everyone must be able to do everything?
No. Each member has a clear strength. Breadth means foundational understanding: enough to collaborate, ask questions, and step in for simple tasks. Not: all skills at expert level.
Is T-Shape better than specialisation?
It depends on context. In innovation teams, T-Shape is often superior. In highly specialised research or operations areas, deep specialisation may make more sense.