In IBM Maximo Application Suite (MAS) implementations, success is often measured by technical delivery: modules configured, integrations completed, and workflows deployed.  
‍

However, the true measure of value lies in how effectively end users can interact with, adopt, and benefit from the system. 
‍

User Experience (UX) is therefore not a “nice to have” layer added at the end of a project. It is a core design discipline that underpins every phase of a Maximo implementation, influencing everything from requirement quality to long-term user adoption.  
‍

This blog explores where UX fits within MAS implementations and how embedding UX thinking throughout the lifecycle leads to better outcomes for both users and organisations. 

The Reality of UX in Maximo Projects

Unlike standalone UX initiatives, Maximo projects rarely include UX as a clearly defined workstream. Budget constraints and lean delivery models often mean that UX must be implicitly woven into existing activities rather than formally scoped.  
‍

As a result, UX can be consciously embedded within three key pillars of delivery:  

• Requirements Discovery  

• User Story Definition  

• User Interface Design  
  ‍

This integrated approach ensures that UX is not treated as an afterthought, but as a continuous influence on shaping decisions across the lifecycle.

UX in Requirements Discovery: Understanding Real Work 

Moving Beyond Workshops

Traditional requirements workshops often focus on capturing what users say they need. However, UX-led discovery recognises a critical gap: Users cannot always articulate their real needs or describe how they actually work.  
‍

To address this, UX introduces a more human-centered approach:  

• Treat discovery as a conversation, not a checklist exercise  

• Focus on user goals, frustrations, and context  

• Understand what “good” looks like in day-to-day operations

The Power of Observation

One of the most effective (and often underused) UX techniques in Maximo projects is observing users in their actual environment.  
‍

Observation helps uncover:  

• Real workflows (not idealised ones)  

• Workarounds and manual processes  

• Environmental constraints (e.g. connectivity, mobility)  
  ‍

This reduces assumptions and improves requirement accuracy significantly.  

Eliminating Ambiguity

Ambiguous requirements are one of the leading causes of rework and user dissatisfaction in Maximo projects.  
‍

UX-driven practices help mitigate this by:  

• Continuously asking “why” to uncover true intent  

• Aligning on client-specific terminology (critical in Maximo contexts)  

• Validating assumptions early and often  
  ‍

For example, a term like “Site” may carry completely different meanings between Maximo’s data model and the client’s operational context, a small misunderstanding that can have large downstream impact.  

Document, Document, Document

UX is not only about design, but also about shared understanding.  
‍

Effective documentation ensures:  

• Decisions are traceable  

• Context is preserved  

• Stakeholders remain aligned  
  ‍

With modern tools, there is little excuse for losing critical insights gathered during discovery.  

UX in User Story Definition: Designing for Reality

Personas: Making Users Real

Personas are a foundational UX tool that bring user groups to life.  
‍

Rather than generic roles like “Planner” or “Technician,” well-defined personas capture:  

• Goals and motivations  

• Pain points  

• Behavioural patterns  

• Working environment  
  ‍

This allows teams to design solutions that reflect real user needs rather than assumptions.  

From User Stories to Usable Solutions

Traditional user stories often focus on functionality:  “As a technician, I want to update work order status…”
‍

While technically correct, this lacks usability context.  
‍

Expanded user stories add critical dimensions:  

• Where the task is performed (shop floor vs office)  

• How it is performed (mobile device, gloves, limited time)  

• Constraints (connectivity, noise, usability friction)  
  ‍

This shifts delivery from:  

• Building features to Delivering usable solutions  

• System-centric thinking to User-centric design  
  ‍

Expanded stories create a direct bridge between requirements and UI design decisions.

UX in User Interface Design: Enabling Adoption

Designing Within Constraints

Maximo provides a structured UI framework, which means not all aspects of UX are fully customisable.  
‍

However, there is still significant influence over:  

• Application layout  

• Navigation flow  

• Field placement  

• Button positioning  

• Data presentation  
  ‍

Le défi est d'optimiser l'expérience dans ces contraintes, en adaptant l'interface à la façon de travailler des utilisateurs.

L'UX comme discipline continue

Ce qu'il faut retenir avant tout, c'est que l'UX n'est pas une phase, elle est un fil conducteur continu tout au long du cycle de vie du projet.
‍

Dans les implémentations Maximo, l'UX :  

• Débute lors de la phase de découverte  

• Évolue au fil des exigences et de la conception  

• Se poursuit lors des tests et de l'affinage  

• Se prolonge par l'amélioration continue après le déploiement
  

Considérer l'UX comme une discipline continue garantit que le système évolue parallèlement aux besoins des utilisateurs, plutôt que de devenir rigide et obsolète.

L'importance de l'UX pour les résultats commerciaux

Une UX de qualité offre des avantages commerciaux concrets :  

• Adoption accrue par les utilisateurs  

• Réduction de l'effort de formation  

• Amélioration de la qualité des données  

• Efficacité opérationnelle accrue  

• Meilleure satisfaction des parties prenantes  
  ‍

À l'inverse, une mauvaise UX entraîne souvent :  

• Solutions de contournement (par ex. dépendance à Excel)  

• Faible confiance dans le système  

• Risques de conformité  

• ROI réduit  
  ‍

En fin de compte, le succès d'une implémentation Maximo est indissociable de la qualité de son expérience utilisateur.  

Réflexions finales

Pour les architectes de solutions et les équipes de livraison, le défi n'est pas d'inclure l'UX, mais comment l'intégrer efficacement au sein des structures de livraison existantes.
‍

Les projets Maximo les plus réussis sont ceux où l'UX est :  

• Prise en compte dès le début  

• Intégrée tout au long  

• Portée par toute l'équipe de livraison  
  ‍

En passant d'une mentalité axée sur le système à une approche centrée sur l'utilisateur, les organisations peuvent aller au-delà du simple déploiement de Maximo, et plutôt fournir des solutions qui soutiennent véritablement les personnes qui en dépendent au quotidien.