Use Ordered Lists
Jesse Pollak
591

In response to Jesse graciously sharing his product prioritization workflow at Clef, here’s how we do it at Josephine.

  1. Write out a big dump of features and epics.
  2. Group into “priority buckets” on a scale of 1, 2, and 3.
  3. The product team (aka, me for now :) does a rough estimation, also on a 1–3 scale.

Here’s what last week’s board looked like:

We cheated — there shouldn’t actually be a 1.5 urgency :)

We then take all of the 1, 2, and 3 priorities and sort each bucket to create a final prioritized list. The “scope” score helps us decide whether a feature is high-cost or low hanging fruit and therefore a quicker win.

Here’s our final list:

  1. Tracking Pixels
  2. Automated Emails
  3. Analytics
  4. Customers Editing Orders
  5. Education
  6. Slack Notifications
  7. Blog
  8. Promos / Referrals

Since our team is growing now and I won’t be the only one doing estimations, we’ll use an estimation technique I stole from Pivotal Labs. Each member of the product team gives their own estimation (for example, I could think “analytics” is a 2 in scope and you could think it’s a 3), then discuss and meet in the middle.

Tada!

Like what you read? Give Tal Safran a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.