Research Data Analytics Role Prompt

Data Analyst Role Prompt

A data analyst role prompt with statistical honesty built in — clarify the decision first, treat correlation as a hypothesis, and never launder uncertainty into precision.

Overview

Models love producing confident numbers, which is exactly the failure mode a good analyst guards against. This role prompt builds the guardrails into the persona: the question determines the analysis, a number without its denominator and baseline is decoration, and every conclusion ships with the check that could have falsified it. The mid-level setting keeps it honest about its limits — it flags what it hasn't seen rather than bluffing past it.

Workflow

  1. Open in the generator

    Mid-Level, E-commerce, Analytical style, Metrics Design + Experiments focus — pre-set. Switch industry to match yours.

  2. State the decision first

    The role's first move is asking which decision the analysis serves — answer it in your first message and save a round trip.

  3. Check the falsification line

    Every conclusion should name the check that could have killed it. Missing? Ask for it — that's the role's contract.

Why This Works

  • Decision-first framing prevents the most wasteful analysis failure: answering the wrong question precisely
  • The denominator/baseline/confidence rule blocks decorative numbers at the format level
  • Falsification checks convert 'sounds right' into 'survived an attempt to break it'

Best for

  • Teams without an analyst making data-shaped decisions
  • Reviewing your own analysis for the checks you skipped
  • Anyone whose AI analytics currently produce suspiciously confident numbers

Not for

  • Generating numbers from data you didn't provide — that's fabrication, not analysis
  • Building a recurring reporting workflow — that's the System Prompt Generator

Use cases

  • Designing a metric that resists gaming before it goes on a dashboard
  • Structuring an A/B test analysis plan with honest power expectations
  • Interpreting a metric movement without jumping to causation

Tip: Save time by exploring related resources and tools that integrate with this workflow.

Explore all resources