Aiota Desktop & Tablet
Product design for Aiota
Aiota Desktop was designed to be the go-to hub for making sense of the data flowing in from our suite of applications. While our mobile tools focused on capturing and executing tasks on the go, the desktop experience offered users a complete overview bringing everything together in one cohesive dashboard.
It served as the control center where users could monitor activity, analyze performance, and manage operations with greater depth and clarity. From warehouse updates to pricing controls and logistics tracking, the desktop experience was tailored for tasks that required a broader perspective and more screen real estate.
Tablet versions were also developed to support flexibility in the field offering the same power and structure, but in a portable format. Together, the desktop and tablet platforms became essential for users who needed both insight and control grounded in a design that prioritized usability, structure, and data visibility.
HIGHTLIGHTS
Shaping Seamless Experiences Through Design and Partnership
As both Project Manager and Design Lead at Aiota, one of my main priorities was making sure the data we showed actually made sense to the people using it. We had a lot of information coming in from different systems and sources and my job was to help turn that into something clear, useful, and easy to work with.
I worked closely with the developers throughout the project to understand how the data was structured, what was possible technically, and how we could display it in a way that made sense in the user’s daily workflow. We had ongoing conversations to fine-tune logic, fix edge cases, and make sure what we were showing on screen was both accurate and helpful.
This close collaboration helped bridge the gap between back-end complexity and front-end clarity and made sure the final product didn’t just work, but actually worked for the people using it.
My Role in the Project
As Design Lead and Project Manager, I worked at the intersection of strategy, design, and delivery. My responsibility was to turn real-world needs into practical digital tools quickly and effectively. With limited time and high complexity, I had to balance short-term decisions with long-term scalability.
The process involved close collaboration with developers to handle data precision, working with stakeholders to stay aligned, and continuously refining the user experience to support those using the product every day. My focus was always on delivering something that felt both purposeful and easy to use right from the first click.
Before jumping into design, I spent time understanding the core problems we needed to solve. This wasn’t just about listing features—it was about asking the right questions, listening to users, and identifying where they were actually struggling in their day-to-day work.
Once we had clarity, I helped break those challenges down into manageable pieces and worked with the team to prioritize what to tackle first. We focused on solving the problems that would bring the most value early on—without losing sight of long-term goals. This approach helped us move quickly while staying grounded in what really mattered for the people using the product.
Gathering feedback early and acting on it was a big part of how we worked. Throughout the project, I made sure we kept an open loop with both users and stakeholders, so we could quickly spot what was working and what wasn’t.
Instead of waiting until the end, we shared early versions, prototypes, and flows to get honest input.
Sometimes that meant reworking parts of the interface, adjusting logic, or simplifying things we thought were “clear enough.”
This iterative way of working helped us catch issues early, make smarter decisions, and ultimately build a product that felt right for the people using it because their voices shaped it along the way.
Maintaining quality and consistency was a key part of my role especially as the product evolved across screens and use cases. I focused on making sure the experience felt cohesive, whether you were on desktop, tablet, or mobile.
To do that, I built and continuously refined a shared design system that helped keep spacing, colors, typography, and components aligned. This also made collaboration with developers smoother, since we all worked from the same visual language.
I regularly reviewed and tested designs to make sure they held up in different contexts both visually and functionally. The goal was always the same: create something reliable, easy to use, and consistent from one interaction to the next.
See images from the Figma file
REFLECTIONS
Balancing Structure and Empathy in a Fast-Paced Project
Wearing both the Project Manager and Design Lead hats taught me a lot about balance between moving fast and staying thoughtful, between structure and empathy.
As a PM, I had to keep timelines tight, decisions clear, and communication flowing across the team. But as a designer, I also had to slow down at the right moments to listen, observe, and make space for user insight to shape what we built.
What made the process work was staying close to the people on both sides developers who needed clarity and structure, and users who needed tools that genuinely supported their day-to-day work. Keeping those needs aligned was where the real challenge and the real impact lived.
Looking back, this project reminded me that good design isn’t just about clean interfaces. It’s about building trust, guiding a team through complexity, and creating something useful for the people who rely on it.
