Taking a Platform from Consumer to Enterprise

CliftonStrengths is a science-backed, Gallup talent assessment, that analyzes 34 different strengths that make up an individual. What started off as a simple assessment for individuals (a code in the back of a book) began to grow as a strategic tool amongst organizations. The opportunity presented itself and the decision was made to sunset and migrate the solo platform into Gallups larger ecosystem, and integrate the smaller product within Gallup’s larger workplace platform named Gallup Access.

Goals:
Drive organizations and larger teams to sign up for an enterprise subscription account within Access. Support individuals and managers in leading and sustaining a strengths-based culture by providing more tools and features throughout.

Key Partners:
Project Managers | Software Architects & Developers | Marketing & Communications | Digital & Content Strategy

Categorizing New Subscription Features and Functions

With the integration of the CliftonStrengths platform into our larger Gallup Access platform, the concept of the CliftonStrengths subscriptions was born. The subscription included a mix of new and existing features, so to better understand what users were getting I mapped out overall features by user type and categorized them by theme/page. I worked closely with product partners to understand what was being offered, any specific use cases to account for and to confirm that what I had put together was correct and in the right direction.

Leveraging the Power of a the Larger, More Robust Platform

The migration into the existing platform meant that I needed to take into consideration what features could be CliftonStrengths specific and what features would pull from other areas of the Gallup Access platform. I diagramed a flow that showed which screens and functions would be a part of the CliftonStrengths and which could be pulled from other parts of the Gallup Access platform. By leveraging existing functionalities, we were able to add more offering to our subscriptions and make a more desirable product.

Simplified Wireframes to Kick off Discussion Around Functionality

Now that we had the pages laid out, I began creating rapid wireframe/mock-ups to start discussing page functionality and hierarchy. The wireframes included a breakdown of the key sections & functions, order of navigation and other elements that would appear across all screens. I also brought in some new ideas like the addition of upgraded features that were visible to the user, but locked, in hopes that it could tease and encourage more upgrades within the product.

Considering All of The Use Cases

Another thing that we had to consider about the product was all of the different product types that we were offering. This included showing what each product type or role saw on the platform when they signed in. The two main use cases were a top 5 user that had the introductory product and an all 34 user that had the full product. Within those two user types, they could have a subscription which included client and teams capabilities. And within those clients, we had a few with specialized or one off reports, so we needed to consider what those users would see in their platform.

Final Dashboard Features, Community Features, & Team Features

I would say that one of the biggest differences when going form consumer to enterprise was that enterprise was much more feature focused. The additions that we made were client requests and they features really helped our sales team in selling the subscriptions. We made some improvements to the dashboard from learnings and feedback from previous user research which included keys to explain the colors, an interactive table to learn more about your strengths, and quick links to get to your reports.

What I Learned

•I learned that there are a lot about complexities around user roles and permissions and what we allow users to see. It was an interesting challenge to design for the many cases and making sure the experience was consistent but different enough that if a role changed, it didn’t seem like a mistake for a user.

•I learned that it was more challenging getting users of enterprise clients engaged with the systems because their organizations purchased the product while they may not have the familiarity or interest for it as a consumer would. It was crucial that we used email prompts to draw them in and gave them tools to interact with each other and create communities.

•I learned the challenges that come with integrating two systems. The struggle to keep them connected while making sure that their journey is seamless is something that we’re trying to solve for to this day. When we first launched, users would go to another part of the larger system and there would be no way for them to get back other than using the back button. We’ve included a lot of back links and enhancements to the navigation and dashboard to let users know to how get back to the main CliftonStrengths dashboard.