# Problem and Solution

This document separates the user problem from the proposed implementation. A problem remains true even if the chosen interface or technology changes.

[Kit README](README.md) · [Project Overview](Project%20Overview.md) · [PRD](Full%20PRD%20Template.md) · [Master Build Prompt](Master%20Build%20Prompt.md) · [Completion Checklist](Project%20Completion%20Checklist.md)

## Problem Statement

**[TARGET USERS]** experience **[MAIN PROBLEM]** when **[TRIGGER OR CONTEXT]**. Today they **[CURRENT BEHAVIOR]**, which causes **[MEASURABLE COST, DELAY, RISK, OR FRUSTRATION]**. Evidence: **[SOURCE OR “ASSUMPTION”]**.

## Root-Cause Check

| Why? | Answer | Evidence Needed |
| --- | --- | --- |
| Why does the visible problem occur? | [CAUSE 1] | [CHECK] |
| Why does that condition exist? | [CAUSE 2] | [CHECK] |
| Why has the current workaround persisted? | [CAUSE 3] | [CHECK] |
| Which cause can this project realistically change? | [ADDRESSABLE CAUSE] | [PROOF] |

## Proposed Solution

**[PROJECT NAME]** will help the primary user complete **[CORE TASK]** by providing **[SMALLEST COHERENT CAPABILITY]**. It will not promise outcomes outside its control. The first release should be able to demonstrate:

- The user can understand the offer within ten seconds.
- The user can reach any primary page in two navigation actions.
- The user can submit a contact request with clear confirmation.

## Solution Mechanisms

| User Need | Product Behavior | Evidence of Success | Failure Behavior |
| --- | --- | --- | --- |
| understand the offer within ten seconds | responsive header and navigation | [OBSERVABLE RESULT] | [SAFE RECOVERY] |
| reach any primary page in two navigation actions | purpose-built page templates | [OBSERVABLE RESULT] | [SAFE RECOVERY] |
| submit a contact request with clear confirmation | contact form with validation and spam controls | [OBSERVABLE RESULT] | [SAFE RECOVERY] |
| understand the offer within ten seconds | SEO metadata and structured content | [OBSERVABLE RESULT] | [SAFE RECOVERY] |
| reach any primary page in two navigation actions | analytics with consent-aware events | [OBSERVABLE RESULT] | [SAFE RECOVERY] |

## Non-Goals

Version 1 will not include CMS authoring, multilingual content, site search, personalization, advanced experimentation. It will also not claim live integrations, real customers, verified accuracy, or complete automation when only sample behavior exists.

## Alternatives Considered

1. **Do nothing:** What happens if the user keeps the current process?
2. **Manual service:** Could a person or checklist solve the problem before software is justified?
3. **Existing product:** What already works, and where is the genuine gap?
4. **Smaller feature:** Can one focused workflow create most of the value?

## Acceptance Criteria

- [ ] The problem is written without naming a preferred technology.
- [ ] At least two root causes are supported by evidence or clearly labeled assumptions.
- [ ] Every proposed behavior maps to a user outcome.
- [ ] Non-goals prevent the most likely scope expansion.
- [ ] The solution addresses domain risks including unclear positioning and oversized media.
- [ ] A reviewer can explain how success and safe failure will be observed.