Loading
Skip to main content
Case Study 003

Driving Data Science Adoption in Enterprise BI

Unifying Data Science & ML Inside WebFOCUS This started as a concept in the annual roadmap. I took it from idea to shipped architecture — bringing mockups to the table first, with tickets following after. I owned all three workflows and eventually handed off to two designers.

// STATUS: IN_ENGINEERING_—_SHIPPING_2027
Product_VisionSystems_ThinkingCross-functional_LeadershipTeam_Enablement
iq_hub_unified_view.tsx
DSML Hub - Unified Data Science & Machine Learning
Principal Product Designer (Full Ownership)·Cloud Software Group — WebFOCUS·Spring 2024 – Spring 2025 | Shipping 2027

I brought mockups first — tickets followed.

— From roadmap concept to shipped architecture, owning all three DSML workflows

Design Leadership

At a Glance

Situation

Three powerful data science features existed but were scattered across the platform. Different entry points, different patterns, low adoption. Users didn't know they were there.

Task

Unify them into one discoverable experience. Make data science accessible without hiding it.

Action

Defined the architecture and base screens for all three. Established consistent interaction patterns and made everything responsive.

Result

Integrated three features into the Hub — no extra space, everything inside. NLQ and Insights live in production. DSML Hub shipping 2027.

Sound On · Director's Commentary

The Transformation

Narrated walkthrough of the fragmented legacy workflows vs. the unified modern experience.

Current Workflows (Public)

NLQ (Natural Language Query)

Standalone NLQ workflow in Explore Data — separate entry point, different mental model.

Automated Insights

Standalone Automated Insights workflow — another separate entry point with its own interface.

ML Functions (Predict Data)

ML Functions from Reporting Server — redesigned with unified patterns.

Unified DSML Hub (Password Protected)

The new unified DSML Hub: all three DSML capabilities consolidated into one cohesive entry point.

Password Required

Click to unlock unified workflow

Key Differences

Before
  • Three separate entry points
  • Different patterns for each feature
  • Users had to hunt for features
  • Intimidating for business users
After
  • Single unified entry point
  • Consistent patterns everywhere
  • All DSML in one place
  • Approachable for all users

Discover Deeply: From Roadmap Concept to Strategic Definition

TL;DR

Three powerful features existed — but nobody could find them. Customer feedback confirmed: visibility was the problem.

WebFOCUS had three data science features:
  • NLQ — Natural Language Query: ask questions against your data in plain English ("Which product sold most last quarter?")
  • Insights — Auto-generates visualizations and patterns from your dataset
  • ML — Train predictive models: classification, regression, time-series forecasting, anomaly detection
All shipping. None legacy. The problem? They weren't visible. NLQ was buried in Explore Data. Insights was hidden in a submenu. ML lived in a completely separate context.
How I discovered this: Customer feedback from support reps, PMs, and leadership all pointed to the same issue — users didn't know these features existed. The problem wasn't quality; it was discoverability.

Empathize with the Ecosystem: Bridging the Gap Between Personas

TL;DR

Data scientists needed depth. Business users needed simplicity. One entry point had to serve both.

Two primary personas with conflicting needs:
  • Data scientists wanted depth, control, and advanced configuration options
  • Business users wanted simplicity, guidance, and quick answers without technical complexity
They had completely different mental models — but we needed one entry point for both. The solution was layered disclosure: approachable on the surface for business users, powerful underneath for data scientists.

Simplify the Chaos: Mapping and Unifying the System

TL;DR

Integrated three scattered entry points into the Hub. Already owned all three — integration felt natural.

I defined the architecture before any tickets existed. The PM wrote tickets after seeing my mockups — that's how I operated throughout.
Why integration was natural: I already owned all three features. NLQ, Insights, and ML were mine. When the DSML Hub opportunity came, the hard work was already done — I understood every workflow, every edge case, every user pain point.
Key architectural decisions:
  • Smart integration into the Hub — no extra space, everything inside
  • One DSML Hub as the single entry point
  • Consistent interaction patterns across NLQ, Insights, and ML
  • Fully responsive — works on any screen size
  • No new infrastructure; built within existing Hub ecosystem
This meant faster development and familiar patterns for engineering.
// ARCHIVE_EVIDENCE

The Idea Lab

3 products in 1 plugin. From napkin sketches to high-fidelity wireframes, mapping out how Natural Language, Insights, and Analysis would coexist.

Rapid Board Ideation

Rapid Board Ideation

System Architecture Flow

System Architecture Flow

Low-Fidelity Wireframes

Low-Fidelity Wireframes

Initial Concept Mockup

Initial Concept Mockup

Hub Integration Spec

Hub Integration Spec

🔒

Architecture Blueprint

Detailed artifacts and sensitive diagrams are available for authorized reviewers.

// UX_PRINCIPLES

Design Principles Applied

Unified Entry PointProgressive DisclosureCognitive OffloadingOne Click AwayResponsive FirstContextual Help

Iterate with Inclusion: The Evolution of a Unified Hub

TL;DR

Same features, transformed experience. Three separate tools became one cohesive hub.

The transformation wasn't about changing features — it was about changing how users find and access them.
Before: Three separate entry points, three different mental models, three chances for users to give up.After: One DSML Hub, consistent patterns, one learning curve.
Drag the sliders to see the transformation.
🔒

Design Evolution

Detailed artifacts and sensitive diagrams are available for authorized reviewers.

🔒

Empty States

Detailed artifacts and sensitive diagrams are available for authorized reviewers.

🔒

Protected Content

Detailed artifacts and sensitive diagrams are available for authorized reviewers.

Grow Through Constraints: Strategic Ownership at Scale

TL;DR

Fought for features, lost some battles. Built within constraints, enabled two designers to continue.

What got rejected: A lot. I fought for a navigation bar in IQ — eventually won. Built a "Get Started" panel that got scrapped after significant effort (we integrated it better elsewhere). Pushed for more IQ features on the Hub homepage — rejected due to engineering resources.
The Hub ecosystem constraint became an advantage: familiar patterns meant faster development and easier adoption. After establishing the architecture and base screens, I handed off to two designers (one junior, one senior). They executed confidently because the foundation was clear.
What I'd do differently: I wanted to add proper tutorials and onboarding flows — never got full green light. I envisioned NLQ as a chat interface for WebFOCUS itself (step-by-step workflow guidance), and I wanted to connect ReportCaster and IQ (schedule generated insights automatically). These remain opportunities for the platform.
🔒

Architecture Blueprint

Detailed artifacts and sensitive diagrams are available for authorized reviewers.

Navigate Forward: Adoption, Impact, and Future

TL;DR

NLQ adoption +25%. Insights live. DSML Hub shipping 2027.

Key Metrics:25%
What's live now (9.3.6):
  • NLQ with +25% adoption increase
  • Insights with auto-generated visualizations
What's shipping:
  • ML Functions redesign → 2026
  • Unified DSML Hub → 2027
The +25% NLQ adoption increase came from making the feature discoverable — not from changing the feature itself. Visibility was the problem. Visibility was the solution.
🔒

Workflow Comparison

Detailed artifacts and sensitive diagrams are available for authorized reviewers.

🔒

Protected Content

Detailed artifacts and sensitive diagrams are available for authorized reviewers.

Interested in working together?