working-backwards_skill

Overview

This skill teaches the Working Backwards product method: define the customer problem and desired outcome first, then design the solution. It guides teams to write a customer-facing press release and FAQ before building. The result is clearer product intent, measurable success criteria, and reduced risk of building solutions in search of problems.

How this skill works

The skill leads you through creating a one-page press release that describes the target customer, the problem, and the single compelling benefit. It then builds an FAQ that confronts hard questions, trade-offs, and success metrics. Use the artifacts to align stakeholders, scope work, and decide whether to proceed before committing engineering resources.

When to use it

• Defining a new product or major feature before development
• Evaluating and comparing competing product ideas
• Aligning cross-functional stakeholders on customer value
• Forcing clarity when concepts are vague or solution-led
• Deciding whether an idea is worth investing in

Best practices

• Write the press release first and treat it as the north star for scope and messaging
• Define a specific customer and measurable outcomes, not "everyone" or vague benefits
• Keep the press release focused on one compelling benefit; avoid feature bloat
• Make the FAQ honest: surface uncomfortable trade-offs and assumptions to test early
• Iterate PR/FAQ through concentric-review cycles before design and engineering work begins

Example use cases

• A PM needs to choose between three competing feature bets and justify one with customer outcomes
• A startup founder wants to validate product-market fit before hiring engineers
• A product leader wants a clear launch narrative and measurable success criteria for a major initiative
• A team is stuck in solution-first thinking and needs to reframe around customer jobs-to-be-done
• Preparing a go/no-go decision for a roadmap item with documented assumptions and risks