Create a blog outline from your team's own notes

An original article should answer a real question using evidence or experience you can substantiate. Start from owned notes rather than paraphrasing someone else’s post.

Set the editorial constraints

Give the writing teammate a clear audience, purpose and approved facts. Include a short voice sample when tone matters, and state what the draft must not promise. Save a draft file for review rather than treating a generated message as published copy. A final human edit should verify names, dates, claims and links against the source material.

Inputs for this workflow: Internal expert notes approved for publication and a reader question.

Work through the task

1. Identify the central answer and supporting examples.
2. Mark gaps that need an expert review.

A brief you can adapt

Draft an outline with a direct answer, practical example, limitations and source notes. Flag unsupported statements instead of filling them with generic claims.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Ask the subject expert whether the outline preserves the actual experience and its boundaries.

Where this approach can fail

Do not present a hypothetical workflow as a measured case study.

For the related desktop setup, see company playbook.