01 / AI & TECHNOLOGY
Begin with the consequence of being wrong
An AI output can be useful even when it needs revision, but the acceptable level of error depends on the task. A brainstorming suggestion is different from a statement used in a public policy, a customer message, or an important operational decision. Start by identifying what could happen if the answer is incorrect, incomplete, or misunderstood. This determines how much review is appropriate. The process should reflect the real consequence rather than treating every use as equally risky or equally harmless.
Define the result you expected before judging the result you received. A fluent answer can create a strong impression even when it misses the original question. Return to the task: what was requested, what evidence was available, and what constraints applied? Check whether the response addresses those elements. Separate writing quality from factual quality. Clear prose can make an error easier to believe, while awkward prose can still contain a correct and useful observation.
Pay attention to claims that require evidence. Names, dates, numbers, quotations, product capabilities, and statements about a specific organization should be checked against reliable sources. Do not assume that a citation is valid because it is formatted convincingly. Open the source when possible and inspect whether it supports the actual claim. If the output combines supplied facts with general explanation, make sure the boundary between them remains visible.
02 / AI & TECHNOLOGY
Review the answer in layers
First check correctness: are the central statements supported and internally consistent? Then check completeness: does the response include the qualifications, exceptions, and requested components that matter? Next check relevance: is the level of detail appropriate for the intended reader and decision? Finally check usability: can the result be applied without introducing confusion or extra unsupported assumptions? Reviewing in layers prevents visual polish from obscuring a more important defect.
Use small, independent checks for quantitative or structured work. Recalculate a representative figure, inspect units, check totals, or compare a record with its source. For code or a transformation, run a meaningful example and verify the result. A system's explanation of how it checked itself is not a substitute for external evidence. The goal is not to distrust every output; it is to close the loop between a plausible result and the real task.
Examine uncertainty language. A good answer should be appropriately confident about supported facts and appropriately cautious about missing information. Excessive hedging can make a straightforward result difficult to use, while unjustified certainty can hide a gap. Look for the reason behind the qualification. “This depends on the account's permissions” is informative. A vague statement that “anything is possible” does little to help the reader decide what to check next.
03 / AI & TECHNOLOGY
Use review findings to improve the workflow
When a defect appears, classify it before requesting another answer. The source may be incomplete, the instruction may be ambiguous, the model may have misunderstood a term, or the task may require access it does not have. Different causes need different repairs. Adding more words to the prompt will not solve missing evidence. Asking for a stronger tone will not solve an incorrect calculation. Identify the failure mechanism and change the relevant part of the process.
Preserve useful work while correcting the defect. If most of the answer is accurate, ask for the affected section to be revised with the missing evidence or constraint. Explain the observed issue concretely. A targeted correction is easier to verify than a completely new response that changes several unrelated elements. After revision, review the repaired section and any connected conclusions. A local change can affect the recommendation elsewhere in the document.
For repeated tasks, maintain a small evaluation set. Include representative inputs, known edge cases, and examples of previous failures. Keep the expected result focused on meaningful behavior rather than exact wording. Review the set when the workflow changes. This creates a practical memory of what needs checking and makes improvements easier to assess over time. A single successful answer does not establish dependable behavior across every future case.
Decide what to do with the result
The review can lead to acceptance, revision, additional evidence gathering, or rejection. Each is a legitimate outcome. Record the consequential uncertainty rather than smoothing it away. If the answer is used, make sure the person responsible for the decision understands what was checked and what remains unverified. Responsibility stays with the people and process that put the output into use.
For confirmed company and product information, visit AI & technology. Explore the rest of the reading room for more general guidance.