πŸ§‘πŸΎβ€πŸ’» prep

Your product is deployed, but it has no features!

Prep your Demo presentation πŸ”—

Learning Objectives

Preparation

Access to Google slides

Introduction

The demo is done to the product team and various stakeholders. In our case, it will be to your cohort and all volunteers.

We expect you to watch all other demos and ask questions or give feedback.

The demo aims to maintain transparency, enable faster troubleshooting, and encourage accountability for quality code. Ultimately, it stimulates collaboration, knowledge sharing and continuous improvement.

These small ceremonies build empathy, align priorities, provide teaching moments, and support a culture where shipping features responsibly earn praise.

Develop your presentation

🎯 Goal: Develop a presentation about your team’s achievements (57 minutes)

Your demo should be no longer than 5 minutes. This means you need to be clear and concise on the slides. Here are some tips for your presentation:

  1. Focus on 1 key message. Stick to your point.

  2. Avoid text-heavy slides. Instead, use visuals.

  3. Share stories or examples to ensure understanding.

  4. Practice extensively to deliver it within a tight timeframe.

  5. Summarize critical information at both the opening and closing. End strong.

The demo agenda should include the following:

  • What you’ve done this week
  • Demoing your product, which can be UI/UX designs or a live walkthrough of your product
  • What you are planning to do next

You can use this presentation template as a guideline.

User research πŸ”—

Learning Objectives

Preparation

Your product designs/first iteration

Introduction

When we build products, we build them for someone to use. The best way to ensure that the features, design or functionality makes sense is by asking the user’s opinion.

As a technical person, this also allows you to talk to non-technical people who understand the business, the process and the problem you are trying to solve.

However, ensure you don’t rush off and try to implement everything a user tells you. You cannot solve all problems in a day, so use their input to amend anything going in the wrong direction and add new ideas to your backlog for future prioritisation.

Talk to users

🎯 Goal: Collaborate with non-technical stakeholders (60 minutes)

The below is a reference for you and your team to consider during your user research.

Identify the users

  • Identify between 2 - 5 users of your products
  • Try to be diverse (for example, different sex, gender, ethnicity, etc.)

The research

  • Share the briefing you received with the user beforehand.
  • Demo your product to them.
  • Ask them: β€œWhat are your thoughts?” or some generic questions. If you need to ask more questions, ensure they are open.
  • Make notes of their input and ask why they need this. Understanding the why will give you insight into what their problems are.
  • Thank them for their time and ask if they could talk to you again next week.

The outcome of the research

  • Compile the feedback
  • Share it with your team on your Slack channel
  • Define which changes you will make. These should become tickets on your board. (Remember: not every feedback has to be incorporated in your MVP)