Make the status describe an observable event
An AI interface should tell people what the system has prepared, what it is doing, what requires approval, and what has actually completed. Names, illustrations, button labels, and progress messages should support that understanding. A friendly product can still be precise about its capabilities.
Design Week's 7 September coverage of Public Address's CodeAI identity describes a deliberate choice to avoid presenting AI as sentient. That is a branding decision in an educational context. My application to commercial agents is analysis: evaluate whether the interface encourages users to assume more agency or certainty than the product provides.
Audit claims across the whole experience
Start with the landing page, onboarding, empty states, buttons, notifications, and error messages. A homepage might promise an autonomous assistant while the product only prepares drafts. A button labelled “Launch campaign” may only assemble a preview. That mismatch creates confusion even if each individual screen looks polished.
Write down every verb that implies an action: sends, books, monitors, checks, approves, publishes, or fixes. For each one, identify the actual operation, the evidence of completion, and the role of a person. If the team cannot agree on the meaning, the interface is not ready to communicate it confidently.
Separate preparation from execution
| Actual state | Example label | Evidence needed |
|---|---|---|
| A message has been generated | Draft ready for review | A saved draft exists |
| A person must decide | Approval required before sending | Destination and content are visible |
| The send request is underway | Sending | The operation has started |
| The provider confirms acceptance | Accepted by the email provider | The corresponding provider response |
These labels are illustrative. A provider accepting a request is different from a recipient reading the message. Choose the wording that matches your evidence rather than compressing several uncertain steps into “Done.”
Show what the person is approving
An approval screen should identify the action, destination, material changes, and relevant consequences. For a publishing workflow, show the selected account, final content, and intended timing. If those details change after review, require a fresh decision where appropriate rather than silently reusing the old approval.
Keep the primary action specific. “Approve this draft” and “Approve and send” mean different things. A designer should be able to explain what happens after the click without referring to a hidden technical workflow. The implementation must enforce the same boundary the interface describes.
Give uncertain outcomes their own state
Consider a fictional booking assistant that loses its connection after submitting a request. It cannot safely claim the booking failed merely because confirmation was not received. It also cannot claim success. Show that the outcome is unconfirmed, provide the available reference, and explain the next verification step.
This matters for retry behaviour. A second click could create a duplicate if the first action succeeded. The system should reconcile the result where possible and explain when a person needs to check. Good copy cannot compensate for missing execution safeguards, but it can avoid encouraging a dangerous assumption.
Test comprehension before polishing the personality
Show a few representative screens to someone unfamiliar with the product. Ask what has happened, what remains to be done, and who is responsible for the next step. Record their answers before explaining the intended meaning. Treat confusion as a design finding rather than a failure to read carefully.
Repeat the check for error states and mobile layouts. Important approval details should not disappear below a clipped panel or behind an ambiguous icon. Personality can remain in the illustrations and tone while action labels stay concrete.
JQ's agent architecture and web-design services connect capability with presentation. Start with one workflow and make its real boundaries understandable from the interface alone.
Link Map
Sources and editorial review
Sources reviewed on 21 September 2026. The practical workflows and illustrative examples are JQ AI SYSTEMS analysis unless explicitly attributed.
- Design Week: Public Address rebrands Code.org as CodeAI (7 September 2026; case coverage).