# PRD Lite

## When to use

Use this template when a request is important enough to need written alignment, but not complex enough to justify a long, heavy PRD. It is designed for quick product definition, cross-functional review, and early execution alignment.

## Input needed

Prefer to gather the minimum useful context:

- background or trigger
- target user / affected segment
- problem to solve
- desired outcome or success criteria
- major constraints
- dependencies or known risks

If 1-2 critical premises would materially change the solution, ask about those first.

## Output goal

Produce a short, execution-ready PRD that is clear enough for review, design, engineering discussion, and scope alignment.

---

# PRD Lite

## 1. Background

- What triggered this work?
- What changed, broke, or became important?
- Why are we discussing this now?

## 2. Problem statement

- What problem are we solving?
- For whom?
- What is unsatisfactory in the current state?
- Are we solving the real problem, or jumping too early to a solution?

## 3. Goal and success criteria

### Goal

- What outcome should this work create?

### Success criteria

- What will we use to judge whether this worked?
- Prefer specific user, business, or operational outcomes.

## 4. Target users and core scenarios

### Target users

- Who is this primarily for?
- Which segments matter most in this phase?

### Core scenarios

- In what moments or workflows will users encounter this?
- Which scenario must work well first?

## 5. Proposed solution

- What is the proposed product change?
- What is the core user flow?
- What is the simplest version that still solves the problem?

## 6. Scope

### In scope

- What is included in this version?

### Out of scope

- What is intentionally not included?
- What can wait until later?

## 7. Key requirements

- Functional requirements
- Important UX or behavior rules
- Business or policy rules
- Important edge conditions if relevant

## 8. Constraints and dependencies

- Time constraints
- Resource constraints
- Technical dependencies
- Cross-team dependencies
- Compliance / review needs if applicable

## 9. Risks and open questions

### Risks

- What could reduce success?
- Where may delivery or adoption fail?

### Open questions

- What still needs confirmation before execution?

## 10. Rollout and validation plan

- How should this be launched?
- What do we need to monitor after launch?
- What early signals will tell us whether to continue, adjust, or roll back?

## 11. Next steps

- What should happen after this PRD is reviewed?
- Who needs to review, design, estimate, or validate next?

---

## Misuse guard

Do not treat this as permission to write a smaller bloated PRD.
If the draft still hides the real problem, keeps scope fuzzy, or uses completeness to cover weak judgment, shorten it and sharpen the decisions instead.

## Notes for use

A strong PRD Lite should:

- define the problem clearly before detailing features
- stay short enough to read in one pass
- make scope boundaries explicit
- identify risks and unknowns honestly
- be specific enough that execution can start
