Amazon memo calls AI usage metrics flawed but keeps internal tracking
Amazon’s internal memo, authored by VP Terkowitz in September 2026, redefines how the company measures software engineers’ AI adoption. The document rejects token counts and raw code generation as valid productivity metrics, calling them ‘deeply flawed’ because they don’t reflect customer value. Instead, it instructs engineers to document cases where AI tools don’t help their work and frames…
Key points
- Amazon’s memo rejects token counts and raw code generation as flawed productivity metrics, per VP Terkowitz’s September 2026 guidance
- Engineers must document cases where AI tools fail to help work, framing skepticism as a skill, but usage data remains available to managers
- KiroRank, an internal leaderboard for token usage, was deprecated in May 2026 after employees gamed it to inflate metrics
The memo’s timing is notable amid Amazon’s broader push to prove AI’s business impact, alongside record spending on AI infrastructure. While it avoids outright bans, the guidance creates tension: managers are told to study adoption data for insights but not to rank employees by it. Critics, like commentator Corey Quinn, argue the memo’s mixed messaging—calling token counts flawed while keeping them in play—creates ambiguity, especially during a period of job cuts. The memo also highlights a cultural contradiction: AWS bills customers by token consumption while telling its own staff to treat tokens as a cost to minimize. Engineers are now asked to prove AI’s limitations in writing, adding administrative burden to an already strained workforce.
Amazon AI Memo Mixes 2 Messages After KiroRank
shattered.io · 31 October 2026
Loading the full article…
This text was published by shattered.io and written by Dr. Elena Marchetti. It is reproduced here with attribution so you can read it in full; the rights remain with the publisher. Read it at the source ↗
The headline, key points and digest above were generated by Digest AI's editorial model from the linked sources. Automated summaries can contain errors: the sources are the record. Spotted a mistake? Tell us. Published by Martin K., who runs Digest AI and handles corrections.
More in Policy & Regulation
All →- Microsoft warns North Korean hackers use AI to scale phishing and malware · 2 src
- Accenture contractor allegedly linked Pentagon system to Claude AI agent for two months · 3 src
- OpenAI updates Model Spec with five core values and renames AI as GPT · 12 src
- Anthropic updates Claude to block AI-generated game clones and reverse engineering · 4 src
- Judge allows NAACP lawsuit over xAI data center pollution to proceed · 1 src
Comments
via GitHub Discussions