Skip to main content
HS
HiSETSuccess
LeetCode Prep

AI & FDE Interview Room

Role paths, mocks, cost studio, chapters, cases, and staff-level depth.

Case study · FDE · 25 min

Defining AI Pilot Success Metrics

Choose measurable pilot KPIs that balance model quality, user value, and business ROI — and know when to stop.

FDEmetricspilot

Interview opener

Define pilot success that executives and users both accept.

  1. 1.Leading vs lagging indicators?
  2. 2.What is an automatic kill?
  3. 3.How do vanity metrics mislead here?

Strong signals

Hit 0/3

Weak signals (avoid)

  • Only 'number of queries'
  • Success redefined after the fact

Requirements

  • Pilot: 8 weeks, 150 users, internal knowledge assistant
  • Need leading + lagging indicators; explicit expand/kill thresholds
  • Avoid vanity metrics (raw query count without outcomes)
  • Report weekly to buyer in one page

Back-of-envelope Estimation

MetricCalculationResult
Users150150
Target WAU60% = 90engagement
Minutes saved/queryhypothesis 8 minsurvey + diary
Queries/user/week4360 queries/week
Value/week360 × 8/60 × $75/hr~$3,600
LLM cost/week~$50clear ROI if value real

Metrics Collection API

EndpointMethodDescription
POST /v1/eventsPOSTquery, citation_click, copy, thumbs, escalate
POST /v1/surveysPOSTCSAT / time-saved responses
GET /v1/pilot/reportGETWeekly KPI snapshot JSON

Data Model

EntityKey fieldsNotes
kpisname, target, actual, weekTime series
cohortsuser_id, trained, activeFunnel
outcomesticket_deflect, time_savedBusiness

High-level Design

Metric layers
Quality: groundedness, citation precision (offline+online sample)
UX:      WAU, thumbs-up rate, p95 latency
Value:   time saved, ticket deflection, NPS
Decision: expand if quality≥85% AND WAU≥50% AND value>$X
          kill if quality<75% after week 4 OR WAU<25%

Deep Dive: Goodhart's Law

  • Don't reward query volume — reward successful task completion
  • Pair automatic metrics with 10 user interviews mid-pilot
  • Pre-register kill criteria with the buyer to avoid moving goalposts
  • Separate model quality fails from change-management fails

Bottlenecks at Scale

  • Sparse survey responses — in-product micro-survey after citation click
  • Confounded seasonality — compare to prior period baselines
  • Champion bias — sample end users, not only power users

Failure Modes & Monitoring

KPITargetAction
Groundedness≥ 85%Pause expand; fix retrieval
WAU≥ 50%Training + UX review
CSAT≥ 4.0Interview detractors
ROI proxy> 5× costBuyer go/no-go

Attempt the case aloud first. Then unlock a staff model answer outline.