I was the main designer for a new Product Information Management (PIM) application called Entries which allows users to store, organize, maintain, and enrich products. My primary job was to enhance the user experience so that the PIM application can become a competitor in the PIM market while unifying it with our sister DAM application.
Widen: Product History feature
Background
What features should we build next?
When I first started as the designer of Entries, the application had only basic functionality. The Entries product manager identified several key missing features needed to enhance our application. We believed that this additional functionality would encourage potential clients to purchase our PIM solution. Using this list of table stake features, we decided to conduct 8 contextual inquiries with participants who use other PIM solutions.
What features should we build next?
When I first started as the designer of Entries, the application had only basic functionality. The Entries product manager identified several key missing features needed to enhance our application. We believed that this additional functionality would encourage potential clients to purchase our PIM solution. Using this list of table stake features, we decided to conduct 8 contextual inquiries with participants who use other PIM solutions.
Contextual inquiry
We used interviews to help identify the biggest user pain points.
The goal of these interviews was to understand why these table stake features were vital for PIM functionality and which among them were most likely to attract new PIM clients.
We used interviews to help identify the biggest user pain points.
The goal of these interviews was to understand why these table stake features were vital for PIM functionality and which among them were most likely to attract new PIM clients.
Results
Results showed that having a history log was a "must-have" feature.
Multiple participants expressed concerns about product recalls or auditing situations where accurate and detailed product histories are critical to mitigating potential legal issues.
Results showed that having a history log was a "must-have" feature.
Multiple participants expressed concerns about product recalls or auditing situations where accurate and detailed product histories are critical to mitigating potential legal issues.
While these use cases were infrequent compared to other table stake features discussed during these interviews, we concluded that the product history feature had the highest user value and would be the next feature we developed.
Notes and results from a contextual inquiry.
User persona for Cary.
User persona
Cary was the person who would require the history feature.
From the contextual inquiry we identified Cary as the persona who is verifying product information in the PIM application.
The contextual inquiry also helped us determine that Cary will need to know:
• What the change was for each product edit
• Who changed the information
• When the change occurred
Cary was the person who would require the history feature.
From the contextual inquiry we identified Cary as the persona who is verifying product information in the PIM application.
The contextual inquiry also helped us determine that Cary will need to know:
• What the change was for each product edit
• Who changed the information
• When the change occurred
User testing and prototype
Testing is vital to ensure we captured feature requirements.
I then designed a prototype that accounted for all these requirements. We did unmoderated user testing with 5 Clara participants to ensure:
• Users' needs for product history were met
• Users understood how to navigate to the feature
• Users could locate the information in the history table
• Users understood the term "attribute’s history page"
Results
Results showed design worked well for Cary personas.
Results showed that the prototype was easy to use and, with a few tweaks, would meet users' needs for the product history feature.
Testing is vital to ensure we captured feature requirements.
I then designed a prototype that accounted for all these requirements. We did unmoderated user testing with 5 Clara participants to ensure:
• Users' needs for product history were met
• Users understood how to navigate to the feature
• Users could locate the information in the history table
• Users understood the term "attribute’s history page"
Results
Results showed design worked well for Cary personas.
Results showed that the prototype was easy to use and, with a few tweaks, would meet users' needs for the product history feature.
Top image is of a participant during user testing.
Bottom image is a summary from user testing.
Design specs used to help development create feature.
Development
I worked with the development team to ensure design handoff was smooth.
I worked with the product manager and development teams to define the scope of the first iteration which included meeting WCAG AA standards for accessibility, matching our branding styles, and providing key requirements identified during the research phase.
I worked with the development team to ensure design handoff was smooth.
I worked with the product manager and development teams to define the scope of the first iteration which included meeting WCAG AA standards for accessibility, matching our branding styles, and providing key requirements identified during the research phase.
Current status
User data post-release proved the newly designed feature was successful.
This feature is now released to customers and was tested post-release. The results continue to show a need for search and sorting enhancements, but have otherwise met all user expectations and have led new clients to purchase our PIM solution.
User data post-release proved the newly designed feature was successful.
This feature is now released to customers and was tested post-release. The results continue to show a need for search and sorting enhancements, but have otherwise met all user expectations and have led new clients to purchase our PIM solution.
Final design for product history feature in our PIM solution.