Gabbard v. Amazon.com Services, LLC

CourtDistrict Court, E.D. Kentucky
DecidedMay 1, 2023
Docket5:22-cv-00058
StatusUnknown

This text of Gabbard v. Amazon.com Services, LLC (Gabbard v. Amazon.com Services, LLC) is published on Counsel Stack Legal Research, covering District Court, E.D. Kentucky primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Gabbard v. Amazon.com Services, LLC, (E.D. Ky. 2023).

Opinion

UNITED STATES DISTRICT COURT EASTERN DISTRICT OF KENTUCKY CENTRAL DIVISION (at Lexington)

AARON GABBARD, ) ) Plaintiff, ) Civil Action No. 5: 22-058-DCR ) V. ) ) AMAZON.COM SERVICES LLC, ) MEMORANDUM OPINION ) AND ORDER Defendant. )

*** *** *** *** Plaintiff Aaron Gabbard claims that Defendant Amazon.com Services LLC set him up for failure after he requested accommodations for his disabilities. But Amazon contends that, despite its best efforts to help Gabbard succeed, he simply did not meet the expectations required for his position and was fired. Gabbard filed suit in the Bath Circuit Court alleging discrimination claims under the Americans with Disabilities Act, the Family and Medical Leave Act, and the Kentucky Civil Rights Act. He also claims that Amazon provided false information to the Kentucky Department of Unemployment Insurance, which prevented him from obtaining unemployment benefits. Because there is no genuine issue of material fact that Gabbard was fired due to his performance—not his alleged disabilities or his requests for accommodations—summary judgment will be granted in favor of Amazon with respect to the discrimination claims. However, because Amazon failed to develop any argument with respect to the false statements claim, which is based in state law, summary judgment will be denied on that claim and the remainder of the case will be remanded to state court. I. Background Plaintiff Aaron Gabbard (the “plaintiff” or “Gabbard”) began his career at Amazon.com Services LLC (“Amazon” or the “defendant”) as a customer service associate (“CSA”) at the

Winchester, Kentucky call center in June 2013. [Record No. 32-1, pp. 9-10] Gabbard reports that, while he led that position, he would sometimes need to leave work due to anxiety. Id. at 16. Early on, he was not required to ask in advance for time off. Instead, if he had time off available for use, he would “put it in the system and go on.” Gabbard was promoted to the remote position of customer relations specialist (“ECR”) on April 1, 2018. Id. at 19-20. Brian Ferguson was assigned as Gabbard’s manager. According to Gabbard, he and Ferguson discussed Gabbard’s anxiety often and Ferguson told

him: “Hey, if you need some time off, take the time off, I’ll provide you with those accommodations or voluntary time off if you need it…. [W]e all … need a break and I know you get anxiety.” Id. at 20. Jenna Foster was assigned as Gabbard’s manager approximately six months into his role as ECR. Id. at 22. Foster never made any negative comments about Gabbard’s alleged medical conditions or their impacts on his performance as an ECR specialist. Gabbard thought

that Foster criticized him too harshly at times and he explained to her that “simply [he had] to be treated slightly different.” Gabbard and Foster had discussions about his attendance of therapy and trials of different medications. Foster would allow him to take time off when he did not feel well. Id. at 23. Foster placed Gabbard on a 60-day Development Plan on March 1, 2019. Foster outlined the following performance concerns: Throughout 2018 there were concerns on bias for action and delivering results from [Gabbard’s] end. While [he] would enthusiastically take on new projects, [he] would often get bogged down by the details and lose focus on getting the project to completion, the result of this being that not only [he was] delaying a resolution for [the] customer but also delaying improvements for [Amazon’s] team and business partners. With clear direction and consistent follow-up, [he was] completing tasks, but as a Level 4 ECR specialist, there’s an expectation that [he] will be able to perform well in a sometimes ambiguous space. . . .

Gabbard acknowledged that Foster would “get onto [him] about things,” which included sending an email in violation of company policy. Id. at 23, 31. He denied, however, that he had any performance issues other than making grammar and spelling mistakes due to his alleged dyslexia. Id. at 27-29. Gabbard apparently met the goals of the March 2019 Development Plan and held the ECR position until April 2020, when he applied for and received a temporary position as acting customer escalation insight project manager (“CEI”). Id. at 32. This position also was remote and involved a change in responsibilities. While other employees told Gabbard they considered it “an internal promotion,” it did not result in a change in Gabbard’s pay. Id. at 33. Nicolette Kyte was Gabbard’s manager while he held the acting CEI position. His scheduled work hours were 9:00 a.m. to 5:00 p.m., Monday through Friday. Gabbard and Kyte often communicated by instant messages through Amazon Chime. Id. at 36. At some point, Gabbard told Kyte that he had anxiety and hypersomnia, which he described as an “inability to stay awake during certain times.” Id. at 36. On May 5, 2020, at 8:46 a.m., Kyte messaged Gabbard: “Good morning!” Gabbard responded at 11:29 a.m., stating, “Hey, I had to put time in today[.] I’m not feeling well at all[.] [M]y eyes are swelled up like I got stung by a bee or something.” [Record No. 32-2, p. 26] Kyte told Gabbard that she was worried when she did not see him online and realized that he did not have her cell number “for texts in cases like this.” Id. Gabbard messaged Kyte on May 12, 2020, at 9:50 a.m., advising her that he was taking

