---
id: "counter-adoption-metrics-early"
type: "counter-perspective"
source_timestamps: ["Enrichment Overlay — Counter-Perspectives §6"]
tags: ["metrics", "roi", "measurement"]
related: ["question-measuring-ai-roi", "concept-performative-ai-use"]
challenges: "The prescription to abandon adoption metrics in favor of outcome metrics."
sources: ["adoption"]
sourceVaultSlug: "hbr-seg-adoption"
originDay: 9
articleStem: "hbr-edu-38-ai-workslop"
sourceUrl: "https://hbr.org/2026/01/why-people-create-ai-workslop-and-how-to-stop-it"
sourceTitle: "Why People Create AI “Workslop”—and How to Stop It"
---
# Adoption Metrics May Be Necessary Early

**Adoption metrics may be necessary early.** The open question [[question-measuring-ai-roi]] pits adoption metrics (seats, prompts) against outcome metrics (time saved, error reduction). Some leaders argue early-stage technologies often require crude adoption metrics to justify investment; outcome metrics lag, so strict avoidance of adoption metrics could slow learning and innovation.

The tension: adoption metrics can *drive* [[concept-performative-ai-use]], yet may be unavoidable while outcome measures mature.