Skip to main content
Data Prompts

Explain Data Findings in Plain English

Translate raw data, statistics, or query results into clear, non-technical summaries for stakeholders.

beginnerWorks with any modelData
Prompt
Translate the following data findings into a clear, non-technical summary for [AUDIENCE].

**Raw findings:**
[DATA_FINDINGS]
(Paste your numbers, statistics, query results, or bullet points here)

**Context:**
[CONTEXT]
(What decision or question these findings are meant to answer — e.g., "whether to expand the marketing budget for Q3")

Write a plain-English summary that:

1. **Opens with the headline** — the single most important finding in one sentence, written as a business insight, not a data description. ("Revenue from mobile customers grew 34% YoY" not "The mobile cohort showed a 34% increase in the revenue metric.")

2. **Explains the 2–3 supporting findings** — each in one paragraph, translating the statistic into what it means for [AUDIENCE]. Avoid jargon, percentages without context, and passive voice.

3. **States the implication** — what should [AUDIENCE] do or decide based on these findings?

4. **Flags the main caveat** — one honest limitation or assumption in the data that [AUDIENCE] should know before acting.

Tone: [TONE]
(e.g., "formal executive briefing", "casual team Slack update", "investor-ready narrative")

How to Use

Paste your raw findings — query output, a summary table, bullet points, even a Python print() block — into [DATA_FINDINGS]. Describe the audience in [AUDIENCE] (e.g., "non-technical marketing managers", "the CFO") and the decision being made in [CONTEXT]. Set the tone to match where this summary will appear.

Variables

VariableDescription
[DATA_FINDINGS]Raw numbers, statistics, or analysis output to translate
[AUDIENCE]Who will read the summary — their technical level shapes vocabulary
[CONTEXT]The question or decision the data is meant to answer
[TONE]Formality and style of the summary

Tips

  • If the AI uses jargon, follow up with: "Rewrite the second paragraph assuming the reader has never seen a cohort analysis before."
  • For executive summaries, ask the AI to limit the entire output to 150 words — constraint forces it to prioritize ruthlessly.
  • Add "Include a recommended next step" to push the summary from descriptive to prescriptive.