Workflow Systems
A case that passes through several hands needs more than a spreadsheet: a state, a responsible role, a deadline and a path for when nobody responds. That is exactly what is missing when a process has grown over the years.
A capability is a means. The linked areas describe what it is used for.
What specifically gets built.
Every line is a commitment about future work — none of it is a claim about completed projects.
The decisions behind it.
Categories rather than vendor names — which product is used depends on your existing systems.
- The process is built as a state machine, not as scattered conditions
- Deadlines are checked on a schedule, not by chasing
- Notification by email or push, depending on the role
What is not included.
So that no time in the intro call is spent on an expectation we do not meet anyway.
- No workflow without named responsibilities
- No fully automatic approval where there are legal consequences
- No mapping of a process nobody can explain
These eight capabilities are means, not offerings. Which of them are used follows from the process — not the other way round. If you are not sure which ones you need, that is the normal case and not a problem.