Back

Red Bull Backend Applications

Red Bull Backend Applications

Product Design
User Research
User Testing
Design System
Product Strategy
Product Design
User Research
User Testing
Design System
Product Strategy

Agency

OkayBueno

Role
Product Designer

Duration
11 Months

Red Bull Owned Media operates globally across more than 100 countries, managing a vast ecosystem of digital platforms, channels, and publishing tools. These platforms allow the brand to create and distribute its own content, build a consistent identity, and connect directly with its audiences without relying exclusively on paid or traditional media.

Over time, this ecosystem grew into 25+ backend applications developed independently, resulting in fragmented experiences, inconsistent interfaces, complex navigation, outdated design systems and inefficient workflows for the teams relying on them daily, forcing employees to rely on inconsistent, overly complex, and hard-to-use tools that reduced productivity and created financial inefficiencies for the company.

Agency

OkayBueno

Role
Product Designer

Duration
11 Months

15 in-depth user interviews with Red Bull team members across different roles (editors, channel operators, managers) and time zones.

Analysis of application usage to identify which tools were most critical in day-to-day operations.

Observation of workflows to uncover inefficiencies, repetitive tasks, and bottlenecks.

The Challenge

Reduce complexity and create a unified app ecosystem.

Reduce complexity and create a unified app ecosystem.

How?

Improving workflows, introducing shared navigation patterns, and creating a scalable foundation for Red Bull’s internal platforms.

Improving workflows, introducing shared navigation patterns, and creating a scalable foundation for Red Bull’s internal platforms.

My Role

As a Product Designer, I led both research and design to simplify the ecosystem and improve tools for Red Bull’s global teams.


I collaborated closely with the Red Bull team and stakeholders to align research, design, and product strategy.

Key Metrics

  • Task completion time for key workflows across apps.

  • Number of support requests during user onboarding (first 3 months).

  • Number of publishing errors (especially those related to not following new directives)

Research

To build a deep understanding of the problem, I carried out a multi-layered research process:

15 in-depth user interviews with Red Bull team members across different roles (editors, channel operators, managers) and time zones.

15 in-depth user interviews with Red Bull team members across different roles (editors, channel operators, managers) and time zones.

Analysis of application usage to identify which tools were most critical in day-to-day operations.

Observation of workflows to uncover inefficiencies, repetitive tasks, and bottlenecks.

Analysis of application usage to identify which tools were most critical in day-to-day operations.

Observation of workflows to uncover inefficiencies, repetitive tasks, and bottlenecks.

15 in-depth user interviews with Red Bull team members across different roles (editors, channel operators, managers) and time zones.

Analysis of application usage to identify which tools were most critical in day-to-day operations.

Observation of workflows to uncover inefficiencies, repetitive tasks, and bottlenecks.

To protect the interviewees’ privacy, their faces have been blurred.

To protect the interviewees’ privacy, their faces have been blurred.

A clear set of pain points emerged:

Inconsistency across applications: each tool had a different navigation system and interaction model, which confused users and slowed them down.

Repetitive and manual tasks: for example, editors often had to update the same asset across 30+ locales manually.

Lack of transversal tools: there was no unified way to communicate internal announcements or provide quick access to frequent tasks.

Content discovery challenges: inefficient search and tagging systems made it hard to find and reuse content.

Country-specific workarounds: since teams in different markets used the apps differently, issues were solved in isolation, making it difficult to learn from each other.

Country-specific workarounds: since teams in different markets used the apps di

Inconsistency across applications: each tool had a different navigation system and interaction model, which confused users and slowed them down.

Repetitive and manual tasks: for example, editors often had to update the same asset across 30+ locales manually.

Content discovery challenges: inefficient search and tagging systems made it hard to find and reuse content.

Lack of transversal tools: there was no unified way to communicate internal announcements or provide quick access to frequent tasks.

Country-specific workarounds: since teams in different markets used the apps differently, issues were often solved in isolation, making it difficult to learn from each other.

Goals & Design Strategy

After doing Research we could start with a set of requirements for Red Bull's app ecosystem:

Our strategy was to reduce friction and bring intelligence into existing workflows. We explored how to unify and extend current tools, especially the Editor App, which is the most relevant application as it already covered 80% of user activity.

After doing Research we could start with a set of requirements for Red Bull's app ecosystem:

After doing Research we could start with a set of requirements for Red Bull's app ecosystem:

Slide from a deck I created to present user sentiment. The right side shows which participants shared the same pain points.

Document from my user research showing the percentage of time each participant spent on each app.

After reviewing all the research documentation, I needed to start drawing conclusions and forming hypotheses, and in doing so we uncovered insights that slightly shifted the project’s focus. By clustering the requirements, clear themes emerged: faster workflows, smarter editor options, better content discovery, and improved visibility.

Bugs (4)

Content Discovery (6)

Faster & Easier Workflows (32)

Editor Options (5)

Co-Creation (1)

Reminders & Tasks (7)

Some examples of these requirements that later would be part of the design strategy:

FASTER & EASIER WORKFLOWS

“I don’t use the Editor App that often and I struggle when I have to Create an image gallery”

