Skip to Content
logologo
AI Incident Database
Open TwitterOpen RSS FeedOpen FacebookOpen LinkedInOpen GitHub
Open Menu
発見する
投稿する
  • ようこそAIIDへ
  • インシデントを発見
  • 空間ビュー
  • テーブル表示
  • リスト表示
  • 組織
  • 分類法
  • インシデントレポートを投稿
  • 投稿ランキング
  • ブログ
  • AIニュースダイジェスト
  • リスクチェックリスト
  • おまかせ表示
  • サインアップ
閉じる
発見する
投稿する
  • ようこそAIIDへ
  • インシデントを発見
  • 空間ビュー
  • テーブル表示
  • リスト表示
  • 組織
  • 分類法
  • インシデントレポートを投稿
  • 投稿ランキング
  • ブログ
  • AIニュースダイジェスト
  • リスクチェックリスト
  • おまかせ表示
  • サインアップ
閉じる

インシデント 10: Kronos Scheduling Algorithm Allegedly Caused Financial Issues for Starbucks Employees

概要: Kronos’s scheduling algorithm and its use by Starbucks managers allegedly negatively impacted financial and scheduling stability for Starbucks employees, which disadvantaged wage workers.

ツール

新しいレポート新しいレポート新しいレスポンス新しいレスポンス発見する発見する履歴を表示履歴を表示

組織

すべての組織を表示
Alleged: Kronos developed an AI system deployed by Starbucks, which harmed Starbucks employees.

インシデントのステータス

インシデントID
10
レポート数
10
インシデント発生日
2014-08-14
エディタ
Sean McGregor, Khoa Lam
Applied Taxonomies
CSETv0, GMF, CSETv1, MIT

CSETv1 分類法のクラス

分類法の詳細

Incident Number

The number of the incident in the AI Incident Database.
 

10

Special Interest Intangible Harm

An assessment of whether a special interest intangible harm occurred. This assessment does not consider the context of the intangible harm, if an AI was involved, or if there is characterizable class or subgroup of harmed entities. It is also not assessing if an intangible harm occurred. It is only asking if a special interest intangible harm occurred.
 

no

Date of Incident Year

The year in which the incident occurred. If there are multiple harms or occurrences of the incident, list the earliest. If a precise date is unavailable, but the available sources provide a basis for estimating the year, estimate. Otherwise, leave blank. Enter in the format of YYYY
 

2014

Estimated Date

“Yes” if the data was estimated. “No” otherwise.
 

Yes

Multiple AI Interaction

“Yes” if two or more independently operating AI systems were involved. “No” otherwise.
 

no

Embedded

“Yes” if the AI is embedded in a physical system. “No” if it is not. “Maybe” if it is unclear.
 

no

CSETv0 分類法のクラス

分類法の詳細

Public Sector Deployment

"Yes" if the AI system(s) involved in the accident were being used by the public sector or for the administration of public goods (for example, public transportation). "No" if the system(s) were being used in the private sector or for commercial purposes (for example, a ride-sharing company), on the other.
 

No

Infrastructure Sectors

Where applicable, this field indicates if the incident caused harm to any of the economic sectors designated by the U.S. government as critical infrastructure.
 

Food and agriculture

Lives Lost

Were human lives lost as a result of the incident?
 

No

Intent

Was the incident an accident, intentional, or is the intent unclear?
 

Unclear

Near Miss

Was harm caused, or was it a near miss?
 

Unclear/unknown

Ending Date

The date the incident ended.
 

2015-01-01

GMF 分類法のクラス

分類法の詳細

Potential AI Technology Snippets

One or more snippets that justify the classification.
 

