HR Briefing

HR Technology

Conversational Analytics Shifts Data-Quality Burden to Employees

Conversational AI analytics gives employees direct answers from business data, but shifts the burden of checking definitions, permissions and lineage onto teams that may never see them.

AI analytics raises the stakes for showing your work
AI analytics raises the stakes for showing your workigorovsyannykov / pixabay

Nathan Brooks

· 3 min read

Conversational AI analytics now lets employees ask business questions in plain language — and it hands them full responsibility for judging answers they may lack the expertise to check. The shift from established dashboards to chat-based tools touches people-process decisions across data teams, security teams and business units, because errors once caught while building a dashboard may now surface only after someone acts on an answer.

The stakes rise further when analysis feeds automated workflows. An incorrect calculation or an overlooked access restriction can influence a business process before any analyst reviews the result, according to the reporting underlying this analysis.

Why can two correct numbers disagree?

Teresa Tung, global advanced data lead at Accenture, said conversational tools must first interpret terms that carry different meanings across departments. "If it gets that interpretation wrong, everything that follows can be wrong too," she said.

Sales and finance illustrate the problem. Both can ask for last quarter's customer count and receive different answers without either number being miscalculated. Sales may count everyone who made a purchase; finance may count only accounts with active contracts, Tung explained. Unless the tool makes its interpretation clear, employees could mistake a disagreement over definitions for a discrepancy in business performance. A conventional dashboard lets data teams resolve those differences before publication. A conversational tool can leave that choice to the AI each time someone asks.

How do errors hide inside plausible results?

Megha Kumar, research vice president for analytics and AI at IDC, said errors in how datasets are combined can distort results without making them look obviously implausible. "A bad join can count orders twice and inflate revenue or drop records that don't match and leave out part of the business," she said.

Kumar also cautioned that a tool might use information collected for another purpose, or filter results using a sensitive attribute. Checking whether the final number seems reasonable would not necessarily reveal either problem.

Users unfamiliar with the underlying data are particularly poorly placed to catch such errors, explained Nick Maynard, vice president of research at Juniper Research. "Without full familiarity on the data sources, an answer that meets a user's preconceptions can be accepted at face value," he said.

Do permissions follow the question?

Conversational access can also expose inconsistencies between systems that previously served different audiences. An employee permitted to view purchasing trends should not gain access to individual customer records simply because a tool draws on both sources.

Sonal Ramrakhiani, CEO of LatentView Analytics, said organizations must preserve existing restrictions as they introduce conversational interfaces. "Companies need to make sure employees' access to sensitive information through a conversational tool is identical to the more well-established tools in the business," she said.

Tung noted conversational analytics does not inherently bypass controls. The risk increases when identity and permissions are enforced inconsistently across the systems supplying an answer. Data managers working with security teams therefore need to examine access throughout the analysis, including the sources consulted and the information returned.

What evidence should employers retain?

Before an analysis informs a consequential decision, users need to understand how their question was interpreted, which definitions applied and how current the data was. Tung said the evidence should also allow teams to reconstruct sources, transformations and lineage.

For automated actions, Kumar recommended rules governing which sources are acceptable, plus records connecting each action to the answer that triggered it. Investigators need the original question, the requester, the generated query, the model version, the permissions and the resulting output.

Those records support distinct responsibilities. Data and analytics teams must investigate the analysis itself, while business owners review the decisions affected by a mistake, Ramrakhiani said. Keeping only the final answer leaves both groups without enough evidence to establish what happened.

"That requires keeping a history of the analysis so the team can reproduce the result, even if the underlying data has since changed," she said.

What comes next?

As conversational analytics moves from experiment to everyday practice, employers that pair the tools with consistent permissions, shared definitions and reconstructable audit trails will be the ones able to trust — and correct — what their employees ask.

Source: techtarget.com

Share this article:

More from Nathan Brooks

Nathan Brooks

Show full bio

News editor covering people, launches and day-to-day practice in Recruiting and talent acquisition, learning and development at HR Briefing.

270 articles

© 2026 HR Briefing. All rights reserved.