As its an internal product all the screens shown here is recreated and changed to meet NDA requirements and they don't represent the actual functionality details and UI of the platform.
Internal platform: BMW research projects table with sidebar navigation

Empower Your Data
Research Teams

Internal platform for data analytics teams — covering project setup, asset marketplace, and budget management at 20,000-user scale.

My role: Product Designer (2020-2023)

Product overview

This project is an internal product for the #1 most valued brand in the consulting industry globally. It's a platform designed for data analytics teams.

Within the platform, users can create projects, invite collaborators, connect services, handle payments, monitor costs, and give clients access to research results. There's also a section for publishers, where they can create publisher teams, publish assets, provide support, and get information on asset usage. The target audience for this product is around 20,000 users.

Main sections

Project

Team Members Assets Project attributes
Project section schema — sidebar, asset list with statuses, stickers: Budget & costs / Team & access / Assets & status

Marketplace

Assets Curated pages Asset details
Marketplace section schema — categories and filter sidebar, asset tile grid, stickers: Discover & connect / Industry-curated spaces

Publisher space

Team Members Requests Asset statuses
Publisher space schema — published assets list with statuses, stickers: Revenue & usage stats / Asset requests
Discovery phase

What were the first steps?

Initial conditions:
The platform was originally developed by another company and later acquired for internal usage. It had very basic functionality that didn't fully cover actual user and business needs.
But we had some initial user base as the platform was helpful for some types of engagements.

User research

40 user interviews

Interview scenario sections (3-5 questions per section)

  • General work context and tasks
  • Detailed scenario of using the platform or alternative ways to complete tasks
  • Challenges with using the platform

Goals

  • Establish a structured interview and testing process for regular monthly application
  • Identify key pain points and value drivers for each role-based persona
  • Define user segments for each of the 4 key roles

Event based analytics

  • Developed an event taxonomy to choose and group key user properties and events to track
  • Created dashboards to track product and ux metrics
  • Created funnels for activation and some other flows
  • Identified steps in user journeys that caused significant drop-offs or time inefficiencies

24 moderated user testing sessions

Main user flows (3-5 session per flow)

  • Project creation
  • Adding team members
  • Discovering and adding assets
  • Managing multiple asset-related tasks (adding, removing, performing actions)
  • Navigation refinement via tree-testing for project-side navigation

UX artefacts (NDA)

  • Informational architectureGoal: refine navigation
  • Role-based personas and segment personas.Goal: synthesise user interviews so the team can understand and empathise with users.
  • Customer Journey Maps (CJM) for each role-based persona:Goal: map user stories and identify areas for improvement

Output

UX/UI

  • Decomposing complex forms into simple steps
  • Developed a plan to improve accessibility
  • Global and local navigation patterns refinement

Product

  • Drove prioritization of feature releases
  • Built the analytics dashboard the team used to track metrics
  • Designed and ran activation experiments

Processes

  • Established continuous user research processes
  • Integrated the design workflow into the broader product workflow

At the initial stage, it was important to define the expectations and goals of the business. I proposed conducting several stakeholder interviews and assisted in moderating the workshop.

Stakeholder research

Stakeholder interviews

Interview scenario sections (3-5 questions per section)

  • Vision for the platform in 5 years
  • Product development priorities
  • Design team responsibilities

Goals

  • Align stakeholder expectations
  • Define a high-level roadmap

Workshop

Design Thinking Workshop (1 week, 2-3 hours per day)

  • 7 participants with cross-functional expertise
  • Defined mid-term vision for the platform (1-2 years)

Goals

  • Clarify platform vision
  • Define high-level roadmap

Output

Product

  • Suggested prioritization of feature releases
  • Built an analytics dashboard to track key metrics
  • Proposed strategies to improve user activation

Processes

  • Suggested
  • Integrated the design workflow into the broader product workflow
Product overview

How did product look when you finished your job there?

Project:
This is the main entity of platform, created for each new client engagement. Within a project, you can monitor asset status, budget, edit the access levels, manage the team and the project info.

Project

Platform project view — BMW research assets table Platform project view — Costs dashboard

Marketplace:
Here, you can find and connect assets, learn additional details about their use, and visit curated spaces for specific industries.

Marketplace

Marketplace — curated spaces and featured assets Marketplace — asset detail view

Publisher Space:
Engaging users in the creation and distribution of their assets was crucial. Publishers can view requests for assets, support requests, see statistics on revenue and usage, and publish new assets.

Publisher Space

Publisher space — published assets overview Publisher space — asset status and revenue

I was also involved in creating a knowledge base and an admin panel for the platform.

Other

Knowledge base Admin panel
My role

What was your role?

My priorities was changing over these three years

Initial Phase (1st year):
When I first joined, the marketplace had a limited set of assets, about 50. Later, it expanded to several thousand, requiring a different approach to the catalog. At this time, my main task was a global redesign of the platform, transitioning from one design system to another, while also addressing smaller feature requests and expanding functionalities. I initiated improvements in platform accessibility, proposing to move away from grey colour in typography, enlarging fonts, and enhancing the experience for colour-blind users by adding distinctive elements to colour coding and increasing tonal contrast.

Second Phase:
We added the publisher space, created a knowledge base, and reworked the catalog. This phase introduced several large new sections, with a lot of time dedicated to research. I conducted interviews and user testing sessions, validating numerous hypotheses. I created clickable, interactive prototypes with tasks in Maze, a service that allows for automated testing of prototypes. I also started working on a mobile version of the platform.

Last Phase:
We added more roles at the project level and introduced asset-level access — so permissions could be managed at two layers, not one. This phase also introduced more ways to manage project finances, including dashboards and spending forecasts.

What about team?

During my time on this product, I experienced different team configurations, sometimes being the sole designer, other times leading the process or partnering in managing it.
In terms of design process, we focused on User-Centered Design (UCD) and prioritized moving forward in quick, small iterations.

Challenges

What were the main challenges?

Challenges:

  • Migrating to the new design system was the hardest part — components were used daily at scale, so changes had to land without disruption. The challenge lay in the fact that the new design system, which I was meant to adopt, was in its early stages and did not cover many necessary use cases, also lacking a wide range of essential components. In practice, it was harder than building a new design system from scratch.
  • Mapping the underlying technical model behind user operations was the hardest part — small UI choices had large engineering implications.
  • Managing roles at two different levels was also very challenging, as was the request to create custom roles within the project and on the asset level

Thanks for reading.

Next case Hearing Care Hub Keep scrolling