Generate customer-facing product changelog updates from Jira/Linear tickets

Create simple categories for product updates: new feature, improvement, integration, bug fix, performance update, security update, admin update, and API change. Define rules for customer-facing language: lead with benefit, avoid internal ticket names, explain who it helps, and never overstate a small fix as a major launch. Paste the relevant source material into Claude with labels for ticket, audience, benefit, release status, and approval owner, then ask for structured output instead of a polished final draft on the first pass. Make the decision explicit and leave enough context that another marketer or seller could continue the work without re-reading every source. Before moving on, check that technical details are translated accurately and nothing unreleased, internal, or customer-specific is exposed.

Export Jira or Linear tickets from the release, sprint, or date range you want to summarize. Include title, description, labels, status, linked epic, customer impact notes, screenshots if available, and owner. Exclude incomplete tickets and internal chores unless they have customer impact. Keep the work organized in Jira and Linear with fields for ticket, audience, benefit, release status, and approval owner so the next person can see how the decision was made. Make the decision explicit and leave enough context that another marketer or seller could continue the work without re-reading every source.

Paste the ticket export into Claude and ask it to classify each ticket as customer-facing, internal-only, needs clarification, or potential support note. Have it identify the user benefit, affected persona, release category, and what information is missing. Paste the relevant source material into Claude with labels for ticket, audience, benefit, release status, and approval owner, then ask for structured output instead of a polished final draft on the first pass. Make the decision explicit and leave enough context that another marketer or seller could continue the work without re-reading every source. Before moving on, check that technical details are translated accurately and nothing unreleased, internal, or customer-specific is exposed.

Open Claude and use the prepared inputs to write customer-facing entries for the approved tickets. Each entry should include a short title, one-sentence summary, customer benefit, who it affects, and optional technical note. Keep minor fixes short and reserve longer explanations for meaningful features or workflow improvements. Paste the relevant source material into Claude with labels for ticket, audience, benefit, release status, and approval owner, then ask for structured output instead of a polished final draft on the first pass. Make the decision explicit and leave enough context that another marketer or seller could continue the work without re-reading every source.

Open Claude and use the prepared inputs to turn the individual entries into audience-specific summaries: one for customers, one for customer success, one for sales, and one for internal leadership. Each version should emphasize what that audience needs to know, not repeat the same changelog copy. Paste the relevant source material into Claude with labels for ticket, audience, benefit, release status, and approval owner, then ask for structured output instead of a polished final draft on the first pass. Make the decision explicit and leave enough context that another marketer or seller could continue the work without re-reading every source. Before moving on, check that technical details are translated accurately and nothing unreleased, internal, or customer-specific is exposed.

For meaningful feature updates, add screenshots, annotated images, or simple diagrams in Canva. Keep visuals functional: show the changed workflow, new button, improved dashboard, or before-and-after state. Avoid decorative product graphics that do not help customers understand the update. Keep the work organized in Canva with fields for ticket, audience, benefit, release status, and approval owner so the next person can see how the decision was made. Create a quick preview version before polishing so layout, sequence, and message hierarchy can be judged early.

Publish the approved entries in LaunchNotes or your changelog tool. Add segmentation if only certain customers or plans should see the update. Save internal summaries in Notion and notify customer-facing teams with the sales and CS versions. Keep the work organized in Launchnotes and Notion with fields for ticket, audience, benefit, release status, and approval owner so the next person can see how the decision was made. Make the decision explicit and leave enough context that another marketer or seller could continue the work without re-reading every source.

After publishing, collect customer replies, support questions, sales feedback, and CS confusion points. Feed them into Claude to identify what was unclear and what should be explained better next time. Update the changelog writing guide based on recurring gaps. Paste the relevant source material into Claude with labels for ticket, audience, benefit, release status, and approval owner, then ask for structured output instead of a polished final draft on the first pass. Make the decision explicit and leave enough context that another marketer or seller could continue the work without re-reading every source.