Promises and Outcomes: what was announced, what happened

This is not a corporate scorecard. It preserves the original scope and compares it with attributable outcome evidence, including the honest state “deadline passed / outcome unverified.”

Last reviewed

12 September 2026

Coverage

Documented facts and clearly stated limits

Regional note

U.S. reference; verify region, device, edition, account and plan where applicable

Outcome record

Specific, attributable commitments only.

Aspirational slogans are context, not promises with invented deadlines. Each entry preserves the original scope and distinguishes an announcement from a demonstrated outcome.

01 / Outcome records

reversed before retail launch

Retail Xbox One policy after reversal

Promise/event date: 2013-06-19
Confidence: high

outcome unverified

Selected-disc digital-access test

Promise/event date: 2026-08-26
Confidence: medium on announcement; low on broad applicability

effective implementation unverified

Announced cloud-gaming changes

Promise/event date: 2026-09-03
Confidence: high on notice; unresolved on current application

completed transaction; consequences require separate evidence

Activision Blizzard King transaction completion

Promise/event date: 2023-10-13
Confidence: high on completion

Verification rule

Store the original wording, scope and time precision. Check the source and outcome separately. “Partially delivered” must name the region, device or feature boundary. A past date without adequate evidence becomes outcome unverified, not automatically broken promise.

The 2013 reversal demonstrates why proposal, reversal and shipped state must remain separate.

Method

Claims separate documented facts from interpretation and uncertainty. Read our method.

Updates

Material factual revisions are recorded publicly. View the correction log.