01 / Explain the shift

From isolated tasks.To a shared workflow.

Show the structure before naming the tools.

Creators

Prepare the work

Reviewers

Resolve the open questions

Readers

Understand the result

One review boundary

accuracy · ownership · access

Prepare

Turn evidence into a clear draft.

Deliver

Share the version people can use.

Context
Tools
History
Permissions

The takeawayPeople, flow and shared capabilities form one understandable map.

Build presentation / illustrative workflow01 / 04

02 / Keep the same map

Now name the components.

Same positions.
Concrete labels.

Authoring space

Where creators prepare

Review queue

Where reviewers decide

Published view

Where readers arrive

One review boundary

accuracy · ownership · access

Draft workspace

The working version and its evidence.

Delivery channel

The approved version and its audience.

Source register
Templates
Change log
Roles

The takeawayChange the labels, not the audience's mental model.

Build presentation / illustrative workflow02 / 04

03 / Explain the handoffs

Prepare. Review. Deliver.

Make each responsibility visible.

01 / INPUT

Prepare

Gather sources.
Choose the message.
Make a first draft.

Owner: creator

→
02 / DECISION

Review

Compare the draft with the brief and evidence. Resolve what is unclear.

Owner: reviewer

→
03 / OUTPUT

Deliver

Share an approved version. Make the next action clear.

Owner: publisher

The takeawayThe diagram explains who acts, what changes, and where feedback returns.

Build presentation / illustrative workflow03 / 04

04 / Zoom into one step

Make the response concrete.

One problem.
A clear response.

PrepareReview / focusDeliver

The problem

The message is difficult to review.

The purpose, evidence and decision are scattered across the draft.

→

Explicit scope

One audience, one purpose and a clear boundary.

Source notes

Keep claims connected to their evidence.

Shared templates

Keep the structure familiar while the content changes.

Review gate

Name the decision and the person who makes it.

The takeawayUse this layout to connect a pain point to a practical next step.