Context Problem Solver

Fix prompts with wrong assumptions about your context

analysisbeginnerContext ManagementIndustry Specifics350-450 words
Customize Your Prompt
Fill in the variables to generate your personalized prompt
Preview
See how your prompt will look with the current variables
AI makes wrong assumptions about [Your Industry] and [Company Stage] with: "[Problematic Prompt]"

Role: Product Context Expert with deep industry knowledge.

Instructions:
1. Identify incorrect assumptions
2. Add explicit context constraints
3. Include negative examples (what NOT to assume)
4. Add verification questions
5. Industry-specific parameters

Specifics:
## Assumption Analysis
**Incorrect Assumptions:**
1. [Assumption and why it's wrong for [Your Industry]]
2. [Assumption and correction for [Company Stage]]

## Context Enhancement
**Industry Context:** [[Your Industry] specific constraints]
**Company Stage:** [[Company Stage] considerations]
**User Base:** [Characteristics that matter]
**Constraints:** [Resource/regulatory/technical]

## Revised Prompt with Guards
[Enhanced prompt with explicit context]

**Guard Rails Added:**
- "Note: We are a [Company Stage] [Your Industry] company, NOT..."
- "Our users are [specific], not [common assumption]"
- "Consider [industry-specific factor]"

## Validation Questions
AI should ask these if unclear:
1. [Clarifying question 1]
2. [Clarifying question 2]

Purpose: Ensure AI understands your specific context.

## Important Guidelines

### Confidence Scoring
For all assessments and recommendations, provide confidence levels:
- **High Confidence (>80%)**: Based on clear data, established patterns, or widely accepted best practices
- **Medium Confidence (50-80%)**: Based on reasonable assumptions, limited data, or emerging trends
- **Low Confidence (<50%)**: Based on speculation, very limited information, or untested hypotheses

### Accuracy Requirements
- Mark assumptions with **[ASSUMPTION]**
- Mark estimates with **[ESTIMATE: methodology used]**
- Mark uncertainties with **[UNCERTAIN: reason]**
- Never invent company names, statistics, or case studies
- When data is unavailable, explicitly state what information would improve the analysis
- Distinguish between facts, inferences, and recommendations

### Source Attribution
- General knowledge: "Based on industry standards..."
- Inferences: "This suggests that..."
- Speculation: "One possibility is..."
- Best practices: "Common approaches include..."
What Makes Context Clear to AI
  • Industry and stage constraints made explicit (what to assume, what not to).
  • Negative examples: “Do not assume enterprise budgets” (if Series A).
  • Verification questions the model must ask before answering.
  • Parameterization: users, budget, compliance, data sources, markets.
  • Traceability: call out which assumption drove which recommendation.
Common Context Mistakes
  • Letting the model pick your industry/stage for you (it will be wrong).
  • No guard rails—AI optimizes for a different world than yours.
  • Asking broad questions before basic facts are set (geo, ICP, channel).
  • Zero “what not to assume” examples. They matter more than you think.
Questions PMs Actually Ask (Context)

Why does the advice feel off?

Because it’s answering for a different company. Lock context first: industry, stage, ICP, budget, constraints. Then ask for advice.

Do I need negative examples?

Yes. “Don’t assume we have an enterprise sales team” saves 10 paragraphs of fiction. Guard rails beat cleanup.

How to Use This Prompt

When to Use

Fixing context and assumption problems

Pro Tips

  • Be specific with your variable inputs for better results
  • Review and iterate on the AI output as needed
  • This prompt works best with your specific context added

Expected Output

Context analysis with enhanced prompt

Quick Info
Categoryanalysis
Output Length350-450 words
Web SearchNot Required
Frameworks
Context ManagementIndustry Specifics
Try PM Toolkit Calculators

Turn your AI insights into quantified metrics with our interconnected calculators.