Revamp of a sales enablement platform to set growth direction

Overview

Case study: revamping the SalesHood sales enablement platform through user-centered research, personas, JTBDs, and a new visual design language to set growth direction.

My role

Product Designer

Company

SalesHood

Timeline

2020–2021

#user-centered-design#in-depth-user-interviews#persona#jtbds#theme-analysis#visual-designs#illustration#prototyping-with-protopie#after-effects

The design team proposed a thorough revamp of the "SalesHood" platform, a corporate sales enablement tool. Following a user-centric approach, we employed methods such as user interviews, competitor analysis, and persona development. This led to the creation of new features and a comprehensive restructuring of the platform. The redesigned platform now includes many new features. The final design was showcased using prototypes and promotional videos to Board of Director.

Overview

Final DesignLink to section

The entire platform was redesigned using a new visual design language. A design system was also implemented to maintain consistency across the platform. The number of improvements made is too numerous to count.

Context

Problems and ContextLink to section

In 2019, the team faced challenges in enhancing two key elements of the platform, Huddle and Path. These elements were rigid and complex, making it hard to modify them. Customer needs often led to creating patches or workarounds, like the new Path type - Dynamic Due date, instead of substantial improvements.

"This software is great for serving up evergreen content to your employees, but when trying to manage learning content that needs to be updated from time to time, it can prove very difficult if you have used it as a way to store your content."

A snapshot of two core objects in our platform: Path & Huddle

SalesHood platform is losing customers and revenue due to complicated core object logics, lack of flexibility for different use cases, outdated UX design, and inconsistent user interface elements leading to a messy platform.

The initial designs of a core feature (Huddle)

Goals

GoalsLink to section

Transform the platform into a versatile, user-centric tool that promotes independent learning and enhanced interaction

1

Tailoring to user needs with a flexible IA — creating a versatile product that caters to the unique needs and use cases of each customer.

2

Ensuring consistency in platform concepts — enhancing existing features and ensuring consistency among platform concepts.

3

Enhancing visibility of sample projects — empowering users to develop personalized learning applications independently, eliminating the need for customer service.

4

Dynamic content and data management — improving the overall interaction and visual design of the platform.
The framework we follow to redesign based on the existing product

Research

ResearchLink to section

Comprehensive user understanding through multi-channel feedback and analysis

We've dedicated considerable time and effort to understanding our clients. We've learned about their everyday challenges, how they use our platform, the issues they want to address, and their pressure points both within and outside Saleshood. This understanding has come from going through tickets, customer interviews, questionaires, NPS feedback, and more.

User complaints through NPS survey

Through analyzing hundreds of customer quotes and conducting interviews with 14 individuals from various sectors, we gained a clear understanding of our users' challenges.

"You need to define what coaching means"

"SalesHood is very slow. It takes me more than 30 seconds to find a file"

"UI is confusing for somebody looking for sales tool versus learning content"

"Very difficult to find things"

"If that person is a reader, I will give content, if that person is watcher, I tell them to rewatch video"

"Team dashboard currently's just a step up of sales sheet in an email"

Records of user interviews and their segments

Utilizing "Jobs to be Done" for Effective User Story Development

The team leveraged the "Jobs to be Done" method for crafting user stories, enhancing their effectiveness by incorporating specific contexts and pain points from interviews. User stories were divided among the team members for four key personas and categorized with tags in Notion for easy identification.

Mapping JTBDS with Persona and other categories to have an overview

Solution

SolutionsLink to section

Iteratively brainstorm solutions for existing conceptual models.

Using user stories, insights, and interviews, we brainstormed from a vague concept to a fully developed justification. We focused on diagramming, structuring models, and important use cases. This allowed us to test ideas, get early feedback, and iterate design criteria. After various iterations, the team agreed on the direction.

A lot of diagrams were made to propose new structures, logics of concepts within platform

Based on the list of stories and concepts we created, we held several brainstorming sessions to name the key features. We then sorted these features into their respective concept folders. Features marked in blue are existing ones in the current product that need improvement. Purple features originate from insights into NPS pain points, and green features are derived from interviews.

New features, Existing features were organized into different categories and marked with different colors based on priority

We iteratively sketched user flows and wireframes for each feature and screen using Whimsical until we finalized and logically organized these wireframes.

So many wireframes, so little time to do…

Seeking for a new visual direction by using style tiles method

The visual design involved a detailed process to create a fresh, user-friendly interface. The new design responded to customer complaints about the previous interface, focusing on dynamism, color, abstract geometric illustrations, balanced iconography, and ease of use.

Collecting references from Dribbble, Behance, we made an initial moodboard
From the vague moodboard, we went toward with initial style tiles, establishing a direct connection with actual UI elements
Finalized style tile, which laid the foundation for our design system afterward

Final Designs

Final DesignsLink to section

The Challenging and Rewarding Journey of Redesigning SalesHood

Homepage

The homepage is designed to engage and inspire users with relevant updates and facts. It's crucial to offer users the ability to explore and personalize content, fostering active learning. Participants are encouraged to join relevant topics and courses independently, promoting active engagement and skill development.

Curriculum and Session

SalesHood's "Template and Events" feature was renamed to "Curriculum and Session". Coaches create the curriculum, and Managers use it to plan their own learning sessions.

New Huddle page

Huddle, our platform's core object, contains various learning activity modules. We refined the structure from many types to four distinct modules: reading, video, pitch, and exercise. This made module creation simpler and more flexible.

New feature: Analytics and Huddle Module builder

The new analytics feature will gather data from all programs to provide users with visual insights on their progress and learning outcomes, also a totally new experience of building a module instead of conventional forms.

New feature: Learning Dashboard

Based on user input, we created customizable dashboards for efficient access to key information and activities.

New feature: Discussion Hub

The Discussion Hub is a space for users to share ideas, seek support, and contribute to training, fostering increased engagement and active participation in the platform.

Outcomes

OutcomesLink to section

Strategic impact

North star

The redesign became the pivotal foundational research for the entire company, influencing the board of directors and shaping the product roadmap.

Visual language

Established

A new design language was created for SalesHood and promptly incorporated into the product roadmap.

More case studies

AISAP · 2026

Two AI agents, one pattern

Designed two AI agents on SAP Business Network for Sapphire 2026 — and set the pattern the team now uses for every transaction-document agent that follows.

Read case study