Microsoft will remove user names from Productivity Score feature after a privacy backlash, says Microsoft 365 will only aggregate data at the organization level
Microsoft says it will make changes in its new Productivity Score feature, including removing the ability for companies to see data …
The stakes go beyond one feature — Microsoft is positioning itself as the default productivity platform for enterprises, and individual-level tracking was the part of Productivity Score that made that pitch radioactive.
First-order effects
Managers using Microsoft 365 lose the ability to see per-employee usage data; Productivity Score now reports only organization-level aggregates.
Microsoft defuses the immediate surveillance backlash without killing the feature, preserving the enterprise analytics product while removing its most criticized capability.
Second-order effects
Rivals selling employee-monitoring software keep the individual-tracking capability Microsoft just abandoned, making granular surveillance a differentiator for third-party tools rather than a bundled default.
Enterprise buyers gain leverage: the episode shows public pressure can force Microsoft to retool telemetry features, so customers and privacy advocates have a template for pushing back on future Workplace Analytics-style products.
Third-order effects
If the pattern holds — criticism forces aggregation-level retreats, as with the 2017 Windows privacy changes — workplace-analytics tooling may structurally split between org-level dashboards from major platforms and individual monitoring left to specialized vendors.
Regulators weighing employee-data rules get a concrete case study of a major vendor conceding that individual-level productivity tracking crosses a line, strengthening the argument for defaults that protect workers rather than relying on opt-outs like the Data Dignity initiative.
The trend: Employee-productivity telemetry is being pushed toward organization-level aggregation as privacy backlash makes individual-level manager tracking untenable for mainstream platforms.
Our commitment to privacy in Microsoft Productivity Score . The thing I love most about MSFT is that when we screw up, we acknowledge the error and fix it. 10,000 thanks to @WolfieChristl and others for the feedback which led to this change! https://www.microsoft.com/...
Our commitment to privacy in Microsoft Productivity Score - @Office365 << personal take: this is an improvement. When I first saw this what immediately went through my mind was the two awful managers I have had. Taking away names is a start https://www.microsoft.com/...
#Microsoft will remove user names from ‘Productivity Score’ feature after #privacy backlash https://www.geekwire.com/... via @GeekWire #workplace < now “Productivity Score can't be used to monitor individual employees”. Good move if it works
What is baffling for me is that these things were not actually thought of and required someone external to point it out on Twitter for the change to take place. https://twitter.com/...
Would you look at that! Microsoft is scrapping the privacy hellhole of snitching on Office 365 users in response to the outcry. That's... really fucking nice! The future isn't written yet. Keep fighting every damn day as though you had a say. You just might! ❤️✌️ https://twitter.…
I love working for Microsoft for a myriad of reasons but this is probably the biggest: the company can & will modify course based on received feedback. “We also believe that privacy is a human right” 👍👍 https://twitter.com/...
I really like this response from the M365 folks regarding the Productivity Score: feature updates that make it exclusively for organizational health (as intended), and privacy preserving. https://www.microsoft.com/...
Microsoft will be removing all user-level usage measurements from its Productivity Score dashboard. I guessed this was going to happen and this was an over-eager tech deployment scorecard under an unfortunate name. https://twitter.com/...
Good. A creepy tool - and not a very accurate one, given many people use lots of people use a mix of Microsoft and non-Microsoft tools during their workday https://twitter.com/...
That they even CONSIDERED this is really indicative of a broken requirements pipeline in that org. What PM THOUGHT that this was OK??? https://twitter.com/...
Incredible how many people were telling me it wasn't actually surveillance just last week, and that I simply didn't understand the feature https://twitter.com/...