post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Guest Post

How to build a companion product and win user trust

mission statement

Deep dive: Crafting your product vision and mission

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

Join us at #mtpcon London in 2025 – mark your calendars

Connecting fans to creators at Spotify (Dariusz Dziuk, Product Lead, Spotify)

Why teams often struggle with OKRs: A conversation with Jeff Gothelf

5 ways to invent and simplify as an AI/ML product manager

Louron serves as the Editor at Mind the Product, bringing nearly a decade of experience in editorial positions across business and technology publications. For any editorial inquiries, you can connect with him on LinkedIn or Twitter.

Louron Pratt

In this Sunday Rewind post, we go all the way back to the pre-pandemic days of March 2016 when Martin Eriksson shared his thoughts on why Product Requirement Documents (PRDs) don’t always work.
Martin believes that PRDs and various other documents similar to this focus on the solutions, not problems. He says “I believe product manager’s job is to focus on defining and prioritising the customers’ problem, not the solution.”
This means that once you get it in front of the design and engineering teams, you can work together to come up with the best possible solutions to that problem that fit within the scope or budget of the project. However, by definition, PRDs force you to start documenting features and requirements (the solutions) upfront.
Additionally, he mentions how they are often “open to interpretation”. The individual who reads them and has to act on them is generally not the person who wrote them, so you’re basically playing telephone whispers with your product.
Martin offers an alternative and argues that it’s important to go back to the first principles and work collaboratively with research, design, and engineering as one team to design the right product for your customer.
He closes by listing what you should focus on instead of writing a PRD: 
<ul>
<li>Individuals and Interactions.</li>
<li>Working with software (or hardware)</li>
<li>Customer collaboration</li>
</ul>
<a href="https://www.mindtheproduct.com/product-requirement-documents-must-die/" target="_blank" rel="noopener">To delve further into Martin’s argument, read Product Requirement Documents Must Die in full.</a>
<hr />
Want to share your thoughts on this article? <a href="https://community.mindtheproduct.com/c/start-here/" target="_blank" rel="noopener">Use Circle—our members’ discussion platform exclusive to MTP members—to drive the discussion and share your product experiences</a>.

core/freeform

Common transformation pitfalls by Marty Cagan

Using principles to make better decisions faster by Martin Eriksson

How to build for creators by Peter Yang

How to navigate tricky work relationships

Organizing around complex products at the intersection of physical and digital by Matthew Cornford

Scaling Empowered Teams: Advice From Nilan Peiris

Bottom-Up Product Strategy – The State of Product, by Susana Lopes

Testing Business Ideas, by David Bland

How to Connect Your Product Work to Your Top Business Metrics, By Pratima Arora

Atomic Product Strategy, By Rob Hayes

SUNDAY REWIND: Product requirement documents must die

ProductTank Kraków

ProductTank Cardiff

ProductTank Bangalore

ProductTank Mumbai

ProductTank Johannesburg

ProductTank Tauranga

ProductTank Bielefeld

ProductTank Auckland

ProductTank Vilnius

ProductTank Timisoara

ProductTank Stockholm

ProductTank München

ProductTank Düsseldorf

ProductTank Birmingham

ProductTank Norwich

ProductTank Heidelberg

ProductTank Malmö

ProductTank Amsterdam

ProductTank Barcelona

ProductTank Newcastle Upon Tyne

ProductTank London

ProductTank Curitiba

ProductTank Brisbane

ProductTank Perth

ProductTank Málaga

ProductTank Buenos Aires

ProductTank Tokyo

ProductTank Braunschweig

ProductTank Edinburgh

ProductTank Pittsburgh

ProductTank Dubai

ProductTank Vienna

ProductTank Bristol

ProductTank Washington

ProductTank Valencia

ProductTank Raleigh

ProductTank Brno

ProductTank Paris

ProductTank Orlando

ProductTank Rotterdam

ProductTank Montréal

ProductTank Bangkok

ProductTank San Diego

ProductTank Hong Kong

ProductTank Charlotte

ProductTank Exeter

ProductTank Manchester

SUNDAY REWIND: Product requirement documents must die

Louron Pratt

Read more

Comments