Ten short statements about how the job runs, where the data lives, and who owns the change. Answer them honestly and you'll get a straight read: fix the process first, book a Workflow Review, or go straight to a build.
Everything runs in your browser. Nothing is sent anywhere and there's no email box.
Ten statements, each worth 0 to 3. The bands are my own judgement from the Workflow Reviews I run, not a published benchmark. The score only exists in this page's URL if you share it, nothing is stored or sent anywhere.
Ten statements can't see your business. Here's where the score can mislead you.
It's one person's guess, not a team vote. The owner and the person actually doing the invoicing often score the same statement differently. If you can, get someone else in the business to run it too and compare answers.
One statement scores backwards on purpose. "People type the same thing into two places" is the one question where always is the bad answer, so answering never scores full marks there. Every other statement works the normal way round: always is good.
A high score doesn't mean the timing is right. The scorecard tells you whether the business is ready. It doesn't know if this is the month you can afford to spend on it, or whether you're mid-way through something else that needs finishing first.
Ten statements, each worth 0 to 3: never, sometimes, mostly, always. Add them up and you get a score out of 30. Below 14, fix the process before you spend money on anything else. From 14 to 23, there's enough here to justify a paid Workflow Review. From 24, the process, the data and the people are lined up, and a build is worth pricing.
What these bands are, and aren't. They're my own judgement from scoping work, not a published benchmark or an industry standard. No dataset sits behind the numbers, and I haven't found one worth citing.
Automation readiness scorecard, Kove. kove.nz/automation-readiness-scorecard
Ten statements about the process, the data and the people, each scored 0 to 3: never, sometimes, mostly, always. Add them up for a score out of 30. One statement, about typing the same thing into two places, scores backwards, because always is the bad answer there.
Below 14, fix the process before you spend money on anything else. From 14 to 23, there is enough here to justify a paid Workflow Review. From 24, the process, the data and the people are lined up, and a build is worth pricing.
No. The bands are my own judgement from the Workflow Reviews I have run, not a published benchmark. Treat the number as a starting conversation, not a verdict.
Nothing bad. It is a common outcome, and it just means the process needs to settle before a build would hold up. Read what a Workflow Review actually gets you, then come back once a few of the low-scoring statements have moved.