Project to strengthen the experience from the ground up.
Centuri is a platform that helps companies manage, collaborate, and share information. They have clients in life science, healthcare, food, and manufacturing.
The goal was to find out users' needs and redesign the core journey as part of the the launch of their latest systemversion. This project spanned 6 months from research, conceptualization, testing to Hi-fi prototypes.
The Team
Me and Niki Parvaresh as the UX Designers.
Working closely with CCO and developers.
The goal
Our goal is to implement a standardized design that users can easily recognize, reducing the learning curve for new users while enhancing Centuri's marketability. The new design should be intuitive, efficient, and visually appealing.
This was the goal we formulated together with Centuri.
Initial discovery research
Started by interviewing 13 people at Centuri and 13 users from 6 different clients, to understand their experience. I asked questions like: How do you use Centuri? What problems do you encounter? How do you solve the problems? What do you like? What can be improved? Any other products that you like using? How would you change Centuri?
From the interviews I categorized 9 themes and 14 insights out of them these are some of the high level findings:
👀
Inconsistent menu structure makes so users have to interpret similar pages differently.
🔎
No clear main search function, with multiple search options that behave inconsistently.
🏃🏻♀️➡️
Creating a document requires too many steps, with no clear way to save and exit or track progress.
⚠
Inconsistent naming of buttons and functions, with duplicate labels for different actions and technical language.
📱
Lacks responsive design, problem when many users on use pads or phones to read documents.
📜
Dated design which has a low recognition that confuses users.
Workshop
The system is big and complex, and we had many areas of improvement. We showed a series of wireframes of core paths to 4 people at Centuri and had them write what was good, bad and ideas of how to improve certain areas then vote on the most important point for each main flow.
Usertesting A/B designs
Through a Lightning Decision Jam and subsequent storyboarding, we developed two potential solution sketches. The workshop generated differing views on what would work best for the main flow, so we created A/B versions of the following pages, which we tested with users (3 internal stakeholders and 7 external users):
-
Startpage
-
Documents and filters
-
Search
-
Create new
Startpage
Our recommendation based on feedback is a left-side icon-and-text menu, with separate Notifications and Profile buttons, To-do as default, and customizable placement plus selectable widgets so users can tailor their home screen.
.png)
Variant A
Variant B
Documents and filters
Merge agreements, forms, and documents into a “Files” module. Filters sit above the list and are expandable (variant A). Include an expandable detail view with title, owner, registration number, description, and metadata chips (new, confidentiality, attachment), plus consider valid dates, status, workflow stage, and file type.
%201.png)
Variant A
Variant B
Search
Keep the search experience as in variant A, where users land on a general search results view not tied to a specific module. “Search within filter” is a nice-to-have but not essential. It can be useful to search within filter categories, but it should not act as a competing free-text search against the main search bar.
Variant A
Variant B
Create new
Keep the “create new” button in the left menu as in variant A, labeled “new.” Keep the tag filter and add search within it. Let customers choose between two flows: variant B for complex, data-heavy use cases and variant A for simpler, faster use.
Variant B
Variant A
Key takeaways
I am proud of the work me and my team did for this project! At first, the task was quite overwhelming, but we managed to get a solid focus that led to a reliable solution. Through the process, I gained a lot of valuable lessons both about our way of working and the solution.
😕
🍭
❌
Some users felt insecure about sharing their private data when not knowing the purpose of sharing data. However, the majority did not have a problem sharing it knowing the meaning.
Users crave feedback in every step. Confirmation of their actions comforts the users in the process.
A sprint is not always the answer. Since we have had a lot of short projects, the google sprint has been handy. But we now had a longer time than usual. I realized that the sprint is convenient for quick projects but is not the best tool in every project.