AI-Driven Workflows and Tools
Most people use AI in one-off moments.
Ask question → Get answer → Close tab
That is useful, but it is not a system.
A workflow is a repeatable series of steps that handles a type of work every time it appears.
The difference:
| One-off AI use | AI-driven workflow |
|---|---|
| Solves one task | Handles a type of task reliably |
| Output varies a lot | Output becomes consistent |
| Starts from zero each time | Starts from a designed system |
| Lives in chat history | Can be saved, shared, improved |
| User dependent | Team can use it |
1. 🗺️ Anatomy of an AI-Driven Workflow
Every workflow has five parts.
1. Input → What enters the system
2. Prompt → What instructions guide the AI
3. AI Processing → What the model does
4. Review → Human checks the output
5. Output → What is acted on or sent
None of these steps can be skipped if the workflow is to be reliable.
| Workflow part | What goes wrong if you skip it |
|---|---|
| Input | AI has no context. Output is generic. |
| Prompt | AI guesses. Quality is random. |
| AI Processing | Nothing gets done faster. |
| Review | Errors reach the world unchecked. |
| Output | Work gets done but nothing changes. |
2. 🔧 Three Workflow Patterns You Can Build Today
Pattern A — Draft and Approve
Best for: replies, posts, messages, summaries
Situation arrives (enquiry, complaint, request)
↓
Paste into AI with prompt template
↓
AI drafts a response
↓
Human reads, edits, approves
↓
Response is sent
Time saved: 60-80% of writing time. Human still responsible: Yes.
Pattern B — Read and Extract
Best for: long documents, meeting notes, feedback forms, recordings
Raw material arrives (transcript, notes, feedback)
↓
Paste into AI with extraction prompt
↓
AI pulls out key points, decisions, or action items
↓
Human scans and confirms
↓
Summary is stored or shared
Time saved: reading and organising time. Human still responsible: Yes, for what gets acted on.
Pattern C — Create and Reuse
Best for: course content, quiz questions, revision notes, templates
Source material available (chapter, recording, syllabus)
↓
Use a reusable prompt to generate structured output
↓
AI creates notes / questions / outlines
↓
Teacher or creator reviews and adjusts
↓
Content is stored for reuse
Time saved: content creation time, every batch. Human still responsible: Yes, for accuracy and level.
3. 🛠️ Tools — What to Use for What
You do not need to use every tool. You need to pick the right tool for the job.
| Tool | Best used for | Not ideal for |
|---|---|---|
| ChatGPT | Explaining, drafting, brainstorming, notes | Verified facts, live data |
| Claude | Long documents, careful drafts, nuanced analysis | Quick one-liners |
| Notion AI | Organising notes, summaries inside Notion workspace | Building automated flows |
| Google Gemini | Connected to Google Docs and Drive workflows | Standalone creative drafting |
| Make / Zapier | Connecting apps — e.g. form → AI → email | Direct AI conversations |
| Perplexity | Research with sources and citations | Creative writing or drafting |
Simple rule for beginners:
Start with one tool.
Master the prompt.
Add a second tool only when you hit a clear limit.
4. 🏗️ Building Your First Real Workflow — Step by Step
Pick one repeated task from your work or studies. Build this:
Step 1 — Name the task
What is the task?
How often does it appear?
What does the output look like when done well?
Step 2 — Design the prompt
Role: Act as [relevant role]
Context: [background about the situation]
Task: [what AI should do with the input]
Format: [how output should be structured]
Constraints: [what to avoid]
Step 3 — Test with three real examples
Run the workflow on three actual cases from the past.
Check: Is the output useful? What needs adjustment?
Step 4 — Add the review step
Decide: Who reviews the output? How long should that take?
Step 5 — Save and reuse
Store the prompt template somewhere accessible.
Give it a name. Use it next time the same situation appears.
5. 📐 Workflow Design Mistakes to Avoid
| Mistake | Why it hurts | Better approach |
|---|---|---|
| No review step | Errors reach the world unnoticed | Always assign a human to check |
| Prompt too vague | Output is inconsistent and generic | Add role, context, format, constraints |
| Too many tools at once | Complexity hides quality problems | One tool, one workflow, one month |
| Automating judgment work | Decisions lack values and context | Keep AI on preparation tasks |
| Never updating the prompt | Quality drifts over time | Review and improve after 20 uses |
Task: Convert class recording into student revision notes
Prompt template:
Act as a patient teacher creating revision notes.
Input: [paste transcript or rough notes here]
Audience: Class 10 students, mixed levels.
Format: Headings, key concept in bold, one example per concept, 5 revision questions at the end.
Avoid: Jargon, formulas unless essential, long paragraphs.
Review: Teacher reads the output for accuracy. Adjusts examples to match what was taught.
Reuse: Same prompt every batch. Saves 90 minutes per class.
6. 📈 From AI User to AI Builder — The Real Shift
The brochure calls this course a path to becoming an AI builder.
Here is what that shift actually means:
| AI user | AI builder |
|---|---|
| Asks AI questions | Designs prompts for repeated situations |
| Gets one answer | Creates a system that works repeatedly |
| Fixes bad output by asking again | Fixes bad output by improving the prompt |
| Uses one tool | Connects the right tools for the right job |
| Works alone with AI | Creates workflows others can use |
| Starts from zero each time | Builds on saved systems |
The shift is not technical. It is a mindset.
You stop asking: "What should I ask AI today?"
You start asking: "What repeated work in my environment needs a designed system?"
7. 🗺️ Module 6 — Full Map at a Glance
| File | What it covered |
|---|---|
| M6-A | Decision-making support, finding the hidden tax, automation targets, human-in-the-loop |
| M6-B | Workflow anatomy, three workflow patterns, tools, building your first workflow, user to builder ← you are here |
✅ Recap
- A workflow handles a type of task reliably — not just one task once.
- Every workflow needs: Input → Prompt → AI → Review → Output.
- Three starter patterns: Draft and Approve, Read and Extract, Create and Reuse.
- Pick one tool, master the prompt, then add tools only when needed.
- The shift from user to builder is a mindset: stop asking one-off questions, start designing repeatable systems.