anylytics.ai

anylytics.ai

IndustryB2B, SaaS
TimeframeSummer 2024
RoleUI/UX Designer
TeamProject Managers, Designers, Software Engineers
Data Copilot Overview

Anylytics.AI, an upcoming startup that houses and interprets complex data scopes for businesses, needed an interactive, intuitive, and social AI chatbot feature for their platform.

As a lead designer, I was tasked with building an interactive chatbot that could simplify complex data insights without overwhelming users.

What is Anylytics about?Anylytics wants to make data interpretation easier for both excel warriors and data newbies, as they cater to businesses in a variety of industries. The goal is to democratize data analytics in the current market!

Data Copilot on a laptop, showing the Visualize Data chart picker
Research 01 / 04

I conducted three quick interviews with a crystal report analyst, consultant, and product manager to understand user pain points with current data analytics and AI tools on the market. Here’s what I found...

01

Users crave clear next steps.

Interviewees who had experience with tools like JuliusAI and Microsoft Power BI expressed that while there were a variety of useful data analytic tools, there was a steep learning curve for beginners.

02

Current tools lack customization.

There seemed to be a general lack of customization for data visualizations and interfaces, often making products fall short of specific business needs.

03

Desire for more data context.

People also had a desire to see multiple data insights within one seamless interface, and understand the technical context of their data.

With this in mind, I went into the design process focusing on both users new to data analytics and those with more experience.

*Another feature I focused on in initial designs was the ability to share conversations between employees. Although not implemented into the final MVP, I really enjoyed working on it.

First Iterations 02 / 04

Initial designs aimed to empower users to generate graphs and tables, switch between data scopes, and share data between teams.

I introduced tabs to simulate a familiar user experience that would let them easily switch between data scopes.

Design System
Design system: Gilroy type scale, search dropdown, buttons, selection highlight and icons
Color palette: #0F49A0, #D0D5DD, #77ABF9, #5D5D5D, #FFFFFF
First iteration of the Data Copilot conversation page
Team Feedback 03 / 04
What the team found

The interface felt crowded and lacked clear action paths after the copilot provided data.

Users need a more direct way to switch between data sets, as this was a central component of the user experience.

“Users will feel lost among all the tools”

Notes + feedback from the product team led me to revisit how the workspace reflected AI generated insights + the relationships between data scopes and connections that are present throughout the rest of the product.

Guiding question

How can micro-components (touchpoints, dropdowns) clarify this system?

A lot of my work from here on out was refining + developing micro-components within the interface. The general design was there, and due to quick shipping timelines, couldn’t undergo much change. However, smaller interactions within the interface were undefined, and didn’t provide enough context for the data. Here are a few things I was developing over rounds of revision: data scope switching, conversation filtering, and clarifying feature functionality.

Final Iterations 04 / 04
Less clutter

To reduce clutter, I introduced collapsible navigation and sidebars, and added feature icons (sharing, visualizations, MySQL code generation) to make advanced features more accessible without overwhelming users.

More context

I also added conversation filtering + visible scope switching, to allow users to access scopes outside of conversation tabs and easily parse through past conversations, adding more context for data insights.

Less anxiety

Additionally, for more hesitant users, I implemented confirmation states, to make the user experience less anxiety inducing!

Previous model interface, always open
Revised collapsible model interface
Old scope switching, with no visual connection between the current scope and switching scopes
Revised visible scope switching with tooltips
Confirm Copilot Refresh dialog over the Copilot conversation
Results Outcome
50+Participants in successful testing
~85–95%Projected task completion rate
On timeMVP delivered and integrated into the live product

Testing also showed a decrease in task completion time from the initial design.

Reflection Why is this important?

In a market increasingly reliant on AI tools, it’s hard to stand out as a competitor. For Anylytics.AI, this meant putting the user first, and prioritizing an experience that businesses want to come back to.

As a designer, this project provided me an opportunity to think about data accessibility, and how we as developers, designers, and engineers can make the technical world more friendly for all. (: