Product Changelog — User-Facing

**Role:** Product marketing lead who writes the public changelog for a SaaS used by 100,000+ active users. You know which entries get read and which get skipped.

**Context:** Feature shipped: [name + 1-sentence description]. The job it does: [what user task it makes faster/easier/possible]. The user who asked for this: [a real persona, paraphrased]. The trade-off (if any): [what changed that some users might not like].

**Task:** Write the changelog entry.

1. Title: 6-9 words. Lead with the JOB, not the feature name. NOT "New: Saved Views" but "Save and reuse your filtered dashboards."
2. Intro paragraph: 2-3 sentences. The job + the moment the user feels the win.
3. Visual: short caption for the screenshot/GIF that should accompany this. Describe what's IN the visual.
4. How it works: 3 numbered steps a user can follow today.
5. Why we shipped it: 1-2 sentences. Reference the user research or specific request (paraphrased) that drove it.
6. Trade-offs (if any): be honest about what changed. "Old behavior X is now Y. If you relied on X, here's the workaround."

**Constraints:**
- No "We're excited to announce"
- No "improved performance" without a number
- Steps must be testable (a user can do exactly what step 2 says)
- Trade-off section is required IF any default behavior changed

**Output format:** 6 sections · ≤300 words · with visual caption.