Clubbie

I began with market and competitor research, mapping how existing products approached team management, sports statistics, communication, and social sharing. This phase did not include user interviews, so I used it to clarify the landscape and shape hypotheses rather than present unverified customer conclusions.

The resulting direction connected two product promises: help coaches and team administrators manage the day-to-day work, and give players, parents, and fans reasons to return, participate, and celebrate progress.

Clubbie needed to feel energetic and sports-led while carrying dense operational information. I used a dark navy foundation, bright blue actions, warm off-white text, and clear status colors to create contrast and focus across feeds, forms, events, and performance views.

Role-aware onboarding introduced the promise before asking people to register. Reusable navigation, tabs, cards, inputs, and data patterns kept the experience consistent as the product expanded from social content into team and payment workflows.

Team Hub brought events, member availability, lineups, statistics, subscriptions, and payments into one operational area. The hierarchy emphasized what needed attention now while keeping the wider team context close by.

Events connected schedules with attendance responses. Lineups made formation and player selection tangible. Payments separated pending requests, completed activity, and approval details so administrators could act without reconstructing the situation from messages.

The avatar generator extended the idea of a player profile beyond static information. A guided capture flow prepared people for a successful scan, then let them preview clothing and animated poses before publishing the result.

This was a distinctive product moment, but it still followed the system’s core rule: explain the next action clearly, show progress, and keep the result connected to the wider community experience.