---
id: "claim-cross-functional-necessity"
type: "claim"
source_timestamps: ["§ Implementing the Framework", "¶3"]
source_url: "https://hbr.org/2026/05/what-are-your-companys-ai-nightmares"
source_title: "What Are Your Company's AI Nightmares?"
tags: ["team-dynamics", "blind-spots"]
related: ["concept-enc-teams"]
confidence: "high"
testable: true
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?"
---
# Cross-functional teams are essential for identifying AI nightmares

**Claim:** No single department can foresee all AI risks. Data scientists identify **technical** sources of nightmares invisible to marketers; marketers understand **consumer-behavior** risks invisible to engineers; product designers see **UX failures** invisible to legal. Only by combining these perspectives in a shared language — nightmares — can an organization comprehensively map and mitigate its AI risk surface.

This is the design rationale for [[concept-enc-teams]] and the reason a technologist is mandatory on every team. The action is [[action-form-enc-teams]].

**Confidence: high. Testable: yes** (risk-discovery completeness can be compared across siloed vs. cross-functional teams).

**Enrichment calibration:** *Well supported.* Blackman's framework is explicitly built around cross-functional teams (in the DataCamp podcast he stresses legal, compliance, IT/data, and HR participation), and it aligns with broad AI-governance practice, which advocates cross-functional committees/working groups precisely because AI risk is multidimensional. This is among the least contested claims in the source.


## Related across articles
- [[framework-autonomous-scrum]]
- [[claim-autonomous-scrums-outperform]]