Umbel Design Sprint
Popularized by Google Ventures, it’s a 5 day process that uses design thinking to reduce risk of failure when bringing a new product, service or a feature to the market. Each day consists of a specific set of goals to accomplish with the final day used for testing a prototype with your users.
We needed a way to show the value of the Umbel product to our users more easily and potentially all in one place. We wanted to make sure to show how many different parts of Umbel can show ROI, both from a financial standpoint of how much money we have helped them make as well as how the data they collect from their fans is valuable as well because it helps them know who their fans are and what they like. We thought we might want to test some sort of dashboard, but were not sure exactly would be the most impactful information to display or how to display it.
We had to come up with a mission statement to guide us as we went through the process. It was “We help clients understand their data to encourage action that drives measurable value over time.”
We ended up testing a rough dashboard view focusing on our Sports/Entertainment clients to see which parts of it would appeal the most to users in those industries. We made all the areas the same size to try to minimize any influence visual prominence might have and shifted the squares around each time so they weren’t always in the same place aid in placement not being the key driver for things they liked or didn’t like.
We tested with 7 users having them walk and talk through the static dashboard based around what they thought they were seeing, what appealed the most to them, what didn’t appeal to them, etc. The middle 3 widgets and the “Opportunities” widget appealed the most to our users by far.
I began to ideate more on the concepts for a dashboard with only those elements most liked by users from Design Sprint testing sessions. After a few days of ideating, it was clear we needed to create aggregate data for two of those sections on their pages in the app before we could successfully summarize that data on a dashboard view. Not to mention, without first summarizing and testing data on those two pages, we would have no way to have a baseline for recommending actions like we provided in the “Opportunities” widget of the mock dashboard tests. It was fantastic to see the Design Sprint yield a direction towards practical and impactful features within such a short amount of time.