A behavioural design framework for Adobe Acrobat — turning fragmented usage into a felt sense of value, before the renewal decision is ever made consciously.
Acrobat is used in fragments. People sign a document, edit a contract, extract a table — and then leave. The value of a subscription is built across dozens of these tiny moments, but the user is never conscious of stacking them together.
By the time the renewal moment arrives, the user has no memory of what they actually got out of the product. The decision gets made on gut feel, not on accumulated evidence.
Without a trigger for reflection, value stays invisible.
The strategic bet was simple: visibility is the missing primitive. This isn't a UX problem — it's a behavioural one. The intervention had to live at the right moment in the user's psychology, not just the right place in the interface.
Make users' progress visible early — and the subscription stops being an abstract recurring charge. It becomes a felt outcome.
Acrobat isn't the first product with this problem. The pattern of mirroring user behaviour back at the moment of natural reflection is well-established in consumer products that have to earn renewal every year.
Annual recap as a cultural moment. Identity through behaviour — "you're a top 1% listener."
Reflection at natural milestones. Personalised, sharable, social-proof-ready.
"You saved with Prime this year." Direct value attribution to membership.
Stats on creation activity. Surfacing the collaborative outcome.
Across all four references, the same behavioural move shows up: mirror the user's behaviour back to them, at the moment of natural reflection. Don't tell people what the product can do. Show them what they've already done with it.
Surface a recap of the user's activity during their early weeks on Acrobat — anchored in their real behaviour, framed by an archetype they can recognise themselves in, and always pointing toward what's next.
Recap only appears when the user has done enough to make it meaningful. Never empty, never premature.
Numbers alone don't move people. Every recap maps behaviour to an archetype the user can see themselves in.
Half mirror, half map. Every reflection ends with one suggested next tool — turning realisation into action.
We walked the framework through a signed-in trial user — mapping each touchpoint in the flow against the three design principles.
Just as much care went into the dismissal path. The user closes the recap. The user doesn't take the next step. Recap had to feel like a gift, never a guilt-trip — so missing the moment costs the user nothing.
The reflection surface needed a reusable identity layer — a vocabulary for telling users who they were becoming as they used Acrobat. So we built an archetype system: task-oriented, glance-readable, gender-neutral, and globally legible by default.
Four early archetypes — each mapped to a distinct behavioural pattern in the product. Visual design under NDA.
This isn't an onboarding intervention — it's a behavioural intervention across the user's whole Acrobat journey. By surfacing accumulated value at moments of natural reflection, the framework is designed to move four commercially-meaningful behaviours that compound from first session through long-term retention.
Users who experience a milestone-anchored reflection have a tangible reason to stay through the critical activation window, before the decision to renew is ever consciously made.
Recap surfaces engineer a reason to come back — directly improving the proportion of trial users who open Acrobat again in Week 1 and beyond.
Each recap closes with one suggested next tool — broadening the surface area of the product the user actually touches, which compounds perceived value.
The "forward, not backward" principle pulls users back into active workflows from the moment the recap ends — translating reflection into measurable next-step activity.
A single reflection surface moves metrics once. A framework for surfacing accumulated value at the right behavioural moment can be re-used at every milestone in the user's journey — turning a one-off lift into a compounding capability.
The framework didn't add a feature to Acrobat — it added a moment. A deliberate pause, designed at the seam where habit forms, where the product gets to remind the user who they're becoming with it. That, more than any single screen, is the unit of behavioural design I came away with.