21,99 €
Mehr erfahren.
- Herausgeber: John Wiley & Sons
- Kategorie: Fachliteratur
- Serie: Silicon Valley Product Group
- Sprache: Englisch
Help transform your business and innovate like the world's top tech companies!
In INSPIRED, product thought leader Marty Cagan revealed the best practices and techniques used by the top product teams operating in the product model. Next, EMPOWERED shared the best practices and techniques used by the top product leaders to provide their teams with the kind of environment they need to thrive in the product model.
Yet, the most common question after reading INSPIRED and EMPOWERED has been: "Yes, we want to work this way, but the way we work today is so different, and so deeply ingrained, is it even possible for a company like ours to transform to the product model?"
TRANSFORMED was written to bridge the gap between where most companies are right now and where they need to be. The leaders of these companies know they must transform to compete in an era of rapidly changing enabling technology, but most of them have never operated this way before.
TRANSFORMED has three big goals:
- First, the book will educate you with a deep understanding of the product operating model, and what it means to work that way.
- Second, the book will convince you with detailed case studies of successful transformations, that while difficult, it is absolutely possible for you to transform your company to the product operating model.
- Third, the book will inspire you with truly impressive case studies of product innovation, showing what you too will be capable of doing once you successfully transform.
TRANSFORMED is written for those driving change, including the senior company leaders—starting with the CEO—as well as the senior executives and stakeholders who need to collaborate with the product teams, the product leaders, the members of the product teams, and all those who either support or depend on these product teams.
Written by best-selling author Marty Cagan and his partners at the Silicon Valley Product Group, TRANSFORMED is filled with real-world examples and proven, practical advice from their decades of experience helping companies move to the product operating model.
Sie lesen das E-Book in den Legimi-Apps auf:
Seitenzahl: 439
Veröffentlichungsjahr: 2024
Ähnliche
Table of Contents
Cover
Table of Contents
Title Page
Copyright
Dedication
PART I: Introduction
CHAPTER 1: Who Is This Book For?
CHAPTER 2: What Is a Product Operating Model?
CHAPTER 3: Why Transform?
A Competitive Threat
A Compelling Prize
Frustrated Leaders
CHAPTER 4: A Typical Transformation
A New Start
Friction and Pushback
Focus on Predictability
Note
CHAPTER 5: The Role of the CEO
CHAPTER 6: A Guide to
TRANSFORMED
Note
PART II: Transformation Defined
CHAPTER 7: Changing How You Build
Notes
CHAPTER 8: Changing How You Solve Problems
Empower Teams with Problems to Solve
Product Discovery
True Collaboration with Stakeholders
CHAPTER 9: Changing How You Decide Which Problems to Solve
Disrupting Product Planning
Disrupting Yourselves Before You're Disrupted
Customer-Centric Product Vision
Insight-Driven Product Strategy
The Role of Product Leadership
Note
PART III: Product Model Competencies
CHAPTER 10: Product Managers
Note
CHAPTER 11: Product Designers
How the Product Works
Product Discovery
CHAPTER 12: Tech Leads
Notes
CHAPTER 13: Product Leaders
Management
Leadership
Note
CHAPTER 14: Innovation Story: Almosafer
Company Background
The Problem to Solve
Discovering the Solution
The Results
PART IV: Product Model Concepts
CHAPTER 15: Product Teams
Principle:
Empowered with Problems to Solve
Principle:
Outcomes over Output
Principle:
Sense of Ownership
Principle:
Collaboration
Note
CHAPTER 16: Product Strategy
Principle:
Focus
Principle:
Powered by Insights
Principle:
Transparency
Principle:
Placing Bets
CHAPTER 17: Product Discovery
Principle:
Minimize Waste
Principle:
Assess Product Risks
Principle:
Embrace Rapid Experimentation
Principle:
Test Ideas Responsibly
CHAPTER 18: Product Delivery
Principle:
Small, Frequent, Uncoupled Releases
Principle:
Instrumentation
Principle:
Monitoring
Principle:
Deployment Infrastructure
Notes
CHAPTER 19: Product Culture
Principle:
Principles over Process
Principle:
Trust over Control
Principle:
Innovation over Predictability
Principle:
Learning over Failure
CHAPTER 20: Innovation Story: Carmax
Company Background
The Problem to Solve
Discovering the Solution
The Results
PART V: Transformation Story: Trainline
PART VI: The Product Model in Action
CHAPTER 21: Partnering with Customers
Promises
Product Discovery
Product Delivery
Happy, Referenceable Customers and Business Impact
Note
CHAPTER 22: Partnering with Sales
CHAPTER 23: Partnering with Product Marketing
Market Understanding and Competitive Analysis
Product Go-to-Market
Key Product Decisions
Customer Discovery Program
Messaging and Positioning
Customer Impact Assessment
Pricing and Packaging
Sales Enablement
CHAPTER 24: Partnering with Finance
Testing the Product Model
Product and Finance Collaboration
Requests of Finance
CHAPTER 25: Partnering with Stakeholders
CHAPTER 26: Partnering with Executives
Decisions
Outcomes
Disagreements
Promises
Surprises
Trust
CHAPTER 27: Innovation Story: Gympass
Company Background
The Problem to Solve
Discovering the Solution
The Results
PART VII: Transformation Story: Datasite
PART VIII: Transformation Techniques
CHAPTER 28: Transformation Outcome
CHAPTER 29: Transformation Assessment
Overview
High-Level Assessment
The Detailed Assessment
Note
CHAPTER 30: Transformation Tactics—Competencies
Product Model Competencies
CHAPTER 31: Transformation Tactics—Concepts
Product Teams
Product Delivery
Product Discovery
Product Strategy
Product Culture
CHAPTER 32: Transformation Tactics—Adoption
Pilot Teams
Product Model Dimensions
Top Down and Bottom Up
Coaching Stakeholders
Stakeholder Briefings
Managing Existing Commitments
CHAPTER 33: Transformation Evangelism
The Transformation Plan
Continuous Evangelism
The Value of Quick Wins
Constantly Beat the Drum
CHAPTER 34: Transformation Help
Managers as Coaches
In-House Product Coaches
External Product Coaches
Finding a Product Coach
Product Coach: Gabrielle Bufrem
Product Coach: Hope Gurion
Product Coach: Margaret Hollendoner
Product Coach: Stacey Langer
Product Coach: Dr. Marily Nika
Product Coach: Phyl Terry
Product Coach: Petra Wille
CHAPTER 35: Innovation Story: Datasite
Company Background
The Problem to Solve
Discovering the Solution
The Results
PART IX: Transformation Story: Adobe
PART X: Overcoming Objections
CHAPTER 36: Objections from Customers
CHAPTER 37: Objections from Sales
CHAPTER 38: Objections from the CEO and Board
CHAPTER 39: Objections from Line of Business
CHAPTER 40: Objections from Customer Success
CHAPTER 41: Objections from Marketing
CHAPTER 42: Objections from Finance
CHAPTER 43: Objections fromHR/People Ops
CHAPTER 44: Objections from the CIO
CHAPTER 45: Objections from the PMO
CHAPTER 46: Objections from Inside Product
Note
CHAPTER 47: Innovation Story: Kaiser Permanente
Company Background
The Problem to Solve
Discovering the Solution
The Results
PART XI: Conclusion
CHAPTER 48: Keys to Successful Transformation
1. The Role of the CEO
2. The Role of Technology
3. Strong Product Leaders
4. True Product Managers
5. Professional Product Designers
6. Empowered Engineers
7. Insights-Based Product Strategy
8. Stakeholder Collaboration
9. Continuous Evangelization of Outcomes
10. Corporate Courage
CHAPTER 49: Innovation Story: Trainline
Company Background
The Problem to Solve
Discovering the Solution
The Results
Learning More
Acknowledgments
About the Authors
End User License Agreement
Guide
Cover
Title Page
Copyright
Dedication
Table of Contents
Begin Reading
Learning More
Acknowledgments
About the Authors
End User License Agreement
Pages
i
ii
iii
iv
v
vi
viii
ix
x
xi
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
127
128
129
130
131
132
133
134
135
136
137
138
139
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
271
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
329
330
331
332
333
334
335
336
337
338
339
340
341
343
344
345
346
Praise for TRANSFORMED
“TRANSFORMED should be in the hands of every organizational leader evolving their organization in this post-pandemic world. Marty has captured all the impactful aspects of product operating model and I can wholeheartedly attest, based on my own personal journey in both retail and healthcare, this is a key reference guide moving forward.”
—Prat Vemana, Chief Digital and Product Officer, Target
“Marty has been helping set the standard in Product for years with INSPIRED, EMPOWERED, and his work at SVPG. With TRANSFORMED, Marty offers a powerful guide to help companies master the product concepts, overcome the inevitable obstacles of a transformation, and learn from real-world examples of product transformations. This book should be a trusted resource for any company trying to transition to the product model.”
—Tyler Tuite, Chief Product Officer, Carmax
“SVPG understands what most executives don't. In order to achieve organizational transformation, you must experience a personal transformation. This book will show you how to do both.”
—Brendan Wovchko, Chief Technology Officer, Ramsey Solutions
“If you have—or are seeking—the courage to transition to a product operating model, TRANSFORMED will be your guiding light. This book not only underscores why your organization should transform but also provides practical techniques to implement the change and drive positive results. Marty's candid and straightforward advice on pressing questions, such as how to overcome objections from within the organization, is indispensable and actionable. If you've ever questioned your company's ability to innovate—or stay relevant—in an era of exponential technological growth, TRANSFORMED is a must-read.”
—Melissa Cohen, Senior Product Director, Rocket Mortgage
“If you feel like your organization needs to evolve to the product operating model, then TRANSFORMED is a must-read. In typical Marty fashion, he candidly outlines why to do it, how to do it, the challenges you'll face (both the who and the what), and how to navigate and overcome them. It's a quick and powerful read and one you'll come to revisit over and over.”
—Shawn Boyer, CEO, GoHappyLabs
“No one has as much depth and breadth of experience with world-class product teams as Marty. In TRANSFORMED, Marty presents a very pragmatic path for otherwise-successful companies that still haven't cracked the nut on consistently building high-impact software products. This path is not just about adopting one magic tactic for goal setting, or rolling out a popular software development process. Instead, TRANSFORMED presents a more holistic approach for organizational design, strategy, culture, leadership, and ongoing improvement that actually works in the real world.”
—Shreyas Doshi, Advisor and former product leader at Stripe, Twitter, Google, Yahoo
“SVPG has already taught us how the product model empowers all companies to better serve their customers. TRANSFORMED now teaches us how to unlock that power in any company despite its industry, product type or past management approach. With this book, we now all have the roadmap needed to transform our businesses into product powerhouses.”
—Michael Newton, CEO, Qorium; former VP Product at Nike
“TRANSFORMED is the definitive resource for executives looking to gain the ultimate competitive edge in transforming from a feature factory to a world-class product organization that delivers unrivaled value to customers.”
—Michelle Longmire, CEO, Medable
“In an era where technology is the heartbeat of most successful businesses, TRANSFORMED stands out as the essential guide for any company navigating the transition to the product operating model. Marty masterfully demystifies the journey, blending hard-won insights with compelling case studies, making it not only a roadmap for transformation but also an inspiration. Having witnessed countless organizations grapple with this very shift, I can confidently say this book is the beacon they've been waiting for. A must-read for anyone serious about harnessing the power of technology to propel their business forward.”
—Mike Fisher, former CTO at Etsy
“If you're looking to understand the importance of a product-first approach to business, this book is a must-read. TRANSFORMED is an inspirational guide through the product model that speaks directly to the non-product executive.”
—Matt Brown, Chief Financial Officer, Altair Engineering, Inc.
“Marty Cagan and the SVPG team have done it again. Through the use of great examples, and their signature style of hitting issues head-on, they've created a guide to help companies navigate the roadblocks and pitfalls that come with transforming to the product operating model. This book should be required reading for any executive team who wants to make their journey more successful.”
—Anish Bhimani,Chief Product Officer, Commercial Banking, JPMorgan Chase
“The money, time, and patience you can save by implementing the insights in this book is incredible. This was the missing piece in Marty's collection that now addresses the common mistakes and patterns you encounter while transforming from the rest to the best. I hope every board, CEO, and product team reads this.”
—Anuar Chapur, VP of Technology, The Palace Company
“TRANSFORMED is the field guide to embedding innovation into organizational DNA. With real-world lessons, provided in easily understood narratives, Marty and team bring decades of experience to navigating product transformation. A must-read for any CEO or CIO who is looking to build a smart, responsive, and technologically enabled organization.”
—Madhu Narasimhan, EVP Innovation, Wells Fargo
“There are so many ingredients necessary to make a successful transformation work. Marty gives you everything you need in TRANSFORMED. From a valuable perspective for the CEO and Board level, to critical technology components like CI/CD, to how product can effectively partner across the organization and beyond, this is the path to success.”
—Thomas Fredell, Chief Product Officer, ShiftKey
“Building great products that customers love but work for your business is really, really hard. Transforming an organization to discover and deliver impactful products consistently is even harder. Meeting Marty in 2019 and reading his book Inspired started my journey as a product leader, transforming an organization from an uninspired feature factory to an empowered organization. Christian Idiodi delivering a transformation workshop to our entire organization in 2020 accelerated that process and led us to exponential growth, thriving through the pandemic and then coming out even stronger after the pandemic. TRANSFORMED powerfully and simply articulates the principles and components that were critical to successfully transforming our business to the product model and then scaling it.”
—Ronnie Varghese, Chief Digital Officer, Almosafer
“This is a must-read for any company leader interested in learning what it takes to successfully implement and sustain the product operating model. TRANSFORMED not only provides a taxonomy that decodes how the best technology companies work, but also supplies the reader with specific techniques to drive a true digital transformation and showcases real examples from several companies across diverse industries. I have no doubt that this book will become an essential change management guide to drive product transformations across the world!”
—Juan D. Lopez, Director of Product Management, Blue Origin
“Every CEO and Chief Product Officer who wants to delight customers, increase revenues and profits, and attract and retain top talent should read and apply this book—it will transform everything.”
—Phyl Terry, Founder and CEO, Collaborative Gain
“TRANSFORMED is the guide for a successful digital transformation. It's comprehensive and practical, giving companies the blueprint of what great looks like and how to get there. The book is a must-read not only for businesses in the midst of transformation, but for any company aspiring to operate at its best.”
—Gabrielle Bufrem, Product Coach
“Companies spend huge amounts of time and money trying to transform, and all too often get little in return. TRANSFORMED shows what's possible on the other side, what it actually takes to pull it off, and what can derail the effort. I finally have a book I can give to the people I work with that clearly and practically explains the journey we're on.”
—Andrew Skotzko, Product Leadership Coach & Advisor
“If your organization aims to innovate like the best tech companies, you need to read TRANSFORMED. I'm buying copies for all of my clients.”
—Felipe Castro, Founder, OutcomeEdge
“Ever wondered what sets companies like Stripe, Slack, and Apple apart? It's the Product Operating Model, a dynamic conceptual framework that transcends traditional processes. In TRANSFORMED, discover how you, as an executive or product leader, can embrace the model's set of first principles, reflecting what the best product companies believe to be true about creating products. Recognize that there's no one-size-fits-all approach to product development. Here, strategic direction is woven into the fabric of your organization, with product leaders in tech, design, and product providing essential strategic context and dedicating themselves to coaching and mentoring their staff. Learn to accelerate value delivery and to empower teams to tackle problems to solve, rather than features to build. Marty, with 20 years of transformation expertise, offers a practical guide to instill trust, innovation, and adaptability. Your journey taking your organization to the next level begins now.”
—Marcus Castenfors, Partner at Crisp & Co-author of Holistic Product Discovery
The Silicon Valley Product Group Series
INSPIRED: How to Create Tech Products Customers Love, 2nd Edition(Marty Cagan, 2017)
EMPOWERED: Ordinary People, Extraordinary Products(Marty Cagan with Chris Jones, 2021)
LOVED: How To Rethink Marketing For Tech Products(Martina Lauchengco, 2022)
TRANSFORMED: Moving To The Product Operating Model(Marty Cagan with Lea Hickman, Christian Idiodi, Chris Jones, and Jon Moore, 2024)
HOW TO TRANSFORM YOUR COMPANY TO INNOVATE LIKE THE WORLD'S TOP COMPANIES
MARTY CAGAN
WITH LEA HICKMAN, CHRISTIAN IDIODI, CHRIS JONES, AND JON MOORE
Silicon Valley Product Group
TRANSFORMED
MOVING TO THE PRODUCT OPERATING MODEL
Copyright © 2024 by John Wiley & Sons, Inc. All rights reserved.
Published by John Wiley & Sons, Inc., Hoboken, New Jersey.Published simultaneously in Canada.
Hedcut illustrations © Alison Boddy
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, (978) 750–8400, fax (978) 750–4470, or on the web at www.copyright.com. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748–6011, fax (201) 748–6008, or online at http://www.wiley.com/go/permission.
Trademarks: Wiley and the Wiley logo are trademarks or registered trademarks of John Wiley & Sons, Inc. and/or its affiliates in the United States and other countries and may not be used without written permission. All other trademarks are the property of their respective owners. John Wiley & Sons, Inc. is not associated with any product or vendor mentioned in this book.
Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created or extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Further, readers should be aware that websites listed in this work may have changed or disappeared between when this work was written and when it is read. Neither the publisher nor authors shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages.
For general information on our other products and services or for technical support, please contact our Customer Care Department within the United States at (800) 762–2974, outside the United States at (317) 572–3993 or fax (317) 572–4002.
Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic formats. For more information about Wiley products, visit our web site at www.wiley.com.
Library of Congress Cataloging-in-Publication Data:
Names: Cagan, Marty, author.
Title: Transformed : moving to the product operating model / Marty Cagan, with Christian Idiodi, Chris Jones, Lea Hickman, and Jon Moore.
Description: Hoboken, New Jersey : John Wiley & Sons, Inc., [2024]
Identifiers: LCCN 2023049041 (print) | LCCN 2023049042 (ebook) | ISBN 9781119697336 (hardback) | ISBN 9781119697404 (adobe pdf) | ISBN 9781119697398 (epub)
Subjects: LCSH: Organizational change. | Product management. | New products.
Classification: LCC HD58.8 .C24 2024 (print) | LCC HD58.8 (ebook) | DDC 658.4/06—dc23/eng/20231019
LC record available at https://lccn.loc.gov/2023049041
LC ebook record available at https://lccn.loc.gov/2023049042
COVER DESIGN: PAUL MCCARTHY
This book is dedicated to Bruce Williams (1950–2016). Bruce was the person who gave me the encouragement and confidence to leave my comfort zone of leading product for other companies and to go out on my own and start the Silicon Valley Product Group (SVPG).
In addition to being an exceptional human who truly helped improve the lives of countless people, he was the best friend that anyone could ever hope for. Bruce provided me everything from office space to expert advice on design, sales, marketing, publishing, finance, and more.
Without Bruce, it's likely I would have stayed a product leader and not had the opportunity to write any books or to enjoy the previously unimaginable quality of life that I've experienced as part of SVPG. I thank Bruce for encouraging me to make the single best career decision I have ever made.
I wish that everyone could be lucky enough to have a Bruce Williams in their lives.
PART IIntroduction
This book has three big goals:
First, we want to educate you as to exactly what the product operating model is and what it means to work in this way.
Second, we want to convince you—primarily with detailed case studies of successful transformations—that, while such transformation is difficult, it is absolutely possible for you to transform your company to the product model.
Third, we want to inspire you—primarily with several truly impressive case studies of product innovation—of what you too will be capable of once you successfully transform your organization.
We start by discussing why we wrote TRANSFORMED and how it relates to the books that led the way to this one: INSPIRED and EMPOWERED.
Next, we lay out the main reasons that companies are motivated to embark on this very significant amount of time and effort to transform.
Then we jump in and describe an all-too-typical transformation effort, which usually yields the same all-too-predictable—and disappointing—results.
It's very important that we provide you with a realistic understanding of what is involved and required for a successful transformation. Many people will try to tell you it's easy—if you simply hire them to help. The reality is very different.
But it's also important that we convince you that it is indeed very possible to succeed. And further, we want you to understand what you'll be able to do as a company once you have developed these new muscles.
Finally, we tackle the dilemma of knowing you need to change, but not necessarily having leaders who have worked this way before.
CHAPTER 1Who Is This Book For?
TRANSFORMED is written for anyone who is trying to help their company move to the product operating model.
That includes:
Members of product teams who are trying to move to the product model
Product leaders trying to guide their company through these changes
Senior executives of the company, especially the CEO and CFO, who want to learn what is involved in moving to the product model, to decide if this is something they wish to pursue, and if so, how they can help
Other company executives, stakeholders, and employees who are impacted by the product model, and want to learn how to constructively engage
Product coaches who are trying to help companies successfully transform to the product model
One very common question is: “We're not a tech company, so is the product model even relevant for us?”
This is a very widespread confusion. When our industry refers to a “tech company,” the term is not referring to what the company sells, it is referring to how the company believes it should power its business.
Tesla sells cars. Netflix sells entertainment. Google sells advertising. Airbnb sells vacation lodging. Amazon started with selling books and now sells just about everything.
The difference is not what these companies sell; it's how they design and build what they sell, and how they run their business.
The product operating model is for companies that believe they should be powering their business with technology. Today, that's a very wide range of businesses across virtually every industry.
How does this book relate to INSPIRED and EMPOWERED?
We wrote INSPIRED to share the best practices and techniques used by the top product teams operating in the product model.
Then we wrote EMPOWERED to share the best practices and techniques used by the top product leaders to provide their product teams with the environment they need to thrive in the product model.
Yet, by far the most common question we get is: “Our company operates so differently from what you describe. Is it even possible for a company like ours to change to the product model, and how would we change?”
The goal of this book is to answer that question.
For the past 20 years, we at SVPG have been helping companies through these changes.
What we've learned is that there are some companies—mostly newer companies that were created in the internet era—born out of this new model of technology-powered product companies. For them, this way of working is quite natural.
However, for the vast majority of companies in the world, the ways of working we describe are very foreign.
One CEO described the experience of transforming as “changing from driving on the right side of the road to the left—but gradually.”
These companies know they need to transform to compete in an era of rapidly changing enabling technology, but they have found that the degree of change necessary is substantial, and anything but easy.
If you've read INSPIRED or EMPOWERED, then you'll recognize the components of the product model, but those books don't address how to make the necessary changes to how you work.
If you have not read our other books, this book was written to provide the necessary understanding of the concepts of the product model and give you the foundation you need.
CHAPTER 2What Is a Product Operating Model?
Unfortunately, the tech industry is not great when it comes to standardization of terms. We often have different terms for the same concept and, in some cases, different definitions of the same term.
We don't like introducing new nomenclature, but we do need to be clear on what we mean when we talk about important concepts in this book.
The most fundamental concept we use and need to be clear on is the general product operating model.
We did not invent the term—we've found it in use in several strong product companies, and several more use the shortened form product model.
The product operating model is not a process, or even a single way of working. It is a conceptual model based on a set of first principles that strong product companies believe to be true. Principles such as the necessary role of experimentation, or prioritizing innovation over predictability.
We're using the term in this book to refer to the way of operating that we find the best product companies consistently use.
Essentially, the product operating model is about consistently creating technology-powered solutions that your customers love, yet work for your business.
From the financial perspective, it's about getting the most out of your technology investment.
It's important to emphasize that there is no single right way to build products. There will be more on this critical point later. But for now, know that there are many good ways, much as there are an even larger number of bad ways.
It's also a good time to point out something we emphasize in each of our books: Nothing you will read in this book was invented by us. We simply write about what we observe in the best product companies. That said, we don't write about everything we see; we focus on what we believe are the common themes and first principles. We are effectively playing the roles of curator and evangelist.
The product operating model is sometimes referred to as product-led company or product-centric company. We don't like those terms because they often have the unfortunate side effect of implying that the product organization is taking over.
Similarly, while the product operating model is an example of a customer-driven company, that term has been misused to the point that it has lost its utility.
A tougher concept to name is the model you might be coming from.
The main influence on how the company thinks of its previous model is generally this: Who is really in the driver's seat?
In many companies, you'll hear constant references to “the business” in terms of making requests, and they're running what is commonly referred to as the IT model (as in “IT is there to serve the business”).
A close cousin of the IT model is the project model, where the CFO plays an outsize role because funding and staffing are typically project based.
If general stakeholders are in the driver's seat, then it's often called the feature-team model (because each stakeholder drives their roadmap of features).
If sales is driving, then you'll often hear the term sales-driven product, and if marketing is driving, you'll hear marketing-driven product.
Throughout this book, we refer to whatever model you are coming from as your prior model, and we refer to the model you're working to transform to as the product operating model, or simply the shortened term product model.
In part III of this book, Transformation Defined, you'll see a detailed definition of what it means to work in the product operating model.
There are several other important product terms and concepts that we discuss in this book, and we will define those as we go.
What Is a Product?
This seemingly simple question comes up very frequently, but there are several layers to this question, and there are different reasons that people ask the question.
Sometimes the person is concerned they are not working on something that is customer-facing, such as an e-commerce app or a consumer device. Maybe they are working on an internal tool, used by employees at their company to take care of the company's paying customers. Or maybe they're working on a platform service that is used to build other types of products. Or maybe a back-office–style system that provides critical data. Or maybe the person is building a device and not purely software. We have different terms for these types of products, but rest assured, these are all products that the product model is designed to help with.
Sometimes the question is whether what you're working on constitutes a complete product, or if it's just a small piece of something much larger. This is getting at the important topic of something we call team topology, but for our purposes, these are all considered products as well, even if just a small part of a larger whole.
And sometimes people are asking the question because they are not actually building anything. Plenty of types of products are not technology-powered products built by engineers. Perhaps the person manages a relationship with a third-party vendor, and they are wondering if the product model applies to them as well. In this case, no. The product model is meant to address the unique challenges of those who are building technology-powered products and services.
CHAPTER 3Why Transform?
By making the decision to read this book, odds are you already have your reasons for embarking on a transformation.
But with the stakes so high, and the effort required so substantial, it's helpful to have a clear articulation of your purpose.
Generally speaking, we find companies are motivated by one or more of three major drivers:
A Competitive Threat
Few industries remaining have not already been attacked by new competitors providing demonstrably better solutions for customers.
As of this writing, the latest disruptive technology, Generative AI, is already reshaping the competitive landscape for many industries. As is always the case, some companies are leveraging this new technology to solve long-standing problems for their customers in ways that are just now possible, and other companies are being left behind.
This process of disruptive innovation has taken place in industries as varied as financial services, health care, retail, automotive, logistics, advertising, and even space exploration.
Certain industries have higher switching costs, more significant regulatory hurdles, or a degree of government protection, so this disruption has taken longer, but few companies feel truly secure.
These companies realize they are competing in a battle for customers with weapons and strategies that once worked but that today cannot match the tools and capabilities of their new adversaries.
A Compelling Prize
Other companies are motivated by the financial rewards available to those companies that have demonstrated the ability to consistently innovate on behalf of their customers.
They see the valuations of the new generation of companies, as well as the rewards to those that have successfully transformed, and the promise of this prize motivates investors, executives, product leaders, and employees to pursue this path.
Frustrated Leaders
Some companies pursue the product model because they have grown frustrated at the level of funding they've been pouring into their technology efforts, with so little in return.
The constant cost overruns, the disappointing results, the time it takes to ship anything, customers who are losing patience, and the endless stream of blaming and excuses.
Perhaps the leaders have read about companies that spend less yet generate much more, and they wish to learn if these methods might apply to them.
In some cases, one or more additional factors conspire to push a company to the point where its leaders feel they must take the leap to transform:
Perhaps you find your most capable technology employees leaving your company out of frustration with the current way of operating.
Perhaps your company has hired a leader who comes from a strong product company and has been encouraging others to consider this approach.
Perhaps your customers' expectations have changed, and while they wish to remain loyal, they are increasingly vocal about their frustrations with your offerings and your pace of improvement.
Whatever the motivations, fundamentally, companies transform because they believe they need to be able to successfully take advantage of new opportunities that arise and effectively respond to serious threats.
CHAPTER 4A Typical Transformation
Most companies that we've engaged with on a transformation have already tried to transform—at least once—before they realized they've spent a lot of time and money going nowhere.
The story that follows is all too common. We've removed the names, but the circumstances are very real. See how much of their story you recognize.
This company had dominated the financial operations market since its inception in 2000. It had always had a strong customer focus, priding itself on being able to deliver exactly what the customer requested, which ended up driving a long series of “specials” to meet the perceived needs of different individual customers.
Initially, this focus on doing whatever was necessary to close the deal achieved some real business success. Internally and externally, delivering quickly on client needs became a key brand strength.
That is, until it wasn't.
Despite increasing headcount and a culture of long working hours, the time to deliver new capabilities had noticeably slowed. At the same time, there were several new entrants to the market. Each had moved fast to gain traction. The result was that sales had started to lag, and market share was dropping.
In response, the company pursued a strategy of aggressive acquisition, moving quickly to purchase and integrate additional solutions. But far from igniting a new era of profitability, the acquisitions proved problematic and were not generating the hoped-for revenue.
A New Start
The board reacted, taking action to make changes at the very top.
The company's incoming CEO arrived with an impressive commercial track record. After quickly making her1 way through the ranks of a global consultancy to become its youngest senior partner, she then assumed a variety of C-level roles across numerous commercial finance organizations.
As a first-time CEO, she understood that her career would be defined by her results. This was no time to fail, and she had done her homework. The company still had strong market share, a recognized brand name, and was profitable. But she knew change was required—she had pitched as much to the board. Her appointment was based on a mandate to reinvigorate the brand.
The playbook was well rehearsed, one she had practiced across multiple different sectors in her years as a management consultant. She quickly got to work diagnosing the problems.
The company had become a sprawling organization, with offices across the globe, including in the US, India, and Europe. The resulting cultural differences ran deep.
After years of acquisition-led growth, the company was essentially several companies, with little integration, heavy technical debt, and frustrated customers.
The new CEO's previous relationships allowed her to quickly employ the advice of consultancy services, which helped to rapidly diagnose some key legacy practices.
The changes would need to be significant. They included a new, centralized organizational structure, the insourcing of engineering, a more focused business mission, and the creation of a new product unit housing product managers and designers. A new chief digital officer (CDO) was hired to lead the transformation effort.
Friction and Pushback
Numerous challenges were taken on in parallel, not least the insourcing of engineering. Hiring a team of 600 engineers in tough market conditions meant high salaries, and 12 months in, the company had exceeded the budget but was still short of its required numbers. To keep costs down, rather than hire skilled product managers, the company opted to retitle a team of business analysts. The rationalization was that the product suite was complex and required deep domain experience.
Change was proving to be more disruptive and costly than the company had originally anticipated. Sales, long regarded as the sole owner of customer success, was not happy with the changes and complained directly to the CEO. While the new CDO reported positively on new engineering hires and the creation of multiple product teams, things were moving slowly, and costs continued to increase.
Away from the ears of the executives, the incoming engineers gasped at the levels of technical debt. Each one of the acquired businesses had continued to operate on its legacy technical stack. There had been no serious attempt to integrate their solutions. Many of the original people were gone. Those who were left could barely keep many of those systems running. The engineers saw no real alternative to immediate replatforming.
Privately, leadership was sympathetic to the new engineers, but there was little appetite to take on yet another significant effort, this time for replatforming. They were encouraged to refactor where they could but to try to find a way to accelerate the roadmap delivery.
After two years of transformation, things were moving slower than ever. The CEO decided that the core issue was with engineering, and they needed help to deliver predictable and reliable results.
Focus on Predictability
The CIO recommended a switch to a new, more formal and structured engineering delivery process, and teams were retrained on this process in hopes of increasing predictability, albeit with longer, less frequent release cycles.
But with even fewer releases, the new battleground was which business unit could shoehorn in sufficient amounts of features to satisfy the pain—and cost—of customer upgrades. There was also significant new process overhead.
With all eyes on each and every lengthy release, a team of program managers was hired to oversee the delivery process by adding a layer of governance and control.
As costs continued to increase, releases became few and far between. Meanwhile, competitors were thriving. The board's initial expectations of success were now all but forgotten.
Additionally, a key number of the recently hired engineers had resigned, citing a failure of leadership. Customer retention was proving increasingly difficult, with many frustrated by the all-too-obvious lack of progress.
Believing they had nothing to lose, a small number of product and engineering leaders chose to speak directly to the CEO.
Their technology, they argued, was preventing the company from meeting the needs of customers, and the level of bureaucracy was now so high that they felt no ability to make any forward progress.
None of the options was good. The technology mismanagement of the past had finally caught up with the company.
With tens of millions of dollars in transformational costs spent, the CEO wondered what the company had to show for it. After four years of pain and expense, and with the combined frustration of her fellow executives bearing down on her, the CEO was informed she no longer had the support of the board.
The company's transformation had, gradually, then all at once, failed.
Note
1
Aligned with our long-standing interest in expanding the perception of who a strong leader is, we use she/her pronouns throughout this book. That being said, this book is intended for
anyone
of
any
gender identity. Our view is that if you are a good person who cares about the craft of product, we hope to have you as a friend.
CHAPTER 5The Role of the CEO
Probably the most important lesson we have learned in 20 years of helping companies with transformations to the product model is the absolutely critical role that the CEO needs to play in order for the transformation to succeed.
Please don't misunderstand. The CEO does not need to have prior experience with the product model. And the CEO doesn't have to spend a lot of time on the transformation itself.
But, nevertheless, the CEO role is critical.
Now, every CEO will of course say she supports the transformation.
Yet most don't truly realize what this means until much later in the effort.
Here is the problem: Transformation impacts the company far beyond what was previously your technology department.
The issue is that transformation impacts sales, marketing, finance, HR, legal, business development, compliance, and manufacturing.
In this book, we discuss precisely how and why transformation impacts each of these areas. But the important point here is that not every key leader and stakeholder will be enthusiastic about moving to this new way of working.
Most will be motivated to at least try out an approach that holds the potential for better results. And many of these people realize that learning to work effectively in the product model is increasingly an asset to any resume.
It's also important to realize that even the most enthusiastic stakeholder or executive may have questions or very legitimate objections that they want to make sure are addressed.
But some will passively resist, and likely a few will actively resist. Either because they are protecting their current responsibilities, or because of the age-old preference for the devil you know versus the devil you don't.
These problematic stakeholders all eventually report up to the CEO, and that's whom they will look to decide if this is truly important and necessary.
As the legendary coach Bill Campbell used to say: “The company cares about what the leader cares about.”
Too often, the CEO delegates ownership of the transformation to a CIO, a chief digital officer, or a chief transformation officer. And while these individuals can influence decisions and actions within their organization, unless the stakeholders report to them (which is rarely the case), this same problem will result.
If you're a CEO, this may be the first time you're learning that transformation is something that goes beyond IT. If that's the case, it's critical that you consider this new information.
It's true that most companies begin their transformation efforts by focusing on the necessary changes to product, design, and engineering. And that's appropriate because until and unless those capabilities are established, the rest is premature.
There are new competencies you'll need to develop, new skills and new principles to instill in your organization, and, most important, a cultural change that needs to take place.
However, too often it is only after those changes are made that the company realizes that taking advantage of these new capabilities impacts the entire company. And when the CEO and the other senior leaders are not actively supportive of these changes, the transformation effort stalls out.
To be explicit: The CEO needs to be viewed as the chief evangelist for the product model.
If this is something your CEO is unwilling or unable to do, then you can likely save yourself a lot of time, money, and effort by reassessing your readiness.
However, the good news is that a company operating successfully under the product model improves the situation for everyone, not just the product and engineering organization.
Employees feel more pride in the company's products. Marketing has more to promote and position. Sales can sell more. Everyone sees the financial impact. Employee morale and retention improve.
Which is all to say that there's a strong case to be made to justify the active help and support of the CEO.
CHAPTER 6A Guide to TRANSFORMED
We hope that by now you are starting to develop an appreciation for what we mean when we say that transformation is hard.
This book is intended to prepare you for what lies ahead.
One thing you won't find in this book is any sort of recipe or playbook for transformation. Many people out there will try to sell you such a thing, but unfortunately, we have never seen these one-size-fits-all, overly simplified approaches work.
Interspersed throughout the book are Transformation Stories—case studies of successful transformations—as well as Innovation Stories—case studies of innovative solutions created by companies that have previously transformed.
The transformation case studies are meant to give you confidence that, although difficult, success is absolutely possible. These stories are shared with you by the person who was leading the product organization at each of these companies.
The innovation case studies are intended to get you excited about what you'll be able to do once you've transformed.
Beyond the case studies, the book is organized into the following parts:
We start things off in part II, Transformation Defined, with a comprehensive definition of what is truly meant by transformation to the product operating model.
The next two parts get to the heart of the new skills and capabilities you'll need to develop to move to the product model.
In part III, we begin by discussing the new Product Model Competencies you will need to develop in order to transform. If you think you already have these competencies in your company, you are almost certainly wrong and headed for transformation failure. Don't be fooled by people who have simply adopted these titles.
Next, in part IV, we present the Product Model Concepts—and the product model principles they are based on—that are the foundation of the product model. Most companies very quickly realize that they don't yet have these skills, which is the first step to learning them.
The new product model competencies and the product model concepts are the foundation upon which transformation rests.
In part VI, The Product Model in Action, we discuss how the product organization constructively and effectively partners with customers, sales, product marketing, finance, stakeholders, and the senior executives.
Next, in part VIII, we discuss the Transformation Techniques that are helpful in guiding your organization through a change of this magnitude. Change is always difficult, but there are several key techniques and tactics designed to facilitate transformation. We begin with an organization assessment, then we describe a variety of tactics. We also describe the importance of ongoing transformation evangelism.
You may already realize there's a bit of a catch-22 going on here. How does a company that has never worked in a new way, and may not have any leaders who have worked that way, learn this new way of working?
Books and various types of training can help (if the authors and trainers know what they're talking about), but they are rarely sufficient. We explore how you can move to the new model when your leaders have never worked this way before.
Next, in part X, Overcoming Objections, we discuss the various concerns that commonly arise from each key stakeholder—sales, marketing, customer success, finance, HR, the CIO, the PMO, the CEO, and the board—and also the objections that come from inside the product organization.
These are all legitimate objections and concerns, and people typically raise them in good faith, simply because they can see an issue and they don't yet know how that issue will be addressed. We consider each of these objections and then discuss how to overcome them.
In part XI, Conclusion, we try to connect the dots and summarize the critical points discussed in the book, including the common themes from the transformation case studies and the keys to success.
Tough Love for Product Leaders
Successful transformation is hard to pull off, and it requires tackling tough issues where often the people involved really don't want to hear it.
So, in that spirit, we'll start with a bit of that tough love right now, intended for the product leaders:1
There is no question that the executives of the company have a major role to play in helping the company transform.
However, the surprise for so many product leaders is that they have at least as much work to do.
It is truly perplexing how many product leaders believe that once the senior executives change their ways, all will be good. They focus their energy on getting others to change, rather than on changing themselves.
They complain about having weak product managers.
They complain about not being empowered.
They complain about engineers who don't seem engaged.
They complain about having stakeholders that don't trust them.
They complain about CEOs who demand detailed product roadmaps.
Yet, they don't seem to realize that each of these problems is very much a consequence of their own actions (or inactions, as the case may be).
