PRODUCT DESIGN · CPG ANALYTICS · CONVERSATIONAL AI

AI Executive Assistant: designing for quick answer, not a dashboard user has to dig through. 🖌️

A data-heavy analytics dashboard was slowing C-suite down. Finding one KPI meant clicking through filters and charts just to answer a single business question. I designed a conversational AI assistant that let executives ask in plain language and get a trustworthy answer in seconds, for a leading CPG company.

MY CONTRIBUTION

Problem framing → competitor analysis → conversational flow design → trust framework → high-fidelity UI → prototyping → stakeholder alignment

ROLE
Product Designer
DURATION
1-month sprint
PLATFORM
Web · React
USERS
C-suite executives
01

Outcome: an assistant built to earn trust, one answer at a time.

L1 · L2
Question levels the assistant answered confidently at launch
100%
AI responses that cite a data source and timestamp
POC → Engagement
Proof of concept converted into a full build
✓ My ownership
  • Led the UX process through discovery to high-fidelity design
  • Ran competitive analysis of existing executive analytics tools
  • Designed conversation flows for L1 & L2 high-fidelity questions
  • Delivered inside the client's existing design system
🗂️ File📌 Ownership🕐 12:00 PM
✓ Deliverables
  • Competitor analysis of AI analytics assistants
  • Conversation flow maps and suggested-question logic
  • Error and permission-denied state library
  • Interactive prototype for stakeholder review
🗂️ File📌 Delivery🕐 12:00 PM
02

The problem was not missing insight. It was missing speed.

The dashboard held the answer to almost every question an executive might ask. Getting to it was the part that was broken.

⚠️ DANGER: Where is the answer?!
  • Data-heavy → a dense dashboard packed with charts, tables and filters
  • Hard to navigate → finding one KPI meant clicking through several menus and filter combinations
  • Search that did not help → the dashboard's built-in search rarely got an executive to the right answer
  • Time-poor users → C-suite executives could not spend minutes solving what should be a one-line answer
  • No shortcut → there was no faster path from having a question to having an answer
THE UX QUESTION
"If an executive lands on the dashboard just to answer one business question, how fast can we get them to that answer, without asking them to learn the dashboard first?"
What's the question Where's the answer Can I trust it Whats Next
✏️
03

Research told me what to build. Trust told me how.

Quick interviews with executives were enough to confirm the ask. The harder design problem sat underneath: how do you get someone to actually rely on an AI answer.

Quick executive interviews·Competitor analysis·Conversational pattern research·AI trust and adoption research

THE ASK WAS CLEAR

Interviews were short because executives already knew what they wanted. The open question was never scope, it was whether they would trust what came back.

NOBODY KNEW WHAT TO ASK

Several executives were not sure what even the assistant could answer, which meant an empty chat box was a barrier all on its own.

AI MEANS FAST, OR IT MEANS NOTHING

If the assistant hesitated or got something wrong even once, the expectation was that people would simply go back to the dashboard for good.

Evidence
Insight
Design response
Executives were confident about what they needed, but unsure what the assistant could actually answer
An empty chat box is a barrier, even for a confident user
Surface six suggested questions the moment the chat opens, pulled from real, frequently asked questions
Adoption research and competitor analysis both pointed to mistrust as the top reason executives abandon AI tools
One unverifiable answer can be enough to send someone back to the old dashboard for good
Cite the data source and timestamp under every single response, so trust does not depend on faith
Only L1 and L2 questions were ready at launch, but users could still type anything
A blank or missing answer reads as the assistant failing, even when it's just a scope decision
Respond honestly to out-of-scope questions and redirect to something the assistant can help with today
Research note: this project did not include an extended discovery phase. The client already knew what they wanted, so quick interviews confirmed the ask, and a broader competitor analysis of executive analytics tools filled in the rest. I'm flagging that distinction rather than presenting it as deeper research than it was.
04

The core experience: from a blank chat to a trusted answer.

Every part of the flow exists to solve one problem, get an executive from "I have a question" to "I have my answer," without a single wasted step.

Eliminate extra steps reduce time taken to get to answer
✍️ Keep the trust as base
Open chat
Executive opens the assistant from the dashboard
→
See suggestions
Six likely questions surface immediately
→
Ask naturally
Type or speak the question in plain language
→
Get a sourced answer
Response, chart, source and timestamp together
→
Follow up
Keep going without starting over
AI Chatbot information architecture
Why suggested questions matter as much as the answer engine — The biggest early adoption risk was never a wrong answer, it was silence. If an executive didn't know what to type, the assistant never got a chance to prove itself.

Why every non-answer still gets a full response — Leaving a question blank when the assistant couldn't help would look like a broken product. Naming what's coming and redirecting turned a dead end into a next step.
05

The final interface makes trust visible, not implied.

The biggest design shift wasn't visual. It was deciding what the assistant should say when it couldn't answer at all.

V1 · Stay quiet about the gap
  • Early idea: don't respond to anything outside L1 and L2 scope
  • Kept the experience clean and avoided drawing attention to limits
  • But a missing answer reads as a broken assistant, not a scoped one
→
V2 · Say it, then redirect → Shipped
  • Every out-of-scope question gets an honest reply naming what's on the roadmap
  • Every permission-denied answer explains why, and who to ask
  • Both states redirect to a question the assistant can actually help with

Every answer arrives with a source. Every gap gets a straight, human response instead of silence.

AI Chatbot final interface — suggested questions, sourced answers, chart and error states
06

What I delivered.

A complete, design-system-aligned experience, from the first suggested question to the last edge case, inside one month.

DESIGN FOR TRUST, NOT JUST TASKS

A correct answer that nobody believes is still a failed product. Sourcing and transparency were treated as core features, not nice to haves.

MEET PEOPLE WHERE THEY DON'T KNOW WHAT TO ASK

Suggested questions did more for adoption than the answer engine itself, because they solved the moment before the question even happens.

TURN A GAP INTO A REDIRECT

When the product can't help, saying so honestly and pointing somewhere useful beats the illusion of solving it, instead of losing the relationship.

The goal was never to build a chatbot that could answer everything. It was to build one an executive would actually come back to.

Scope note: this case study describes a real one-month engagement for a leading CPG company. To protect client confidentiality, brand names, exact figures and screens shown here are representative recreations, not reproductions of the client's actual dashboard or data.

The best AI feature is the one people actually trust enough to use.
AI-driven product design: treat trust as a design problem, not an afterthought, and make sure the answer engine still leaves the user in control.

AI Chatbot • Product Design Case Study • Madura Sankar
VIEW OTHER CASE STUDY BACK