4
2
Enhancing a dashboard usability and adding essential information
B2B e-commerce and reservations SaaS
Team:
Platforms
Web
Tools
Figma, NativeForms, Useberry, Intercom
Outcomes
Challenge
The Today Page had been built without a plan. As the platform had scaled up and added different types of events, org administrators were frustrated they couldn't get this information all in one place.
This particular page had been created as part of an "Innovation day" and its use case was never carefully considered. Over time however, users had come to use it as a go-to resource for their everyday operations. As a result of it's considered use, many requests and complaints had come in from users wishing the page had the information they'd find most helpful.
Previously, the page listed just one kind of site information: Activities (scheduled recurring events). As the platform had added the ability to sell private lessons and rentals, this information needed to be easily accessible, for org administrators to have a "one-stop-shop" for their site management.
Goals
Verify we're solving the right problem(s) through user research.
I conducted user testing (surveys through the product) to ensure we uncovered and addressed unmet needs. I synthesized the findings into an affinity map and led a feasibility and prioritization workshop with the dev team to identify low-hanging fruit we could include, and which user requests we'd have to de-prioritize. I then designed and tested two prototypes through the product, using Intercomm and a live prototype. The results validated our choice of solutions to be the best for the users.
Solutions
Prototype and usability testing, on both internal stakeholders and real-world clients.
Once we'd determined the highest value content to add to the page, I created prototype versions of side-by-side and progressive disclosure (tabs) prototypes and tested them side-by-side. Throughout the investigation, the company had shifted priorities aggressively and by the time the team had time to get to this improvement, bandwidth was reduced. I made the decision to guide the team towards the cards version but wanted to validate this on real-world users. I ran a usability test and the results aligned with our chosen version.
Design highlights:
Verified Needs
User Research
Tools:
Methodology:
Prioritization
Affinity mapping:
MVP selected features
Design presentation to internal stakeholders
Mid-fidelity design presentation:
Cards version
Tabs version
Scope change
Pared-down MVP:
Final MVP version released to production
Trust, but verify
Prototype testing:
