People are not having one AI visualization experience.
The same person can be delighted by a first draft, frustrated by the repair loop, afraid to put their name on the result, and still choose to use the tool tomorrow. Attitude and behavior do not move together.
01 · Before the work
Is this invitation, pressure, or a threat?
People arrive with organizational demands, prior skill, career hopes, and fears about what assistance may remove.
Analytics team lead · workplace mandate
“We need to use AI” arrived before a useful job.
Leadership wanted visible thought leadership. The custom chatbot was unreliable; for the immediate task, a pivot table was faster. The frustration was having to perform adoption.
Visualization coder · personal project
Fear of losing the rewarding part gave way to momentum.
Jisell Howe first worried that instant code would remove the journey from idea to customized chart. A concrete build changed the feeling: errors remained, but search and troubleshooting became less disruptive.
Master’s student · guided practical
Early anxiety became a sense of access and accomplishment.
AI produced a first bar chart, but an instructor supplied the visualization knowledge needed to improve it. The gain was reaching the work—not yet independent mastery.
02 · First candidate
The initial rush is real—and often comes from staying in motion.
Delight tends to attach to access, flow, and continuity across chores, not only to a chart appearing.
Independent creator · personal dashboard
Loose instructions worked because the materials were ready.
A two-day revision felt surprisingly fluid. Four short lines were enough once the current files, requested changes, and source URLs were present. The creator’s lesson was that organized context mattered more than prompt polish.
Technologist · visualization class project
The pleasure came from continuity across a whole project.
Sef Kloninger called the work “plain fun.” The agent moved with him from a 500 GB dataset through tests, exploration, a dashboard, debugging, and a presentation; he still inspected raw data and requested checks.
Experienced BI analyst · unfamiliar API
A week-sized unknown became a day-sized job.
The practitioner immediately added the caveat: prior proficiency made the compression possible. A novice in another account valued a smaller gain—producing cleaning and validation scripts that had been out of reach.
03 · Working loop
Assistance turns into interruption when precise repair begins.
The experience depends on whether explaining, waiting, inspecting, and retrying costs less than direct manipulation.
Power BI practitioners · report authoring
Greenfield structure was fast; local refinement was clumsy.
Stale filters, bookmark identifiers, whitespace churn, and slow edit-preview cycles accumulated. One experienced practitioner said describing a small change could take longer than making it.
Analytics educator and practitioner · stakeholder work
“Babysitting” meant protecting a professional reputation.
Christina Stathopoulos described useful brainstorming and exploration, then recalled a generated chart whose accompanying interpretation reversed the visible comparison. The feared failure was looking careless in front of a stakeholder.
Data journalist · published interactive
The build became hardest when it looked almost finished.
A recognizable site appeared in about an hour. Geography, evidence notes, rate limits, mobile behavior, architecture, and fact-checking then consumed repeated rounds of repair.
04 · Acceptance
Trust becomes personal when someone must accept the work.
The imagined stakeholder, patient, client, colleague, or excluded reader changes which errors matter and where refusal is rational.
Dashboard consultant · client reconstruction
A 25-minute reconstruction became an existential pricing question.
An agent recreated roughly a week’s visible dashboard work from a finished screenshot and source tables. The consultant’s question was what clients had really paid for: construction, diagnosis, or the judgment embedded in the reference.
17 biomedical-visualization practitioners · consequential work
Refusal was sometimes expertise, not resistance to change.
Participants welcomed boilerplate, inspiration, and translation while some rejected final AI imagery for anatomy, patient communication, or scientific work. Others protected rendering because it was also where control, flow, and creative joy lived.
Blind journalist · news reader and colleague
Access felt different when it became a shared habit.
Johny Cassidy describes exclusion from charts with missing or useless descriptions—and the relief of colleagues taking responsibility. Generated alt text is not accessible delivery without alternatives, feedback, and correction.
05 · After delivery
Creation stories are vivid. The artifact’s afterlife is mostly quiet.
Use, maintenance, correction, learning, and second-person handoff determine whether the saved effort became value.
BI practitioner · urgent dashboard request
Praise and distribution did not become use.
A manager praised an urgent dashboard and sent it to six colleagues. Three months later, the usage record showed one manager view. Creator pride, stakeholder approval, and reader use were three different outcomes.
BI developer · adjacent work
The durable gain sat around the chart.
AI documented SQL and calculations, reviewed junior work, and rehearsed stakeholder questions. Those tasks made the dashboard easier to explain and maintain without asking the model to own the final claim.
Freelance data journalist · analog practice
Some friction created attention rather than waste.
Emilia Ruzicka collected and drew personal data by hand. Slowness, imperfection, and direct contact with the data produced experimentation and care—the kind of learning a faster route can accidentally remove.
Listening past the original creator
Non-use is often quiet. Reliance is often provisional.
A second pass pursued spreadsheet-native work, people who do not make AI their default, recipients deciding whether an answer is defensible, blind and low-vision learners, and the second person asked to maintain the result.
Routine public-sector work · mixed-methods evaluation
People kept the assistant and routed experienced Excel work around it.
DWP staff allocated tasks according to expertise, time, trust, data sensitivity, and habit. Data-heavy Excel work, chart generation, and intricate formatting remained weak points. One person valued having the assistant but was often too busy to remember to use it.
Decision recipients · within-person comparison
The preferred interface changed with the acceptance criterion.
When speed mattered
Chat 15Dashboard 3Both 2
When confidence mattered
Chat 0Dashboard 18Both 2
Twenty-participant exploratory study ↗. The chatbot compressed retrieval; the dashboard retained overview and an inspectable chain to the data. Eighteen participants had computer-science backgrounds and were proxies for industrial decision makers.Spreadsheet-help community · public discussion
An instant private answer can also remove a public learning episode.
A supply-chain analyst noticed that AI had displaced visits to a peer forum. Replies described both useful help and invented functions, wrong references, damaged formulas, and refusal. Several people valued the incidental learning produced by solving someone else’s problem in public.
Program recipients and an executive-dashboard observer
“Go check the raw data” is not a recipient verification contract.
Program managers and funders wanted overview, drill-down, definitions, neutral language, and review support. In a separate sales-dashboard demonstration, an observer rejected the idea that an executive seeking a quick answer should independently validate regenerated charts against raw data.
Blind and low-vision chart learners · 12-participant study
A useful answer can still fail to supply the spatial model.
Eleven participants preferred tactile charts plus text and chat; one said the better mode depended on complexity; none preferred text and chat alone. Touch supplied spatial structure and chat supplied flexible clarification. Measured chart-understanding accuracy did not improve.
Second maintenance · public discussion
The refresh job lived on the creator’s laptop.
An AI-built dashboard failed while its creator was away. The inheriting maintainer replaced the creator-local scheduled job with a proper pipeline; replies surfaced missing metric semantics, hidden dependencies, documentation gaps, and service expectations nobody had owned.
What listening adds
Capability scores cannot tell us what the gain costs—or what people are trying to protect.
Delight is often momentum.Staying in motion across formerly blocking chores can matter more than a perfect first chart.
Frustration is often interruption.The comparison is prompt-and-repair time versus direct work, not AI versus a blank page.
Fear has distinct objects.Employment, reputation, learning, craft, access, scientific harm, and vendor dependence require different responses.
Trust has a face.People picture who will spot the mistake, bear its consequence, or be unable to inspect the claim.
Refusal can be expert practice.Keeping some work manual can preserve accountability, knowledge, control, or the purpose of doing it.
The afterlife is underreported, not empty.One direct handoff failure exposes hidden execution and ownership assumptions; routine use, cross-release maintenance, and retirement remain faint.