Scovey
Manage a fast and intuitive data catelog platform. Created for data teams to help organize their data.
My Contributions
Brand Identity
Concept Ideation
Prototyping
User Research
Brand Research
Mockup
Design Specifications
Wireframing
End-to-end Flows
My Role
Solo UX &
UI Designer
Tools Used
Sketch App
Adobe Illustrator
invision app
Figma
Ton of Coffee
The Team
1 UX/UI Designer
3 Developers
1 Project Manager
Duration
4 Week Sprint
3 Weeks UX
1 Week UI
Scovey is an open source software to help with data management and visualization. Social features such as comments are added to help mark data that requires edits or praise.
Credits:
For this project I was a UI/UX Designer who:
-
Produced low to high-fidelity wireframes
-
Performed a user testing session
-
Construct a prototype.
The Problem
How can Scovey offer data organization that's quick and effortless?
I need to produce a fast and intuitive way to upload data.
My Role
As the sole UX/UI designer, I devised a strategy for the overall experience, upgraded Scovey interface, and enhanced its features.
The Goals
-
A flow to point A to point B of adding a dataset
-
Create a team/groups page so users are encouraged to share datasets with each other.
-
Update the interface to enhance overall usability during iterate phase.
Research Stage
I. The Design Challenge
How can we offer a fast and straightforward way to organize data and help users create
dialog edit and peer-review data in one place?
2. Users & Interviews
My PM wanted to design Scovey for a small group of people internally and then make it open sourced.
​
My research consisted sending out surveys to analyze Users in data analytics at Samtec. I gathered their comments using a card sorting exercise in order to identify common themes among the respondents.
Insight #1
New Team Page
Privacy is important for the team to be able to share internal datasets securely.
Result: Reduce nonessential input fields to make adding data more intuitive.
Insight #2
Quick way to add data
Users do not want any hassle while adding their data; that's the whole point of cataloging datasets.
Result: Straight path to quickly get to their goals by having the create btn in view and prominent.
Insight #3
Data conversations
Users find it useful having a discussion board where they can have regular and substantive conversations about the data displayed. The discussion board provides user-to-user constructive criticism to continuously improve their datasets.
Results: Add comment sections to dataset page to see what other users are saying about the data. Kind of like what youtube comment section.
Ideate
Turning scribbles into prototypes
With all my research and conclusions in mind, I started building the dashboard. Beginning with some rough sketches on paper, I drew up ideas on the whiteboard, sought feedback from my teammates and then brought the final ideations to life in sketch app.
Prototype
Does this actually work?
I conducted five user testing sessions as well as tree testing sessions to ensure that the information architecture of the Dashboard was intuitive and functional.
Change #1
+ Btn in navigation
Previously, it took users two clicks to add a Dataset, Discussion, or Analysis, so, I placed the "+" Btn beside each option to eliminate a click and to make navigation more efficient.
Change #2
One column into two
During testing, Users requested to see their datasets and their colleagues' (featured) datasets listed in the first column of the Dashboard. Less important information, such as "My Feed", was moved lower on the Dashboard, and i moved other information, such as status graphs, into the second column.
​
This new layout immediately directed users' eyes to the most important information.
Describe your image
Describe your image
Describe your image
Change #3
New Team Page
I added a page to hold all team data in a central location. Users could see their team members' names and the ongoing dialogues. The team admin could add daily messages to help the team grow their datasets.
Reiterate
Main issues to minor issues
Once the core issues were solved and Users could navigate the prototype, I proceeded to iterate remaining issues to enhance the experience of Scovey.
Get started
Clear and simple onboarding
At Scovey's onset, there was no option to sign up to create an account. Because we were introducing new Users to Scovey, we added a simple onboarding functionality.
Feed Section
Updated feed
The feed section shows an ongoing stream of actions and updates performed by the Users, their teammates, and their followers.
Through a card sorting exercise, I structured the layout of the feed to identify what was most important in this section. Overall, Users has a positive response to the design and no further enhancements had to be made to the feed section.
Dataset page
2nd column section
To eliminate the need for scrolling, I added a second column to the right side of the page that contained less important information, such as File Update Overview, Tags, and Sources. The most pertinent information (e.g., Comments) remained in the first column.
Other updates to note is that i added primary button to download files since Users couldn't quickly see where the button was before, it was a simple underline text.
Final Thoughts
In the end, the team was proud of the new layout design for the dashboard we’d created 50+ screens. With another 2 weeeks to refine some of the user flows further it could have been really exceptional prototype. Our users were very pleased with the end results and was enthusiastic about using a product that quickly helped managed their dataset.