Designing to help manipulate data for better comparison and consumption

Skills : Product design, iterative design, facilitating brainstorming sessions, UI design

This was one of the projects that had a simple task to do on the user’s end but wasn’t simple enough to execute keeping user’s simplicity in mind.

This is a gif of the final iteration. It’s supposed to be moving. If it’s not moving please hover your mouse over it or click on it. I promise it will move.

This is a gif of the final iteration. It’s supposed to be moving. If it’s not moving please hover your mouse over it or click on it. I promise it will move.

Problem Discovery

Most users on Crux would also download CSV files of data and then use it on excel to transform it to the way they want to use it. They were simple transformations like changing the order of the columns or pivoting them. But this falls shorts when you take into account that our users also want to click on most numbers and further analyse the whole story about why they are the way they are.

There are many types of questions that our users ask on our ask bar but it’s not always conducive to the type of comparison that they’re trying to accomplish. And that’s how this project started.

Final solution

Untitled (18).gif

The reason it’s two clicks before getting to the pivot to compare window is because there might be other settings that we might want to add and hence making it easier scale.

As you can see measure is already pivoted as an initial state, that is because we consider

when it is a column - it is un-pivoted

when it is a row - it is pivoted

And since all “measures” such as Dollar sales, Unit sales are laid out in a row, they are considered to be pivoted.

Allowing pivoting from header of a column

ezgif-1-50f0775868.gif

I came up with this not always might a user map transforming a particular as “settings”

We also limited the number of pivoted columns to be 3 because after that the nesting gets really complicated and the horizontal scroll gets too much to the point that the initial aim to “compare” is lost. For now, we decided to do this and see how it goes.

Use cases/ Personas