Metaratings: products and design leadership
At Metaratings, I led a design team of five covering sports platforms, mobile apps, and marketing, and later reduced its size. As Head of Design, I built products and presentations, reviewed the team's work, and changed how we delivered it. The challenge was to keep improving the products while reducing repeated design work and frontend handoffs.
Taking sports products beyond isolated screens
For the METARATINGS redesign, I brought navigation, the match center, news, bookmaker ratings, and product modules together in a working web prototype. Review could follow a reader between these parts of the product, rather than stop at individual Figma screens. The prototype was deployed; further development was later put on hold because there was no capacity to continue.
I also built NextSport, a sports and esports publishing platform with editorial tools and product analytics. It reached a public release and was handed over for ongoing support.
Building WINSCORE for three regional apps
WINSCORE brings scores, matches, tournaments, teams, and players into a native app. I designed the product and a tokenized UI kit reused across three regional apps. Shared components and light and dark themes let regional work build on the same design decisions instead of recreating the interface.
The product also had a separate web implementation, WoWscore. Native and web work continued with the product team after handover.
Making the partnership proposition presentable
I built a METARATINGS partner pitch explaining the CPA proposition, how the partnership would work, and the questions to settle before a pilot.
I also worked on the METARATINGS and WINSCORE brandbooks so product and marketing teams had shared rules for their materials. The brand systems were handed over to their respective teams.
Reducing repeat work without dropping design review
The team needed a way to reuse decisions and carry them into implementation. For METARATINGS web, Storybook exposed component states for frontend handoff. For WINSCORE, the native UI kit carried that role. Design Portal collected the methodology, review criteria, and repeatable production paths in one place.
Repeatable landing-page production moved into design, removing the routine frontend handoff from that work. I reviewed design quality and coached the remaining designer to deliver independently.
Requests had arrived through direct messages and separate Figma files. I put intake, priorities, capacity, and reporting into YouTrack so product work could be planned alongside those responsibilities. I also prepared an AI validator for task goals, readiness, and review evidence; it remained in read-only testing at handover.