InsightsAI Strategy & Transformation
← All insights All tools

Insight

Real Person Impact: A Summer 2026 Update

Published 2026-06-07 · Mike Kennedy

Agentic EnterpriseStrategyMulti-Agent OrchestrationReal People ImpactData FoundationOperating Model & GovernanceLeadership

Real Person Impact: A Summer 2026 Update

Why I lead with RPI, headless in the flow of work, and an AI-first lens on every transformation dollar — Mike Kennedy

This summer the "augment, don't replace" argument stopped being a position and became consensus. Three sources that don't talk to each other — our own platform doctrine (Imtiaz, Stokes), Microsoft's 7 trends to watch in 2026, and Stanford HAI's newly launched AI and Organizations Lab under Melissa Valentine — all land on the same headline: agentic AI creates value by amplifying people, not replacing them.

But consensus on a slogan is worth almost nothing. "Augment humans" stays unfalsifiable until you can say which humans, doing what, measurably better, by when. That gap is exactly where most agentic programs stall. So I lead client conversations with three things, in this order: Real Person Impact, headless in the flow of work, and an AI-first lens on every transformation dollar.

1. Real Person Impact (RPI) is the scorecard

RPI is my answer to the productivity-claim problem. I define Real Person Impact across three measures, each inside a defined time bound:

Three things make this the right frame for the room. First, it keeps the human at the center — impact is measured on a person, which is the augmentation thesis made accountable instead of rhetorical. Second, it is time-bound, which matters more than it sounds: a recent survey found 71% of global CIOs would freeze or cut AI budgets if value couldn't be demonstrated within two years. RPI is built to answer that clock. Third, it is the discipline Stanford is about to start enforcing from the outside — the AI and Organizations Lab exists to test workplace AI with empirical research rather than broad productivity claims. An RPI figure with a defined denominator and a time bound survives that scrutiny. A "16x faster, half the TCO" headline with no baseline does not.

That last point is self-imposed. Where we assert performance, RPI forces the honest questions: measured against what, for whom, by when.

2. Headless removes the friction — that's the mechanism

RPI doesn't materialize from buying tools. It materializes when AI runs in the flow of work rather than behind one more surface a person has to log into and operate.

This is the part of the headless argument I find most under-told. For twenty years we asked people to be the operating layer of systems that were never designed for the way they actually work — updating records, logging activity, navigating UIs after the fact. Headless inverts that. A rep finishes a call and tells the agent what happened; the agent updates the opportunity, logs the call, drafts the agreement, and runs all of it against the governed metadata model — validation, sharing, approvals intact — while the human reviews and approves. The friction of accessing the platform's power collapses. Microsoft's framing of agents as digital coworkers is the same idea seen from the outside: the human steers, the agent does the operating.

Removing that friction is not a UX nicety. It is the direct mechanism that converts platform capability into cost takeout, revenue uplift, and recovered capacity — into RPI. No friction removal, no impact to measure.

3. Every transformation dollar gets an AI-first lens

If RPI is the goal and headless is the mechanism, the investment rule follows: every dollar pointed at digital transformation should pass through an AI-first lens before it's committed.

The external case is now strong. Deloitte's investment-ROI work argues for setting spending minimums so AI doesn't starve the rest of the portfolio, and finds that CFO- and CDO-led "profitability masters" capture the strongest digital ROI — discipline at the top of the house, not scattered experimentation. The cautionary half is just as clear: Google Cloud's "agent sprawl" argument shows decentralized AI spend without a unifying, governed stack actively undermines enterprise ROI, and the majority of CEOs in PwC's latest survey still report no measurable AI benefit to date. Money is moving — by one estimate US firms spent roughly $37B on generative AI in 2025 — but undisciplined money produces sprawl, not impact.

An AI-first lens is the antidote: don't fund a workflow, a UI, or a system upgrade without first asking whether an agent should operate it, what RPI it would generate, and whether the spend points at the governed platform layer or just stands up another silo.

The fault line underneath all three

These pillars rest on the platform-versus-wrapper question I keep returning to. RPI is only durable if the impact is governed — measured against a trustworthy metadata, semantics, and permissions layer rather than a fragile bolt-on. Headless friction removal only works if the agent operates on that governed layer. And the AI-first lens only protects ROI if it pushes spend toward the platform substrate instead of sprawl.

The HBR/Deloitte paper locates orchestration in the service wrapper; Stokes locates it in the platform's governed runtime; Microsoft's per-agent identity, least-privilege, and "double agents" trend quietly votes for the platform side. The governed layer is where Real Person Impact is ultimately defended.

What I'm watching into the fall

Two things. Whether Stanford's lab attaches real numbers to the cost of un-redesigned work — which would give RPI a vendor-neutral benchmark to anchor against. And whether governance-in-the-runtime hardens from a narrative into an actual CIO buying criterion. If it does, RPI stops being a story we tell and becomes the number we're measured on. That's the number I'd want to be measured on.

Sources