An ERP is not a database with a UI

When the screen mirrors the table

Many ERPs start from the database schema: a screen per table, a field per column. The result is technically correct and humanly exhausting, because users think in tasks, not tables.

A storekeeper does not want to “edit an item movement record”; they want to receive a shipment and check it matches.

Start from the question, not the field

Every screen answers one question. “What is waiting for my approval today?” makes a very different screen from “Purchase orders list”.

Rules and exceptions

Separate what happens 90% of the time from the exceptions. The common path should be the shortest; exceptions stay reachable without crowding it.

How to know it worked

Measure steps and task time before and after, and ask new staff: how many days until you worked without help?