Racing Post: Janus

The Racing Post’s B2C products – the website, the iOS and Android apps had been limping along on a very complex technical platform that was slowing down new feature development to a glacial pace, editorial content was creaking through an antiquated CMS, and the user experience had been design without many “users” involved. The overall effect was declining revenue as Racing Post couldn’t keep competitive, the editorial team getting increasingly frustrated by how limited their CMS was to handle new types of content, and new users bouncing at a high rate because they could not understand what was in front of them. Something had to given. The company finally bit the bullet and invested. On came Project Janus…  

THE CONTEXT & OBJECTIVES

Project Janus: Racing Post’s aim was to create a B2C product that is the aggregator of all Horse Racing & Sports Bettor needs/ This would drive growth across 5 customer related and 2 technology goals. The first customer facing product to be released was the app– it was the top revenue generator and the best platform to reach a larger swathe of the audience.

Design vision and user needs:
  1. We needed to get users involved this time. Most product features across platforms up to that point were never run by users and users were rarely consulted about new features / needs.
  2. The visuals and functionality needed to be modernised, refreshed, rebranded. The website and the app hadn’t had a proper design or brand revamp in nearly a decade. Users’ comments about the products included “old fashioned”, “fiddly” and “clunky”. It was time to use the rebrand to do a proper design and functionality revamp!
  3. The product needed to meet basic accessibility needs, most of the current core audience skewed older.
  4. We needed to engage our growth audience, not just core users. Our core base wasn’t getting any younger and, though very engaged (they loved our free news and data), very hard to monetise consistently. This caused the company to confront their bias that most of their monetisable audience was similar racing experts as themselves.

THE SET UP

  • My role: Director of Product Design and User Research
  • Company: Spotlight Sports Group, Racing Post brand
  • Main Team: B2C product designers, user researchers, B2C product management, delivery, development, 3 P&L owners, CPO, CTO, & the Editor in Chief

I was charged with overhauling the process of how discovery was tackled in the company, especially how the business interacted with design and research, trying to combine user feedback along with subject matter and discipline expertise when problem solving. 

THE PROCESS

Kick-off: Getting agreement on strategy, outcomes, and larger processes. This was the main part of my role on this initiative. That and to get the rest of the company to buy into the importance of user input. Trust was still being built on all sides between product, data, editorial, design, research and tech. My role was to get agreement with the Director of Racing, the CTO, CPO and the Editor in Chief  on what good user and business metrics looked like within the budgets / timelines. 

Working with Head of B2C Product and the CTO to map out how to approach breaking up the work for such a huge project. From a design POV, dev was building this platform in REACT, so we had to determine how to design for both app and web to have shared and native elements – without a design system already in place – at pace. I consulted with the design team – Design Sprints was decided as the methodology to tackle the massive scope.

A new, refreshed look
  • Modernising the look and feel to be more engaging and competitive
  • Bringing the UI inline with the new, lighter focused branding direction
  • Injecting more energy through photos, graphics and wider colour usage
  • Updating navigation patterns to emphasise dynamic content
  • Prominently displaying and positioning Racing Post’s unique content
Design sprint workshops…

Where post-its went to die. We were dealing with massive features or journeys in every design sprint (definitely not ideal and led to a lot of burn out later on). We needed a lot of outside input and had to please a large number of stakeholders with low UX matrity. By doing structured, scheduled, transparent design sprints, we were able to do discovery at pace and keep everyone in-the-loop, as relevant.

As part of the sprint process, I worked with the research team  to get in front of research needed for upcoming sprints and advised how to keep stakeholders in the loop on user testing viewing sessions. Refining research’s process fundamentally changed how the business worked with the UXDR team, especially in regards to consulting us about user knowledge and insights.

The beta release

It was a whole new app on a new platform – we had to do one big-bang release. No easing customers into it (not really) As the Android platform had the least revenue impact of our platforms, we started with a “blind” release to 500, 1000, 10,000 users in a forced app update. Along with the analytics data, we also set up in-app surveys to gage user reaction and identify any major technical or UX issues.  This went on for 4 months and allowed us to be more confident with the later iOS beta launch, our money maker platform.

And, of course, the design system and development process.

This project was a chance to finish implementing Racing Post’s rebrand that had kicked off a year prior.

