Review edition · Complete text lesson. Platform screenshots are being prepared.
Suppose you could…
Give one repetitive task a head start
Turn a repeat task into a reusable prompt that does the first draft for you.
Create a reusable workflow with input requirements, review checks and a human handoff; test it on a second case and a missing-information case.
Time is a practice estimate. Pause or return whenever you need.A useful little possibility.
The final lab turns a useful one-off prompt into a small system you can use again. You’ll build a weekly-update workflow, test it twice and write down when it should stop and ask for help. Your result: a reusable workflow card and two reviewed sample outputs. It remains human-assisted, not an unattended automation.
Let’s make a start.
Minute 0–3: name the recurring task and the fields it needs. Read inputs A, B and C. Predict why C is too vague for a factual status report.
Minute 3–7: use the prompt with input A only. Review the draft against the input.
Minute 7–11: use the same prompt in a fresh chat with input B. Check that it does not carry over outdated facts from A.
Minute 11–15: test input C and save a workflow card that includes a stop rule, a review checklist and the human action required before sending.
Your sample material
Fictional training material. No real customer information needed.
FICTIONAL WEEKLY UPDATE INPUT A Done: welcome-sheet draft written. Next: ask the manager to review it. Blocker: feedback owner not agreed. Dates: none confirmed. Audience: teammates. FICTIONAL WEEKLY UPDATE INPUT B Done: the manager reviewed the draft and requested larger link text. Next: Jo agreed to revise the text by Friday; calendar date not supplied. Blocker: start date still not agreed. Audience: teammates. EDGE CASE INPUT C “same as last week, nearly ready” — no other detail provided.Download sample .txt ↓
Create a weekly update from this run’s input only. Do not use facts from earlier conversations. Use headings Done, Next and Needs attention, under 120 words total. Keep completion, proposals and commitments distinct. Do not invent dates, approvals, progress or people. If the input is too vague to support an update, ask up to three clarification questions instead of drafting. Preserve relative dates without guessing their calendar date. End with a separate “Review before sending” list of unresolved details. Do not send messages or change any external system. THIS RUN’S INPUT: [Paste input A, B or C, one at a time.]
Keep personal and confidential information out of external AI tools. Start with the sample material.
Turn a first try into your thing.
Save your improved instruction together with its required input fields, rather than saving the prompt alone. Add a stop rule: do not produce a factual report when evidence is missing.
Compare A and B. A says a review is next; B says it happened. A reusable workflow must respond to the actual input, not a remembered template story. Keep both reviewed outputs as test cases for future edits.
Pause for the “aha.”
A reusable workflow contains more than wording: it defines inputs, output, checks, exceptions and responsibility. Changing the model or prompt can change behaviour, so repeat the test cases after a change.
Generating a draft is different from sending it. You remain responsible for fact-checking and approving the communication. Do not connect automatic sending simply because two examples worked.
Useful beats convincing.
Check these against your actual output. Your answers stay on this device; this is self-review, not automated grading.
Finished your first try? Reveal a worked example ↓
Input A:
Done: The welcome-sheet draft is written.
Next: Ask the manager to review it.
Needs attention: A feedback owner and dates are not yet agreed.
Review before sending: Confirm whether a review request has already been made; don’t say it has without evidence.
Input B:
Done: The manager reviewed the draft and requested larger link text.
Next: Jo will revise the text by Friday; the calendar date needs confirmation.
Needs attention: The trial start date is not agreed.
Review before sending: Confirm which Friday before relying on the deadline.
Input C: A useful response is clarification, not a confident update. For example: “What changed this week? What is actually complete? What is the next agreed action?”
Why it works: the same workflow changes with the evidence and refuses to manufacture missing progress.
A new case. Your own approach.
Apply the review principles to these new facts, not the previous sample’s specific numbers or answers.
WITHOUT THE STARTER PROMPT: Design a reusable handover workflow for a colleague taking over a project. Define required inputs, the output headings, two review checks and one stop condition. Test it using a fictional case and then a case missing an owner. Save the two test outputs with the workflow.
One possibility leads to another.
Choose a real low-stakes task that recurs this week, using only data you are allowed to share with your chosen tool. Try the workflow independently. Record what you corrected and whether you would use it again. That independent reuse is more meaningful than collecting a completion badge.
Your reusable workflow card ↓
MY REUSABLE WORKFLOW CARD Task and intended audience: __________ Use it when: __________ Do not use it when: __________ Required inputs and allowed sources: __________ Steps / prompt: __________ Expected output and length: __________ Facts, calculations, dates and permissions I must check: __________ Stop and ask when: __________ Human approval / next action: __________ Test case 1 and expected behaviour: __________ Test case 2 / missing-input case: __________ Last checked date and tool used: __________Download workflow .txt ↓
You tried something. That counts.
Keep a note of what you made or what surprised you. It stays in this browser.