Brevian
Brevian
Brevian
Redesigned Agent Tasks feature to enhance usability and provide a seamless experience for business users.
Redesigned Agent Tasks feature to enhance usability and provide a seamless experience for business users.
Redesigned Agent Tasks feature to enhance usability and provide a seamless experience for business users.
Internship · Feature Redesign
Role
UX Design Intern
Conducted a heuristic evaluation, designed solutions for 3 major features
Role
UX Design Intern
Conducted 1 heuristic evaluation, designed solutions for tasks, tools, integrations, and workspaces features
Role
UX Design Intern
Conducted a heuristic evaluation, designed solutions for 3 major features
Timeline
2.5 months
Timeline
2.5 months
Timeline
2.5 months
Team
1 Front-End Developer
2 Product Managers
5 Engineers
Team
1 Front-End Designer
2 Product Managers
5 Engineers
Team
1 Front-End Developer
2 Product Managers
5 Engineers
Tools
Figma
Tools
Figma
Tools
Figma
Background
Context
During the summer of 2024, I was UX Design intern at Brevian where I worked with a front-end developer and two product managers to redesign the interface for the Agent Tasks feature. I also created designs for the Workspaces and Tools pages.
The goal of the Agent Tasks feature is to enable users to define tasks for an Agent, which will process computations and deliver results to a designated output destination. The aim is to create a resilient and efficient task orchestration system that operates independently of client connectivity issues and can handle long-running tasks seamlessly.
Problem
The interface does not efficiently and intuitively present the necessary set of actions end users require to be able to use the Agent Tasks feature, which is to be able to configure a task for an agent to execute. The existing user flow and design does not demonstrate the desired functionality of the Tasks feature and visual language of the Brevian platform.
Background
Context
During the summer of 2024, I was UX Design intern at Brevian where I worked with a front-end developer and two product managers to redesign the interface for the Agent Tasks feature. I also created designs for the Workspaces and Tools pages.
The goal of the Agent Tasks feature is to enable users to define tasks for an Agent, which will process computations and deliver results to a designated output destination. The aim is to create a resilient and efficient task orchestration system that operates independently of client connectivity issues and can handle long-running tasks seamlessly.
Problem
The interface does not efficiently and intuitively present the necessary set of actions end users require to be able to use the Agent Tasks feature, which is to be able to configure a task for an agent to execute. The existing user flow and design does not demonstrate the desired functionality of the Tasks feature and visual language of the Brevian platform.
Background
Context
During the summer of 2024, I was UX Design intern at Brevian where I worked with a front-end developer and two product managers to redesign the interface for the Agent Tasks feature. I also created designs for the Workspaces and Tools pages.
The goal of the Agent Tasks feature is to enable users to define tasks for an Agent, which will process computations and deliver results to a designated output destination. The aim is to create a resilient and efficient task orchestration system that operates independently of client connectivity issues and can handle long-running tasks seamlessly.
Problem
The interface does not efficiently and intuitively present the necessary set of actions end users require to be able to use the Agent Tasks feature, which is to be able to configure a task for an agent to execute. The existing user flow and design does not demonstrate the desired functionality of the Tasks feature and visual language of the Brevian platform.
ORIGINAL SCREENS
Importance
As a business user, navigating a new tool such as Agent Tasks should be intuitive, without needing external assistance. The steps needed to define a task for an AI agent to execute a function properly should align with familiar user interactions to ensure efficiency within a given workflow. Since Brevian is utilizing AI Agents to compute, schedule, and execute tasks effectively in order to reduce cognitive load, the design of the interface must also reflect this objective.
Importance
As a business user, navigating a new tool such as Agent Tasks should be intuitive, without needing external assistance. The steps needed to define a task for an AI agent to execute a function properly should align with familiar user interactions to ensure efficiency within a given workflow. Since Brevian is utilizing AI Agents to compute, schedule, and execute tasks effectively in order to reduce cognitive load, the design of the interface must also reflect this objective.
Importance
As a business user, navigating a new tool such as Agent Tasks should be intuitive, without needing external assistance. The steps needed to define a task for an AI agent to execute a function properly should align with familiar user interactions to ensure efficiency within a given workflow. Since Brevian is utilizing AI Agents to compute, schedule, and execute tasks effectively in order to reduce cognitive load, the design of the interface must also reflect this objective.
Research Insights
HEURISTIC EVALUATION
My first course of action was to evaluate the existing Brevian platform to identify the most important UX issues and areas for improvements. I evaluated the interface from the perspective of both admins and business users based on 8 metrics:
Visibility of System Status
Match Between the System & the Real World
User Control and Reversibility
Consistency and Navigational Clarity
Error Prevention
Memory Recognition Ease
Flexibility and Efficiency of Use
Simplicity and Information Architecture
Research Insights
HEURISTIC EVALUATION
My first course of action was to evaluate the existing Brevian platform to identify the most important UX issues and areas for improvements. I evaluated the interface from the perspective of both admins and business users based on 8 metrics:
Visibility of System Status
Match Between the System & the Real World
User Control and Reversibility
Consistency and Navigational Clarity
Error Prevention
Memory Recognition Ease
Flexibility and Efficiency of Use
Simplicity and Information Architecture
Research Insights
HEURISTIC EVALUATION
My first course of action was to evaluate the existing Brevian platform to identify the most important UX issues and areas for improvements. I evaluated the interface from the perspective of both admins and business users based on 8 metrics:
Visibility of System Status
Match Between the System & the Real World
User Control and Reversibility
Consistency and Navigational Clarity
Error Prevention
Memory Recognition Ease
Flexibility and Efficiency of Use
Simplicity and Information Architecture
Key Issues
There is no clear feedback when inputting information or performing tasks; missing progress indicators, especially for first-time users
Tasks page has multiple usability issues, including unclear navigation, an unclear sequence of actions, and missing confirmation messages when saving
Task order, urgency, and roles are not clearly defined. The layout is undefined, making it difficult to understand Task structure
Some features (e.g., "Save" vs. "Submit" buttons) are redundant, and important Task-related actions are not distinguishable
Users do not always know how many steps are needed for completing a task; there are no clear ways to undo or exit certain actions
Initial Recommendations
Add visual feedback for task completion and input processes
Create a logical sequence for Task-related actions, ensuring users understand the steps required
Standardize UI elements; define button states, dropdown menus, and use distinct colors for selection, hover, and focus highlights
Implement clear cancel, undo, and back buttons to enhance user control
Introduce tooltips and brief explanations to help users understand important actions and expectations
Problem Statement
How might we redesign the Brevian "Tasks" feature to create a more intuitive and seamless experience for users configuring AI agent tasks?
User Flow Analysis
After my initial evaluation of the interface and overall user flow, I created a user flow diagram of the existing “Agent Creation” process as a way to layout all the pieces of this feature to understand how they are arranged within the system. This was an essential step of my research, as it allowed me to discover the existing relationship between elements, uncover gaps and areas for improvement, and lay a foundation for design.
Overall Questions
The order of menu items is not intuitive - Why is the current order of menu items structured this way?
A progress bar could provide guidance and feedback, ensuring users complete necessary steps - Should users be guided to fill out information in a specific order?
If users should enter details in a specific order, tabs should reflect this logical sequence - How can first-time user guidance be integrated (e.g., onboarding steps, tooltips, or contextual help)?
"Tasks" Insights
Confusing Trigger-Action Workflow: Adding/removing triggers leads to unexpected behaviors (e.g., triggers being deleted when removing an action)
Unintuitive Button Functions: The “+” and “-” buttons often duplicate existing functionality, making the interactions confusing
Lack of Confirmation: Assigning triggers or actions lacks a save button, forcing users to exit popups with no clear feedback
Broken Navigation Flow: Searching within the Tasks list suddenly exits users from editing and returns them to the Agents list page
Key Issues
There is no clear feedback when inputting information or performing tasks; missing progress indicators, especially for first-time users
Tasks page has multiple usability issues, including unclear navigation, an unclear sequence of actions, and missing confirmation messages when saving
Task order, urgency, and roles are not clearly defined. The layout is undefined, making it difficult to understand Task structure
Some features (e.g., "Save" vs. "Submit" buttons) are redundant, and important Task-related actions are not distinguishable
Users do not always know how many steps are needed for completing a task; there are no clear ways to undo or exit certain actions
Initial Recommendations
Add visual feedback for task completion and input processes
Create a logical sequence for Task-related actions, ensuring users understand the steps required
Standardize UI elements; define button states, dropdown menus, and use distinct colors for selection, hover, and focus highlights
Implement clear cancel, undo, and back buttons to enhance user control
Introduce tooltips and brief explanations to help users understand important actions and expectations
Problem Statement
How might we redesign the Brevian "Tasks" feature to create a more intuitive and seamless experience for users configuring AI agent tasks?
User Flow Analysis
After my initial evaluation of the interface and overall user flow, I created a user flow diagram of the existing “Agent Creation” process as a way to layout all the pieces of this feature to understand how they are arranged within the system. This was an essential step of my research, as it allowed me to discover the existing relationship between elements, uncover gaps and areas for improvement, and lay a foundation for design.
Overall Questions
The order of menu items is not intuitive - Why is the current order of menu items structured this way?
A progress bar could provide guidance and feedback, ensuring users complete necessary steps - Should users be guided to fill out information in a specific order?
If users should enter details in a specific order, tabs should reflect this logical sequence - How can first-time user guidance be integrated (e.g., onboarding steps, tooltips, or contextual help)?
"Tasks" Insights
Confusing Trigger-Action Workflow: Adding/removing triggers leads to unexpected behaviors (e.g., triggers being deleted when removing an action)
Unintuitive Button Functions: The “+” and “-” buttons often duplicate existing functionality, making the interactions confusing
Lack of Confirmation: Assigning triggers or actions lacks a save button, forcing users to exit popups with no clear feedback
Broken Navigation Flow: Searching within the Tasks list suddenly exits users from editing and returns them to the Agents list page
Key Issues
There is no clear feedback when inputting information or performing tasks; missing progress indicators, especially for first-time users
Tasks page has multiple usability issues, including unclear navigation, an unclear sequence of actions, and missing confirmation messages when saving
Task order, urgency, and roles are not clearly defined. The layout is undefined, making it difficult to understand Task structure
Some features (e.g., "Save" vs. "Submit" buttons) are redundant, and important Task-related actions are not distinguishable
Users do not always know how many steps are needed for completing a task; there are no clear ways to undo or exit certain actions
Initial Recommendations
Add visual feedback for task completion and input processes
Create a logical sequence for Task-related actions, ensuring users understand the steps required
Standardize UI elements; define button states, dropdown menus, and use distinct colors for selection, hover, and focus highlights
Implement clear cancel, undo, and back buttons to enhance user control
Introduce tooltips and brief explanations to help users understand important actions and expectations
Problem Statement
How might we redesign the Brevian "Tasks" feature to create a more intuitive and seamless experience for users configuring AI agent tasks?
User Flow Analysis
After my initial evaluation of the interface and overall user flow, I created a user flow diagram of the existing “Agent Creation” process as a way to layout all the pieces of this feature to understand how they are arranged within the system. This was an essential step of my research, as it allowed me to discover the existing relationship between elements, uncover gaps and areas for improvement, and lay a foundation for design.
General Questions
The order of menu items is not intuitive - Why is the current order of menu items structured this way?
A progress bar could provide guidance and feedback, ensuring users complete necessary steps - Should users be guided to fill out information in a specific order?
If users should enter details in a specific order, tabs should reflect this logical sequence - How can first-time user guidance be integrated (e.g., onboarding steps, tooltips, or contextual help)?
"Tasks" Insights
Confusing Trigger-Action Workflow: Adding/removing triggers leads to unexpected behaviors (e.g., triggers being deleted when removing an action)
Unintuitive Button Functions: The “+” and “-” buttons often duplicate existing functionality, making the interactions confusing
Lack of Confirmation: Assigning triggers or actions lacks a save button, forcing users to exit popups with no clear feedback
Broken Navigation Flow: Searching within the Tasks list suddenly exits users from editing and returns them to the Agents list page
Key Issues
There is no clear feedback when inputting information or performing tasks; missing progress indicators, especially for first-time users
Tasks page has multiple usability issues, including unclear navigation, an unclear sequence of actions, and missing confirmation messages when saving
Task order, urgency, and roles are not clearly defined. The layout is undefined, making it difficult to understand Task structure
Some features (e.g., "Save" vs. "Submit" buttons) are redundant, and important Task-related actions are not distinguishable
Users do not always know how many steps are needed for completing a task; there are no clear ways to undo or exit certain actions
Initial Recommendations
Add visual feedback for task completion and input processes
Create a logical sequence for Task-related actions, ensuring users understand the steps required
Standardize UI elements; define button states, dropdown menus, and use distinct colors for selection, hover, and focus highlights
Implement clear cancel, undo, and back buttons to enhance user control
Introduce tooltips and brief explanations to help users understand important actions and expectations
Problem Statement
How might we redesign the Brevian "Tasks" feature to create a more intuitive and seamless experience for users configuring AI agent tasks?
User Flow Analysis
After my initial evaluation of the interface and overall user flow, I created a user flow diagram of the existing “Agent Creation” process as a way to layout all the pieces of this feature to understand how they are arranged within the system. This was an essential step of my research, as it allowed me to discover the existing relationship between elements, uncover gaps and areas for improvement, and lay a foundation for design.
Overall Questions
The order of menu items is not intuitive - Why is the current order of menu items structured this way?
A progress bar could provide guidance and feedback, ensuring users complete necessary steps - Should users be guided to fill out information in a specific order?
If users should enter details in a specific order, tabs should reflect this logical sequence - How can first-time user guidance be integrated (e.g., onboarding steps, tooltips, or contextual help)?
"Tasks" Insights
Confusing Trigger-Action Workflow: Adding/removing triggers leads to unexpected behaviors (e.g., triggers being deleted when removing an action)
Unintuitive Button Functions: The “+” and “-” buttons often duplicate existing functionality, making the interactions confusing
Lack of Confirmation: Assigning triggers or actions lacks a save button, forcing users to exit popups with no clear feedback
Broken Navigation Flow: Searching within the Tasks list suddenly exits users from editing and returns them to the Agents list page
User Flow Analysis
After my initial evaluation of the interface and overall user flow, I created a user flow diagram of the existing “Agent Creation” process as a way to layout all the pieces of this feature to understand how they are arranged within the system. This was an essential step of my research, as it allowed me to discover the existing relationship between elements, uncover gaps and areas for improvement, and lay a foundation for design.
Overall Questions
The order of menu items is not intuitive - Why is the current order of menu items structured this way?
A progress bar could provide guidance and feedback, ensuring users complete necessary steps - Should users be guided to fill out information in a specific order?
If users should enter details in a specific order, tabs should reflect this logical sequence - How can first-time user guidance be integrated (e.g., onboarding steps, tooltips, or contextual help)?
"Tasks" Insights
Confusing Trigger-Action Workflow: Adding/removing triggers leads to unexpected behaviors (e.g., triggers being deleted when removing an action)
Unintuitive Button Functions: The “+” and “-” buttons often duplicate existing functionality, making the interactions confusing
Lack of Confirmation: Assigning triggers or actions lacks a save button, forcing users to exit popups with no clear feedback
Broken Navigation Flow: Searching within the Tasks list suddenly exits users from editing and returns them to the Agents list page
Design
Design Considerations
I was also given a few initial requirements for the UI by the project managers:
UI Goal: “Notebook”-like interface
Knowledge and tools should be easily configurable
I was also given a few initial requirements for the UI by the project managers:
UI Goal: “Notebook”-like interface
Knowledge and tools should be easily configurable
PRELIMINARY SKETCHES
Design Walkthrough
DESIGN SYSTEM
While I initially thought it would be a challenge to work within the constraints of an existing design system, I found that these limits allowed me to be creative. I was able to bring in new components, such as status bars, icons and various menus, that would help communicate user functionalities and elevate the UI while maintaining brand integrity.
Design Walkthrough
DESIGN SYSTEM
While I initially thought it would be a challenge to work within the constraints of an existing design system, I found that these limits allowed me to be creative. I was able to bring in new components, such as status bars, icons and various menus, that would help communicate user functionalities and elevate the UI while maintaining brand integrity.
TASKS EDITOR
Streamlining interactions via fewer steps but more directed actions.
The existing trigger-action setup caused unintended deletions and confusion when modifying tasks. My priority for the user flow was to establish a clear hierarchy and dependencies, so users could confidently add or remove elements without disrupting the workflow. This guided layout and design of the interface. I explored three different layout options before deciding on the final one as shown below.
TASKS EDITOR
Streamlining interactions via fewer steps but more directed actions.
The existing trigger-action setup caused unintended deletions and confusion when modifying tasks. My priority for the user flow was to establish a clear hierarchy and dependencies, so users could confidently add or remove elements without disrupting the workflow. This guided layout and design of the interface. I explored three different layout options before deciding on the final one as shown below.
As mentioned in the initial design UI requirements, it was important to ensure the look and feel of a "Notebook"-like interface. That helped me guide the visual elements and organization in the hi-fi wireframes. This included redesigning the action-oriented buttons (ex. "Run" vs "Run After") to have distinct functions. The layout of the "Triggers" menu, which is needed to test run the tasks, took time to figure out. However, with iteration and feedback, I decided to put it at the top to make the instruction creation process more guided and highlight its importance. The side menu with tools, knowledge and agents was informed by the tool panel on creative apps.
As mentioned in the initial design UI requirements, it was important to ensure the look and feel of a "Notebook"-like interface. That helped me guide the visual elements and organization in the hi-fi wireframes. This included redesigning the action-oriented buttons (ex. "Run" vs "Run After") to have distinct functions. The layout of the "Triggers" menu, which is needed to test run the tasks, took time to figure out. However, with iteration and feedback, I decided to put it at the top to make the instruction creation process more guided and highlight its importance. The side menu with tools, knowledge and agents was informed by the tool panel on creative apps.
Updating the information presented in the Past Runs table for a task was also necessary. The original table was cluttered and had past runs for many tasks which was confusing. The new design includes the trigger type, a "view" filter button and visual elements such as progress bars and status tags to make it easier to view and digest the various data for each run.
Updating the information presented in the Past Runs table for a task was also necessary. The original table was cluttered and had past runs for many tasks which was confusing. The new design includes the trigger type, a "view" filter button and visual elements such as progress bars and status tags to make it easier to view and digest the various data for each run.
TOOLS INTEGRATIONS
Prioritizing clarity and organization.
For the Tools Connection Dialog, I aimed to make it more logical, so I referenced the user flows to see where steps could be consolidated. Since this was a pop-up dialog, only accessible on the tasks editor page, I had limited space to work with. I prioritized making the main action, selecting the desired tool(s) for the task, more intuitive within the larger flow. Icons helped distinguish between tools that were already integrated and tools that could be added.
TOOLS INTEGRATIONS
Prioritizing clarity and organization.
For the Tools Connection Dialog, I aimed to make it more logical, so I referenced the user flows to see where steps could be consolidated. Since this was a pop-up dialog, only accessible on the tasks editor page, I had limited space to work with. I prioritized making the main action, selecting the desired tool(s) for the task, more intuitive within the larger flow. Icons helped distinguish between tools that were already integrated and tools that could be added.
I used a similar layout for the Tools Page, because it was essentially the same content as the dialog on the editor page. In my initial evaluation of the tools page, there was no way to add a tool, yet this was an essential action. I also kept the icons consistent to ensure clarity across pages, since making changes here would dynamically change the dialog content. To give the user more control, I created two additional layout views: a grid and a panel view.
I used a similar layout for the Tools Page, because it was essentially the same content as the dialog on the editor page. In my initial evaluation of the tools page, there was no way to add a tool, yet this was an essential action. I also kept the icons consistent to ensure clarity across pages, since making changes here would dynamically change the dialog content. To give the user more control, I created two additional layout views: a grid and a panel view.
NAVIGATION BAR
Integrating familiar interactions and icons.
The side navigation bar's collapse/expand function was not intuitive, sometimes collapsing automatically when switching pages (Why is there an "x" button for collapsing?). Additionally, the icon labels blended into the selection highlight, creating visibility issues.
NAVIGATION BAR
Integrating familiar interactions and icons.
The side navigation bar's collapse/expand function was not intuitive, sometimes collapsing automatically when switching pages (Why is there an "x" button for collapsing?). Additionally, the icon labels blended into the selection highlight, creating visibility issues.
The new side navigation bar design improved visibility and interaction clarity by distinguishing hover vs. selected highlights, ensuring the collapse/expand action is clear and consistent across the platform, and consolidating the placement of key elements like the dark mode toggle. I also created a more recognizable icon for the "Agents" tab.
The new side navigation bar design improved visibility and interaction clarity by distinguishing hover vs. selected highlights, ensuring the collapse/expand action is clear and consistent across the platform, and consolidating the placement of key elements like the dark mode toggle. I also created a more recognizable icon for the "Agents" tab.
Prototypes
Tasks Editor - Running Instructions
Configuring Triggers for a Task
Viewing Past Runs for a Task
Configuring Tools for a Task
Tools Page - Managing Your Tools
Navigation Bar Functionality
Takeaways
Takeaways
Challenges
Thinking about business goals in design.
My initial approach was focused on design decisions from a purely UX perspective. However, I quickly realized the importance of viewing the design holistically— considering feasibility, alignment with business goals, and integration within the broader user journey. To address this, I iterated on the prototype with feedback from developers, project managers, and engineers. The most important questions we asked were: Does this make sense within the larger user journey? Is it realistic to implement within the given timeframe? Does it align with the broader vision and objectives of the Agent Tasks interface?
Be proactive about feedback and alignment.
As the sole designer, I learned to take a proactive approach to seeking feedback and making design decisions. With a tight timeline, it was important to regularly check in with my team to catch anything I might be missing and incorporating the recent updates to the platform.
Things I would do differently
Conduct usability testing with business users.
Designs are always evolving. Given more time, I would have loved to observe how users interacted with my design to further refine it.
Get more feedback from other designers when iterating.
Receiving feedback from other designers would have provided valuable perspectives, helping to catch overlooked details and prioritizing during the design process.
Challenges
Thinking about business goals in design.
My initial approach was focused on design decisions from a purely UX perspective. However, I quickly realized the importance of viewing the design holistically— considering feasibility, alignment with business goals, and integration within the broader user journey. To address this, I iterated on the prototype with feedback from developers, project managers, and engineers. The most important questions we asked were: Does this make sense within the larger user journey? Is it realistic to implement within the given timeframe? Does it align with the broader vision and objectives of the Agent Tasks interface?
Be proactive about feedback and alignment.
As the sole designer, I learned to take a proactive approach to seeking feedback and making design decisions. With a tight timeline, it was important to regularly check in with my team to catch anything I might be missing and incorporating the recent updates to the platform.
Things I would do differently
Conduct usability testing with business users.
Designs are always evolving. Given more time, I would have loved to observe how users interacted with my design to further refine it.
Get more feedback from other designers when iterating.
Receiving feedback from other designers would have provided valuable perspectives, helping to catch overlooked details and prioritizing during the design process.