Preparing a Presentation

One-sentence summary

In this lesson we learn to turn your project into a short, clear story: a rehearsed, time-controlled presentation that explains the problem, the solution and the result with little text and the right visuals.

Why it matters

Even if you build a great project, no one will understand it unless you can explain it. A presentation is the fastest way to pass your work on to a listener.

Presenting is not the same as being talkative. A good presentation is less about saying a lot and more about choosing the right things to say. You may have worked for weeks, but your listener has about five minutes, so you must pick the most important part.

Preparing a presentation also helps you understand your own project again. If you cannot clearly answer “Why did I do this?”, you probably have not fully understood that part yet.

Throughout this lesson we follow one example: the automatic night light from earlier modules (a small lamp that turns on when the room gets dark and off when it gets bright). We are not claiming it was ever shown at a competition or won anything; it is only here to make the steps concrete.

A presentation is a story: Problem → Solution → Result

If you want your listener to follow without getting bored, build your presentation like a story. The simplest, strongest story shape has three parts.

1. Problem: What were you trying to solve?

First, make your listener think, “Yes, that really is a problem.” Start with an everyday situation, no technical detail.

For the night light example:

“When I woke up at night, I had to feel around for the switch to find the light. I wanted the light to come on by itself in the dark.”

2. Solution: What did you do?

Now explain your solution, but not every wire and line of code, just the main idea.

“I used a light sensor. When the room drops below a certain value, the microcontroller turns the LED on, and when it gets bright it turns it off.”

One visual is enough for the details: a circuit diagram or a short flowchart.

3. Result: What happened, what did you learn?

The result is the part most presentations forget, yet the most valuable. Be honest: did it work on the first try, what did you change?

“On the first try the lamp also came on during the day. It was fixed when I raised the threshold value. Next, I want to adjust the brightness to the room.”

You do not have to hide the parts that failed. “It didn't work the first time, so I changed this” is far more convincing than pretending everything was perfect.

Little text, many visuals

The most common presentation mistake is filling slides with paragraphs of text. Your listener cannot read the slide and listen to you at the same time.

Rule: A slide is a poster, not a notebook

When you glance at a poster from a distance, you understand it at once. Your slide should be the same.

• At most 3–4 short lines per slide.
• Use keywords, not full sentences.
• Make the text large; the person at the back should read it.
• One main idea per slide.

Two everyday examples: Same information, two different slides

Wrong slide (too much text):

In my project I used a light sensor that measures the light in the
room, and I wrote code that reads this value and compares it to a
threshold to decide whether the LED turns on, and at first it didn't
work but then I changed the threshold...

Better slide (little text + visual):

HOW DOES IT WORK?

- Light sensor measures the room
- Dark → LED turns on
- Bright → LED turns off

[picture of the circuit diagram]

The second slide has little text; you tell the rest by speaking, and the visual explains the idea quickly. Photos, diagrams, a short video or a simple chart are good choices.

A slide-by-slide presentation outline

Here is an outline for a five-minute school project presentation, filled in with the night light example. Change it to fit your own project.

This outline is a pattern, not a law. For a small project 5–6 slides are enough; don't confuse slide count with minutes.

Rehearsal and time management

Planning a presentation in your head is very different from saying it out loud. The first time you speak without rehearsing, the words don't come out as expected.

The three steps of rehearsal

1. Solo rehearsal: Tell it out loud, alone, looking at your slides. Note where you stumble.
2. Timed rehearsal: Start a stopwatch. If you go over time, shorten the text instead of adding a slide.
3. Rehearsal with a listener: Present to a family member or friend. Ask, “Was anything unclear?”

How do you keep to time?

• Write down beforehand how long each slide should take (like in the outline).
• If time is short, keep the problem, solution and result; drop the details.
• Don't save time by speaking fast; the listener won't follow. Say fewer things.

You will notice your first run almost always takes longer than planned. That is normal; shortening is harder than lengthening, but more valuable.

Mini practice

Starting from your own project (or the night light example), prepare the following:

1. Explain your project in one sentence: “What does it do?” (At most 20 words.)
2. Fill in three headings:

• Problem: …
• Solution: …
• Result / what I learned: …

1. Use the outline above to draft a 6–8 slide plan. At most 3–4 lines per slide.
2. Rehearse out loud once, with a stopwatch. Note the time.

Check yourself:

• Does any slide have more than 3–4 lines of text?
• Would a stranger understand the project just by looking at the slides?
• Does the result section have an honest “I changed this” sentence?

Common mistakes

Filling slides with text

The most common mistake. If you read the slide, the listener follows the screen instead of you. Cut the text; do the talking yourself.

Skipping the result and lessons learned

Most people explain the solution but forget the “what happened, what did I learn” part, which is exactly what the listener is most curious about.

Going on stage without rehearsing

A presentation that seems smooth in your head stumbles out loud. Rehearse at least once, with a timer.

Trying to explain everything

You want to show everything, but it won't fit into five minutes. A little said clearly beats a lot said in a muddle.

Managing time by speeding up

When time is short, speaking fast doesn't work; the listener drops off. Instead, remove a slide or a detail.

Safety note

Because a presentation is given in front of others and sometimes shared, be careful with your personal information.

• Don't put your full name, school, home address or phone number on the cover slide. Your first name is enough.
• If there are other people's faces in the presentation or the photos, get their (or their parents') permission. Without permission, don't show the faces.
• If you share your project online, make sure no email, password or location shows up in your screenshots.
• Let an adult check once that your presentation and shared visuals are appropriate.

In short: share your project, but protect yourself and others. Getting permission and hiding personal information is a quiet but important part of a good presentation.

Lesson summary

• A good presentation is not talking a lot but choosing the right things: problem, solution and result.
• Build the presentation like a story; the result and lessons learned are the most valuable part.
• Use little text and many visuals; a slide is like a poster, not a notebook.
• Make a slide-by-slide outline and time plan to fit within five minutes.
• Rehearse and check your time with a stopwatch; be careful not to share personal information.

Review questions

1. What are the three main parts of a good presentation story?
2. Why shouldn't we put too much text on a slide?
3. Which part do most people forget, even though it is the most valuable?
4. When time runs short, should you speak faster or cut detail? Why?
5. Name two pieces of personal information you should not put on your cover slide.

Answers

1. Problem (what you solved), solution (what you did) and result (what happened, what you learned).
2. Because the listener cannot read the slide and listen to you at once; too much text pulls attention to the screen and hides the main idea. Keep little text on the slide, the rest in your talk.
3. The result and lessons-learned part. Whether it worked, what you changed and your next step are what the listener is most curious about.
4. Cut detail. Speaking fast makes it harder for the listener to follow; saying less but clearly is always better.
5. For example: full name, school, home address, phone number (any two are correct).

Source and verification note

For “Preparing a Presentation”, verification focuses on whether the relationship between A presentation is a story: Problem → Solution → Result and 2. Solution: What did you do? remains consistent across examples. A project page should make a result claim only when it is supported by a real prototype, test record or observation. Numbers such as cost, duration and success rate must be labelled clearly when they are estimates.

Next lesson

Making a Demo Video: Making a short, clear video that shows your project working; shot plan, sound, light and privacy.