Transcript
Page 1: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

The Things I Don’t Know About Product Retirement Could Fill A Slide Deck

Phil Wolff Product Grim Reaper Graceful Exits at Let My Data Go.org

My Ignorance On Display as a Research Agenda

#prodmgmt #eol #killthepwoduct

#producthospice #gracefulexit

#productmanagement

Page 2: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Done Map

Stage

Kill? How?

Deploy

Close Out

Signals

Done

Plan

All products die.

We put them down when their time is up.

Page 3: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Done Map

Stage

Kill? How?

Deploy

Close Out

Signals

Done

Plan

But we don’t talk about it.

Page 4: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Done Map

Stage

Kill? How?

Deploy

Close Out

Signals

Done

Plan

So product managers have little knowledge and less experience in the end-of-life stage.

Page 5: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Done Map

Stage

Kill? How?

Deploy

Close Out

Signals

Done

Plan

Maybe you’ll have answers to some of these questions. Or know someone. Or have a theory or a story.

Page 6: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

How often do organizations agree on product retirement criteria before needing to kill a product? Is preplanning rare?

Page 7: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

How do chiefs commonly judge the success of retirement projects?

No problems vs. Value vs. Speed

Page 8: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Why do product managers delay pulling the trigger?

Hope

Weak data

Lack of consensus

Distraction

Page 9: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

How do organization attributes affect speed of product exit decision making?

How does size affect how fast and how crisply you make exit decisions?

Page 10: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Is it better to turn things off earlier or later?

You prepare, then turn things off and respond to fallout.

When are you better off…

•  closing early to see what things break? •  (and breaking more things, breaking them worse, but giving

you more time to respond)

or

•  thoroughly preparing a seamless closure? •  (minimizing breakage quantity and severity)?

Page 11: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What triggers a “farewell visit”?

A consumer farewell visit might be for…

• Saying “goodbye” to friends in the system

• Data export/migration

• Petition to restore features, products, services

• Learn terms of retirement

Q. What induces the farewell visit?

Q. What converts a farewell visit into action?

Page 12: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What percent of retirement projects are…

Bullet to the Back Of The Head?

Graceful Exits?

Something in between?

Page 13: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What percent of retirement projects fail and restart?

% fail and restart within 90 days

% fail and restart 2 times

% fail and restart 3+ times

% fail and don’t restart

Page 14: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What percent of retirement projects dispose of the product via

Killing it

Harvesting and recycling parts

Selling it

Donating it

Page 15: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Where does the retirement team come from?

•  __% The existing product team

•  __% Elsewhere in the organization

•  __% In-house product retirement specialists

•  __% Outside product retirement specialists

Page 16: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What percent of retirement teams work together killing products multiple times in a year?

Does reaper expertise live in groups, in individuals, or not at all?

Page 17: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

How many product closures do 1000 product managers lead per year?

Page 18: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

How many weeks per year do product managers spend on product closure?

Page 19: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What percent of product endings result in something other than shutting down?

% handed off to another part of the organization

% sold to a company

% donated to an NGO

% released to open source

Page 20: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Why do some retirement projects get stalled in the execution stage?

% Underfunded

% Key people missing

% Contractual commitments

% Regulatory duty

% Unwilling to break dependent systems

% Hope

Page 21: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

How do organizations respond when customers protest product closure?

Page 22: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Who are the decision makers in product retirement?

Who makes recommendations and who decides?

• Product

• Marketing

• Engineering

• Finance

• CEO/COO

Page 23: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What ToS/EULA elements help or hinder a graceful exit?

Page 24: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

How, and how well, do leaders of product closure projects deal with the strong feelings of the product’s teams?

Page 25: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What constitutes meaningful notice to customers?

By industry/segment

By geography

By age

Page 26: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What communication plans work best for meaningful notice?

Page 27: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What are the best ways to tell the product team “your product is about to die”?

Page 28: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What constitutes meaningful notice to independent developers and other business partners?

Page 29: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What regulatory trends affect product termination? Product disposal?

Page 30: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What works to keep key personnel working until retirement is complete?

Page 31: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

How do you value a retirement project that goes well?

Page 32: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Does the shift from creation to destruction harm the product team after the retirement?

Does it lose unit cohesion?

