Practice : Cross-Functional Squads
Purpose and Strategic Importance
Cross-Functional Squads bring together all the skills needed to deliver value, reducing handoffs and dependencies. They own problems end-to-end, increasing autonomy, accountability, and speed.
Without cross-functional squads, work is fragmented across silos, slowing flow and diluting ownership.
Description of the Practice
- Small, stable teams combining product, design, engineering, and domain expertise.
- Squads are aligned to outcomes, not functions.
- Teams are empowered to make decisions close to the customer.
How to Practise It (Playbook)
1. Getting Started
- Form squads around high-value problem spaces.
- Ensure representation from key disciplines.
- Give squads clear missions linked to outcomes.
2. Scaling and Maturing
- Maintain squad stability while rotating individuals occasionally for learning.
- Align squad outcomes with portfolio strategy.
- Provide enabling teams and platforms to reduce cognitive load.
3. Team Behaviours to Encourage
- Collective ownership of outcomes.
- Open collaboration across disciplines.
- Pride in autonomy and accountability.
4. Watch Out For…
- Squads formed but still dependent on external approvals.
- Too many responsibilities without proper support.
- Misalignment between squad missions and strategy.
5. Signals of Success
- Qualitative: Squads demonstrate pride in owning outcomes.
- Quantitative: Reduction in delivery lead time due to fewer dependencies.