← All work

Partnership · Product Design · AI · UI/UX

AI-Powered Anomaly Detection for Workiva

An AI assist for financial analysts who hunt for anomalies in collaborative spreadsheets. Cuts down the manual scanning so review moves faster.

Duration
3 months
Team
Nandha, Ranga
Role
Product Designer, UX Researcher
Tools
Figma, Python, Tableau
Focus Area
Anomaly Detection
Long story short
  • 01 Research Interviewed 6 analysts and mapped the review journey. The problem wasn't finding anomalies, it was trusting them.
  • 02 Design Designed an AI panel that sits beside the spreadsheet, pins each anomaly, and ranks the likely reasons behind it.
  • 03 Outcome A projected 45% cut in review time, with 89% anomaly detection accuracy.
(01)   The question

Review couldn't keep up

Workiva users were spending 73% more time than necessary reviewing collaborative reports for data anomalies and formatting inconsistencies. Datasets kept growing, compliance deadlines kept tightening, and the review was still done by eye.

73%
Additional review time
30%
Increase in revision cycles
6
Analysts interviewed

How might we help analysts trust what an AI flags in their spreadsheet?

(02)   Speaking to users

Three problems, in their words

I interviewed 6 Business Analysts and MIS students using an 18-question guide, then ran a thematic analysis. Everyone relied on domain knowledge plus manual scanning. Three problems came up again and again.

Problem 01

A flag without a reason is just more work

"Ideally it would tell me what the problem could be as well. Maybe we can tell me that it's possibly because this variable seems to have too many missing values."
Business Analyst

Problem 02

"Something's wrong" isn't an answer

"It should actually tell you where exactly is the error instead of just telling that there is something wrong."
MIS graduate student

Problem 03

Two users with opposite needs

Newer analysts couldn't tell an anomaly from a normal spike and wanted guidance. Senior analysts wanted speed and control: "Show me the anomalies, let me decide what to do with them."

Journey map of a novice analyst moving from overwhelmed to confident across five review stages, with pain points and AI opportunities at each stage
Fig 1. Novice analyst journey. The lowest point is cleaning and analysis, where "Is this pattern normal or an anomaly?" goes unanswered.
(03)   Early concept

The pop-up we dropped

My first sketches put the AI in a floating pop-up over the spreadsheet, with its own projects panel. It looked clean on paper, but it covered the data the analyst was trying to check.

Interviewees kept describing the same habit: they looked at the numbers and the chart at the same time. So I moved the AI into a docked side panel. The spreadsheet, the chart and the explanation all stay visible together.

Hand-drawn wireframes moving from a floating AI pop-up to a docked side panel next to the spreadsheet
Fig 2. Sketches, left to right: floating AI pop-up, then the docked panel built for multitasking.
Decision
Docked panel over pop-up. An AI that hides the spreadsheet asks for blind trust. One that sits next to it lets the analyst check its work.
(04)   The flow

From raw sheet to report

Each problem became one step in the flow: detect the outlier, explain it, tune it if needed, and add it to the report.

User flow from opening Workiva and importing data, through graphing and AI outlier detection, to the anomaly insights panel, detection settings and adding to a report
Fig 3. User flow, from importing data to adding a finding to the report.
(05)   Final designs

Find it, understand it, tune it

Pinpointed, not just flagged

The AI marks the exact point on the chart and states it plainly: the date, the value, and the expected range it fell outside. Answers problem 02.

Workiva spreadsheet with the AI panel docked on the right, showing a marked revenue spike, a plain-language summary and ranked possible explanations
Fig 4. Summary: "Revenue was unexpectedly high on Friday, August 30, 2019," with the expected range underneath.

Reasons, ranked by strength

Each flag comes with possible explanations scored by strength. Opening one shows the evidence chart, which the analyst can add to their workspace next to the original. Answers problem 01.

An expanded explanation, 'Seller is Northwind Traders' at 71%, with its evidence chart added to the workspace beside the original revenue chart
Fig 5. Drilling into "Seller is Northwind Traders" (71%) and comparing it with the original chart.

Control for experts, defaults for everyone else

Newer analysts never need to leave the defaults. Senior analysts can open settings to change sensitivity, pick the parameters to explain by, and restyle how anomalies are marked. Answers problem 03.

Anomaly detection settings in the AI panel: sensitivity slider at 83%, explain-by parameters, anomaly shape, size and color
Fig 6. Detection settings: sensitivity, explain-by parameters, and marker style.
(06)   Impact

Impact & learnings

45%
Reduction in review time (projected)
89%
Anomaly detection accuracy
Learning 01

Explainable comes before accurate

An 89% accurate flag that nobody trusts saves no time. For enterprise analysts, the explanation is what turns a flag into a decision.

Learning 02

Where the AI sits changes how much people trust it

Moving from a pop-up to a docked panel was a layout change, but it was really about trust. Analysts believe what they can check against the data.

Learning 03

Design for both ends, then hide the difference

Novice and expert needs looked like they conflicted. Good defaults plus settings one tap away served both without two separate modes.