Designed the enterprise dashboard behind Asimov, an AI coworker in Slack, creating a unified system for managing data, tools, and workflows
Designed the enterprise dashboard behind Asimov, an AI coworker in Slack, creating a unified system for managing data, tools, and workflows
Designed the enterprise dashboard behind Asimov, an AI coworker in Slack, creating a unified system for managing data, tools, and workflows
TL;DR
TL;DR
Problem Space
Teams using Slack struggled to find relevant information across scattered conversations, shared files, and multiple tools. Employees often repeated questions or wasted time searching for context, reducing overall productivity and team efficiency.
Teams using Slack struggled to find relevant information across scattered conversations, shared files, and multiple tools. Employees often repeated questions or wasted time searching for context, reducing overall productivity and team efficiency.
Customer Needs
Reduce time spent switching between tools and searching for information
Maintain enterprise-grade privacy and control over shared knowledge
Fit into existing team workflows without heavy onboarding or setup
Reduce time spent switching between tools and searching for information
Maintain enterprise-grade privacy and control over shared knowledge
Fit into existing team workflows without heavy onboarding or setup
Business Goals
Prove measurable productivity gains through everyday usage
Enable scalable management of AI knowledge and integrations via a centralized dashboard
Differentiate Asimov in an increasingly crowded workplace AI landscape
Prove measurable productivity gains through everyday usage
Enable scalable management of AI knowledge and integrations via a centralized dashboard
Differentiate Asimov in an increasingly crowded workplace AI landscape
Solution
I designed Asimov, an AI coworker embedded in Slack, alongside a centralized desktop dashboard that helped teams manage knowledge, integrations, and agent behavior. Early adoption reached 41%, with a 33% reduction in task-related queries.
I designed Asimov, an AI coworker embedded in Slack, alongside a centralized desktop dashboard that helped teams manage knowledge, integrations, and agent behavior. Early adoption reached 41%, with a 33% reduction in task-related queries.
Timeline
Jan - March 2024
Jan - March 2024
Industry
Conversational AI
Conversational AI
B2B SaaS
B2B SaaS
Contribution
Product Design
Product Design
Research
Research
Collaborators
Product Manager
Product Manager
Full Stack Developers
Full Stack Developers
Customer Success Team
Customer Success Team
Too many messages. Too many tools.
Too little clarity.
Too many messages. Too many tools. Too little clarity.
Too many messages. Too many tools. Too little clarity.
Teams rely on Slack to collaborate, but critical knowledge often lives across documents, tools, and long-running conversations. Finding accurate information meant switching tabs, scrolling threads, or interrupting teammates, slowing work and breaking momentum.
Teams rely on Slack to collaborate, but critical knowledge often lives across documents, tools, and long-running conversations. Finding accurate information meant switching tabs, scrolling threads, or interrupting teammates, slowing work and breaking momentum.
These challenges compounded as teams grew, making it difficult to maintain a shared source of truth without adding more tools or manual overhead.
These challenges compounded as teams grew, making it difficult to maintain a shared source of truth without adding more tools or manual overhead.
15+ interviews
15+ interviews
“...Why do I need 10 different tabs open just to get one answer? I jump between Slack, Notion, HubSpot, Google Drive all day, and it’s exhausting....”
“...Why do I need 10 different tabs open just to get one answer? I jump between Slack, Notion, HubSpot, Google Drive all day, and it’s exhausting....”
Customer Success Professional
Customer Success Professional
“...I once spent 15 minutes scrolling through a 50-message-long discussion just to find a two-line answer, I could’ve messaged someone but I felt like that would disturb them...”
“...I once spent 15 minutes scrolling through a 50-message-long discussion just to find a two-line answer, I could’ve messaged someone but I felt like that would disturb them...”
Engineering Lead
Engineering Lead
“...I find myself digging through an endless pile of Slack messages. Searching for what I need is a task and by the time I find what I need, I’ve already lost my momentum...”
“...I find myself digging through an endless pile of Slack messages. Searching for what I need is a task and by the time I find what I need, I’ve already lost my momentum...”
Social Media Marketing Intern
Social Media Marketing Intern
Why an admin dashboard was essential
Why an admin dashboard was essential
While Asimov lived inside Slack, its effectiveness depended on how teams managed knowledge, integrations, and permissions behind the scenes. A dedicated desktop dashboard was essential to give admins visibility and control without overloading the conversational experience. I designed this dashboard as the operational backbone of the product, balancing flexibility for advanced teams with clarity for first-time setup.
While Asimov lived inside Slack, its effectiveness depended on how teams managed knowledge, integrations, and permissions behind the scenes. A dedicated desktop dashboard was essential to give admins visibility and control without overloading the conversational experience. I designed this dashboard as the operational backbone of the product, balancing flexibility for advanced teams with clarity for first-time setup.
Asimov Overview
Asimov Overview
Asimov Overview
Below is a representative view of the admin dashboard I designed to support Asimov. The interface allowed teams to connect knowledge sources, configure integrations, and monitor Asimov's usage in a scalable dashboard.
Below is a representative view of the admin dashboard I designed to support Asimov. The interface allowed teams to connect knowledge sources, configure integrations, and monitor Asimov's usage in a scalable dashboard.
Below is a representative view of the admin dashboard I designed to support Asimov. The interface allowed teams to connect knowledge sources, configure integrations, and monitor Asimov's usage in a scalable dashboard.
App Integration
App Integration
App Integration
An integration hub where teams can connect their everyday tools, giving Asimov the context it needs to deliver smarter, more relevant responses. Teams can easily view, manage, and disconnect integrations, all in one place.
An integration hub where teams can connect their everyday tools, giving Asimov the context it needs to deliver smarter, more relevant responses. Teams can easily view, manage, and disconnect integrations, all in one place.
An integration hub where teams can connect their everyday tools, giving Asimov the context it needs to deliver smarter, more relevant responses. Teams can easily view, manage, and disconnect integrations, all in one place.
Actions
Actions
Actions
With Actions, teams can decide what tasks Asimov can perform across connected tools. From updating a deal in HubSpot to creating a note in Notion, everything happens right inside Slack, reducing friction and saving time.
With Actions, teams can decide what tasks Asimov can perform across connected tools. From updating a deal in HubSpot to creating a note in Notion, everything happens right inside Slack, reducing friction and saving time.
With Actions, teams can decide what tasks Asimov can perform across connected tools. From updating a deal in HubSpot to creating a note in Notion, everything happens right inside Slack, reducing friction and saving time.
Key Design Decisions
Key Design Decisions
01
Aligned early on system boundaries
Aligned early on system boundaries
Aligned early on system boundaries
Defined clear separation between conversational interactions in Slack and administrative control in the dashboard to keep both experiences focused.
02
Designed for scalable knowledge management
Designed for scalable knowledge management
Designed for scalable knowledge management
Structured the dashboard to support multiple sources and permissions without increasing cognitive load for admins.
03
Balanced flexibility with clarity
Balanced flexibility with clarity
Balanced flexibility with clarity
Explored multiple IA patterns before committing to a layout that worked for both small teams and enterprise use cases.
04
Validated through internal evaluations
Validated through internal evaluations
Validated through internal evaluations
Used real team workflows to pressure-test assumptions and refine interaction patterns before broader exposure.
Reflection
Reflection
Working on Asimov was my first time designing something that sat at the intersection of AI, productivity, and everyday team communication. It was equal parts exciting and humbling.
Collaborating closely with engineers also pushed me to think beyond interfaces. I started to understand how systems, permissions, and integrations shape the final user experience. Even though the product didn’t move past beta, the process changed how I think about building products that feel seamless in complex environments.
Working on Asimov was my first time designing something that sat at the intersection of AI, productivity, and everyday team communication. It was equal parts exciting and humbling.
Collaborating closely with engineers also pushed me to think beyond interfaces. I started to understand how systems, permissions, and integrations shape the final user experience. Even though the product didn’t move past beta, the process changed how I think about building products that feel seamless in complex environments.
Working on Asimov was my first time designing something that sat at the intersection of AI, productivity, and everyday team communication. It was equal parts exciting and humbling.
Collaborating closely with engineers also pushed me to think beyond interfaces. I started to understand how systems, permissions, and integrations shape the final user experience. Even though the product didn’t move past beta, the process changed how I think about building products that feel seamless in complex environments.