Opens in a new tab
14 min 34 sec
Available in:Englishไทย

Inspired: How To Create Products Customers Love

Shows product managers and their teams how to choose the right opportunities and prove a product is valuable, usable and feasible with realistic prototypes and real users before engineers start building it.

Table of Content

Most new products miss their goals. In Inspired, Marty Cagan, who held senior product roles at eBay and Netscape, puts the failure rate at nine releases in ten. His diagnosis points less at engineering than at a product manager role nobody defined well, or a person unable to fill it. Cagan’s remedy is to treat product work as discovery. Before engineers write any code, a small team proves that an idea is valuable to customers, usable by them and feasible to build, by putting a realistic prototype in front of real people. That discipline, backed by clear roles and firm priorities, is the thread through everything that follows.

Along the way come a seven-question test for any new idea, a way to recruit eight to ten customers as partners, two invented users named Mary and Freddy who settle feature fights, and a careful method for changing a product people already depend on. Anyone who builds, funds or manages products gets a routine for releases that actually land.

Most product releases miss their goals, and the reason usually sits in one poorly defined job. The person who can fix that may already work for you, in a department nobody thought to check.

A product manager surrounded by the wrong roles, or by roles with fuzzy borders, burns out on work that is not hers. One device’s success shows which role companies most often underrate.

Two search engines once looked unbeatable, and then they were not. A short page of questions helps decide which openings deserve a team’s effort, and it deliberately leaves one thing out.

Many products fail one of three tests that could have been run before a line of code. The trick is shrinking the idea far enough to test it, and then knowing when to stop changing it.

A prototype can replace a thick spec and serve as a test on the same day. What you do while users try it matters as much as what you show them.

Asking customers what they want rarely produces a good product. A small group recruited the right way does far more, and pays the team back a second time on launch day.

Every feature debate pits strong opinions against each other. An auction site’s priority and two invented customers show how a team can settle arguments before they start.

After launch, the easy path is to add whatever customers ask for. That habit can damage a good product, and so can a well-meant change released the wrong way.

Inspired is finally an argument about where risk belongs. Most teams carry it into engineering and learn only after months of building that customers do not want the product, cannot use it, or that it costs more than anyone guessed. Cagan pulls that risk forward. A product manager fluent in technology and business, a team with clear roles, and designers allowed to finish first can find out before the build what a failed release would have revealed after it. The tools are modest: a page of questions, a clickable prototype, ten customers who share the pain, two invented people named Mary and Freddy. Their strength comes from the order in which they are used.

The habits follow from that order. Before committing to an idea, write down what problem it solves and for whom, without describing a feature. Put a realistic prototype in front of real people early, then say nothing and watch. When the product is live, tie each change to a metric and warn users before it lands.

Nine releases in ten miss their goals. The ones that land were proved before they were built.

About this book

What is this book about?

Most product releases fail to reach their goals, and Marty Cagan traces much of that failure to one job. When the product manager role is poorly defined, or held by someone who cannot fill it, teams end up building things customers do not want or cannot use. Cagan, a former senior product leader at eBay and Netscape, describes what the role really involves: judging which opportunities deserve pursuit and defining the product that answers each one. He sets out the team a product manager needs, from engineers treated as peers to a full design group, and argues that design should finish before building begins. The heart of the book is product discovery. Readers learn to test an opportunity with seven plain questions, define a minimal product, and try a high-fidelity prototype on real users while changes are still cheap. Cagan adds a charter user program of eight to ten customers, product principles and personas for settling tradeoffs, and a careful way to improve products already in customers' hands.

Book Information

Rating:

Genre:

Technology & the Future

Topics:

Product Strategy, Product-Market Fit

Publisher:

Wiley

Language:

English, ไทย

Narrator:

Peter

First published:

January 1, 2008

Pages:

368

Length:

14 min 34 sec

Get the book:

Amazon

Who it's for

  • Deciding what to build

    Product managers who keep shipping features that miss their targets and want a tested way to decide what to build.

  • Founders testing an idea

    Founders turning an idea into a first product who need to know it is worth building.

  • Eyeing a product role

    Engineers, designers and analysts hoping to move into a product role.

Listen to Preview

About the Author

Marty Cagan

