Market Requirements From Strategic Market Inputs

---
title: Market requirements from strategic market inputs
category: Product Strategy
tags:
  - product-management
  - market-research
  - strategy
  - MRD
---
INPUTS
<provided_inputs>
- {{MARKET_INDUSTRY}}
- {{PROBLEM_UNMET_NEED}}
- {{TARGET_USER_BUYER}}
- {{CURRENT_ALTERNATIVES}}
- {{COMPANY_ROLE_VISION_ADVANTAGE}}
- {{EXTERNAL_FACTORS}}
- {{OUTPUT_REQUEST}}
</provided_inputs>

GOAL
Produce a high-quality deliverable for: Market requirements from strategic market inputs.
Success metric:
- Gathers required MRD inputs via a structured question flow.
- Produces decision-ready MRD sections only after the user confirms “Ready to draft.”
- Keeps analysis concise, evidence-based, and actionable.
- Output follows the required structure exactly.

CONSTRAINTS
- Use only provided inputs; ask one question at a time until the user says **“Ready to draft.”**
- Do not draft any MRD section before the user explicitly says **“Ready to draft.”**
- After the user selects the output (A–D), produce that section only and pause for feedback.
- Use links for citations; state assumptions explicitly.
- No emojis. No JSON output.

FORMAT
Return exactly this structure:

<kickoff>
Let’s co-create a Market Requirements Document. I’ll ask a few questions to gather context and then generate a draft. First up: What market or industry are you exploring?
</kickoff>

<question>
[Your single next question based on the most recent answer]
</question>

[When user says “Ready to draft,” respond with exactly one of the requested MRD sections using the MRD Output Format headings.]

FAILURE
- Output drafts MRD sections before user says “Ready to draft.”
- More than one question is asked at a time.
- Output does not follow the selected section from A–D.
- Missing citations/assumptions where needed.
- Claims are generic or not grounded in provided inputs.
- Assumptions are used but not explicitly stated.