The Analytics Backlash: Are Teams Overcorrecting?

Six Teams Said They Were Done With Data

Between 2021 and 2024, six MLB front offices made public statements about reducing their reliance on analytics. The Twins restructured their analytics department in 2023, cutting 4 positions. The Mariners moved their lead analyst out of the baseball operations hierarchy. The Angels, Phillies, Pirates, and Mets all made varying degrees of public statements about returning to traditional scouting and trusting their eyes over their spreadsheets.

The media framed this as a correction. After two decades of Moneyball-era quantification, the pendulum was swinging back. Scouts were relevant again. The human element was returning to front offices that had become too reliant on algorithms. It was a clean story. It was also mostly wrong.

The gap between rhetoric and behavior is the real story. Teams that publicly said they were de-emphasizing analytics continued to invest in data infrastructure, hire quantitative staff under different titles, and use model-driven processes for player evaluation. The backlash was a branding exercise.

Follow the Money, Not the Press Conference

Every MLB team pays for Statcast data access, Trackman or Hawk-Eye installations, and proprietary player tracking systems. These contracts cost $1-3 million per year depending on the scope. None of the 6 "backlash" teams cancelled or reduced their data contracts. Every one renewed or expanded them during the same period they were publicly distancing from analytics.

The hiring data confirms the pattern. Teams that cut analytics department headcount simultaneously hired data scientists, quantitative analysts, and "player development strategists" in other departments. The Twins cut 4 analytics positions in 2023 and posted 3 new roles with different titles in their player development and scouting departments. The job descriptions listed the same technical requirements: SQL, Python, Bayesian modeling, and Statcast fluency.

Five of the 6 teams have more analytics-adjacent staff now than they did before their public statements about pulling back. The Twins are the only team with a net decrease, and their reduction was 1 position. The retitled roles column tells the real story: across all 6 teams, 22 positions were moved out of "analytics" departments and into scouting, player development, or front office operations with new titles but the same function.

The Audience Was Internal

The analytics backlash was a management strategy, not a philosophical shift. Front offices had a specific problem: players, coaches, and scouts felt alienated by analytics departments that operated as parallel authority structures. Coaches who had managed for decades were told their bullpen decisions should be overridden by a 26-year-old with a laptop. Scouts who had spent careers evaluating talent were told their reports were less reliable than a model. The friction was real and it was harming clubhouse culture.

The solution was to change the language, not the math. Instead of an analytics department issuing directives, the same analysis was repackaged as "information support" or "decision tools." The output stayed identical. The framing shifted from prescription to suggestion. Coaches received the same data but felt more ownership over the decision. Scouts contributed to models instead of competing with them.

The Phillies are the clearest example. Their public de-emphasis of analytics coincided with their 2022 World Series run and 2023 NLCS appearance. During that stretch, they used defensive positioning models, platoon matchup data, and bullpen leverage indices at rates equal to or above league average. They called it "feel-based decision-making" in press conferences. It was model-based decision-making with better PR.

The Backlash Teams Won More

If the analytics pullback were real, you'd expect the backlash teams to underperform analytically-driven organizations. The opposite happened. The 6 backlash teams averaged 84.3 wins per season from 2022 through 2024, compared to a league average of 81.0. Three of the 6 made the playoffs in that span. The Phillies reached the World Series. The Twins won a playoff series for the first time in 18 years.

The results don't support the narrative that pulling back from analytics hurt these teams. They support the thesis that the pullback was cosmetic. The teams that "went back to basics" still used the analytics. They got better at packaging the information so coaches and players trusted it. The cultural integration improved. The numbers stayed the same.

Analytics Failed at Communication

The backlash wasn't a rejection of data. It was a rejection of how data was communicated. Analytics departments in the 2015-2020 era operated like consulting firms dropped into organizations with no change management plan. They produced excellent analysis, presented it to decision-makers who lacked the statistical literacy to evaluate it, and expected compliance based on the math alone.

The teams that struggled with analytics integration shared a common pattern: the analytics staff had no relationship with the coaching staff. Reports landed on desks with no context. Recommendations arrived without the reasoning behind them. When a coach asked why a reliever should face a certain batter, the analyst cited a Bayesian model. The coach wanted to know what the pitcher's slider looked like against left-handed hitters that week. Both were answering the same question from different angles, and neither was translating for the other.

The correction was managerial, not analytical. Teams didn't need less data. They needed better translators between the data and the people making in-game decisions. The "backlash" rebranding gave organizations cover to restructure their communication without admitting the original implementation had failed.

The Debate Is Already Over

Every MLB team now employs at least 8 full-time analytics staff. The smallest departments (the Rockies, Royals) are larger than the Astros' analytics team was in 2014 when they began their rebuild. The infrastructure is permanent. No team will uninstall Statcast. No team will stop building models. The question of whether to use analytics was settled 10 years ago.

The question that replaced it is how to use analytics within a human organization. That's a management problem, not a math problem. Teams that solve it win. Teams that pretend they've moved past analytics by changing department names and issuing press releases are solving the same problem with a different label.

The backlash will be remembered as the moment baseball figured out that data science needed a communications department. The math was always right. The delivery was the variable. Every front office now understands this. The organizations still hiring for it are the ones that learned last.

Sources & Data

Jesse Walker

Jesse Walker writes about baseball through data. He played outfield in high school, found his real position behind a spreadsheet, and hasn't stopped building models since.