Product Case · Phase 2 of 3 · Client Follow-on

A completion-rate target alone wouldn't prove a redesign had actually taken hold.

This is a Product Strategy Metrics Deterioration problem.

Follow-on measurement framework delivered to NoMoBo. All figures are modeled, not measured. Builds on the Phase 1 field-assessment redesign, a built, interactive prototype delivered to NoMoBo that was never deployed into production or usability tested.

Phase 1 was designed to raise completion rates, but hitting that target wouldn't by itself prove the feature people needed most — offline mode — was actually being used, or that the improvement would last. I designed and delivered an activation-funnel and 90-day-retention measurement framework to find out — modeling a 4× activation lift and 3.8× retention lift, not a measured result.

Who Product & UX leadership from Phase 1 Would need proof beyond a single targeted completion-rate number, even before anything is built.

What Prove field access became sustained field usage Track adoption and retention over weeks, not just measure day-one completion.

Why 4× activation, 3.8× retention — illustrative 21% → 55% activation, 17% → 64% sustained 90-day submission rate — modeled, not measured.

Activation funnel — desktop vs iPad completion, pre/post redesign — The activation funnel — desktop vs. iPad completion, pre/post redesign.

Two things a completion number couldn't tell us

A higher number wasn't proof

Completion rate went up, but that didn't confirm the feature people needed most — offline mode — was actually being adopted.

No visibility into where people dropped off

Pre- vs. post-redesign, there was no way to see exactly where assessors abandoned the flow, or whether the gain would hold beyond day one.

What we changed

Mapped the full activation funnelTraced 6 stages from access to submission to find exactly where users dropped off.
Defined activation as two valid pathsSingle-session and offline draft-to-sync completion both count as success.
Tracked feature adoption weeklyMeasured offline mode, auto-sync, and draft save adoption over an 8-week ramp.
Modeled 90-day retentionMeasured sustained submission behavior, not just first-time completion.
Reframed the core health metricCompletion rate replaced logins and time-in-app as the primary signal.

8-week adoption curve for offline mode, auto-sync, draft save — The 8-week feature-adoption curve — offline mode, auto-sync, and draft save.

Transformation scale

6-stage funnel instrumented
3 core features tracked for adoption
8-week adoption curve modeled

What it moved

4×

Higher activation at final funnel stage

21% → 55%

3.8×

Higher 90-day retention

17% → 64% sustained submission rate

83%

Offline mode adoption by week 8

up from 41% in week 1

Before/after strip for time-to-submission, offline-path usage, 90-day retention — Before/after: time-to-submission, offline-path usage, and 90-day retention.

Business impact

4× activation rate vs. pre-redesign — 21% → 55% at final funnel stage
3.8× growth in offline-path completions — 5% → 38% of completions
3.8× higher 90-day retention — 17% → 64% sustained submission rate
Offline mode adoption reached 83% by week 8, up from 41% in week 1
Completion rate established as the core product health metric