PlaysbyMoat8
Back to the library
The workflow guideMarketing

Turn parallel research into an illustrated expert post

Explore a technical topic from several angles, then combine the findings into a draft in the author’s established voice with visual options.

6 implementation stepsIntermediate

How this works

Explore a technical topic from several angles, then combine the findings into a draft in the author’s established voice with visual options. A technical expert post needs an argument the author actually endorses, not a collage of research summaries in an approximate voice. Parallel research can broaden coverage, but contradictory sources and speculative implications must be resolved before illustration makes the claims look authoritative.

Assign distinct research angles, merge evidence into a claim map, and draft around one author-approved point. Apply the author's style using supplied examples. Generate visual options that clarify the argument without depicting uncertain mechanisms as established fact.

Before you start

Author's point

Identify the intended insight and audience rather than inventing an opinion.

Research scope

Choose the technical, recent-development, and business angles needed.

Style and visual guidance

Provide approved writing examples and image constraints.

Prepare the inputs

topic_brief
Required

Question and angle

State what the post should help readers understand.

research_sources
Required

Evidence with dates

Distinguish primary findings from commentary.

author_notes
Required

Actual opinions or experience

Do not manufacture personal anecdotes.

style_examples
Required

Approved posts

Extract reusable writing choices.

visual_brief
Required

Purpose and format

Avoid misleading scientific or product depictions.

Implementation, step by step

  1. Divide research by question

    • Assign non-overlapping angles with explicit outputs.
    • Keep source dates and access limits in each research note.

    Checkpoint: A coordinated research plan.

  2. Merge and challenge findings

    • Combine claims, remove repeated coverage, and identify contradictions.
    • Trace consequential assertions to primary evidence before using them in the argument.

    Checkpoint: A reviewed claim map.

  3. Choose the central argument

    • Connect the research to the author's supplied perspective and audience need.
    • Separate evidence-backed explanation from the author's interpretation.

    Checkpoint: A focused outline.

  4. Draft in the author's voice

    • Use the approved style profile for pacing, hooks, and paragraph structure.
    • Preserve factual qualifications and avoid invented first-person experience.

    Checkpoint: An original post draft.

  5. Create explanatory visual options

    • Propose illustrations that support the central idea rather than decorate unrelated themes.
    • Use available image tools or provide a design brief; label conceptual imagery where needed.

    Checkpoint: A small visual shortlist.

  6. Review the complete piece

    • Check text and image together for unsupported implications, mismatched tone, and factual errors.
    • Prepare the selected version for the normal editorial approval process.

    Checkpoint: A coherent illustrated draft.

Decisions along the way

Research does not support the intended thesis

Revise the thesis or frame it as an open question.

The author has no supplied personal experience

Use analytical language instead of a fabricated anecdote.

A visual implies a measured result

Replace it with a clearly conceptual or accurately data-backed image.

What you will produce

illustrated-expert-post.md

Markdown

An editable post package.

Include: argument · body · source_notes · visual_option · open_checks

research-claim-map.csv

CSV

Keeps parallel research reviewable.

Include: claim · angle · source_ref · evidence_type · limitation · status

Check the result

  • Trace technical claims to reviewed sources.
  • Verify first-person statements come from author input.
  • Check illustration meaning against the text.
  • Review style without sacrificing clarity or caveats.

When something goes wrong

Parallel researchers repeat the same secondary source

Find the original evidence and reduce apparent corroboration.

The draft overstates a preliminary result

Restore the study's actual scope and uncertainty.

Generated image introduces false labels

Remove or replace labels through controlled design.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Draft an expert post about automating document review.

Inputs

Synthetic example. Synthetic research describes a limited benchmark; the author says human exception handling remains important.

Expected result

Synthetic expected result. The post explains the benchmark's limits and the author's review principle. It does not invent a personal deployment or illustrate perfect autonomous accuracy.

Run a small pilot

Start small

One topic with a few distinct research angles and visual options.

Record the baseline

Record research consolidation and editorial correction effort.

Agree success criteria

Agree factual support, authentic voice, and visual clarity.

Stop or revise

Stop publication when the central claim or author attribution is unresolved.

Keep the scope clear

  • Research sources do not authorize copying their figures or long passages.
  • A draft does not authorize publishing in the author's name.

Check before using

The recorded example is a live demonstration, not measured campaign performance. Verify technical claims, avoid invented quotations, and review image meaning and rights before publishing.

Business activities

  • Create and publish content

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Research question and time window · Approved writing examples · Audience and visual brief

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