# Audience, decisions, and rollout for the state of AI-assisted data visualization

Status: audience and distribution strategy, 15 August 2026.

Evidence cut: 2026-08-15. Community routes and event dates should be checked
again immediately before any outreach. This document recommends a rollout; it
does not authorize publication, community posting, submissions, or direct
outreach.

Companions: [editorial architecture](/reports/editorial-architecture/),
[executive summary](/reports/executive-summary/),
[research field guide](/reports/research-review/), and
[practitioner and reader experience](/reports/practitioner-and-reader-experience/).

## Recommendation

Do not launch this as one large report for one imagined audience. Launch one
canonical evidence hub with several decision-shaped entry points.

The underlying research has at least six credible reader groups. They share an
interest in AI and visualization but arrive at different moments, use different
language, and need to make different decisions. The comprehensive report is the
evidence spine. The useful public units are shorter guides, scorecards, figures,
methods, and source tables that help one group decide something now.

The first four audiences should drive the package:

1. visualization and data practitioners deciding where AI belongs in a real
   workflow;
2. BI and analytics leaders deciding what to enable, buy, govern, or stop;
3. visualization, HCI, and AI researchers choosing studies, benchmarks, and
   claims; and
4. data journalists, graphics editors, and newsroom developers deciding what is
   safe to use and publish.

Product builders and educators are important secondary audiences. General
executives and broad AI readers should receive a concise brief, not set the
structure of the research.

The positioning should be literal:

> What AI chart and dashboard systems can do in 2026, where they fail, and how
> to evaluate them for real work.

Use **AI-assisted data visualization** as the umbrella. Use the audience's own
more specific terms in route titles and descriptions: **AI data visualization
tools**, **Power BI Copilot**, **Tableau Agent**, **conversational analytics**,
**agentic analytics**, **agentic visualization**, **LLM visualization
generation**, **coding agents for data analysis**, **semantic models**, and
**reader trust**. Do not force one vocabulary across every surface.

## What is observed, inferred, and still unknown

This strategy combines three evidence classes:

- **Observed:** the current report files and rendered artifacts; official
  descriptions of community access, editorial terms, conference programs,
  search-measurement and citation mechanics; and bounded public language
  samples. No site-specific query or route-use data entered this synthesis.
- **Inferred:** audience priority, decision moments, suitable artifacts, and the
  sequence in which those artifacts should travel through the observed routes.
- **Unknown until tested:** how many people will read, refer, cite, subscribe,
  invite, or change a decision because of this work.

The audience map is therefore a testable model, not an adoption claim. Community
membership counts do not establish interest in this report. A visible page does
not establish use. A citation does not establish a changed decision.

The source trail for the audience scan is preserved in a private evidence
ledger, while this public-facing strategy links to sources that can be checked
by a reader. No private captures or copyrighted source text should travel into
the public package.

## The actual product

The phrase “report rollout” can hide the wrong unit of work. A reader rarely has
the job “read a state-of-the-field report.” They have a question such as:

- Can this tool be trusted with our semantic model?
- Which parts of my workflow should I delegate, and which must remain mine?
- What evidence would show that an agent made the work better rather than merely
  faster?
- Which benchmark or study would close a real gap?
- What can a newsroom permit without weakening source, editorial, or reader
  accountability?
- What should a student still learn when a model can produce the first chart?

The public offering is therefore a family of **evidence-backed decision guides**
built from one maintained evidence base. Internally, **decision products** is a
clearer name for this family than “automated consulting.” “Automated consulting”
foregrounds the production mechanism and invites a comparison with consulting
labor. “Decision product” names the object and its use. For public language,
“evidence-backed decision guide” or “maintained decision guide” is more legible
and less grandiose.

## Priority audience map

Priority reflects fit with the current evidence, reachability through observed
routes, and likelihood of a concrete decision. It is not a market-size estimate.

| Priority | Audience | Trigger | Job to be done | Decisions this package can improve | Best first asset | Plausible routes |
| --- | --- | --- | --- | --- | --- | --- |
| 1 | Visualization and data practitioners | A new tool or agent is offered; a deadline or unfamiliar stack makes assistance attractive; generated output looks plausible but is hard to finish | Use AI to reduce work without losing analytical intent, precise control, or accountability | Which tasks to delegate; which work surface to use; what to inspect; when to stop or revert | Workflow evaluator plus practitioner guide | DVS, Nightingale, visualization newsletters and podcasts, Tableau and Power BI practitioner groups |
| 1 | BI and analytics leaders | A Copilot or agent license, pilot, governance review, or high-visibility error | Decide whether and how to adopt AI over governed organizational data | Enable, pilot, procure, restrict, or retire; semantic-model readiness; review and incident ownership | BI pilot and procurement scorecard | Tableau AI user group and Slack, Microsoft Fabric or Power BI groups, dbt community, analytics leadership events |
| 1 | Visualization, HCI, and AI researchers | Literature review, study design, benchmark selection, grant or workshop planning | Locate what is measured, what is merely demonstrated, and which evidence would change the synthesis | Reuse a benchmark; design a study; select a gap; avoid an invalid cross-benchmark claim | Benchmark crosswalk plus research-gap ledger | IEEE VIS, VISxGenAI, BELIV, AccessViz, EduVis, labs, reading groups, citation repositories |
| 1 | Data journalists, graphics editors, and newsroom developers | A newsroom policy review, an AI-assisted analysis, a graphics deadline, or a proposal to publish generated work | Use assistance while preserving source custody, reproducibility, editorial authority, and reader trust | Permit or prohibit a use; set disclosure and review; validate an analysis; choose a reader test | Newsroom protocol and one worked case | NICAR/IRE, OpenNews/Source, data-journalism communities, graphics teams, newsroom training |
| 2 | Product, engineering, and tool teams | A roadmap decision, evaluation failure, customer demand, or a plan to add an agent or skill | Choose durable mechanisms and tests rather than copying demo behavior | Context architecture; agent versus deterministic component; eval suite; recovery path; instrumentation | System anatomy plus evaluation and ablation guide | GitHub projects, Observable, engineering blogs, developer events, targeted product-team briefings |
| 2 | Educators, data-literacy, and accessibility specialists | Curriculum redesign, assignment policy, an accessibility review, or evidence of assisted performance | Preserve learning, transfer, critique, and access while using assistance deliberately | Allowed assistance; skills to teach; unassisted transfer test; delivered-reader acceptance | Learning and accessibility protocol | EduVis, AccessViz, DVS education groups, instructors, accessibility communities |
| 3 | Executives, editors, and broad AI readers | Board discussion, investment planning, or a need to interpret a striking claim | Understand what is possible, what remains risky, and where investment is warranted | Sponsor, pilot, require evidence, or decline | Five-page executive brief and two figures | Trusted intermediaries, invited briefings, newsletters, podcasts, LinkedIn |

