Adoption without barriers.

Driving adoption and engagement in enterprise applications through Whatfix HUB widget thereby enabling teams to deliver organizational knowledge, streamline workflows, simplify onboarding, and accelerate support resolution

For a year and half at Whatfix, I advocated the transformation of the HUB widget, both end user and authoring journeys, from fragmented overlays to a unified, no-code experience layer.

This shaped how I think about products holistically, and not just design them. For readers , a product walkthrough comes first, then a deep dive into the details and nuances. Use the Quick Access button (bottom right) to jump sections.

The HUB: Walkthrough of the end user and authoring experience

HUB - The Unified Experience layer

The HUB bridging guidance, tasks, and communication into one cohesive surface replacing fragmented overlays with a scalable, production ready system for 1200+ ENTs

End user experience - clarity in the flow of work

A lightweight, contextual layer embedded directly into the workflow, driving an increase to 28% open rates and 53.4% engagement of the combined experience

Authoring experience - control without complexity

A structured, play first system that enables authors to configure, style, preview, and essentially play around and deploy independently, thereby driving faster publishing cycles and a 20x increase in content creation velocity.

The Silent Saas problem

Powerful features don't guarantee adoption. When guidance is absent from daily workflows, users disengage quietly. Analytics show drop-offs. Support costs rise. ROI erodes. Adoption isn't a training problem. It's a behaviour design problem.

Humans in the ecosystem

Behind every adoption metric there are distinct users with varied responsibilities and expectations. Whatfix supports three core personas that together shape the success of the platform. 

End Users are employees of customers navigating enterprise applications to complete their daily tasks; they seek clarity, speed, and minimal disruption.

Admins and Managers focus on configuring the system, monitoring performance, and ensuring adoption translates into measurable outcomes. 

Learning & Development Authors and Instructional Designers craft the in-app guidance and learning experiences that enable users to build confidence over time. 

Understanding these interconnected roles allows us to design not just for usage, but for sustained value across the entire ecosystem.

End users
Admins and managers
Content authors and instructional designers

The wakeup call - realization that things need to change

Self Help and Tasklist were meant to drive adoption. Instead, they were adding friction. End users couldn't find contextual help. Admins couldn't prove ROI. Authors couldn't customize without raising a support ticket. By Q4 2024, open rates had fallen to 20.8% even among high-performing enterprise accounts. The signals were clear.- value of the platform became harder to realize and the ecosystem had failed. 

Understanding the problem - beyond the symptoms

As I looked deeper, the issue wasn’t engagement alone, it was structural.

The engagement dip was a symptom. The real issue was structural. 80% of widget customization required AC code, CSS, or engineering intervention, turning a product capability into a service dependency. The result: a 22% spike in support tickets and fragmented experiences across 1,200+ enterprise accounts.

Reinforcing the pattern - from customers to product

Authors reported: no self-serviceable controls, redundant configuration effort, inconsistent options across widgets. End users felt: the experience looked dated, felt disconnected from their actual application, and broke continuity with every product update. Competitive benchmarking confirmed it — most alternatives offered out-of-the-box customization and unified widgets with no support dependency. The problem wasn't just customization. It was coherence, control, consistency, and confidence across the ecosystem.

Rebuilding the Core - beyond design

After customer calls, support ticket audits, competitive analysis, and heuristic evaluations, the diagnosis was clear: this wasn't a UI refresh. It was a structural product problem.

Shift 1 - From Multi Overlays to One Embedded System

Stakeholders were protective of their application space. "We don't want another Whatfix icon in production." The widgets needed to feel embedded, not appended.

Shift 2 - From Service Dependency to Self Serviceability

80% of configurations needed engineering intervention. Authors the people most accountable for adoption had the least control. That had to change.

The bigger picture

Solving these problems wasn’t just about improving engagement metrics, it was about securing long-term scalability. The need was to future-proof DAP, reduce the operational burden of fragmented codebases, and shift from service-led to product-led growth. This wasn’t a redesign, it was a foundational rebuild of the experience so to restore coherence, control, consistency, and confidence

Building for the B2B2C ecosystem

The real differentiator wasn't more features , it was giving customers confident, independent control of the experience.

Three parallel tracks ran simultaneously:

  • Elevating the end-user experience to feel native

  • Refactoring the authoring foundation for scalable customization

  • Protecting business velocity by reducing ticket volume

Guiding principles

