Inspired: How To Create Products Customers Love [Kindle Edition]

It is a pity that there are only 5 stars to award the maximum appreciation for this book. There are a number of achievements that deserve, alone, five stars.

First, Marty Cagan clearly states what qualities a Product Manager must have. Not everyone is talented to be a Product Manager. The author lists unmeasurable traits, such as product passion, customer empathy, innate intelligence (there is no substitute for it, we learn), ethics, integrity and confidence. The latter is very important as the entire teams in engineering and marketing must be kept inspired. This leads to the corollary that simply training a person to be a Product Manager is not enough. One must know when an unsuitable person must look for other positions. This is something uncommon, to consider what many view a process driven function to a talent.

Second, the book asks where to place the Product Manageent function. In Engineering? In Marketing? There is a distinction between a Product Manager and Product Marketing Manager. As veteran product manager myself, I know the challenges to be part of engineering. Engineers are sometimes suspicious of marketing and their product manager becomes the "piñata" everyone beats in frustration. As part of Marketing, there is tendency to follow release processes and create demands engineering can not deliver in a logical way. Marty advocates the creation of a Product Council with equal rights as engineering and marketing

Marty says a successful product manager sees himself as the CEO of the product. This is absolutely true, but unfortunately the Directors of Engineering and those of Marketing, also see themselves as CEOs. As long as an independent product council does not exist, the product manager must be a CEO with zero authority. S/he must be a diplomat and shrewd negotiator before he can be a CEO. Yet the true blue blood product manager is the one whose skills are required for start up.

As startup is usually a one product or service company. Chapter 28 is dedicated to product management in a startup company. The challenge is a new start up is started with an idea that comes from engineering. However we must have the right product for the right audience, before "before burning through $500,000 or more in seed funding".

Every aspect of the product management function is presented.

I am an alumni of UC Berkeley Haas School Product Management executive program, one of few, if not the only program dedicated to Product Management. Berkeley program talks of portfolio management. What products to release, how many are completely new and how many are new releases of older or even very old products?

It all depends on the risk tolerance. A products portfolio must include new high risk, lottery-like winning products. This is what made Silicon Valley, Silicon Valley. After reading Marty Cagan, every professional team all over the world can produce "inspired" products. Silicon Valley and it's personalities now share all they know. But what is a low probability to create outside Silicon Valley is another Google. The Google Sequoia Capital VC's made more money in Google than all the rest of the portfolio combined over the last 20 years.

Another topic that I would have liked to see expanded in a next edition is pricing. How do we price the products in such a way that we do not leave money on the table? But this is another subject. Marty's book is both educational and thought provoking. The book self published by Silicon Valley Product Group, the company of Marty Cagan, went beyond the goal of being a reference for it's prospective v customers. It is THE BOOK for of product management, a must-read for anyone.

The idea of the product manager as a creator with talent and passion I advocated for years in my blog, "The memories of a Program Manager". It is re-assuring to see the same sentiments shared in the more comprehensive, practical and sensitive book of Marty Cagan..

I spent years as an interface designer in a risk-averse Fortune 500 company as the sole advocate for usability, wearing the additional hats of information architect, HTML coder, visual designer, and more. In that company, the developers were an abusive bunch who called the shots, fought me on every design proposal, and demanded tons of documentation before anything was ever built. I also had little access to end users. There were maybe two releases per year, and they were always painful.

I left that environment to become a user experience consultant in another Fortune 500 company. Despite the fact that I now had a fresh start in a friendlier environment with a more collaborative team of developers, I was wary and defensive. I didn't want to blow my new gig, though, so I was looking for guidance fast. I read two books that saved me: Alan Cooper's "Inmates Are Running The Asylum", and "Inspired".

Prior to these books, I'd heard the terms "waterfall" and "agile" before but never really knew what they meant. But now it was like suddenly learning the name of an affliction from which I'd been suffering. Several times while reading "Inspired" I caught myself saying, "Yes - yes, that's it! That's what happened to me!" It really was like the song by Roberta Flack: this guy knew my pain and had could have BEEN me in some of the stories he describes.

I'm not able to put into practice everything Mr. Cagan describes in an optimal environment, but thanks to this book I have a much better understanding of my hats, including ones I didn't know I was wearing. His insights have helped me learn to pace myself, and perhaps even more importantly, to forgive myself if I don't get to every single thing. I highly recommend this book to user experience professionals who are working for large organizations where it is a challenge to introduce and nurture new thinking.

Even though I'm a total "one click" junkie, and often make book recommendations to friends and co-workers, I've never taken the time to post a review until today.

So why now? I've been working in and around product management for over 10 years and I really, really wish that I could have had the benefit of a resource like this when I started. Inspired should absolutely be required reading for anyone in the product development space: product managers, UX designers, engineers, projects managers, marketing--anyone responsible for the creation of new products (or the significant improvement of existing products that are missing the mark somehow).

[Disclaimer: I've been a fan of Marty's blog and newsletter for several years now, so most of the information in the book was not new to me. I also hired Marty (twice) as a consultant--which should make this recommendation even more credible because I put my money where my mouth is regarding his insight and the value he brings to organizations!]

Even though I was already very familiar with most of the topics covered in the book, I still pre-ordered it and read it cover to cover as soon as it arrived.

Having all of this information together and organized like this allows readers to get the benefit of Marty's 20+ years of experience--as an executive at some of the leading companies in Silicon Valley as well as through his consulting practice--in one concise package. This guy knows his stuff and, as a result, there's no more comprehensive resource for product managers out there--not even close!

In his Introduction Marty writes: "I chose this career because I wanted to work on products that customers love; products that inspire and provide real value... Yet most products are not inspiring, and life is too short for bad products." Amen!

So read Inspired, and give a copy to anyone else who you want to be successful in the product creation space. They'll thank you for it.

P.S. Chapter 31: Succeeding in Large Companies alone is worth the price of the book if you take his advice and start employing these 10 techniques in your current job!