A system can be entirely correct and still fail. The calculations are right, the integrations hold, the data is where it should be, and the team still keeps a spreadsheet on the side, because the software asks for eleven clicks to do the thing they do forty times a day.
The same applies to anything a customer touches. An app that wants a registration form, a verification code and a profile photo before it will show a single price gets deleted on the walk back to the car. Nobody files that as a bug. It arrives later as a number nobody can explain.
So we design the path before the screens. What is this person here to do, what is the shortest honest route to it, and what can be removed altogether. The screens are then built around that path rather than around the database tables, which is what happens by default when nobody is watching.
Two practical consequences follow. Interfaces have to hold their shape across the devices people actually own, from an ageing Android in a warehouse to whatever launched last month, without anybody maintaining a second design. And Arabic has to be a first-class layout rather than a mirrored afterthought: right to left, the numerals and dates a reader expects, and type that does not clip its own marks.
None of this is decoration. It is the difference between a system the company uses and a system the company works around, and the second is how the spreadsheets come back.