MiCollab

Senior UX Designer at Mitel

MiCollab is an enterprise UCaaS platform spanning telephony, messaging, and video across web, desktop, and mobile. I led the mobile and desktop user experience, defining cross-platform interaction patterns and key product decisions to create a consistent experience that helped enterprise teams communicate seamlessly across devices.

Role
Senior UX Designer

Focus
Enterprise UX · Interaction Design · Cross-platform Design · Product Strategy

Platforms
Web · Desktop · Mobile

The Problem

Mobile had outgrown its role as a companion experience.

The desktop product had historically been Mitel’s primary experience, while mobile was designed by a separate team as a complementary tool. As mobile adoption grew and users increasingly relied on it as a primary product, the two experiences became noticeably inconsistent in both functionality and interaction patterns.

The challenge was to bring mobile and desktop into closer alignment without simply replicating one platform on the other.

Small annotations:

  • Different navigation patterns

  • Different feature depth

  • Different interaction behaviors

The Design Question

How might we create a consistent mobile and desktop experience while still designing appropriately for the strengths and constraints of each platform?

My Approach

I began by evaluating the desktop experience to identify the workflows, features, and interaction patterns users relied on most. I then compared those against the mobile product to understand what was missing, what was already working well, and which desktop patterns actually made sense in a mobile context.

Show:

  • key tasks

  • desktop behaviors

  • mobile gaps

  • patterns worth preserving

  • patterns that needed to adapt

From there, I defined a cross-platform direction that preserved the strengths of each experience, aligned the core interaction model, and created a foundation that could scale as the product evolved.

Key Decisions

01. Preserve the core calling experience while designing for mobile first.

Telephony was the primary use case, so the goal was to make calling feel familiar to existing desktop users while taking advantage of native mobile behaviors.

Rather than copying the desktop experience, I adapted the core calling model to mobile conventions and used those learnings to identify opportunities that could improve the desktop experience as well.

Priority

  1. Calling

  2. Messaging

  3. Video

Why it mattered

A large portion of users already understood the desktop product and its interaction patterns. Those same users were increasingly using mobile devices, so the experience needed to feel familiar without ignoring the conventions of each platform.

The goal was not to make mobile and desktop identical. It was to make them feel like the same product. Mitel

02. Support third-party integrations without disrupting existing workflows.

Many enterprise customers already relied on tools such as Salesforce, Zoom, and Tableau as part of their daily workflows.

Rather than forcing users to leave those tools behind, the goal was to make MiCollab work alongside them and provide a consistent integration experience across desktop and mobile. Mitel

Small callouts:

  • Same workflow

  • Consistent entry point

  • Platform-appropriate interaction

Why it mattered

In enterprise products, the people using the software are often different from the people purchasing it. For large organizations, introducing a new platform cannot disrupt established workflows or reduce productivity.

The experience needed to fit naturally into the tools employees already used, maintain consistency across devices, and ideally improve productivity rather than create additional friction.

03. Create a shared design system with accessibility and localization built in.

As we brought fragmented experiences into a more unified product, I worked closely with front-end developers to establish a shared component library and design system.

The goal was not only to create visual consistency, but also to build accessibility and localization into the system from the beginning. Mitel

Show:

  • components

  • states

  • typography

  • spacing

  • localization example

  • accessibility considerations

Why it mattered

MiCollab was used across multiple international markets, including Germany, France, and Greece, so the product needed to support different languages, content lengths, and accessibility requirements without breaking the experience.

At the same time, a shared design system gave design and engineering a common language, reduced inconsistency, and created a foundation that could make future product development faster and more scalable.

The Solution

A more cohesive cross-platform experience built to scale.

I helped evolve MiCollab from a desktop-led product with a complementary mobile experience into a more unified system across desktop and mobile.

Core interactions were aligned around the same mental model, while each platform preserved the behaviors that made sense for its context. Mitel

The result was a more consistent experience across calling, messaging, integrations, and shared UI patterns, supported by a reusable design system that made future product development more efficient and easier to scale. Mitel

Consistent core interactions

Calling and messaging followed the same mental model across devices. Mitel

Platform-appropriate patterns

Mobile behaviors were adapted to native conventions instead of copied directly from desktop. Mitel

Integrated workflows

Third-party tools fit into the product without forcing users to change how they worked. Mitel

Shared design foundation

Reusable components helped design and engineering work from the same system.

Impact

A stronger product experience and a more scalable foundation.

Mobile adoption

Usage increased as mobile became a more complete and reliable extension of the core product. Mitel

Enterprise readiness

Accessibility and localization expanded the product’s ability to serve global customers and support larger sales opportunities. Mitel

Ecosystem growth

Third-party integrations, including Zoom, helped MiCollab fit more naturally into existing enterprise workflows. Mitel

Scalable design foundation

The design library and shared design language improved consistency and gave teams a reusable system for future product development.

Reflection

The biggest lesson was that consistency is not about making screens look the same — it’s about creating familiar patterns and behaviors across the product.

A thoughtful design system, built with accessibility and localization from the start, can improve team alignment, speed, and long-term product consistency.