1 of 30

LEAN PRODUCT MANAGEMENT

2 of 30

WHAT IS LEAN?

As a designers, engineers, product managers we want to...

Deliver value fast, forever

3 of 30

WHAT IS LEAN?

As a designers, engineers, product managers we want to...

Deliver value fast, forever

Outcomes and user benefits through features

Quickly and often

On an ongoing basis without burning out

4 of 30

HYPOTHESIS DRIVEN PRODUCT MANAGEMENT

When faced with uncertainty, you’ll take your riskiest assumptions, reframe it as a hypothesis to make it testable, develop tests for them, and observe the outcomes. Based on the results, you’ll either pivot away from these ideas or you’ll stay on course.

5 of 30

OUTCOMES VS OUTPUTS

What is an outcome?

  1. Specific measurable statement that lets you know when you’ve reached your goals
  2. What you expect to occur as the result of your actions

What is an output?

  1. List of features to be built
  2. Inability to change direction if those features don’t bring value to the end user

6 of 30

WHAT OUTCOME DRIVEN PRODUCT MANAGEMENT LOOKS LIKE

Before defining product direction, the full team needs to understand the user needs, the business priorities, and the technology to accurately define the features to be built.

Inverting the pyramid from PO’s defining requirements allows the team to respond to user needs that are aligned with the product vision.

Users

Product Team

Product

Owner

Feature direction

7 of 30

DIRECTION OF FEATURES

Users

Product Team

Product

Owner

Feature direction

Product

Owner

Product Team

Users

8 of 30

METAPHOR!

  • Landlord is paying for renovations
  • Hires designers and contractors to build what she wants
  • Tenants are never consulted with what they want

9 of 30

LEAN METHODOLOGY

1. Select the biggest risk 

2. Decide how to address it

4. Analyse and iterate

3. Observe

01

02

03

04

10 of 30

WATERFALL VS LEAN

11 of 30

WATERFALL METHODOLOGY

Stakeholders decide requirements

Design

Build

Test

Maintenance

12 of 30

WATERFALL

Risk building wrong stuff

Time spent building stuff

Waterfall

Risk

13 of 30

WATERFALL

Time spent building stuff

Waterfall

Oh snap!

Risk building wrong stuff

14 of 30

WATERFALL VS LEAN

Time spent building stuff

Waterfall

Risk building wrong stuff

15 of 30

WATERFALL VS LEAN

Time spent building stuff

Waterfall

Oh snap!

Risk

Risk building wrong stuff

16 of 30

WATERFALL VS LEAN

Time spent building stuff

Waterfall

Build

Measure

Learn

Risk building wrong stuff

17 of 30

WHY LEAN?

18 of 30

CONTINUOUS DELIVERY

Continuous Delivery is the practice of delivery software to production in short cycles, repeatedly

    • Our ideal: pushing to production several times a week
    • Push when it’s ready--not when everything else around it is ready

Why it works

    • Tighter feedback loops lead to faster feedback
    • Add value in the least amount of time
    • Risk mitigation

The Feedback Loop

Build

Measure

Learn

19 of 30

LEAN IN USE

Other groups using lean

    • Facebook
    • Apple
    • Netflix

Other government groups using lean

    • USDS
    • 18F

The Evolution of IOS Home Screens

20 of 30

PRIORITIZATION

21 of 30

PRIORITIZATION

User Value

Business Impact

Level of Effort

Lean teams take on user value, level of effort and business impact when determining what gets worked on first

22 of 30

HGTV + LEAN

You’ve bought a fixer upper, you’re on a budget and you can’t fix every room in the house at once…

  • De-risk
    • Appliances that might die soon
    • Roof that leaks

  • Iterative
    • Concentrate on one room at time?
    • Concentrate on parts first? Floors? Doors?

23 of 30

METHODS

24 of 30

2X2

Benefit

Effort

Outcome 1

Outcome 3

Outcome 2

Outcome 4

Outcomes

Level of pain

Frequency

Problem 1

Problem 3

Problem 2

Problem 4

Problems

25 of 30

2X2

Benefit

Effort

Outcome 1

Outcome 3

Outcome 2

Outcome 4

Outcomes

Level of pain

Frequency

Problem 1

Problem 3

Problem 2

Problem 4

Problems

Address this first

Do this first

26 of 30

2X2

Benefit

Effort

Outcome 1

Outcome 3

Outcome 2

Outcome 4

Outcomes

Level of pain

Frequency

Problem 1

Problem 3

Problem 2

Problem 4

Problems

Don’t address this

Don’t do this

27 of 30

MATRIX

Business

User

Tech

Outcome 1

Outcome 2

Outcome 3

2

1

3

3

1

2

3

2

1

Total

8

4

6

28 of 30

MATRIX

Business

User

Tech

Outcome 1

Outcome 2

Outcome 3

2

1

3

3

1

2

3

2

1

Total

8

4

6

Do this first

29 of 30

TURNING IT INTO A ROADMAP

30 of 30

QUESTIONS?