Salesforce
Jan 1, 1970
UX Designer
UX Director, UX Designer, Executive Team, VP Design
UX Research
User Testing

🔥 UX Reckoning Overview
This wasn’t just a design problem, it was a team problem.
UX was misunderstood and disconnected. I worked across silos to rebuild trust, improve collaboration, and make UX part of the product strategy.
The Problem Was Systemic. UX was siloed, reactive, and misunderstood across teams.
I Disrupted the Status Quo.I introduced new rituals, pushed for earlier UX involvement, reframed collaboration, and helped teams think differently about user-centered design.
People and Culture Shifted.UX engagement rose by 85%. Designers took initiative. Stakeholders saw UX as strategic. Silos turned into shared problem-solving.
Problem & Context
The Custom Key Initiative Plan (CKIP) serves as an important service, providing personalized plans to the organization's members, utilizing top research, tools and templates to maximize satisfaction and renewals.
Latest data suggested that members with a custom service plan have an increased retention rate by 34%
Traditionally, these plans have been developed using PowerPoint presentations, posing challenges in tracking completion rates and ensuring timely delivery. To address these issues, a project was initiated to transition CKIP creation to Salesforce. This shift aims to make it easier to manage plans and track their completion.
This case study outlines the UX research conducted to assess the feasibility and usability of building CKIPs in Salesforce compared to PowerPoint. Before joining the team, this project was already underway and considered a business priority.

Task
High-fidelity wireframes were developed using the Salesforce Lightning Design System, and a beta version was available for testing.
As a user researcher, my role encompassed various aspects from planning and recruitment to synthesis and implementation. Collaborating closely with other team members, I conducted data synthesis with another researcher to identify main themes, ultimately compiling insights into an Airtable document.
Process
Research Goals
We wanted to understand our users and how they currently build CKIPs. Will building a CKIP in Salesforce be easier for them?
What were the goals?
Identify users pain points in the current CKIP creation process.
Determine if users find building CKIPs in Salesforce easier than PowerPoint.
Identify usability issues associated with building CKIPs in Salesforce.
The research involved remote, task-based usability testing sessions lasting one hour each. Participants were asked to speak aloud their thoughts as they worked through tasks, with tests moderated by multiple note-takers.
Remote 1 Hour Interview:
Chat about role and demographic data
Prototype walkthrough
Prototype tasks with the goal to build a CKIP in Salesforce and export a final PPT
Questions and suggestions recorded
1 interviewer, 1-3 note takers per participant
Data was reviewed, synthesized, and a report was written
First round of interviews: 15 people, June 6th 2022 – June 17th 2022
Second round of interviews: 6 people, August 1st 2022 - August 7th 2022
Participant Criteria
Build CKIPs for members
Train others in building CKIPs
Have seniority with the company and product knowledge
Salesforce user
Language: English
Geography: North America
Tools used to recruit participants:
-- Outlook calendar & email
-- Sent invitations to participate in user testing
Analysis & Synthesis
Post-interview debrief:
After each session, a word document was captured of the raw dataalong with the recording of the meeting. As a team, we reconnected after each user testing session to have a discussion about what pain points we uncovered and other insights.
Process: I synthesized the data, by importing the raw notes into a FigJam while collaborating with the team. I organized the notes based on the tasks that we observed users perform, and grouped the notes based on pain points, needs, usability issues or other patterns that emerged. We had a total of 15 sessions in the first round, so we each captured our notes in FigJam to make sure we did not miss anything relevant. We grouped our data into 4 user groups: sales reps, advisors, trainers and stakeholders.
Key Learnings:
We learned that there were problems ranging from minor inconsistencies in both visual design and flow to significant obstacles to creating a CKIP.
-- Some of our findings also revealed that in the current CKIP process, users experience frustration and overwhelm due to the disjointed nature of the process, which involves switching between multiple tools to gather information, make calls, and collaborate. As a result, using PowerPoint to build a custom plan for a member can take up to 10 days, with some users managing as many as 200 members.
01
Changes
After the first round of testing, aspects of the prototype platform that cause inefficiencies were identified. Changes, making the components usable within the limitations of Salesforce were prioritized based on user pain points and ease of technical implementation.
The second round of testing aimed to assess improvements based on implemented changes.
We used the same methodology as the first round this time with a smaller group of 6 participants and we synthesized the data in the same way.


02
How my role in user testing prevented a failed SaaS launch
Impact
Value of user research:
The research that we did for this project helped the organization see the value of user testing. Stakeholders called the process “game changing”. By including stakeholders in testing in order to build a CKIP in Salesforce, we highlighted the importance of including the user in the design process.
Improved Efficiency:
Overall users in the senior advisor group reported a significant reduction in time (less than a day, compared to 10 days) required to create and manage custom service plans, thanks to standardized templates, automation, and streamlined workflows in Salesforce.


Reflections
What went well:
-- Successful implementation of user feedback into final designs proved to be a great way to launch the platform.
-- Stakeholders were involved in research and agreed of the importance of a user-centered mind set.
-- Users agreed that building a CKIP in Salesforce is much easier than building a CKIP in PowerPoint.
Challenges:
-- Some usability issues could have been accounted for if the UX team was invited to collaborate earlier into the design process. Perhaps a good way to avoid this is to work in advance by having access to the product roadmap. UX could be part of the product life cycle at a strategic level, which is a leadership issue.
-- User research takes time and the synthesis of raw data can delay the project. It would help if the UX team has a process well established (help of Ai) in order to improve efficiency.
-- Low UX maturity within the organization is a big challenge. Even with a focus on educating cross-functional teams on the importance of user research, this can take a long time.
Contents