Our approach
Software should help people do their work well. That means respecting their time, being honest about what is known and keeping consequential decisions accountable.
Good design helps someone understand a request, find the right context and take the next appropriate step. Features should earn their place by making that work easier.
We favour clear language, sensible defaults and a short route through everyday tasks.
A label should reflect something that can be explained. Keep the original communication, record the action, show the observation and acknowledge what is not yet known.
History should help the next person understand what happened, without reconstructing it from memory.
A failed connection should have a considered outcome. Where a local fallback can safely preserve useful work, its source and age need to remain visible.
A fallback is a fallback. It should never quietly present old information as current truth.
Automation should carry out an understood task within agreed limits. People need to know what it can do, why it acted and what happened afterwards.
The level of autonomy should be appropriate to the task and the authority granted.
Business systems have their own responsibilities. Useful integration respects those boundaries and exchanges the facts needed for the work.
LEGEND should keep its operational purpose, whether or not an external system participates.
The question behind each design decision
If the answer is unclear, the design needs more work.
Discuss your requirements
Discuss the practical requirements of your team and how our approach could support them.
