Tournament Engine / Section 04 of 06
Process
Discovery
Research began by analyzing feedback from recorded customer success and sales calls in Gong, then synthesizing insights in Dovetail. I facilitated assumption-mapping workshops and prioritization exercises to validate what we believed we knew about our users.
We interviewed over 20 tournament organizers plus a handful of parents and coaches. One surprising insight: organizers frequently registered returning teams on their behalf — a clear signal that the registration flow was too time-consuming for busy coaches and staff.
Key Insights
- Bulk registration was the single highest-impact capability missing from the platform
- Flexible pricing models and payment plans were requested by nearly every organizer interviewed
- A native waitlist system was missing but highly requested — most partners had built manual workarounds
- Tournament caps (by team or player count) needed to be configurable at the program level
- Mobile-first was non-negotiable — nearly every critical action happened on a phone, on a field
Design & Strategy
With these insights, I restructured the experience around scalability and reuse — not just patching existing flows, but rearchitecting the registration model.
Introduce a bulk registration cart and simplified checkout
WhyOrganizers needed to register dozens of teams in a single session. One-at-a-time checkout created compounding friction and payment errors.
TradeoffCart architecture added backend complexity and required coordination across Payments and Registration squads during an already fragile migration window.
Dynamic payment plan entry — up to 12 configurable options
WhyThe original structure offered a single fixed payment option. Partners needed granular control over installment schedules to serve different budget situations.
TradeoffMore options risk decision paralysis. We capped at 12 and added smart defaults to reduce cognitive load for both organizers and registrants.
Apply Fieldhouse DS for accessibility and consistency
WhyFieldhouse enforced WCAG 2.1 compliance across the platform. Tournaments needed to meet the same baseline — especially for mobile and form-heavy flows.
TradeoffSome component constraints required custom pattern work. We contributed back to the system rather than working around it.
Reduce visual clutter — open layouts over box-heavy UI
WhyThe existing NG interface was dense and overwhelming. Tournament registration involves many steps and high-stakes decisions — clarity reduces error rates.
TradeoffOpen layouts can feel less structured to power users. We used progressive disclosure to keep advanced controls accessible without surfacing them by default.
Collaboration & Handoff
I led design reviews across both squads, presenting work twice monthly to leadership and weekly to engineering. During handoff, we used boxing exercises — structured working sessions mapping each UI element to its backend endpoint — to catch mismatches early and keep velocity high.
Feedback loops were tight: constant iteration between Figma prototypes, Jira tickets, and in-progress demos kept all parties aligned without heavy documentation overhead.
Testing & Iteration
I moderated prototype walkthroughs at key decision points. The most significant early win came from a single microcopy change.
Registrants were entering parent information where tournament administrators expected child information. One field label update nearly eliminated the error entirely.
RUN DEMO: Compare the original and updated labels
These iterative test-and-learn cycles transformed stakeholder understanding of user testing's value — leading to broader adoption of unmoderated usability testing company-wide.
Bulk Cart & Core Registration
- Bulk team registration cart
- Mobile-optimized checkout
- Roster cap configuration
- Fieldhouse DS application
Pricing, Waitlists & Compliance
- Dynamic payment plan builder
- Native waitlist management
- Position-based pricing logic
- Automated compliance flows