The release brief
What the export includes, where it is available, who can use it, and any documented limits.
Teams / Growth teams
A launch draft
you can stand behind.
A worked example: announce a new CSV export in your own product. Build the message from approved facts, then review the exact asset before it reaches your audience.
Example workflow. Connections and live agent execution are planned.
Before assigning the task
Give the team these inputs.
Audience and voice
The intended customer, a real use case, two approved writing examples, and the preferred call to action.
Evidence
The current help article, release notes, and an approved sample export with no customer data.
A brief you can adapt
One task. A defined result.
Task: Announce the CSV export to existing customers.
Deliver: 250-word email + 80-word in-app draft.
Use: Approved release brief and help article.
Do not: Invent benefits, availability, or results.Owners and handoffs
Separate doing from reviewing.
Researcher
Extract supported facts, useful examples, and open questions from the release material.
Writer
Draft the two formats in your voice, with the same accurate scope and next step.
Editor · You
Verify claims, links, audience, and timing before approving publication.
The working sequence
How the task moves forward.
Make a small fact sheet.
List the supported export fields, access rules, limits, and instructions with a source for each. Flag missing facts before turning them into marketing claims.
Draft for one customer action.
Explain the relevant use case, how to find the export, and what to try next. Use the email for context and the in-app draft for a short, direct prompt.
Review the final versions together.
Check that both drafts describe the same feature and route to the correct help page. The editor approves the final copy, audience, channel, and release timing.
The handoff
Ask for these artifacts.
- release-facts.md — Verified claims, source links, and questions that still need an answer.
- customer-email.md — Subject line, preview text, body, and one clear call to action.
- in-app-announcement.md — Short announcement copy and its destination link.
Example acceptance criteria
Check the result against the brief.
- Each availability or feature claim is supported by the approved release material.
- The email and in-app draft use the agreed formats and word limits.
- Help links resolve to the correct instructions and the call to action is clear.
- No made-up customer quote, performance claim, or adoption figure is added.
The human decision
Review the work before acting.
The editor signs off on the exact drafts and recipient group. Sending email, publishing content, or buying advertising requires its own approved action; completing a draft is not permission to distribute it.
Put it in your plan
Use this as your first milestone.
Choose research and writing roles in setup. Add the audience, source documents, two output formats, and the publication review point to the first milestone.