How a Panel Redesign Helped Sales and Customer Success Teams Avoid Critical Setup Errors

I redesigned a complex admin tool used daily by Sales and Customer Success teams to configure enterprise client settings. The legacy system made critical errors easy. I rebuilt it around clarity, feedback, and safer workflows, reducing support needs and user stress.

MY ROLE ON THE PROJECT

I led product design from early discovery to launch.


I worked closely with Product, Sales, CSM, and Data teams to:

  • Clarify the problem we were solving

  • Map how sales reps actually worked

  • Define what “good” recommendations looked like

  • Design the end-to-end experience

I owned the UX strategy, interaction design, and prototyping.

Problem

A tool used daily for enterprise setup was becoming a liability.

Sales and Success teams used the Enterprise Panel to configure accounts, assign licenses, and turn features on and off. But the interface had grown unclear and risky. 

People weren’t sure what actions would do, and one wrong click could block content access or misassign a license pool for a client.

Controls were scattered around and hidden under obscure tab labels, there was no preview, no confirmation, and no clear structure. As a result Confidence was low, and mistakes were common.

BEFORE THE REDESIGN

Business complexity was rising fast:

The company was moving from a simple, flat pricing model to a tiered system.
The company was moving from a simple, flat pricing model to a tiered system.
Portfolios expanded from 2 (Tech and Marketing) to many, to personalise offers.
Portfolios expanded from 2 (Tech and Marketing) to many, to personalise offers.
Legacy clients, exceptions, and contract-specific setups all needed to coexist.

Meanwhile, new CSMs needed to configure accounts on day one, but had no documentation or structured guidance. Every action felt potentially destructive, and risky.

What I found (through interviews & task-based observation)

New users were unsure what they were even allowed to do.

They didn’t know which toggles mattered, what license models meant, or whether clicking a button would break something.

Quote from a Sales Rep
Quote from a Sales Rep

Experienced users relied on workarounds.

Even power users avoided parts of the interface and trained new hires to proceed with caution.

Quote from a Sales Rep
Quote from a Sales Rep

Learning the panel took weeks or even months.

There was no structured onboarding, and much of the tool required institutional knowledge to use correctly.

Quote from a Sales Rep
Quote from a Sales Rep

How might we make internal setups feel safer and more predictable in a changing system?

I approached this by first mapping out what made the current experience risky. Through interviews and live task observation with both new and experienced users, I uncovered a pattern: people weren’t confused by the number of features—they were afraid of making a mistake.

Some users didn’t know what they were allowed to do. Others didn’t trust what would happen when they clicked a button. And almost everyone relied on memory, peer support, or workarounds like Ctrl+F to get through critical tasks.

From there, I restructured the panel to reduce ambiguity and surface consequences early, without slowing down the workflow too much. The redesign focused on three things:

Rebuilding the information architecture to address real, current problems, instead of stacking new logic on top of existing UX debt.
Rebuilding the information architecture to address real, current problems, instead of stacking new logic on top of existing UX debt.
Making feature toggles and license models safer and more explicit
Making feature toggles and license models safer and more explicit
Supporting confident decisions through clearer feedback and guardrails
Supporting confident decisions through clearer feedback and guardrails

Legacy clients support

To ensure legacy clients who joined under an all-you-can-eat contract felt supported during the pricing redesign, we designed flexible, custom feature-panel settings that allow plans to be upgraded or downgraded at any time as needs evolve.

Early outcome

The redesign has only been live for a few months, but early signs point to meaningful improvements:

New CSMs are reporting higher confidence, earlier.

While onboarding still takes time, some recent hires say they feel comfortable navigating the panel weeks ahead of where others typically were.

New CSMs are reporting higher confidence, earlier.

While onboarding still takes time, some recent hires say they feel comfortable navigating the panel weeks ahead of where others typically were.

Fewer support tickets are tied to misconfigurations.

Early tracking suggests a ~15% drop in error-related tickets linked to setup mistakes. A promising sign that the new structure and clearer UI are reducing confusion and risk.

These early outcomes suggest the redesign is not just more usable: it’s starting to build trust, reduce support needs, and prevent setup errors.

“I don’t feel like I need to double-check every click anymore — it’s more intuitive now.”

New CSM (informal post-launch feedback)

What I Learned

Internal tools often suffer from a lack of design ownership, even when the stakes are high. 

This project reinforced how important it is to:

  • Design for ambiguity, not just for edge cases

  • Make mental models visible in the UI

  • Balance speed with safety in internal tools

Check out more projects

UI of AI assistant illustrating chat and and text selection

Scaling personalized learning through AI

Enterprise learning programs relied heavily on admins manually curating and assigning training, making personalization difficult to scale. To reduce dependency while improving learner engagement, we leveraged existing AI infrastructure to help learners generate personalized development paths aligned with their career goals, skills, and interests. The initiative transformed learning discovery from a largely admin-driven workflow into a scalable self-service experience.

63% adoption of AI-generated learning programs

70% retention on AI-generated learning paths vs. 24% on content library enrollments

UI of AI assistant illustrating chat and and text selection

What an AI sales tool taught me about product adoption

Designed an AI tool to help sales reps create learning recommendations faster and reduce reliance on SMEs. Early adoption was promising, but over time the project revealed bigger challenges around trust, workflows, and product adoption.

Time from lead to first offer dropped

Significant reduction in SME involvement

Revealed how AI adoption depends on trust, existing workflows, and user behavior

UI of AI assistant illustrating chat and and text selection

How I've helped QA users learn more confidently with an AI assistant.

I led the end-to-end design of Ela, QA’s AI-powered learning assistant, transforming an inherited prototype into a trusted and scalable product in just two months. Designed to reduce friction and support learning momentum, Ela is now adopted by 80+ client accounts, holds a 4.5/5 satisfaction score, and has influenced the development of new AI capabilities across the platform.

4.5/5 Avg. Rating

1,178 Client Accounts

+34% Adoption Growth

Sidebar of an assignment displayed on top of a lesson

How I redesigned navigation to keep learners on track.

I designed a universal sidebar to unify all content types during a major content merger. Learners can now track their progress without leaving the lesson, reducing distractions.

53% drop in users exiting lessons to track progress

28% reduction in fullscreen toggling to study

Marathon's user dashboard and result page

How I gamified learning at Cloud Academy boosting user motivation and MoM cashflow.

I designed a 3-month challenge that increased engagement, reduced churn, and boosted cashflow. 20% of participants stayed active three months after—well beyond typical subscription periods.

+18% increase in MoM upfront cashflow

1,178 Client Accounts

+34% Adoption Growth