Overview
BYUM is a mobile and web platform designed to streamline the booking process for cricket umpires.
It addresses two key coordination challenges:
- Cricket organisers struggle to find qualified and available umpires quickly
- Umpires struggle to gain visibility and manage bookings efficiently
This project focuses on reducing operational friction and making booking status and availability clear.
The Problem
Umpire booking is often managed through fragmented methods (phone calls, WhatsApp groups, informal networks), which creates:
- unclear availability
- slow confirmations
- last-minute cancellations with no fallback workflow
- inconsistent qualification verification
The result is avoidable scheduling risk and high coordination overhead.
Users
- Primary: Cricket organisers (clubs, leagues, match coordinators)
- Secondary: Umpires (visibility, availability, booking management)
This is a two-sided workflow problem requiring trust and reliability on both sides.
My Role
I owned the product end-to-end: problem framing, workflow design, prioritisation, prototyping, and delivery across web and mobile.
Key Product Decisions
1) Prioritise booking reliability first
Focused on availability clarity and confirmation flows before expanding feature breadth.
2) Design for trust and coordination
Made booking states explicit to reduce back-and-forth communication.
3) Reduce manual overhead
Designed workflows to minimise reliance on external messaging and informal tracking.
What I Built
- Umpire profiles with qualification and availability visibility
- Booking workflow: request → confirmation → scheduling
- Umpire booking management: accept/decline and schedule control
- Communication/status visibility to reduce match-day risk
Outcomes
BYUM is built as a pilot-ready MVP, designed for validation with a small group of organisers and umpires.
Learnings
- Two-sided workflows succeed when reliability is designed in early
- Availability and confirmation are the real “product,” not the profile
- Clarity of state reduces operational friction more than adding features
What’s Next
- Pilot validation with organisers and umpires
- Improve matching (location, qualification, availability)
- Add cancellation and fallback workflows