Lesson 14 · Illustrative scenarios
Evaluate a process on your own data
These examples are not customer references or documented company results. Use them to plan a pilot and measure your own outcome.
- Before
Manually draft posts from a catalogue.
- AI task
AI creates 3 drafts using only the current catalogue.
- Human review
A person checks products, prices, material rights and tone before publishing.
- Measurement
Time to an accepted draft and number of revisions.
Showcase - What you can do in a company
8 complete ChatGPT Work workflows
One example is enough for a first trial. Read its conditions, use test data and record review time as well as execution time.
PROBLEM
The board deck gets built the night before. Data sits in three files, the conclusions live in one person's head, and the slides are glued together in a rush.
GOAL
A finished slide set with a narrative, charts built only from the data provided, and speaker notes.
WORKFLOW
INPUT
- Source material: report, spreadsheet, notes
- Audience and meeting context
- The one sentence that must stick
- Target number of slides
TOOLS
OUTPUT
- Slide outline approved before any copy is written
- Full slide content with speaker notes
- Charts together with the data behind them
- List of spots marked [TO BE FILLED IN BY A HUMAN]
PROMPT
Full workflow: ROLE / GOAL / INPUTS / TOOLS / PROCESS / OUTPUT / CONSTRAINTS / QA / APPROVAL GATE
ROLE You are a consultant who builds board-level decks. You write tersely and always tie numbers back to a source. GOAL Build a presentation on [TOPIC] for [AUDIENCE] for the meeting [WHEN / CONTEXT]. Final result: a finished slide set with speaker notes. INPUTS - Source material: [UPLOADED FILES / LINKS / PASTED TEXT] - The one message that must stick: [ONE SENTENCE] - Number of slides: [e.g. 10-12] - Language and tone: plain, factual, no marketing fluff TOOLS - Reading the uploaded files - Data analysis and charts - Web search only to fill in missing market context - Reading an existing deck through the Google Drive connector, if it is connected. - Deliver the result as a downloadable deck file or as a document with the slide structure. Do not assume you can write changes straight into a Google Slides file - if that is not available, say so plainly and hand me the file. PROCESS 1. Read all material and list what it actually supports and what is absent from it. 2. Propose a storyline: problem → data → conclusion → recommendation → next step. 3. Show me the slide outline (title + one sentence per slide) and STOP. 4. After my approval, write the full slide content plus speaker notes. 5. Add charts only where I gave you numbers. Never chart data you were not given. 6. Finish with a "Questions we must be able to answer" slide. OUTPUT - Slide outline (step 3) - Full slide content + speaker notes - List of charts with the data behind each - List of spots marked [TO BE FILLED IN BY A HUMAN] CONSTRAINTS - Do not invent numbers, client names or quotes. No data = write "no data". - Max 6 lines of text per slide. - Do not copy whole paragraphs from sources - summarize. QA Before showing the result, check and report under a "QA" heading: - does every number name its source (file + location), - does every slide carry one idea, - does the narrative lead to the recommendation, - what was missing from the material for the deck to be complete. APPROVAL GATE Stop after the outline and wait for my "OK". Do not create or overwrite any deck file without my explicit approval of a specific location.
SAFETY - where the agent must stop
- Stop after the outline - copy is written only after approval.
- Writes a deck file only to a named location and only with consent.
- Never overwrites existing decks.
- The deck does not leave the company without a human decision.
READ → DRAFT → REVIEW → APPROVE → WRITE / SEND
EXERCISE
Take one report you recently presented. Run the workflow and compare the agent's outline with your own. Write down 3 differences.
KPI - does this automation make sense?
Time saved: hours this deck used to take vs. now
Manual steps: how many times you had to switch between files
Errors: how many slide numbers needed a fix after verification
Delivery time: from receiving the data to a finished file
Measure these four on your own process. We do not publish invented savings numbers.
PROBLEM
The export sheet has 12,000 rows, three date formats and duplicates. Half a day goes by before anyone computes anything meaningful.
GOAL
A short report answering one business question, with metrics, charts and clearly flagged uncertainty.
WORKFLOW
PROBLEM
A list of 200 trade-show leads sits in a sheet. The rep contacts the names they recognize; the rest go stale.
GOAL
A weekly priority ranking based on public buying signals, plus drafted first outreach.
WORKFLOW
PROBLEM
The team reads the same newsletters, everyone misses something different, and an important industry change lands two weeks late.
GOAL
One message a day, readable in 3 minutes - only what can actually affect our work.
WORKFLOW
PROBLEM
At month end someone digs through the mailbox, hunts for invoice attachments and retypes amounts into an accounting summary.
GOAL
All invoices in one folder, consistent file names, a roll-up summary and a gap list.
WORKFLOW
PROBLEM
We learn about a competitor's price change from a customer during a sales call - usually too late to prepare a response.
GOAL
An alert only when something material changes: pricing, packages, offer headline, a new feature or a new market.
WORKFLOW
PROBLEM
A market entry decision rests on a few articles someone read over the weekend. Nobody knows what is fact and what is somebody's opinion.
GOAL
A report with a clear split: what we know and from where, what is merely likely, and what we do not know at all.
WORKFLOW
PROBLEM
Picking a tool or vendor ends with two quotes and a rushed decision, because nobody had time to compare terms.
GOAL
A comparison of at least three options against agreed criteria, plus a recommendation and a realistic alternative.
WORKFLOW
Availability depends on your plan, region, workspace and administrator configuration.