A 0.06% adoption rate became 164% growth in 30 days.
The problem
Theme updates were buried 4+ clicks deep with no preview and no feedback loop. Users described being “terrified” and “afraid I'll break everything” — so adoption sat at 0.06%. Not 6%. Point-zero-six percent. Meanwhile, 12% of all support tickets were theme-related.
The obvious fix was a full rebuild of the theme system. We didn't have the engineering runway for it — a codebase migration was already scheduled and that was the team's capacity. So the question shifted: what's the highest-impact fix we can land within what's already planned?
What I owned
- →Product strategy and prioritization across a fixed 3-month migration timeline.
- →Customer research: interviews plus analysis of theme-related support tickets (12% of all tickets at the time).
- →Cross-functional scoping — identified the highest-impact fixes within the codebase migration already in progress.
- →Established theme adoption as a tracked product KPI for the first time.
Key decisions
One-click apply with preview and fallback pages
Replaced the buried 4-click flow with a single "Apply Theme" action plus a confirmation/preview step, and shipped default fallback pages (404, login, forgot password) so switching themes stopped feeling dangerous. The fear of breaking something was the actual adoption blocker — not the number of clicks.
Scope to the migration already in progress
Rather than lobbying for separate engineering time, I scoped the fix to ride inside an already-planned codebase migration. The question was "what can we fix right now that moves the metric most," not "what's the ideal fix." This got the work shipped in 3 months instead of onto a backlog.
Outcome
- →164% increase in theme adoption within 30 days.
- →Active website usage rose from 3.49% to 4.22% weekly.
- →Reduced theme-related support ticket volume.
- →Theme adoption became a tracked core product KPI — it had never been measured before this project.