Stress test data conclusions with counterarguments
Challenge data findings and business recommendations before presenting them. Use this to catch false correlations, survivorship bias, and hidden assumptions.
You getCore Vulnerabilities, skeptical Audit Questions and data Validation Checklist
Prompt
Act as a skeptical principal data scientist and strategy auditor. Stress-test the analysis and conclusions provided below to uncover hidden biases and weak assumptions.
Rules:
- Challenge assertions based on correlation versus causation.
- Identify data blind spots, such as selection bias, survivor bias, seasonality, or missing cohorts.
- Formulate tough, specific counterarguments that a critical executive or competitor would raise.
- Do not affirm the findings; prioritize finding structural vulnerabilities in the logic.
Output format:
1. Core Vulnerabilities (table: Claim Made, Logical Weakness, Alternative Explanation)
2. Skeptical Audit Questions (5 challenging questions the analyst must answer)
3. Data Validation Checklist (specific checks needed to defend the thesis)
Data conclusions and context are below:Example output
Paste your draft insights, presentation claims, or memo conclusions into ChatGPT, Claude or Gemini. Follow up by asking the model to suggest control groups that could definitively prove or disprove your primary hypothesis.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Detect hidden assumptions in reported dashboard numbers
Surface filtering tricks, omitted baselines, and date cutoffs hiding behind pasted dashboard metrics. Use this before presenting figures to executive leadership.
Audit driver-based models for compounding optimism bias
Expose subtle, compounding growth assumptions across pipeline stages and conversion metrics. Use this during quarterly budget reviews and board deck prep.
Create an anomaly investigation checklist for analytics teams
Run a disciplined diagnostic process before investigating metric shifts. Use this checklist whenever unexpected data spikes or drops appear in reports.
Differentiate structural null values from missing data
Identify whether null values represent expected business logic or export dropouts. Use it when auditing schema quality or preparing datasets for modeling.
Evaluate past forecast variances to set accurate targets
Analyze past forecast misses to identify systematic over- or under-projection patterns. Use this before locking in next quarter's revenue or operational targets.
Map inconsistent export columns to target schemas
Match disparate, poorly named export headers to a structured target data schema. Use it when consolidating CSV reports from multiple platforms.
- Normalize retention comparisons for immature recent customer cohorts
- Sanity check revenue projections against past baselines
- Segment conversion funnel drop-offs by device and marketing channel
- Separate true anomalies from pipeline data errors
- Summarize customer segment shifts for executive updates
- Translate statistical model outputs into plain business decisions