Data Product Platform

Data Product Platform

Transforming enterprise data discovery from a developer-only workflow into a self-service platform that increased adoption by 350%.

Transforming enterprise data discovery from a developer-only workflow into a self-service platform that increased adoption by 350%.

Transforming enterprise data discovery from a developer-only workflow into a self-service platform that increased adoption by 350%.

UX/UI Design

Research

Design Systems

oisinmckeever.com

Overview

1

Data products were difficult to discover, slow to create and lacked robust access control. Creation required API knowledge, discovery relied on word of mouth and permissions were managed inconsistently.


We redesigned the workflow into a self-service platform featuring a searchable catalogue, guided creation and role-based access controls, making enterprise data easier to discover while maintaining governance.

Outcomes

350%

350%

350% increase in adoption, helping shift the organisation toward self-service data consumption.

5x Faster Creation

5x Faster Creation

Reduced creation time from over 15 minutes to under 3 minutes, lowering the barrier for new producers.

Centralised Data

Centralised Data

All data housed under 1 roof, data discovery democratised

Role

Role

I led end-to-end product design, driving discovery, stakeholder alignment, research, interaction design and developer collaboration from concept through delivery.

The Challenge

2

01

Available data is scattered across the organisation, difficult to discover what's available and who can use it


02

The process of creating a data product is long and highly technical, limiting the amount of users who can create

03

Lack of access control processes in place for existing data, relying on due diligence of data owners


How might we create a platform to improve discoverability, streamlined data creation collaboration with enhanced access control?

How might we create a platform to improve discoverability, streamlined data creation collaboration with enhanced access control?

Research Insights

3

I interviewed a variety of data producers and consumers to understand the current data product creation process and process for discovering and consuming data across the organisation. This helped identify various pain points and opportunities to help shape the solution

Conducted user interviews with 8 producers and consumers to understand the creation, discovery and consumption process


Conducted weekly workshops with SME's, and users within the data practice to review progress and encourage collaboration with the project

Because access to users was limited, we relied on short research cycles, weekly workshops and rapid validation with subject matter experts to continuously refine the product.


Three themes consistently emerged. Discovery relied on word of mouth, creating a data product required over 15 minutes of API configuration, and requesting access was a slow manual process. These findings became the foundation for the product strategy.


Rather than inventing new interaction patterns, I deliberately borrowed familiar retail concepts such as catalogues, baskets and checkout. These existing mental models reduced learning time while making a highly technical workflow feel approachable.

Key Product Decisions

4

01 Data Product Catalog and Filter System

01 Catalog and Filter System

I designed a retail-inspired catalog for discovering available data products, a central location for all data products in the organisation. Users could search and filter to refine their search results.

oisinmckeever.com

oisinmckeever.com

Having a visual, familiar experience for finding products in one location made it much easier for users to consume data. Familiar search and filtering patterns reduced cognitive effort, allowing users to focus on selecting the right data rather than learning a new system.

Having a visual, familiar experience for finding products in one location made it much easier for users to consume data. Familiar search and filtering patterns reduced cognitive effort, allowing users to focus on selecting the right data rather than learning a new system.

oisinmckeever.com

02 Data Creation Wizard

The average time for creating a data product was around 15 minutes or more, and required highly skilled coding ability in order to create it. We wanted to significantly reduce the time taken but also make the process more accessible, attracting more producers to the platform.

oisinmckeever.com

Breaking creation into logical stages reduced cognitive load while allowing users to save progress and collaborate asynchronously. This transformed a technical workflow into something approachable for non-developers.

oisinmckeever.com

03 Customisable Check-Out

The complexities of data products required a highly customisable experience, what platforms to consume with?, which version of the data?, which output port type do you want to consume from?

oisinmckeever.com

Rather than exposing every configuration upfront, the basket became a staging area where users could review consumption options before provisioning. This mirrored familiar e-commerce behaviours while supporting highly configurable enterprise workflows.

Rather than exposing every configuration upfront, the basket became a staging area where users could review consumption options before provisioning. This mirrored familiar e-commerce behaviours while supporting highly configurable enterprise workflows.

Rather than exposing every configuration upfront, the basket became a staging area where users could review consumption options before provisioning. This mirrored familiar e-commerce behaviours while supporting highly configurable enterprise workflows.

oisinmckeever.com

04 Role Based Access Control

Controlling permissions and access to data was a high priority feature, we need to ensure data was secure and on a "need to access" basis. Rather than introducing another permission system, we integrated with the organisation's existing Active Directory groups. This reduced administrative overhead while aligning with established governance processes.

oisinmckeever.com

oisinmckeever.com

oisinmckeever.com

A producer can decide who can access the product using custom policies, which contain specified project groups. The system will automatically detect whether a consumer is a member of these groups or not, determining access and enhancing security.

A producer can decide who can access the product using custom policies, which contain specified project groups. The system will automatically detect whether a consumer is a member of these groups or not, determining access and enhancing security.

oisinmckeever.com

oisinmckeever.com

oisinmckeever.com

Reflection

5

The biggest challenge wasn't designing screens—it was translating a highly technical backend into workflows that felt familiar without sacrificing flexibility or governance.

By leaning on existing mental models from retail experiences, we reduced cognitive load while making enterprise data significantly more accessible to both producers and consumers.

oisinmckeever.com

oisinmckeever.com

oisinmckeever.com