Make AI suggestions possible to review
A person can approve a fluent rewrite without noticing that it changes a commitment. Consider this constructed example: “We can send it on Friday if the review is complete” becomes “We will send it on Friday.” The second sentence is shorter, but the condition has disappeared.
A confirmation button alone does little to expose that change. The interface has to make the relevant comparison possible before the person acts on the result.
Design the decision the person is being asked to make
In the Simplify development build, the original selection stays in the document while the result appears beside it. Copying and replacing are separate actions. Replacement checks that the source text, range and editor still match before writing.
That protects the target of the action. It does not tell the person whether the new wording preserves the original meaning. The interface must also keep enough source context available to inspect names, amounts, qualifications and commitments.
For the Friday example, a useful comparison keeps the conditional clause visible. A product might highlight changed wording, but the highlight itself would still need review: detecting a text difference does not establish its significance.
Microsoft’s Guidelines for Human-AI Interaction include making unwanted assistance easy to dismiss and errors easy to correct. I apply that here by treating rejection and correction as ordinary paths through the interaction, alongside acceptance.
Put the control where the consequence changes
Generating a suggestion, replacing text in a document and sending that document have different consequences. Labels and feedback should make those differences understandable. “Done” is ambiguous if the person cannot tell whether a draft was created or a message was sent.
For a replacement, the review needs to identify the affected passage. For sending, it needs the destination and the material being sent. If the source changes while generation is running, the old approval no longer describes the current target. The product must resolve that mismatch before applying the suggestion.
More confirmations are not automatically more control. Asking the person to approve every harmless intermediate step can obscure the decision that matters. The design task is to put a clear, inspectable choice at the point where the system changes their work or acts beyond it.
A review step earns its place when the person can understand what will happen, decline it and recover from a mistake. The button is the final part of that design.