Data Hub

Data Hub

A one-stop-shop for all things data. A centralised hub for the global data practice. Learn, explore and connect.

A one-stop-shop for all things data. A centralised hub for the global data practice. Learn, explore and connect.

UX/UI Design

Research

Design Systems

My Role

As the design lead I was responsible for leading the vision, research strategy and design for the project. I collaborated closely with key stakeholders, users and developers to ensure our designs were functional, aesthetic and solved both the business and users requirements.

Team Structure

2x UX Designers,

2x UX Designers,

3x Front-end Developers,

3x Front-end Developers,

Product Owner

Product Owner

Research Methods

Competitor Analysis,

Competitor Analysis,

Interviewing,

Interviewing,

Workshopping,

Workshopping,

Usability Testing

Usability Testing

Platform

Web

Web

Web

Project Duration

6 months

6 months

6 months

Tech Stack

Overview

001

Overview

001

Overview

001

The initial ecosystem had led to duplication of work due to lack of visibility across the practice as well poor engagement and collaboration. The bank partnered with us to create a centralised location for the data capability to enhance collaboration, engagement and ultimately help the organisation become more data-driven.

Objectives

01

Identify the root cause of poor engagement across the practice and revamp the ecosystem through user research and best practices.

02

Design and develop a centralised, scalable and maintainable platform that encourages community, participation and collaboration.

03

Refine and iterate on the platform based on frequent user feedback to ensure the platform solves both user and business needs.

Outcomes

220%

Achieved an average increase of 220% in event signups and participation after the first release



4/5

Achieved an average satisfaction score of 4/5 from surveys and interviews, an increase from previous releases


6 Months

Launched the Foundation hub platform with 3 successful releases over a 6 month timeframe


The Challenge

002

The Challenge

002

The Challenge

002

The lack of engagement in events and duplication of effort with projects indicated difficulties with visibility across the practice.

01

Large volume of team spaces across a variety of platforms, information scattered and difficult to find

02

Only notified of events within immediate team spaces, many users missing out due to not being apart of certain groups

03

No visibility of ongoing projects across the space had lead to multiple duplications, inefficient use of time and costly for the bank

How might we create a centralised location for the data practice to help drive engagement, collaboration and enhance visibility across the practice?

How might we create a centralised location for the data practice to help drive engagement, collaboration and enhance visibility across the practice?

Research

003

Research

003

Research

003

To understand the reason for the poor engagement and duplication my team and I conducted comprehensive research, including an as-is analysis of the existing eco-system, user interviews, usability testing, and stakeholder interviews.

Conducted user interviews with 14 users across multiple team spaces to understand the needs and frustrations across the data practice



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


Conducted multiple rounds of usability tests with 10 unique users to assess the usability of the sight and identify any missed opportunities to iterate with


Some of the research activities conducted throughout the project.

The research enabled us to get an understanding of the practice , identify the pain points experienced, why engagement was low and why duplication had become common place. We leveraged these insights to design the platform and continued our research throughout the design process iterating based on feedback to ensure the platform solved these core issues.

“Access to VODs of past events would drive usage”

“Access to VODs of past events would drive usage”

“If i was notified of events I would attend much more”

“If i was notified of events I would attend much more”

“You only find out about events after they've taken place and wonder why attendance is low”

“You only find out about events after they've taken place and wonder why attendance is low”

“You only find out about events after they've taken place and wonder why attendance is low”

“A lot of hubs (team sites) haven't been updated in months so I stopped visiting”

“A lot of hubs (team sites) haven't been updated in months so I stopped visiting”

Direct quotes from interviews and workshops

Key Features

004

Key Features

004

Key Features

004

01 Personalised Content

For the initial release, we created a feature that prompted users to choose topics of interest, this would help push relevant content specific for the user. Content with the green tag "For you" communicates to the user that this content is curated for you.

This helped users filter out irrelevant content and encourage users to engage by communicating "Hey, we think you'll like this!"

02 Events, Highlights and Notifications

Users voiced frustration at missing events due to not being notified. if you did not belong to specific distribution lists you often missed out.

To solve this we wanted to create prominent features to help users quickly find events and articles about the data practice along with a notification system to ensure that they no longer missed out on content.

To further strengthen this, we created a "resource" page that held historic posts and VODs of those events just encase they couldn't make them.