Project:
Configuration (Logik.io)
Cisco
Overview & Objective
Cisco’s goal was to streamline the configuration of server chassis and blades by implementing Logik.io—a configuration tool that simplifies complex product setups. In this case, it enabled a bottom-up configuration process, starting at the individual server level and building up to the chassis. Think of a chassis as a home that houses all server blades. It provides the server blades a unified place to work together effectively.
Business Context
It is unknown what system they used prior, but Cisco used a different engine to configure their purchased servers and hardware. They were having a lot of difficulties with it as far as user experience. However, Cisco provided a walkthrough of their existing system which gave designers a quick glance of the UX difficulties they were experiencing. I also believe their license with the current system was expiring and they wanted an alternative that may function with a better UX.
Discovery and Research
An experience architect and I worked frequently with each other (given that this was a very technical project to understand and navigate). We were given very little instructions and due to privacy constraints we were not able to view the current system they were using. This led us to try our best to understand Logik.io and how it worked, which led us to design ideas. Our design ideas were not exactly visually appealing, because the customer did not care or want that. The people who use this product are very technical and have no need for anything other than a good UX rather than an attractive UI with added bells and whistles.
This UI could have been easily extremely cluttered and overwhelming, involving many inputs to identify exactly how the blades and chassis were configured. This looked like several inputs, which led us to the design idea of roll ups navigated with clickable chevrons. This allowed us to have an overwhelming amount of inputs and content on a page, without it looking too cluttered. It also allowed us to point out what sections needed filling out, which was important because during the research stage, we found out that the end users sometimes will need hours to make the configurations due to the high volume of inputs and little room for human error.
Design Iteration & Prototyping
Challenges Faced
This project was unique in the way that typically we are instructed to use out of the box reusable Salesforce components (SLDS), or slightly customized Salesforce components, however, we were told to use out of the box Logik.io components which were very bare boned and not aesthetically pleasing due to the nature of the configuration tool.
The Salesforce team was told on several occasions to halt all work, due to licensing agreement issues. The design team was not informed on when the Logik.io license was going to be signed and we were often left in the dark on the progress with leadership decisions. Instead of halting all work, we knew that if the contract could unexpectedly be signed any morning, then we would have a huge backload of design work.
In order to get ahead of the design, knowing that the license could be signed at any given time, and simply to make the best use of our time, we wireframed possible Logik.io designs with the knowledge I had researching about how it functioned during the configuration process. I also had to learn about chassis and blades, which my experience architect was primarily responsible for explaining to me and guiding me in the right direction UI wise and explaining the technicality behind it. Ultimately, we explained to the customer that we did not want to stop the design work, so we still demoed the designs to the customer, and they were really pleased with the designs overall even given the license constraint.
Clickable Prototype
Outcome & Impact
Ultimately, my project contract with Cisco was 8 months, and given that the design was in good standing, I rolled off the project and eventually the Logik.io licenses were issued after I was no longer on the project. However, I was told the designs were put to effective use. The client has relayed that the users are pleased with the interface. Personally, it was difficult for me to not pay attention to the modern look and feel (UI) of the wireframes, but the client made it clear they wanted a bear boned, strictly OOTB look and feel, and they were ultimately very pleased with how we made that possible.