---
type: "synthesis"
theme: "team-design"
sources: ["governance"]
id: "cross-small-empowered-teams"
sourceVaultSlug: "hbr-seg-governance"
originDay: 7
articleStem: "hbr-seg-governance"
sourceUrl: "(unified vault: 8 sources)"
sourceTitle: "HBR — Firm Ⅱ-B · Governance, decision rights, leadership, risk"
---
# The Small Cross-Functional Team as Universal Unit

Independently, three articles converge on almost the same headcount for the group that actually does the deciding.

- **6–8 people** — the [[framework-autonomous-scrum]] ([[claim-autonomous-scrums-outperform]]): interdisciplinary teams with authority to *act*.
- **5–8 people** — [[concept-enc-teams]] ([[action-form-enc-teams]]): cross-functional, with at least one technologist ([[claim-cross-functional-necessity]]).
- **2–4 people** — RACI's Responsible cap ([[action-limit-responsible-role]]) plus one Accountable, enforced by [[action-restrict-meeting-attendance]].

*How C-Suite Roles Are Reshaped* supplies the macro-trend that legitimizes all three: [[concept-modular-leadership-systems]] — flatter hierarchies where "teams assemble dynamically around problems."

Why the convergence? Small teams debate honestly (see [[cross-structured-friction]]), keep accountability concentrated (see [[cross-single-owner-principle]]), and move at AI speed (see [[cross-governance-speed-gap]]). The corpus treats the oversized meeting as a governance anti-pattern — [[contrarian-inclusion-reduces-buy-in]] — and the tight, cross-functional cell as the reusable unit for both *execution* (scrums) and *risk* (ENC teams). The enrichment caveat, shared across sources: small autonomous teams need alignment guardrails to avoid fragmentation and local optimization.