Consumer applications are designed under competitive pressure: make it confusing and people leave. Internal business systems have no such discipline. Staff cannot choose an alternative, so poor design does not show up as lost users. It shows up instead as data entry errors, long training periods, workarounds in spreadsheets, and a quiet resentment towards the IT department.
The design work that improves these systems is unfashionable. It is mostly about forms, tables and labels.
Optimise for the task done fifty times a day
Every operational system has one or two actions that dominate everything else. In a service desk it is logging a job. In a distribution business it is creating an order. In a clinic it is booking an appointment. Those actions deserve disproportionate attention.
Count the clicks and keystrokes required, then remove some. Can it be reached from anywhere without navigating a menu tree? Can it be completed with the keyboard alone? Are the fields in the order the information actually arrives in over the phone? Shaving fifteen seconds off a task performed two hundred times a week is a real saving, and the people doing it will notice immediately — the same adoption principle that decides whether a CRM survives its first year.
Write labels in the language of the business
Systems are often labelled with database terminology because that is what the developers were looking at. Users then have to translate mentally on every screen. If the company says “job sheet”, the button should not say “create work order record”. If the team distinguishes between an enquiry and a booking, your CRM or business system should not call both of them leads.
This costs nothing to get right at the start and is tedious to change later, since the vocabulary spreads into reports, training material and habits. It is worth spending an hour with the team writing down the words they use before any screens are designed.
Make tables work properly
Most time in business software is spent looking at lists, and most lists are badly built. The useful ones share a set of characteristics: sensible default sorting, filters that persist when you navigate away and come back, column choices the user controls, a genuinely useful search, and an export that produces something openable in a spreadsheet without repair.
Alignment matters more than people expect. Numbers should be right-aligned so they can be compared vertically, dates should use one unambiguous format throughout, and statuses should be distinguishable without relying on colour alone. Rows that all look identical are how the wrong record gets edited.
Prevent errors rather than reporting them
Validation that appears after a form is submitted, having cleared the other fields, is a small daily cruelty. Better to constrain the input in the first place: date pickers that reject impossible ranges, dropdowns instead of free text where a fixed list exists, automatic formatting for phone numbers and registration codes, duplicate warnings shown while typing a customer name.
Destructive actions need the opposite treatment — a moment of friction. A confirmation that names the specific record being deleted, and ideally an undo or an archive rather than a permanent removal. Most data loss in internal systems is not malicious; it is a tired person clicking the wrong row at half past five.
Design the dashboard for a decision
Dashboards accumulate charts because charts are easy to add. The result is a screen nobody looks at. A better starting question is what someone should do differently after seeing it: which jobs are overdue, which invoices need chasing, which stock lines need reordering this week.
Three numbers that trigger action are worth more than twelve that describe the past. If a chart has never changed anyone’s behaviour, it is decoration and can be removed.
None of this requires a visual redesign or a new framework. It requires watching the people who use the system for half a day, noting where they hesitate, sigh or reach for a notepad, and then fixing those specific things.
