Mobile Operations Platform

The project: A complex operational platform needed to turn regulated requirements, live monitoring and follow-up workflows into an experience that users could understand and act on across mobile, tablet and desktop.

My contribution: I joined an existing foundation of requirements, information architecture and a basic UI Kit. After reviewing and refining that foundation, I became the Sole Product Designer, leading UX across the platform—covering flows, interaction design, responsive behavior, visual design, Design System evolution, prototyping, validation and developer handoff.

The outcome: The MVP established a combined application architecture, state-based operational experience, connected workflows, responsive foundation and product-specific Design System. Approved designs were being implemented incrementally when I left the project due to budgetary constraints.

The product served a highly regulated operational environment. Users needed to monitor live information, interpret changing conditions and take appropriate action without losing sight of the operational context.

The requirements had already been translated by the Business Analyst into functional needs, priorities and an initial information architecture developed together with the previous UX Designer.

The challenge was to turn that foundation into an experience that made complex information understandable and actionable across mobile, tablet and desktop contexts.

The UX therefore needed to establish clear hierarchy across three interconnected needs:

The requirements map translated the Business Analyst’s functional needs and priorities into product areas and MVP scope. It provided the starting point for reviewing how those capabilities should be organized in the application.

During my first weeks, I reviewed the initial information architecture and worked alongside the previous UX Designer to complement and refine it across the product. I also audited the UI Kit proposed by the Tech Lead and identified opportunities to establish stronger UX patterns and consistency.

I subsequently became the Sole Product Designer, leading UX across the platform. From that point onward, I led the UX flows, interaction design, responsive behavior, visual design, Design System evolution, prototyping, validation and developer handoff.

The resulting application architecture organized those product areas into one unified experience, connecting operational and administrative capabilities while accounting for different user roles and access levels.

The product needed to bring operational and administrative capabilities together within a unified application architecture.

I helped establish a unified structure and navigation model across operational and administrative workflows, while accounting for different user roles and levels of access.

The architecture needed to support both day-to-day operational use and more advanced configuration and management activities without creating disconnected experiences.

A central design challenge was translating complex underlying information into an interface that users could understand and act upon without exposing unnecessary system complexity.

The backend remained the source of truth for data and rules, while the interface needed to make relevant information, conditions and available actions clear.

I focused on hierarchy, progressive disclosure and contextual interaction so users could access the information needed for a decision without being overwhelmed by the full complexity of the system.

The dashboard translated changing operational conditions into distinct levels of attention and action. Normal, warning, critical and unavailable states needed to be recognizable without relying on users to interpret raw data alone.

I designed visual and interaction patterns to make these distinctions recognizable at a glance and consistent across the application.

Progressive disclosure allowed more detail to become available when needed rather than presenting every possible piece of information at once.

The experience needed to support a connected path from detecting a condition through review, action and confirmation. Each step had to preserve enough context for the next decision.

I designed the sequence to keep each step understandable and actionable, avoiding unnecessary navigation and keeping the condition’s context available throughout follow-up.

The goal was to make the interface support decision-making rather than simply expose the underlying system structure.

The project began with a basic React UI Kit proposed by the Tech Lead. I audited that starting point and expanded it to support the product’s specific interaction and responsive requirements.

I expanded the foundation into a product-specific Design System, defining and refining components, variants, interaction patterns and responsive behaviors required by the application.

The library covered buttons, chips, accordions, inputs, cards and navigation patterns, with the variants and states needed to support the product’s operational workflows. The goal was not simply to collect UI elements, but to establish reusable behavior and consistency across the application.

The Design System helped maintain consistency while accommodating the complexity of the product and its different responsive contexts.

The product was designed mobile-first rather than treating mobile as a reduced version of a desktop interface.

Information hierarchy, interaction patterns and component behavior needed to work within limited screen space while remaining scalable to larger screens.

On mobile, information was carefully stacked and prioritized. On larger screens, the same structures could unfold to provide greater visibility without changing the underlying interaction model.

The responsive experience needed to support mobile, tablet and desktop contexts.

I focused on preserving the visibility, accessibility and actionability of important information while redistributing hierarchy according to available space.

This meant reconsidering how information was grouped, how controls were exposed and how components unfolded as the viewport increased.

The work was reviewed continuously with the core product team. Business, technical, regulatory and usability considerations — together with stakeholder feedback and technical feasibility — informed successive iterations. Flows and edge cases were examined before moving into development.

At the point I left the project due to budgetary constraints, the MVP’s principal areas and flows had been defined, the combined application architecture had been accepted, and the approved designs were being implemented incrementally.

The project established a UX foundation for a complex operational product: a unified application structure, state-based interactions, connected follow-up workflows, a responsive experience and a product-specific Design System for technical, regulated and information-dense work.

One of the most important lessons from the project was the distinction between the complexity of the underlying system and the complexity that needs to be exposed to the user.

The backend owns the data and rules. The interface’s role is to make that system understandable, navigable and actionable.