Project duration
Oct-Jan 2023(16 weeks)
Project duration
Oct-Jan 2023(16 weeks)
My role
Lead UX designer
My goal, as the lead UX designer, was to transform the Bodo.ai platform, making it much easier to navigate and perform tasks related to clusters and workspaces. This led to a substantial 40% improvement in user experience. This achievement was the outcome of in-depth research, creative planning, prototype building, and insightful conversations with users. I took charge of developing new ideas, mapping out the process, crafting detailed blueprints, and designing an appealing interface. I collaborated closely with project managers, subject matter experts, and software developers to uphold exceptional UX standards. Additionally, I conducted thorough interviews with 7 users, gathering invaluable feedback to further refine and enhance the Bodo.ai platform.
Before the redesign, Bodo users, even experienced data engineers and scientists, faced challenges navigating the platform to complete essential tasks like configuring clusters, managing workspaces, and selecting the right instance types. The lack of guidance, unclear permissions, and inconsistent navigation led to frequent misconfigurations, accidental deletions, and confusion about costs and performance. These issues resulted in higher support tickets, user frustration, and directly threatened adoption, retention, and overall trust in the platform.
To improve usability and reduce critical user errors by enhancing the clarity of job status, permissions, and workflows, making it easier for users to confidently manage clusters, configure jobs, and navigate the platform without confusion or unnecessary support. This directly supports improving user adoption, retention, and operational efficiency.
The platform’s complexity makes it difficult even for experienced users to confidently complete essential tasks. To address this, we propose an intelligent assistant that leverages smart UX, product design, and automation to simplify setup. The Smart Cluster Recommendation Engine guides users through a brief workflow, asking a few targeted questions to recommend the optimal machine type, Bodo version, instance configuration, and scaling strategy. Paired with a Cost Estimator with Slider Control, users receive real-time pricing feedback to better understand cost-performance trade-offs. Together, these features reduce friction, prevent misconfigurations, and enable users to make confident, cost-effective decisions.
Leading platforms like Databricks and Snowflake stand out for their user-centric design and advanced data-handling capabilities. Databricks offers IPython-style notebooks and automated cluster management, supported by a modular UI and side navigation that simplifies workflow and feature discovery. Snowflake emphasizes cloud-based accessibility, with options for editing cluster properties and a dedicated support menu, empowering users with seamless, scalable data analysis experiences.
I performed user interviews and surveys to better understand the users and their requirements. I conducted the evaluation, followed by several usability testing sessions with data scientists using the beta platform with the help of the product manager and chief engineer. In the end, we identified the key areas for improvement in the platform.
Insight
Pain Point
Design response
Cluster Accidental Deletion: Users didn't know there was no delete confirmation.
Missing confirmation.
Added warning modal with red button and confirmation.
Workspace Visibility: Users couldn't easily see which workspace they were in.
Hard to find active workspace; confusing navigation.
Make active workspace name more visible.
Instance Type & Cost: Users didn't know which computer type to pick or its cost.
Confused by computer types; worried about cost.
Clearer computer type details, examples, and a cost estimator with a slider for live pricing.
Version Selection: Users struggled to pick the right Bodo version.
Unsure about version; couldn't find "latest/best."
Label "latest/recommended" Bodo version clearly; add short tips.
Cluster Editing & Notifications: Users found it hard to change cluster settings and wanted alerts.
Couldn't find edit options; no alerts for changes.
Make cluster edit options easy to find; add email alerts for changes.
Support Access: Users couldn't find where to get help.
Hard to find support; felt stuck.
Put "Help" link in an easy-to-find spot.
Even experienced users struggle to complete essential tasks like choosing the right cluster, configuring instances, or locating support.
The system doesn’t support or educate users through their workflows.
Users are forced to make complex decisions (e.g., machine type, scaling, versions) without guidance.
Users don’t understand how changes affect cost and performance.
Returning users often have to reconfigure setups manually.
Returning users running similar jobs repeatedly may forget or misconfigure settings.
These early ideas were rejected because they didn’t balance ease of use with guidance. The setup wizard was too rigid for advanced users, while the full control dashboard overwhelmed beginners with too many options and no help. Chat-like guided questions leave users confused and prone to mistakes. We needed an approach that guides users, lets them adjust settings, and shows live cost estimates, helping them make better, more confident choices.
Added a confirmation step before deleting the workspace.
Added the capability to edit the cluster properties such as name, type, and instance number.
Added a permission setting to the cluster to control user access rights.
The changes above were made after conducting and analyzing the results of the usability study.
View the Bodo.ai high-fidelity prototype
The project led to positive outcomes by simplifying the user journey, removing unnecessary steps, and reducing confusion. I explored different design approaches and visual elements to better align with Bodo’s goals. I also practiced explaining my design decisions to the team, which helped get many of my ideas into the final product.
One mistake I made was trying to solve too many problems at once. I learned that it’s better to focus on fixing the core issues first, instead of spreading my efforts too thin. This helped me become more strategic and thoughtful in my design process.
A/B test new permission UX with 20 beta users
Instrument cluster deletion flows to track modal interactions
Measure the drop in error rate from deletion attempts without permission
Make simple guides or videos for new features.