Guidance for performing certain actions

“I don’t use the Editor App that often and I struggle when I have to Create an image gallery”

Guidance for performing certain actions

FASTER & EASIER WORKFLOWS

“I want to be notified when an embargo date has passed so I get reminded that I have to unpublish a story”

Notify when an expiration or embargo date has passed

REMINDERS & TASKS

“I want to see if any of my stories is getting many views”

Giving information on how user’s stories perform will help them to know what works better

CONTENT DISCOVERY

“I would love to be able to set different aspect ratios and better focal point support”

Enable more options for Image Sizing/Framing

EDITOR OPTIONS

REMINDERS & TASKS

“I want to be notified when an embargo date has passed so I get reminded that I have to unpublish a story”

Notify when an expiration or embargo date has passed

CONTENT DISCOVERY

“I want to see if any of my stories is getting many views”

Giving information on how user’s stories perform will help them to know what works better

EDITOR OPTIONS

“I would love to be able to set different aspect ratios and better focal point support”

Enable more options for Image Sizing/Framing

All requirements were clustered into two directions:

General Solutions
Solutions that solve more than 1 requirement. For example, we have 5 requirements from users that could get solved with the implementation of a Notification Center. The Notification Center is a general solution, and so it is the Quick Action Bar.

Specific in-app Solutions
Solutions that tackle existing problems from within existing tools. For example, the implementation of Bulk Editing in the Editor App, or repairing things that don’t work.

Key Design Solutions

I proposed a set of interconnected solutions and features, what we called solution starters, that directly addressed pain points from research:

Key Design Solutions

New Design System: “Gravity”

We introduced Gravity, a design system built on Red Bull’s existing foundations and adapted for complex backend workflows. It unified interaction patterns across applications, reducing cognitive load and improving usability, while also bringing scalability.

I contributed by proposing ideas, testing components, and defining new ones, while a teammate led the system’s implementation.

Unified Navigation across all apps

Each application had its own navigation logic, making the ecosystem difficult to scale. We introduced a unified navigation bar across all apps, standardizing core elements while allowing product-specific customization.

Here are examples of how the navigation bar would scale and adapt across different applications in the ecosystem.

A Shared Entry Point for All Apps: Ecosystem Hub

I created a unified homescreen as a shared entry point to the ecosystem. Users could see quick actions, access the apps relevant to their user role, and have a more guided experience. This not only made the ecosystem more approachable but also set the foundation for scalability.

Notification Centre

Red Bull lacked a system for internal announcements. We introduced a cross-app Notification Centre to deliver timely updates, reminders, and insights directly within user workflows.

Quick Action Bar

To reduce friction, especially for new users, we introduced a Quick Action Bar integrated into the navigation. This allowed users to perform frequent actions such as creating stories, uploading media, or checking upcoming events without having to guess which application to open. It streamlined onboarding and simplified recurring tasks.

When the user clicks on Quick Search, the Quick Action Bar opens in the center of the screen in focus mode, blurring the background while keeping the navigation bar visible.

Impact & Learnings

By introducing these design solutions, the project directly addressed Red Bull’s goals of reducing friction, streamlining workflows, and designing for scalability.

These solutions gave users consistent patterns across apps, seamless transitions within the ecosystem, faster access to frequent actions, and timely feedback through notifications, ultimately improving efficiency while laying the foundation for a unified and future-proof platform.

41%

Quicker onboardings for new users.

64%

Reduction in support tickets

28%

Fewer publishing errors

This project underlined the importance of balancing user needs with organizational strategy. By resisting the temptation to add a new product, we instead delivered a vision for simplifying and strengthening what was already in place.

The process also highlighted how critical it is to involve diverse user groups in research. Insights from editors in Japan, programmers in Switzerland, and engineers at RB Racing all converged to shape a solution that worked globally.

In the end, the project wasn’t just about new features. It was about a mindset shift: from building more to building smarter, turning Red Bull’s complex ecosystem into a unified, future-proof platform for Owned Media.

I collaborated closely with the Product Manager on strategy and with the Red Bull team throughout the process, while leading presentations and stakeholder alignment to ensure clarity. At the same time, I was responsible for all research and design work.

I collaborated closely with the Product Manager on strategy and with the Red Bull team throughout the process, while leading presentations and stakeholder alignment to ensure clarity.

At the same time, I was responsible for all research and design work.

Product Design
User Research
User Testing
Design System
Product Strategy

Agency

OkayBueno

Role
Product Designer

Duration
11 Months

Red Bull Owned Media operates globally across more than 100 countries, managing a vast ecosystem of digital platforms, channels, and publishing tools. These platforms allow the brand to create and distribute its own content, build a consistent identity, and connect directly with its audiences without relying exclusively on paid or traditional media.

Over time, this ecosystem grew into 25+ backend applications developed independently, resulting in fragmented experiences, inconsistent interfaces, complex navigation, outdated design systems and inefficient workflows for the teams relying on them daily, forcing employees to rely on inconsistent, overly complex, and hard-to-use tools that reduced productivity and created financial inefficiencies for the company.