---
id: "concept-enc-teams"
type: "concept"
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-design", "cross-functional", "agile-governance"]
related: ["concept-ethical-nightmare-challenge", "action-form-enc-teams", "claim-cross-functional-necessity"]
definition: "Small, cross-functional, decentralized teams (5-8 people) that rapidly identify and mitigate AI nightmares specific to their projects or departments."
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?"
---
# ENC (Ethical Nightmare Challenge) Teams

Small, decentralized, cross-functional groups — typically **five to eight people** — tasked with implementing [[concept-ethical-nightmare-challenge]] at various levels of an organization.

**Composition (non-negotiable):** Each team must include **at least one technologist** (data scientist / engineer) alongside domain experts drawn from marketing, HR, legal, and product design. The cross-functional mix is the entire point — it is what makes the team able to see the full risk surface (the argument in [[claim-cross-functional-necessity]]).

**Why the mix matters — it prevents departmental standoffs:**
- Data scientists spot **technical** vulnerabilities invisible to marketers.
- Marketers understand **consumer-behavior** risks invisible to engineers.
- Product designers see **UX failures** that legal might miss.

**Mission:** Collaborative problem-solving to identify the technical and behavioral sources of AI nightmares and to *build resources* to avoid them (Question 2 of [[framework-enc-questions]]).

**Cadence:** They operate on rapid **6-to-10 week pilot timelines** (see [[action-run-enc-pilot]]) rather than year-long design phases.

Under [[concept-first-line-defense-shift]], these teams become the organization's *first line of defense* for AI risk. Forming them is the action item [[action-form-enc-teams]].

**Enrichment note:** In the DataCamp podcast Blackman describes ENC teams operating through a *seven-step method* and stresses that participation should span legal, compliance, IT/data, and HR. A live counter-perspective (see [[question-nightmare-disagreement]]) is that decentralization risks inconsistent standards unless tightly coordinated with central functions.


## Related across articles
- [[framework-autonomous-scrum]]
- [[action-restrict-meeting-attendance]]
- [[action-limit-responsible-role]]