Before founding the Silicon Valley Product Group, Marty Cagan was a senior product leader at eBay, Netscape Communications and other companies. Over his career he has filled most of the jobs inside a technology product organization, including software development, design, product marketing and general management. Today he writes, speaks, advises and coaches through his firm, and he is asked to speak at conferences and companies worldwide. He also co-authored Empowered and Transformed.

Ratings & Reviews

Ratings at a glance

4.4

Overall score based on 597 ratings.

What people think

Listeners consider this title essential reading for product managers, offering a broad perspective on the field along with actionable tips. The content is accessible and educational; one listener points out that it is jam-packed with advice. Its motivational quality is well-regarded, with one person highlighting its ability to assist in creating products that change people's lives. Opinions on the prose are divided, as some value the brevity of the writing while others describe it as poor.

Top reviews

Takeshi

Finally got around to reading this after seeing it on every essential list imaginable. Frankly, the hype is mostly justified because Cagan cuts through the noise of corporate bureaucracy to focus on what actually matters: product discovery. The way he frames the distinction between delivery and discovery changed how I approach my weekly sprints immediately. While some sections feel a bit like a lecture, the actionable advice on high-fidelity prototypes is worth the price of admission alone. It’s a high-level overview that manages to stay grounded in the reality of modern tech organizations. If you want to build products that people actually use instead of just shipping features, this is your roadmap. Just don't expect it to solve every tiny tactical bug on your Jira board.

Show more
Audrey

This book is essentially a masterclass in how to build a product-focused organization from the ground up. Marty Cagan writes with a no-bullshit attitude that I find incredibly refreshing in a sea of fluffy business books. He isn't just an anonymous voice; his credibility as a guru for tech leaders shines through in every chapter. I particularly enjoyed the focus on empowering teams rather than just tasking engineers with tickets. Truth is, most companies are still stuck in the old way of doing things, and this provides the blueprint to escape that trap. It’s jam-packed with advice that feels both visionary and surprisingly practical for everyday use. A must-read for anyone serious about the craft.

Show more
Gioia

The chapter on building a product team is arguably the most valuable part of this entire book. It’s rare to find an author who understands the nuances of marketing, design, and engineering as well as Cagan does. He emphasizes that product managers must let UX designers fully contribute before tasking the dev team, which is a lesson many organizations still need to learn. Look, the writing style is concise and punchy, making it easy to digest during a busy work week. I’ve already started implementing his advice on usability testing and the results are promising. It’s a truly decent guide for anyone serious about delivering products that change people’s lives. Every CEO should have a copy on their desk.

Show more
Connor

Wow, this really is the gold standard for a reason. Cagan manages to condense decades of Silicon Valley experience into short, focused chapters that don't waste a second of your time. I was particularly impressed by how he handles the hidden costs of custom development and stakeholder management. It’s an updated version that feels contemporary, moving beyond the old-school specifications and into a world of continuous testing and validation. Frankly, I wish I had read this four years ago when I was first starting out in tech. It provides the kind of inspiration that makes you want to go back to the office and overhaul your entire workflow immediately. Absolutely essential for any growth-stage company.

Show more
Eli

As someone who has been navigating the product world for years, I found this to be a solid reminder of core principles. It focuses heavily on the organizational challenges of development, which is where most PMs actually struggle. To be fair, if you’re looking for hyper-tactical, step-by-step guides, you might find more value in the SVPG blog or various online resources. However, the book serves as a healthy reminder of our critical role in balancing user needs with business viability. My only gripe is that it feels very B2C-centric, which can be frustrating for those of us in B2B with long sales cycles. Still, it’s a decent introduction for anyone entering the field or looking to refresh their perspective.

Show more
Brooklyn

Ever wonder why some companies churn out hits while others just spin their wheels? Marty Cagan argues it’s all about the culture of discovery and the use of high-fidelity prototypes to test assumptions early. I appreciate his stance on role separation, though I’ve definitely seen successful products launch without the rigid team structures he advocates for. In my experience, the utopia he describes can feel a bit theoretical, especially when dealing with stubborn CEOs. Also, prototypes answer if someone can use it, but not always if they will pay for it. That said, the concise chapters make it an easy read over a weekend. It's a great companion for beginners, even if it ignores some of the grit of the B2B world.

