Adoption Product Strategy

Unified Whatfix experience

Helping Whatfix customers drive engagement and adoption of their enterprise applications through a unified Whatfix authoring and consumption experience

Timeline
2025 – 2026
Impact
Phase 1
14x
Content creation
3 hrs
Avg widget deployment time
Phase 2
+20%
Open Rate
53.4%
Engagement
Evaluated during a 90-day beta release in comparison with the original.
My Role
Advocated ans owned end-to-end design across both phases.
Collaborated with PM, 1 researcher, 3 engineers, multiple DAC and curomaer POCs.

Context

Whatfix helps enterprises improve application adoption, engagement, and ROI through in-platform content and widgets. Self Help and Task List are two key end-user widgets configured by L&D admins and content authors to guide end users through their base applications

The original Self Help and Task List configurations, from left to right

By early 2025, however, we saw two strong signals that the platform’s value was becoming harder to realize.Widget open rates had fallen to as low as 20.8% among high-performing enterprise accounts, while customer success ticket analysis showed a 22% spike in support requests.

Data from Q4 2024 Pod review

🤝
Increased support tickets wasn't the bottleneck
Before moving into solutioning, we analyzed configuration behavior across 1200+ enterprise accounts. We found that more than 80% relied on custom CSS blocks or AC code to meet their needs. This beacme the base; as we were not just re-designing but building a scalable system for non-technical users.

Challenge

Analysis of 1,200+ accounts reframed the challenge: this was not just a redesign, but an opportunity to refactor the experience into a scalable, reusable configuration pattern

📌
Problem statement
How might we enable content authors and L&D teams to configure and maintain end user widgets consistently, reducing support dependency while improving creation efficiency and long-term scalability?.

Strategy

Through close prioritization discussions with enginnering and DACs, we structured the experience into two phases to balance impact, adoption effort, and implementation complexity.

Two phases, one experience
The idea was in Phase 1 do the heavy lifting on the product side, with minimal intervention required from customers. This allowed us to demonstrate clear efficiency gains in content creation before introducing a larger customer-facing shift. Once the value was established Phase 2 could then focus on migrating customers in batches toward the merged end-user one widget experience.
phase 1

Configure , customize, create

A self-serve playground for content creators to design, preview, and deploy branded widgets that seamlessly match the look and feel of the base application.

Challenges we addressed

The original configuration experience had a cluttered IA and repetitive widget-level styling which made configuration harder to use, scale, and maintain.

🖥️
High code dependency
Content creators relied on custom CSS and AC code for basic customization. With limited out-of-the-box controls, the product became harder to maintain and scale.
🤯
Slow creation process
A cluttered hierarchy surfaced every option upfront, thereby increasing cognitive overload for content authors to find the right settings, make decisions, and configure efficiently.
🔁
Repetitive effort
Two separate widgets needed to be configured for a common adoption and engagement goal, creating duplicate styling effort, slower maintenance, and lower ROI.

Key design interventions

Out of Box - Play, customise, configure

In an effort to reduce reliance on custom code, we introduced out-of-the-box customization controls that let non technical content authors experiment, preview and configure widgets with their base application. This enabled them to create polished, branded experiences independently and become design evangelists within their organization

Layered flexibility of customisation

Usage patterns across enterprise accounts helped us identify which customizations were frequently used, which were contextual, and which belonged behind feature flags. This allowed us to restructure the information architecture around user intent and end outcomes, thereby surfacing only the most relevant options upfront to reduce decision fatigue and speed up configuration.

Whatfix HUB - one widget, multiple possibilities

The experience shifted from repeated widget-level configuration to a single, unified setup model. One configuration could now power multiple experiences; including Self Help, Task List, Support, chatbot integrations, and AI agents therby reducing repetitive effort and making the system easier to scale and maintain.

The all new - Whatfix HUB

📢
Self serviceability with control
A structured, self serviceable system that enables authors to configure, style, preview, and essentially play around and deploy independently, thereby driving faster publishing cycles and a 14x increase in content creation velocity along with a redution in content creation time to 3 hours from an average of 2,5 days.
phase 2

Unified widget ecosystem

The success of Phase 1 — reflected in faster content creation velocity and reduced authoring time — created the momentum to rethink the end-user experience at a larger scale. This led to the strategy of unifying all end-user interactions into a single widget ecosystem called HUB.

Instead of exposing users to multiple disconnected widgets across the application UI, HUB introduced one centralized entry point that surfaced support, guidance, tasks, chatbot integrations, and AI-powered assistance contextually within the flow of work.

Challenges we addressed

The existing end-user experience exposed users to multiple Whatfix widgets - such as Self Help and Task List — each competing for attention alongside other external widgets in the application interface.

⛓️‍💥
Fragmented experience
Switching between overlays and widgets disrupted the end user primary intent on base application thereby reducing task completion and efficiency.
🔔
Notification fatigue
Multiple Whatfix and external widgets created repetitive prompts and UI noise, causing users to ignore guidance over time and reducing overall engagement and adoption.

Key design interventions

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

Entry - Discoverable, not distracting

The FAB evolved into a recognizable yet adaptable entry point across host applications - designed to stay discoverable without disrupting the workflow

Expansion - One unified surface

Interacting with the FAB expanded a single structured panel instead of multiple disconnected overlays. Guidance, tasks, and communication were unified into one cohesive workspace — reducing context switching and organizing functionality around the user’s workflow instead of adding more UI clutter.

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

Action - segregated 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

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.

The HUB: End user experience

The unified widget ecosystem
The HUB bridges guidance, tasks, and communication into one cohesive surface replacing fragmented overlays with a scalable, production ready system for 1200+ ENTs
🚀
Clarity in the flow of work
A lightweight, contextual layer embedded directly into the workflow, driving a 20% increase in open rates and 53.4% increase in engagement of the combined experience

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. This shift also opened new conversations around the future of AI-driven DAP experiences and adaptive guidance.

Reflections- learnings from over a year

🧭
Design for user reality
Enterprise experiences are built around users at the centre, understand what they already know, what they aspire to achieve, and the limitations they navigate every day.
💡
Slow creation process
Great experiences aren't about adding more functionality, but about simplifying fragmented experiences into a cohesive, scalable system users could trust confidently
🧩
Repetitive effort
Solving user problems at scale required identifying what would influence the business to act thereby connecting user pain points with measurable product and operational impact.