Back
1 / 0
→ next ← back F full ? help
Take a break
How long?
Break
00:00

Keyboard

Next slide→
Previous slide←
Full screenF
Black the screenB
First / last slideHome End
Close anythingEsc
Day 2 · Wednesday 9 September 2026 · 09:00 to 14:00

Presentations
and data

Yesterday you learned to ask. Today you learn to build, and to check.
CODED Campus, KuwaitClaude Design · Gamma · ExcelDay 2 of 3
Yesterday, in one line

You are
the variable.

Six parts in a prompt. Show rather than describe. Give it the source, then check the summary back against the source.
All of that still applies today. The output just gets bigger, and the mistakes get more expensive.
Today

Three things you
leave with.

01
A deck you did not format
Built twice, in two tools, from one prompt.
02
Charts you can defend
From data you cleaned yourself, with every number checked.
03
A prompt library and one Skill
So you stop typing the same instruction twice.
Question

How long does a deck
actually take you?

Split it: thinking, writing, formatting.
Section 1 1.1

Where the hours
actually go.

Part 1
Deciding what to say
The genuinely hard part. Nobody can do this for you.
Part 2
Writing it down
Quick, once you know what you are saying.
Part 3
Making it look like a deck
Hours. Every time. For nothing anybody remembers.
AI is very good at part three and useful on part two.It has almost nothing to offer on part one, which is the part that matters.
🖥️

What Claude Design is

You describe the deck you want. It builds the slides, the layout and the structure, inside the same conversation that already has your document in it.
📎It already has your context because you attached the report earlier in the chat
✏️You can change one slide by asking, rather than rebuilding the whole thing
📊It can carry the analysis through from the same data you gave it
It is not a design tool. It is a writing tool that outputs slides.
Section 1 1.2

A deck is a document
with a shape.

The shape is the prompt. Six things, and it is the same six as yesterday.
Audience
Who is in the room, and how long they have
Slide count
Say a number. Otherwise you get twelve.
The spine
Name every slide. This is the part people skip.
The numbers rule
Where figures may come from, and what to do when one is missing
Tone
Direct, or diplomatic. They produce very different decks.
The ask
What you want the room to do when it ends
Name the six slides yourself. If you cannot, the deck is not ready to build.
Before you build anything

A deck that looks right
and misquotes one number
is worse than no deck.

A rough draft gets questioned. A polished slide gets believed. The better it looks, the less anyone checks it.
Today's source is yesterday's report, and it still has five faults in it. That is on purpose.
Task 1 Claude Design

Report to deck.

Task 120 minutesClaude Design
Six slides from the report you already know is dirty
  1. Attach yesterday's operations report to a new Claude conversation.
  2. Write your own six part prompt, then ask Claude to design it.
  3. Open two slides and check every figure against the source.
  4. Fix one slide by hand, so you feel where Claude stops and you start.
Open task 1 →
Boss tier: ask it to fact check the report against itself before it builds. How many of the five does it catch?
Break

Section 1 done.
Take a break.

One deck built. Next we build the same thing somewhere else and compare.
Pick a length. The countdown goes full screen and shows the room when to be back.
Question

Are you learning a tool,
or learning a prompt?

Section 2 2.1

Gamma, in one line.

A presentation tool that generates the whole deck from a prompt, then lets you edit it like a web page. Design first, where Claude is writing first.
Gamma is stronger at
  • Looking finished on the first try
  • Themes, images and layout variety
  • Sharing as a link people can scroll
  • Speed from nothing to something
Claude Design is stronger at
  • Keeping your document in context
  • Getting the words right
  • Carrying analysis through from data
  • Changing one slide without a rebuild
Section 2 2.1

Your turn.

You have a 40 page report and you need six slides where every figure is traceable back to it. Where do you start?
Section 2 2.2

The export test.

Somebody will ask you for the PowerPoint. They always do. So the real question is not how it looks in the tool.
What usually survives
The words, the order, the basic layout
What usually shifts
Spacing, font substitution, anything overlapping
What usually breaks
Charts, custom graphics, and anything clever
What to do
Export once, early, before you have built twelve slides on a broken pattern
Run the export test in task 2, not the night before the meeting.
Task 2 Gamma

Same prompt,
different tool.

Task 215 minutesGamma
One prompt, two decks, one honest opinion
  1. Copy the prompt from task 1. The exact same one, not an improved version.
  2. Generate it in Gamma and pick a theme.
  3. Put the two decks side by side and answer the four questions.
  4. Export the Gamma deck to PowerPoint and see what shifts.
Open task 2 →
You need a Gamma account. Free tier is enough. Sign up now if you have not already.
Say this out loud

It is not better than what
you would have written.
It is faster than what you
would have formatted.

Those are two completely different claims. Only one of them is true, and it is still worth a lot.
Break

Section 2 done.
Take a break.

Two decks, one prompt. After the break we stop making things look good and start checking whether they are true.
Pick a length. The countdown goes full screen and shows the room when to be back.
Question

Everyone ask the same file
the same question.

We will compare answers in four minutes.
Section 3 3.1

Sometimes it calculates.
Sometimes it predicts.

When it writes and runs code on your file, it calculates. When it answers from the shape of the numbers, it predicts. You cannot tell which from looking at the answer.
This is yesterday's prediction slide, arriving with a budget attached. Ask it to show its working, every time.
Section 3 3.2

Ask what is wrong
before what it says.

Every real export is dirty. Nobody tells you which parts.
Duplicates
The same response counted twice
Blanks
Which some tools drop and some read as zero
Impossible values
A 7 on a scale that stops at 5
Spelling variants
One department, four names, four fake departments
The re-identifier
A comment that names the person who wrote it
The profiling prompt takes twenty seconds. Skipping it costs you the whole analysis.
Task 3 In Claude

