Skip to content
Principles

The Operating Manual for Calm Work

April 28th, 2026

Calm work is not slow work. It is work where fewer things need to be re-decided.

Most teams lose speed in the invisible places: unclear ownership, scattered context, and decisions that were made once but never written down. The fix is not more process. The fix is a smaller operating manual.

Defaults beat reminders

A reminder asks people to remember the system. A default lets the system remember for them.

For a website, that means a shared layout, predictable metadata, one place for navigation, and content files that carry enough frontmatter to render everywhere. For a product team, it means a clear path from idea to decision to shipped change.

Notes are not reports

A good note does not prove that someone was busy. It preserves the reason a decision was made.

The most useful notes answer four questions:

  • What changed?
  • Why did it matter?
  • What tradeoff did we accept?
  • What should the next person check first?

Async only works with shape

Writing is not automatically better than chat. A vague written thread is still vague.

The shape matters: title, context, decision, evidence, next action. When that shape is consistent, people can enter the conversation later without restarting the whole thing.

The goal

The goal is not a perfectly documented company. The goal is fewer surprises.

Calm work comes from reducing the number of places where intent can disappear.



Related thinking

Continue through the same thinking system.