---
id: "action-form-enc-teams"
type: "action-item"
source_timestamps: ["§ Implementing the Framework"]
source_url: "https://hbr.org/2026/05/what-are-your-companys-ai-nightmares"
source_title: "What Are Your Company's AI Nightmares?"
tags: ["team-building", "implementation"]
related: ["concept-enc-teams", "claim-cross-functional-necessity"]
action: "Create small, cross-functional teams (5-8 people, including at least one technologist) to identify AI nightmares."
outcome: "Comprehensive identification of AI risks across technical, behavioral, and legal domains without departmental standoffs."
speakers: ["Reid Blackman"]
sources: ["governance"]
sourceVaultSlug: "hbr-seg-governance"
originDay: 7
articleStem: "hbr-cl-82-ai-nightmares"
sourceUrl: "https://hbr.org/2026/05/what-are-your-companys-ai-nightmares"
sourceTitle: "What Are Your Company’s AI Nightmares?"
---
# Form cross-functional ENC teams

**Action:** Assemble small teams of **5 to 8 people** that mix domain experts (marketing, HR, legal, product) with **at least one technologist** (data scientist / engineer) to collaboratively identify and solve for AI nightmares.

**Expected outcome:** Comprehensive identification of AI risks across technical, behavioral, and legal domains — *without departmental standoffs*, because each function catches the blind spots of the others.

This operationalizes [[concept-enc-teams]] and is justified by [[claim-cross-functional-necessity]]. These teams then run the pilot in [[action-run-enc-pilot]] and become the first line of defense under [[concept-first-line-defense-shift]] (see [[action-repurpose-risk-boards]]).


## Related across articles
- [[action-empower-autonomous-scrums]]
- [[action-restrict-meeting-attendance]]