How Prime earns loyalty.

Nobody had named the problem yet, so I started by naming it.

At the time, three teams inside Amazon held three different opinions about what Prime should sound like, and members were hearing all of them at once. Research kept arriving from every direction, but each team was reading its own version in isolation, which meant the conflict never got resolved at the level it needed to.

I started by reading every value-communication-adjacent research study I could find. Four major ones existed, completed over eighteen months across three different teams, and while each was a useful finding on its own, reading them together was where the verdict emerged. So I synthesized them and brought leadership a single diagnosis.

Then I mapped the internal landscape. Three sets of guidelines were quietly competing for authority across Prime surfaces: Amazon's RIO standards, the Brand voice (Charm and Disarm), and Prime's own retention strategies. Each was strong on its own. Together, they left a gap nobody owned: how Prime talks about its value to members.

I brought both findings to leadership in a single document. The recommendation: Prime needed a framework that owned the gap between strong benefits and the weak communication around them.

There was also a value bias to address. Prime's communication leaned hard on shipping speed and the headline benefits. Members already knew about shipping; saying it again was noise. The dozens of secondary perks had low adoption and felt irrelevant when surfaced. The new system needed to be customer-backward, built from what members noticed and needed.

The counterfactual was concrete: with no shared model, the benefits would have kept shipping and the language would have kept fragmenting, with each team optimizing to its own loudest stakeholder. The framework's job was to make that fragmentation visible and replace it with a shared one.

I built the framework by winning the first fight.

The first decision was about who Prime was being measured against. Senior leadership wanted a benchmarking cohort of Costco and Walmart Plus, which would have anchored the framework to a price-comparison story. I argued for a different cohort: AllTrails, Nike, Starbucks, Thrive Market, Headspace, Target, Duolingo, Spotify. The brands members trust, and the standards Prime was being measured against whether the org said so or not.

I made the case in a deck and a working session. A Costco comparison would have optimized for price-per-benefit and produced more of the same headline-savings copy. A high-trust brand comparison would optimize for the relationship Prime was failing to build, which was the actual problem in the diagnosis. Spotify was the threat we hadn't named. The audit was approved, and that decision shaped everything downstream because it set the bar the framework had to clear.

From there, I designed the system to be answerable to four inputs at once, because anything less would have made it opinion and anything more would have made it unreadable. Every principle, tone, and rubric question started from what members noticed and needed, so the structure inherited the customer-backward stance from the inputs.

What the high-trust audit returned.

I documented the patterns from real product surfaces across the audit cohort: the language, the timing, and the trade-offs each brand made. Four behaviors showed up in every one, and they became the backbone the framework's principles were tested against.

I documented the patterns from real product surfaces: the language, the timing, the trade-offs each brand made. Below: the source material the audit was built on.

04aTrust: transparency, agency, social proof, clarity.

04bCelebration: recognition without an offer attached.

04cRelevance: value translated into the member's context.

04dEmpathy: structural, beyond a voice layer.

From four inputs to one architecture.

The architecture mapped five Value pillars through three Content Principles to nine Tones, read left to right. Writers don't pick one principle and ignore the others; they pick where the emphasis sits.

The five Value pillars cover what Prime delivers. The first three (Monetary, Convenience, Access) were familiar to the org. Trust and Emotion were the fight. Research showed they carried more retention weight than savings did. I argued the case in research review. Both pillars were added.

The three Content Principles describe how to write about that value. The argument: emotion creates consistency, confidence, familiarity, and the relationships retention depends on.

The architecture also had to be legible to every person who'd ever touch Prime content: writers, PMs, marketers, designers, eventually AI agents. So I named the surfaces explicitly. Where value communication lives, and who sees it.

Four artifacts turned the framework into a practice.

A framework on a slide doesn't ship. It needed four operational artifacts to scale beyond me, and I built each one with the people who'd use it.

Artifact 01 / The matrices.

Two operational matrices translated the principles into specific content moves for every audience-and-surface combination. Aggregated Value covered the savings dashboards and benefit summaries, while Milestone & Recognition owned anniversaries, achievements, and welcome moments. Together they answered the question every writer kept asking the brief: which tone for which surface, for which member, at which moment?

Fig. 09 Aggregated Value matrix. A writer landing on a benefit dashboard for a tenured member knows from this matrix that they're writing toward Pertinent (Contextual, Relevant). The matrix gives them the assignment in copy: personalize savings summaries to reflect their unique usage and priorities.

Fig. 10 Milestone & Recognition matrix. The 1-year anniversary surface for a tenured member maps to Empathetic (Celebratory & Delightful). The matrix is the assignment: honor their loyalty with genuine celebration that reflects years of partnership.

The framework at copy level. A 30-day welcome card for a new member, before and after:

Artifact 02 / The writing process.

