Information Architecture

Big Data.

Overview

What I Did

This project was for Unifi Software, a big data application for enterprises like Visa, Nike and Disney.
The main goal for this story was to simplify the flow for the creation of datasets.

I was the Product Design Lead for this feature and worked in collaboration with a design team: the Director of Engineering, a UX Designer and a Visual Designer.

I also collaborated with cross-functional teams for final approval and release.

The Need

This story came from working with a couple Project Managers that had a lot of experience with big data. Based on their feedback, we created the story to simplify the flow and integrate all data creation elements in one.


In big data and in our application we have separate pages for adapters, data stores, data sources and data sets. For data set creation there was no easy path on where to start, continue or end.


The user had to go to multiple pages to accomplish one task
because the flow was spread within multiple pages and site areas.

Process

I created multiple solutions using hand drawn sketches and hi-fidelity mock-ups with flows, interactions and visuals using Sketch.
I also created animations for engineers using Principle and Flinto to explain behaviors, timings and transitions.

The key elements redesigned and used were:

  1. The removal of modals

  2. The use of the side panels or drawers for a step-to-step process

  3. Site architecture and flows for easier use

  4. The use of animations to communicate better with users

Main Screens

Starting Point

Analyzed the creation flows for adapters, data stores, data sources and data sets and the relationships with each other. Main tools used for data were Tableau, Power BI and Alation. For animations and behaviors I researched GDrive and Dribble.

Creation pages for Data Sets, Data Sources and Data Stores.

Lessons Learned

  1. Go deeper into the user needs and tasks by sitting with multiple users to see them perform the task you are designing for

  2. Go deeper into understanding how a very technical tool works by surrounding yourself with expertise, in this case for big data

  3. Be clear when sorting what works, what can be changed and what should be changed and why

User Flow

Tested the new flow and interactions with 10 users during a training session. Big data is abstract and some times difficult to grasp if you are not a data scientist. The blade approach was a simpler and better to understand. Users were able to both create and edit objects easier and faster. Not only the flow improved but the site architecture became more organized and concise.

Previous
Previous

Feed

Next
Next

Navigation