Kronos Scheduling Algorithm Allegedly Caused Financial Issues for Starbucks Employees

August 14, 2014

The consequences of Kronos's flawed scheduling algorithm at Starbucks have left a lasting impact on vulnerable hourly workers, who were unfairly caught in the middle of management decisions that prioritized corporate interests over employee well-being. As this scandal highlights, the use of automated systems without proper oversight can exacerbate existing inequalities and undermine efforts to create fair and equitable workplaces. The incident serves as a stark reminder of the need for greater accountability and transparency in scheduling practices, which is why we invite you to explore this issue further with us JOIN US.

Matched TAIM controls

Suggested mapping from embedding similarity (not a formal assessment). Browse all TAIM controls

Alleged deployer
Starbucks
Alleged developer
Kronos
Alleged harmed parties
Starbucks employees

AI governance case studies

For forensic AI governance failure analysis (TAIMScore™ case studies), browse Human Signal’s Failure Files™.

Source

Data from the AI Incident Database (AIID). Cite this incident: https://incidentdatabase.ai/cite/10

Data source

Incident data is from the AI Incident Database (AIID).

When citing the database as a whole, please use:

McGregor, S. (2021) Preventing Repeated Real World AI Failures by Cataloging Incidents: The AI Incident Database. In Proceedings of the Thirty-Third Annual Conference on Innovative Applications of Artificial Intelligence (IAAI-21). Virtual Conference.

Pre-print on arXiv · Database snapshots & citation guide

We use weekly snapshots of the AIID for stable reference. For the official suggested citation of a specific incident, use the “Cite this incident” link on each incident page.