lesson
30 min

Discovery and Priorities

Learn what users need by asking good questions, then rank ideas by impact and effort.

What you will learn

By the end of this lesson, you can plan a short user interview and rank a list of ideas by impact and effort.

Discovery: learn before you build

Discovery is finding out what people really need before you build. It saves time, because building the wrong thing is the most expensive mistake.

The best discovery tool is a conversation. Talk with five to eight people who have the problem. You will start to hear the same things.

Ask about the past, not the future

People are poor at predicting what they would use. They are good at describing what they already did. So ask about real, recent events.

Weak questionBetter question
Would you use an app for this?Tell me about the last time you tried to sign your child up for a program.
Do you like our website?What were you trying to do the last time you visited? What happened?
What features do you want?What is the hardest part of this for you right now?

Listen more than you talk. Do not pitch your idea. Write down their exact words.

Respect the people you interview

  • Ask permission before you take notes or record.
  • Explain how you will use what they say.
  • Do not collect names in your notes unless you need to. Use "Parent 1," "Parent 2."
  • For anyone under 18, get a parent or guardian's permission first, and have another adult present.

Prompt Lab

Draft a short, respectful interview guide. Then cut any question that asks people to predict the future.

Who should the AI act as?

What exactly should it do?

What does it need to know?

What shape should the answer take?

How should it sound?

Your prompt

Act as a product researcher who interviews community members with respect.

Format: A two-sentence opening that asks permission, then six open questions about past experiences, then a thank-you

Do not paste private details (full name, address, ID numbers) into any AI tool.

Prioritize: impact and effort

You will always have more ideas than time. Rank them. A simple method is to score each idea on two things:

  • Impact: how much it helps users with the core problem.
  • Effort: how much time and work it takes.

Then sort into four groups.

Low effortHigh effort
High impactDo firstPlan carefully
Low impactMaybe laterDo not do

The hardest part is saying no to ideas in the bottom-right box, especially when someone important suggested them. Explain the tradeoff with evidence from your interviews.

Discovery check

0 of 5 done

Go deeper: Product Management: Building the Right Thing (and Getting People to Use It)

Ask. Answer. Build together.