CASE STUDIES

Case Review for CS Managers

Support Hub

​





​CASE STUDY #1
​Case Review Flow for CS Managers

Role
Senior Product Designer (research + strategy + end-to-end UX)

Users
Customer Support (CS) Managers at enterprise IT organizations

Problem Statement
SupportLogic rolled out the new Case Review feature in beta to a subset of clients. Adoption was unexpectedly high, but usage surfaced a critical friction: CS managers were spending excessive time per review, struggling to navigate between case details and evaluation inputs, and asking for enhancements to make the workflow reliable at scale. The challenge was to improve efficiency and clarity without expanding engineering scope, since the feature was already mid-flight.

Approach
1) Defined shared understanding of users and success.
Although the startup had strong client relationships, personas were not formally defined. I introduced lightweight persona profiles to align product, design, and engineering around primary vs. secondary users, the review “feedback” stage in the journey, and the outcomes that mattered (speed, consistency, auditability). I highlighted only the persona attributes relevant to reviews to keep the team focused and reduce debate.

2) Established evidence quickly in a fast-moving environment.
I audited the backlog and existing research repository to avoid duplicating work, then identified gaps and unknowns (especially given that both the PM and I were new to the team). To close those gaps, I led three 1-hour sessions with beta clients (primary persona fit), combining:

• open-ended interview questions to capture workflow reality, and
• a short usability walkthrough of the beta experience to pinpoint friction in-context.

This gave us immediate clarity on why the feature was adopted and where it was failing.

Strategy & Solution
3) Translated research into priorities and a plan.
I synthesized findings into a problem list, partnered with the PM to prioritize, and converted the priority set into a clear flow narrative. From there, I created low-fidelity “pencil” wireframes to drive decision-making early—so we didn’t waste time polishing multiple directions.

4) Proposed a scalable interaction model that reduced context switching.
I designed a streamlined one-screen layout with independently scrollable sections so reviewers could move between case context and evaluation without losing place. I added mechanisms for:

• commenting, tagging, and flagging case elements,
• navigating across flagged items and comments,
• free-text justification per review section, and
• saving drafts / resuming reviews.

The goal wasn’t “more features”—it was a workflow that supports consistent decisions under time pressure.

Prototyping and Usability Testing
We reviewed some of the wireframes with engineers who showed concerns about the solution, so I constructed a prototype to eliminate those concerns. This prototype explicitly proved the solution, and I refined the flow in high fidelity, which I presented to internal stakeholders first, followed by three 30-minute usability sessions with users. While some minor adjustments pertained to icon selection and wording, the overall design was validated and got positive feedback.

Final Design and Visual Elements
The next step involved annotating the design file, generating development tickets to track requested changes, and delivering them to the development team. The design required minimal alterations by leveraging existing components, primarily focused on layout adjustments and a few updates/extensions to existing elements. This strategic approach conserved significant developer time and expedited the implementation process.

​Implementation and Development
I actively monitored and supported the development process. The implementation proceeded smoothly and efficiently, allowing for the inclusion of all desired features.

Evaluation and Outcomes
The refined flow yielded notable benefits. CS managers now enjoy a significantly more efficient review process. On average, they spend twice less time per review than with the previous beta version, even with additional data and comments to a case. Additionally, CS agents started to receive more insights into their manager's decisions and get notifications upon review submission. The enhanced functionality was introduced in the alpha phase, and subsequently, several other clients opted to include the Review Module in their subscription, increasing its value and impact.

Challenges and Learnings

• The project was a second iteration of an existing feature (in beta); therefore, I had a challenge to re-use existing layouts and components as much as possible to save the dev time. Due to my experience, this was an easy challenge, and the engineering team was surprised by the results. They spend twice as little time as they initially planned.  
• Providing design options with wireframes is good enough to make high-level design decisions. It saves design time since the designer has to proceed in high fidelity with only one selected option, and high fidelity is the most time-consuming. 
• The engineering team had concerns about the interface with three columns with independent scrolling. I overcame the challenge by constructing a prototype for the interface solution and presenting it to all stakeholders, including the engineering team.
• Showing a prototype to end users allowed us to validate the solution and to identify exact content prior to the implementation phase, which saved development time (money) and design iterations.
• It was the first project I started to use AI generative tools for content creation. No more 'lorem ipsum dolor'! I learned a fantastic tool to save time and enrich the story with realistic details. It eliminates unnecessary feedback from detail-oriented viewers and helps them focus on the right things.
• It's crucial to introduce and evaluate one feature at a time to accurately gauge design success, as introducing multiple updates simultaneously introduces too many variables, making it challenging to pinpoint the specific factors contributing to user experience outcomes. However, it is hardly archivable in a fast-paced environment where company revenue depends on satisfying client requirements on time, so think carefully about the roadmap and don't overpromise to your customers!  

Conclusion
This case study highlights the significant impact of a carefully executed redesign of the case review functionality. Through extensive user research, ideation, prototyping, and usability testing, the refined flow resulted in a notably more efficient review process for CS managers. The strategic use of prototypes was instrumental in streamlining the design process. Overall, this endeavor exemplifies the value of user-centric design in enhancing product functionality and user satisfaction.

2.4X

faster review time

3X

insights on manager decisions

+6%

CSAT growth

+8

clients purchased the module
(in 2 months after the release)

​CASE STUDY #2
​Support Hub 

Role
Sr Product Designer

