Vibe Coder · Unit 6: Thinking in Products · Lesson 7 of 9

Prioritising

Product managers: rank what to build by value and effort, and defend the order with reasons.

Read the short notes and pictures.Do everything inside a blue frame.

Choosing the order

Prioritising is deciding what happens first and being able to say why. A simple value and effort score is enough for a first version, as long as the reasons are written down.

A 3D scene of coloured blocks and cards. Score two things: value to the user, effort to build.
Value to the user and effort to build.

A simple method

  1. List the must-haves

    From your scope.

  2. Score value, one to three

    How much does this help the user do the one job?

  3. Score effort, one to three

    Ask Claude for a rough estimate, and treat it as rough.

  4. Order and explain

    Rank them, with one line of reason each.

A 3D scene of coloured blocks and cards. : First, Last.
High value and low effort first.
ActivityBuild stepYour product spec

Rank your must-haves

Score each must-have for value and effort, rank them, and write a one-line reason for each. Add the ranked list to the spec.

Done when

You will build in this order in Unit 8.

Keep these

  • Score value and effort.
  • Build high value, low effort first.
  • Write the reason beside each choice.