AI readiness assessment

0 of 15 answered

1. 01 / Data readiness

   Where does the data this workflow depends on live today?

   Mostly in people's heads and email threadsSpread across spreadsheets and shared drivesIn a few systems of record with some manual copiesIn one or two systems of record that stay current

2. 02 / Data readiness

   How consistent is the format of the records involved?

   Every record looks differentLoose conventions, frequent exceptionsA standard format with known exceptionsA validated format enforced at entry

3. 03 / Data readiness

   Can someone on your team export a full year of this data this week?

   No, and nobody is sure where it all isOnly in pieces, with manual stitchingYes, with a day or two of effortYes, on demand and already scheduled

4. 04 / Process maturity

   Is the workflow written down anywhere?

   No written version existsAn outdated document existsA current document covers the main pathA current document covers the main path and the exceptions

5. 05 / Process maturity

   How often do two people handle the same case differently?

   Constantly, judgment drives every caseOften, on anything non-routineOccasionally, on edge casesRarely, the rules are explicit

6. 06 / Process maturity

   Do you know the current volume and the current cycle time?

   Neither number is trackedOne number is roughly knownBoth numbers are estimatedBoth numbers are measured and reported

7. 07 / Process maturity

   What happens today when a case fails or stalls?

   It surfaces when a customer complainsSomeone notices during a periodic reviewA person owns a manual exception queueA defined escalation path catches it quickly

8. 08 / Technical capability

   Do the systems involved expose an API or a supported integration?

   No, or the vendor blocks accessUnknown, nobody has checkedSome of them doAll of the critical ones do

9. 09 / Technical capability

   Who can grant integration credentials for those systems?

   Nobody identifiedAn outside vendor controls accessAn internal owner exists but is stretched thinA named internal owner can grant access quickly

10. 10 / Technical capability

    Who will maintain the automation after launch?

    UndecidedWhoever has time that monthAn internal team, with outside help expectedA named owner or a managed operations agreement

11. 11 / Technical capability

    What are your security and compliance requirements for this data?

    Unclear, and no one owns the answerKnown informally, never documentedDocumented, with review needed before launchDocumented, with an approval path already defined

12. 12 / Organizational buy-in

    Is there a named executive sponsor for this work?

    NoInterest exists but nobody owns itA sponsor exists, budget is unconfirmedA sponsor exists with budget authority

13. 13 / Organizational buy-in

    How does the team doing this work today feel about automating it?

    Actively opposedUnaware the project is being consideredOpen, with concerns about accuracyAsking for it directly

14. 14 / Organizational buy-in

    Has a budget range been discussed internally?

    No conversation yetDiscussed with no number attachedA rough range existsAn approved range exists for this fiscal period

15. 15 / Organizational buy-in

    What does success look like to the sponsor?

    Not definedDescribed in general termsOne measurable target is namedMeasurable targets with a baseline already captured

No email is required. The score is produced in your browser from the answers you pick.