Book Image

Lean Product Management

By : Mangalam Nandakumar
Book Image

Lean Product Management

By: Mangalam Nandakumar

Overview of this book

Lean Product Management is about finding the smartest way to build an Impact Driven Product that can deliver value to customers and meet business outcomes when operating under internal and external constraints. Author, Mangalam Nandakumar, is a product management expert, with over 17 years of experience in the field. Businesses today are competing to innovate. Cost is no longer the constraint, execution is. It is essential for any business to harness whatever competitive advantage they can, and it is absolutely vital to deliver the best customer experience possible. The opportunities for creating impact are there, but product managers have to improvise on their strategy every day in order to capitalize on them. This is the Agile battleground, where you need to stay Lean and be able to respond to abstract feedback from an ever shifting market. This is where Lean Product Management will help you thrive. Lean Product Management is an essential guide for product managers, and to anyone embarking on a new product development. Mangalam Nandakumar will help you to align your product strategy with business outcomes and customer impact. She introduces the concept of investing in Key Business Outcomes as part of the product strategy in order to provide an objective metric about which product idea and strategy to pursue. You will learn how to create impactful end-to-end product experiences by engaging stakeholders and reacting to external feedback.
Table of Contents (19 chapters)
Lean Product Management
Contributors
Preface
Another Book You May Enjoy
Index

Solution #3 – don't strive for throughput, instead restructure teams based on outcome-driven timelines


Releasing often helps us to learn and respond swiftly to feedback, but how often is often? A combination of timeline, effort, and desired outcomes (business and customer impact) may determine how often we release. Some functionality can be built in a few hours. Some can take a few days or weeks. Also, based on the stage of product maturity, we may need less or more focus on technical stability. Technical success criteria are likely to vary based on desired outcomes. Customer context and market needs also have a bearing on how soon or frequently we can update our product.

If something can be released in a few hours and can speed up our feedback cycle, then why wait until the end of day? If something can be released in a day, then why wait until the weekly release cycle? Part of this is how development and production environments are set up, or how code pipelines are structured and so on,...