The designers got to start from scratch with the look-and-feel and the design system – we didn’t want to carry over the older, antiquated brand and UI assets. And through this work, it organically created an opportunity to collaborate more closely with development, yielding better ways working, better design handover processes and documentation (thanks, Figma!). Ultimately, through some pain, we got the coded assets and designed assets naming conventions aligned, aiding in better UI consistency in the product and speeding up implementation of new designs for the future.

The result a new, cleaner, more consistent, better branded interface and more speed efficiency for the devs with the new design kit, along with more collaborative involvement earlier on in the feature design cycle. 

BEYOND PRODUCT: WORKING WITH EDITORIAL

The news and editorial side of the business was finally, after many long years, upgrading their extremely restrictive CMS. Transforming how news content would work in the Janus products meant editorial content could get a long overdue visual refresh. Editorial also wanted, needed, demanded more flexibility and features for how content could be presented on the website and in the apps. This led to changes in content taxonomy and the design of many variations of content presentation including:

    • Highlighting breaking news, video and audio content
    • Visually indicating which content needed a subscription
    • Dynamic data modules integrated into related articles
    • Differentiation between editorial feature content vs tipping and analysis
    • Highlighting racing festivals and related events
    • Live commentary feeds and social media integrations
    • Sponsored editorial and affiliate partner promotion
    • And all the states of each: bylines, date/time of publication, sharing, popularity, etc.

    A massive project all in itself, crammed into the same timeline. It only worked due to the good working relationships built between product management, design, research and Editorial, and the trust built between the teams.

    (Coming soon!) More Editorial design improvements:

    KEY HIGHLIGHTS AND FEATURES

    Racing Post insights and proprietary information more up front:

    (e.g. RP Verdict and Spotlights) Helping to showcase Racing Post’s specific content and expertise.

    More flexibility for News & Editorial:

    Switching to a new CMS system helped streamline processes, new designs from the Product Design Team added a new layer of flexibity in how they showcased content.

    Accessibility basics:

    All text, links, buttons (UI) meet a minimum size and a AA colour contrast– as Racing Post’s audience skews older than average, this was also a win.

    Helping users new to racing:

    More descriptive labels and easy, more obvious ways to access to info and data definitions–helping a larger audience to understand our content and convert with us.

    Racing Post App, main screens
    Racing Post App - more screens
    (Coming Soon!) Quick case studies about specific features and flows of this project:

    THE ORGANISATIONAL IMPACT

    Trust and understanding between the business, editorial and product were established: The UX maturity of the business and trust in qualitative research improved drasticaly throughout the new processes introducted in this project. Establishing Design Sprints involving all relevant the teams and stakeholders helped with raising the profile of designers to “business problem solvers” and with better sharing of subject matter expertise from different disciplines across the company to all teams involved.

    Proper understanding of our users: Through our pre-project user research and validation user testing sessions throughout the project, our stakeholders and subject matter experts gained a more broad, yet nuanced view of who used our products, when, how and why. This helped to break down long held assumptions and biases that had stymied product innovation. 

    Broader collaboration across departments within and outside of the product production track: The inclusiveness and transparency produced with the design sprint process lead to the design and research team to be first port of call for other departments looking for different or more creative way to solve their day-to-day issues, both in regards to deliverables and better processes.

    Long overdue improvements to News and Editorial content handling: Some improvements launched right away and others funneled into a detailed future-state plan for design and implementation of new content templates. The upgrades gave more flexibity to the Editorial team to present more engaging content in written, photographic and video formats, as well as better cross navigation and integration of racing data and tipping. 

    RESULTS

    The iOS app released in Oct 2022, the Android app in Nov 2022, some revised web areas in Jan 2023

    Commercial impact

    • In app conversion increased over 10%
    • News pages consumed up by 2.6 pages per session
    • Customer satisfaction scores increased from 3.1 to 4.5 (out of five) within 3 months; scores were always high with new and younger app users, long time customer ratings steadily rose
    • Increased customer set diversification, picking up more growth market and midlevel users

    Organisational impact

    • More formalised and accountable processes for agreeing on business and user needs, briefing teams, gaining user insight, and handover between departments
    • Design and research became seen as crucial problem solvers and strategic partners for iniatives across the business
    • New structures and opportunities for advancement and leadership resulted from the length and depth of this project

    Want more detail?

    This is just the topline . I am happy to go into more relevant detail. Just contact me and let me know which areas you’d like to know more about.

    Contact me
    Location

    London, UK

    Copyright

    2025. All rights reserved.