API | Data Structure | Operations | Customer sucess

Areas Impacted
Operations | Product | Customer Success
Products involved
Mobile Apps, Web dashboard, API B2B Product
Project Overview
In building a scalable sports analytics platform, I tackled complex challenges to deliver value across multiple fronts ensuring data integrity, enhancing user experiences, and streamlining internal operations. Each solution empowered users, reduced operational overhead, and future-proofed the system for growth.
- Dynamic Player Identities: Solved jersey number changes mid-tournament, preserving historical data while ensuring live updates across 4 platforms.
- User Management Tools: empower users and reducing dependency and costs on OPS support.
- Unified Communication System: Automated real-time notifications for internal teams and end-users, improving transparency and cutting manual effort.
- Self-Service Knowledge Hub: Created a Notion-based resource for coaches, reducing FAQs and empowering users with guides, videos, and checklists.
Managing Dynamic Player Identities & Data Integrity Across Platforms
Challenge: Track dynamic player jersey numbers (changing mid-tournament) while preserving data integrity and delivering accurate stats across 4 platforms (mobile, web, internal tools). Users needed to update player identities (name/numbers) without disrupting historical data or live stats.
Solution:
- Linked stats to unique player IDs (not jersey numbers).
- Built dynamic UI logic to display current/jersey-specific stats contextually.
- Automated cross-platform sync to ensure real-time consistency (stats, videos, apps).
Result:
- Admins update player details freely; historical stats stay accurate.
- Example: A player switching from #4 to #5 retains legacy stats under #4, while live data reflects #5—no overlap with the new #4 player.
- Scalable system for future tournaments/platforms.


Insights for coaches to get the right performance data
Challenge: While player-users viewed stats via the mobile app, coaches needed a dedicated interface to manage teams, players, and games without relying on internal OPS support.
Solution:
We implemented management features in a web dashboard:
- Edit jersey numbers per game/tournament and schedule matches.
- Integrate videos: Upload match footage linked to specific games/players.
- Access custom stats views: Tailored metrics for in-depth analysis.
- Streamline team onboarding with an invite system (in-app + email).
Result:
- Coaches edit jersey numbers mid-tournament in live stats or historical data.
- Unified workflow: Schedule updates or video uploads once → reflect instantly across all platforms.
- User self-management reduced internal operational costs significantly.
Notification logic system design and documentation
Challenge: Designing a cohesive communication system to notify:
- Internal teams (via Slack and internal platform “bell” notifications) about game upload statuses (success, errors, readiness).
End-users (via push notifications, in-app “bell” alerts, and email) for reminders (e.g., upcoming games), team invitations, results updates, and game status changes.
Solution:
Documented and automated real-time messaging logic with validations
- Internal alerts triggered by API events (e.g., “Game uploaded successfully,” “Error: Missing player stats”).
- User notifications tied to key actions:
- Push/in-app alerts: “Your game starts in 1 hour,” “You’ve been invited to Team X.”
- Email summaries: Post-game stats, onboarding confirmations.
- Logical timing rules (e.g., reminders sent 24h/1h before games; errors).
Result:
- Users stay informed with timely, non-intrusive updates across channels.
- Reduced manual effort and OPS costs with predefined triggers and validation workflows.


From OPS Workflows to Self-Service User Empowerment
Challenge: The OPS team needed clear procedures for data changes (confidential processes not detailed here). This required documenting all possible scenarios, timelines, and workflows to reduce errors. Additionally, we needed a self-service solution for end-users (e.g., coaches) to understand processes without direct support.
Solution:
- Documented all data change scenarios, including:
- When and how to edit jersey numbers.
- Timelines for updates to reflect across platforms.
- Validation rules to prevent conflicts.
- Created a Notion-based knowledge hub for end-users, featuring:
- Step-by-step procedures.
- Video tutorials.
- Checklists for coaches (e.g., onboarding, editing player details).
Result:
- OPS team saved time with standardized workflows for data changes.
- Improved user satisfaction with clear, accessible documentation.
- Avoided implementation costs by leveraging Notion for the knowledge hub.
Data logic definition and API documentation
Challenge: Adding a new sport introduced unique scoring logic and required API-driven results delivery for B2B customers. This demanded updates to internal/external apps, validation rules, and clear documentation to avoid data conflicts.
Solution:
- Collaborated with backend/frontend teams to design scoring workflows, including:
- Sport-specific rules (what actions award points, validations).
- Wireframes for UI/API interactions to reflect logic changes.
- Built a scoring logic to adapt to sport differences without overhauling core systems.
- Documented APIs and scoring logic for B2B customers to ensure seamless integration.
Result:
- Unified system handles multiple sports with zero scoring conflicts.
- B2B partners access sport-specific stats via standardized APIs.
- Scalable framework for future sport additions.
