Specializing in Amazon optimization consulting, we needed a proprietary tool to determine the growth potential of products sold on Amazon for their clients.
To increase internal workflow efficiencies and provide actionable insights, we needed to build a web-based application for automating Velocity’s proprietary algorithm.
Discovery & Definition
User Research
Through stakeholder and user interviews, we identified three core personas and what they needed from the application to be successful.
User Epics & Requirements
We determined our epics by focusing on primary user goals and defining the tasks and steps needed to complete each.
Referencing user epics and mapping out high-level flows, we gathered requirements serving as a living document throughout the project.
ideation
With a better understanding of the team’s workflow and needs, we began sketching different approaches . After compiling the best of our ideas, we defined the ideal user flow.
Prototyping & User Testing
Using Invision, we were able to build a prototype for a scripted study of the product. We began focusing on the three core views of the user interface – admin dashboard, PHS input form and analytics dashboard. With the study concentrated on specific flows, we defined the usability metrics as the users ability to perform the necessary tasks, the time a task requires, the error rate and users' subjective satisfaction.
Findings:
Admin Dashboard
Users thought “Re-run” meant re-run entire ASIN
Users tripped up on status definitions
Users immediately searched ASINs on admin dashboard when asked to create new PHS
Analytics Dashboard
“Run ASIN” vs “Create PHS” was confusing and couldn’t figure out the difference
Users immediately expected they needed to fill out entire form
Users expected to be able to create a new PHS on admin dashboard and fumbled looking for the form
PHS Form
“Run ASIN” vs “Create PHS” was confusing and couldn’t figure out the difference
Users immediately expected they needed to fill out entire form
Users expected to be able to create a new PHS on admin dashboard and fumbled looking for the form
Design
Implementation
Working in 10-day sprints, we are continuing the development for the first phase of the tool and will begin rolling out the tool to the internal team and select clients within the coming months.
With a switch in development teams mid-project, this project also reiterated the importance of keeping detailed documentation to distribute across different teams. As well as the value of starting with your optimal design then scaling back, allowing the team to account for factors necessary for long-term scalability early on.