🧑🏾‍💻 prep

Your product is deployed, but it has no features!

🔖
  1. Prep your Demo
  2. User research

Prep your Demo presentation

Learning Objectives

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:

  • 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

  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. Something visual, like layout changes, are fine, but it should also be technical, e.g. “this is how we derived this value”

  5. Decide who will speak - it’s important everyone in the team takes a turn

  6. Practice! Your update should take no longer than

User research

Learning Objectives

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

However, don’t rush off and implement everything a user tells you. Use their input to amend existing features going in the wrong direction; add new ideas to your backlog for future prioritisation.

Talk to users

Collaborate with non-technical stakeholders

Identify the users

  • Identify between 2 - 5 users of your products

  • Ask a range of people (of 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. Ask open questions.

  • 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)