Metadata before screens
A polished interface cannot compensate for a weak underlying model of the records, relationships, rules and responsibilities in an operational process.
10 August 2026
Operational software discussions often begin with screens.
What should the form look like? Which fields should be visible? What dashboard should management see?
Those questions matter, but they are downstream of a more important one: what does the system actually need to represent?
Make the operating structure explicit
Before the interface, define the entities, identifiers, relationships, workflow states, responsibilities, evidence and rules.
Once those are explicit, different interfaces can be built for different roles and devices without changing the meaning of the underlying records.
A good screen can simplify a strong model. It cannot rescue a weak one.