Product demos & UI / Prompt

Prompt: build a report around one question

Build the report around a question the viewer can answer from the finished view. Show why the selected fields matter and keep the interpretation inside the sample’s scope.

By AnimroUpdated 2 min readAI-assisted · independently agent-reviewed

Who this is for: Teams explaining report builders.

What to prepare

  • Field definitions
  • Sample records
  • Builder and result states

Copyable creative brief

An authored planning example. Replace illustrative details with your approved product facts and assets.

Create a 30-second illustrative report demo answering “Which sample requests await review?” Use a fictional dataset of four requests: R-014 Awaiting review, R-015 Draft, R-016 Awaiting review and R-017 Approved. In the supplied report builder, select Identifier, Subject and Status, then apply the actual Status equals Awaiting review condition. Show any real run or save action. Inspect the resulting two matching rows, R-014 and R-016, with the condition visible. Name the report “Sample review queue.” End with “Two sample requests match this condition.” Do not infer team performance, delays or customer outcomes. Do not invent aggregation or filtering controls. If the product’s field labels differ, update the brief and all sample states consistently.

Make it your own

Question
Choose one answerable reporting question.
Fields
Use actual definitions and labels.
Dataset
Make rows and counts consistent and visibly illustrative.

Prepare the report inputs

Supply field definitions, actual builder controls and the matching dataset. Keep one row per request unless the product’s report model uses another unit. Duplicate events can otherwise make a request count misleading.

Adapt the question

For a date question, state which date field is filtered. For a grouped view, explain the grouping and use totals consistent with the rows. Avoid adding a chart merely because the builder supports it.

Fix unbounded interpretation

Replace “Your team has two unfinished requests” with the scoped sample conclusion unless the view truly covers that entire population. If the result includes unexpected rows, verify condition logic instead of deleting them from the image.

Review checklist

  • Field choices serve the opening question.
  • Filter logic explains every result.
  • The conclusion is limited to the shown scope.
Explore product demos & ui ↗