Product management

Explore

How to use

  • This setup is currently designed for a 1-person startup, but can easily be adapted to teams by adding Collaborator columns
  • Use the views in the Backlog table. Scoring/Interessents are just meta-tables and are not intended to be used directly
  • Not everything is moved to the "Work in progress" board by design. This is to reduce clutter in day-to-day usage. To bump something into the board, simply assign it a "Status"
  • Add ideas to the inbox continuously and process them at least one a day by assigning them an area and type. You could even set up a Form and allow your users to submit ideas and tasks directly to the team
  • Assign interessents to rows. This is especially useful to track requests from users, group them and being able to follow up users when you release the feature they've been waiting on.
  • There are types for different tasks (Epic, Feature, Bug, etc). But there is intentionally no hierarchy here to keep things simple and flexible. Simply use them to zoom in and out when you need different perspectives.

​

Choosing the right thing to work on

There is no single right answer here, but this setup helps you by:

​

  • Being pragmatic about scoring. Not every row needs a score, but for the ones who do (i.e. epics, bugs); simply attach a score and fill out the form.
  • The score should be helpful in prioritising, but is not a perfect fit for everything and everyone. Use your own judgement, strategies and gut feeling in addition to the score, when deciding which problems to spend time on.
  • Capture problems and questions by using the Question/challenge type. Use them to keep track of what you are struggling with or are trying to accomplish. This can then be assigned to a release so you'll remind yourself and the team about what you are trying to solve.

​

The scoring formula

  • Roughly the formula is IMPACT * FREQUENCY * EFFORT
  • Where IMPACT is a sum of Feeling (how the user would feel about this feature/bug, or lack of. Inspired from the KANO model). + AARRR field, from the pirate metrics model + Negative impact (if nothing is done about this thing. Typically used on bugs)
  • FREQUENCY is simply how often the user will experience the benefits of the impact
  • EFFORT is how long it will take for the team to implement.
  • You don't have to populate every field, but you should at least populate one from each category (i.e impact, frequency and effort) to avoid a 0 score
  • To adjust the score formula. Go to Scoring -> Calculation -> Customize field type and play with the variables

​

​

​

Explore
Updated January 8, 2021 at 6:05 PM
Copied 101 times
Explore the base
Work in progress
Everything
Inbox
Needs scoring (has interessent)
Not scored
Epics
Roadmap
Bugs
Questions/challenges
By score
By area
By interessents
By Kano
Quick-fixes
Marketing efforts
Grid view
Grid view