AI Prompting Essentials
Get reliable results from AI assistants.
You already use an AI assistant at work. This course helps you get answers you can use on the first try, and know when not to trust them.
Your week
Welcome
Transcript
Hi, I'm Mariia, and I designed this course. A quick note first: the presenter you're watching is an AI avatar of me, created with my consent, so I can keep these videos up to date as AI tools change.
Over the next five days, you'll go from one-line requests to prompts you can reuse at work. Each day takes about half an hour: a short video, a worked example, and a real task in your own AI assistant.
This isn't a list of tips. Every day, you'll practise on a real task, and by Day 5 you'll build a prompt template for something you do every week.
Before we start: what do you use AI for most? Pick one below, and let's begin.
What do you use an AI assistant for most?
Why vague prompts fail
An AI assistant writes the most likely answer to what you asked. When you leave something out, it fills the gap with the average.
Transcript
You ask an AI assistant to write an email. It gives you something polite, correct… and useless. You rewrite half of it yourself. Today we'll see why that happens, and it's not because the tool is bad.
Here's the prompt most of us write. I ran it three times. Notice anything? Every version is fine. None of them is yours. None mentions the real reason, the new date, or who's reading.
An AI assistant doesn't know your project. It writes the most likely answer to what you asked. When you leave something out, it fills the gap with the average: the email that fits every project, which means it fits none.
So a vague prompt isn't a small problem. Every gap you leave is a decision the model makes for you, and it will always choose the safest, blandest option.
Now watch what happens when we fill those gaps. The task: tell the client the launch moves by two weeks. The context: a supplier delay, and a client who values honesty. The constraints: under 120 words, calm tone. The format: a subject line plus three short paragraphs.
Same tool, same model. The difference is the brief. And that's the key idea for this whole course: a prompt is a brief. If a new colleague couldn't do the task from your message, neither can the model.
In the next lesson you'll get the four elements as a checklist you can keep. Then it's your turn.
Anatomy of a prompt
Four elements turn a request into a brief. You don't need all four every time, but check for each one before you send.
Keep this: the Prompt brief
In the full course this is a one-page PDF to download. It also covers what is safe to paste into a prompt.
Worked example
Watch one weak prompt become a strong one, one element at a time. Every email below is real output.
Your turn: fix the prompt
You're a project coordinator. The launch is two weeks late and you need to tell the client. Improve the prompt by choosing one card for each gap, then check what the AI writes.
Try it for real
Open your own AI assistant. Pick a message you need to write this week and write the prompt as a brief.
- Open a new chat, so earlier messages don't steer the answer.
- Paste your prompt and send it.
- To change the prompt, edit your message instead of adding a new one.
Before you send, check your prompt
Quick drill
Each prompt is missing one element. Spot it.
Safe to paste?
Before anything goes into a prompt, sort it: safe, remove first, or never.
That's Day 1
A prompt is a brief. If a new colleague couldn't do the task from it, neither can the model.
Working from material
Give the model your own documents, examples and images, so the answer sounds like you.
Warm-up
Two questions from yesterday before we start.
Show, don't tell
An adjective like "professional" means something different to everyone. An example means one thing.
Transcript
Yesterday you learned that a prompt is a brief. Today we'll add the most powerful thing you can put in a brief: your own material.
Ask for a "professional" email and you'll get the model's idea of professional: formal, long, a little stiff. Your idea might be warm and short. An adjective can't tell the difference. An example can.
Instead of describing the style, show it. Paste a message you've already sent, and say: match this tone. One or two good examples do more than a paragraph of adjectives.
Your material doesn't have to be an example of style. It can be the notes you want summarised, a report, or even a photo of a whiteboard. Most assistants accept all three.
Two habits make material work. First, label it: tell the model what it is, and mark where it starts and ends. Three quotation marks work fine. Second, say what to do with it: summarise it, copy its structure, or match its tone.
And one check before you paste: documents are full of names and numbers. Remove what the model doesn't need. You learned how yesterday.
Let's see it on a real example: messy meeting notes, and a manager with two minutes to read them.
Adding your material
Three kinds of material, two habits.
Habit 1 · Label it
Say what the material is, and mark where it starts and ends. Three quotation marks are enough.
Meeting notes:
"""
Weekly sync 14 Oct. Design: homepage mockups 80% done…
"""
Habit 2 · Say what to do with it
Worked example
Messy meeting notes, and a manager with two minutes to read them. Every summary below is real output.
Pick the right example
You need a short announcement for customers. Pick the example the AI should copy, then see what it writes.
A photo as input
After a planning meeting, someone photographed the whiteboard. We asked the AI to turn it into action points.
Check it against the photo. Which row is wrong?
Try it for real
Take a document from your own work: notes, a report, or a message you want to match. Give it to your AI assistant with a clear job.
Before you send
Quick drill
Pick the material that gets the result you need.
That's Day 2
Show, don't tell. Then check what the AI copied, and what it made up.
The summary copied last week's format perfectly, and still invented a date. The table marked unclear items, and still gave a task to the wrong person. Tomorrow is about exactly this.
When the answer is wrong
Diagnose why an answer misses, choose the right fix, and check facts before you use them.
Warm-up
Two questions from yesterday.
Diagnose before you retry
An AI assistant sounds just as sure when it's wrong as when it's right. When an answer misses, find the cause before you change anything.
Transcript
Yesterday you saw the AI copy a format perfectly and still get the facts wrong. Today is about what to do when the answer is wrong.
An AI assistant sounds just as sure when it's wrong as when it's right. It added a currency to our budget, then changed it. It invented a date. None of it was flagged. Confident is not the same as correct.
When an answer misses, there's usually one of four causes. The model didn't have the facts. The limits were vague. It didn't know what good looks like. Or you asked for too much at once.
Each cause has its own fix. Add the facts. Name the limit: length, tone, audience. Show an example. Or split the task into steps. Diagnose first, then fix. Just pressing "regenerate" is a lottery.
Before you use any answer, run a three-question check. Is every fact in my material, or in a source I trust? Are names, numbers and dates exactly right? And would I sign my name under it?
One more thing to check: bias. Ask for a job ad for a "strong, young team player", and the model will describe exactly that person, and leave everyone else out. The words in your prompt shape who appears in the answer.
Let's practise on answers that look fine, and aren't.
| WHY IT MISSED | WHAT YOU SEE | THE FIX |
|---|---|---|
| Missing facts | Blanks like [date], or facts it made up | Add the facts |
| Vague limits | Too long, too formal, apologetic | Name the limit: length, tone, audience |
| No example | Right content, wrong style or structure | Show an example |
| Too much at once | Parts of the task skipped or rushed | Split into steps |
Follow up or start fresh
Once you know the cause, decide where to fix it: in the same chat, or in a new one.
Same prompt, different day
On Day 1 this exact prompt produced an email with no greeting. Today the same prompt, in a new chat, produced one with a greeting. We asked for a greeting anyway, and nothing changed.
Hi [Client Name],
The project launch date has moved from 3 March to 17 March. We want to share this change with you as soon as possible.
The delay is due to a supplier delivering later than originally agreed. This affects the timeline for the remaining project work.
We are adjusting the schedule to keep everything on track for the new launch date. We’ll keep you informed of progress and flag any further changes promptly.
Best,
[Your Name]
Worked example: the invented policy
A shop asks the AI to answer a customer question. The first answer reads like a real policy. It isn't.
Diagnose it
Three real answers from earlier in the course. For each one, pick the cause. The fix follows from it.
The leading question
If your question assumes something false, the model usually goes along with it. Read this answer. Does anything look wrong?
Meeting notes:
"""
Weekly sync 14 Oct. … Launch 3 Nov still realistic if staging is fixed by Monday. Developer to report Monday. Next sync 21 Oct.
"""
The 3 November launch was cancelled because the staging server instability put the testing timeline at risk.
At the 14 October sync, the launch was still considered realistic, but only if the staging environment was fixed by the following Monday. Since the server had already gone down twice that week, the team could not rely on having a stable environment for testing. Other work was also incomplete—only 12 of 20 product pages were written, and the homepage still needed final copy—but the critical issue identified in the notes was the unresolved staging problem.
So the key message to the team is: the launch was cancelled because the technical testing timeline could not be secured, making a 3 November release no longer reliable.
Check who it leaves out
The words in your prompt shape who appears in the answer. Two prompts for the same job ad.
We’re looking for a strong, young, and energetic team player to join our warehouse team!
What you’ll do: pick, pack, and organize products · load and unload goods · keep the warehouse clean and organized · work closely with the team
What we’re looking for: physically fit and comfortable with active work · reliable, hardworking, and energetic · team-oriented with a positive attitude · able to work in a fast-paced environment · warehouse experience is a plus
Ready to join our team? Apply now!
We are looking for a Warehouse Assistant to join our team.
What you’ll do: receive, check, and organize incoming goods · pick and pack orders · load and unload boxes weighing up to 20 kg · keep the warehouse clean · follow warehouse procedures · work scheduled shifts, including occasional evenings or weekends
What you’ll need: ability to lift boxes up to 20 kg · ability to work in shifts · basic understanding of workplace safety · ability to follow instructions · warehouse experience is an advantage
What we offer: shift-based work with a clear schedule · training and support · a safe and structured working environment · opportunities to develop warehouse skills
Try it for real
Find an AI answer you used at work this week. Check it now, the way you'd check a colleague's draft.
The three-question check
If something failed
Name the cause (missing facts, vague limits, no example, too much at once), change the prompt, and run it again. Decide: follow up, or start a new chat?
Quick drill
Name the cause.
That's Day 3
Confident is not the same as correct. Diagnose, then fix, then check.
Multi-step work
When one prompt is too much: split the job into steps, and ask for tables and checklists you can use straight away.
Warm-up
Two questions from yesterday.
Break it down
Some jobs are too big for one prompt. Split them into steps, and ask for answers in a shape you can use straight away.
Transcript
Some jobs are too big for one prompt. Today you'll learn to split them into steps, and to get answers in a shape you can use straight away.
One job, one prompt. Ask for an agenda, a materials list, a budget and an invitation all at once, and the model does each of them a little. Something gets skipped, something gets rushed, and you can't tell which part went wrong.
Instead, build a chain. Step one: the agenda. Step two: the materials list, based on that agenda. Step three: the invitation, based on both. Each step uses the one before it.
Stay in the same chat, so the model remembers each step. And check between steps: a mistake in step one travels all the way to step three.
Ask for the shape you need. An agenda works best as a table: time, session, goal. Materials as a checklist. Name the columns, and the model will fill them.
So: one job per prompt, a check after each step, and a clear shape for every answer. That's how long tasks stay under control.
Let's plan a real workshop, one step at a time.
Same chat for every step. Check each answer before you ask for the next one.
How to write a chain
Three moves. You'll see all three in the worked example next.
Which shape?
| SHAPE | USE IT FOR | SAY |
|---|---|---|
| Table | Agendas, comparisons, plans with owners | “as a table with columns: …” |
| Checklist | Materials, steps someone will follow | “as a checklist grouped by …” |
| Short list | Ideas, options, names | “give me 5 options, one line each” |
Worked example: one prompt or a chain
The same job, done twice: a half-day workshop for 12 people. First in one big prompt, then as a chain of three.
Check before the next step
This is step 3 of the chain: the invitation. Before you send it, select every sentence that needs a fix.
Hi team,
Best,
[Your Name]
Plan the chain
Here's the big prompt again. Split it: tap the five parts in the order you would ask for them.
Try it for real
Pick a job from your week that has more than one part: a report and its summary, an event and its invitation, a plan and its checklist.
Run it in your AI assistant, in one chat
Only you see what you type here. Keep your chain: on Day 5 it can become your template.
Quick drill
Pick the shape, or decide: one prompt or a chain?
That's Day 4
One job per prompt. A check after each step. A shape for every answer.
Your own task
You'll build a prompt template for a task you do every week, test it, and check it against the rubric for your certificate.
Warm-up
Two questions from yesterday.
Make it reusable
A good prompt you write once and use every week is worth more than a perfect prompt you write once.
Transcript
Welcome to the last day. You've learned to write a clear request, to work from your own material, to check the answer, and to break big jobs into steps. Today you'll turn all of that into something you keep: a prompt template.
A template is a prompt you write once and reuse every week. The parts that stay the same are written out: the structure, the length, the tone, the rules. The parts that change are placeholders in square brackets: the audience, this week's notes.
Add one line that protects you: "Use only facts from the notes. If something is unclear, list it under To check instead of guessing." It helps. It doesn't do your checking for you.
Before you trust a template, test it on two different real cases. If it works on both, keep it. If it doesn't, fix the template, not just the answer.
Build yours today, check it against four criteria, and take the final check for your certificate.
Anatomy of a template
Everything you learned this week, in one prompt. What changes goes in brackets. Everything else stays.
"""
[notes]
"""
Use this structure: Overall status (On track / At risk / Off track) with one sentence why; Done this week; Next week; Risks and what we need. Under 150 words, plain and direct. Use only facts from the notes. If something is unclear or missing, list it at the end under "To check" instead of guessing.
Worked example: one template, two weeks
The same template, run in two new chats with two different sets of notes. Same instructions, different surprises.
Whose decision is it?
Test 2 again. The template worked, and the model still made three decisions that belong to you.
Build your template
Pick a task you do every week. Build a template for it, test it on two real cases, and check it against the four criteria.
Run it in two new chats with two different real cases from your work. Remove anything sensitive first.
Check it against the rubric
Final check
Ten questions drawn from all five days. Score 8 or more to earn the certificate of achievement.
You've finished the course
Clear request. Your material. Check the answer. One step at a time. Then make it reusable.