User flows

During this phase, I partnered closely with product managers, engineers, and QA to define and prioritize features for each design and development sprint.

Informed by user research, we analyzed current task flows to identify friction points and opportunities for simplification.

One major challenge was the fragmented process for creating a Digital Twin. Previously, users had to navigate a disjointed, nonlinear workflow. To improve this, we consolidated the steps into a single, cohesive flow—streamlining the experience and reducing user confusion.

Next, I developed interactive prototypes in Axure, which allowed us to visualize and validate the end-to-end user flow. These clickable models enabled the team to collaboratively explore the experience, identify pain points, and uncover opportunities for improvement.

We tested multiple iterations, incorporating feedback from stakeholders and usability testing, until we arrived at a version that delivered the most intuitive and effective experience for our users.

Information architecture (IA)

To make the platform more approachable, especially given the complexity of IoT, we introduced a “Getting Started” guide as the user’s landing page after sign-in. This onboarding experience provides contextual guidance, tutorials, and foundational IoT concepts to help users quickly understand how to navigate and use the platform effectively.

We restructured the navigation to group related items logically, making it easier for users to locate features and understand how different sections of the platform connect. This improved information architecture was informed by card sorting exercises, which revealed how users naturally categorize key functions. As a result, discoverability improved and the overall user experience became more intuitive.

Interaction design

Microinteractions were strategically implemented to reinforce data integrity and prevent errors.

For instance, on the Device Detail screen, the delete function is disabled for active devices. Attempting to delete an enabled device triggers a subtle notification guiding the user to disable it first, preventing accidental removal.

The delete option becomes available only after the device is disabled, with confirmation prompts ensuring deliberate action.

The Ecosystem Browser was a key UI feature designed to empower users to explore and construct their platform ecosystems intuitively. Drawing inspiration from the familiar and efficient column navigation of MacOS Finder, this pattern enabled a seamless experience for users to drill down through hierarchical levels of their ecosystem and create new entities precisely where needed within that structure. This approach aimed to provide a clear mental model of the ecosystem's organization and streamline the creation process.

The "Create Rule" screen presented a complex UI challenge due to its layered functionality. Our solution was a two-column layout (excluding navigation) that separated user selections on the left from the dynamic rule-building interface on the right. This pattern allowed the right column to adapt its states based on the left-column selections, providing crucial context. This design accommodated key elements such as:

• Disabled templates with a clear visual indication for enabling
• Tabbed navigation for efficient browsing of selectable items
• An embedded code editor for immediate rule testing
• A readily accessible library of sample code for quick copy-paste

By employing this layout, we aimed to provide users with a more organized and manageable experience when creating complex rules.