### Audiences are not amplifiers

Editors, community hosts, newsletter writers, podcast hosts, conference
organizers, instructors, and vendors may carry the work to readers. They are not
automatically the people whose decision the work should serve. Each outreach
pitch should distinguish:

- **reader:** who uses the material;
- **decision:** what they can do differently;
- **carrier:** who already has permission to reach them; and
- **proof object:** the figure, result, protocol, or dataset that makes carrying
  it worthwhile.

This prevents “distribution” from becoming a list of places to paste a link.

## Audience dossiers

### 1. Visualization and data practitioners

**Who this includes.** Independent visualization designers, data analysts,
analytics engineers who also communicate results, BI authors, newsroom graphics
practitioners, and developers who build custom visual interfaces. They vary in
code fluency, but all own some part of the path from question to delivered
artifact.

**Decision moments.** The blank page; a request outside the creator's normal
stack; a recurring transformation; a generated chart that is almost right; a
repair that breaks something else; a handoff or maintenance obligation.

**Jobs.** Get to a useful first representation, understand unfamiliar code or
data, compare alternatives, make precise corrections, prove the numbers and
interactions, deliver in the real environment, and preserve a record another
person can maintain.

**Questions in their language.** “Can it make the chart I mean?” “Can I edit the
result?” “Where did that number come from?” “Does it work with live data?” “How
many prompts will this take?” “Which parts still need me?” “Will I spend the
saved time checking it?”

**What to give them.** A surface-by-job map; the possible/accomplished/experienced
threshold; a checklist for data meaning, transformation, interaction,
accessibility, and handoff; and worked examples where assistance both helped and
failed. Lead with the job, not model names.

