Share Trigger Design

Identify the emotional and functional moment that makes a user want to share, and surface a share affordance exactly then.

Why

Sharing is driven by emotion (pride, amusement, frustration) or function (collaboration, evidence, saving for later), and the trigger must match the dominant emotion at that moment. A 'look what I built' moment is pride — the share UI should celebrate the achievement and make the output look impressive. A 'I need help with this' moment is frustration — the share should pre-fill a question and target a help channel. Surfacing the affordance at the wrong moment (a share button on an empty state) gets ignored; surfacing it at the right moment with the right framing converts 5-10x. The discipline is to instrument every shareable moment and A/B test which trigger framing converts best, because your intuition about which emotion dominates is usually wrong.

When

When you have 3+ identifiable shareable moments in the product. Instrument all, then optimize the highest-potential one.

How

1. List every moment the user produces a shareable artifact: saved result, completed build, won game, generated image, written doc
2. For each, identify the dominant emotion: pride (I built this), amusement (this is funny), utility (I need this), frustration (help me)
3. Design a share affordance at each moment with framing that matches the emotion: pride → "show off your build", utility → "send to a teammate"
4. Instrument every trigger with: impression, share-click, channel selected, recipient count, downstream opens and signups
5. After 2 weeks of data, rank triggers by share-rate and downstream-signup-rate; the best trigger is often not the one you predicted
6. A/B test the framing copy and the preview rendering on the top 2 triggers; the preview's visual quality drives opens
7. Make the shared artifact look impressive in the preview (rendered output, not a URL) — preview quality drives 50% of opens
8. Track the share-to-signup conversion per trigger and double down on the top 1-2; kill triggers with <1% downstream conversion

Example

# Shareable moments in a code-screenshot tool
1. Generated a beautiful screenshot  → emotion: pride
   Trigger: "Share to Twitter" with rendered image preview
   Framing: "Look at this clean code 👇" (auto-attached image)
2. Saved a snippet to share with team → emotion: utility
   Trigger: "Send to Slack" with code preview + one-click
   Framing: pre-filled "Check this snippet — reuse in our repo"
3. Got an error, want help              → emotion: frustration
   Trigger: "Ask the community" with error pre-filled
   Framing: posts to Discord #help with the error + repro

# After 2 weeks (ranked by downstream signup rate)
1. Pride/Twitter: 8% share-rate, 12% downstream signup → KEEP, optimize
2. Utility/Slack:  3% share-rate, 34% downstream signup → KEEP, optimize
3. Frustration/Discord: 1% share-rate, 0% signup → KILL (helps retention, not growth)

Common Problems

⚠Adding a generic 'share' button in the header — it fires at no particular emotion and converts near zero.
⚠Using a URL-only preview instead of a rendered preview of the artifact; URLs get 5% open rates, rendered previews get 40%+.
⚠Assuming the 'pride' moment is the highest-converting trigger without data; often the 'utility' moment converts 3x better.
⚠Not instrumenting downstream signups per trigger, so you optimize for shares (a vanity metric) instead of acquired users.

Best Practices

✓Match the trigger framing to the dominant emotion at the moment (pride/utility/frustration); a mismatched frame converts poorly.
✓Render the shared artifact in the preview, not just a URL; preview quality drives 50% of open rates.
✓Instrument downstream signups per trigger and optimize for acquired users, not share count; shares are a vanity metric.
✓Kill triggers with <1% downstream conversion even if their share-rate looks good; the goal is users, not shares.