The Hidden Architecture of Fairer Play: Lessons from MLB’s ABS System

In this conversation, MLB Vice President of On-Field Strategy Joe Martinez explains that the best way to modernize a legacy system is not to automate it entirely, but to design a human-in-the-loop mechanism that forces players to navigate trade-offs. The hidden consequence of the Automated Ball-Strike (ABS) challenge system is not just increased accuracy; it is the creation of a strategic layer that rewards situational awareness over raw talent. For leaders and operators, the takeaway is clear: the most durable innovations do not replace human judgment. They refine it by making the cost of error transparent and the incentive for precision undeniable. This insight provides a competitive advantage for those who prioritize systemic design over speed.

The Hidden Cost of Perfect Solutions

A common trap in systems design is the pursuit of total optimization, or the idea that if a technology can perform a task, it should perform it 100 percent of the time. Martinez explains that MLB deliberately chose not to automate every pitch, opting instead for a challenge system. This was not just a concession to tradition; it was a structural decision to preserve the game's flow and entertainment value.

> "We don't want the game slowing down too much. And even though we've worked very hard at making sure these challenges are adjudicated quickly and clearly in an entertaining way, a lot of them starts to become like especially you're sitting out of game like, all right, enough's enough let's just play baseball."
>
> -- Joe Martinez

By limiting teams to two challenges, MLB created a scarcity dynamic. This forces players to weigh the immediate benefit of correcting a single call against the downstream risk of running out of challenges in a high-leverage moment. When you remove the friction of a challenge, you remove the strategy. By keeping it scarce, the system ensures that the most important pitches get the attention, while the game maintains its momentum.

Why Immediate Discomfort Creates Lasting Moats

The transition to ABS required players to accept a new layer of complexity: the personalized strike zone. Historically, strike zones were living, breathing entities that shifted based on the umpire’s mood, the score, or the count. Martinez notes that replacing this with a fixed, height-based definition is a radical shift that initially feels uncomfortable.

However, the downstream payoff is consistency. By removing the variance of human perception, MLB has created a system where players can train against a stable target. The discomfort of adapting to a rigid, mathematical zone is the price paid for a long-term increase in fairness. Most organizations shy away from this kind of change because it disrupts established habits, but that resistance is exactly what creates a competitive moat. Once the system is implemented, the noise of bad calls is replaced by the signal of consistent data.

> "I think for the first time we have an actual defined definition of the strike. So even though the kind of robooch has tried to do it in the past, I'm not sure. That's how it was used actually. I know that's not kind of how it was employed right? The strikes one was almost like a living breathing thing."
>
> -- Joe Martinez

The System Responds: How Players Adapt

Systems thinking teaches us that participants will always route around a new policy. Martinez observes that because catchers have a better vantage point than batters, the challenge system currently skews toward the defensive team. This is a classic example of a second-order effect: a rule designed for fairness creates a new form of asymmetry.

The implication for operators is that no system is ever finished. The moment you introduce a new constraint, like a pitch clock or a challenge system, the participants change their behavior to exploit the new rules. The success of the pitch clock, which Martinez notes surprised even skeptics like his father, demonstrates that when you remove dead time, the system does not just get faster; it becomes more engaging. The downstream effect is a product that is objectively more watchable, proving that sometimes, forcing efficiency improves the core experience.

Key Action Items

• Audit for Scarcity: Identify processes where unlimited access is causing bloat. Introduce a challenge or budget constraint to force stakeholders to prioritize what truly matters. (Immediate)
• Map the Human-in-the-Loop: When automating, do not remove the human; place them in a position where their judgment is required to trigger the system. This maintains accountability and engagement. (Over the next quarter)
• Standardize the Strike Zone: Define your success metrics based on objective, repeatable criteria rather than living, breathing subjective standards that shift with context. (12-18 months)
• Embrace the Uncomfortable Baseline: If a new operational standard feels restrictive, recognize that you are likely removing subjective variance. The initial friction is a sign that you are building a more robust system. (Over the next 6 months)
• Monitor for Asymmetry: After implementing a new rule or process, track who benefits most. If the system creates an unintended advantage, plan for a secondary adjustment to restore balance. (Ongoing)