Kosmos is a no-code platform for industrial IoT that lets you control and monitor your applications remotely, and makes hardware as flexible and easy to update as software
project background
Kosmos is a no-code platform that allows users to collect environmental data with connected sensors. It allows customers (who are primarily from manufacturing, logistics, energy production, and other industrial sectors) to remotely control and update their IoT applications and devices. Kosmos provides email alerts and web-based sensor and diagnostic monitoring for IoT devices, and enables users to customize email alert settings, and monitor their devices in a browser-based dashboard that surfaces diagnostic data, data insights, and alerts, and leverages machine learning for predictive analytics and anomaly detection.
my role
I led the UX and visual design through several rounds of iterations, and contributed to product strategy and technical implementation. I helped improve the navigation structure, interface messaging, and on-boarding experience for both new and experiences users. Distilling complex problems, needs of our customers, and business objectives into actionable goals, I led the design from concept through iteration and worked closely with engineers and product managers to define feature specifications, implement the new design, and produce detailed behavior and interaction specifications.
first iteration: conversational ui
The first iteration showcases a conversational UI format that guides first-time users through the flow of creating and deploying sensor and actuator alerts for their devices. This is a key feature that enables users to create multiple conditional statements that allows them to receive notifications when attention is required after a condition is met, and remotely control and update their applications to help reduce waste and resource consumption and provide protection against mishaps. Click to expand and view details.
design objectives & goals
Going into this project, our objective was to build a platform with a cohesive and approachable design language and an on-boarding flow that would make the process for creating and deploying sensor alerts as intuitive and seamless as possible, in order to appeal to users from all levels of digital literacy. I also wanted to bring a clean and modern look and feel to Temboo's platform and bring it up to date with current design trends and web standards.
process
I started out by conducting a competitive analysis of similar products in this space and thinking about how our product could improve upon what others were doing. I handled additional research to understanding how we could design and implement a conversational interface and whether it would be valuable to our customers. I also conducted an analysis of areas of improvement on Temboo’s current product experience and pinpointing the key pain points that needed to be resolved.
steps forward
Due to time constraints and limited resources, we decided to move away from this direction and towards a design that expanded on Temboo’s existing design template for similar products and could be pushed out to customers sooner.
second iteration: the final design
For the second (and final iteration) I built out the pre-existing design and made key improvements to the architecture that would enhance the product experience for users, enable scalability, and improve the overall visual design, while working with the engineers’ time constraints. Click the images to expand and view details.
final thoughts
A significant aspect of this product was the presence of machine learning-driven insights that customers could access about their devices. One of the challenges I encountered was communicating these features while keeping the confusing and overly technical language to a minimum, and only surfacing what was of value to the customer. Additionally, when working in a very lean team, it’s crucial to keep moving even when product requirements are changed drastically – through the process of the first iteration of the design, the stakeholders made a decision to prioritize pushing out an MVP and then build on that and making incremental improvements as feedback was received from customers. As the sole designer for this project, I learned to not get too attached, and to take elements that proved to be successful and apply that to subsequent versions.