Users
CS Team Managers, CS Agents and Engineers, Escalation Managers, Business Analysts of IT companies 

​Problem Statement
The 'SupportHub' is a case details page, the most visited page within the core product and across other SupportLogic products. Despite its popularity, the backlog housed several issues associated with this page. Concurrently, SupportLogic's other product utilizing the page, AgentSX, was in development, featuring a new React component library. The project presented an opportunity to enhance the page's usability, requiring designs with slightly modified functionality to align with the unique features of AgentSX.

Research Phase
The process began with a heuristic evaluation of the existing page, followed by a comprehensive analysis of usability studies and related issues cataloged in both the user research repository and the backlog. I also analyzed the layout, flows, and interactions of case detail pages of four different CRMs used by SupportLogic clients (Zendesk, Monday, HubSpot, and Salesforce). The page was used by different personas throughout their user journeys and I had to keep that in mind, while finding, analyzing and suggesting solutions for critical issues. 

Ideation and Conceptualization
Once I had brainstormed solutions for each item, I documented the necessary updates as user stories and collaborated with the team to confirm prioritization. 

Subsequently, I started the redesign process using low-fidelity wireframes, focusing initially on identifying necessary layout changes and components, particularly those not present in the existing library. Since I had two primary personas whose interaction with the page was quite different, I separated those designs into two main use cases. Each case had sub-cases to cover states of the support case (new, not assigned, in progress, closed, etc.) I prioritized higher components that applied to both cases and products, reserving new and advanced features and product-specific elements for future phases. This approach helped effectively manage the workload of the front-end team and gave more time for ideation and fine-tuning of brand-new components.

Initially, I conceptualized and developed a low-fidelity wireframe of responsive, adaptable, and scalable layout accommodating two different products. Then, I proceeded with more detailed wireframes for various cases.  I gathered feedback on wireframes during design reviews and through Figma collaboration and commenting tools. 

Prototyping and Usability Testing
​After iterating on feedback on wireframes, I designed page templates  and components covering different use cases in high fidelity. I combined screens according to user stories and connected them into prototypes, which we used for usability testing and demoed to stakeholders and the engineering team to gather the final round of feedback.  

Final Design and Visual Elements
In addition to improving page usability, I integrated features of custom case attributes, sentiment acknowledgment, and collaborative efforts within a CS team.

As soon as designs were approved, I masked high-fidelity mockups with FPO overlays (for positioning only) so developers could focus only on updated elements, transferred components to the stories, and annotated the designs. I passed the final designs on to the development team during hand-off meetings, and monitored the designated Slack channel for follow-up questions. 

Implementation and Development
I worked on several user stories simultaneously and handed them off to developers as soon as I completed the design work on any of them. This approach helped to distribute the workload evenly and have more control over design implementation and its results.

Since the design caters to a wide range of user scenarios involving basic and advanced functionality, I developed a strategy for implementing the changes and meticulously documented the desired enhancements through prioritized user stories, ensuring seamless organization based on dependencies. Altogether, there were ten user stories, and we descoped only a few suggestions marked as 'nice to have'. 

While the process spanned several development sprints, we successfully orchestrated a seamless transition for existing users. Each group of updates underwent thorough implementation and quality assurance testing before being introduced to the beta version.

​Evaluation
As we were updating the main functionality, we decided to proceed cautiously. We provided an opportunity to try a new layout or switch back to a previous version in the interface itself so as to not interrupt the existing workflow. We also gathered feedback by introducing an on-screen form to SupportLogic users for the first time. We made adjustments based on the received input, and once the response became positive or neutral, we progressed the updates into the alpha environment. To evaluate the success we were also looking into number of users switching back to previous version as well as their qualitative feedback and explanations on why they did so.

Challenges and Learnings

• I collaborated with two distinct teams to enhance the overall usability of the existing product while creating React components for the new product. Notably, both teams used different use cases, however, utilized the same component library, ensuring design consistency across SupportLogic products.
• Initially, no product manager was assigned to the project (since the company was hiring), so I had to continue to develop my product and project management skills, where I had to identify requirements, dependencies, and prioritize items correctly. 
• I also had to work on the strategy carefully and handle multiple projects simultaneously.

Outcome
The updated page gathered positive feedback and demonstrated substantial improvements in usage metrics. During usability testing, the tasks were completed in less time. With the alpha version of the update, the team collaboration surged, and there was an increased rate of sentiment acknowledgments, which supported better training of the ML model.

'SupportHub 2.X' before re-design

'SupportHub 3.0' after re-design

Conclusion
​This case study outlines a comprehensive redesign project to enhance the usability of the 'SupportHub' page, a critical page of SupportLogic's products. Through meticulous research, ideation, and prototyping, the project addressed existing issues and incorporated new features to accommodate the unique requirements of the Core and AgentSX products. The iterative process involved wireframes, high-fidelity mockups, prototypes, and usability testing. The implementation phase, guided by prioritized user stories, ensured efficient development and quality assurance. Introducing user feedback mechanisms and cautious roll-out strategies further contributed to the project's success. Despite challenges such as managing multiple projects and navigating the absence of a dedicated product manager, the redesigned page garnered positive feedback. It demonstrated notable improvements in usage metrics, highlighting its positive impact on user experience and team collaboration. This project showcased the effectiveness of cross-team cooperation and emphasized the importance of a strategic approach and iterative design processes in achieving successful product enhancements.

< eBay

B-Stock >