Feature Audit
Project Case Study :: Research
Case Study Overview
This case study focuses on artifacts created for aligning features and functionalities between the Basic platform and the Premium Platform.
Over the years, the two platforms didn’t have a clear strategy against each other. There were a lot of similar features to what extent hadn’t been documented before. It was also a good opportunity to test which versions would perform better.
Another element of this research was accounting for the three user roles and privileges.
Goals
- Determine what current features and functionalities exist in the platforms.
- What features and functionalities do we want to keep and remove for the new built.
- Which features and functionalities outperform the other platform.
- Determine priority of features and functionalities.
- Purpose new features and functionalities.
Timeline
- Platform Documentions / 2 weeks
- Gap Analysis / 1 week
Terms to Remember
Customers vs Clients
- Customers are self-help users that purchase the product through our e-commerce store. They generally have no direct communication or business agreements with Gallup OR had one in the past but have chosen to downgrade.
- Clients were customers that have gone through the marketing funnel that now have a relationship with the Practice and have client contracts with Gallup. They started on the Basic platform and wanted more features and services from the Premium platform.
Basic vs Premium
- Basic refers to the self-help platform that institutions are first exposed to the product through our e-commerce store. This applies to customer users primarily.
- Premium refers to the custom centralized platform that institutions purchase through a contract. This applies only to client users.
This graph represents where clients and customers fall between our measurements of product usage. The black square (upper-right) represents where our best clients (and sometimes consumers) fall under.
The Audit :: Too Big to Fail
Breaking down the platforms in such a way gave clarity to how similar the platforms were.
An assumption could be that the Practice thought to make them similar so the user experience was close to each other. However, the actual experiences of the features and functionalities behaved very differently, which makes the effort moot.
I can’t tell you how nuts the engineers went over these visuals. They are more geeked out by these feature maps than the actual mockups!
