# Less is more: from psychology to technical writing
## Less is more: what Kahneman teaches us about technical writing
In [Thinking, Fast and Slow](https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow), Daniel Kahneman reveals something every technical writer should know:
**the mind prefers coherence over completeness.**
When we read, we constantly build quick mental models of what’s happening. If a message is clear, we trust it. If it’s cluttered or contradictory, we tune out, even if it’s accurate. That’s why *less is more* isn’t just an aesthetic principle. It’s a cognitive truth.
> **The core thesis:** Good documentation optimizes for coherence first, then reveals depth on demand. "Less" must mean less cognitive friction, not less useful information.
Good documentation aligns with human cognitive mechanics: fast intuitive orientation first, deliberate analytical depth second.
Good documentation works *with* human cognition, not against it. Minimalism, as refined by researchers like **Hans van der Meij** and **John Carroll**, is how we apply that truth in practice. For a deeper dive into how Systems 1 and 2 connect with affordance and DITA structure, see [Systems 1 and 2, affordance, and minimalism in technical writing](https://redaction-technique.org/systems-1-2-affordance-minimalism-technical-writing).
## How System 1 shapes the reader’s first impression
System 1 doesn’t read; it *glances*. It forms an evaluation in seconds:
* *“Can I find what I need?”*
* *“Does this look trustworthy?”*
At this stage, your job isn’t to explain: it’s to **make orientation effortless**.
### Practical design rules for System 1
1. **Short, task-based titles** signal immediate intent and scope.
2. **Action-first examples** invite immediate execution before theory:
```bash
deploy
```
*Deploy your app in one step.*
3. **White space and clear visual hierarchy** allow readers to parse document structure without conscious effort.
This satisfies System 1’s craving for coherence: a structure that *feels right* before it’s even fully analyzed. Applying [DITA information typing principles in Markdown](https://redaction-technique.org/strong-information-typing-without-xml-overhead) is one concrete way to build this kind of structured clarity.
---
## How System 2 demands depth and precision
Once the reader slows down, System 2 takes over. This is where **detail, accuracy, and logical order** matter. Readers start asking: *Why? What happens if I change this parameter?*
This is where **layering** and **progressive disclosure** protect clarity from collapsing into oversimplification:
| Layer | Cognitive Mode | Purpose |
|---|---|---|
| **Top layer** | System 1 (Orientation) | Clear action, task-based command, and core idea |
| **Middle layer** | Transition (Context) | Context, rationale, structure, and conceptual boundaries |
| **Deep layer** | System 2 (Analysis) | Full API references, edge cases, exceptions, and recovery |
By structuring documentation this way, you honor both readers:
* **System 1** gets a quick, coherent path to initial success.
* **System 2** finds the logical depth it needs when curiosity, edge cases, or errors kick in.
---
## Why “less” works: cognitive economy
Kahneman’s research on *cognitive load* explains why minimalism works so reliably in documentation:
* The mind is **energy-conserving by design**: it minimizes effort by simplifying.
* Every extra word or digressive paragraph is a **mental toll**.
* The easier it is to process information, the **more credible** it feels.
Concise documentation builds *trust* faster than exhaustive explanation. When readers grasp the core idea instantly, System 1 rewards them with confidence, and confidence sustains engagement.
> **The danger of unearned fluency:** Cognitive ease produces *the feeling of truth*, not truth itself. The same fluency that makes a correct instruction feel trustworthy makes an incorrect one feel trustworthy in exactly the same way: a clean, well-spaced page lowers the reader’s guard regardless of whether the content is right. Fluency is an editorial responsibility: make correct, complete, recoverable guidance easy to process—never borrow ease's credibility for content that hasn't earned it.
---
## When “less” becomes “not enough”
Minimalism fails when brevity removes essential context: System 1 says *“this feels easy,”* but System 2 hits a wall: *“wait, something’s missing.”*
Hans van der Meij’s minimalist heuristics prevent that breakdown by balancing brevity with completeness:
Give readers an actionable step immediately. Front-load commands and examples before theoretical background.
Ground explanations in genuine user workflows rather than abstract feature tours or synthetic scenarios.
Anticipate failure modes directly in the flow; show readers how to diagnose and recover when things break.
Design typography and structure for three simultaneous reading behaviors: skimming, studying, and reference lookup.
These principles ensure that *less* never becomes *less useful*.
---
## Designing documentation for two minds: an editing checklist
Kahneman gives us a practical lens to audit our documentation:
| Review Question | Cognitive Focus | Editing Check |
|---|---|---|
| Can readers grasp the goal instantly? | System 1 | **Simplify, rephrase, front-load** |
| Do explanations appear where curiosity peaks? | System 2 | **Layer detail, not overload it** |
| Can readers recover easily from mistakes? | Both | **Inline error recovery guidance** |
| Does the structure mirror real actions? | Both | **Task-based organization** |
If a page satisfies both systems, it’s not just readable: it’s *thinkable*.
---
## The deeper lesson: tell the right story
Kahneman’s insight was never about technical writing, but it might as well have been. A good story *feels true* because it’s easy to follow. Good documentation works the same way: it **feels usable** because it’s easy to think through.
Minimalism and layering simply translate cognitive psychology into structure and language. They ensure that “less is more” never becomes “less is not enough.” This approach pairs naturally with [flat-file content management](https://redaction-technique.org/manage-content-in-files-not-databases), where the simplicity of the toolchain itself supports cognitive economy.
## Summing up
## Related reading
- [The KISS principle of simplicity](https://docs.redaction-technique.org/en/costs/kiss-principle/) - the simplicity strategy behind these ideas, in depth.
## External sources
- [Kahneman: System 1 / System 2](https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow)
- [Layering / progressive disclosure](https://en.wikipedia.org/wiki/Progressive_disclosure)
- [Cognitive economy behind minimalism](https://en.wikipedia.org/wiki/Cognitive_load)
*Hero image: ["Misty morning"](https://www.flickr.com/photos/47515486@N05/45020012244) by [Hefin Owen](https://www.flickr.com/photos/47515486@N05/), licensed under [CC BY-SA 2.0](https://creativecommons.org/licenses/by-sa/2.0/).*
---
Source: https://redaction-technique.org/less-is-more-layering