Roberts v. International Business Machines Corp.

896 F. Supp. 2d 1068, 2012 WL 4052515, 2012 U.S. Dist. LEXIS 130413
CourtDistrict Court, N.D. Oklahoma
DecidedSeptember 13, 2012
DocketCase No. 11-CV-040 JHP-PJC
StatusPublished
Cited by1 cases

This text of 896 F. Supp. 2d 1068 (Roberts v. International Business Machines Corp.) is published on Counsel Stack Legal Research, covering District Court, N.D. Oklahoma primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Roberts v. International Business Machines Corp., 896 F. Supp. 2d 1068, 2012 WL 4052515, 2012 U.S. Dist. LEXIS 130413 (N.D. Okla. 2012).

Opinion

OPINION AND ORDER 1

JAMES H. PAYNE, District Judge.

Before the Court are Defendant International Business Machines Incorporated’s (IBM’s) Motion for Summary Judgment,2 Plaintiffs Response to Defendant’s Motion for Summary Judgment,3 and Defendant’s Reply in Support of Defendant’s Motion for Summary Judgment.4 For the reasons cited below, Defendant’s Motion for Summary Judgment is GRANTED.5

BACKGROUND

A. Undisputed Material Facts6

The instant case arises from the termination of Plaintiff George M. Roberts, an [1071]*1071at-will employee, from Defendant IBM’s Global Business Services Unit.7 Plaintiff was an application developer, responsible for developing and maintaining software applications for IBM client Williams Companies, Inc. (Williams).8 Plaintiffs main responsibility was a records management application for Williams called “OmniRim,” which required Plaintiff to both maintain the OmniRim application and resolve customer problems as they arose.9 Plaintiff was also responsible for performing similar support work for other smaller applications.10

Plaintiff was made aware of customer problems through the use of “remedy tickets.” 11 When a customer encountered a problem with the OmniRim application, a remedy ticket describing the issue would be electronically generated and delivered electronically to Plaintiff.12 Plaintiff was then responsible for responding to the remedy ticket within a certain period of time, either fixing the problem himself or engaging other team members.13 All employees, including Plaintiff, were responsible for updating the status of open remedy tickets at least once a week.14

In June 2008, Debra Dobson-Morrison became Defendant IBM’s Delivery Manager of the Williams account as well as Plaintiffs manager.15 On or about June 19, 2008, Williams employee Debbie Stubble-field met with Dobson-Morrison to discuss IBM’s work on the Williams account.16 Williams was concerned about the amount of time it was taking to complete remedy tickets for the OmniRim application.17 At that time, Plaintiff was the only IBM employee supporting the OmniRim application for Williams.18 Dobson-Morrison’s contemporaneous notes from the meeting indicate complaints from Williams that Plaintiff in particular did not understand the scope or issue with the API application and a general complaint about OmniRim remedy tickets not being updated weekly as required and having long resolution times.19

Dobson-Morrison’s confidential notes reflect an October 15, 2008 meeting with Ms. Stubblefield, at which they again discussed Williams’ concerns with Plaintiffs work and the backlog of remedy tickets.20 These notes further reflect that the OmniRim application had 9-10 remedy tickets that had not been updated and that Ms. Stubblefield specifically requested Plaintiff no longer be the direct contact for the applications he supported for Williams.21 At this time, Dobson-Morrison named Kathy Gillespie the team lead for the OmniRim application and asked her to oversee Plaintiffs work.22 Dobson-Morrison also informed human resources supervisor Wil[1072]*1072liam A. Steele of her concerns regarding Plaintiffs job performance.23

On Plaintiffs 2008 year-end Employee Performance Feedback Form, DobsonMorrison noted client complaints and also noted Plaintiffs lack of collaboration teamwork and Plaintiffs difficulties in following through and setting priorities.24 The Form also states that Plaintiff refused to train a back-up employee and notes that this is likely because Plaintiff believed that a lack of a back-up provided him job security.25 Based on the job performance issues cited, Plaintiff received a 2008 year-end performance based review rating of “PBC 3,” signifying he was among the lowest contributors compared to his peers supporting the Williams account and that his performance required improvement.26 Plaintiff made no comments and offered no disagreement regarding the poor performance review in the space provided for comments.27

Around February or March of 2009, Plaintiff was selected as part of a resource action named “Project Blue.”28 Resource actions are similar to reductions in force and seek to identify skill sets or practice areas for which there is an overabundance of “resources” or employees.29 Although performance does not factor into what skill areas are selected for a resource action, performance may be a factor in selecting the individuals who will be subject to termination as a result of the resource action.30 Plaintiff was ultimately not terminated as a result of his inclusion in “Project Blue.”31

In March of 2009, Dobson-Morrison and Steele met with Plaintiff to discuss his 2008 performance review and informed Plaintiff that although they had seen some improvement in his job performance, they would need to see further and sustained improvement to consider his performance satisfactory.32 Plaintiffs performance was again formally evaluated on the 2009 MidYear Employee Performance Feedback Form prepared by Dobson-Morrison.33 This review states that Plaintiff lacked strong time-management skills and required significant guidance.34 The Form further notes that Plaintiffs, as well as other team members’, client communications sometimes lacked professionalism and were not always clear and concise.35 The form also noted that Plaintiff in particular had failed to provide requested information and failed to answer direct questions.36

The 2009 Mid-Year Form also details a problem concerning client Williams sending “false complimentary notes” to Plaintiff in an effort to motivate him through positive reinforcement.37 Plaintiff cites these complimentary notes, referred to as [1073]*1073“kudos,” in an effort to demonstrate that Williams was not complaining about Plaintiffs work.38 However, the affidavit of Williams employee Ryan Zilm, who sent the “kudos” to Plaintiff, indicates (1) that Zilm found Plaintiffs technical skills marginal; (2) that Plaintiff took longer to complete tasks and projects than was necessary; (3) that the “kudos” in question were simple thank-you notes sent when Plaintiff completed tasks “relatively quickly;” and (4) that the notes were sent in an effort to motivate Plaintiff and did not reflect Zilm’s overall satisfaction with Plaintiffs performance.39

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
896 F. Supp. 2d 1068, 2012 WL 4052515, 2012 U.S. Dist. LEXIS 130413, Counsel Stack Legal Research, https://law.counselstack.com/opinion/roberts-v-international-business-machines-corp-oknd-2012.