Product Design
The Product Layer
How the public routes, layout decisions, and UI rules are designed to make ABS analysis readable under real user attention.
ByColby Reichenbach
Overview
Each route is supposed to answer one baseball question quickly.
AiBS is not designed as a single mega-dashboard. The product layer is routed so the user can start from the question they actually have: what is happening right now, how is a team using ABS, what kind of review profile does an umpire have, or what changed in one specific game.
That structure keeps the interface from collapsing under its own ambition. A product about ABS can get noisy fast. The route design is there to keep the experience opinionated and readable.
The product layer also makes scope explicit. Public AI is bounded to selected explanatory surfaces, the About desk functions as a permanent dossier, and the route hierarchy is meant to match the stable public product instead of an internal wishlist.
Route roles
The desks are deliberate.
The home page frames the league. Team pages show challenge identity. Umpire pages show review behavior. Game pages show event-level context. The About desk explains the product itself, and the Articles desk handles recurring editorial work. That separation is intentional product architecture, not just URL organization.
It also helps the visual language stay focused. Each page can prioritize the charts and copy that belong to its specific job instead of trying to be everything at once.
Scope discipline
Gating is part of product quality.
Several features remain intentionally gated rather than exposed half-ready. That includes global Copilot, Query Lab, and internal admin workflows. The product layer is stronger because scope is treated as a first-class decision instead of a temporary hack.
A smaller product with coherent boundaries is stronger than a broader product with fuzzy ones.