Four steps with checkpoints, designed to scale to non-writers.

Artifact 03 / The rubric.

The rubric was the artifact I co-designed most closely with UX research. Working with research solidified my conviction: Prime was failing emotionally, and A/B testing alone missed it. A/B optimizes for clicks. It narrows success to single-point conversions, hides emotional response, and rewards false positives that can look like wins quarter over quarter. The framework needed a measurement layer beyond clicks. The rubric became that layer.

Structurally, it is a four-quadrant scoring instrument covering Value Clarity, Audience Alignment, Context & Timing, and Communication Style, with five points possible per quadrant for a total of twenty. Each quadrant is built from explicit yes-or-no questions a non-writer can answer.

What the rubric looks like in use. The same surface (a 30-day welcome card), scored before and after the framework took hold:

Artifact 04 / The scaling plan.

Then the part nobody talks about: socialization. I ran sessions across content marketing, retention, acquisition, and the brand team. The pattern was consistent. Agreement in the room, drift the moment people went back to their briefs. The framework needed three commitments to take hold.

The realization curve: how value moves through time.

The framework also accounted for time, since members don't experience value all at once. They move through a curve of promised, perceived, and proved, and each stage requires different content moves for different segments. This map became the briefing tool I gave PMs before any new surface review.

The hardest decisions I made.

Frameworks read clean in retrospect, but the decisions that built them never do. Three I'd defend in any interview:

The framework expanded into four member journeys.

The framework gave Prime a shared model for value. The next move was turning that model into journeys: one for every kind of member Prime had, calibrated to where they were in their relationship.

Non-Prime is a skeptic who has tried other subscriptions and needs proof that Prime is worth the mental real estate. New is in their first 30 days, looking for one genuine win they can point to before renewal becomes a question. Tenured is the renewing member at risk of taking the relationship for granted because nothing on the surface acknowledges the years they've stayed. Returning is the lapsed member the system needs to invite back without making them feel guilty for leaving. Four different reasons to engage, and four different writing jobs.

Each segment also moves through three stages of value realization. Members start with potential (what Prime promises), build perception over time (what they believe), and end with realization (what they can prove). The pillar voice matrix gave writers a target quote per stage, in member language. The copy had to earn those quotes.

Five objectives shaped every screen.

Five Value Communication Objectives became the shared brief for every surface. Designers, PMs, and writers used them to evaluate any new screen against the framework. If a surface couldn't answer at least two of these, it wasn't ready to ship.

Here's the work, surface by surface.

Member journeys live on shared surfaces. The Homepage, Search, Cart, and Email all carry every segment, but each segment needs the surface to do a different job. The framework's design decision was to keep the surface architecture consistent across segments, while letting the value moves shift segment by segment.

Surface 01 / Homepage.

The Homepage is the first place a relationship lives or dies, and it has to do a different job for every kind of member who lands on it. For non-members, it has to inspire; for new members, it has to orient; for tenured members, it has to recognize them. Same canvas, three different greetings.

Fig. 19 Non-Prime Homepage. Lead with tangible savings and frictionless convenience. The pillar focus is Monetary + Convenience, the messaging objective is Inform & Inspire. Search, Detail, and CTYP carry the same logic forward, building a continuous case from awareness to commitment.

Fig. 20 New to Prime Homepage. Same canvas, different work. Welcome and Orientation lead. The tone shifts to celebratory and empowering. Pillars become Convenience + Access + Emotion. Objective becomes Guide & Empower. Members feel seen the moment they land.

Fig. 21 Tenured Homepage. The work shifts from persuasion to recognition. Anniversary milestones, benefit re-surfacing, and emotional reaffirmation. Pillars become Emotion + Trust + Monetary. Objective becomes Reinforce & Reward.

Surface 02 / Search and detail.

Search and detail pages are where intent meets value. The framework treated these surfaces as proof moments. Every Prime badge, every savings callout, every shipping promise had to earn its real estate by being timely and contextual.

Fig. 22 New member journey across Search, Detail, Cart, and Checkout. Each surface does a discrete job: Value Guidance on Search, Membership Re-enforcement on Detail, Ease and Savings reinforcement in Cart, Simplify and Confirm at Checkout. The journey compounds proof at every step.

Fig. 23 Tenured member journey across Detail, Cart, and CTYP. Decision moments quantify accrued value ("$42.50 saved this year"). Cart aggregates lifetime impact. Order confirmation surfaces customer value metrics across savings, deliveries, and orders.

Surface 03 / Cart and checkout.

The framework's most personalized work showed up in cart and checkout. These are the surfaces where members pay, and where Prime's value has to make its strongest case.

Fig. 24 Non-Prime cart and post-purchase moments. Even non-members see Prime's value clearly: $6.99 missed savings on this order, $230 potential savings on delivery last year, $46 missed savings on exclusive deals. The framework named the cost of not joining without nagging about it.

