Strategic Growth through Total Experience

In many SaaS companies, adoption, retention, and growth are treated as separate challenges. Product teams focus on building features, Customer Success handles training and renewals, and Support manages troubleshooting. Each team works hard, but customers still feel friction because these experiences are not connected. What's missing is a shared framework that treats all of these interactions as part of one system.

This is where Total Experience (TX) comes in. Popularized by Gartner, TX brings together four distinct areas: User Experience (UX), Customer Experience (CX), Employee Experience (EX), and Partner Experience (PX), and treats them as interdependent. A strong design decision improves usability for customers, makes training easier for employees, and creates consistency for partners. By connecting these pillars, organizations reduce silos and deliver outcomes customers feel in real ways: smoother onboarding, more consistent support, and higher adoption.

I introduced this lens into product planning and growth strategy, using the TX pillars to guide both daily work and long-term decisions. TX reshaped how we planned and executed growth efforts at SafetyChain, connecting multiple teams and surfacing actionable improvements.

How we focused on each of the four pillars:

• User Experience (UX). We revamped the onboarding experience directly in the product, adding guided tours and contextual help to reduce friction. Support ticket data showed where customers were struggling most, and those areas became the first focus for new in-app tours, dramatically reducing tickets in high-friction areas and giving customers uninterrupted progress without waiting on email or support responses.
• Customer Experience (CX). To shorten time-to-value, I partnered with Solution Engineering and Account Specialists to align onboarding across documentation, training materials, and in-app flows, and trained the team on the basics of Pendo, helping create dashboards that tracked user progress. Customers could get productive faster, and account teams could track their progress with clearer metrics.
• Employee Experience (EX). I organized cross-functional workshops that pulled individuals from across the company to define use cases and analyze workflows, surfacing tribal knowledge that often stayed siloed. A side benefit was internal onboarding guides that gave any employee the ability to deep dive into a product area and understand its full range of capabilities and limitations.
• Partner Experience (PX). During planning for future areas of product expansion, I flagged concerns on our IoT roadmap. Having built IoT products before, I recognized the limitations and technical debt in the current outline, and recommended realigning the project to focus on partnering with mature IoT providers. The new roadmap emphasized APIs and interfaces that allowed customers to integrate data while keeping the UI clean, intuitive, and consistent with our brand.

Applying a Total Experience strategy created measurable improvements across customer, employee, and organizational outcomes.

• Support efficiency. In key onboarding areas, guided in-app tours reduced support tickets by up to 90 percent month over month by module and friction type, reducing the burden on support engineers and shortening resolution times as ticket aging dropped.
• Customer adoption and advocacy. By shortening time-to-value for new accounts, onboarding became a differentiator. Customers could roll out the product faster across their facilities, and early wins translated into stronger advocacy for expansion.
• Employee empowerment. Workshops and internal onboarding documentation gave employees across departments the confidence to step into customer conversations, solve problems quickly, and understand the context behind unique workflows, reducing dependency on a handful of experts.
• Internal knowledge alignment. By capturing tribal knowledge, resolving gaps, and aligning processes, the organization eliminated high-risk blind spots that had previously only been passed along informally.
• Strategic roadmap alignment. Raising flags early on the IoT roadmap prevented the company from investing heavily in an unsustainable path, shifting the strategy toward partnerships and API development and saving development resources.