Product Management - Simplest Framework for Prioritization

16
SIMPLEST FRAMEWORK TO SET PRODUCT PRIORITIES (for startups) [email protected]

Transcript of Product Management - Simplest Framework for Prioritization

Page 1: Product Management - Simplest Framework for Prioritization

SIMPLEST FRAMEWORKTO SET PRODUCT PRIORITIES

(for startups)

[email protected]

Page 2: Product Management - Simplest Framework for Prioritization

SIMPLE AND

FAST TOOL

WHAT IS THE SIMPLEST

PM FRAMEWORK TO

GET THINGS DONE?

Page 3: Product Management - Simplest Framework for Prioritization

STEP 1 - TODO LIST

• FEATURES

• DESIGN

• TASKS

• USER FEEDBACK

• … anything you add to the list

Page 4: Product Management - Simplest Framework for Prioritization

EXAMPLE - FEATURES

Date Feature Comments

2/15/15 Feature 1 MVP

3/1/15 Feature 2

3/6/15 Feature 3

3/7/15 Feature 4

Page 5: Product Management - Simplest Framework for Prioritization

STEP 2 - RANK

Rank is defined as multiple of:

R = User Value x Business Value x Delivery

each one is rated 1-5 (1=worst, 5=best)

You can add more, but NOT RECOMMENDED

Page 6: Product Management - Simplest Framework for Prioritization

VALUES (ATTRIBUTES)• User value is based on Segmented -

Aggregated votes (inputs: Sales, Support,

Training)

• Business value is based on revenue

opportunity, marketing value (inputs:

Business, Marketing)

• Delivery (T2M, Engineering Effort) is based

on how quickly it could be done (input: Eng

team)

Page 7: Product Management - Simplest Framework for Prioritization

RANK

ver FeatureUser

Value

Business

valueT2M Rank

Feature 1 4 2 5 40

Feature 2 5 4 4 80

Feature 3 5 5 3 75

Feature 4 4 3 4 48

Page 8: Product Management - Simplest Framework for Prioritization

STEP 3- SORT AND

VERSION

ver FeatureUser

Value

Business

valueT2M Rank

1.01 Feature 2 5 4 4 80

1.02 Feature 3 5 5 3 75

1.03 Feature 4 4 3 4 48

1.03 Feature 1 4 2 5 40

Page 9: Product Management - Simplest Framework for Prioritization

VERSIONS = RELEASES• Combine many small improvements or

few large features

• Releases are "bundles" of requirements

with total value sum of X of more

(~400pts)

• Example:

v.1.03 has 88pts = 48pts (Feature 4) +

40pts (Feature 1)

• Best practice: Don’t make releases “too

big”. Customers will always find

bugs/problems

Page 10: Product Management - Simplest Framework for Prioritization

BEST PRACTICE -

EQUALIZE

0

110

220

330

440

550

April May June July

0

150

300

450

600

750

April May June July

Good

Not

Page 11: Product Management - Simplest Framework for Prioritization

SUMMARY

1. MAKE A LIST

2. RANK BY 3 DIMENSIONS (USER, BIZ,

ENG)

3. GROUP INTO RELEASES OF X PTS

Use any tool you like (diagramic.com,

spreadsheet)

Page 12: Product Management - Simplest Framework for Prioritization

DEMO

Page 13: Product Management - Simplest Framework for Prioritization

BEST PRACTICE

ALTERNATE “FEATURE” RELEASES AND

“USABILITY” RELEASES

0

110

220

330

440

550

April May June July

Page 14: Product Management - Simplest Framework for Prioritization

SUMMARY

1. MAKE A LIST

2. RANK BY 3 DIMENSIONS (USER, BIZ,

ENG)

3. GROUP INTO RELEASES OF X PTS

use any tool you like (google spreadsheet)

Page 15: Product Management - Simplest Framework for Prioritization

THIS IS AS SIMPLE AS IT CAN

GETI've seen very complex systems, but

the overhead is not worth it

Page 16: Product Management - Simplest Framework for Prioritization

DIAGRAMICSIMPLEST PRODUCT PRIORITIES FRAMEWORK

[email protected]

www.diagramic.com