---
id: "question-resource-building-mechanics"
type: "open-question"
source_timestamps: ["§ 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: ["implementation-details", "tooling"]
related: ["framework-enc-questions"]
resolutionPath: "Concrete examples of the outputs generated by an ENC team during a 6-10 week pilot."
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?"
---
# What specific 'resources' do ENC teams build?

**Open question:** Question 2 of [[framework-enc-questions]] asks, *"What resources will you build to avoid those nightmares?"* — but the text leaves "resources" highly abstract. It is unclear whether this means **technical guardrails** (code, filters), **new localized policies**, **human-in-the-loop workflows**, or something else.

**Why it matters:** "Resource building" is where the framework converts insight into mitigation; if it stays undefined, the ENC risks becoming a diagnosis without a treatment.

**Resolution path:** Concrete examples of the outputs generated by [[concept-enc-teams]] during a 6-10 week pilot ([[action-run-enc-pilot]]).

**Enrichment note:** Adjacent literature suggests the likely toolbox — red-teaming, adversarial evaluation, benchmarking, penetration testing, human-in-the-loop review — with ENC teams acting as the organizational structure that *initiates and interprets* those technical exercises in light of business-specific nightmares. Blackman's own broader work references red-teaming and benchmarking as part of this adjacent toolset.