Surface 04 / Email and account.

Email and account surfaces are where members spend time outside the buying flow. The framework treated these as recognition moments. Less selling, more reflection. Members revisit these surfaces precisely because they want to feel the membership is working for them.

Fig. 25 New member email and account moments. Order emails celebrate and educate. The welcome email bridges joining and believing. Value recap surfaces tangible returns ($230 saved, $46 in deals). Each touchpoint converts data into celebration.

Fig. 26 Tenured member account and recap moments. Account hub reflects progress. Order history embeds ease. Member emails turn transaction data into a story of achievement. Membership recap anchors longevity in measurable proof.

The hypothesis: if a rubric can score copy, a model can generate it.

Most loyalty programs at this scale celebrate the same way: a generic anniversary email, a discount code, a thank-you that feels machine-written even when it isn't. The framework gave us a chance to do something different, because every piece of it (the pillars, the principles, the matrices, the rubric) had been designed from the start to be machine-parseable. The question I brought to leadership was whether we could prove that by handing the framework to a language model and letting it generate celebration copy at the moment a member hit a milestone, with quality controlled by the same rubric a human writer used.

This had never been done at Prime. Generative copy in production was happening in pockets, but nothing had attempted to direct an LLM through a multi-input content framework with cross-functional approval baked into the pipeline. The reason I pushed for this work was that scale was the only honest test of the framework. If it held under machine generation, it was real. If it didn't, the team would learn faster from that failure than from another quarter of human iteration.

The governance work was the real unlock.

Generative content in a regulated environment doesn't ship because the model is good. It ships because the right people have agreed in advance on what the model is allowed to do, and on how to verify the model did that. For Milestones, that meant aligning four distinct partners before a single celebration card went live, with my role being to hold the center and translate between them.

Each partner contributed a non-negotiable. Prime Video would not allow credit language that overpromised on catalog access. Brand would not approve copy that drifted from Charm & Disarm voice. Legal would not approve celebration claims that risked being read as transactional inducements in regulated markets. Data Science would not run a pipeline whose outputs couldn't be deterministically scored. The framework gave us a shared language to honor every one of those constraints inside a single artifact, which is what made the project shippable.

The system shipped three flavors, two variants, and five surfaces.

The first launch covered three milestone flavors that mapped to different stages of the member relationship. The 1-month anniversary celebrated early belonging, when a new member is still deciding whether Prime is for them. The 1-year anniversary celebrated proven loyalty, where the work shifted from persuasion to recognition. The "just because" surprise was the most interesting test, because it ran on no anniversary at all and was triggered by accumulated value (savings, deliveries, streaming hours) rather than time.

The 1-month anniversary, in two variants.

The 1-month flavor showed up first as a personalized member page (PMP) hero, a Your Orders banner, and a pop-up triggered on entry. The incentivized variant carried a Prime Video credit; the non-incentivized variant was pure recognition. Both were generated against the same Empathetic principle but emphasized different tones, with the incentivized version leaning Celebratory and the non-incentivized leaning Considerate.

Fig. 30 1-month anniversary, incentivized variant. "Cheers to your first month of Prime!" carried across PMP, Your Orders, and Pop-Up, with a $6 Prime Video credit attached. Each surface adapted the headline length and CTA placement, but the framework's tone was constant.

30aPMP, incentivized: "Claim $6 Prime Video credit."

30bPMP, non-incentivized: "Thanks for being Prime, Jennifer."

30cPop-up, incentivized: catalog tile reinforcing the credit.

The 1-year anniversary and the "just because" surprise.

At 1-year, the copy shifted from "Cheers to your first month" to "Happy 1-year with Prime," and the visual language gained a celebratory weight that recognized the relationship had earned more emphasis. The "just because" flavor was the riskiest test, since it had to feel earned without any anniversary to anchor on. The framework solved that by tying the celebration to accumulated value: "Your membership just paid for itself" when savings crossed a meaningful threshold during a Prime Big Deals Day.

31a1-year pop-up. The anniversary the framework rewarded with weight.

31b"Just because" PMP. Tied to accumulated savings on Prime Big Deals Day.

31cSavings tab. Where the proof of value lived in numbers.

Push and reminder copy.

Push notifications carried the most stylistic risk because they reach members outside the app, on a lock screen where every word counts. The framework's Empathetic principle constrained the LLM toward gratitude rather than urgency, and the reminder logic was tuned to surface only when a credit was about to expire, so the messaging never read as nagging.

32aPush, gratitude variant. Lock-screen tone, generated against Empathetic.

32bPush reminder, only when the credit is about to expire.

32cPop-up, non-incentivized close. Recognition without an offer.