a half day off to “get things straight with [his] place.” Kyte responded: “Make sure you are communicating prior to shift on any changes. Just like in ECR—text or chime so I know. Also, understand prioritization in CEI is critical as we do have deadlines for work—so if you have any training/low priority meetings set this week we may need to push those to make up for the half day, etc.” Gabbard responded, “Okie Doke. May be back in sooner just had a bunch of things cone [sic] up I needed to take care of.” Id. at 29. The following week, Gabbard asked Kyte, “Would you be able to have our Daily Sync

up a little earlier today? I was going to see if I could leave out a few hours earlier.” Id. at 33. Then, on May 28, 2020, Gabbard advised Kyte that he was late due to oversleeping. Rather than notifying her immediately, he waited until after he clocked in for work to log his missed time. Kyte responded, “After you logged in—why didn’t you ping me to let me know you had been late? We’ve had so many conversations about the need to notify me when these things occur. In this case, obviously it wasn’t an option prior to it occurring—but as soon as you

know is what we’ve discussed in the past.” Id. at 36. Gabbard responded, “I entered my time as soon as I got in, I thought for sure that would notify you to let you know that I entered the time, I’ll be more direct and ping you if anything at all pops up.” Kyte admonished Gabbard that “entering time is the expectation only to cover your time off.” She further advised him to contact her directly using whatever method he could get to first. Gabbard stated that he had been embarrassed about oversleeping. Kyte told him, “embarrassment aside, your focus always should be to do what you need to do to ensure you are following policy.” Id. Later that day, Gabbard contacted Doug Berry, Amazon’s Senior Human Resources

Partner, and advised him that he had a medical condition he believed was affecting his attendance. [Record No. 32-2, p. 3] Gabbard wanted to know if there were any accommodations that he could get for his condition or if Berry could do anything to help. Berry instructed Gabbard to contact Amazon’s Disability Leave Services (“DLS”) department, which would be able to assist him in submitting an intermittent leave request under the Family and Medical Leave Act (“FMLA”).1 [Record No. 32-2, p. 3] Berry maintains that he did not inform Kyte that Gabbard contacted him concerning an accommodation. Id.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

McDonnell Douglas Corp. v. Green
411 U.S. 792 (Supreme Court, 1973)
Anderson v. Liberty Lobby, Inc.
477 U.S. 242 (Supreme Court, 1986)
Carnegie-Mellon University v. Cohill
484 U.S. 343 (Supreme Court, 1988)
Spees v. James Marine, Inc.
617 F.3d 380 (Sixth Circuit, 2010)
Bereatha Kyle-Eiland v. Albert Neff
408 F. App'x 933 (Sixth Circuit, 2011)
Frances Hankins v. The Gap, Inc.
84 F.3d 797 (Sixth Circuit, 1996)
Michael E. Kleiber v. Honda of America Mfg., Inc.
485 F.3d 862 (Sixth Circuit, 2007)
Seeger v. Cincinnati Bell Telephone Co., LLC
681 F.3d 274 (Sixth Circuit, 2012)
Carole Tingle v. Arbors at Hilliard
692 F.3d 523 (Sixth Circuit, 2012)
Dobrowski v. Jay Dee Contractors, Inc.
571 F.3d 551 (Sixth Circuit, 2009)
Mickey v. Zeidler Tool and Die Co.
516 F.3d 516 (Sixth Circuit, 2008)
Bryson v. Regis Corp.
498 F.3d 561 (Sixth Circuit, 2007)
Daugherty v. Sajar Plastics, Inc.
544 F.3d 696 (Sixth Circuit, 2008)
Anthony Rorrer v. City of Stow
743 F.3d 1025 (Sixth Circuit, 2014)
Mark Laster v. City of Kalamazoo
746 F.3d 714 (Sixth Circuit, 2014)

Cite This Page — Counsel Stack

Bluebook (online)
Gabbard v. Amazon.com Services, LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/gabbard-v-amazoncom-services-llc-kyed-2023.