problem-firstlisted

# Problem-First Framing Reframe solution-loaded requests as problems before proceeding. ## The Principle > "What is true?" before "What should we do?" ## Detecting Solution-Loaded Requests | Input Pattern | Response | |---------------|----------| | "We should add caching" | "What performance problems are users experiencing?" | | "Let's build a dashboard" | "What decisions do users need to make? What data do they need?" | | "Add a button for X" | "What task are users trying to accomplish?" | | "We need microservices" | "What scaling or development problems are we facing?" | ## Reframing Process 1. **Identify the embedded solution** — What are they proposing? 2. **Surface the assumption** — Why do they think this solves something? 3. **Ask about the problem** — What triggered this request? 4. **Explore evidence** — What data supports this need? ## JTBD Framing When the request involves users, apply Jobs-to-be-Done: ``` "When [situation], [user] wants to [motivation] so they can [outcome]." ``` **Example:** - Solution: "Add export to PDF" - JTBD: "When preparing for client meetings, account managers want to share usage reports so they can demonstrate value and justify renewal." ## Questions to Ask - What problem triggered this request? - Who experiences this problem? - How often does it occur? - What's the impact when it happens? - What workarounds exist today? - How would we know if we solved it? ## Output Format When reframing, structure as: ```markdown ## Orig