Kamposa
A TOURNAMENT CONTROL CENTER DESIGNED TO REDUCE ADMINISTRATION AND GIVE EVERYONE CLEAR, LIVE INFORMATION.
I developed the product concept, information architecture, user journeys and visual system for Kamposa across desktop and mobile. The platform turns registrations into suggested classes, groups, schedules and venue allocations for the organizer to review and approve. Each audience receives a focused experience designed around its role.
The challenge
Running a tournament means coordinating registrations, teams, playing areas, schedules, results and constant changes. Organizers need a reliable operational overview, while team leaders, players and spectators need simple, live information without being exposed to the complexity behind it.
One system, tailored experiences
Kamposa uses one shared tournament system but presents different experiences for organizers, team leaders, participants and spectators. Organizers work from a desktop-first control center, while external audiences use focused mobile views built around the information they need at that moment.
Information architecture
I structured the product around a shared tournament model: organizations, tournaments, registrations, teams, classes, groups, playing areas, matches, results and standings. Organizers can move between these areas without losing context, while each external audience sees only the information relevant to its role.
Core workflows
The main workflow starts with tournament details and registrations. As registrations arrive, Kamposa can suggest classes, groups, match schedules and playing-area allocation for the organizer to review and approve. During the event, the control center shifts toward live matches, delays, missing results and upcoming activity.
Responsive by audience
The organizer experience is desktop-first and prioritizes overview, comparison and operational control. Mobile views are more immediate, bringing forward the current match, next fixture, playing area, result and standings so each audience can find the right information within seconds.
Design principles
The interface follows four principles: show the most important information first, keep actions in context, automate repetitive setup and use one consistent visual language across every role. A restrained palette, modular cards and clear spacing keep complex tournament information calm and manageable.
Outcome
The result is a connected product experience covering the full tournament journey, from registration and setup to live operations, public information and history. Kamposa demonstrates how automation and role-specific interfaces can reduce repetitive administration while making tournament information clearer and more reliable.
Selected interfaces
The organizer control center and public mobile experience use the same tournament data while giving each audience the level of detail, context and control it needs.
“Kamposa should help the organizer review and approve - not configure everything manually.”