Chapter 07 — Evaluating and Developing Technology Solutions#
Sports Context#
The Decision That Changed Everything#
Jordan Martinez stared at her spreadsheet, coffee growing cold. As newly promoted director of operations for the River City Thunder minor league baseball team, she faced her first major challenge: their outdated ticketing and fan management system was failing. Online purchases crashed during promotions, season ticket holders complained, and manual concession tracking was costing revenue. The general manager asked her to lead the search for a new integrated system.
“I studied sports management, not computer science.” But evaluating technology isn’t about coding — it’s about understanding business needs and making strategic decisions.
Week One: Understanding What Success Looks Like#
CFO Marcus introduced Jordan to a Technology Evaluation Framework — a structured approach for assessing technologies based on functionality, cost, risks, and alignment with business goals. Jordan spent a week interviewing ticket office staff, concessions managers, marketing, and fans. Pain points: website crashes during flash sales, no mobile ticketing, disconnected concession and merchandise systems, hours wasted reconciling data. Opportunities: dynamic pricing, integrated loyalty programs, mobile concession ordering, data analytics for marketing.
Total Cost of Ownership (TCO) — the full cost of acquiring, implementing, and maintaining a technology solution — included software licenses, hardware at the ballpark and ticket office, training for 75 staff, technical support, system integration costs, and implementation time.
The cheapest option upfront had the highest TCO due to expensive per-transaction fees. The mid-priced option included training, support, unlimited transactions, and updates in its subscription.
Jordan’s Return on Investment (ROI) — comparing the benefits of an investment with its costs — showed dynamic pricing alone could generate $960,000 in additional revenue on high-demand games (8% of $12M). Better inventory management would save $85,000 in food waste annually. The system would pay for itself within 18 months.
Week Three: Development Approaches#
IT manager Sarah introduced the Software Development Lifecycle (SDLC) — the structured process of planning, building, testing, and deploying software. Understanding it helped Jordan ask better vendor questions.
Waterfall Methodology — a sequential approach with completed phases — suited stable requirements like ticketing and payment. Like constructing a stadium: structure before seats.
Agile Methodology — an iterative method emphasizing flexibility and rapid delivery — suited experimental features like personalized fan experiences and predictive analytics. Like a coach adjusting game strategy based on what’s working.
Week Five: MVPs at the Ballpark#
Minimum Viable Product (MVP) — a functional version with just enough features to validate key assumptions — let Jordan test vendors during a weekend series. Vendor A handled ticketing well but struggled with concessions. Vendor B was slower but more intuitive for part-time staff. Vendor C failed integration tests with accounting software and league reporting systems. Season ticket holders were even invited to test the mobile app, generating negotiating leverage for additional features.
Week Seven: RFPs and SLAs#
A Request for Proposal (RFP) — a formal document outlining requirements and evaluation criteria — asked vendors how they’d handle 4,200 simultaneous ticket purchases, provide game-day support, integrate with league systems, and plan for future features.
The Service Level Agreement (SLA) — a contract defining performance expectations — specified 99.9% uptime with 15-minute response times for critical issues during games. Vendor A wouldn’t commit to game-day priority support. Vendor B charged extra for evening and weekend support — exactly when the Thunder needed it most. Vendor C included 24/7 support with dedicated game-day assistance.
Week Ten: Change Management#
Change Management — a structured approach to preparing people and organizations for new technologies — meant getting 75 staff across ticketing, concessions, merchandise, marketing, and operations to adopt the new system. Jordan communicated the “why,” trained department “super users” who then trained peers during the off-season, and scheduled training to avoid disrupting game operations. The rollout started during spring training with smaller crowds, then launched fully for opening day.