Less is more: from psychology to technical writing

Less is more: what Kahneman teaches us about technical writing

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

System 1 and System 2: the two readers in every mind

Kahneman describes two distinct modes of thinking that operate in every reader:

When readers open documentation, they start in System 1. They’re skimming, looking for quick cues: headings, examples, or one command to copy and run. If something breaks or feels unclear, System 2 wakes up to analyze, compare, or debug.

Most users don’t read documentation linearly; they scan, act, and adjust:

Minimalist writing feels natural because it aligns directly with this non-linear rhythm.

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:

   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 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:

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:

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:

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, where the simplicity of the toolchain itself supports cognitive economy.

Summing up

Related reading

• The KISS principle of simplicity — the simplicity strategy behind these ideas, in depth.

External sources

• Kahneman: System 1 / System 2
• Layering / progressive disclosure
• Cognitive economy behind minimalism