Self-assessment
Six questions before you rely on an AI result
Think of one thing you are about to let AI do or decide, and answer eighteen questions about that one thing.
Izam Ryan is a chartered accountant who builds with AI. He has spent years checking other people's figures on behalf of whoever was paying for the answer. More recently he has been directing AI models to design and ship working software. Both come down to the same habit: before relying on a result, ask how it was arrived at and who would answer for it.
CANDOR is the list he runs through before trusting an AI result. Consequence: should AI touch this at all? Accountability: who is answerable, and who can switch it off? Non-discrimination: is it fair to the people it affects? Data: can the inputs and the model be trusted? Operational integrity: is the system sound and behaving? Reperformance: can what it did be shown and repeated? (Re-perform: a second person can repeat the work and get the same answer.) Candor is named for it.
Pick one use. A price change, a letter to a customer, a shortlist of candidates, a set of figures for the board, a contract review. Answer every question about that one use, not about AI in general. The read-out does not say whether to go ahead. It shows which of the six questions could not yet be answered, which is usually the one worth asking.
The answers stay in this browser. Nothing is recorded anywhere unless the Send control at the foot of the read-out is pressed.
Section 1 of 6
Consequence: should AI touch this at all?
These tools are wrong some of the time by their nature, and that does not get fixed later. So the first question is not how good the tool is but what a wrong answer would cost and whether it could be taken back. This lens is inspired by the work of Alexandra Najdanovic at Aieutics (aieutics.com) on error tolerance and reversibility.
Section 2 of 6
Accountability: who is answerable, and who can switch it off?
A tool cannot be blamed and cannot be sacked. Somebody has to own the result as if they had produced it themselves, and that somebody has to be able to stop it.
Section 3 of 6
Non-discrimination: is it fair to the people it affects?
Anything that ranks, filters, prices or scores people can favour some and disadvantage others without anyone having decided that it should. The tool will not say so. Somebody has to look.
Section 4 of 6
Data: can the inputs and the model be trusted?
A result is only as good as what went in and what did the work on it. That means knowing what the tool was given, whether it was allowed to have it, and whose model is behind it.
Section 5 of 6
Operational integrity: is the system sound and behaving?
A tool that gave good answers in the demonstration is not the same as a tool that gives good answers on a Tuesday afternoon after its supplier has updated it. Soundness is shown by testing, watching and having a way out.
Section 6 of 6
Reperformance: can what it did be shown and repeated?
This is the one Izam cares about most. A result that cannot be traced back to its sources and arrived at again by someone else is a claim, not evidence. It is also the difference between a tool that saves time and a tool that has to be re-done by hand before anyone will act on it.
0 of 18 answered
Read-out
Six questions before you rely on an AI result
0%
What a board, a customer or a regulator would ask about this one use
Not answered
Nothing here is a verdict, and the read-out does not say whether to go ahead. A low score on one letter usually means a question that has never been asked rather than a tool that should not be used. The uses that hold up are rarely the ones with the best tool. They are the ones where somebody could show how the result was arrived at and who would answer for it.
If you would like Izam's view on what you have just answered, you are welcome to send it. A reply is a conversation, not advice.
Keep or share this read-out
The link carries the answers after the # so they stay in the browser and never reach a server.
Email my answers to Izam
Optional. This opens a draft email to hello@withcandor.dev in your own mail application, and nothing is sent until you send it from there. All four fields below can be left empty.
Please do not include personal details about other people. If you add your own contact details here, tick the box below.
If no email opens, write to hello@withcandor.dev with the results link above.