Show more
Layla

After hearing so much praise for this book, I finally dove in and was pleasantly surprised by the depth of insight. It’s not a full compendium of every possible PM skill, but it hits the big rocks with incredible precision. I especially liked the discussion on dealing with special requests from major customers—a common headache that usually goes unaddressed in these types of books. Personally, I think the focus on passion and being enamored with the product is a bit much. Most of us just want to do a good job and go home. Regardless, the core framework for product discovery is excellent. It’s a strong companion for anyone looking to transition from a feature-factory mindset to being truly product-led.

Show more
Tariq

Look, if you are a product manager in the B2B space, take some of this advice with a grain of salt. While the discovery techniques are brilliant, they assume a massive pool of users and mountains of data that just don't exist in enterprise sales. That being said, the book is still a mandatory read for its perspective on the PM's role as a leader. Cagan’s writing is practical and easy to understand, even if it feels a bit repetitive at times. The emphasis on high-fidelity prototypes answering the usability question is a great starting point for any team. It’s a good holiday read that will leave you feeling recharged and ready to tackle your roadmap with fresh eyes.

Show more
Joe

Truth is, I found the philosophy in this book to be a little bit alienating at points. The author suggests we should be obsessed with our products and work infinite hours to achieve success, which just isn't a sustainable way to live. Not everyone wants to live for their company, even if they are a high-performing PM. Beyond the work-culture issues, the book is quite theoretical and often paints an ideal world that doesn't exist in most budget-strapped startups. While the sections on role separation were interesting, I’ve seen plenty of great products launch without the proper team structure he demands. It’s okay as a high-level overview, but it didn’t quite deliver the tactical guidance I was hoping for.

Show more
Divya

Not gonna lie, I expected a bit more substance from such a highly-rated title. If Cagan’s idea for a product utopia is Hewlett Packard, then we are all doomed to endless meetings and corporate red tape. The content feels dated in the current landscape, particularly the strict distinction between discovery and execution phases. Many of the examples sound like a boring lecture rather than real-world case studies I can apply immediately to my team. While there are some healthy reminders about stakeholder management, the overall tone is far too high-level. It misses the daily grind. I picked this up after a great review in the Economic Times, but I walked away feeling disappointed by the lack of tactical depth.

Show more
Show all reviews

Questions about this book

Cagan argues that most product releases fail mainly because the product manager’s role is poorly defined or the person in it is unable to fill it. A product manager’s job is to assess opportunities and define products for them, and with a well-defined team she must show that each product is valuable to customers, usable by them and feasible to build. The proof comes from a realistic prototype tested with real users as early as possible, before engineering starts.

It is a short set of questions Cagan uses to judge a product opportunity before anyone designs a solution. It asks what problem would be solved and for whom, how large the market is, what competitors offer and why this team can win, which factors and metrics matter, why the timing is right and how the product will be sold. The answers support a clear go or no-go decision with senior management.

A charter user program recruits eight to ten customers from the target market who feel the problem the product addresses. The team develops and tests the product with them as partners. Customers get early, usually free access to a fix for a painful problem, and the team gets fast feedback on prototypes. At launch, those customers serve as satisfied references. Cagan warns against shaping the product around just one or two participants.

Build a high-fidelity prototype that looks real but has minimal functionality, such as clickable pages for a simple website. Recruit testers from any source, including friends, family or people found through Craigslist. Decide in advance which tasks they should complete, focusing on the ones they will spend most time on. During the test, say as little as possible and watch where they struggle. Fix obvious problems right away so the next testers see the improved version.

It suits product managers at technology companies and the leaders who hire them. Leaders get a picture of the traits to look for and the team roles to set up. Practitioners get working tools: an opportunity assessment, minimal products, prototype tests, charter users, principles and personas. People in engineering, customer service or marketing who want a product role will also find a clear description of what the job demands.

AUDIO SUMMARY AVAILABLE

Listen to Inspired in 15 minutes

Get the key ideas from Inspired by Marty Cagan, plus 5,000+ more nonfiction titles.

  • 5,000+ titles
  • Listen as much as you want
  • 7-day free trial
  • Cancel anytime

Inspired

Preview · Full summary 14 min 34 sec
Home

Discover

Open app

Log in