The Tampa Bay Rays’ most useful lesson may be that baseball strategy works best when it serves the players on the field. Modern analysis has sharpened the case for pulled fly balls and strikeouts, but those patterns aren’t universal instructions. They describe tendencies that can help teams make decisions; they don’t settle what every hitter should do in every count or what every pitcher should do the third time through a lineup. The Rays found value in recognizing when a familiar rule didn’t fit. That judgment is part of analysis, too.
Strategy should follow the player
Consider the contrast between Johnny DeLuca and Chandler Simpson. DeLuca’s .429 slugging percentage came with Statcast indicators that offered little encouragement for a pull-heavy approach. That kind of swing can still suit one hitter; it would be a poor template for Simpson. A team that treats a league-wide trend as a requirement risks sanding away the skills that make individual players useful. The underlying metrics are most helpful when they explain what a particular player can do, rather than when they prescribe the same adjustment for everyone.
That distinction matters because a broad offensive trend can disguise very different routes to production. A pulled fly ball may be a productive outcome for a hitter whose swing and contact support it, while asking another hitter to chase that shape could weaken the parts of his game that already work. The relevant question isn’t whether a player conforms to the preferred model. It’s whether a change improves his chances without costing more than it adds.
The same logic applies on the mound. The third-time-through-the-order penalty is real, but it doesn’t mean every starter should leave as soon as the lineup turns over. Drew Rasmussen faced 71 batters across three starts against the Yankees and Guardians. When an ace is controlling a game, the matchup data matters alongside the conditions in front of him. A manager still has to weigh command, the quality of the at-bats, the available relief options and the likely cost of extending the outing.
Here’s the thing: a useful average describes what tends to happen across many situations. It can’t tell a manager exactly what’s happening in this one. The decision to keep a starter in becomes less about defending a general rule and more about reading the evidence that’s unfolding on the field.
Pitch selection has similar flexibility. Changeups are often associated with opposite-handed hitters, yet a pitch that gets same-side opponents out has earned its place. The point isn’t to discard evidence. It’s to avoid turning a useful tendency into a rigid command. Pitchers and coaches can use a pitch’s conventional role as a starting point, then judge whether its movement, location and results make it effective against a specific hitter. Not every successful adjustment needs to match the textbook pattern.
The World Series wasn’t a referendum on analytics
The Rays’ approach fits a broader argument prompted by the World Series between Tampa Bay and Milwaukee. The teams hit four home runs combined, the fewest in a Fall Classic since 1985. That low total led some observers to celebrate a return to small-ball baseball and treat the series as a rebuke of analytics. The appeal of that conclusion is clear: a handful of games can make a tactical story feel visible and decisive.
That reading stretches one result too far. A short series can produce an outlier without establishing a new model. Rob Mains has argued that the teams’ low home-run total shouldn’t be mistaken for a trend. The more revealing point is how both clubs tailored their approach to the players they had. A limited run of games can show how teams responded to their opponents and circumstances; it can’t, on its own, prove that a broad shift in strategy has taken hold.
Milwaukee offers a useful parallel. As Jarrett Seidler put it in his front-office rankings, the Brewers weren’t simply rejecting pulled fly balls: they had spent a first-round pick on Andrew Fischer. Instead, the club was willing to get the most from players whose strengths didn’t necessarily match that profile. That’s a more precise way to describe the choice: a team can value a general offensive idea while still building plans around players who contribute in other ways.
And yet, a low home-run total can still prompt a worthwhile question about how teams win. The answer needn’t be that baseball has swung back to one preferred style. It may be that teams can reach productive outcomes through different combinations of power, contact, baserunning and pitching, depending on who’s available and what a game asks of them.
Rules of thumb, not rules of baseball
Baseball has formal rules and traditions that live outside the rulebook: don’t steal with a big lead, don’t celebrate a home run too emphatically. Analytics challenged plenty of those conventions, while its own findings have sometimes hardened into new orthodoxy: prioritize strikeouts, discount batting average, avoid bunts and intentional walks. Those ideas can help teams question habits that survived on reputation alone. They can also become habits of their own when people stop asking what a finding actually says.
The distinction is between evidence and obedience. A tendency can guide a decision without dictating it, and a model can clarify tradeoffs without removing the need for judgment. If you’re working in this space, the practical challenge is to make sure analysis keeps describing the players and situations in front of you, instead of becoming a checklist that players are expected to satisfy.
Those principles can point teams toward sound decisions. They can also obscure the question that matters most: what gives this roster its best chance to win? The Rays’ examples suggest that a useful strategy begins with evidence, then adjusts to the player, pitch or game in front of it. This is more significant than it looks: flexibility isn’t a rejection of analysis, but a test of whether a team can apply it with care. Sometimes the exception is the better call.
What the approach means for teams
The broader implication is that analytical work has to leave room for individual skill. A team that adopts a successful pattern wholesale may miss the reason it worked in the first place: the fit between a tactic, a player and a particular situation. Similar systems typically help most when they inform choices while leaving decision-makers able to account for context. In baseball, that context includes the hitter’s strengths, the pitcher’s command and the state of the game.
That said, flexibility can’t just mean choosing whichever explanation supports a decision after the fact. Teams need to distinguish a deliberate adjustment from an exception made because a result happened to go their way. The evidence still matters; so does the discipline to ask whether it applies here. The Rays’ examples point toward a demanding standard: know the general tendency, understand the player, and be prepared to explain why one should outweigh the other.
Not a formula. A judgment.