Lesson 20
Presenting a Demo
4 min read
Why this matters
Sprint reviews, client calls and company all-hands meetings often include demos. A demo shows your work to people who don't read your code, such as managers, clients and other teams. A clear demo makes your work visible, and it's often the moment people remember who built something.
The core skill
The structure
A good demo has four parts:
- Context: what problem you solved, and for whom.
- The demo: show the feature from the user's point of view.
- What's next: what's missing or planned.
- Questions.
Hi everyone. Today I'm going to show you the new CSV export.
A lot of customers told us they need report data in Excel, and before
this, they had to copy it by hand.
Let me share my screen.
...
So that's the export. Next sprint, we're going to add scheduled exports.
Any questions?
Describe what you're doing
While you click, say what you're doing and why it matters. Use the present continuous for your actions, and the present simple for what the system does.
I'm going to the reports page, and I'm choosing last month.
Now I'm clicking "Export". As you can see, the file downloads right away,
and it uses the same filters as the table.
As you can see is a very common phrase in demos. It points the audience to the screen.
Talk about users, not code
Most people in a demo don't care how the code works. Show the user's journey with realistic data, not "test test 123".
- Code focus: This calls the new endpoint, which uses a streaming response.
- User focus: Even with 10,000 rows, the download starts immediately.
When something goes wrong
Demos often fail. Stay calm, say what happened, and continue.
Hmm, that's not what should happen. Let me try that again.
It looks like the staging server is slow today. While it loads,
let me tell you about the next step.
I'll look into this after the meeting and send a short video.
Prepare a backup, like screenshots or a recording, for important demos.
Useful phrases
Starting
- Today I'm going to show you the new onboarding flow.
- The problem we wanted to solve was …
- Let me share my screen. Can everyone see it?
During the demo
- As you can see, the results update immediately.
- Now I'm going to add a new user.
- Notice that the button is disabled until the form is valid.
- Let me zoom in so you can see it better.
Problems
- Bear with me for a second. (= please be patient)
- Let me try that again.
- It worked five minutes ago, I promise! (a light joke can help)
Finishing
- That's it for the demo.
- What's still missing is the mobile version.
- Happy to take any questions.
Common mistakes
"Now I will show you how works the export." In this kind of phrase, the subject comes before the verb: "Now I'll show you how the export works."
"As you can see, appears a popup." English needs a subject before the verb: "As you can see, a popup appears."
"Can you see my screen?" (silence) "Hello? Hello?" In large meetings, people often don't reply. Ask one person directly: "Ana, can you see my screen?"
"Sorry, sorry, this is a disaster, it never fails…" Too many apologies make a small problem feel big. One short line is enough: "Let me try that again."
Formal vs. casual
- Client demo: "Thank you for joining. Today I'd like to walk you through the new reporting features. Please feel free to stop me at any point if you have questions."
- Team sprint review: "OK, quick demo of the export. Shout if anything's unclear."
Walk someone through means to explain something step by step. Shout here just means "tell me", not literally shout.
Exercise
Choose a feature you built recently. Prepare a two-minute demo:
- Write your opening (context: the problem and who it's for).
- Write three sentences you'll say while clicking.
- Write your closing (what's next and questions).
Then record yourself giving the demo, and watch it once.
Hint: while you watch, count how many times you say "so" or "um". Pausing silently sounds more confident than filling the silence.
Recap
- Context, demo, what's next, questions.
- Present continuous for your actions, present simple for the system.
- Use As you can see and talk about users, not code.
- If something breaks, stay calm and continue.
- Subject before verb: how the export works.