Design · Essays · 3 min
What an interface needs to explain
Every button, form and error message makes a small promise. Reviewing those promises reveals problems that a screenshot cannot show.
Read the essayOn web design, artificial intelligence and publishing.
Design · Essays · 3 min
Every button, form and error message makes a small promise. Reviewing those promises reveals problems that a screenshot cannot show.
Read the essayAI · Essays · 4 min
A chat application can use tools, and a custom system can be small. The choice depends on the operations you need and who will be responsible for them.
Read the essayAI · Essays · 4 min
Reading information, preparing a change and executing it require different permissions. Review needs to check those boundaries where operations take effect.
Read the essayContent · Essays · 4 min
Every article adds content that someone will need to maintain. A short editorial record and a review process help decide what to publish, update or retire.
Read the essayDesign · Notes · 2 min
The opening screen has limited space. The size of each element should help people recognise the offer and decide whether to read further.
Read the noteDesign · Notes · 2 min
A colour or spacing value preserves the result. A short note preserves the reasoning for the next time it needs to change.
Read the noteAI · Notes · 2 min
A generic confirmation asks people to rely on a summary. Reviewing an action requires the actual result and a way to correct it before execution.
Read the noteContent · Notes · 2 min
A handover needs to explain how the website is changed and who looks after each part. That agreement prevents a small update from starting with a search for access.
Read the noteDesign · Films
Size, position and space give the title, explanation and next step different roles.
Three messages compete. Equal sizes do not explain what to read first. Offer, details and contact initially have the same size and weight. None establishes a reading entry point.
The offer takes the first level. Details expand what the title already makes understandable. Offer grows larger. Details moves to a second level and Contact keeps a separate position.
Space connects the parts. Distance groups the explanation and distinguishes the next step. A region groups Offer with Details. Contact is separated as the next step without competing with the title.
This video could not load. You can read its complete visual story above.
AI · Films
A boundary separates granted capabilities from actions that need another permission.
Define the capabilities. Reading and preparing are different permissions from sending or deleting. Read and Prepare sit inside an authorised region. Send and Delete remain outside it.
The proposal reaches the boundary. Having a result ready does not grant permission to execute it. A marker moves from Prepare to the boundary. It stops before Send.
Changing permission requires review. A person can authorise, request changes or stop the process. Three decisions appear at the boundary: Authorise, Revise and Stop. Only Authorise connects to the action.
This video could not load. You can read its complete visual story above.
Content · Films
Content returns to review when information changes. Updating and archiving are different outcomes.
Writing has a destination. Review connects a draft with publication. Write connects to Review and then Publish. The path remains open after publication.
Information changes. Published content returns to review when it needs updating. A return arrow connects Publish to Update and takes content back to Review. The path forms a cycle.
Sometimes archiving is appropriate. An outdated piece can leave the publishing path. Review branches into two paths: update and publish again, or archive and leave the cycle.
This video could not load. You can read its complete visual story above.
Try another topic or return to the complete archive.