42/100

Emerging evidence

Published recordLaborProblem Space (a documented problem)

'Working Here Is Joyless & Demoralising': Microsoft Employees' Open Letter Accuses Company Of Putting AI Ahead Of People

Truvace record
TRV-2026-2442raw data (JSON)
Version
v1Published
First published
Evidence type
News report
Sources
1 sourceJournalism
sha256
15ababc0f18b…check it

A group of current and former Microsoft employees has circulated an open letter accusing the company of putting AI ahead of workers, customers and climate commitments. The letter says morale has declined amid heavier AI investment, workloads and reorganisations. It gained attention after Microsoft offered voluntary buyouts to about 60,000 staff across India, the US, UK and Canada.

The problem

In an open letter, current and former Microsoft workers said the company's AI push left staff with heavier workloads, little training, repeated reorganisations and fear of replacement, while the company offered buyouts to about 60,000 employees.

What this doesn’t fix

The letter's claims come from anonymous signatories, and Coleman said the buyouts are not tied to how AI is changing work, so the link between AI and the morale decline is asserted rather than shown.

Sources

1 on file
  1. Free Press Journalfreepressjournal.in
    Journalism2026-11-09

Cite this record

v1

Truvace Impact Record TRV-2026-2442, v1: “'Working Here Is Joyless & Demoralising': Microsoft Employees' Open Letter Accuses Company Of Putting AI Ahead Of People.” Truvace, 2026-11-09. /record/TRV-2026-2442 (accessed on the day you copy it). sha256 15ababc0f18b4fb3…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv115ababc0f18b…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2442 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.