Skip to main content

Case Study Presentation

We Built the Intelligence. Nobody Knew It Existed.

Anuja Harsha — Lead Product Designer

DSML Hub · Cloud Software Group — WebFOCUS

Lead Product Designer (End-to-End Ownership)

We Built the Intelligence. Nobody Knew It Existed.

Cloud Software Group — WebFOCUSSpring 2024 – Spring 2025

Problem

Low Adoption

Three AI features, invisible

Solution

3 → 1 Hub

Unified discovery surface

Timeline

Spring 2024 – Spring 2025

Architecture to production

Three Powerful AI Features. Near-Zero Adoption.

NLQ buried inside “Explore Data.” Insights in a submenu. ML in a data flow canvas. Millions invested. Nobody could find them.

Invisible Features

Three AI features. Three different entry points. Three different mental models. Users didn't even know they existed.

!
Not Assigned — Co-Created

My PM Karishma and I conceived the Hub together. My Director of Design and Head PM shaped the vision with us. Karishma pitched. VP approved. We owned it end-to-end.

The Fragmented Landscape

Two Paths — Zero Shared Context

Path 1 — Finding NLQ or Insights

Hub
+ Menu
Explore Data
NLQ
Insights

4 clicks · buried in a popup · side-by-side tabs

Path 2 — Finding Predict Data (ML)

Hub
App Dirs
Right-click
Predict Data

4 clicks · completely different path · different mental model

Two separate paths. Two mental models.

No wonder nobody found them.

NLQ Empty State
View Focus

NLQ — buried in 'Explore Data' popup

Insights — hidden alongside NLQ
View Focus

Old Workflows

NLQ (Natural Language Query)

Automated Insights

ML Functions (Predict Data)

The Turning Point
I already owned NLQ, ML, and Insights. IQ was the culmination — bringing everything I'd built to the front and center of WebFOCUS.

Upgrading the Building Blocks.

I already owned NLQ and ML. Insights landed in my lap — same engineering team, same PM, same QA. Before unifying them, I modernized each one individually.

NLQ Redesign

NLQ Redesigned Empty State
View Focus

Suggested queries, conversational errors

NLQ Suggested Questions
View Focus

Zero-intimidation entry point

NLQ Results
View Focus

AI-generated chart from natural language

NLQ Error Handling
View Focus

Conversational errors — not stack traces

Insights Redesign

Insights Results
View Focus

Auto-generated insight cards

Insights Tile View
View Focus

Scannable card-based results

The Turning Point
Same PM. Same engineers. Same designer. NLQ, Insights, ML — I'd modernized each one. IQ brought them all together. The culmination of everything I'd pushed for.

Architecture Before Tickets.

I pushed for things never done in the org. Karishma wrote tickets after seeing my mockups. 3–4 meetings a week across timezones — architecture already mapped before anyone asked.

The Solution — One Click

After — Everything Under One Roof

Hub
IQ Plugin
NLQ
Insights
ML
1
Click
3→1
Entry Points
0
New Infra

IQ Architecture

One Entry Point

Smart integration inside the existing Hub. No new infrastructure needed. Three scattered menus → one destination, one mental model.

IQ Plugin Architecture Flowchart
View Focus

IQ Plugin architecture — NLQ, Insights, and ML under one Hub

Dataset Selection Workflow

Dataset Selection Workflow
View Focus

Unified dataset selection workflow

Hub Layout

Hub Structure Layout
View Focus

How IQ fits into the existing Hub layout

Sketches & Early Concepts

Hand-drawn Sketches
View Focus

Early concept sketching

IQ Wireframes
View Focus

Architecture wireframes

Responsive Design

Responsive Mockups
View Focus

First fully responsive Hub app

Four Iterations to the Final Hub.

V1 too dense. V2 too passive. V3 competed with Hub navigation. V4 — clean icon tiles — landed.

Design Iterations

IQ Hub Concept — NLQ, Insights, ML
View Focus

IQ Hub concept: NLQ + Insights + ML in one place

V1 — Too Dense

V1 — Early Concept
View Focus

First concept — too much information

V2 — Too Passive

V2 — Mid Iteration
View Focus

Second iteration — too sparse