Is there some institutional version of PTSD?

Or is it a useful break? A lagniappe?

Page 33: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

How common are data portability practices in product retirements? How strong? Frequency •  No portability

•  Contributed data export

•  API/json

•  Profiles

•  Contacts

•  Conversations & Gestures

•  History

• Migration tools

Factors correlated with high portability and low portability •  Org size

•  Industry/Customer Segment

•  Product revenue

•  Funding type/stage

Page 34: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What does the law say about shutting down a service or ending a product’s life

Jurisdictions?

US? California, New York, Texas?

EU? UK?

Japan? Canada, Commonwealth?

BRIC?

Bodies of law?

Privacy/data protection

Consumer/patient/client protection

Telecom

Anti-trust

Page 35: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

How often do IT organizations and startups have repeatable practices for shutting down products?

Many products

Few

Brief Long

Portfolio

Product Lifespan

Lots of Experience

Startups

Startups

Page 36: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What are the differences between great product champions and great project reapers?

Page 37: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What are the differences between great product champions and great project reapers?

Passion vs. Dispassion

Sense and Respond vs. Map and Conquer

Soft Power vs. Formal Authority

Continuous Process vs. Hard Deadlines

Creater vs. Destroyer

Mark on the world vs. No trace left behind

Page 38: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

How do core values affect exit project tradeoffs?

Page 39: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What are the most common reasons given for a fast, rough, bullet-to-the-back-of-the-head product closure? The real reasons?

Page 40: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

To what degree do product communities stay together and migrate when a product dies? Why? Why not?

Page 41: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What are the seven best discussions to have in a product team debriefing workshop?

Page 42: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Do companies reward or penalize retirement project managers differently than they do product managers?

Page 43: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

“You come back from lunch and are told to shut down your product by the end of the day. Could you? How well? What would you expect to go wrong?”

Page 44: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What HR issues are most likely to screw up an otherwise clean product retirement project?

Page 45: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

What financial reports are most useful in a post-retirement product review?

Page 46: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Done Map

Stage

Kill? How?

Deploy

Close Out

Signals

Done

Plan

Let me ask you a few questions about your own product hospice experiences.

Page 47: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Done Map

Stage

Kill? How?

Deploy

Close Out

Signals

Done

Plan Are you ready to prepare for end-of-life while your product is still healthy?

Page 48: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Done Map

Stage

Kill? How?

Deploy

Close Out

Signals

Done

Plan Can you shift to the happily grim mindset of a reaper?

Page 49: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Done Map

Stage

Kill? How?

Deploy

Close Out

Signals

Done

Plan

Are you, your product’s champion, best suited and best prepared to deal death to your own products?

Page 50: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Done Map

Stage

Kill? How?

Deploy

Close Out

Signals

Done

Plan

It’s time for a new #prodmgmt specialty.

The Reaper.

Page 51: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Share your product death stories to improve reaping

Your stories from real product endings

Anecdotes tell us what to test

Instrumented experiments

Share hard data

Surveys

How people think

Prediction markets

Test conclusions

Page 52: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Product Reaping could become a standalone product management discipline

More science, less art

More ROI, less housekeeping

More brand building, less brand protection

More experience, less “ooh, that’s a wheel”

More up front planning and prep, less last minute scramble

More reaping ecosystem:

•  apps (or features in #prodmgmt apps)

•  markets (for selling features, products)

•  services (project support)

Page 53: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Done Map

Stage

Kill? How?

Deploy

Close Out

Signals

Plan

Thanks!

Done

Page 54: The Things I Don't Know about Product Retirement Could Fill A Slide Deck

@evanwolf

Phil Wolff Hi!

Email or tweet your stories, suggestions, referrals or just call/skype

Phil Wolff is a consulting product manager in Oakland, California. Phil co-founded four startups,

worked as a programmer, project manager, business analyst, technology architect, industry analyst,

operations researcher, and tech journalist at Bechtel National, Wang Labs, LSI Logic, Adecco SA, NavSup,

and privacy NGOs. He volunteers in Code for America’s #OpenOakland brigade.

e [email protected] skype evanwolf v +1-510-343-5664 t @evanwolf @letmydatago bio About.me/evanwolf cv Linkedin.com/in/philwolff blog Letmydatago.org


Recommended