More on this book
Community
Kindle Notes & Highlights
A good PR/FAQ honestly and accurately assesses these dependencies and describes the specific concepts or plans for the product to solve them.
Feasibility
The fact that most PR/FAQs don’t get approved is a feature, not a bug. Spending time up front to think through all the details of a product, and to determine—without committing precious software development resources—which products not to build, preserves your company’s resources to build products that will yield the highest impact for customers and your business.
Another one of the biggest benefits of a written PR/FAQ is that it enables the team to truly understand the specific constraints and problems that would prevent a new product idea from being viable and aligning on them.
Jeff would say something to the effect of, “We shouldn’t be afraid of taking on hard problems if solving them would unlock substantial value.”
keep in mind that the PR/FAQ is a living document.
a huge benefit of the process—a considered, thorough, data-driven method for deciding when and how to invest development resources.
