Use when asked to "working backwards", "PR/FAQ", "Amazon PR/FAQ", "write a press release", "define a new product", or "write a customer-focused PRD". Helps define products by starting with the customer problem and desired outcome before building. The Working Backwards process (developed at Amazon) forces clarity on customer value before committing engineering resources.
Working Backwards is a product development method that starts by defining the customer problem and desired outcome before designing a solution. It requires writing an internal press release and FAQ upfront to clarify the value proposition and ensure alignment on what success looks like. This approach reduces wasted effort by forcing teams to articulate a compelling customer benefit before committing engineering resources.
Rather than beginning with technology or features, Working Backwards reverses the process to prioritize customer needs. It helps teams avoid building solutions in search of problems and creates clear, measurable criteria for product decisions. The method is especially useful for defining new products or major features with a shared vision across stakeholders.
This skill is ideal for growth leads and product strategists responsible for launching new offerings or major features. Agency strategists working with clients on product-market fit can use it to evaluate and prioritize ideas before development. Performance marketers involved in go-to-market planning benefit from the clarity and alignment Working Backwards brings to messaging and positioning.
Teams facing competing product concepts or vague briefs will find this approach valuable to focus efforts and avoid costly missteps. It suits scenarios where stakeholder alignment is critical and where customer clarity is needed to make confident build/no-build decisions.
Practitioners begin by drafting an internal press release that clearly states the customer problem, the product’s key benefit, and measurable outcomes. Next, they develop a detailed FAQ that anticipates difficult questions and defines scope, success metrics, and potential challenges. This FAQ forces teams to confront uncertainties and refine assumptions early.
The draft PR/FAQ is then circulated for iterative review across engineering, design, marketing, and leadership to build consensus and identify gaps. Only once the document convinces stakeholders of the product’s value does the team proceed to development, ensuring resources are focused on validated customer needs.
How detailed should the press release be? It should be concise but specific enough to convey the core customer benefit and measurable outcomes. Will this method slow down fast-moving teams? While it adds upfront work, it typically saves time by preventing costly rework and misaligned builds. Can this be used for minor feature updates? It is best reserved for new products or significant features, not incremental tweaks or bug fixes.
Attach the Working Backwards skill to a Metaflow agent task when defining new products or major feature initiatives that require clear customer-focused outcomes. Expect the agent to guide you through writing a press release and FAQ that clarify your product vision and success criteria. This structured approach helps align stakeholders and reduce ambiguity early in the project lifecycle. You can then build workflows that incorporate iterative feedback and validation checkpoints to refine your PR/FAQ before committing to development.
For broader context, see our roundup of claude marketing skills, and read ultimate guide to Claude marketing skills for related setup guidance.