HOME/RESEARCH
PUBLIC-EVIDENCE RESEARCH

Go beyond the headline.

Evidence-led cases examining how AI-related improvements move through workflows, workforce decisions, and financial outcomes—and where public reporting leaves questions unanswered.

PUBLIC SOURCES ONLYOBSERVATION ≠ ATTRIBUTIONUNKNOWN ≠ FAILURE
RESEARCH CASES

Follow the evidence.

Each case has its own evidence boundary. An accessible story and a technical assessment need not have the same publication status.

DBS · CASE 003Technical dossier in review

DBS and the Architecture of AI Value Realization

The operating machinery behind DBS's reported AI economics: cross-functional journeys, embedded data expertise, workforce redesign—and limits of attributable financial verification.

KLARNA · CASE 001Existing published case

Klarna’s $59 Million AI Question

How to distinguish customer-service automation claims, ongoing staffing decisions, and sustainable value realization.

Explore the published case ↗
UPS ORION · CASE 002Existing published case

When the Operating Model Catches Up

How route optimization met operational constraints, management adaptation, and company-reported economic gains.

Explore the published case ↗
HOW WE WORK

Readability and rigor aren't opposites.

Accessible editorial pieces invite exploration. Research case files show the claims, sources, alternative explanations, and limits behind the argument. Each publication uses publicly available evidence; neither may borrow confidence from undisclosed professional access.

Examine the diagnostic framework ↗
01

Establish the public evidence and claim boundaries.

02

Separate observed improvements from economic attribution.

03

Test plausible operating-model explanations and alternatives.

04

Publish only to the evidence and review standard achieved.

Research independence

Analysis draws only on publicly available information and excludes confidential, proprietary, customer-specific, or nonpublic knowledge acquired through professional relationships. Company-reported results are identified as such. The Outcome Disconnect remains developmental and is not a certified audit instrument.