Case Study — Opportunity Command Center

From idea to realized savings — an AI-augmented opportunity pipeline

For a Fortune 100 healthcare payer running a multi-billion-dollar Cost-of-Care savings mandate. Replacing document-heavy intake and ServiceNow blind spots with a connected, AI-classified opportunity lifecycle.

Client
Fortune 100 Healthcare Payer
Industry
Healthcare — Cost of Care
My Role
Lead Product Designer (E2E)
Timeline
2026
Team
1 Designer · Eng · 2 PMs
Engagement
Deloitte Consulting
01 — The Challenge

A doc-heavy process for a multi-billion-dollar mandate

The Problem

  • Ideas scattered across email, Slack, decks, and SharePoint
  • ServiceNow only tracks execution — ideation is a blind spot
  • No one place to see "idea → estimated → realized" for any opportunity
  • Inconsistent classification: the submitter had to guess the right team
  • Annual savings target invisible at the portfolio level
  • No archetype-level rollup to compare domains

The Shift

  • One intake, any employee, any plain-language description
  • AI agent classifies archetype and suggests priority at capture
  • Five-stage ontology applied consistently across every archetype
  • ServiceNow integrated as an execution step, not the system of record
  • Portfolio dashboard mapped to the annual CoC target
  • Action Center unifies the individual's task list across opportunities
$B+
Annual CoC Mandate
6,000+
Opportunities Tracked
10+
Archetype Domains
4
Persona Journeys
02 — User Research

Four personas, one shared data model

One system, four audiences — from the clinician with an idea to the VP defending the annual savings mandate. Each persona enters from a different surface; the data model underneath is the same.

Submitter
Clinician · Pharmacist · Ops Analyst
Spots a cost-saving idea anywhere in the org. Has a browser tab and a thought — not a structured template.
Pain: No idea where to file it. Prior path was an email that died, or a SNOW ticket that only tracked execution.
Owner
Cost-of-Care Analyst
Owns a portfolio of active opportunities across stages; drives each through workflow steps toward realized impact.
Pain: Task tracking scattered across SNOW, Excel, Slack. No single view of what's next for me.
Archetype Lead
Domain Director (CM · UM · Rx · Network)
Curates the archetype backlog, spots patterns, unblocks the pipeline for their domain.
Pain: Dozens of opps per archetype — can't see aging, blockers, or the gap between estimated and realized.
Program Lead
VP, Cost of Care
Accountable to the multi-billion savings mandate; reports portfolio progress monthly.
Pain: No portfolio-wide view across phases. Pipeline vs. realized gap invisible. Board asks one number.
03 — Platform Overview

Three dashboards, three audiences

The portfolio shows up differently depending on whether you're executing, curating, or reporting. Click any tile to see the full page.

04 — MVP Walkthrough

Three key moments in the lifecycle

The product is broad, but three moments carry the whole story: how an idea enters the system, how the archetype ontology gives it structure, and how execution rolls up into realized impact.

Moment 01 · Opportunity Submitter
AI-Guided Intake

Anyone describes the idea — AI handles the structure

Intake & classification

The submitter types the opportunity in plain words. An AI agent reads the description, auto-assigns the archetype, suggests a priority, and populates the structured fields. What was once a "where do I send this?" friction point becomes a one-minute capture.

AI-Guided Intake — Intake & classification
AI-Guided Intake · sample screen
05 — Impact

Idea-to-realized, made legible

From doc-heavy to intelligent

AI archetype classification removes the org-chart literacy the submitter used to need. Idea in, structured opportunity out.

Pipeline visibility before SNOW

Ideation is no longer a ServiceNow blind spot. The portfolio-level view starts at "someone had an idea," not "a ticket exists."

Consistent rollup across archetypes

The same 5-stage ontology across every archetype means a VP can compare CM vs UM progress without first reconciling templates.

One surface, four audiences

Submitter captures, Owner executes, Archetype Lead curates, Program Lead reports — same product, different entry points, shared data model.

06 — Reflection

Designing an ontology, not a form

The core design challenge wasn't a form — it was an ontology. Opportunities flow through the same five stages, but the workflow steps inside each stage differ by archetype and by the team that executes it. Getting that abstraction right — general enough to roll up, specific enough to be useful — shaped every downstream decision.

Strategic frame: The design problem was less "a form" and more "an ontology" — what makes an opportunity count, how it moves, what "realized" means
AI as guardrail, not replacement: The archetype agent removes friction at intake; the Archetype Lead still confirms classification before the opp moves out of Draft
Connecting strategy to delivery: ServiceNow handles the execution-step tickets; this platform surrounds it with the idea-to-realized narrative a VP needs to defend the annual mandate
Next Case Study

Agentic AI Platform for Healthcare

View Project →