Overview

Nativo is an ERP system designed for industrial businesses and distributors, supporting operations across:

• inventory and stock management

• procurement and replenishment

• sales and point-of-sale

• production workflows

• administrative and financial processes

With over 30 years in the market, the product operated as a modular, on-premise system tailored to each client.

I joined the company to lead the UX definition of a new web-based platform, rethinking the product experience to align with modern usability standards and enable scalability.

The Problem

A powerful system that users struggled to use

Despite its functional depth, the system required up to 2 months of training for users to become operational.

This was due to fundamental UX issues:

Flat and unprioritized navigation

• All processes were presented at the same level

• Core workflows were not easily accessible

• High-frequency tasks competed with rarely used configurations

👉 Users had to know where to go, instead of being guided.

Chaotic and overloaded forms

• Forms exposed too much information at once

• Fields lacked clear grouping and hierarchy

• Validation rules were unclear or invisible

👉 Completing tasks required interpretation, not just execution.

No clear mental model

• Modules lacked a consistent structure

• Relationships between actions were unclear

• Navigation patterns were unpredictable

👉 Users couldn’t build intuition — only habits.

Dependency on memory

• Workflows relied on memorized paths

• Navigation became muscle memory

• New users struggled to replicate tasks

👉 The system rewarded experience, but punished newcomers.

Error-prone interactions

The structure led to frequent issues such as:

• incorrect selections in dense forms

• missed required fields

• navigation mistakes

• duplicated or misconfigured operations

Inverted priorities

Critical workflows were harder to access than advanced configurations.

Why this mattered

• Long onboarding times

• High dependency on support

• Difficulty acquiring new customers

• Risk of churn

👉 The system’s complexity became a barrier to growth.

Key Insight

The system didn’t fail بسبب lack of functionality —
it failed because users had to adapt to the system, instead of the system adapting to users.

System Redesign

From process-driven to object-oriented UX

The core transformation was shifting the system from:

👉 process-driven → object-oriented

Instead of asking:

“What do you want to do?”

The system now answers:

“What are you working with?”

Reframing around objects

I identified that most workflows revolved around core entities:

• clients

• products

• invoices

• orders

Solution

• Each object became a primary entry point

• Users could access lists, actions, and creation flows in one place

• Actions became contextual

👉 The system became explorable and predictable.

Introducing hierarchy

• Prioritized high-frequency workflows

• Separated operational actions from configurations

• Structured navigation layers

👉 Everyday tasks became immediately accessible.

Redesigning forms

Proactive forms (data creation)

• Structured for clarity

• Focused on correctness

• Clear validations

Reactive forms (transactions)

• Optimized for speed

• Guided completion

• Progress indicators

Improvements

• logical grouping of fields

• visible required inputs

• reduced cognitive load

New mental model

Everything is an object you can view, create, or act upon.

Each object includes:

• list view

• detail view

• contextual actions

• creation flow

👉 Users can transfer knowledge across the system.

Simplification through abstraction

Many “different” processes were actually variations of the same objects.

Result

• reduced fragmentation

• unified interactions

• simpler system without losing power

Impact & Results

Early validation

The redesign is currently being implemented as an MVP.

User feedback shows:

• improved clarity of system structure

• easier navigation

• reduced reliance on memorization

Onboarding improvements

• less intensive training required

• faster understanding of workflows

• reduced dependency on support

👉 The system began to teach itself through its structure.

Expected business impact

• reduced onboarding time

• lower support costs

• improved adoption

• decreased churn risk

My Role

• UX strategy and system restructuring

• definition of object-oriented interaction model

• end-to-end flows

• UI Kit and Design System

• documentation (ClickUp)

What I Learned

Structure defines usability

Usability is not a layer — it emerges from system organization.

Mental models scale

Designing around objects creates consistency and learnability.

Simplification requires abstraction

Reducing complexity is about unifying patterns, not removing features.

Legacy systems require paradigm shifts

Incremental improvements are not enough — real impact comes from redefining the system.

Closing

This project pushed me beyond interface design into system thinking.
By redefining the structure of the product, I helped transform a complex ERP into a more intuitive and scalable experience.