Shareability

Help users share a meaningful outcome when they want to tell its story.

What it is

Shareability is the deliberate design of a moment where a user can export or post something they made or achieved—a finished design, a completed goal, a generated insight—in a form that tells their story rather than the product’s. The share card, the export link, the “download my results” button: all exist to let the user’s accomplishment travel with enough context that a stranger understands it, while the product’s branding stays quiet in the corner rather than taking over the frame. Unlike Referral, there is no invitation loop and no reward attached—nobody has to join anything for the share to work, and the artefact is valuable on its own even if the recipient never opens the product. The test for whether it is genuinely shareability: would the user still want to post this if the brand mark were removed?

Why it works

Peak–End Rule is the reason timing matters so much here: a completed outcome is a candidate positive peak, one of the few moments in a session strong enough to be remembered afterwards, and a share prompt offered right then extends that peak outward instead of letting it evaporate once the tab closes. It also does reflective work in Emotional Design’s sense—the level concerned with the story a person tells about themselves for using a product—because showing someone else what you made is how a private feeling of accomplishment becomes a public, remembered fact about yourself. That is a stronger driver of goodwill than almost anything a share button can add mechanically.

Skip this and a genuine peak goes uncelebrated—the user made something they were proud of, and the product gave them no way to carry that feeling anywhere, which is a missed opportunity rather than a harm. Overdo it, and the mechanism curdles into the failure Social Transmission warns about: manufactured comparison, streak pressure, or a share prompt timed to interrupt work rather than follow a real result, which turns an invitation into a performance obligation. The tell is the same one that separates a share from a billboard—if the prompt appears before value exists, or the branding crowds out the user’s own achievement, it is serving the product’s growth numbers, not the user’s pride.

When to use it

• After a genuine Success Moment, meaningful milestone, or completed creation
• When a result is useful or understandable outside the product: a chart, playlist, image, summary, or artefact
• When an existing community practice gives the user a relevant audience for the outcome

Do

• Let users preview, edit, and remove personal or sensitive details before sharing
• Create accessible, accurate formats with context that makes sense beyond the product
• Keep branding modest and preserve the user’s ownership of the story

Don’t

• Interrupt a task with share prompts before the user has experienced value
• Manufacture public comparison, streak pressure, or embarrassment to drive posting
• Publish automatically, prefill public audiences, or make sharing a condition of receiving an outcome

Founder Tip

The strongest share card makes someone look good because it reflects something real they did—not because it turns them into your billboard.

Make It Yours

1. To earn the moment:
   • What result would a user be proud, relieved, or genuinely pleased to show?
   • Does it reflect real effort, insight, taste, or progress?
2. To preserve ownership:
   • Can the user decide exactly what is included, named, and omitted?
   • Would the shared item still feel like theirs with the brand removed?
3. To make it useful elsewhere:
   • Does someone outside the product understand the result and its context?
   • Are image descriptions, readable text, and accessible alternatives available?
4. To choose timing:
   • Does this follow a completed outcome rather than interrupt work in progress?
   • Is the prompt easy to dismiss permanently or defer?
5. To protect trust:
   • Could this expose sensitive data, location, collaborators, or private performance?
   • Are we inviting expression, or creating social pressure to perform?

Related concepts

• Social Transmission
• Emotional Design
• Peak–End Rule

Further reading

• What Makes Online Content Viral? — research on the psychological drivers of sharing.
• Social Sharing — UX guidance for placing and designing sharing controls.
• Web Content Accessibility Guidelines (WCAG) 2.2 — standards relevant to accessible shareable content.
• Endorsements, Influencers, and Reviews — disclosure expectations where rewards or endorsements are involved.

Agent skill

• Primary command: /productfeeling feel — design voluntary sharing where the user’s story leads and the product stays modest
• Related commands: /productfeeling peaks-ends, /productfeeling delight, /productfeeling map
• When the agent should load this TTP: “share card”, “export achievement”, “social sharing”, “shareable outcome”, “celebration post”
• Companion handoff: Impeccable — share preview, edit controls, and accessible export formats
• Feeling north star this TTP serves: user-owned expression of real accomplishment
• Anti-goals: pre-value share prompts, manufactured comparison pressure, automatic publishing, sharing as condition of outcome
• Reference path: skill/reference/feel.md