Back to results
Explore the library298 guides total · goals, work & tasks
By goal

Choose what you want to achieve.

By work or interest

Choose a setting you work or spend time in.

By task

Choose the kind of help you want.

Counts show all available guides. Filters combine to narrow your results.

Communicate clearlyGuide

Explain an unfamiliar work process with a careful analogy

Use a familiar comparison, then state where it could mislead.

Illustrative resourceNot tool-testedPeople explaining a routine process to a new colleague
What you’re working towards

A plain explanation, a bounded analogy and the point where that analogy stops working

Download playbook .md

Your choice also saves this guide’s current worked-example checkmarks. Only this browser; no account or sync. View saved guides

Saving needs JavaScript. Reading and downloading this guide does not save it.

Make a start

One step at a time.

3 steps

Start with the synthetic worked example or other non-sensitive inputs. Run one prompt at a time in your chosen AI tool. Replace any bracketed placeholders with the requested material, check each reply, and supply the source or earlier outputs that step needs. Paste them again if the tool lacks that context.

Start with the synthetic example, then adapt each prompt to your task.

01

Open a chat and use the complete sample

Open https://chatgpt.com. If you have access, choose New chat. Copy all the instructions below (the prompt), including the SAMPLE INPUT, into the message box and send it. You do not need to upload a file. You should see a source-faithful explanation, a short familiar analogy and its limitations. The wording can differ from the worked example, but the facts and constraints must agree. If you cannot access this service, use another text assistant available to you; account requirements and limits may differ.

Your starting prompt
Explain the editorial process in plain language, then use a restaurant-order analogy to make the stages memorable. Explicitly identify the important ways the analogy does not match. Keep the explanation under 220 words. Use only the supplied facts; mark missing information rather than inventing it. Return written text only. Do not send, publish or change anything in another service.

SAMPLE INPUT
Made-up example for practice. All people, organizations, records and product behavior below are fictional.

Fictional editorial process: requests are recorded in one queue. The editor chooses what to work on according to relevance and available time, not strictly arrival order. Selected items become drafts. A second person reviews a draft before publication. Some drafts are sent back for changes. Unselected requests are not promised publication. Need a plain explanation, a restaurant-order analogy and a clear limit to the analogy. Do not infer delivery times, payment, guaranteed acceptance or automatic approval.
02

Compare, correct and save

Compare the answer with the complete sample input and the checks below. Selection depends on relevance and available time, not first-in-first-out order. If a fact is missing, changed or invented, paste the correction prompt below into the same chat. Read the revised result again; if it still fails, correct the text yourself before using it. Copy the reviewed result into a new note or text document. Keep real publication, decisions and sending for a separate human review.

Your starting prompt
Check your previous answer against the SAMPLE INPUT in my first message. Test each point below. For a failure, show the problem and then return a complete corrected answer; for a missing source fact, keep it explicitly unknown. Do not invent a successful check.
- Selection depends on relevance and available time, not first-in-first-out order.
- Another person reviews before publication, and revisions remain possible.
- The analogy explicitly rejects guaranteed acceptance, payment implications and promised completion times.
03

Optional: use your own facts

Open a new chat. Copy the prompt below and replace [PASTE YOUR INPUT HERE] with your own non-sensitive source text, facts and limits for this task. Include any desired headings, count or length. Send the whole message. Expect the same kind of written result, using your facts. Check every source fact and limit yourself; the example’s names and totals do not apply. If a detail differs, show the exact mismatch and ask for a complete correction. Save the checked draft before any separate decision to use or send it.

Your starting prompt
Explain my supplied process in plain language, then use the analogy I request below. Map the stages and explicitly explain where the analogy stops fitting. Follow my word limit. Do not turn a metaphor into a factual claim about the process.

Use only my input. Ask for information needed to finish rather than guessing. Return written text only; do not send, publish, book, submit or change another service.

MY INPUT
[PASTE YOUR INPUT HERE]
Optional: improve the result

Check the reader’s understanding

Use simple questions to catch the most likely misunderstanding. This extension uses the worked example. Return to that example chat, or paste its input and your checked example answer into a new chat first. Do not apply its sample values unchanged to your own input.

Advanced prompt
Write three short comprehension questions about selection order, review and publication guarantees. Include answers based only on the actual editorial process, not assumptions from the restaurant analogy. Keep the same SAMPLE INPUT from my first message unless I explicitly replace it.
Show, then try

See the shape of the result.

This input is synthetic. The output is a written illustration of the intended result, not a verified AI-tool run.

The starting point

Synthetic input
Made-up example for practice. All people, organizations, records and product behavior below are fictional.

Fictional editorial process: requests are recorded in one queue. The editor chooses what to work on according to relevance and available time, not strictly arrival order. Selected items become drafts. A second person reviews a draft before publication. Some drafts are sent back for changes. Unselected requests are not promised publication. Need a plain explanation, a restaurant-order analogy and a clear limit to the analogy. Do not infer delivery times, payment, guaranteed acceptance or automatic approval.

Copies text only. For image or file tasks, use the source files named in the steps too.

Download source .txt

The intended result

Illustrative output
Worked example written for this guide, not output recorded from a live AI session.

Plain explanation
Requests go into one list. The editor selects work that is relevant and fits the time available. A selected item becomes a draft. Another person reviews it before publication and may return it for changes. Being on the list does not guarantee publication.

A useful analogy
Imagine a restaurant with a list of possible dishes to prepare. The editor is like the person deciding which dishes the kitchen will work on. Drafting is the preparation stage, and the second review is like checking a dish before it leaves the kitchen. A dish that needs changes goes back for more work.

Where the analogy stops
This is not a normal promise to fulfill a customer’s paid order. Requests are not necessarily selected in arrival order, may never be selected, and have no promised completion time. The comparison helps explain stages; it does not create a service guarantee.
Download result .txt
You’re the final check

Check the worked example.

These checks use the worked example and its particular facts. With your own material, check your actual names, numbers, sources and rules; do not reuse the sample’s values as the answer.

Unsaved checks stay in this tab and reset when you reload. If you choose Save guide, its current example checkmarks are kept in this browser when storage is available.

A few things to watch for.

  • Analogies can smuggle in rules from the familiar situation. State the most important mismatch.
  • Do not let the comparison replace the actual process description.

What has been checked?

Documentation
No dated source review recorded.
Included files
No scoped artifact-check record.
AI workflow
Not run in a recorded consumer-AI workflow.
Time savings
Time savings not measured

Copy these instructions

Your browser blocked automatic copying. Select the text below and copy it.