Opening and Setting Context

  • Let me walk you through what we shipped this sprint.
    Simple, direct demo opener
    "Let me walk you through what we shipped this sprint — we focused on the checkout flow."
  • The goal of this sprint was to…
    Remind stakeholders of the objective before diving in
    "The goal of this sprint was to reduce onboarding friction, so everything you'll see today addresses that."
  • I'll share my screen and show you the working feature.
    Smooth transition into live demo
    "I'll share my screen and show you the working feature rather than slides."
  • We completed X out of Y stories — here's what that looks like in practice.
    Velocity report combined with demo
    "We completed 8 out of 9 stories — here's what that looks like in practice."

Presenting and Handling Questions

  • Feel free to stop me if you have questions.
    Invite participation without losing control
    "Feel free to stop me if you have questions — I'll also leave time at the end."
  • That's a great question — let me pull that up.
    Buying a moment to navigate the UI
    "That's a great question — let me pull that up so you can see it live."
  • This is still in progress — I can show the current state if that's useful.
    When demoing an incomplete item
    "This is still in progress, but I can show the current state if that's useful for feedback."
  • We'll park that and follow up after the demo.
    Deferring deep dives to keep time
    "Great point — we'll park that and follow up after the demo so we don't lose momentum."
  • One thing to note: this is behind a feature flag right now.
    Important caveat about release status
    "One thing to note: this is behind a feature flag right now and will go live on Friday."

Phrases to Avoid

These common phrasings undermine your professionalism. Here are better alternatives.

Avoid "It's basically done."
Better "We've completed the core functionality — the remaining work is [X]."

"Basically done" is vague and erodes trust; stakeholders need a clear status.

Avoid "Sorry, this is a bit messy."
Better "This is a work in progress — what you're seeing reflects the current state."

Apologising for work-in-progress frames negatively. Just state the status.

Avoid "I hope this makes sense."
Better "Does this address what you were expecting?"

"I hope" sounds uncertain. A direct question invites useful feedback.

Practice Exercises

Choose the most professional or correct phrase for each scenario.

Frequently Asked Questions

What does "walk you through" mean in a demo context?

"Walk you through" means to explain or show something step by step. It's a common phrase in presentations: "Let me walk you through the new checkout flow."

What is a feature flag in plain English?

A feature flag is a configuration switch that enables or disables a feature at runtime without deploying new code. It lets teams ship code safely and release it to users gradually.

How do you say a task is incomplete without sounding negative?

Use factual, forward-looking language: "This story carries over to the next sprint" or "We completed the backend — the UI is in progress." Avoid "we failed" or "we couldn't."