# 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.

![Colorful Toothed Wheels](https://redaction-technique.org/images/blog/less-is-more-layering-large.webp)

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/blog/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 a judgment 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**.

* **Short, task-based titles** signal clarity.
* **Action-first examples** invite success:

  ```bash
  deploy
  ```

  *Deploy your app in one step.*
* **White space and hierarchy** help readers spot structure without thinking.

This satisfies System 1’s craving for coherence: a story that *feels right* before it’s even fully understood. Applying [DITA information typing principles in Markdown](https://redaction-technique.org/blog/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?*

This is where **layering** and **progressive disclosure** protect your clarity from oversimplification.

| Layer            | Cognitive Mode | Purpose                                 |
| ---------------- | -------------- | --------------------------------------- |
| **Top layer**    | System 1       | Clear action and core idea              |
| **Middle layer** | Transition     | Context, rationale, structure           |
| **Deep layer**   | System 2       | Full references, exceptions, edge cases |

By structuring docs this way, you honor both readers:

* System 1 gets a quick, coherent path to success.
* System 2 finds the logical depth it needs when curiosity or confusion kicks in.

---

## Why “less” works: cognitive economy

Kahneman’s research on *cognitive load* explains why minimalism works so reliably in documentation:

* The mind is **lazy by design**: it conserves energy by simplifying.
* Every extra word or paragraph is a **mental toll**.
* The easier it is to process information, the **more credible** it feels.

That’s why concise documentation builds *trust* faster than exhaustive explanation.
When readers can grasp the core idea instantly, their System 1 rewards them with confidence, and confidence keeps them engaged.

There’s a sharp edge to this that Kahneman is careful about and technical writers should be too: cognitive ease produces *the feeling of truth*, not truth. The same fluency that makes a correct instruction feel trustworthy makes an incorrect one feel trustworthy in exactly the same way: a clean, confident, well-spaced page lowers the reader’s guard regardless of whether the content is right. So fluency is a responsibility, not just a goal. Minimalism that makes a wrong or incomplete procedure *feel* effortless is more dangerous than a clumsy one, because the reader has no friction to warn them. The aim is to make correct, complete, recoverable guidance easy to process - never to borrow ease's credibility for content that hasn't earned it.

---

## When “less” becomes “not enough”

Of course, minimalism can go too far.
If the main layer omits essential context, readers hit cognitive dissonance: System 1 says “this feels easy,” but System 2 says “wait, something’s missing.”

Hans van der Meij’s minimalist heuristics prevent that collapse:

1. **Action first**: give readers something they can do immediately.
2. **Anchor in real tasks**: use examples drawn from genuine workflows.
3. **Support error recovery**: anticipate mistakes; show how to fix them fast.
4. **Write for multiple modes of reading**: skim, study, or locate.

These principles ensure *less* never becomes *less useful*.

---

## Designing documentation for two minds

Kahneman gives us a lens to test our docs:

| 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 support           |
| 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 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 that 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/blog/manage-content-in-files-not-databases), where the simplicity of the toolchain itself supports cognitive economy.

---

## TL;DR for technical writers

* **System 1 reads fast:** make your core message visible, actionable, and coherent.
* **System 2 thinks deeply:** provide depth and rationale through layering.
* **Minimalism works** because it matches how humans manage cognitive load.
* The goal isn’t to say less. It’s to make *thinking effortless*.

---

## 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)

<small>*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/).*</small>

---

Source: https://redaction-technique.org/blog/less-is-more-layering