**Where they gather.** The Data Visualization Society describes its community
as a place for practitioners and enthusiasts to connect and offers Slack,
events, and interest or local groups through membership. Its 2024 State of the
Industry survey was disseminated through email, Nightingale, Slack, LinkedIn,
X, and local meetups, showing a real multi-route field network rather than a
single feed. The survey had 980 starts and 763 completions; the existing
practitioner report uses the 825 respondents who answered its AI question and
keeps that denominator visible. [DVS membership](https://www.datavisualizationsociety.org/membership),
[DVS State of the Industry 2024](https://www.datavisualizationsociety.org/soti-report-2024).

**Access strategy.** Earn editorial treatment first. Nightingale accepts
original member submissions in a roughly 500–3,000 word range and describes
promotion through the DVS newsletter, Slack, and LinkedIn. Pitch a
self-contained finding or practical protocol, not a summary of everything.
Respect its exclusivity terms and do not duplicate the submitted essay during
the stated window. [Nightingale submission guidance](https://nightingaledvs.com/article-submission/).

### 2. BI and analytics leaders

**Who this includes.** Heads of analytics, BI platform owners, analytics
engineering leaders, data governance leads, report developers, and technically
engaged business sponsors. Authors, platform owners, and budget owners are not
the same persona; the asset should make their distinct responsibilities visible.

**Decision moments.** A vendor adds AI to an existing license; leadership asks
for a conversational interface; a pilot reaches production data; an assistant
returns one wrong executive number; or an agent appears capable of rebuilding a
dashboard end to end.

**Jobs.** Separate demo capability from acceptable organizational behavior;
determine whether semantic models and metadata are ready; choose pilot scope;
define refusal, review, logging, escalation, and recovery; and estimate total
human and machine cost.

**Questions in their language.** “Does it respect the semantic model?” “Can it
use certified metrics?” “How does it handle row-level security?” “Who owns the
wrong answer?” “Is this conversational analytics or report authoring?” “Do we
still need dashboards?” “How do we govern agents using MCP?”

**What to give them.** A two-page decision brief, a pilot scorecard, a semantic-
readiness checklist, an incident scenario, and a total-cost ledger. The report's
central distinction between possible output and accepted work is more useful to
this group than a tool ranking.

**Where they gather.** The official Tableau community exposes user groups,
forums, Tableau Public, and Slack; its Slack page names channels including
AI-specific discussion and visualization feedback. An official AI and Tableau
user group runs recurring virtual sessions around best practices and governance.
The dbt community offers Slack and local or virtual meetups for analytics
practitioners. These are separate communities with different norms, so a useful
BI-specific artifact should be discussed in one appropriate venue at a time,
not sprayed across all of them. [Tableau community Slack](https://www.tableau.com/community/slack),
[AI and Tableau user group](https://usergroups.tableau.com/ai-tableau-user-group/),
[dbt community](https://www.getdbt.com/community).

**Access strategy.** Recruit pilot reviewers from author, platform-owner, and
governance roles before public launch. After revision, offer a concrete session:
“How to tell whether an AI dashboard pilot is ready for governed work.” Use one
worked scenario and let the scorecard be the handout.

### 3. Visualization, HCI, and AI researchers

**Who this includes.** Visualization and visual-analytics researchers, HCI
researchers, NLP and agent researchers working on visualization, benchmark and
evaluation authors, and graduate students entering the literature.

**Decision moments.** Scoping a literature review; positioning a paper; choosing
a benchmark; deciding whether a product demonstration supports a research
claim; or selecting the next study.

**Jobs.** Find the primary literature, compare unlike evaluation regimes
without flattening them, identify contradictions and nulls, reuse taxonomies,
and formulate a study whose outcome would change what the field believes.

**Questions in their language.** “What is the task definition?” “What is the
baseline?” “Is this text-to-vis, chart-to-code, visual analytics, or agentic
visualization?” “What does the benchmark actually measure?” “Was there a human
study?” “Does author success transfer to reader outcome?” “What is the
ecological validity?”

**What to give them.** Stable claim IDs or section anchors, a benchmark
crosswalk, machine-readable study cards, a negative-findings table, an explicit
gap ledger, methods, and a frozen citable release. Researchers should be able to
reuse a table or dispute a claim without reverse-engineering a designed page.

**Where they gather.** The official IEEE VIS 2026 workshop program includes
VISxGenAI (“GenAI, Agents, and Future of VIS”), BELIV, AccessViz, EduVis,
VISxAI, and related venues. That program is direct evidence that the topic
crosses generation, evaluation, accessibility, education, and visual analytics.
It does not prove that every attendee wants this report. The 2026 submission
deadlines have passed; the responsible current route is discussion with
organizers and attendees where invited, followed by a 2027 submission plan.
[IEEE VIS 2026 workshops](https://ieeevis.org/year/2026/info/program/workshops/).

**Access strategy.** Release a frozen research edition with citation metadata.
Deposit an approved snapshot in a repository that can assign a persistent DOI;
Zenodo describes a DOI as a persistent identifier that supports citation and
discovery. Add a root CITATION.cff if the public repository is meant to be
cited; GitHub then exposes a “Cite this repository” surface and can point to the
preferred report citation. These are publication choices and require owner
approval. [Zenodo DOI guidance](https://help.zenodo.org/docs/deposit/describe-records/reserve-doi/),
[GitHub citation files](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-citation-files).

### 4. Data journalists, graphics editors, and newsroom developers

**Who this includes.** Reporters who analyze data, graphics and visual editors,
news application developers, data editors, investigative teams, and the people
who set newsroom policy or training.

**Decision moments.** An analysis deadline; a coding agent used on source data;
a generated graphic proposed for publication; a new newsroom policy; or a need
to explain how a result was produced.

**Jobs.** Accelerate exploration or implementation without surrendering source
custody, reproducibility, editorial judgment, disclosure, accessibility, or the
reader test. Know which evidence belongs in the published explanation.

**Questions in their language.** “Can we reproduce it?” “Can an editor inspect
the transformation?” “What did the agent invent?” “What needs disclosure?” “Is
the source material allowed to leave our environment?” “Will a reader understand
the claim on a phone?”

**What to give them.** A newsroom use protocol, a provenance checklist, a short
benchmarking guide, and a worked example that begins with source custody and
ends with the delivered reader surface. Keep product promotion out of it.

**Where they gather.** NICAR 2026 included sessions framed as “Using coding
agents for data analysis,” “Build your own AI benchmark,” and practical AI in
the newsroom. Those titles are useful language evidence: the audience is
looking for bounded methods and tests, not only “AI visualization.” NICAR 2026
has passed; the next formal opportunity should be checked through IRE rather
than implied to be open. OpenNews/Source explicitly connects developers,
designers, and data analysts working in journalism through code. [NICAR 2026](https://www.ire.org/training/conferences/nicar-2026/),
[OpenNews/Source community](https://source.opennews.org/people/).

**Access strategy.** Seek two newsroom reviews before packaging the protocol.
Then propose a training or conference session whose promise is operational:
“A reproducible acceptance test for AI-assisted data analysis and graphics.”
The complete report is follow-through evidence, not the session abstract.

### 5. Product, engineering, and tool teams

**Decision moments.** Adding an agent to a product, choosing an intermediate
representation, deciding between a specialist model and a general agent,
interpreting a benchmark win, or responding to a failure that the current eval
did not catch.

**Jobs.** Choose where model reasoning adds value; bind it to authoritative
context; expose inspectable state; create recovery paths; and test the complete
delivered artifact rather than a screenshot or successful execution alone.

**Language.** “Agentic workflow,” “MCP,” “tool calling,” “semantic layer,”
“structured representation,” “critic,” “browser evaluation,” “repair loop,”
“ablation,” “human-in-the-loop,” and “end-to-end dashboard.”

**Assets and route.** Give this audience the system anatomy, technique matrix,
evaluation ladder, and reproducible ablation protocol. A repository-ready
methods page and compact diagrams can travel through GitHub, Observable, and
engineering blogs; only original results should be submitted as “news.”

### 6. Educators, literacy, and accessibility specialists

**Decision moments.** Revising a curriculum, deciding what assistance is
permitted, assessing whether students learned or merely completed a task, or
reviewing a generated interface for disabled readers.

**Jobs.** Separate assisted performance from durable learning; preserve critique
and data/domain reasoning; evaluate transfer without the tool; begin access with
co-creation rather than automated remediation; let users inspect, challenge, or
take an alternative path around generated descriptions; and test the delivered
interaction with representative readers and assistive technology.

**Language.** “Visualization literacy,” “learning outcome,” “unassisted
transfer,” “retention,” “cognitive offloading,” “accessibility from the start,”
“co-creation,” “verification,” “user agency,” “alternative pathways,” “screen
reader,” “low vision,” “mobile,” and “reader comprehension.”

**Assets and route.** Give this audience the human-skills model, a classroom or
training protocol, and an accessibility acceptance sheet that covers
participation, multimodality, disclosure, verification, agency, maintenance,
and sustained use. VIS workshops such as EduVis and AccessViz provide obvious
intellectual homes; DVS education and accessibility groups may provide
practice-facing routes. The AccessViz 2025 outcome report treats adoption as a
socio-technical process and AI-mediated access as a trust and power question,
not merely an alt-text feature. Its participant denominator is not stated, so
it supplies design requirements rather than prevalence evidence.
[AccessViz 2025 outcome report](https://accessviz.github.io/docs/report_2025.pdf).

## Jobs and decisions: the product matrix

The same chapter can support several readers, but the decision artifact should
be explicit about who holds authority and what counts as an answer.

| Decision product | Primary user | Trigger | Decision supported | Required inputs | Output | Acceptance evidence |
| --- | --- | --- | --- | --- | --- | --- |
| AI visualization workflow evaluator | Practitioner | Starting or repairing a piece of work | Delegate, assist, or keep manual for each stage | Purpose, data, stakes, delivery surface, edit needs | Stage-by-stage workflow and review plan | User can choose a path and name the retained human responsibilities |
| BI pilot and procurement scorecard | BI platform and governance leads | New license, pilot, renewal, or incident | Pilot, buy, constrain, or stop | Semantic model, permissions, expected questions, incident path, cost | Readiness score with blocking conditions and pilot design | Named owner accepts scope; test includes wrong-number and recovery scenarios |
| Benchmark and research-gap crosswalk | Researcher | Study or evaluation design | Reuse, extend, or reject an evaluation | Task, data, model, scaffold, renderer, judge, human sample, outcome | Comparable study cards and unanswered question | Reader can trace every comparison and state what result would change the synthesis |
| Newsroom use and publication protocol | Editor or newsroom developer | AI-assisted analysis or visualization proposed | Permit, revise, disclose, or prohibit | Source custody, transformations, generated code, editorial claim, delivery surface | Reproducibility and publication checklist | A second person reproduces the result; editor and representative reader checks pass |
| Agent or product evaluation protocol | Product or engineering team | Feature, skill, model, or architecture decision | Ship, change mechanism, or continue testing | Current-model baseline, tool/harness, task set, cost, failures, user context | Equal-budget test and defect ledger | Results survive deterministic and rendered checks; scope and regressions are visible |
| Learning and access protocol | Educator or accessibility lead | Curriculum or delivered-interface review | Permit assistance, revise teaching, or reject delivery | Learner profile, learning goal, assistive context, unassisted task | Assisted and unassisted outcome record | Retention/transfer or representative accessibility evidence, not completion alone |
| Executive evidence brief | Sponsor or commissioner | Investment or policy decision | Fund, pilot, require controls, or decline | Decision, stakes, current workflow, acceptable evidence | Five-page brief with unresolved risks | Sponsor can state the next gated decision without overclaiming the research |

### A reusable decision-product specification

Every derived asset should carry these fields:

1. **For whom:** role, environment, existing practice, and authority.
2. **At what moment:** the observable trigger that makes the material timely.
3. **Decision:** the actual fork, including a legitimate “do not use AI” branch.
4. **Inputs:** what local context the reader must supply.
5. **Evidence:** which report claims and limitations support the guidance.
6. **Output:** the record the reader leaves with, not merely information read.
7. **Acceptance:** how to know the decision path worked.
8. **Reopen condition:** what product, model, benchmark, or field evidence would
   require revisiting it.

This is the useful inheritance from the adjacent automated-consulting work: one
maintained corpus can produce several moment-shaped artifacts, but each artifact
must still have a named human user, decision, and acceptance test.

## The language map

### Use one canonical term and several audience routes

**Canonical umbrella:** AI-assisted data visualization.

It accurately covers human-led work that uses AI without claiming autonomy. It
also keeps research, practice, products, and reader outcomes in one field.

**Public subtitle:** What AI chart and dashboard systems can do in 2026, where
they fail, and how to evaluate them for real work.

“State of” signals comprehensiveness but not the reader's job. The subtitle and
route titles should answer that deficiency.

| Context | Words readers encounter or use | How to use them |
| --- | --- | --- |
| Broad tool discovery | AI data visualization; AI visualization tools; AI chart generator; AI dashboard generator; ChatGPT data visualization; best AI for data analysis | Use in plain-language route copy and FAQs. Do not turn the work into a “best tools” ranking the evidence cannot support. |
| Enterprise BI | Power BI Copilot; Tableau Agent; conversational analytics; generative BI; agentic analytics; semantic model; certified metrics; governance | Use in the BI route, scorecard, worked scenarios, and metadata. Keep vendor feature terms distinct from independent evidence. |
| Practitioner workflow | first draft; live data; precise edits; accurate numbers; show its work; prompts; DAX or SQL; dashboard; handoff; maintenance | Use in headings and examples. These describe lived friction more clearly than “capability frontier.” |
| Agent and engineering | MCP; tool calling; agent skills; end-to-end dashboard; browser validation; critic; repair loop; observability | Use in the builder route. Define acronyms and keep architecture terms out of the executive entry. |
| Research | AI-assisted visualization; agentic visualization; LLM-based visualization generation; text-to-vis; chart-to-code; visual analytics; mixed-initiative; human-AI collaboration; benchmark; ecological validity | Use in abstracts, methods, literature pages, and citation metadata. Reserve “agentic visualization” for systems with meaningful planning or action, not all AI help. |
| Journalism | coding agents for data analysis; practical AI in the newsroom; build your own AI benchmark; reproducible workflow; disclosure; reader trust | Use in the newsroom route and session pitch. “AI data visualization” alone is too detached from editorial work. |
| Education and access | visualization literacy; learning outcome; transfer; retention; cognitive offloading; accessibility; screen reader; low vision; mobile comprehension | Use in the human-skills route and in outcome labels, not a generic ethics appendix. |
| Anxiety and professional identity | Does this replace dashboards? Are we cooked? What am I charging for? Which numbers should I distrust? | Address the underlying concern directly. Do not use fear language as clickbait or treat bounded public posts as prevalence evidence. |

A dated search and community-language sweep found that exact “AI-assisted data
visualization” phrasing is less common in broad tool discovery than “AI data
visualization” or product-specific terms. “Agentic visualization” is already
useful in research and system-design contexts, while vendors and BI communities
use “conversational analytics” and “agentic analytics.” The correct response is
an intentional vocabulary bridge, not keyword substitution throughout the
report. [Agentic Visualization research paper](https://arxiv.org/abs/2505.19101),
[Tableau's agentic-analytics framing](https://www.tableau.com/agentic-analytics).

### Language evidence is not demand

The 15 August source pass added four useful boundaries to the language map:

- an independent visualization podcast asks how people actually use dashboards,
  where generative AI enters visualization work, whether it is effective, and
  what would make it safer; it is an interview and research preview, not a
  prevalence estimate ([PolicyViz with Melanie Tory](https://policyviz.com/podcast/dashboards-ai-data-visualization-melanie-tory/));
- a Spanish public-data exercise frames the work as converting natural-language
  questions into analysis through explicit dataset context, executable code,
  retries, corrections, and visible results; it is one implementation account,
  not evidence for a general Spanish-speaking market
  ([datos.gob.es implementation exercise](https://datos.gob.es/es/conocimiento/chateando-con-datos-publicos-una-aplicacion-practica-de-inteligencia-artificial));
- the AccessViz workshop makes co-creation, durable deployment, verification,
  alternative pathways, and user agency native language for AI-mediated
  accessibility; the report does not state a participant denominator; and
- official search documentation shows how the site's own query evidence could
  later be interpreted, while also documenting anonymized queries, row
  truncation, normalized Trends scores, filtering, and low-volume noise
  ([Search Console query dimensions](https://support.google.com/webmasters/answer/17011259?hl=en),
  [Google Trends methodology](https://support.google.com/trends/answer/4365533?hl=en)).

Use a four-rung evidence ladder:

| Rung | What is observed | What it earns | What it does not prove |
| --- | --- | --- | --- |
| 1. Source wording | A term or question in a captured community, editorial, implementation, or research source | A candidate vocabulary bridge or design requirement | That the term is prevalent or that this package is wanted |
| 2. Qualified discovery | A site-specific query or referral reaches the relevant route | Evidence that some readers find the package through that language | That they used it; anonymized and truncated queries remain missing |
| 3. Decision-path use | A reader chooses a route and completes its scorecard, protocol, or crosswalk | Evidence that the translation supported its intended job | That the resulting decision was good |
| 4. Decision consequence | A pilot, workflow, study, publication, curriculum, or access decision changes, is confirmed, or stops | Evidence of a bounded outcome | Population-wide impact |

This pass strengthens rung 1 and defines how to measure rung 2. Rungs 2–4 are
still unknown. Broad Google Trends interest sits outside the ladder: it is
context, not site demand. A direct Fabric community issue remained uncaptured
after the available capture routes were tried, so its search-result wording is
not used here. Power BI/Fabric language remains a live custody gap rather than
an inferred community verdict.

### Questions worth answering verbatim

These are stronger discovery doors than generic chapter labels:

- What can AI actually do in a data-visualization workflow in 2026?
- Can AI-generated charts and dashboards be trusted?
- How should a team evaluate Power BI Copilot, Tableau Agent, or conversational
  analytics?
- Which parts of data visualization should remain human-controlled?
- Does an AI visualization tool save time after checking and repair?
- What is agentic visualization, and how is it evaluated?
- Which benchmarks test chart generation, dashboards, interaction, or reader
  understanding?
- How should journalists disclose and validate AI-assisted analysis and graphics?
- What data-visualization skills still matter when AI can produce a first draft?
- How do accessibility and mobile testing change the verdict?

Each should have a direct two- or three-sentence answer, a visible evidence date,
and a route into the deeper report.

## Public artifact architecture

### One canonical hub, not sibling islands

The current rendered artifacts already have substantial strengths: crawlable
text, literal titles and descriptions, responsive viewport declarations, real
heading structure, section anchors, skip links, and visible evidence dates. The
research and practitioner sites are usable long-form reading surfaces.

The content map adds a local prototype of the routing layer: it shows which
draft owns which question, emphasizes four reader paths, compares coverage
against the comprehensive-report promise, and keeps planned bridges visually
separate from existing work. It does not yet supply durable public URLs,
canonical links, source navigation, or publication state.

The current draft package is still a set of sibling artifacts. Inspection on 14
August found no canonical-link declaration, Open Graph or social-card metadata,
author metadata, article structured data, alternate feed, or shared citation
surface in the AI-visualization artifact heads. The artifacts also do not yet
provide one audience router, public change log, or shared source and download
index. These are packaging gaps, not research gaps.

The public package should have this shape:

1. **Canonical hub.** One durable URL, one-sentence thesis, evidence date, scope,
   audience router, major findings, and links to every rendering.
2. **Audience routes.** “I make visualizations,” “I run analytics,” “I research
   visualization,” “I publish data journalism,” “I build AI systems,” and “I
   teach or evaluate access.” Each begins with decisions, not biography.
3. **Executive brief.** HTML first; a well-made PDF as a printable companion.
4. **Comprehensive report.** The connective argument and complete evidence
   accounting.
5. **Standalone essays.** Self-contained capability, workflow, reader-outcome,
   methods, and contested-claim entries with canonical links back to the hub.
6. **Decision tools.** The evaluator, BI scorecard, research crosswalk, newsroom
   protocol, and learning/access protocol.
7. **Reusable evidence.** Public-safe figures, tables, CSV or JSON exports,
   definitions, and claim/source index. Never publish the private source corpus.
8. **Methods and limits.** Search dates, inclusion rules, evidence ladder,
   known absences, conflicts, corrections, and disclosure of assisted methods.
9. **Citation and versions.** Preferred citation, authors or accountable owners,
   date published and modified, frozen release, and change log.

### The route page contract

Every audience route should fit this sequence above the fold:

- **Moment:** “You are deciding whether to…”
- **Short answer:** the strongest conclusion the evidence supports.
- **Decision tool:** a checklist, scorecard, or crosswalk.
- **Three findings:** each linked to its evidence and limitation.
- **Worked case:** a realistic path through the decision.
- **Go deeper:** the relevant report sections and methods.
- **Recheck:** evidence date and next update trigger.

Do not begin with an abstract history of AI or a decorative manifesto. The
reader should know within one screen whether this page can help with the current
decision.

### Search and AI visibility

Google's official 2026 guidance says the same foundations support ordinary
Search and generative AI features: useful original content, crawlable text,
clear structure, semantic HTML, indexability, and a good page experience. It
also says no special AI markup or tiny “AI-sized” chunks are required and that
Google does not use llms.txt. The rollout should therefore invest in the
substance and technical legibility of the canonical site, not an AEO ritual.
[Google's guide to optimization for generative AI](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide).

At publication:

- use stable, descriptive URLs rather than dates alone;
- add canonical links, sitemap, robots policy, RSS or Atom for material updates,
  and internal links between every rendering;
- supply unique title and description metadata, Open Graph and social cards,
  accountable author or organization, date published, and date modified;
- use Article or TechArticle structured data only when the visible page supports
  every field, and Dataset metadata for genuinely downloadable public datasets;
- keep substantive findings in HTML text rather than images, canvas, or a PDF;
- give each major table and figure a stable anchor, caption, alt text, source,
  and downloadable form;
- expose a preferred citation and a frozen release only after publication is
  approved; and
- verify indexation and actual referrals separately from merely shipping tags.

The website is the primary reading and linking surface. The PDF is for printing,
offline reading, and institutional circulation. It should not be the only
indexable version.

After publication, use Search Console's query dimension only as qualified
discovery evidence. Preserve impressions, clicks, page, country, device, date
window, and known omitted-query share where available; do not turn the displayed
row list into a complete denominator. Google Trends may help compare broad
relative interest in candidate terms, but its sampled, normalized 0–100 values
do not describe this site's readers. Neither source measures whether a reader
made a better decision.

## Rollout strategy

The sequence is **reader proof, canonical release, earned interpretation,
sustained evidence**. The public report should launch once, but the audience
routes should travel over several weeks.

### Phase 0 — prove decision usefulness before publication

Timing: approximately two weeks, or until the acceptance threshold is met.

Recruit 8–12 named reviewers, with at least two from each of the first four
audiences. Include different authority positions: practitioner and reviewer; BI
author and platform/governance owner; early-career and senior researcher;
reporter/developer and editor.

Give each reviewer one scenario, not the whole site and a satisfaction survey.
Observe whether they can:

1. identify their route without explanation;
2. find the evidence relevant to a named decision;
3. distinguish provider claims, benchmark results, human evidence, and unknowns;
4. produce the intended decision record;
5. name what remains unresolved; and
6. cite or send the right unit to a colleague.

Record time to decision, wrong turns, unanswered questions, language mismatches,
and whether the artifact changed, confirmed, or failed to affect the decision.

**Gate:** do not launch until at least one reader in each primary audience can
complete its decision path without live guidance and no unresolved defect would
misstate evidence, expose private source material, or obscure ownership.

### Phase 1 — publish the complete canonical package

Publish together:

- the hub and audience router;
- executive brief;
- comprehensive report;
- research and practitioner companions;
- at least three decision tools: practitioner evaluator, BI scorecard, and
  research crosswalk;
- methods, public-safe source index, preferred citation, and corrections policy;
- public change log and evidence/recheck date; and
- social cards and a compact set of reusable figures.

The launch note should make one claim, show one original figure, state who the
work is for, and link to the router. Avoid “we are thrilled to announce,” an
exhaustive feature list, or a thread that reproduces the report without giving a
reader a reason to use it.

**Gate:** human owner approves public claims, source rights, authorship,
disclosure, repository/site destination, DOI choice, and publication. HTTP,
mobile, accessibility, metadata, links, downloads, and analytics are separate
acceptance checks.

### Phase 2 — earned distribution by audience

Timing: three to four weeks after the canonical release. The exact dates depend
on editorial and community permission.

**Week 1: visualization practice.** Pitch one original essay or protocol to
Nightingale. Share in DVS only under the applicable community rules, framed as a
substantive question and resource. Offer the practitioner evaluator, not just
the report link. Give newsletters and podcasts one figure plus the evidence
behind it.

**Week 2: BI and analytics.** Run or propose a concrete scorecard session for an
AI and Tableau, Fabric/Power BI, or analytics-engineering group. Use product
names in the scenario but keep the evaluation vendor-neutral. Ask participants
to test the scorecard against one real pilot and report missing inputs.

**Week 3: research.** Circulate the research edition and benchmark crosswalk to
relevant labs and workshop participants. Offer it as a citable synthesis and
request corrections, conflicting evidence, and missing studies. The 2026 IEEE
VIS submission cycle is already past; plan a 2027 paper, workshop contribution,
or dataset release only if the resulting work is genuinely original.

**Week 4: journalism and education.** Offer the newsroom protocol to IRE/NICAR
and OpenNews-adjacent practitioners for review or training. Offer the learning
and access protocol separately to EduVis, AccessViz, and teaching communities.
Do not collapse editorial accountability and classroom learning into one ethics
essay.

Good secondary carriers include established visualization newsletters and
podcasts, but outreach should wait until there is a distinctive finding, figure,
or protocol they can discuss. Personal LinkedIn posts can make the work visible
to existing relationships; they are exhaust from the release, not the strategy.

### Phase 3 — keep the evidence alive without creating a content factory

- Publish a change note only when a material claim, source, tool contract,
  benchmark, or forecast status changes.
- Review high-volatility product and model statements monthly internally.
- Publish a quarterly evidence update or gap-ledger delta if it contains real
  changes.
- Preserve dated releases; never silently rewrite the historical snapshot.
- Invite corrections and missing primary sources through a bounded form.
- Turn repeated reader questions into better route pages or decision tools.
- Publish new experiments when they add evidence, not to fill a cadence.

## Channel map and participation rule

| Route | Audience reached | Native contribution | Evidence of fit | Participation rule | First ask |
| --- | --- | --- | --- | --- | --- |
| Nightingale | Visualization practitioners and adjacent readers | Original essay, case, or method | Publisher explicitly accepts member work and promotes through its network | Join/submit under editorial and exclusivity terms | Editorial fit for one standalone finding |
| DVS Slack, groups, and events | Practitioners, researchers, educators | Discussion, peer review, event, research recruitment | Official membership and research-recruitment surfaces | Follow channel rules; no repetitive link dropping | Review a workflow evaluator or answer one field question |
| Tableau AI user group and Slack | BI authors, admins, consultants, product users | Live demo, governance case, office-hours discussion | Official AI group and named Slack topics | Use product-specific scenario; disclose independence | Test the BI pilot scorecard |
| Microsoft Fabric or Power BI user groups | BI practitioners and platform owners | User-group session or technical discussion | Candidate route; the configured capture ladder could not preserve the current events page | Recapture and verify the current group and organizer route before use; do not cross-post indiscriminately | Critique a semantic-model and incident scenario |
| dbt community | Analytics engineers and data leaders | Governance or semantic-layer discussion | Official Slack and meetup network | Keep visualization claim tied to analytics-engineering work | Review the context/readiness section |
| IEEE VIS workshops and labs | Researchers, builders, students | Paper, position, dataset, poster, or reading-group discussion | 2026 program has several directly relevant workshops | Respect closed deadlines and archival standards | Correct the benchmark crosswalk and gap ledger |
| NICAR/IRE | Reporters, editors, newsroom developers | Training, session, reproducible protocol | 2026 program used practical agent and benchmark language | Verify next call; serve newsroom work rather than promote a product | Test the newsroom protocol |
| OpenNews/Source network | Journalism developers, designers, analysts | Case study, method, community discussion | Official community identity matches the intersection | Follow community norms and contribute operational detail | Review a reproducible worked case |
| GitHub and archival repository | Researchers and builders | Versioned report, data, methods, issue-based corrections | Native citation and release mechanics | Public-safe material only; clear license and custody boundary | Reuse or challenge a stable artifact |
| Trusted newsletters and podcasts | Mixed but already opted-in audiences | Interview, figure, case, or debate | Editorial relationship and thematic fit | Pitch one audience-specific story; do not send a generic blast | Discuss one defensible finding and its consequence |

The DVS research-recruitment program is a particularly appropriate route for
future original studies: it describes a monthly opt-in email to members and
states that member data is not shared with researchers. That is a research
recruitment mechanism, not a report-promotion loophole. Use it only when there
is a reviewed protocol and human-subjects obligations are clear.
[DVS research recruitment](https://www.datavisualizationsociety.org/research-recruitment/).

## Visibility and usefulness metrics

Use a funnel that preserves the difference between being available and changing
work:

| Level | Question | Useful measures | What it does not prove |
| --- | --- | --- | --- |
| Eligibility | Can the right reader or system retrieve it? | Successful crawl, indexed canonical pages, valid metadata, working feeds, HTTP and mobile checks | That anyone noticed or read it |
| Qualified circulation | Did intended readers reach the relevant route? | Route views by referral and audience, engaged reading, return visits, methods/source-index use | That the material changed a decision |
| Decision use | Did someone use the artifact for its intended job? | Scorecard completions, protocol runs, decision records, report sections cited in internal memos, reviewer scenarios completed | That the decision produced a good outcome |
| Reuse | Did the evidence travel with attribution? | Backlinks, academic citations, syllabus inclusion, figures or datasets reused, methods referenced | That readers interpreted it correctly |
| Relationship | Did qualified readers consent to a continuing connection? | Update subscriptions, interview opt-ins, correction submissions, community invitations | Revenue or durable adoption |
| Outcome | Did work change? | Pilot changed or stopped, evaluation run, policy revised, research gap adopted, error prevented, reader test added | Population-wide impact |

Report denominators and segment the measures by audience route. Do not combine
one highly engaged research cohort with general traffic and call the average
“engagement.” Do not optimize raw visits if the work is meant to change a small
number of consequential decisions.

### First-cycle targets

Targets should be learning thresholds, not synthetic growth forecasts:

- 8–12 prelaunch decision-path reviews across the four primary audiences;
- one corrected route or artifact from each audience's feedback;
- three or more completed uses of each launch decision tool;
- at least five attributable reuses across citations, internal protocols,
  syllabi, presentations, or linked technical work within the first quarter;
- at least two concrete outcome accounts, including “we did not adopt” or “we
  narrowed the pilot” as legitimate positive evidence; and
- a public ledger of substantive corrections and missing evidence.

If the package receives broad traffic but no recorded decision use, the problem
is not solved. If a small number of credible teams use it to improve or stop a
decision, that is meaningful early success.

## Ownership and gates

| Work | Canonical owner | Handoff or gate |
| --- | --- | --- |
| Private source custody, captures, grades, and question ledger | Private evidence owner | Never expose private captures merely because the synthesis is publishable |
| Cross-source synthesis, relevance, recommendations, and experiment agenda | Research synthesis owner | Every material public claim traces to an eligible source and states its limit |
| Public report design and route implementation | Public presentation owner, not the private source notebook | Preserve content parity, accessibility, stable URLs, and report authority |
| Publication, authorship, licensing, DOI, and outreach | Human owner | Explicit approval per surface; one approval does not authorize every channel |
| Community participation | Named human participant or approved representative | Respect community rules and answer questions; no unsupervised promotion |
| Audience and outcome evidence | Named audience/research owner | Keep observed use distinct from traffic, citations, and inferred value |

No automated posting, synthetic persona outreach, private-community scraping,
or posting quota belongs in this strategy. Automation can prepare views,
maintain evidence, check links, assemble release assets, and surface approved
opportunities. A human should own relationships, claims, and participation.

## Risks and countermeasures

| Risk | Likely symptom | Countermeasure |
| --- | --- | --- |
| The comprehensive report becomes the only product | Praise without use; high abandonment; vague sharing | Route by decision and ship tools that create a decision record |
| A tool-ranking frame overwhelms the evidence | Search traffic but rapid staleness and vendor comparison demands | Explain tool families and evaluation; refuse unsupported “best” rankings |
| The audience language fragments the field | Separate pages make inconsistent claims | One canonical vocabulary and evidence base; audience terms are routes, not rival truths |
| Community distribution reads as promotion | Deleted posts, low trust, no substantive replies | Earn access, contribute native value, ask one real question, and follow host rules |
| Private source custody leaks into public work | Copyright, confidentiality, or provenance failure | Publish only public-safe synthesis, short attributed quotations where allowed, and source metadata |
| A flashy figure loses its denominator | Attention followed by credibility damage | Put denominator, evidence class, date, and limitation in the figure itself |
| Updating destroys historical citability | Readers cannot reproduce what they cited | Frozen versions plus visible change log and current living view |
| Metrics collapse into page views | Distribution is mistaken for usefulness | Track eligibility, circulation, decision use, reuse, relationship, and outcome separately |
| “Automated consulting” becomes the headline | Readers debate replacement rather than use the work | Lead with the human decision product; describe assisted maintenance in methods |
| Cadence produces thin derivative content | Many posts, fewer reasons to care | Publish on evidence changes and recurring reader questions, not a quota |

## The first six artifacts to build

1. **Canonical hub and audience router.** This is the missing connective public
   surface and should precede broad distribution.
2. **Should AI help with this visualization job?** A practitioner evaluator
   using purpose, stakes, data authority, correction, delivery, and reader
   evidence.
3. **Is this BI agent ready for a real pilot?** A scorecard covering semantics,
   permissions, refusal, review, incidents, total cost, and maintenance.
4. **What does each benchmark establish?** A research crosswalk with task,
   model, scaffold, renderer, judge, sample, measured outcome, and limits.
5. **A newsroom acceptance protocol for AI-assisted analysis and graphics.** A
   reproducibility path from source custody through editorial and reader review.
6. **A public-safe evidence bundle.** Figures, tables, method, citation, version,
   and change log that make the work reusable without releasing the private
   corpus.

The executive brief, comprehensive report, and current long-form companions are
already substantive. These six pieces make the corpus navigable and actionable.

## Ninety-day sequence

| Window | Work | Exit evidence |
| --- | --- | --- |
| Days 1–14 | Build router prototype and three decision tools; recruit 8–12 scenario reviewers | Completed decision-path records across four primary audiences; blocking defects resolved or explicit |
| Days 15–30 | Complete canonical metadata, public-safe source/index exports, version and citation mechanics, accessibility and mobile acceptance | Human publication approval plus technical and content gates; frozen release candidate |
| Days 31–45 | Canonical launch and visualization-practitioner editorial route | One launched package; one earned editorial conversation or substantive DVS review; evaluator use recorded |
| Days 46–60 | BI-specific scorecard sessions and analytics-community reviews | At least three real or reconstructed pilot uses; missing inputs and governance defects logged |
| Days 61–75 | Research crosswalk circulation and corrections; archive approved release | Corrections or missing studies adjudicated; citable frozen version; 2027 research route chosen or declined |
| Days 76–90 | Newsroom and education/access reviews; publish first material change note | Protocol uses recorded; first outcome accounts; prioritized next evidence work rather than a content calendar |

## What would change this strategy

Revisit audience order if decision-path tests show another audience completing
more consequential jobs with less explanation. Revisit channel choices if
community policies, editorial terms, or event calendars change. Revisit the
artifact family if readers consistently use the full report and reject the
decision tools, or if the tools are used without consulting their evidence and
limits. Revisit the positioning if search and referral evidence shows a more
precise term consistently brings the intended readers without distorting scope.

Most importantly, replace this modeled audience map with observed use as soon
as the first cohort exists. The strategy has succeeded when the report becomes
an evidence spine that real people use to make named decisions—not when it has
been reformatted into the largest number of posts.

## Update log

- **2026-08-15 — Audience-language evidence ladder.** Added primary custody for
  an independent podcast, a Spanish public-data implementation, AccessViz
  community outcomes, and official search-measurement limits. Separated source
  wording, qualified discovery, decision-path use, and changed work; expanded
  the accessibility route around co-creation, verification, agency, and
  sustained use. Power BI/Fabric community wording remains a capture gap.
- **2026-08-14 — Initial public edition.** Defined audience routes, decision
  products, evidence boundaries, publication gates, and an outcome-oriented
  rollout sequence.