Claude Dashboards & Motion Prompts: 70+ AI Templates for 2026
Claude Dashboards & Motion Prompts: 70+ AI Prompts for Live Dashboards, Animated Explainers and Data Visualization in 2026
Artificial intelligence is moving beyond generating text and answering questions. New AI tools are helping people transform business data into dashboards, explain complicated ideas through animation, and turn information into visual experiences that are easier to understand.
On October 8, 2026, Anthropic introduced Claude Dashboards and Claude Motion in beta. Claude Dashboards is designed to create dashboards using connected data platforms and business systems, while Claude Motion helps turn ideas into animated explainers. Anthropic also announced that Claude Docs, Slides, and Design had moved out of beta and become available on every Claude plan, including Free. Feature availability differs by product and plan.
For creators, marketers, analysts, students, founders, and business owners, this opens up new ways to present information without starting every project from a blank page.
In this guide, you will discover 70+ practical Claude Dashboards and Claude Motion prompts for creating business dashboards, KPI reports, marketing analytics, animated explainers, educational visuals, presentations, and more.
You can adapt these prompts for Claude's supported features or use them with other AI tools that can create dashboards, visualizations, or animations.
Table of Contents
What Are Claude Dashboards and Claude Motion?
How to Write Better Dashboard and Animation Prompts
Master Prompt for Data Visualization
70+ AI Prompts for Dashboards and Motion
Advanced Prompts for Improving Visuals
Common Mistakes to Avoid
Frequently Asked Questions
SEO Settings for Blogger
1. What Are Claude Dashboards and Claude Motion?
Claude Dashboards and Claude Motion are two different AI-assisted creation experiences announced by Anthropic in October 2026. They are designed for different but complementary tasks.
<box gap={3}> <row align=start gap={3}> <AsyncImage query="modern business analytics dashboard charts KPIs clean dark interface" aspectRatio="3:4" maxWidth="112px" /> <box flex="1" gap={1}> **Claude Dashboards**
Create visual dashboards from business data. Anthropic describes connections to data platforms such as BigQuery, Databricks, and Snowflake, as well as CRM systems such as Salesforce. The dashboard feature is in beta on paid plans.
</box></row> <divider color="subtle" /> <row align=start gap={3}> <AsyncImage query="minimal motion graphics animated data storytelling abstract shapes infographic presentation" aspectRatio="3:4" maxWidth="112px" /> <box flex="1" gap={1}> **Claude Motion**
Create animated explainers that help communicate ideas visually. Anthropic announced Motion in beta for Team and Enterprise plans. It is aimed at turning concepts into motion-based explanations rather than relying only on static slides.
</box></row> </box>
What can you create with these tools?
Depending on your access, connected data, and available capabilities, useful projects include:
Sales performance dashboards
Website and SEO reports
Marketing campaign analytics
Revenue and expense visualizations
Customer support dashboards
Project progress trackers
Product performance reports
Animated business explainers
Educational motion graphics
Data storytelling for presentations
Process and workflow animations
Visual summaries of research
Important: A prompt describes what you want, but it does not guarantee that every requested chart, integration, interaction, or animation is supported. Confirm that the connected source is available, validate the output, and never treat an illustrative mockup as verified live data.
2. How to Write Better Dashboard and Animation Prompts
A strong prompt should explain the purpose of the visual, its audience, the data or concept involved, and what the viewer should understand after seeing it.
Use this formula:
For dashboards:
Objective: What question should the dashboard answer?
Data: Which source, table, or dataset should be used?
Audience: Who will use the dashboard?
Metrics: Which measurements matter?
Visuals: Which charts or comparisons will help?
Filters: What dimensions should users be able to explore?
Accuracy: How should missing or uncertain values be handled?
Output: What should the finished dashboard communicate?
For animations:
Message: What idea must the viewer understand?
Audience: Who is watching?
Duration: How long should the explanation take?
Sequence: What should appear first, next, and last?
Motion: How should objects, charts, or diagrams move?
Labels: Which text must remain readable?
Style: What visual language should the animation use?
Ending: What should viewers remember?
For example, instead of writing “Make a sales dashboard,” try:
“Create a sales dashboard for a small online business. Show total revenue, orders, average order value, and monthly growth. Compare the current month with the previous month, include a product-category breakdown, and highlight unusual changes. Use clear labels and distinguish missing data from zero. Finish with three evidence-based observations and avoid making claims that cannot be supported by the connected data.”
This prompt establishes the dashboard's purpose and tells the AI how to handle the information responsibly.
3. Master Prompt for AI Dashboards
Start with this reusable prompt whenever you want to transform a dataset or connected business source into a dashboard.
Prompt 1: Build a Complete Business Dashboard
Act as a senior data analyst and dashboard designer.
Create a business dashboard for the following purpose:
BUSINESS TYPE: [Business or industry]
AUDIENCE: [Owner, manager, analyst, marketing team]
DATA SOURCE: [Connected source or supplied dataset]
TIME PERIOD: [Period to analyze]
PRIMARY GOAL: [Decision the dashboard should support]
Include the following:
1. A clear dashboard title and date range.
2. The most relevant key performance indicators.
3. Charts that answer specific business questions.
4. Comparisons with previous periods where valid.
5. Filters for relevant dimensions, if supported.
6. Clear labels, units, and definitions.
7. An indication of missing, incomplete, or stale data.
8. Three to five observations supported by the data.
9. Potential issues that require further investigation.
10. A concise executive summary.
Use the connected source or supplied data only.
Do not invent figures, fill missing values with guesses,
or imply that the data is live unless verified.
Prioritize readability and decision-making over decoration.
Explain the purpose of each major chart.4. 70+ Claude Dashboard and Motion Prompts
The following prompts are organized by use case so you can quickly find templates for your website, business, marketing projects, presentations, or educational content.
Category A: Business Dashboards
Prompt 2: Executive Overview Dashboard
Create an executive dashboard for a growing business.
Show revenue, expenses, profit, customer growth, and
operational performance using the available data.
Place the most important metrics at the top. Add period
comparisons only where the data supports them.
Highlight material changes, explain the calculation behind
each KPI, and distinguish facts from possible explanations.
End with a concise executive summary and three questions
leadership should investigate next.Prompt 3: Startup Performance Dashboard
Design a startup dashboard for founders and operators.
Include customer acquisition, activation, retention,
monthly recurring revenue where applicable, churn,
cash position, and product engagement.
Use only metrics available in the source data.
Label unavailable metrics rather than estimating them.
Make the dashboard useful for a weekly review and show
which metrics improved, declined, or remained stable.Prompt 4: Small Business Daily Dashboard
Create a simple daily dashboard for a small business owner.
Show today's sales, number of transactions, top-selling
products, outstanding tasks, and any important operational
alerts supported by the data.
Keep the layout easy to scan in under one minute.
Use plain-language labels and show the date and time
of the latest available data.Prompt 5: Monthly Business Review
Build a monthly business review dashboard.
Compare this month with the previous month and, where
reliable historical data exists, the same month last year.
Include revenue, costs, profitability, customer metrics,
and operational performance where available.
Explain changes using observed data, not assumptions.
Highlight missing context that could affect interpretation.Prompt 6: Department Performance Dashboard
Create a department performance dashboard for
[DEPARTMENT].
Identify the department's main objectives and map each
objective to an available measurable indicator.
Group metrics by business function, show progress over
time, and flag indicators that need attention.
Avoid ranking employees using incomplete or misleading
data. Make the dashboard useful for improvement rather
than blame.Prompt 7: Business Health Check
Analyze the available business data and build a
business-health dashboard.
Group indicators into financial performance, customers,
operations, and growth.
For each indicator, show the value, measurement period,
definition, and relevant historical comparison.
Identify possible warning signs but explain the evidence
and limitations behind each one. Do not present the
dashboard as a guarantee of future business performance.Category B: Sales and Revenue Analytics
Prompt 8: Sales Performance Dashboard
Create a sales performance dashboard from the available
sales records.
Include total revenue, order volume, average order value,
sales by product, sales by region, and sales by period
where those fields exist.
Show trends and comparisons with consistent date ranges.
Separate gross sales from net revenue if both are available.
Identify the strongest and weakest observed categories
and explain what additional information would be needed
to understand why they performed differently.Prompt 9: Sales Pipeline Dashboard
Create a sales pipeline dashboard using the connected
CRM data or supplied opportunity dataset.
Show opportunities by stage, total pipeline value,
stage conversion, deal age, and expected close dates
where available.
Clearly distinguish booked revenue from potential revenue.
Do not count an opportunity as closed unless the source
records it as closed.
Highlight stale opportunities and missing fields.Prompt 10: Revenue Forecast Visualization
Build a revenue-trend dashboard using historical data.
Show historical revenue and, if the available tools
support forecasting, a clearly labeled forecast with
its assumptions and uncertainty.
Keep actuals and projections visually distinct.
Explain the forecast method and identify major limitations.
Do not present projections as guaranteed results.Prompt 11: Product Revenue Comparison
Create a dashboard comparing revenue and order volume
across products or product categories.
Show the contribution of each category to the total,
identify changes over time, and include profit margin
only if reliable cost data is available.
Make the ranking easy to read and explain how returns,
discounts, or missing product records affect the analysis.Prompt 12: Regional Sales Map or Comparison
Analyze sales performance by region using the available
geographic fields.
If reliable geographic data and mapping support exist,
create a map. Otherwise, use a ranked chart or table.
Show sales, order volume, and growth where available.
Identify regions with meaningful changes and explain
which conclusions require more investigation.Prompt 13: Customer Retention Dashboard
Build a customer-retention dashboard from the available
customer and transaction records.
Define the retention period and cohort method before
calculating retention.
Show repeat-purchase behavior and cohort changes where
the source supports them.
Explain missing customer identifiers, incomplete history,
and other limitations that may affect the results.Category C: Marketing and SEO Dashboards
Prompt 14: Digital Marketing Overview
Create a marketing performance dashboard for
[BUSINESS OR CAMPAIGN].
Include spend, impressions, clicks, conversions, and
cost per result where the data is available.
Compare campaigns using consistent attribution windows
and definitions.
Separate observed metrics from inferred explanations.
Highlight which campaigns warrant further investigation
rather than automatically declaring a winner.Prompt 15: SEO Performance Dashboard
Build an SEO dashboard using the supplied search
performance data or connected analytics source.
Include clicks, impressions, click-through rate, average
position, landing-page performance, and changes over time
where available.
Group results by page, query, and device if supported.
Flag pages with meaningful declines or opportunities.
Do not assume average position alone measures business
success. Suggest follow-up analysis for each finding.Prompt 16: Content Performance Dashboard
Create a content performance dashboard for a website
or blog.
Show traffic, engagement, conversions, and publishing
frequency where those metrics exist.
Compare content by topic, format, and publication date.
Account for differences in how long each page has been live.
Identify useful patterns and recommend which articles
deserve updating, internal links, or further analysis.Prompt 17: Social Media Analytics
Build a social media performance dashboard.
Show reach, impressions, engagement, follower growth,
video views, and link clicks when supported by the source.
Compare platforms separately before combining results.
Define engagement rate and disclose the calculation.
Identify top-performing posts and suggest hypotheses
for future experiments without claiming that correlation
proves what caused a result.Prompt 18: Email Campaign Dashboard
Create an email marketing dashboard with delivery,
bounce rate, click rate, conversions, and unsubscribes
where the source provides them.
Show campaign-level comparisons and identify unusual
changes.
Clearly distinguish delivered messages from total sends.
Avoid using open rates as the sole measure of success,
because tracking methods can affect their reliability.Prompt 19: Paid Advertising Comparison
Create a dashboard comparing paid advertising campaigns.
Include spend, attributed conversions, cost per acquisition,
and return on ad spend when the required fields exist.
Use consistent attribution settings and time periods.
Separate reported platform metrics from independently
verified business outcomes.
Highlight incomplete tracking and avoid treating
attributed conversions as proof of causation.Prompt 20: Website Conversion Funnel
Visualize the website conversion funnel from visits
through key steps to completed conversions.
Use the actual event definitions and available counts.
Show both counts and conversion rates at each stage.
Identify the largest observed drop-off and recommend
specific questions to investigate.
Do not infer individual visitor behavior from aggregated
data or assume a drop-off has one specific cause.Category D: Finance and Budgeting
Prompt 21: Monthly Expense Dashboard
Create a monthly expense dashboard from the supplied
financial records.
Group expenses into categories, show monthly totals,
and compare actual spending with budget where available.
Clearly label currency, time period, and category rules.
Flag unusual values for review without automatically
assuming they are errors or fraud.
Summarize the largest cost categories and missing data.Prompt 22: Cash Flow Visualization
Build a cash-flow dashboard using the available records.
Show cash inflows, cash outflows, and net movement
over time. Distinguish cash flow from accounting profit.
If future projections are supported, label them separately
and document the assumptions.
Do not make financial decisions on the user's behalf.
Identify which figures need confirmation.Prompt 23: Budget Versus Actual
Create a budget-versus-actual dashboard for
[MONTH OR REPORTING PERIOD].
Compare planned and actual spending by category.
Show absolute and percentage differences where valid.
Highlight categories over budget and those with unused
budget. Verify that the budget and actuals cover the same
period and use compatible category definitions.Prompt 24: Profitability Dashboard
Create a profitability dashboard for a business,
product line, or service.
Show revenue, direct costs, gross profit, and operating
profit only where the data supports those calculations.
Document which costs are included in each measure.
Avoid comparing margins based on inconsistent accounting
definitions.
Explain the strongest observed contributors and the
limitations of the available cost data.Prompt 25: Financial Scenario Comparison
Build a scenario-comparison dashboard for a business
planning exercise.
Compare a baseline with clearly specified optimistic
and conservative scenarios.
Allow key assumptions to be varied where supported.
Label all scenario values as hypothetical, not actual
results or guaranteed forecasts.
Show which assumptions create the largest changes
in the output.Category E: E-Commerce and Customer Analytics
Prompt 26: Online Store Dashboard
Create an e-commerce dashboard using the available
store and order data.
Include orders, revenue, average order value, returns,
conversion rate, and product performance where supported.
Distinguish order value from collected revenue and explain
how canceled orders or refunds are handled.
Identify operational questions and opportunities for
further analysis.Prompt 27: Shopping Cart Analysis
Analyze the available shopping-cart funnel data.
Show product views, add-to-cart events, checkout starts,
and completed purchases where those events exist.
Calculate step-to-step conversion rates using consistent
definitions and time windows.
Highlight where the largest observed loss occurs and
suggest possible explanations to test, not assumptions
to accept as fact.Prompt 28: Customer Segmentation Dashboard
Create a customer segmentation dashboard from
the supplied customer data.
Use only relevant fields and document the segmentation
method. Compare group size, purchase frequency, and
revenue contribution where available.
Avoid sensitive or protected characteristics and do not
infer personal attributes that are absent from the data.
Explain the business purpose and limitations of each
segment.Prompt 29: Product Returns Dashboard
Build a product-returns dashboard.
Show return volume, return rate, product category,
return reason, and time trends where available.
Define the return-rate denominator and ensure it matches
the reporting period.
Highlight recurring patterns while distinguishing
customer-provided reasons from verified root causes.Prompt 30: Customer Support Dashboard
Create a customer-support dashboard using available
ticketing data.
Include ticket volume, backlog, response time, resolution
time, and customer satisfaction where measured.
Define each metric and show the period covered.
Break down trends by issue category or channel if useful.
Use aggregated data where possible and avoid exposing
private customer information.Category F: Operations and Project Management
Prompt 31: Project Progress Dashboard
Build a project dashboard for [PROJECT NAME].
Show milestones, task status, due dates, dependencies,
and completion progress using the supplied records.
Clearly distinguish completed work from work in progress.
Highlight overdue tasks and blocked dependencies.
Do not estimate completion percentages unless a defined
method and supporting data exist.Prompt 32: Team Workload Dashboard
Create a team workload dashboard using the available
project or task records.
Show task assignments, due dates, work status, and
estimated effort where those fields exist.
Highlight potential workload imbalances as signals
for review, not proof of individual performance.
Avoid unnecessary employee surveillance and keep
the dashboard focused on planning and coordination.Prompt 33: Inventory Dashboard
Build an inventory dashboard for [BUSINESS].
Show available stock, incoming stock, outgoing units,
and reorder thresholds where supported by the source.
Identify items below defined thresholds and highlight
stale or inconsistent inventory records.
Do not create purchase orders automatically. Present
recommended items for human review.Prompt 34: Delivery Performance Dashboard
Create a delivery performance dashboard using
the available shipment records.
Show delivery volume, on-time rate, delay duration,
and delivery status where the data supports them.
Define the expected delivery date and the calculation
of on-time performance.
Separate verified delays from missing tracking updates.
Summarize recurring operational patterns.Prompt 35: Workflow Bottleneck Dashboard
Analyze the supplied workflow data to identify possible
bottlenecks.
Show time spent at each stage, queue size, and completed
work where available.
Use consistent start and end definitions for cycle time.
Identify stages that merit investigation and explain
what evidence supports each finding.
Do not assume that the slowest stage is necessarily
the root cause.Category G: Data Quality and Advanced Analytics
Prompt 36: Data Quality Dashboard
Create a data-quality dashboard for the supplied dataset.
Measure missing values, duplicate records, invalid formats,
inconsistent categories, and outdated timestamps.
Show the total records checked and the rule used for
each quality measure.
Provide examples of affected fields without exposing
sensitive values. Recommend corrections but do not
overwrite the source data without approval.Prompt 37: KPI Definition Audit
Review the KPI definitions used in this dashboard.
For each metric, document the formula, unit, data source,
reporting period, exclusions, and intended interpretation.
Identify duplicate or conflicting definitions.
Do not silently change a business metric. Explain
the proposed correction and ask for approval when
definitions are ambiguous.Prompt 38: Anomaly Review Dashboard
Analyze the supplied time-series data for unusual values
or changes.
Use a clearly described anomaly-detection method where
available. Show the baseline and explain why each
observation was flagged.
Distinguish unusual observations from confirmed errors.
Recommend validation steps before anyone takes action.Prompt 39: Data Dictionary Generator
Create a data dictionary for the dataset used by
this dashboard.
For each field, provide its name, apparent meaning,
data type, unit, example format, and known limitations.
Mark definitions that cannot be confirmed from the
source. Do not guess the meaning of ambiguous columns.
Use the dictionary to improve chart labels and metric
definitions consistently.Prompt 40: Executive Insight Audit
Audit the insights written for this dashboard.
For each insight, identify the supporting metric,
the relevant time period, and the comparison used.
Flag claims that confuse correlation with causation,
ignore missing data, or overstate certainty.
Rewrite each weak insight as a factual observation
or a clearly labeled hypothesis.Category H: Claude Motion and Animated Explainers
The following prompts are designed for animation and visual storytelling. Adapt them to the features available in your account.
Prompt 41: Explain a Complex Idea in 30 Seconds
Create a concise animated explainer about [TOPIC].
AUDIENCE: [AUDIENCE]
DURATION: Approximately 30 seconds
MAIN MESSAGE: [ONE KEY IDEA]
STYLE: Clean, modern, educational
Structure the animation into a clear beginning, middle,
and ending. Introduce one concept at a time, use simple
visual metaphors, and keep labels short.
End with one memorable takeaway. Do not sacrifice
factual accuracy for dramatic visual effects.Prompt 42: Animate a Data Story
Turn the supplied data story into an animated explainer.
Begin by establishing the question the data answers.
Introduce the most important figures gradually, then
show the relevant comparison or trend.
Keep units, labels, and time periods visible.
Distinguish observed data from interpretation.
Finish with a concise summary of what the evidence
supports and what remains uncertain.Prompt 43: Animated Business Process
Create an animation explaining this business process:
[PROCESS DESCRIPTION].
Show each stage in the correct order and use consistent
visual symbols for inputs, decisions, actions, and outputs.
Highlight important handoffs and decision points.
Keep the sequence easy to follow for a new employee.
Do not invent process steps that are not in the supplied
description. Mark unclear steps for review.Prompt 44: Explain Artificial Intelligence Visually
Create an educational animation explaining how an
AI system processes a user request.
Show the input, relevant processing stages, and output
using a simplified conceptual diagram.
Clearly distinguish the illustration from a literal
representation of a model's internal computation.
Use accessible language, restrained motion, and a final
summary of the key concept.Prompt 45: Animate a Before-and-After Comparison
Create a before-and-after animation comparing
[BEFORE STATE] with [AFTER STATE].
Keep the camera framing, scale, and labels consistent
so viewers can compare the two states fairly.
Use motion to highlight the most meaningful differences.
Do not exaggerate small changes or hide important
differences through inconsistent scales.
End with a short factual comparison.Prompt 46: Animated Product Explanation
Create a polished animated explainer for [PRODUCT].
Show the problem it addresses, the relevant product
features, and a simple example of how it is used.
Use a clean visual style and concise labels.
Do not invent product capabilities, customer results,
certifications, or performance claims.
End with a clear summary of the verified value proposition.Prompt 47: Explain a Scientific Concept
Create an educational animation explaining [SCIENTIFIC
CONCEPT] to a beginner.
Use a sequence of simple visual models and introduce
technical terms only when needed.
Clearly label any simplifications or analogies.
Avoid presenting an illustrative model as a literal
photographic representation of the underlying process.
End with three concise learning points.Prompt 48: Animated Timeline
Turn the supplied events into an animated timeline.
Arrange the events in chronological order and display
dates, labels, and concise descriptions.
Use consistent spacing and readable text. Highlight
important milestones without suggesting that chronology
alone proves causation.
Do not invent dates or events. Flag missing or conflicting
information before producing the final timeline.Prompt 49: Animated Statistics Explainer
Create an animation explaining these statistics:
[DATA OR FINDINGS].
Start with the main question, then reveal the figures
in an order that supports understanding.
Show the denominator, units, and time period.
Use proportional visual encodings where possible.
Do not change chart scales in a misleading way or imply
statistical significance without supporting analysis.Prompt 50: Animate a Workflow Diagram
Transform this workflow into an animated diagram:
[WORKFLOW].
Show each step as it becomes active. Use arrows to
indicate direction and distinct visual styles for
actions, decisions, and outputs.
Pause briefly at important decision points.
Keep the diagram accurate to the supplied process
and make it understandable without narration.Prompt 51: Animated Educational Lesson
Create a short animated lesson about [LESSON TOPIC].
Break the lesson into three to five visual stages.
Introduce the concept, demonstrate an example, and
show a common mistake.
Use brief on-screen text and a consistent visual style.
Finish with a question that helps learners check
their understanding.Prompt 52: Animated Case Study
Create an animated case study based on the supplied
facts and data.
Present the context, challenge, actions taken, and
observed results in sequence.
Separate documented facts from interpretations.
Do not invent customer quotes, metrics, or outcomes.
End with the main lesson and one limitation of the case.Category I: Marketing and Social Content
Prompt 53: Animated Social Media Explainer
Create a short animated explainer about [TOPIC] for
a social media audience.
Start with a clear, accurate hook. Explain one useful
idea through three short visual stages.
Use large readable labels and a strong visual hierarchy.
Keep essential information inside the safe area for
the intended platform and aspect ratio.
Avoid misleading claims or exaggerated results.Prompt 54: Product Launch Animation
Create an animated product-launch visual for [PRODUCT].
Introduce the product, highlight up to three verified
features, and show the intended use case.
Use consistent branding, clear typography, and restrained
transitions. Do not invent product specifications or
promise outcomes that are not substantiated.
Finish with a simple call to action.Prompt 55: Brand Story Animation
Create a short brand-story animation for [BRAND].
Use the supplied brand history, values, and audience
information to build a beginning, middle, and ending.
Keep the story specific and credible. Do not fabricate
founder experiences, customer testimonials, or milestones.
Use the brand's existing colors and visual assets
where available.Prompt 56: Animated Infographic
Transform these verified facts into an animated
infographic.
Organize the information into a clear hierarchy:
main message, supporting statistics, and final takeaway.
Animate one visual element at a time. Keep numbers,
units, sources, and labels readable.
Use proportional charts where appropriate and avoid
decorative effects that distort the information.Prompt 57: Animated Campaign Results
Create an animated summary of this marketing campaign's
results using the supplied data.
Show the campaign objective, reporting period, key
metrics, and relevant comparisons.
Clearly distinguish actual results from targets.
Explain any attribution limitations and avoid claiming
that the campaign caused a change without evidence.
Finish with the main learning for the next campaign.Prompt 58: Animate a Customer Journey
Create an animation showing a customer journey through
the stages described in the supplied research.
Show the customer's goal, touchpoints, decisions,
and potential friction points.
Distinguish observed research findings from assumptions.
Avoid presenting a single journey as representative
of every customer.
End with the most useful opportunity for improvement.Category J: Presentations and Research
Prompt 59: Animate a Presentation Opening
Create an animated opening for a presentation about
[PRESENTATION TOPIC].
Establish the central question and show why it matters.
Use a small number of visual elements and a coherent
transition into the main subject.
Keep text brief and legible. Avoid revealing conclusions
that the presentation has not yet supported.Prompt 60: Animate a Research Summary
Turn this research summary into an animated explainer.
Organize it into the research question, method, main
findings, limitations, and implications.
Use the supplied source material only. Keep the
distinction between evidence and interpretation clear.
Do not convert uncertain findings into definitive claims.
Finish with the most important limitation.Prompt 61: Animated Roadmap
Create an animated roadmap for [PROJECT OR PRODUCT].
Show milestones, dependencies, and target dates from
the supplied plan.
Distinguish confirmed commitments from tentative dates.
Use consistent visual markers for completed, active,
and planned work.
Do not invent delivery dates or imply that a milestone
is complete unless the source confirms it.Prompt 62: Explain a Technical Architecture
Create an animated technical architecture explainer
for [SYSTEM].
Show the main components, data flow, external services,
and important boundaries described in the documentation.
Use consistent symbols and label each connection.
Do not invent security controls or integrations.
Provide a simplified overview first, followed by
a more detailed view for technical audiences.Prompt 63: Animate a Decision Tree
Transform the supplied decision process into an
animated decision tree.
Show each question, available branch, and resulting
action in the correct order.
Use clear yes/no or labeled branches and make every
valid path traceable to an outcome.
Flag ambiguous or missing branches rather than guessing
how the process should work.Prompt 64: Animated Comparison of Two Strategies
Create an animated comparison of [STRATEGY A] and
[STRATEGY B].
Use the same criteria and visual scale for both options.
Show costs, benefits, risks, and assumptions from
the supplied information.
Avoid implying that one option is better for every
situation. End with the conditions under which each
strategy may be more suitable.Category K: Advanced Dashboard and Motion Workflows
Prompt 65: Convert Dashboard Insights Into an Animation
Review the dashboard and identify its three most
important supported findings.
Create a storyboard that explains those findings
in a logical order.
For each scene, specify the key metric, visual,
label, transition, and takeaway.
Use the same definitions and time periods as the
dashboard. Do not introduce new numbers or alter
the meaning of the original data.Prompt 66: Create a Live-Data Executive Briefing
Using the connected data source, prepare a dashboard
and concise executive briefing for [BUSINESS GOAL].
Identify the reporting period and last successful
data refresh where available.
Show the most relevant metrics, meaningful changes,
and unresolved data-quality issues.
If live connectivity or refresh status cannot be
verified, state that clearly. Do not describe a static
snapshot as real-time data.Prompt 67: Design a Dashboard for Different Audiences
Create two versions of this dashboard using the same
underlying verified data.
Version A is for executives and emphasizes strategic
outcomes and major risks.
Version B is for operators and emphasizes detailed
performance indicators and actionable follow-up.
Keep metric definitions consistent across both versions.
Do not remove context that changes the interpretation
of a number.Prompt 68: Create an Animated Dashboard Walkthrough
Create a short animated walkthrough explaining how
to read this dashboard.
Begin with the main KPI area, then introduce the
important trends, comparisons, and filters.
Show how each major chart answers a business question.
Keep the sequence suitable for a first-time user.
Do not claim that filters or interactions exist unless
they are available in the actual dashboard.Prompt 69: Dashboard Quality Assurance
Audit this dashboard before it is shared.
Check metric formulas, units, date ranges, chart labels,
data freshness, missing values, and consistency between
the visuals and the written summary.
Identify misleading scales, unsupported comparisons,
and conclusions that exceed the available evidence.
Provide a prioritized issue list. Do not state that
an item has been tested successfully unless it was
actually verified.Prompt 70: Build a Complete Data Storytelling Package
Create a data storytelling package from the supplied
dataset or verified connected source.
Include:
1. A concise dashboard brief.
2. A list of the most relevant KPIs.
3. Recommended charts and their purposes.
4. Three to five evidence-based findings.
5. A storyboard for an animated explainer.
6. A concise executive summary.
7. A list of uncertainties and data limitations.
Use consistent metric definitions across all outputs.
Separate observed results, hypotheses, and recommendations.
Do not invent values or imply unsupported causation.5. How to Turn These Prompts Into Better Results
The most effective workflow is to separate analysis, design, and quality checks instead of requesting everything in one step.
<box border radius="xl" padding={4} gap={3}> <row align=start gap={3}> <box background="surface-secondary" radius="lg" size="40px" align="center" justify="center"> <icon name="database" size="xl" /> </box> <box flex="1" gap={1}> **Step 1: Validate the source**
Confirm the dataset, date range, fields, units, and definitions. Identify missing or stale information before drawing conclusions.
</box></row> <divider color="subtle" /> <row align=start gap={3}> <box background="surface-secondary" radius="lg" size="40px" align="center" justify="center"> <icon name="chart-no-axes-combined" size="xl" /> </box> <box flex="1" gap={1}> **Step 2: Design the dashboard**
Select KPIs and charts that answer real questions. Keep the most important information visible and avoid unnecessary visual clutter.
</box></row> <divider color="subtle" /> <row align=start gap={3}> <box background="surface-secondary" radius="lg" size="40px" align="center" justify="center"> <icon name="clapperboard" size="xl" /> </box> <box flex="1" gap={1}> **Step 3: Build the visual story**
Use Claude Motion or another suitable tool to explain the most important finding, process, or concept through a clear sequence.
</box></row> <divider color="subtle" /> <row align=start gap={3}> <box background="surface-secondary" radius="lg" size="40px" align="center" justify="center"> <icon name="clipboard-check" size="xl" /> </box> <box flex="1" gap={1}> **Step 4: Check and refine**
Verify the numbers, labels, transitions, and conclusions. Fix specific issues individually rather than redesigning the entire output each time.
</box></row> </box>
6. Common Mistakes to Avoid
Mistake 1: Asking for every metric at once
A dashboard filled with dozens of charts can be difficult to use.
Better approach: Identify the three to seven most important metrics first, then add supporting details when they serve a clear purpose.
Mistake 2: Using unclear metric definitions
Two reports may calculate conversion rate, profit, or customer retention differently.
Better approach: Define every important KPI, its formula, the reporting period, and any exclusions before comparing results.
Mistake 3: Confusing correlation with causation
A chart may show that two metrics changed together, but that does not establish that one caused the other.
Better approach: Ask for the observed pattern, alternative explanations, and further evidence needed to test the hypothesis.
Mistake 4: Making animations too complicated
Excessive motion, lengthy labels, and too many simultaneous elements can make an explainer harder to understand.
Better approach: Give each scene one primary message and use motion to direct attention rather than decorate every object.
Mistake 5: Assuming the data is live
A dashboard may display a connected source's latest available snapshot without updating continuously.
Better approach: Confirm the source, refresh behavior, and last successful update. Label static or cached data honestly.
Mistake 6: Sharing sensitive business data unnecessarily
Dashboards can contain customer information, employee records, financial data, or confidential business details.
Better approach: Use approved connections, limit access to what is necessary, and remove personal or confidential fields that are not required for the task.
Mistake 7: Trusting AI-generated conclusions without review
An attractive dashboard can still contain incorrect calculations or misleading interpretations.
Better approach: Verify key calculations against the original source and have a qualified person review consequential findings before acting on them.
7. Frequently Asked Questions
What is Claude Dashboards?
Claude Dashboards is an AI-assisted dashboard feature announced by Anthropic in October 2026. It is designed to turn connected business data into visual dashboards. Anthropic announced beta availability on paid plans, with integrations including selected data platforms and CRM systems.
What is Claude Motion?
Claude Motion is an AI-assisted animation feature designed to turn ideas into animated explainers. Anthropic announced it in beta for Team and Enterprise plans on October 8, 2026.
Are Claude Dashboards and Claude Motion available on the free plan?
Their availability differs. Anthropic announced Dashboards in beta on paid plans and Motion in beta for Team and Enterprise. Claude Docs, Slides, and Design were announced as available on every Claude plan, including Free. Check the current product documentation for updates.
Can I create a dashboard without coding?
AI-assisted dashboard tools can reduce the amount of manual work required, especially for defining metrics and choosing visualizations. The exact level of interaction and customization depends on the tool, the data source, and available features.
Can AI make live dashboards?
Some dashboards can use connected data sources, but a connection alone does not guarantee continuous updates. Verify refresh schedules, permissions, and the timestamp of the latest successful update.
Can I use these prompts with other AI tools?
Yes. These templates are based on general principles of data analysis, dashboard design, and visual storytelling. Adapt the instructions to the features of your chosen AI assistant or visualization software.
What makes a good business dashboard?
A good dashboard answers specific questions, uses accurate and clearly defined metrics, makes comparisons meaningful, and helps the audience decide what to investigate next. Readability and data integrity matter more than the number of charts.
How long should an animated explainer be?
The appropriate duration depends on the audience and message. A brief explainer can focus on one concept, while a technical walkthrough may need more time. Start with the minimum duration that communicates the idea clearly, then add scenes only when they improve understanding.
Can AI-generated dashboards replace data analysts?
AI can assist with data exploration, chart selection, and summary writing, but people still need to validate metrics, understand the business context, assess data quality, and make accountable decisions.
8. Final Thoughts
Claude Dashboards and Claude Motion reflect a wider shift toward AI tools that help people turn information into finished visual outputs. Instead of stopping at a written answer, users can increasingly work toward dashboards, reports, and animated explanations.
The most useful prompt is not necessarily the longest one. It is the one that clearly defines the question, the data, the audience, and the intended outcome.
Start with a small project: a sales dashboard, a website performance report, or a 30-second explanation of one important idea. Check the output carefully, refine the design, and expand only when each additional element serves a clear purpose.
Bookmark these prompts and reuse them whenever you need to turn business data or a complex idea into a clearer visual story.
Comments
Post a Comment