V3 — Competed with Hub Nav

V3 — Competed with Hub Navigation
View Focus

Third iteration — competed with Hub navigation

V4 — Shipped ✔

The Navigation Fight

The lead architect — 20+ years — wanted list views. The WebFOCUS architect — 35+ years — backed him. My argument: lists are exactly why nobody found these features. Large tiles give immediate context.

V4 — Final IQ Discover Page — Shipped
View Focus

The final IQ Discover page — shipped

Insights in IQ

Insights Empty State
View Focus

Insights: Empty state

Insights Data Selected
View Focus

Insights: Data selected

Insights Tile View
View Focus

Insights: Scannable card-based results

NLQ in IQ

NLQ Empty State
View Focus

NLQ: Ask questions in plain English

NLQ Data Selected
View Focus

NLQ: Data selected state

NLQ Results
View Focus

NLQ: AI-generated chart

ML in IQ

ML Landing
View Focus

Predict Data landing — inside IQ

Compare Models
View Focus

Compare models in context

Fitted Values
View Focus

Model results — fitted values

Explainability
View Focus

Run model — explainability view

Run Model Results
View Focus

Run model — prediction results

Preview Data in IQ

Preview Data - Sample
View Focus

Preview data — sample tab

Preview Data - Analysis
View Focus

Preview data — key analysis

Preview Data - Time Series
View Focus

Preview data — time series

IQ Walkthrough

The Turning Point
My Director of Design said it best — bold and fearless. Industry examples. Interaction logic. Visual prototypes. He was fully in my corner, watching me make my own case.

The Room Full of Veterans.

Director of Engineering. Principal Data Scientist. Head PM. Lead Architect. All decades of tenure. I was 2 years in. Karishma and I were the only new people in the room.

20yr
25yr
30yr
35yr
vs
2yr

Every Meeting, Outnumbered

Veterans with 20 to 35 years at WebFOCUS. My PM and I onboarded together. We pushed the vision together.

Earned Trust

And They Were Listening

It hit me later — I was arguing about data flows and ML architecture with people who'd been here for decades. And they were listening.

The Turning Point
Two years in. Everyone else — decades. I set up meetings, drove cross-functional alignment, nudged PMs to collaborate. That wasn't my job title. It was just what the project needed.

Visibility Was the Solution.

NLQ redesign + Phi-3 model upgrade drove +25% adoption. Customers looked forward to NLQ the most. The Hub brings all of it — NLQ, Insights, ML — front and center.

+25%

NLQ adoption from discoverability alone. No feature changes. The highest-leverage design work: making existing features findable.

3 → 1

Scattered tools unified into one Hub. The patterns became the platform's AI strategy foundation. NLQ + Insights live. Hub implemented — final QA pending at departure.

What This Project Proved

We co-created this project as a team. The features didn't change. The visibility did. That's the highest-leverage design work there is.

KK

Anuja led UX design initiatives with remarkable creativity, empathy, and precision. She consistently demonstrated a deep understanding of user-centered design and the ability to translate complex product requirements into intuitive and visually engaging experiences. What truly stands out is her collaborative spirit and problem-solving mindset.

Karishma Khadge, Senior Product Manager

VR

Anuja made a significant impact modernizing UX across our legacy enterprise products. She brings a rare combination of strategic thinking, design intuition, and the ability to work seamlessly across product, engineering, and business teams. Anuja is bold in her ideas and consistently proactive in turning complex problems into practical, user-centered solutions.

Vijay Raman, VP of Product Management

What Came Back With Me

When I returned from maternity leave, the engineering team shared that they valued the way I approached design — understanding the system, asking the right questions, making informed decisions. The experience reinforced something I already believed: context isn't transferable through documentation alone. It comes from genuine curiosity and investment in the problem.

What I'd Push Harder For

Proper Tutorials and Onboarding

Tutorials & Onboarding: Initially proposed a dedicated "Get Started" panel. Through iteration, we improved the tutorials, Discover page, and Explore Data header instead — better UX, same goal.

Future Plans

Ecosystem Integration

Ecosystem Integration: Connect ReportCaster + IQ to auto-schedule generated insights. NLQ as a chat interface for the entire platform.