PRFAQ in Product Management and Why It Matters
- blogs, product management
- 4 min read
Author: Akansha Chauhan – Product Marketer
Many product teams are good at building products, but the harder problem is deciding what to build. Building a product takes engineering time, budget and operational effort. Thus, the decision about what to build is one of the most important decisions in product management.
This is why product discovery exists. Product discovery helps teams understand the customer, the problem, the value, and the business impact before development starts. One of the frameworks used in product discovery is Press Release and Frequently Asked Questions (PRFAQ), a method used at Amazon as part of the Working Backwards approach introduced by Jeff Bezos and later explained by Marcelo Calbucci.
To understand why PRFAQ matters in product management, it is important to first understand the problem it solves.
- PRFAQ is used in the product discovery stage before development begins.
- PRFAQ helps teams decide whether a product idea should be built.
- PRFAQ comes before PRD and roadmap in the product lifecycle.
- The FAQ section evaluates feasibility, risks, and business impact.
- PRFAQ aligns stakeholders before development starts.
- PRFAQ helps companies make product and investment decisions
The Problem With How Many Products Are Built
Many companies start product development with an idea, then move to roadmap planning, and then start development. Only later do they realize that the product does not solve a strong customer problem or does not create enough business value.
Studies on product failures often show that lack of product market fit and poor understanding of customer needs are among the most common reasons products fail. This is why companies invest in product discovery frameworks to evaluate ideas before development begins.
What Is PRFAQ?
PRFAQ stands for Press Release and Frequently Asked Questions. It is a written document created before development begins that describes a future product launch and answers important questions about the customer, the problem, the solution, the business model, risks, and execution in order to evaluate whether the idea should move forward.
PRFAQ Structure
Section | Purpose |
Press Release | Product vision and customer value |
Customer FAQ | Customer questions and benefits |
Internal FAQ | Feasibility, risks, business model, execution |
Appendix | Data, research, metrics |
The press release explains the future value of the product, and the FAQ section evaluates whether that future is realistic and achievable. To understand PRFAQ better, it is important to see where it fits in the product management process.
Where PRFAQ Fits in Product Management?
Product management involves more than building products. It involves multiple stages such as product discovery, planning, development, and execution. Different documents are used at different stages, and each document serves a different purpose.
PRFAQ is used in the product discovery stage. The goal at this stage is to understand the customer, define the problem, evaluate the idea, and decide whether the product should be built. After this stage, teams move to planning and development.
The table below shows where PRFAQ fits in the product management process and how it is different from other product documents.
Stage | Document | Purpose |
Discovery | PRFAQ | Decide what to build |
Planning | Roadmap | Decide when to build |
Delivery | PRD | Decide how to build |
Execution | Sprint | Build the product |
The table shows that PRFAQ is used at the discovery stage to decide what to build, which is why it is considered a product discovery and decision making document rather than a product delivery document.
PRFAQ vs PRD vs Pitch Deck vs Roadmap
Product teams use different documents at different stages of product management. Each document serves a different purpose, and confusion between these documents often leads to poor product decisions.
PRFAQ is used to evaluate and decide whether an idea should be built. PRD is used after the decision is made to explain how the product will be built. Pitch decks are used to present ideas and get approval or funding. Roadmaps are used to plan timelines and prioritize work.
The table below explains the role of each document more clearly.
Document | Stage | Purpose |
PRFAQ | Discovery | Evaluate the idea, define customer value, identify risks, and decide whether the product should be built |
PRD | Delivery | Define product requirements, features, and technical details so the team can build the product |
Pitch Deck | Proposal | Present the idea to stakeholders, leadership, or investors to get approval or funding |
Roadmap | Planning | Plan product timeline, prioritize features, and decide when the product will be built |
The comparison shows that PRFAQ is used before PRD and roadmap because it helps teams decide whether the product should exist in the first place. Once the decision is made, PRD and roadmap are created to plan and build the product, which places PRFAQ in the discovery stage and PRD and roadmap in the planning and delivery stages.
Why PRFAQ Matters in Product Management?
Press Release and Frequently Asked Questions (PRFAQ) is crucial in product management due to its ability to assess product concepts, grasp customer value, analyze business impact, and pinpoint risks prior to allocating time and resources into product development.
PRFAQ helps product teams in the following ways:
- It helps teams clearly define the customer and the problem before development begins.
- It enables teams to assess the product value and business impact before investing resources.
- Risks, dependencies and constraints can be identified at an early stage of the process.
- To reach consensus on a product vision, goals and expected outcomes prior to development.
- Teams are able to make structured product decisions instead of opinion-based decisions.
- Companies can decide where to invest time, money, and engineering resources.
- Low-impact product ideas can be identified and stopped early.
One important part of PRFAQ that makes this possible is the difference between the press release and the FAQ section.
Press Release vs FAQ
PRFAQ has two main parts, the press release and the FAQ section. Both sections serve different purposes, and understanding the difference between them is important to understanding how PRFAQ works as a decision framework.
The press release focuses on the future vision of the product, the customer problem, the solution, and the value the product will create. The FAQ section focuses on feasibility, risks, execution, and business impact. This section evaluates whether the idea described in the press release is realistic and worth building.
The table below shows the difference between the press release and the FAQ section.
Press Release | FAQ |
Vision | Feasibility |
Customer value | Risks |
Future state | Execution |
Benefits | Costs |
Positioning | Metrics |
The comparison demonstrates how the press release tells us about the success of the product to come, while the FAQ tells us whether that success is achievable in the future. The press release is intended to tell the reader why the product exists, while the FAQ section tells the reader how the product will function, the risks associated with the product, and how success will be determined.
For this reason, many of the product leaders believe that the most crucial section of PRFAQ is the FAQ section, where the idea is judged, the presumptions are tested, and the final decision is made.
The PRFAQ Process
PRFAQ is not written once and approved immediately. The document usually goes through multiple reviews, discussions, and revisions before a final decision is made.
The goal of the PRFAQ process is to evaluate ideas, discuss assumptions, identify risks, and align stakeholders before development begins and before resources are committed.
The PRFAQ process in most teams is a formal review process that includes writing the process, soliciting feedback from stakeholders, editing the process, and revisiting the process. This cycle is repeated until the team and leadership are sure that the idea is working or they decide to discontinue the idea.
The PRFAQ process usually includes the following steps:
- Research and customer discovery to understand the problem and the customer
- Write the first PRFAQ draft
- Stakeholders read the document and review the idea
- Discussion and feedback session
- Revise the document based on feedback
- Repeat the review and revision process
- Final decision to move forward or stop an idea
This results in teams spending more time thinking about building, due to the reduction of the risk of building the wrong product.
When PRFAQ Is Used?
PRFAQ is employed when a team is assessing an idea, clarifying a customer and problem and determining if a project should proceed. The framework is useful when the call to action requires engineering, monetary, and time investment, and the team requires clarity before they start the action.
PRFAQ is commonly used in the following situations:
- New product ideas – Teams use PRFAQ to evaluate new product ideas, define the target customer, and decide whether the product should be built.
- New features – PRFAQ can be used for large features where teams need to evaluate customer value, business impact, and technical feasibility before development.
- Internal tools – Many internal tools have internal teams as customers. PRFAQ helps define the internal user problem and evaluate whether building the tool is worth the effort.
- Platform products – Platform teams often build tools or infrastructure for other teams. PRFAQ helps platform teams define the internal customer, use cases, and expected impact.
- Process improvements – PRFAQ can be used to evaluate process changes that impact teams, operations, or customer experience.
- Business initiatives – Companies use PRFAQ to evaluate new business ideas, new markets, or new service offerings before investing resources.
- Strategy proposals – PRFAQ is also used to propose new strategic initiatives and align leadership before execution begins.
These examples show that PRFAQ is used whenever a team needs clarity, alignment, and a clear decision before execution begins.
“Work backwards from the customer, not forward from the technology.”
PRFAQ is applied to assess ideas prior to development and to help the team determine customer value, feasibility, stakeholder alignment and product decisions. In product management, it’s not always about how to build, it’s about what to build, and PRFAQ can help decide what to build in a structured manner.
Frequently Asked Questions
1. What is PRFAQ in product management?
PRFAQ is a product discovery document used to define customer value, evaluate risks, test assumptions, and decide whether a product should be built before development begins.
2. Why is PRFAQ important?
PRFAQ is important because it helps teams make better product decisions, reduce risk, and align stakeholders before development starts.
3. What comes first, PRFAQ or PRD?
PRFAQ comes first. PRFAQ decides what to build, and PRD explains how to build it.
4. Is PRFAQ only used for new products?
PRFAQ can be used for new products, internal tools, platform initiatives, and business strategy proposals.
5. Who writes PRFAQ?
PRFAQ is usually written by product managers and reviewed by engineering, leadership, marketing, finance, and operations teams.
