Innovating Enterprise UX Can Be Easier Than You Think

The Co-Design Method, Field-Tested

In the world of Enterprise software, innovating the user experience has never been easy. Outdated interfaces, endless development cycles, and limited budgets are familiar problems for anyone involved in designing or redesigning complex software.

Over the past few years, we at Moze have worked on numerous UX projects for Business and Enterprise software, collaborating with companies across various industries. From this experience, we developed our own method based on Co-Design.

A different — more effective and truly collaborative — way to tackle complexity, reduce the risk of ineffective solutions, and build only what is truly useful.

The secret? Move beyond the classic client-vendor dynamic and work side by side with both the client and the end users.

Why companies are pushed to rethinking the UX?

Let’s take a step back to understand the recurring reasons that push companies toward a UX redesign:

1. Loss of competitiveness: Customers begin to prefer alternatives with more modern interfaces, even if they are technically inferior.
2. Need for technological updates: The maintenance of obsolete code becomes the perfect opportunity to also review the user experience.
3. Operational inefficiencies: Fragmented and complex interfaces slow down daily work, leading to errors and user dissatisfaction.

The Limits of Traditional Processes

Traditional collaboration between business and design often involves months of planning and development, with limited client involvement and no real user engagement. The end result is frequently a visually refined interface that is ineffective in practice — often ignored by users or replaced with alternatives like Excel.

Our Proposal: The Co-Design Method

To overcome these limits, at Moze we’ve developed a radically different approach: Co-Design. This method creates a single operational team, composed of designers, company stakeholders, and end users, who actively collaborate in short, iterative cycles.

The process is structured into three key phases:

1. Shared Analysis

We begin with interviews of stakeholders and an analysis of existing features. Using visual tools such as User Story Mapping and Service Blueprint, we build a shared understanding of the software and business processes. User interviews help identify real problems and concrete opportunities.

Example: In a project for a vacation rental company, interviews revealed that operators often printed tables to annotate by hand. This clearly prioritized the features to develop.

2. Design System and Rapid Prototyping

We develop a minimal Design System aligned with the adopted technologies (e.g., React, Material UI), then move to prototyping. Interactive prototypes are tested with users in short cycles to quickly validate or revise design decisions.

The advantage? Fixing things at the prototype stage is cost-effective. Moreover, the design can evolve while development progresses in parallel.

3. Final Design and Handover

Once validation is complete, we produce the final design and support the development team during the handoff. Alongside the deliverables, we share a working method that enables the client’s team to independently evolve the software in the future.

A Flexible and Purposeful Approach

Co-Design adapts to the specific context: structured projects may require a fully documented Design System, while others benefit from a minimal version. Regardless, the guiding principle remains the same: do only what is needed, and do it well.