(Snippet Text: “You’re waiting on your job to control your life,” she said, with the scheduling software used by her employer dictating everything from “how much sleep Gavin will get to what groceries I’ll be able to buy this month.”, Related Classifications: Regression), (Snippet Text: In a follow-up piece, the author, Jodi Kantor, points directly to Kronos' scheduling software as the root of the problem., Related Classifications: Diverse Data)

MIT 分類法のクラス

Machine-Classified
分類法の詳細

Risk Subdomain

A further 23 subdomains create an accessible and understandable classification of hazards and harms associated with AI
 

5.2. Loss of human agency and autonomy

Risk Domain

The Domain Taxonomy of AI Risks classifies risks into seven AI risk domains: (1) Discrimination & toxicity, (2) Privacy & security, (3) Misinformation, (4) Malicious actors & misuse, (5) Human-computer interaction, (6) Socioeconomic & environmental harms, and (7) AI system safety, failures & limitations.
 
  1. Human-Computer Interaction

Entity

Which, if any, entity is presented as the main cause of the risk
 

AI

Timing

The stage in the AI lifecycle at which the risk is presented as occurring
 

Post-deployment

Intent

Whether the risk is presented as occurring as an expected or unexpected outcome from pursuing a goal
 

Unintentional

インシデントレポート

レポートタイムライン

+1
Working Anything but 9 to 5
For some Starbucks workers, job leaves bitter tasteAfter A Wave Of Bad Press, This Controversial Software Company Is Making Changes+1
Kronos shift scheduling software a grind for Starbucks worker
+1
​Is Starbucks shortchanging its baristas?
"I Hope That Howard Schultz Hears My Story": A Starbucks Barista on Why He's Fighting for Fair SchedulingHow Starbucks started taking their schedules seriously…and why you should tooThe Seattle Times: Starbucks says its scheduling practices have improved
Working Anything but 9 to 5

Working Anything but 9 to 5

nytimes.com

For some Starbucks workers, job leaves bitter taste

For some Starbucks workers, job leaves bitter taste

cbsnews.com

After A Wave Of Bad Press, This Controversial Software Company Is Making Changes

After A Wave Of Bad Press, This Controversial Software Company Is Making Changes

buzzfeednews.com

Kronos shift scheduling software a grind for Starbucks worker

Kronos shift scheduling software a grind for Starbucks worker

searchhrsoftware.techtarget.com

THE GRIND: Striving for Scheduling Fairness at Starbucks

THE GRIND: Striving for Scheduling Fairness at Starbucks

populardemocracy.org

​Is Starbucks shortchanging its baristas?

​Is Starbucks shortchanging its baristas?

cbsnews.com

Starbucks vows to do more to ease barista schedules

Starbucks vows to do more to ease barista schedules

money.cnn.com

"I Hope That Howard Schultz Hears My Story": A Starbucks Barista on Why He's Fighting for Fair Scheduling

"I Hope That Howard Schultz Hears My Story": A Starbucks Barista on Why He's Fighting for Fair Scheduling

thestranger.com

How Starbucks started taking their schedules seriously…and why you should too

How Starbucks started taking their schedules seriously…and why you should too

quinyx.com

The Seattle Times: Starbucks says its scheduling practices have improved

The Seattle Times: Starbucks says its scheduling practices have improved

fairworkweek.org

Working Anything but 9 to 5
nytimes.com · 2014

SAN DIEGO — In a typical last-minute scramble, Jannette Navarro, a 22-year-old Starbucks barista and single mother, scraped together a plan for surviving the month of July without setting off family or financial disaster.

In contrast to the…

For some Starbucks workers, job leaves bitter taste
cbsnews.com · 2014

Liberte Locke, a 32-year-old "barista" at a Starbucks (SBUX) in New York City, is fed up.

"Starbucks' attitude is that there's always someone else who can do the job," she said in running through her complaints about life at the java giant.…

After A Wave Of Bad Press, This Controversial Software Company Is Making Changes
buzzfeednews.com · 2015

In April, the New York attorney general's office launched an investigation into the scheduling practices of 13 national retail chains, distributing a letter to the Gap, Target, J.C. Penney, and 10 other companies. The letter asked, among ot…

Kronos shift scheduling software a grind for Starbucks worker
searchhrsoftware.techtarget.com · 2015

Caitlin O'Reilly-Green, a barista at an Atlanta Starbucks, says a manager blames her erratic hours on the staff scheduling software used by the giant coffee chain.

"When you try to bring up issues with it, they just kind of blame it on the …

THE GRIND: Striving for Scheduling Fairness at Starbucks
populardemocracy.org · 2015

A 2015 nationwide survey of Starbucks workers reveals that the company is not living up to its commitment to provide predictable, sustainable schedules to its workforce. Starbucks’ frontline employees bear the brunt of the management impera…

​Is Starbucks shortchanging its baristas?
cbsnews.com · 2015

For Starbucks (SBUX) barista Kylei Weisse, working at the coffee chain helps him secure health insurance and some extra money while he studies at Georgia Perimeter College. What it doesn't provide is the kind of stable schedule that the com…

Starbucks vows to do more to ease barista schedules
money.cnn.com · 2015

An internal memo from a Starbucks executive this week urged store managers to "go the extra mile" to improve workers' schedules.

The letter was distributed on Tuesday and refers to a New York Times story that was set to be published the fol…

"I Hope That Howard Schultz Hears My Story": A Starbucks Barista on Why He's Fighting for Fair Scheduling
thestranger.com · 2015

On Tuesday, I wrote about Starbucks baristas and other food service workers who marched downtown at sunrise to call for fair scheduling from their employers. Workers said they often get little notice of when they're scheduled to work and th…

How Starbucks started taking their schedules seriously…and why you should too
quinyx.com · 2016

The best schedules deliver two things; they ensure a business maximises profit while at the same time keeping the workforce happy and motivated.

At first glance, these two outcomes seem to be coming from opposite sides of the spectrum. To m…

The Seattle Times: Starbucks says its scheduling practices have improved
fairworkweek.org · 2016

Originally published on Seattle Times on June 4, 2016 at 8:00 am

The company took a lot of heat in 2014 when The New York Times described scheduling practices that made some employees miserable. But the coffee giant says its policies and so…

バリアント

「バリアント」は既存のAIインシデントと同じ原因要素を共有し、同様な被害を引き起こし、同じ知的システムを含んだインシデントです。バリアントは完全に独立したインシデントとしてインデックスするのではなく、データベースに最初に投稿された同様なインシデントの元にインシデントのバリエーションとして一覧します。インシデントデータベースの他の投稿タイプとは違い、バリアントではインシデントデータベース以外の根拠のレポートは要求されません。詳細についてはこの研究論文を参照してください

よく似たインシデント

テキスト類似度による

Did our AI mess up? Flag the unrelated incidents

Predictive Policing Biases of PredPol

Policing the Future

Nov 2015 · 17 レポート
Poor Performance of Tesla Factory Robots

Tesla’s Factory Woes Reveals Why You Shouldn’t Automate Everything

Oct 2016 · 28 レポート
Female Applicants Down-Ranked by Amazon Recruiting Tool

2018 in Review: 10 AI Failures

Aug 2016 · 33 レポート
前のインシデント次のインシデント

よく似たインシデント

テキスト類似度による

Did our AI mess up? Flag the unrelated incidents

Predictive Policing Biases of PredPol

Policing the Future

Nov 2015 · 17 レポート
Poor Performance of Tesla Factory Robots

Tesla’s Factory Woes Reveals Why You Shouldn’t Automate Everything

Oct 2016 · 28 レポート
Female Applicants Down-Ranked by Amazon Recruiting Tool

2018 in Review: 10 AI Failures

Aug 2016 · 33 レポート

リサーチ

  • “AIインシデント”の定義
  • “AIインシデントレスポンス”の定義
  • データベースのロードマップ
  • 関連研究
  • 全データベースのダウンロード

プロジェクトとコミュニティ

  • AIIDについて
  • コンタクトとフォロー
  • アプリと要約
  • エディタのためのガイド

インシデント

  • 全インシデントの一覧
  • フラグの立ったインシデント
  • 登録待ち一覧
  • クラスごとの表示
  • 分類法

2024 - AI Incident Database

  • 利用規約
  • プライバシーポリシー
  • Open twitterOpen githubOpen rssOpen facebookOpen linkedin
  • 86fe0f5