The checklist
Tick every statement that is true today. Be strict: “we could probably find out” counts as no.
Start with a free fit call. Twenty minutes to find the workflow worth fixing first, or to hear that it’s worth waiting. Book a fit call →
What your score means
- 8–10: Ready. A Workflow Diagnostic will produce a baseline and a fixed-price build quote in ten business days.
- 5–7: Close. The gaps are usually access, examples or ownership, and a Diagnostic closes them as part of the work.
- 0–4: Start smaller. A free 20-minute fit call will find the workflow worth fixing first, or tell you to wait.
Why these ten
Each item maps to a failure we see in SI projects. No owner means no decisions. No examples means no test. No exception path means the system guesses when it should stop. No approver means consequential actions happen without a person. No owner after launch means quality quietly degrades when models, prompts or data change.
The items you can’t tick are not reasons to give up. They are the first things a good diagnostic should resolve, in writing, before anyone quotes a build.
What to write down before release
When a workflow is built, keep an acceptance record. It is the difference between “the demo looked good” and a release decision you can defend:
- Component and version, and its input/output contract
- Test set and test date
- Passed cases and failed cases
- Known limits that remain unresolved
- Release owner and their decision
- Operating owner after launch
An engineering version of this checklist is available as a Markdown file you can copy into your own documentation.