# Working Backwards

> Help PMs apply the working backwards methodology. Use when defining a new product, writing a PR/FAQ, or planning from a future state.

- Skill: `sach1ng/working-backwards` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add sach1ng/working-backwards`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sach1ng/working-backwards/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Sach1ng (https://skillmd.com/u/sach1ng)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sach1ng/working-backwards

---


# Working Backwards

Help PMs apply the working backwards methodology: start from the customer and desired outcome, then work backward to define the product. Produces PR/FAQ, press release, and customer-first plans.

## When to Use

- Defining a new product or major initiative
- Writing a PR/FAQ (Press Release / Frequently Asked Questions)
- Planning from a future state
- Clarifying value proposition before building
- When asked "help me think backwards" or "write a press release"

## Process / Template

### 1. Define the Future State

- **Customer** — who is this for?
- **Problem** — what pain are we solving?
- **Ideal outcome** — what does success look like for the customer?
- **Emotional payoff** — how does the customer feel when it works?

### 2. Write the Press Release

Imagine the product is launched. Write a 1-page press release as if it's real:

**Headline**
- Bold, benefit-focused (not feature-focused)

**Subhead**
- One sentence: who it's for and why it matters

**Problem**
- 1–2 paragraphs: the pain today

**Solution**
- What we built and how it solves the problem

**Quote**
- Customer or executive quote (aspirational)

**Call to Action**
- How to get it, try it, learn more

**Closing**
- Company boilerplate (optional)

### 3. Write the FAQ

Anticipate questions from internal and external audiences:

**Customer FAQ**
- What is it? How do I get it? How much does it cost?
- What if I have [edge case]?

**Internal FAQ**
- Why are we building this? What's the business model?
- What are we not building? What's out of scope?
- How will we measure success? What could go wrong?

### 4. Derive Requirements

From the press release and FAQ:
- What must be true for the press release to be accurate?
- What are the must-have capabilities?
- What can we defer to v2?

### 5. Validate

- Does the press release pass the "so what?" test?
- Would a customer care? Would they share it?
- Is the problem real and meaningful?

## Output

A **Working Backwards Package** including:
- **Press Release** — 1 page, customer-facing, benefit-led
- **FAQ** — customer and internal questions with answers
- **Implications** — what we must build (high-level)

This becomes the north star for the product and can feed into a PRD or one-pager.