Prompt vs workflow: when one ask isn't enough

Beginner · 5 min · Decide when a job needs a workflow instead of a bigger prompt.

  • workflows
  • process design

A prompt asks once; a workflow runs the same reliable sequence every time. If the job has repeatable stages, a checkable output and at least one place where mistakes must be caught, a longer prompt will not save you — the shape is wrong. Prompting harder optimises one conversation; a workflow optimises the process that produces the conversation’s output.

Three questions

  1. Does it repeat? A one-off request needs a prompt. The same job again next week — same inputs, same shape of output — is asking for a process.
  2. Does an output feed the next input? Long jobs are chains: extract the decisions, then check them, then write the summary from the checked list. Each stage deserves its own message and its own verification.
  3. Where does a mistake get caught? If the honest answer is “somewhere before it sends”, that somewhere is a step. Name it, place it, and give it a human when the consequence is real.

Why a bigger prompt is not a workflow

A mega-prompt keeps every rule in one context, so a wrong turn is hard to locate: was it the extraction, the arithmetic or the tone? It also has no place to stand: no checkpoint to insert a human, no artefact you can approve before the next stage consumes it, and no way to test one step alone. Staged work fails smaller. When the summary is wrong, you already have a verified table to blame — and to fix. Stages also change who can help: a colleague can own one step without touching the others, and the review lands on someone’s desk on Tuesday instead of hiding inside a Friday re-read.

Weak prompt

Here are forty pages of meeting notes, the CRM export and last quarter's deck. Write the whole quarterly review, make it good, and don't miss anything important.

Stronger prompt

Stage 1 of 3. From the attached notes, extract every decision with its owner and date as a table. Flag anything ambiguous or missing. Do not summarise yet — I will check this table before we continue to the narrative.

Why the stronger one works
  • The mega-prompt hides its own failure inside one long answer; the staged prompt produces an artefact you can inspect before anything is built on it.
  • “Do not summarise yet” keeps stage 1 doing one job — extraction — instead of drifting into the report.
  • The human gate is explicit: the table gets checked before stage 2 consumes it.
Which job is asking for a workflow rather than a better prompt?

Practice

Judge the two plans

Two colleagues propose ways to produce a weekly competitive digest: one email each Monday covering pricing, product and messaging changes across your market. Read both plans and judge which one will still work in month three.

Compare the plans against the workflow criteria, then choose the one you would put your name on.

Output A

Plan A — “Each Monday I will paste everything I have into one long prompt: the competitor pages, the newsletters, the pricing sheet, and ask for a digest of anything important. If the result feels thin, I will add a sentence like 'be thorough and cover all the changes'. I will send it if it reads well.”

Output B

Plan B — “The digest runs in four steps. Inputs are fixed: three competitor pages, their changelogs and the pricing sheet, saved in one folder each Friday. Step 1 extracts any change as a table row: source, date, what changed, quote. Step 2 filters to pricing, product and messaging — the three areas our team acts on. Step 3 drafts two-sentence entries from the filtered table. Step 4 is my review before anything sends: I check each entry against its quote. If a source is missing or unreadable, the row is flagged and the digest ships with a 'not checked this week' note.”

Rubric — answer each question for both outputs before deciding

  • The inputs are named and arrive in a predictable state
  • Each step does one job, and its output is the next step's input
  • There is a specific check before the digest leaves
  • A missed or broken input has a defined path instead of silent silence
Which output would you ship?
Hint

Look for the check step — a place where a human or a rule compares the output to the source.

A plan that cannot fail visibly will fail invisibly: ask what happens on a broken week.

Transfer

  • Reporting cycles: fixed inputs, staged extraction, human gate before distribution.
  • Onboarding documents: stage 1 gather facts, stage 2 draft, stage 3 check against a rubric.
  • Any “AI keeps missing stuff” complaint: look for the missing check step, not a missing adjective.
  • Personal habits: a Sunday review with three fixed steps is a workflow too.

Key takeaways

  • A prompt asks once; a workflow repeats a sequence you designed and can test.
  • If outputs feed the next stage, split the stages — each gets its own check.
  • Find the gate before you build: where does a mistake get caught, and by whom?

Next

Finished this lesson?