Walls v. Johnson

229 F. Supp. 3d 678, 2017 U.S. Dist. LEXIS 117588, 2017 WL 511859
CourtDistrict Court, E.D. Tennessee
DecidedJanuary 25, 2017
DocketCase No. 1:15-CV-139
StatusPublished
Cited by3 cases

This text of 229 F. Supp. 3d 678 (Walls v. Johnson) is published on Counsel Stack Legal Research, covering District Court, E.D. Tennessee primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Walls v. Johnson, 229 F. Supp. 3d 678, 2017 U.S. Dist. LEXIS 117588, 2017 WL 511859 (E.D. Tenn. 2017).

Opinion

ORDER

TRAVIS R. MCDONOUGH, UNITED STATES DISTRICT JUDGE

Before the Court is a motion for summary judgment filed by Defendant William D. Johnson, President and Chief Executive Officer of the Tennessee Valley Authority (“TVA”).1 (Doc. 25.) For the reasons stated herein, TVA’s motion will be GRANTED IN PART and DENIED IN PART.2

I. BACKGROUND3

Plaintiff Thomas Walls is a former employee of TVA. (See Doc. 30-1, at 1.) TVA is an executive branch corporate agency and instrumentality of the United States of America, 16 U.S.C. §§ 831-831ee, and Bill Johnson is TVA’s President and Chief Executive Officer. (Doc. 30-8, at 1.) Walls began his employment with TVA in February 1985. (Doc. 30-1, at 1.) From 1995 until the end of his career in September of 2014, Walls worked as a Programmer Analyst, reporting to managers in TVA’s Information Technology (“IT”) department. (Id. at 1-2.)

On December 31, 2012, Walls applied for a vacant “System Analyst C” position, a [681]*681position with higher pay. (Id. at 2.) At the time he applied, he was fifty-one-years-old. (Id.) Walls’s supervisor at the time, Satish Patel, was the hiring manager for the System Analyst C position. (Doc. 26-1, at 1.) According to Patel, he wanted a technical expert with experience in at least two programming languages, who could lead teams of two or more programmers, and who could provide technical assistance on multiple computer systems when coding or programming challenges arose.4 (Id. at 2.)

Walls recalls that, not long after he applied for the position, Patel asked him if he was “serious” about the position and suggested that he talk to James Phillips, Patel’s supervisor, about the possibility of reclassifying his current position with a pay raise rather than pursuing the System Analyst C position. (Doc. 30-1, at 2.) When Walls met with Phillips, Phillips asked him when he was going to retire, “questioned whether [he] really wanted the System Analyst position,” and suggested that Walls’s motivation for pursuing the position was simply to “increase [his] salary for pension purposes.” (Id. at 2-3, 5.)

As part of the hiring process, Patel developed criteria to determine each applicant’s qualifications from written records, including resumes and internal TVA service reviews, and required each applicant to take a standardized assessment test to assess proficiency with different programming technologies. (Doc. 26-1, at 4.) According to Patel, the interview was weighted as seventy percent of the selection criteria, with the remaining thirty percent based on the records review and assessment test. (Doc. 30-2, at 11.)

On February 5, 2013, Walls interviewed for the System Analyst C position. (Doc. 26-1, at 5; Doc. 30-1, at 3.) Following his interview, Walls wrote in his planner, “[i]n-terviewed at 10 am for Systems Analyst job; I thought it went ok. Obviously [Patel] thought I was wasting his time; kept checking his blackberry & even left while I was answering a question.” (Doc. 26-8, at 1.) After taking the standardized assessment on February 7, 2013, Walls wrote in his planner “took an ASP.NET assessment test. Blew it! and real pissed!” (Id. at 2.)

