🧑🏾‍💻 prep

Your product is deployed, but it has no features!

🔖
  1. Prep your Demo
  2. User research

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 are to:

  • Demonstrate the incremental progress towards your goal to all your stakeholders (other teams, users, volunteers)
  • Share learnings and gather feedback from other people facing similar challenges to you
  • Practice feeling comfortable speaking in front of larger groups

Develop your presentation

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

Your demo should be no longer than 5 minutes. This means you need to be clear and concise on the slides.

  1. Create a copy of this deck
  2. Update the content on each slide wherever you see
  3. Keep the content short (and sweet!)
  4. Decide what you can demo - it’s great if this is something visual, like frontend changes, but it can also be technical, e.g. “this is how we set up the database”
  5. Decide who will speak - it’s important everyone in the team takes a turn
  6. Practice! Your update should take no longer than 5 minutes

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)