01 / 11 Progress 0/8 slides 0%
Practical AI for everyday work Beginner · Lesson 01 8–10 min read · 15–20 min lab Live

Providing Better Context

The first habit that turns vague AI answers into useful workplace outputs. By the end of this lesson you will be able to turn messy meeting notes into clean action items, every time, in under a minute.

What you'll learn

How to give AI enough context to stop guessing.

Practice task

Turn messy meeting notes into clean action items.

Business impact

Less cleanup, fewer missed details, faster usable drafts.

What you'll learn — 8 slides

02 / 11 Progress 0/8 slides 0%
Start here

The real problem

You paste your meeting notes into an AI tool and ask it to "summarize these notes." Then you wait. Then you sigh.

Most of the time the output comes back generic. It misses the action items that matter. It might be a paragraph when you needed a checklist. Sometimes it sounds polished but is still not useful.

That happens because the AI is guessing. It does not know:

Who is this for?
What should the output be used for?
What format would be helpful?
What level of detail is expected?
What does a good answer look like?
The fix is not a magic prompt.

The fix is better context. The next slides show you how.

03 / 11 Progress 0/8 slides 0%
The core skill

The 4-part context method

Rich context means giving the AI enough useful information to do the job well. There are four elements, and they build on each other.

Build context in layers Each layer gives the AI less to guess.
1
RoleGive the AI the right lens before it starts.
2
Task / FormatSay what to create and how it should be structured.
3
ExampleShow what a good answer should look like.
4
DetailsBackground, constraints, screenshots, and source material.
More complete context → better AI output
04 / 11 Progress 0/8 slides 0%
The first two layers

Role + Task/Format

The first two layers answer the AI's two biggest questions: "Who am I?" and "What am I making?"

Layer 1 · Role

Tell the AI who it should act as. The role gives it a lens — a project manager, HR partner, and executive assistant would all summarize the same notes differently.

You are an experienced project manager. Turn messy meeting notes into clear action items for a busy operations team.

Layer 2 · Task + Format

Be clear about what you want and how you want it structured. If you need a checklist, ask for a checklist. If you need an email draft, ask for an email draft.

Turn these notes into a list of action items. For each, include the owner, deadline if mentioned, and a one-sentence description. Put urgent items first.
05 / 11 Progress 0/8 slides 0%
The last two layers

Example + Details

The third layer shows the AI what good looks like. The fourth layer hands it the source material so it does not have to invent.

Layer 3 · Example of good output

Show the AI what good looks like. If you have a previous meeting summary, email, or report you liked, include it as an example. If you do not have one, invent a tiny fake one — short and simple is enough.

Example style:
- [Owner] [Action] — [Due date] — [Why it matters]
- [Owner] [Action] — [Due date] — [Why it matters]

Layer 4 · Details and background

Paste the source material the AI needs to work with. The more relevant detail you include, the less the AI has to invent. Background the AI does not have = output the AI will have to guess at.

Meeting notes from Monday:
[paste your meeting notes here]
06 / 11 Progress 0/8 slides 0%
Putting it together

Complete example prompt

Here is the four-part method used in a single prompt you can copy and adapt for your own work.

You are an experienced project manager working with
a small operations team. (1) Role

Turn the meeting notes below into a list of action items.
For each action item, include the owner, the deadline if
mentioned, and a one-sentence description. Put urgent
items first. (2) Task and format

Example style:
- Sarah — draft launch checklist — Wed — needed for kickoff
- Marco — confirm vendor pricing — Fri — blocking budget review

Meeting notes (3 & 4):
[paste your notes here]
Notice how the prompt is short.

You do not need a novel. You need the four layers plus the source material. The example does most of the heavy lifting for format and tone.

07 / 11 Progress 0/8 slides 0%
What it looks like when it goes wrong

Bad output example

Same notes. Vague prompt. The output looks polished but is missing the details that actually matter to you. Watch for these five failure modes.

// Bad output — the AI was asked to "summarize these notes"

Meeting Summary

The team discussed the upcoming website launch, marketing plans, and a few other items. Sarah mentioned the launch checklist. Marco talked about vendor pricing. There were some concerns about the timeline. Action items should be followed up on.

— generated by AI

Five things wrong with this output:

  • No owner on any action item — you have no idea who is doing the work.
  • Vague descriptions — "follow up on the website" is not an action item.
  • Wrong format — you asked for a checklist, got a paragraph.
  • Urgent item buried — the Friday deadline disappeared into "some concerns about the timeline."
  • Invented detail — the AI added "a few other items" that were not in the notes.
Polished is not the same as useful.

This is why the next slide is a checklist, not more theory.

08 / 11 Progress 0/8 slides 0%
Before you use the output

Verification checklist

Run through these six questions every time you ask an AI to do work for you — before you send the prompt and again before you act on the reply.

  1. 01 Does it answer the question I actually asked?Not a related question. Not a fancier version. The one I asked.
  2. 02 Is every fact something I can verify in my source material?If you did not write it and the AI did not cite it, you cannot trust it.
  3. 03 Are owners, dates, and numbers real and complete?Not "TBD" unless you accept "TBD" in the final answer.
  4. 04 Is the format what I asked for?Checklist when I asked for a checklist. Email when I asked for an email.
  5. 05 Are urgent items at the top, not the bottom?The AI does not know your deadlines unless you said so.
  6. 06 Did the AI invent, infer, or assume anything I did not provide?If yes, fix it before sending or mark it clearly as a guess.
09 / 11 Progress 0/8 slides 0%
Your turn

Lab · turn your notes into action items

This is the part that actually builds the habit. Pick a real meeting from this week — it does not have to be long. Five messy bullet points is enough.

Step 1 · Gather your raw material

Open a recent meeting notes file. Keep it rough — the point is to give the AI something to work with, not to clean it up first.

Step 2 · Use the four-part prompt template

Copy the template from slide 6. Fill in your role, task/format, an example style, and paste your notes at the end.

Step 3 · Run the output through the checklist

Open slide 8. Check each item before you do anything with the result.

Step 4 · Iterate

If the output is close but not done, send a follow-up: "Move the Friday deadline to the top, add the owner to item 3, and remove the marketing bullet." Iteration is normal — it is not failure.

Done = the action items are ready to send.

You can paste them into Slack, your project tracker, or forward them to whoever is doing the work.

Don't have meeting notes handy?

Download a real (messy) example you can use for the lab. Open it, paste it into the template, and run the prompt.

Download sample notes
10 / 11 Progress 0/8 slides 0%
Knowledge check

Let's see what stuck

Five questions. The next slide will show your score, the questions you missed, why the right answer is right, and where to re-review if you got it wrong.

Answered 0/5
11 / 11 Progress 0/8 slides 0%
Results

Your knowledge check

Your score

0 / 5

Loading…

Question review

What now?

If you missed any, use the re-review links below to jump back to the slide that covers it. If you got all five, you are ready for Lesson 2.