Aspire Academy, Qatar's national football development organization, needed a comprehensive platform to manage every aspect of their players' journey — from youth development to World Cup preparation. The challenge wasn't just building a tool; it was digitizing an entire operational structure that had been running on Excel spreadsheets, PDFs, and manual approval processes. The platform had to serve multiple stakeholders simultaneously: administrators managing rosters and logistics, coaches tracking team performance, physical trainers monitoring individual conditioning, and directors overseeing the academy's overall progress. Each role required its own views, workflows, and data access — all within a single system. I was the sole UX/UI designer on this project, working alongside a Product Owner, a Project Manager, and four developers (frontend and full-stack). The team worked with Vue.js and Node.js. The client communicated their needs through Excel files and PDF reports — documents we had to carefully analyze to understand existing workflows before we could redesign them digitally.

The starting point was understanding how Aspire's staff actually worked. They brought us their Excel files and internal PDF reports — these were the real source of truth for their operations. From there, working closely with the Product Owner, we translated those manual processes into digital flows, defining what each module needed to do before any wireframe was drawn. Aspire provided their brand style guide, which served as the visual foundation. Since many UI components didn't exist in their guidelines, I built them from scratch — tabs, specialized buttons, data tables, selector panels — creating a component library that was consistent with their identity but built for complex operational use. The information architecture was one of the most demanding parts. Players connect to teams, teams connect to tournaments, tournaments connect to matches, matches connect to individual stats — all of it had to be navigable in ways that made sense for each type of user. A physical trainer needed quick access to conditioning data per player; a director needed aggregated views across the entire academy.

The platform covered the full lifecycle of Aspire's operations. Player profiles tracked development over time — training attendance, physical metrics, nutrition, match participation, and performance data per tournament and per game. Coaches and physical trainers could drill down to individual stats or pull up team-level summaries, with data visualizations designed for quick reading during active sessions. One of the more complex modules was the tournament creator. Aspire ran internal competitions regularly — weekend tournaments across different age categories and divisions. The tool let administrators build a tournament from scratch: define categories, schedule matches, assign referees, track scores, goleadores, and awards — all in one flow. This replaced what had been a fully manual, paper-based process. The approval and reporting system was another critical piece. Staff generated reports that needed to be reviewed, signed, and authorized by different levels of management before being archived. I designed those flows to mirror the real authorization chains within the academy, with status tracking and notification systems built in.

The platform was delivered and adopted by Aspire Academy as part of their direct preparation for the 2022 FIFA World Cup. Over a year and a half of continuous development, the system replaced Excel-based operations with a centralized digital platform covering player tracking, training management, tournament administration, performance data, and internal reporting. Being the only designer on a project of this scale for this long taught me how to maintain consistency and quality across a large, evolving system. Modules built in month three had to feel coherent with modules built in month eighteen — which required disciplined component management and close collaboration with developers throughout. It also reinforced how important it is to start from real user workflows rather than assumed ones. The Excel files and PDFs the client brought us were the most valuable design input we received — they showed exactly what the staff needed, in the language and structure they already understood.