Operational software often fails in the gap between a tidy screen and a messy real process. Work has exceptions, approvals, handoffs and evidence requirements. Hiding those realities does not simplify them; it pushes them into messages and spreadsheets.
Map decisions and handoffs
Discovery should identify who initiates work, what evidence is required, who can approve it, what can be corrected and what must remain immutable. The nouns become candidate records; the decisions and transitions become the workflow.
Use states with operational meaning
“Active” is rarely enough. Submitted, validated, approved, scheduled, completed and cancelled each imply different permissions and next actions. Define allowed transitions and preserve who made them.
Design the exception path early
The unusual path reveals the real model. Ask how duplicated submissions, missing references, rejected approvals and corrected records are handled. If the only answer is “an administrator edits the database,” the product is not finished.
Measure the process, not screen activity
Useful measures describe ageing work, bottlenecks, rework and outcomes. Page views do not explain whether an approval is stuck or an operator lacks the information to act.