Startup Product Management

Marty Cagan argues that the common startup approach of funding engineers to build a product before validating it is inefficient and causes many good ideas to fail. Founders typically act as product manager, build in stealth mode, and only show an alpha after months of spending, when the product often misses. He proposes starting with a small team of product manager, product designer, and prototyper to rapidly iterate on a high-fidelity, non-functional prototype validated with real target users. This typically takes 3 weeks to 2 months and yields a validated product, a living spec for engineering, and a clearer understanding of the challenge. Cagan notes the approach is standard in manufacturing and applies to large companies too, though startups have less runway to absorb iteration.

01Key takeaways

• Validate the product idea with real target users before committing large engineering budgets.
• Assemble product management, product design, and prototyping roles before hiring engineers.
• Iterate on a high-fidelity prototype daily, accepting fake back-end data to focus on the user experience.
• Use the validated prototype as a living spec so engineering starts with clear requirements.
• Expect the prototype phase to take roughly three weeks to two months and to save money overall.

02Key sections

The conventional startup model

Founders fund engineers early to build a product in stealth mode, defining requirements on the fly. The first demo after months usually goes poorly and burn rate becomes critical.

A prototype-first alternative

Hire a product manager, product designer, and prototyper before engineering to run rapid design and iteration cycles. Each iteration moves closer to a winning product.

Keys to the approach

Build a high-fidelity prototype that mimics the user experience, with fake back-end data acceptable, and validate it with real target users.

Outcomes and benefits

The process yields a validated product, a rich prototype serving as a living spec, and deeper understanding, letting engineering build faster and better.

Broader applicability

Prototype-based experimentation is normal in manufacturing and should be adopted in software, and larger companies can benefit from it too.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.