---
id: "action-pair-metrics-with-safety-signals"
type: "action-item"
source_timestamps: ["§ What Leaders Must Do Differently", "¶30"]
tags: ["metrics", "governance", "leadership"]
related: ["claim-usage-not-buy-in", "concept-performative-ai-usage", "prereq-adoption-telemetry", "prereq-psychological-safety"]
action: "Pair AI adoption telemetry with surveys measuring AI angst and psychological safety to gauge genuine buy-in."
outcome: "Prevents leaders from optimizing for superficial activity and helps identify hidden organizational resistance."
speakers: ["Erin Eatough", "Keith Ferrazzi", "Wendy Smith", "Shonna Waters"]
sources: ["tail2"]
sourceVaultSlug: "hbr-seg-tail2"
originDay: 2
articleStem: "hbr-tail-127-ai-adoption-stalls"
sourceUrl: "https://hbr.org/2026/02/why-ai-adoption-stalls-according-to-industry-data"
sourceTitle: "Why AI Adoption Stalls, According to Industry Data"
---
# Pair Usage Metrics With Psychological Safety Signals

**Action.** Stop relying solely on license activation and daily active usage to measure AI adoption success. Implement mechanisms to measure **AI angst, psychological safety, and openness to experimentation** alongside telemetry data, so you can distinguish genuine engagement from calculated, fear-driven participation.

**Why it works.** Because usage can reflect [[concept-performative-ai-usage]], telemetry alone hides resistance — the core of [[claim-usage-not-buy-in]]. Pairing it with sentiment signals surfaces the emotional context leaders are otherwise blind to.

**Outcome.** Prevents leaders from optimizing for superficial activity and helps identify hidden organizational resistance before it becomes disengagement or turnover.

**Prerequisites:** [[prereq-adoption-telemetry]] (understand the baseline metrics being critiqued) and [[prereq-psychological-safety]] (understand the construct being measured). This action operationalizes shift #2 of [[framework-three-leadership-shifts]]. The open problem of doing this continuously at scale is [[question-measuring-genuine-buy-in]].