Designing a Palette Business Users Can Actually Use
The hardest interface in a self-service workflow tool is not the canvas – it is the short list of things a user can drag onto it.
The hardest interface in a self-service workflow tool is not the canvas – it is the short list of things a user can drag onto it.
An LLM that routes live cases cannot answer the only question an auditor will ask. Let the model author the process; never let it execute one.
Most hallucination in document extraction is a schema design failure. Stop parsing prose, put the meaning in the schema, and ask for provenance.
Six weeks to add a field is not a process maturity problem. It is an architectural boundary in the wrong place – and moving the graph from deployable artefact to application data is what fixes it.
There are always three versions of a business process: the documented one, the performed one, and the exception one. Interviewing the process owner captures only the first.
Give business users a workflow builder and the first question is what stops them building something broken. Training does not scale. A gate does.
The most useful thing to know about BAW, if you want a modern front end on it: a user task does not have to come with a user interface.
Workflow projects rarely overrun because the workflow was hard. They overrun because of the systems it has to talk to – and those are discovery failures with a long fuse.
What does your product do when the model is unavailable? If the answer is ‘a blank screen’, you have not built an AI feature – you have built a dependency.
If a step in your process is described with the word ‘until’, that is a message event with a correlation key and a timeout – not a fifteen-minute polling timer.