Distinctions
Is
- a team that has — or will learn — all the skills required to turn an idea into something usable for the customer, so the team itself can complete the work end‑to‑end without external handoffs. 1
- A team that collectively possesses all skills needed to deliver value.
- Members have specialties but prioritize the team mission over role purity.
- Skills may overlap to maintain flow and resilience.
Is Not
- A rigid collection of specialists who only perform narrow roles.
- A dependency chain requiring external teams for routine delivery.
- A guarantee that every rare specialty must exist full-time on every team.
Examples
- A cross-functional team is like the crew in a heist movie. Each person has a specialty—the safecracker, the hacker, the driver, the muscle—but the mission comes first. If the driver disappears, the team doesn’t sit on the curb and give up. Someone else grabs the wheel and gets everyone out, because success matters more than sticking strictly to roles. 1
Systems
Relationships
Perspectives
| Point | View |
|---|---|
| Purist Perspective | Every team must contain every skill or it isn’t cross-functional. |
| Pragmatic Scaling Perspective | - Teams should be cross-functional enough to deliver independently most of the time. - Rare specialties may be shared across teams without violating the spirit of the model. |
Lines of Inquiry
- TBD