summary
summary
summary
problem
The existing open source KUI had the key functionality to visualize rich text using a terminal. However, it only had basic features that demonstrated the concept. My goal was to apply design thinking, in order to make the tool more useful and easier to use for its target personas.
target audience
target audience
target audience
Jill (developer)
RELEASE ENGINEER RACHEL
In order to get a deeper understanding of the product and to identify problem areas, I conducted a UX audit. My analysis showed that the site's design was dated, and the interaction model was complicated and at times confusing.
marcus (system admin)
RELEASE ENGINEER RACHEL
In order to get a deeper understanding of the product and to identify problem areas, I conducted a UX audit. My analysis showed that the site's design was dated, and the interaction model was complicated and at times confusing.
goals
After assessing the current journey, I worked with the team (product managers and developers) to define goals. They helped us align around our objectives and ensure that the team is in sync with human-centered objectives.
process
My process started with analyzing the existing too, and applying UX best practices and heuristics. In addition to making the UI more intuitive, we also added new features and commands that made the tool more powerful. After we felt confident that we have a good prototype, I worked with a UX researcher to conduct user testing and validate the prototype. Then, we made updates based on the feedback and applied the Carbon design system. KUI was integrated into the IBM Multiclould Manager platform.
sketches
hi-fi prototype
user research
user research
Hi-fi prototype
SKETCHes
USER TESTING
hi-fi prototype
Sketches
user testing
carbon design system
I collaborated with a visual designer to apply the Carbon Design system to KUI. This was done in order to make it more cohesive with the rest of the production-grade IBM products. Another reason was the fact that we were integrating KUI inside of IBM Multicloud Manager, so it was critical for KUI to look native to the overall platform.
final design
KUI was redesigned and integrated in IBM Multicloud Manager. The redesign included rethinking existing interatcions, adding new features, and applying a new design system. We also added support for multiple tabs, which would allow multiple terminal sessions at the same time.
search
Since searching for objects is key to any person that interacts with a Kubernetes cluster, it naturally became a key experience for us. We added autocomplete popup, in order to aid users in learning how to use search, as well as finding objects faster.
actions
We also added support for actions on pods (Kubernetes objects that hold processes). This was achieved by showing an overflow menu on hover for a pod row. This design could save users the time it would take to manually run commands (such a delete) for each action they want to run on a pod.
save
In order to get a deeper understanding of the product and to identify problem areas, I conducted a UX audit. My analysis showed that the site's design was dated, and the interaction model was complicated and at times confusing.
details sidebar
In order to get a deeper understanding of the product and to identify problem areas, I conducted a UX audit. My analysis showed that the site's design was dated, and the interaction model was complicated and at times confusing.
outcome
Our final design was delivered and presented to the team. It was well received and successfully implemented into MCM. As next steps, the team will observe how users are utilizing KUI and will strive to learn and improve the design. I believe that KUI can be further expanded to cover more use cases and provide more value to customers.
summary
problem
During my work at IBM, I was tasked with working on an open-source tool called KUI. The product is a command line interface (CLI) that also has graphic user interface (GUI) features. I redesigned the tool's user experience, in order to make it more valuable to people. I also designed a way in which KUI would be integrated into IBM's flagship cloud management tool, IBM Multicloud Manager.
target audience
Jill (developer)
In order to get a deeper understanding of the product and to identify problem areas, I conducted a UX audit. My analysis showed that the site's design was dated, and the interaction model was complicated and at times confusing.
marcus (system admin)
In order to get a deeper understanding of the product and to identify problem areas, I conducted a UX audit. My analysis showed that the site's design was dated, and the interaction model was complicated and at times confusing.
goals
KUI is an open-source tool developed in IBM Research that meant to modernize the Terminal/CLI experience by adding GUI-like features, like charts, tables and and richer interactions. Though the tool had a lot of potential, it was lacking cohesive design and its supported features were not built in a human-centered way. I was tasked with improving the functionality and usability of the product, while keeping its core DNA of being a CLI that includes elements of modern graphic interfaces.
process
My process started with analyzing the existing too, and applying UX best practices and heuristics. In addition to making the UI more intuitive, we also added new features and commands that made the tool more powerful. After we felt confident that we have a good prototype, I worked with a UX researcher to conduct user testing and validate the prototype. Then, we made updates based on the feedback and applied the Carbon design system. KUI was integrated into the IBM Multiclould Manager platform.
sketches
hi-fi prototype
user research
user research
Hi-fi prototype
SKETCHes
USER TESTING
hi-fi prototype
Sketches
user testing
carbon design system
I collaborated with a visual designer to apply the Carbon Design system to KUI. This was done in order to make it more cohesive with the rest of the production-grade IBM products. Another reason was the fact that we were integrating KUI inside of IBM Multicloud Manager, so it was critical for KUI to look native to the overall platform.
final design
KUI was redesigned and integrated in IBM Multicloud Manager. The redesign included rethinking existing interatcions, adding new features, and applying a new design system. We also added support for multiple tabs, which would allow multiple terminal sessions at the same time.
Search
Since searching for objects is key to any person that interacts with a Kubernetes cluster, it naturally became a key experience for us. We added autocomplete popup, in order to aid users in learning how to use search, as well as finding objects faster.
actions
We also added support for actions on pods (Kubernetes objects that hold processes). This was achieved by showing an overflow menu on hover for a pod row. This design could save users the time it would take to manually run commands (such a delete) for each action they want to run on a pod.
saving
In order to get a deeper understanding of the product and to identify problem areas, I conducted a UX audit. My analysis showed that the site's design was dated, and the interaction model was complicated and at times confusing.
details sidebar
In order to get a deeper understanding of the product and to identify problem areas, I conducted a UX audit. My analysis showed that the site's design was dated, and the interaction model was complicated and at times confusing.
outcome
Our final design was delivered and presented to the team. It was well received and successfully implemented into MCM. As next steps, the team will observe how users are utilizing KUI and will strive to learn and improve the design. I believe that KUI can be further expanded to cover more use cases and provide more value to customers.
