All projects

ThriveDX

March 2022 - January 2023 · Desktop / Mobile web

Leads, website health, access, and analytics in one responsive product.

WatchDog digital operations platform

Overview

WatchDog had to make several messy operational jobs feel like one product. Leads, website performance, user access, errors, and analytics all affected the same digital operation, but teams handled them in disconnected workflows. My work focused on product structure, the interface system, and visual identity. After rollout, more than 400 workers were onboarded onto the platform and time to lead dropped 53%.

Role
Product Design Lead
My focus
Product ownership, platform structure, and operational dashboard UX across related tools.
Evidence
  • Interviews with teams working across lead management, website operations, and analytics.
  • Existing lead, website-performance, access, and analytics workflows mapped during product definition.

Process and solution

WatchDog product flow connecting operational domains

Keep a broad product readable

Lead management, website health, access, and analytics used different signals and actions. Shared navigation and overview-to-detail patterns kept urgent status separate from deeper work.

This was the main design challenge: the system needed to be powerful enough to cover several operational domains without becoming a dense reporting wall.

WatchDog overview organizing high-priority operational information

Put follow-up next to the signal

Website analytics and lead management sat in the same operating view, connecting performance signals to the follow-up they required.

When teams could see leads, website health, errors, and access in one product, they could identify what needed attention and assign the right operational response faster.

WatchDog website analytics and lead-management views

Use one responsive model

The information architecture adapted to smaller screens without creating separately maintained product versions.

Responsive WatchDog mobile views

Key decision

Centralize related operational capabilities while using hierarchy to contain complexity.

Separate tools were simpler on their own but hid relationships between signals and actions. Centralizing the work added interface complexity, so the information architecture had to keep each domain distinct.

Alternative considered: Keep lead, website-health, access, and analytics work in separate specialist tools. / Reduce the product to a narrower single-purpose workflow.

Outcome

0+

Workers onboarded

-0%

Time to lead

Looking ahead

Extend measurement beyond speed, tracking lead quality and follow-up outcomes as the platform grows.