The twelve principles of Intelligence Age design

The Intelligence Age asks product builders to design another floor on top of the foundations of usability, accessibility, and human-centred design. That floor is built from memory instead of state, intent instead of workflows, reasoning instead of automation, collaboration instead of execution, and intelligence instead of interface alone.

The twelve principles below are a compact reading of that philosophy. They do not replace good visual design. They name what changes when software begins to think.

Reducing cognitive load

1. Low-cognitive first draft. Eliminate the blank page. Begin with thoughtful work people can revise.
2. Point & fix. Prefer surgical editing over repetitive workflows. Pointing becomes a command language.
3. Intent over instructions. People express outcomes, products infer the how from the what.
4. Conversation over configuration. Natural language replaces menus, settings, and forms as the primary way to express intent.

Software that knows you

5. Context is a feature. Context is no longer supporting information, it is a core product capability.
6. Memory is part of UX. Every interaction should improve future interactions. Software becomes personal rather than stateless.

Intelligence as the interface

7. Recommend, don’t respond. Guide decisions rather than merely answer questions.
8. The devil is in the TLDR. Intelligence is measured by how effectively it reduces cognitive effort, not by how much it generates.
9. Visible thinking. Trust grows when software reveals its reasoning instead of hiding it.
10. Intelligence over aesthetics. Intelligence becomes a primary driver of delight, visual polish is expected rather than differentiating.

A new interaction model

11. Language over layout. Language becomes the universal interaction layer across text, voice, images, documents, and environments.
12. Co-pilot the decision. The future lies in collaborative decision-making, balancing human judgment with machine intelligence.

How this meets Thoughtware

These principles describe how products should feel and behave for people. Thoughtware describes how the software underneath should be structured so those behaviours can be located, evaluated, and improved. Intent over instructions needs cognitive units that interpret, memory as UX needs knowledge and experience with approval, visible thinking needs retrospection and evaluable steps.

Design the experience with the twelve. Architect the system so each judgment has a home.