Concept
Designing
How products should feel when software participates in judgment.
Cover for Designing19 concepts in this section.
All sections
Illustration for Intelligence-native productsProducts built around judgment
10 minIntelligence-native products
When interpretation, memory, recommendation, and correction sit inside the primary workflow, products meet Intelligence Age expectations. This page contrasts bolt-on chat with products redesigned around outcomes and judgment chains.
Illustration for The rise of ThoughtwareFrom demos to governed systems
9 minThe rise of Thoughtware
Intelligence-native products need architectural discipline beyond UX trends. Thoughtware rises as category and product craft co-evolve in a market full of fluent demos and thin structure.
Illustration for Consumers direct intelligenceUsers meet capability directly
9 minConsumers direct intelligence
People express outcomes in household language, guide and review results, and remain responsible where authority requires it. Products must channel that direction into working state, not one-shot prompts.
Illustration for Products judged like peopleTrust like a colleague
9 minProducts judged like people
Users describe intelligent software with relational verbs like understanding and forgetting. Design for those judgments explicitly. They map to memory, posture, and collaboration architecture.
Illustration for Low-cognitive first draftReduce load on first pass
9 minLow-cognitive first draft
Start with a thoughtful, revisable plan, not a blank page or infinite chat. The household corrects while the product opens the work.
Illustration for Point and fixRepair in place
9 minPoint and fix
Select what is wrong on the artifact and describe the repair. Local patches preserve accepted work. Regenerating the whole plan because one evening failed is a posture failure.
Illustration for Lead with intent, not instruction listsIntent over instructions
9 minLead with intent, not instruction lists
Users state outcomes in household language. The product compiles intent into working state and plans, not twelve form fields or a feature map users must learn first.
Illustration for Conversation before configuration panelsConversation over configuration
8 minConversation before configuration panels
Structured conversation replaces dense settings for everyday intent. Conversation must compile to inspectable state, not remain an ephemeral transcript.
Illustration for Structured conversation becomes stateChat that updates working state
9 minStructured conversation becomes state
Each conversational turn should update working state, context, or proposed knowledge, not append a transcript line alone. Show the state diff after one message.
Illustration for Context is a featureSituation is part of the product
9 minContext is a feature
What the system knows for this run, from calendar, selection, and endorsed knowledge, is curated and designed, not accidental prompt stuffing.
Illustration for Memory is part of UXRecall shapes experience
11 minMemory is part of UX
Users need visibility and control over what is remembered, endorsed, and temporary. Memory surfaces are product surfaces, not backend-only storage.
Illustration for Recommend, don't only respondPropose, do not only reply
10 minRecommend, don't only respond
Proactive recommendation beats passive Q&A. After critique, propose a substitution, not idle chat asking if you need anything else.
Illustration for What a summary leaves outThe devil is in the TL.DR
10 minWhat a summary leaves out
Aggressive summarisation hides assumptions and tradeoffs users must see. Summaries must preserve material conflicts, sources, and approval needs, not only read well.
Illustration for Visible thinkingShow grounds, not theatre
10 minVisible thinking
Show assumptions, active constraints, and reasons where users need to trust, fix, or approve, not chain-of-thought theatre, but contestable rationale.
Illustration for Intelligence before surface polishIntelligence over aesthetics
10 minIntelligence before surface polish
When tradeoffs collide, conduct, memory, and correction outrank visual novelty. A beautiful calendar that silently violates allergy loses to a plain list with explicit checks passed.
Illustration for Language before layout chromeLanguage over layout
10 minLanguage before layout chrome
In intelligence-native products, utterance, feedback, and correction language come first. Layout serves plan inspection and point-and-fix, not primary data entry.
Illustration for Co-pilot the decisionAssist the call, not the chat
11 minCo-pilot the decision
Augment human-led judgments with options, rationale, and prep, not auto-deciding contested or authoritative choices. Decision ownership stays visible.
Illustration for Beyond the interfaceArchitecture survives the UI
10 minBeyond the interface
Product quality lives in loop behaviour, memory discipline, eval health, and authority respect across weeks, not in one demo session UI.
Illustration for Designing for the Intelligence AgeEighteen chapters in one map
8 minDesigning for the Intelligence Age
Twelve product principles, intent, conversation-to-state, memory UX, recommendation, transparency, indexed here with one Meal Companion line each. Depth lives in linked notes. read this capstone last in the Designing track.