ARTEMIS SPORTSVERSE
SPORTS MANAGEMENT
2026
[ENTIRE PROJECT UNDER NDA. SCREENS ARE VIBECODED BASED ON PROJECT AND DOES NOT DEPICT ACTUAL UI]
ROLE
Product Designer
DELIVERABLES
End-to-end flow + Component Specs
STAKEHOLDER
Artemis Academy Platform
SKILLS
Information Architecture
Data Visualization
Prototyping
OVERVIEW
Artemis is a sports academy management platform serving multi-venue academies in the UAE. Operations teams use it daily to track sessions, bookings, and instructor activity across multiple locations. The platform had a working Capacity Report — a colour-coded matrix showing booking fill rates by level and day of week but it was built around venues, not teachers.
As academies scaled, the ops question shifted. It was no longer just "is this slot full?" — it became "is this teacher performing, compliant, and financially contributing at the level we expect?" The existing matrix couldn't answer that. My task was to evolve the page into a full Teacher Reports workspace without discarding what already worked.
THE PROBLEM
The report framed everything around venue and slot fill and not around the individual teacher. You couldn't answer "how is Erma performing?" from the existing page.
Venue was a single-select filter, so teachers who worked across multiple venues in a term had no way to see their full picture in one view.
There was no separation between time at venue, time teaching, and setup time. Ops teams couldn't distinguish an efficient teacher from one with a lot of idle time.
Revenue, compliance, and admin completion (registers, progress marking, sick days) lived in separate tools or weren't tracked at all. No single view tied financial impact to teacher-level data.
Existing capacity report screen
THE CHALLENGE
The hardest constraint was information density. A teacher report for a single instructor across two venues and one term could legitimately surface: 9 KPI cards, a capacity matrix, a time breakdown chart, a revenue trend chart, a compliance scorecard, a sick leave log, and a student movement table. That's a lot to hold in one page without it collapsing into noise.
The design principle I anchored on was: keep the matrix focused on delivery and capacity — and move richer operational and financial data into summary cards, charts, and drill-down panels. Hierarchy over completeness.
MY APPROACH
The first fork in the design was whether to build this as one very long scrollable dashboard or as a tabbed workspace. A single-scroll approach would have kept everything accessible without clicks, but at the cost of mixed semantics — compliance data next to capacity cells next to revenue charts, with no clear reading order.
I chose a four-tab structure. The filter bar and KPI summary strip remain persistent above the tabs giving operations teams their top-level answer without needing to navigate at all. The tabs then separate distinct analytical modes so each section can be dense without cluttering the others.
Filterbar Redesign
The existing filter bar was extended with three meaningful additions beyond the original Term / Venue / Days / Level / Teacher controls.
Redesigned filter bar with tokenised venue chips
The KPI Summary Strip
The strip is the first thing operations teams see after generating a report. It answers "what's the story for this teacher?" in one horizontal scan before anyone opens a tab. Nine cards, grouped into three meaningful clusters.
Summary - Top level status at a glance
The Analytics Layer
Revenue Attribution
Revenue attribution was the most technically nuanced part of the spec. Rather than showing gross session revenue, the design ties revenue to work completion — so a teacher who completed 80% of a session's delivery is attributed 80% of that session's revenue. This creates an honest financial picture, not an optimistic one.
Teaching Detail Matrix
The level × day matrix was already doing its job well for capacity and completion states. The changes were additive, not disruptive.
The drawer keeps the matrix clean in its default state. Revenue and compliance data only appear when you've chosen to go deeper on a specific cell. This prevents the most common failure mode of data-heavy reporting UIs: putting every number everywhere until nothing is readable.
THE OUTCOME
4
Distinct analytical modes in one workspace
9
KPI cards answering the top-level teacher question before any tab is opened
0
Changes to the existing matrix logic. It was preserved and wrapped, not replaced
The most meaningful outcome was architectural rather than visual: the page now has a hierarchy. Operations teams get their answer from the KPI strip. Managers who need to go deeper open the Teaching Detail or Revenue tabs. HR or compliance reviewers use the Compliance tab in isolation. Each user type can move to their relevant layer without wading through the others.