Brenda Koehler v. Infosys Technologies Limited, Inc.

In the United States Court of Appeals For the Seventh Circuit ____________________ No. 25-2272 BRENDA KOEHLER, et al., Plaintiffs-Appellants, v. INFOSYS TECHNOLOGIES LIMITED, INC. and INFOSYS PUBLIC SERVICES, INC., Defendants-Appellees. ____________________ Appeal from the United States District Court for the Eastern District of Wisconsin. No. 13-cv-00885 — Pamela Pepper, Chief Judge. ____________________ ARGUED MAY 19, 2026 — DECIDED JULY 13, 2026 ____________________ Before BRENNAN, Chief Judge, and ST. EVE and KOLAR, Cir- cuit Judges. ST. EVE, Circuit Judge. Four former employees of or appli- cants to work for Infosys Technologies Limited, Inc. and In- fosys Public Services, Inc. (together, “Infosys”) sued the com- pany, alleging it discriminated against non-South Asians. Plaintiffs relied on an expert report by David Neumark, a la- bor economist who analyzed Infosys’s demographic data and 2 No. 25-2272 concluded that chance alone could not explain the de- mographics of Infosys’ employee population, as the founda- tion of their case. To Plaintiffs, Neumark’s analysis helped prove that Infosys engaged in discrimination. But the district court excluded Neumark’s expert opinions under Federal Rule of Evidence 702. The district court then denied Plaintiffs’ motion for class certification because it relied heavily on Neu- mark’s analysis. It later denied Plaintiffs’ request to supple- ment their summary judgment briefing with different data. Finally, the district court granted Infosys’s motion for sum- mary judgment. We affirm. I. Background A. Factual History Infosys is an India-based consulting and technology ser- vices company, with offices in the United States and around the world. Globally, it employs over 190,000 people, and in the United States it has over 20,000 employees. The four plain- tiffs—Gregory Handloser, Brenda Koehler, Kelly Parker, and Layla Bolten—either worked for or applied to work for In- fosys, and all four are of non-South Asian background. Handloser worked as a sales manager at Infosys. The com- pany evaluates the performance of sales managers and other employees every six months. At the start of a review cycle, In- fosys informs the sales managers of their target metrics for that cycle. At the end of the cycle, the sales manager provides a numerical evaluation of his performance, as does his super- visor. Infosys uses those entries to calculate the manager’s in- dividual “Performance Index.” It then weights each man- ager’s Performance Index against every other sales manager’s score; the output is the “Consolidated Relative Rating” score. No. 25-2272 3 The best such score is a “one plus” and the poorest is a “four.” During the April–September 2012 review cycle, Handloser gave himself a poor evaluation score, as did his supervisor. As a result, his Consolidated Relative Rating was a “four,” and Infosys terminated Handloser as part of a company-wide reduction in force that targeted employees who had received a “four.” Koehler applied to work for Infosys as a “Lead VMware/Windows Administrator”—a Milwaukee-based po- sition working on an Infosys project with Harley-Davidson. Koehler had many of the qualifications necessary for the role, but, after interviewing her, Infosys determined that she lacked the necessary “Microsoft Active Directory” skills and decided not to hire her. Parker worked for Infosys between 2010 and 2012 after the company took over the Harley-Davidson project, where Par- ker previously worked. Infosys informed Parker her position would conclude by the end of 2012. But Parker’s role contin- ued into 2013, and, in June 2013, she began working for SoftHQ—an IT staffing company that helps Infosys fill its temporary staffing needs. Through this, Parker stayed in her prior role at Infosys, though Infosys informed Parker her new role would end once the staffing need concluded. For her part, Parker claims she believed this was a permanent position. In September 2013, Infosys ended Parker’s position and, thus, terminated Parker. Bolten began working for Infosys as a “Test Analyst” in the company’s Washington, D.C. office in 2013. In this role, Bolten worked under Geeta Kulkarni. Bolten claims Kulkarni, who is Indian, harassed her on account of her non-Indian sta- tus. Specifically, after Bolten took a sick day Kulkarni com- 4 No. 25-2272 mented that “stupid Americans” are “lucky” they can take sick days, and at a group meeting, Kulkarni did not let Bolten talk about her background, calling them “American experi- ences,” while allowing other test analysts to share stories about their background. Bolten also raises other instances of harassment, for example when, following the Boston Mara- thon bombing, a coworker noted that the attacker was Rus- sian and that Bolten was Russian as well, while pointing a fin- ger at Bolten, and that her coworkers, including Kulkarni, of- ten did not speak English at work when around her, including when discussing work-related matters. Bolten eventually reported these concerns, and her super- visors claimed they would address them. Bolten also shifted teams at Infosys several times. After one of these reassign- ments, Bolten moved her belongings to a new desk, but a new team member told Bolten someone else on the team already occupied the desk and directed Bolten to a different desk. Bolten responded, “you know what? I’m not moving any- where, I’m not doing anything,” and resigned. B. Procedural History In 2013, Koehler sued Infosys, alleging the company dis- criminated against individuals who were not of South Asian background through its hiring and employment practices. Af- ter adding Handloser, Parker, and Bolten in an amended com- plaint, Plaintiffs sought to represent a class of “[a]ll individu- als who are not of South Asian race or Indian, Bangladeshi, or Nepalese national origin who applied for a position with, or were employed by Defendants, and were discriminated against on the basis of their national origin or race in the last No. 25-2272 5 four years through the date of final judgment in this action.” 1 The complaint brought disparate treatment and disparate im- pact claims under Title VII and disparate treatment claims un- der 42 U.S.C. § 1981. 1. Motion to Exclude Expert During discovery, Plaintiffs sought to introduce the expert opinions of Professor David Neumark. Neumark is a labor economist whom Plaintiffs hired to analyze Infosys’s employ- ment data. After reviewing Infosys’s demographic data, Neu- mark concluded, for example, that “89.39% of Infosys’ United States workforce was South Asian,” whereas only 11.45% of the workforce in the relevant domestic industry was South Asian. According to Neumark, chance could not explain this disparity, along with similar disparities he found in other analyses. But Neumark’s analysis had a challenge. Infosys does not maintain demographic data on its employees and applicants at the level of granularity Neumark needed, so Neumark did not have a complete list of who among Infosys’s employees and applicants was of South Asian background. He did, how- ever, have access to national origin information for Infosys employees. So, Neumark employed his five-step “name- matching” methodology. First, Neumark created a list of the last name of every Infosys employee whose national origin was a South Asian country. Second, Neumark consolidated that list to last names associated with two or more employees. Third, Neumark reviewed the consolidated list and removed 1 For simplicity, we refer to Plaintiffs’ theory as discrimination against people who are not South Asian, encompassing both race and national origin from the countries within South Asia that Plaintiffs identify. 6 No. 25-2272 sixty-three last names that, to Neumark, sounded “clearly … to be non-South Asian/non-Indian.” Fourth, with his twice- consolidated list, Neumark compared the names to the last names of Infosys employees not from a South Asian country and to the last names of Infosys applicants (Infosys did not collect national origin data on applicants). Fifth, if a name matched a last name on his list, Neumark categorized the in- dividual as “South Asian”; if the name did not match, he cat- egorized the individual as “non-South Asian.” In December 2016, following Plaintiffs’ motions for partial summary judgment and class certification, Infosys moved to exclude Neumark’s expert opinions. Approximately three and one-half years later, in June 2020, the district court held a hearing on the motion to exclude Neumark’s testimony. Then, in September 2022, nearly six years after Infosys had moved, the district court finally granted the motion to exclude. Ap- plying Federal Rule of Evidence 702, the district court found that Neumark lacked the qualifications needed to conduct the name-matching methodology, that his methodology was un- reliable, and that, as a result, his opinions were irrelevant. It found him unqualified because he admitted he had no expe- rience or training in identifying whether a name is “South Asian” or not. And it found his methodology unreliable be- cause Plaintiffs offered no evidence demonstrating the meth- odology’s reliability, testing, error rate, peer review, or scien- tific foundation. The court excluded Neumark’s opinions as to both Infosys employees and applicants. 2. Class Certification In the same decision, the district court also denied Plain- tiffs’ motion for class certification. To meet Federal Rule of Civil Procedure 23’s requirements, Plaintiffs had repeatedly No. 25-2272 7 relied on Neumark’s analysis in their motion. So, having ex- cluded Neumark’s opinions, the district court found that Plaintiffs lacked the evidence necessary to satisfy Rule 23 and denied class certification. For the same reasons, the district court also denied Plaintiffs’ motion for partial summary judg- ment. 3. Supplementing Summary Judgment Briefing Stepping back, during discovery Plaintiffs requested “[d]ocuments and ESI relating to the demographics or statis- tics of Infosys’ United States work force, including, but not limited to, EEO reports, studies, or other documents reflecting the statistics of the workforce.” Infosys complied with this re- quest to some extent, but it failed to turn over its “PeopleFlu- ent data.” This is demographic data Infosys contracts with PeopleFluent to collect and analyze as part of Infosys’s obli- gations as a federal contractor to conduct “affirmative action” analyses. 41 C.F.R. § 60-2.1 (2020). Plaintiffs learned in June 2016 that the PeopleFluent data existed and eventually re- ceived the data directly from PeopleFluent in December 2016 and January 2017 (after discovery had closed and after Infosys had moved for summary judgment). Because Infosys had failed to produce this data and Plain- tiffs received it late, the parties met before former Magistrate Judge David Jones several times in early 2017. Judge Jones asked Plaintiffs if they wanted to supplement their prior fil- ings with the PeopleFluent data, but Plaintiffs never indicated such an intent. Returning to 2022, after the district court excluded Neu- mark’s expert opinions, in November, Plaintiffs moved under Federal Rule of Civil Procedure 16(b) to retain a new expert 8 No. 25-2272 and conduct new discovery. They also indicated they might seek to supplement their summary judgment briefing with the PeopleFluent data if the district court denied their motion. In December 2022, the district court denied Plaintiffs’ motion and denied leave to supplement the summary judgment brief- ing with the PeopleFluent data. The court found that Judge Jones several times asked the plaintiffs whether or not they wanted to have to go back and to supple- ment their filings with regard to the summary judg- ment.… And the plaintiffs rejected all of those [offers]. They went ahead.… [T]he plaintiffs were given the very opportunity that I thought they might ask me for after my ruling. Judge Jones gave them that oppor- tunity and gave them an opportunity more than once and told them to propose a plan, and the plaintiffs didn’t. So I … don’t think it is appropriate at this point for the plaintiffs to go back now and somehow modify their response to the defendants’ Motions for Sum- mary Judgment as to the individual plaintiff[s].… Koehler v. Infosys Techs. Ltd., No. 13-cv-00885 (E.D. Wisc. Mar. 15, 2023), Dkt. No. 214 at 32:2–33:6. 4. Summary Judgment Finally, in June 2025—nearly nine years after Infosys moved—the district court granted summary judgment to In- fosys on all claims. 2 First, it denied the pattern and practice 2 As discussed, Plaintiffs first filed this case in 2013. The district court took nearly five years to rule on the motion to exclude and nearly nine years to rule on summary judgment. This is an exceptionally long time. No. 25-2272 9 claims Plaintiffs brought under International Brotherhood of Teamsters v. United States, 431 U.S. 324 (1977), because it found a Teamsters claim requires class certification and it had previ- ously denied Plaintiffs’ motion for class certification. It next turned to the four Plaintiffs’ individual disparate treatment claims, to which it applied the burden-shifting framework of McDonnell Douglas Corp. v. Green, 411 U.S. 792 (1973). In relevant part, it found Handloser’s, Koehler’s, and Parker’s claims all failed at the pretext step, as none could re- but the nondiscriminatory reasons Infosys offered for the em- ployment actions it took. And it found Bolten’s claim— brought as a constructive discharge claim—failed because Bolten could not demonstrate a level of harassment sufficient to meet the constructive discharge’s high bar. Finally, it denied Koehler’s and Parker’s individual dis- parate impact claims, finding that those claims relied on Neu- mark’s statistical analysis and, absent that analysis, Koehler and Parker did not have evidence sufficient to demonstrate a disparate impact. * * * We acknowledge that the parties’ voluminous filings contributed to the delay. But we also underscore that it is a district court’s obligation to ensure the timely resolution of the cases before it. See Fed. R. Civ. P. 1 (“[The Federal Rules of Civil Procedure] should be construed, adminis- tered, and employed by the court and the parties to secure the just, speedy, and inexpensive determination of every action and proceeding.”); Simstad v. Scheub, 816 F.3d 893, 902 (7th Cir. 2016) (“We are distressed that it took this case so long to be resolved. Some of the problems might have been avoided with better control over the schedule ….”). 10 No. 25-2272 Plaintiffs appeal the decisions of the district court (1) ex- cluding Neumark’s opinions, (2) denying class certification, (3) denying leave to supplement their summary judgment briefing with the PeopleFluent data, and (4) granting sum- mary judgment to Infosys on all claims. II. Discussion A. Federal Rule of Evidence 702 The district court applied the proper legal framework when ruling on Infosys’s motion to exclude Neumark’s testi- mony, so we review its decision for abuse of discretion. Artis v. Santos, 95 F.4th 518, 525 (7th Cir. 2024). Federal Rule of Evidence 702 provides: A witness who is qualified as an expert by knowledge, skill, experience, training, or education may testify in the form of an opinion or otherwise if the proponent demonstrates to the court that it is more likely than not that: (a) the expert’s scientific, technical, or other spe- cialized knowledge will help the trier of fact to under- stand the evidence or to determine a fact in issue; (b) the testimony is based on sufficient facts or data; (c) the testimony is the product of reliable principles and methods; and (d) the expert’s opinion reflects a re- liable application of the principles and methods to the facts of the case. In Daubert v. Merrell Dow Pharmaceuticals, Inc. the Supreme Court set out a district court’s “gatekeeping” obligations, 509 U.S. 579, 597 (1993), to ensure “the reliability and relevancy of expert testimony,” Kumho Tire Co. v. Carmichael, 526 U.S. 137, 152 (1999). See also Artis, 95 F.4th at 525. To satisfy its obliga- tion, a district court evaluates: “(1) the proffered expert’s qual- No. 25-2272 11 ifications; (2) the reliability of the expert’s methodology; and (3) the relevance of the expert’s testimony.” Gopalratnam v. Hewlett-Packard Co., 877 F.3d 771, 779 (7th Cir. 2017). “Because ‘much depends upon the particular circumstances of the par- ticular case at issue,’ the Rule 702 analysis is case-specific.” Anderson v. Raymond Corp., 61 F.4th 505, 508 (7th Cir. 2023) (quoting Kumho Tire Co., 526 U.S. at 150). Before engaging with Rule 702 and Daubert, Plaintiffs ar- gue the district court erred by “sua sponte” excluding Neu- mark’s analysis as to Infosys employees when Infosys only moved to exclude his analysis as to applicants. It is clear, how- ever, that “[a] district court is entitled to rule on expert admis- sibility sua sponte. As long as the district court has given the parties an opportunity to be heard and applies the correct le- gal framework under Rule 702, we are satisfied.” Perez v. K & B Transp., Inc., 967 F.3d 651, 656 (7th Cir. 2020). We ground this rule in the general, broad discretion a district court enjoys in how it conducts a Daubert analysis: “We have not required that the Daubert inquiry take any specific form and have, in fact, upheld a judge’s sua sponte consideration of the admissi- bility of expert testimony.” Kirstein v. Parks Corp., 159 F.3d 1065, 1067 (7th Cir. 1998); see also Lewis v. CITGO Petroleum Corp., 561 F.3d 698, 704 (7th Cir. 2009). Here, Infosys put Plaintiffs on notice that it was challeng- ing Neumark’s qualifications and his name-matching meth- odology when it moved to exclude, and Plaintiffs had every opportunity to advance the evidence they now claim—nine years later—they would have advanced before the district court. True, Infosys’s motion to exclude focused on Neu- mark’s name-matching methodology as applied to Infosys applicants, but the motion addressed the extensive issues 12 No. 25-2272 with the methodology generally and Plaintiffs had an oppor- tunity to fully litigate these issues. And, when the court granted Infosys’s motion, it found the flaws on which it based its ruling—flaws Infosys expressly had raised—applied to both applicants and employees, explaining “[i]t is not clear why Neumark’s methodology would be flawed only with re- gard to the applicant studies.” Plaintiffs insisted in their briefs, and particularly at oral argument, that had they known the district court would ex- clude Neumark’s analysis as to employees, they would have pointed to Neumark’s minimal use of the name-matching methodology as a part of his employee analysis. But Plaintiffs could have advanced that argument in opposing Infosys’s motion. They knew Infosys challenged Neumark’s use of the methodology, and one argument in response could have been its minimal impact on his overall analysis. Moreover, even if Plaintiffs had made this argument, the district court still would have been well within its discretion to reject it and ex- clude Neumark’s analysis as to Infosys employees. Implicit in their argument is that even as to Infosys employees the flaws the district court identified with Neumark’s analysis had some impact on his findings. Maybe that impact was lessened but we would still defer to the district court’s exercise of its discretion—after receiving the parties’ briefing and holding a hearing—in determining that Neumark’s analysis as to In- fosys employees did not satisfy the requirements of Rule 702. Turning to Neumark’s qualifications, “[w]hether a witness is qualified as an expert can only be determined by comparing the area in which the witness has superior knowledge, skill, experience, or education with the subject matter of the wit- ness’s testimony.” Gayton v. McCoy, 593 F.3d 610, 616 (7th Cir. No. 25-2272 13 2010) (quoting Carroll v. Otis Elevator Co., 896 F.2d 210, 212 (7th Cir. 1990)). “[W]e ask not whether an expert ‘is qualified in general’ but whether he is qualified ‘to answer a specific ques- tion ….’” United States v. Truitt, 938 F.3d 885, 889 (7th Cir. 2019) (quoting Gayton, 593 F.3d at 617); see also Ollison v. Gossett, 136 F.4th 729, 742 n.41 (7th Cir. 2025). There is “no re- quirement that an expert be a specialist in a given field.” Hall v. Flannery, 840 F.3d 922, 929 (7th Cir. 2016) (quoting Gayton, 593 F.3d at 618). But an expert must “possess[] … specialized education, knowledge, experience, or skill” in the area for which he is proffered. Id. at 929–30. Neumark admitted at his deposition that he had no expe- rience in name matching and no expertise in identifying South Asian names. This alone is fatal to Neumark’s qualifi- cations. Plaintiffs claim we can overlook this because Neu- mark only searched for “western” names, in which, they con- tend, he does have experience identifying (seemingly simply due to his upbringing in a western country). But, setting aside whether his upbringing alone qualifies him as an expert in identifying “western” names, Plaintiffs ig- nore that the two categories are not mutually exclusive. That is, even if Neumark was qualified to identify “western” names, he remained unqualified to determine whether a “western” name was or was not also a “South Asian” name. 3 3 Some examples from Neumark’s list of “western” sounding last names that can also be South Asian last names include: (1) “D’Souza,” which is a common last name for Indians who live in areas of the country that are former Portuguese colonies, see, e.g., De Souza v. I.N.S., 999 F.2d 1156, 1157 (7th Cir. 1993) (plaintiff “De Souza’s parents were born in Goa, a former Portuguese colony which India invaded and conquered shortly 14 No. 25-2272 This is ultimately the issue with the analysis Neumark pur- ported to use: He claimed he could identify who among In- fosys’s employee and applicant population was South Asian based on last name, yet he admitted he lacked the experience or expertise necessary to identify if a last name was South Asian. Given Neumark’s deposition testimony, there was no error, and certainly no abuse of discretion, in the district court’s conclusion that Neumark lacked the qualifications necessary to provide his expert opinions. Rule 702 also requires a court to evaluate “the reliability of the expert’s methodology.” Gopalratnam, 877 F.3d at 779. We have set out “non-exhaustive” factors a court may consider in reviewing reliability, including “(1) whether the particular after De Souza’s birth,” and noting plaintiff is “Kenya[n] … of Indian de- scent”); D’Souza v. Holder, 487 F. App’x 347, 348 (9th Cir. 2012) (“Alldrin Lino D’Souza, a native and citizen of India, petitions for review of the Board of Immigration Appeals’ denial of his application for asylum ….”); D’Souza v. U.S. Att’y Gen., No. 23-10023, 2024 WL 3466573, at *1 (11th Cir. July 19, 2024) (“D’Souza is a citizen and national of India who arrived in the United States through a port of entry on a B2 visa in November 2007.”); (2) “Dave,” see, e.g., United States v. Dave, 652 F. App’x 468, 469 (7th Cir. 2016) (“This is a straightforward immigration appeal brought by Anish Dave, who was born in India and later naturalized as a United States citi- zen in 2005.”); Dave v. Ashcroft, 363 F.3d 649, 650 (7th Cir. 2004); and (3) “Jo- seph,” see, e.g., Kondamudi v. Garland, No. 20-61085, 2022 WL 2187862, at *1 (5th Cir. June 17, 2022) (“Sreekumari Kondamudi and Sajeev Joseph, who are natives and citizens of India, petition for review of an order of the Board of Immigration Appeals ….”); Joseph v. Gonzales, 240 F. App’x 726, 726 (7th Cir. 2007) (“Roome Joseph, a Pakistani citizen[,] … challenges the BIA’s denial of her motion to reopen removal proceedings.”); Joseph v. McDonough, No. 21-1736, 2022 WL 19837507, at *1 (6th Cir. Dec. 27, 2022) (“[Angela] Joseph, a physician born in India, filed a complaint against the Secretary for monetary and injunctive relief ….”). No. 25-2272 15 scientific theory can be (and has been) tested; (2) whether the theory has been subjected to peer review and publication; (3) the known or potential rate of error; (4) the existence and maintenance of standards controlling the technique’s opera- tion; and (5) whether the technique has achieved general ac- ceptance in the relevant scientific or expert community.” Kirk v. Clark Equip. Co., 991 F.3d 865, 873 (7th Cir. 2021) (quoting Deputy v. Lehman Bros., Inc., 345 F.3d 494, 505 (7th Cir. 2003) (citation modified)); see also Gopalratnam, 877 F.3d at 779 (list- ing similar factors). No factor is dispositive and Rule 702’s test is “flexible.” Smith v. Ford Motor Co., 215 F.3d 713, 719 (7th Cir. 2020)). We care not about the “ultimate correctness” of the ex- pert’s opinions; rather, reliability focuses on “the soundness and care with which the expert arrived at h[is] opinion.” Schultz v. Akzo Nobel Paints, LLC, 721 F.3d 426, 431 (7th Cir. 2013). On appeal, Plaintiffs offer evidence that, in their view, bol- sters name-matching’s reliability. Maybe so. But the problem for Plaintiffs is more fundamental: They presented none of this evidence to the district court. Plaintiffs provided no evi- dence of the name-matching methodology’s testing, error rate, peer review, or general acceptance in the scientific com- munity. And Neumark admitted he had no experience with the technique either. Our review is for abuse of discretion, and the district court did not abuse its discretion in concluding Neumark’s methodology was unreliable when Plaintiffs did not offer evidence supporting reliability. Gopalratnam, 877 F.3d at 782 (“A decision is an abuse of discretion only if no reasonable person would agree with the decision made by the trial court.” (quoting Smith v. Hunt, 707 F.3d 803, 807–08 (7th Cir. 2013))). Plaintiffs may regret the choices they made before the district court, but we hold them to those choices. 16 No. 25-2272 B. Class Certification There is little to say about the district court’s denial of Plaintiffs’ motion for class certification. Because we affirm the district court’s decision to exclude Neumark’s expert opin- ions, we affirm the denial of class certification. At oral argu- ment Plaintiffs conceded that absent Neumark’s analysis they cannot meet Federal Rule of Civil Procedure 23’s require- ments. We agree. C. Supplementing Summary Judgment Briefing After the district court excluded Neumark’s expert opin- ions, Plaintiffs sought leave to supplement their summary judgment briefing with the PeopleFluent data. But the court denied leave, a decision we review for abuse of discretion. See Christensen v. Weiss, 145 F.4th 743, 755 (7th Cir. 2025); Frazier v. Dovenmuehle Mortg., Inc., 72 F.4th 769, 778 (7th Cir. 2023). The district court enjoys inherent discretion to manage the case before it and to keep the case moving. Ewing v. 1645 W. Farragut LLC, 90 F.4th 876, 889 (7th Cir. 2024) (“District judges have wide discretion to manage their proceedings ....” (quot- ing Rainey v. Taylor, 941 F.3d 243, 247 (7th Cir. 2019))). For that reason, a district court may properly deny “an effort to sup- plement the record after summary judgment … where the in- formation was available at the time the motion was heard and no reasonable explanation is offered for why it was not sub- mitted.” Perez v. Staples Cont. & Com. LLC, 31 F.4th 560, 569 (7th Cir. 2022) (citing Moro v. Shell Oil Co., 91 F.3d 872, 876 (7th Cir. 1996)). The district court here did not abuse its discretion. Plain- tiffs knew of the PeopleFluent data as of mid-2016 yet only made the request to supplement their briefing in late 2022, af- No. 25-2272 17 ter the district court granted Infosys’s motion to exclude Neu- mark’s expert opinions. Moreover, at the time the parties dis- cussed the PeopleFluent data in early 2017, Judge Jones re- peatedly asked Plaintiffs what recourse they might want given Infosys’s failure to timely produce the data and offered Plaintiffs potential avenues to remedy the impact of Infosys’s shortcomings (including supplementing their summary judg- ment briefing). This occurred five years before Plaintiffs even- tually sought to supplement their briefing. Plaintiffs rejected or ignored those opportunities and proceeded anyway. They are, again, not entitled to a do-over. Plaintiffs do not dispute this but instead contend the dis- trict court’s error was legal: It decided their request to supple- ment without applying the correct legal standard—namely, Federal Rule of Civil Procedure 6(b) and the Supreme Court’s “excusable neglect” test from Pioneer Investment Services v. Brunswick Associates Ltd., 507 U.S. 380, 395 (1993). Rule 6(b) provides that “[w]hen an act may or must be done within a specified time, the court may, for good cause, extend the time … on [a] motion made after the time has expired if the party failed to act because of excusable neglect.” But it is unclear why Plaintiffs contend we (and the district court) should look to Rule 6(b). Setting aside the question of whether a request to supplement summary judgment briefing is a request made under Rule 6(b), Plaintiffs never moved un- der Rule 6(b) or otherwise put the district court on notice that they believed Rule 6(b) and Pioneer’s “excusable neglect” test applied. Instead, they moved under Rule 16 to modify the dis- trict court’s scheduling order so they could submit a new ex- pert and reopen discovery. In the alternative, the district court asked if Plaintiffs might want to supplement their summary 18 No. 25-2272 judgment briefing with the PeopleFluent data, to which Plain- tiffs responded they would. Neither Plaintiffs nor the district court ever raised or addressed Rule 6(b). So, Plaintiffs have waived their Rule 6(b) argument. Seeing no error and certainly no abuse of discretion in the district court’s exercise of its inherent discretion, we affirm its decision to deny Plaintiffs leave to supplement their summary judgment briefing. D. Plaintiffs’ Discrimination Claims Finally, we turn to the district court’s decision granting summary judgment to Infosys on three sets of claims brought by Plaintiffs: (1) the Teamsters pattern and practice claims; (2) the individual disparate treatment claims; and (3) the dis- parate impact claims brought by Koehler and Parker. We re- view de novo the district court’s decision granting Infosys’s motion for summary judgment. Vassileva v. City of Chicago, 118 F.4th 869, 873 (7th Cir. 2024). We “constru[e] all facts and draw[] all reasonable inferences in the light most favorable to [Plaintiffs],” as the non-moving party. Johnson v. Dominguez, 5 F.4th 818, 824 (7th Cir. 2021). “Summary judgment is appro- priate if ‘the movant shows that there is no genuine dispute as to any material fact and the movant is entitled to judgment as a matter of law.’” Id. (quoting Fed. R. Civ. P. 56(a)). 1. Pattern and Practice Claims The primary theory of discrimination Plaintiffs pursue is that Infosys “engaged in a pattern and practice of discriminat- ing against” non-South Asian employees and applicants. That is, such discrimination is Infosys’s “standard operating pro- cedure.” Matthews v. Waukesha County, 759 F.3d 821, 829–30 (7th Cir. 2014). Plaintiffs invoke the Supreme Court’s decision No. 25-2272 19 in International Brotherhood of Teamsters, which explained that the burden of proof for a “pattern-or-practice” claim brought as a class action requires showing “that unlawful discrimina- tion has been a regular procedure or policy followed by an employer or group of employers.” 431 U.S. at 360. The district court correctly recognized that once it had de- nied Plaintiffs’ motion for class certification, Plaintiffs could no longer maintain their Teamsters claims. Teamsters makes clear that a pattern and practice claim is conventionally brought as a class action. See id. at 359–60; see also Franks v. Bowman Transp. Co., 424 U.S. 747, 751 (1976). Since Teamsters, both the Supreme Court and our court have confirmed this view. See Cooper v. Fed. Rsrv. Bank of Richmond, 467 U.S. 867, 876 (1984); Gilty v. Vill. of Oak Park, 919 F.2d 1247, 1252 (7th Cir. 1990) (noting plaintiff “filed an individual claim[,] … not a class action. Consequently, … evidence of a pattern and practice ‘can only be collateral to evidence of specific discrim- ination against the actual plaintiff’” (quoting Williams v. Boorstin, 663 F.2d 109, 115 n.38 (D.C. Cir. 1980)); see also id. (cit- ing approvingly position that “[p]attern-and-practice suits, by their very nature, involve claims of classwide discrimination” (quoting B. Schlei & P. Grossman, Employment Discrimina- tion Law 1322 & n. 95 (2d ed. 1983))); Matthews 759 F.3d at 829. Because we affirm the district court’s exclusion of Neu- mark’s report and denial of class certification, Plaintiffs can- not maintain their pattern and practice claims brought under Teamsters. 2. Individual Disparate Treatment Claims In addition to the Teamsters claims, each plaintiff also brought individual disparate treatment claims under Title VII 20 No. 25-2272 or 42 U.S.C § 1981. Because “[t]he legal analysis for discrimi- nation claims under Title VII and § 1981 is largely identical,” Lewis v. Ind. Wesleyan Univ., 36 F.4th 755, 759 (7th Cir. 2022), we analyze Plaintiffs’ claims together. Plaintiffs must show (1) membership in a protected class, (2) an adverse employ- ment action, and (3) causation. Id. As is often the case, only causation is in dispute, which “require[s] that [race or na- tional origin] be a ‘motivating factor in the defendant’s chal- lenged employment decision.’” Id. (quoting Comcast Corp. v. Nat’l Ass’n of Af. Am.-Owned Media, 589 U.S. 327, 332 (2020)). The fundamental question “is simply whether the evidence would permit a reasonable factfinder to conclude that the plaintiff’s race, ethnicity, sex, religion, or other proscribed fac- tor caused the discharge or other adverse employment action. Evidence must be considered as a whole, rather than asking whether any particular piece of evidence proves the case by itself ….” Ortiz v. Werner Enters., Inc., 834 F.3d 760, 765 (7th Cir. 2016). One method of satisfying this standard is the familiar bur- den-shifting framework of McDonnell Douglas Corp., 411 U.S. 792. “To establish a prima facie case of employment discrimi- nation, the employee must show that ‘(1) she is a member of a protected class, (2) she was meeting the defendant’s legiti- mate expectations, (3) she suffered an adverse employment action, and (4) similarly situated employees who were not members of her protected class were treated more favora- bly.’” Lewis, 36 F.4th at 759 (quoting Tyburski v. City of Chicago, 964 F.3d 590, 598 (7th Cir. 2020)). If a plaintiff does so, the bur- den shifts to the defendant to “to articulate a legitimate, non- discriminatory reason for the adverse employment action.” Id. at 760. Finally, the burden again shifts to the plaintiff to “show why the employer’s explanation is pretextual.” Id. We No. 25-2272 21 have often explained that “[b]ecause the prima facie and pre- text inquiry … overlap, if a defendant offers a nondiscrimina- tory reason for its actions, we can proceed directly to the pre- text inquiry.” Barnes v. Bd. of Trs. of Univ. of Ill., 946 F.3d 384, 389 (7th Cir. 2020). We take the Barnes approach here. “[P]retext … is not ‘just faulty reasoning or mistaken judg- ment on the part of the employer; it is [a] lie, specifically a phony reason for some action.’” Id. at 389–90 (quoting Argy- ropoulos v. City of Alton, 539 F.3d 724, 736 (7th Cir. 2008) (cita- tion modified)). Plaintiffs ultimately must show, by a prepon- derance of the evidence, that Infosys’s stated reasons for the employment actions it took “were false, not that they were un- fair or baseless.” Anderson v. Mott St., 104 F.4th 646, 653 (7th Cir. 2024). Our focus is on whether Infosys “honestly believed the stated reason” for the employment action. Id. at 654. With these principles in mind, Handloser, Parker, and Koehler all fail to raise an issue of fact as to whether Infosys’s reasons for the employment actions it took against each of them were pretext for discriminatory animus. Infosys fired Handloser because he received the poorest possible score during the September 2012 review cycle and the company-wide reduction in force targeted all employees who had received that score. He points to his prior, strong performance—but Infosys does not dispute that he was pre- viously performing well. Rather, it explains that the reduction in force focused only on the one review cycle at issue and that Handloser performed poorly during that cycle. Handloser also points to an email from a supervisor, in which the supervisor, according to Handloser, admitted Handloser would have a strong case against Infosys should it 22 No. 25-2272 terminate him. But his reading of the email is selective. In- deed, it confirms that Handloser evaluated himself as under- performing. Though the email speculates that Handloser might sue Infosys should it terminate him, it does not suggest his lawsuit would have any merit or otherwise suggest In- fosys’s reason for terminating him was pretext for racial dis- crimination. In sum, Handloser has not demonstrated a gen- uine dispute of fact as to whether Infosys’s stated reason for his termination was pretext for discrimination against him on account of his non-South Asian status. Parker contends Infosys discriminated against her twice: (1) in failing to hire her when she applied for a full-time posi- tion and (2) in discharging her when Infosys ended her posi- tion through SoftHQ. But, starting with the first, Infosys pre- sented evidence that when Parker applied for the full-time role, it interviewed her and determined she lacked the quali- fications necessary for the role. Parker does not advance evi- dence which demonstrates this was pretext. She contends she was already performing the same role before Infosys inter- viewed her, so she could not have lacked the necessary quali- fications. But Infosys points to interview logs where Parker’s interviewers concluded she did not possess the skills neces- sary for the role. All Infosys must show is an honestly held belief, Cunn