BLACKWELL/OS 2.6 WORK.TOURNAMENTS/PROBLEM THEME

Tournament Engine / Section 03 of 06

Problem

Core Question

How do we transform a fragmented, one-at-a-time registration system into a scalable tournament engine — without disrupting the ongoing OG-to-NG platform migration?

Tournament organizers and registrants alike struggled with a fragmented and inefficient registration process. The pain points fell into five categories:

Registration Efficiency
Each team, player, and staff member had to be registered and paid for separately — even when multiple registration types were needed in a single session.
Manual Organizer Workflows
Organizers manually handled tasks that should have been automated: adding players, managing waitlists, and enforcing roster caps.
Pricing Rigidity
No tools existed to vary registration costs by player position, role, or form response. A single flat price was the only option.
Poor Mobile Usability
Most users interacted with the system in the field and on the go, yet the interface wasn't optimized for mobile at all.
Inherited NG Debt
The in-progress NG system I inherited had its own usability and scalability gaps — addressed incrementally sprint over sprint to avoid derailing core work.

From a business standpoint, these shortcomings limited LeagueApps' ability to compete in the tournament software market — a space dominated by mobile-optimized, streamlined platforms.


PRESS / TO TYPE A COMMAND. TYPE HELP FOR A LIST.