Clean it before
you trust it.

Task 320 minutesIn Claude
161 survey responses, and not one of them checked
  1. Upload the survey file to Claude.
  2. Step one: profile it. What is wrong with the file, with row numbers.
  3. Step two: the company average, raw and cleaned, with the count behind each.
  4. Verify the counts yourself before you believe them.
Open task 3 →
The headline barely moves when you clean it. Everything underneath it does. That is the lesson.
Section 3 3.3

The smallest sample
always looks like
the best result.

Three people who happen to be content will out-score forty people who are doing fine. The ranking will put them first and say nothing about why.
Put the sample size next to every average. Then the trap cannot survive one glance.
Task 4 In Claude

The answer
and the trap.

Task 418 minutesIn Claude
Which team is struggling, on what, and what you would do
  1. Stay in the same conversation. The cleaned data is already there.
  2. Rank the departments and rank the six questions.
  3. Insist on the number of responses next to every average.
  4. Then ask it which result it would not report to leadership, and why.
Open task 4 →
Boss tier: find a statement about this data that is completely true and completely misleading.
Break

Section 3 done.
Lunch and prayer.

After lunch: the same file, but now somebody is going to disagree with your number.
Back at the time on screen. Bring your laptop.
Question

How far over budget
are we?

It sounds like a question with one answer.
Section 4 4.1

Four checks,
in this order.

Recount
Does the detail add up to the total? Do it yourself once.
Recompute
Is the percentage on the right base? Budget, not actual.
Re-source
Where did this figure come from? Name the cell.
Re-read
Does the sentence claim more than the number supports?
Four checks, about six minutes. Cheaper than one correction email to a board.
Task 5 In Claude

Three answers
to one question.

Task 518 minutesIn Claude
One budget file, three defensible totals
  1. Upload the workbook. Read the Summary sheet first, then the detail.
  2. Ask whether the detail agrees with the Summary. It does not.
  3. Audit the detail: text stored as numbers, duplicates, a sign the wrong way, a wrong base.
  4. Produce one number you would put your name on, and say which corrections got you there.
Open task 5 →
Nobody finds all five in eighteen minutes. Three is a strong result.
Section 4 4.2

Ask for the formula,
not the answer.

A number you cannot reproduce is a rumour. A formula sitting in the real spreadsheet is a result.
Your finance team will accept a formula. They will not accept "the AI said".
Section 4 4.3

A chart makes
one claim.

One claim
If you cannot say it in a sentence, it is decoration
The caption states it
Not "Spend by department". Say what the chart shows you.
A source line
Which sheet, and what you corrected
Nothing else
No second axis, no gradient, no logo on every slide
If the chart has no claim, delete the chart. The room will thank you for the time back.
Task 6 Claude and Excel

The formula
and the chart.

Task 615 minutesClaude and Excel
Two habits that survive contact with finance
  1. Step one: ask for the Excel formula, not the number. Paste it into the real sheet.
  2. Does it return the number you had? If not, find out which one was right.
  3. Step two: two charts from the corrected figures. One claim each.
  4. Add them to the deck you built this morning.
Open task 6 →
Notice whether the deck's story changed once the numbers were corrected.
Break

Section 4 done.
Short break.

Last stretch. Twenty minutes on the thing that makes all of today repeatable.
Pick a length. The countdown goes full screen and shows the room when to be back.
Count them

How many times today
did you retype
the same instruction?

The six part prompt. The profiling prompt. "Show your working." "Put the sample size next to it."
You have been building a library all day. It is just scattered across nine conversations.
Section 5 5.1

Three places
a prompt can live.

Home 1
A document
Simple, portable, works anywhere. You paste it in every time.
Home 2
A Project
Instructions and files that apply to every chat inside it. Good for one ongoing job.
Home 3
A Skill
Claude loads it on its own when the task matches. You stop pasting entirely.
Start with the document. Promote the ones you actually reuse.A library of forty prompts you never open is not a library.
🧩

What a Skill is

A saved set of instructions with a name and a trigger. When your request matches the trigger, Claude loads it without being asked.
🏷️A name and a one line trigger that says when it should fire
📜The full instructions which are just your best prompt, written to work on any input of that type
🔁Consistent output because the same instructions run every time, not the ones you remembered
Worth making when you have done the same task three times. Not before.
Task 7 In Claude

The library,
then one Skill.

Task 720 minutesIn Claude
Five prompts with placeholders, and one that runs itself
  1. Scroll back through two days and find the prompts that worked.
  2. Save four things for each: a title, the prompt with [PLACEHOLDERS], the tool, what you fixed.
  3. Add one for a task only your department has.
  4. Then turn your best one into a Skill, and run it once to prove it works.
Open task 7 →
A prompt you cannot find again is not a saved prompt. Name it for when you would reach for it.
Today

What you built.

01
A six slide deck, built twice
One prompt, two tools, and an opinion about which you would use.
02
A number you would sign
From a file that offered you three, plus two charts that make a claim.
03
A library and a working Skill
So tomorrow starts from something rather than nothing.
Tomorrow

Day 3: your own workflow,
and a package
you present.

We open with data security and privacy, because tomorrow is the day you stop using our sample files and start looking at your own work.
Then connectors, MCP and Skills, a workflow audit, and a capstone you present to the room.
Bring tomorrow

Three things.

Your prompt library
The one you built in task 7
One real workflow
A task you do every week that you dread. We audit it at 09:30.
Your laptop
Charged, with Claude and Excel open
There is a short test tomorrow afternoon, and an end of programme survey. Both take ten minutes together.
End of Day 2

Thank you.

Day 3 starts at 09:00. Same room.