In total, four individuals interviewed for the Systems Analyst C position. (Doc. 26-1, at 4-5.) Patel notes that, while the interview panels may have included different managers, applicants were asked the same questions. (Id.) Patel recorded scores for each applicant in a selection matrix and calculated each applicant’s overall score. (Id. at 5, 29.) Patel’s selection matrix also indicates that each of the four applicants who interviewed met the minimum qualifications required for the position. (Id. at 4, 29.) Ultimately, Matthew Franz, a thirty-two-year-old Programmer Analyst who received the highest overall score, was selected for the position.5 (Doc. 26-1, at 4-5, [682]*68229; Doc. 30-5, at 1-2.) Walls received the lowest overall score. (Doc. 26-1, at 4-5, 29.)

Nonetheless, Walls asserts that he was more qualified for the position than Franz. (Doc. 30-1, at 3-4.) Walls notes that, at the time he interviewed for the position, he had: (1) twenty-eight years of Programmer Analyst and System Analyst experience with TVA; (2) worked at every TVA nuclear plant, most TVA fossil plants, and supported TVA’s Medical and Delivery organizations; and (3) led several major projects for TVA’s Energy Delivery group. (Id.) Conversely, Walls notes that Franz only had two years of work experience with TVA, had never worked on a quality assurance system, and had not designed, built, documented, and installed a major computer application. (Id.) Walls also notes that Franz had seven projects rejected, while he never had a project rejected. (Id.)

On March 6, 2013, Walls met with Patel to discuss why he was not selected for the Systems Analyst C position. (Id. at 5.) According to Walls, Patel stated, “[u]nfor-tunately, at your age, sometimes there is no place to go.” (Id.) Patel, however, denies making this statement. (Doc. 26-1, at 7.)

On July 8, 2013, Walls filed a complaint with TVA’s Equal Opportunity Compliance (“EOC”) office, alleging that he was not selected for the Systems Analyst C position because of age discrimination. (Doc. 26-17, at 2-3.) Senior leadership and managers in TVA’s IT department were aware of Walls’s EOC complaint by January 2014. (Doc. 26-12, at 5; Doc. 30-9; Doc. 30-11, at 2.)

In the fall of 2013, TVA announced an initiative to reduce its operations and maintenance expenses by $500 million by fiscal year 2015. (Doc. 26-5, at 1.) Consistent with this objective, between January and March of 2014, TVA offered voluntary reduction-in-force packages to all TVA employees outside its Nuclear organization who had at least one year of full-time TVA service. (Id. at 2; Doc. 30-1, at 8.) According to Clay DeLoach, Director of Operations Solutions Delivery, the voluntary reduction-in-force offering was designed to “ameliorate the impact of a forced reduction through an involuntary reduction-in-force.” (Doc. 26-5, at 2.) While sixteen Programmer Analysts ultimately separated from TVA pursuant to the voluntary reduction-in-foree, Walls declined the offer. (Doc. 30-1, at 8.)

Beginning in March 2014, after the voluntary reduction-in-force offering closed, TVA released new organizational charts for each non-Nuclear TVA organization. (Doc. 26-3, at 1.) As part of the reorganization process, TVA eliminated the Programmer Analyst and Systems Analyst positions and combined them into one new position—Software Engineer. (Doc. 30-1, at 6.) Walls’s new supervisor, Scott Davi-son, communicated to all Programmer Analysts and System Analysts that they could “bid” on the new Software Engineer positions, meaning that “all TVA employees who had not elected to resign from TVA through the involuntary reduction-in-force offering ... were permitted to apply for one of the vacant positions.”6 (Doc. 26-3, at 4; Doc. 30-1, at 6.) Any employee in an eliminated position who did not apply for, did not receive, or rejected an offer for a [683]*683new position would be terminated as part of an involuntary reduetion-in-force. (See Doc. 26-3, at 2, 7.)

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
229 F. Supp. 3d 678, 2017 U.S. Dist. LEXIS 117588, 2017 WL 511859, Counsel Stack Legal Research, https://law.counselstack.com/opinion/walls-v-johnson-tned-2017.