ContentsTap to jump to a section＋
- Map current work before discussing screens and features.
- Exceptions are where software projects often lose control; identify them early.
- Choose an operating measure to tell whether software actually improves work.
Understand the work before designing screens
Do not start with screen counts or reporting features. Follow one piece of work: who creates it, checks it, approves it, supplies data and stores the outcome. A rough map that matches reality is more useful than a polished feature list.
Four questions prevent a poor fit
Which step consumes time? Which exceptions send people back to spreadsheets or messages? What is the source of truth? Who may change, approve or see each part of the data?
Choose the measure before launch
Agree one operational measure before delivery: handling time, incomplete records, duplicate entry or approval wait. It shows whether the software helps work rather than simply moving it.
FAQ
Frequently asked questions
When should we buy off-the-shelf software?
When your workflow matches industry practice and can be configured within a product. Check exceptions, integrations and data carefully before signing.
When should we build custom software?
When a workflow is a real differentiator, needs specific integrations or off-the-shelf tools force workarounds. Consider long-term ownership and operation cost.
References
Sources used in this guide
We prioritise official guidance and primary technical sources. Visit each source for full context and the latest updates.