To get the best outcome in a B2B2C setting, the need was to mitigate issues of both audiences ( customers at once i,e the business that deploys the solution and the end user who experiences it. To succeed the need was to

  • Understand the need as a user

  • Choose simplicity over sophistication

  • Let right actions be obvious not guesswork

  • Enable flexibility with guardrails

  • Build for self serviceability and trust, not styling

Not ornamental. not external. not disruptive. Self-serviceability and trust became the north star, which meant the experience needed to be native, modern, confident and non-intrusive

Collaboration and craft

This wasn't a solo design effort. It took PMs, engineers, earlier designers, content authors, solution engineers, and CSMs, each adding a layer of context that the design couldn't exist without.

Every decision was documented, reviewed through XRBs and leadership, and tested for scale. The goal wasn't to refresh the interface , it was to restore control and rebuild trust.

Core structures - one step at a time

The system was though in layers. End-user experience came first as it ensure visible impact, faster ROI. Once that foundation held, the authoring experience was shaped around it, ensuring what authors built would always scale to what users needed.

End user experience

#Fluidity over rigidity - Employees need flexibility, but not at the cost of control. Any overlay system has to support users workflow without obstructing the core application experience. This meant designing for adaptability within clear boundaries, offering freedom where needed, while maintaining thoughtful guardrails to protect the primary flow of work.

#Recognise over recall - In fast paced work environments, users shouldn’t have to remember which widget does what. With limited time and high cognitive load, the system should feel obvious and ever-present , not sophisticated for the sake of it, but simple, predictable, and easy to recognize when needed.

#Empowerment over instruction - Users don’t want to be taught how to use a system; they want to feel supported while using it. The experience should empower them to act confidently, knowing the system has their back if something goes wrong. Instead of forcing them into guesswork or trial & error, which means the experience should feel obvious and self evident, guiding through clarity, not instruction.

Content authoring experience

#User is not an engineer - Content authors and instructional designers who build and deploy these widgets are not deeply technical. Their goal is simple: craft / style the widget, launch them and track impact. They operate as adoption champions within their organizations, but are often hesitant to engage with complex, code heavy, or technical systems

#Simplicity over sophistication - Users prefer systems that feel simple and familiar, with minimal learning required. They gravitate toward intuitive experiences that are easy to navigate, rather than complex flows that feel overly sophisticated or difficult to understand.

#Scalability over rigidity - These widgets shape the end user experience, they must be built on a foundation that can evolve. The system should support future enhancements and AI integrations without requiring structural rework. Flexibility at the core ensures the experience can grow alongside product and technological advancements, without being a business blocker

Designing for Systems- Not screens

Part 1 Evolving the end user experience

The widget was rebuilt around a clear interaction anatomy: Entry → Expansion → Action → Exit.

Entry - Discoverable, not distracting

The entry point evolved into a refined FAB, shaped through usability testing and continuous customer feedback. It needed to stay recognizable while adapting to different host applications.

The goal was simple: be present without being intrusive. Visible when needed. Silent when not. Here is the evolution of FAB overs 2 plus years

Expansion - One unified surface

When interacted, the widget expanded into a structured panel - not multiple scattered overlays. This panel became a single, organized workspace for guidance, tasks, and communication.

Instead of adding more UI elements, the consideration was to have functionality into one cohesive layer. Expansion wasn’t about showing more, it was about organizing better.

Action - Clear and contextual

Within the panel, actions were designed to feel obvious and relevant. Primary actions stood out naturally, while secondary options remained accessible but unobtrusive helping the user in taking better decisions. Here is evolution of the end user panel over a period of 2 plus years

The above image is an evolution of Self help panel over the years

The revamped solution brought everything together into a single, unified experience - introduced as the HUB.

The HUB integrates AI assistance, chatbots, and support systems into one seamless experience.

Exit - Effortless return to workflow

Closing or minimizing the widget was designed to feel seamless. The base application immediately regained focus, ensuring the workflow remained uninterrupted. The widget never owned the experience - it simply supported it.

Part 2 Structuring the Content author experience

A scalable end user experience cannot exist without a structured authoring backbone. By building clear hierarchies, reusable patterns, and rule-based configurations, it was ensured that authors could create confidently while maintaining system integrity. Scalability wasn’t achieved by adding more features, but by strengthening the foundation that supports every experience layer.

Out of Box - Play, customise, configure

To reduce friction, the system offered configurations that allowed authors to play around and understand the tool better. These included structured defaults, layout mappings, and visual styling controls designed to match the base application seamlessly maintaining accessibility guidelines. Built-in preview capabilities ensured authors could see changes in real time before publishing.

This reduced learning curves, eliminated guesswork, and enabled content authors to be design evangelist and accelerate deployment.

On demand setings - customize when needed

Beyond the defaults, the system was built to allow deeper customization for specific business needs. Authors could toggle modules on or off, to ensure they met their configuration needs

Advanced controls are available, but never overwhelming. Flexibility was layered thoughtfully, ensuring power without complexity.

Structured organization - ensuring recognition & scalability

The experience was built and organized into clearly defined functional tabs, with consistent accordion patterns to improve discoverability and future scalability Instead of dense control panels, options were grouped hierarchically and surfaced progressively. Familiar patterns reduced cognitive load, made navigation intuitive and space for future expansion. Recognition over recall, for every user.

The Outcome - Fragmented Overlays to Unified Experience

The shift was structural, not just visual. What felt disconnected now was unison - moving from friction to clarity, and from resistance to trust.

Older experience

New experience

Testing with Customers

After the design handoff, the experience was first deployed to a UAT environment for a controlled Beta release with select customers. This helped us validate the build, surface usability gaps, and collect early feedback.

Once the Beta phase concluded, the team initiated a phased GA rollout. During GA, customers custom requests for other refinements, which were captured and prioritised into the product roadmap backlog for future iterations.

The Business Impact

The shift was structural, not just visual. Fragmented overlays became a unified surface. Patchwork controls became a scalable system. From friction to clarity. From resistance to trust.

By early November 2025:

  • HUB open rate → 28% (up 8% in under 10 months)

  • Engagement → 53.4%, the highest since GA

  • ENT ID creation → 20x increase, meaning more content reaching more end users

What worked - whats next ?

Content authors responded positively to the revamped widget system, sharing that the experience now feels on par and in some cases better, than competing products in the market. The structured approach, improved clarity, and unified HUB strengthened both usability and perception.

At the same time, customers were eager to understand how the DAP experience would continue to evolve, especially in the context of rapid AI advancements. Their curiosity highlighted an important opportunity: ensuring the platform not only meets current expectations but stays ahead in an increasingly intelligent, adaptive product landscape.

Reflections- learnings of over a year

Enterprise products need stability, disruption without trust backfires. Powerful systems only work when hierarchy makes them easy to navigate. And great design isn't about adding more. It's about introducing clarity without breaking trust.