The Less Crazy Manifesto

People aren't crazy.

The world has simply become harder to navigate.

Information moves faster than our ability to process it. Technology evolves faster than institutions can adapt. Systems compete for attention, not understanding.

The result is predictable.

People feel lost. Untethered. Confused. Sometimes angry.

Not because they are broken.

Because the environment is overwhelming.

The Signal Problem

Human beings evolved to process small groups, direct conversations, and tangible problems.

The modern environment is something else entirely.

Every day we encounter thousands of messages, competing narratives, constant alerts, systems demanding attention.

The signal-to-noise ratio collapses.

When that happens, decision-making collapses with it.

People begin to rely on shortcuts:

A or B
Yes or No
Us or Them

This isn't stupidity. It's cognitive overload.

Structural Confusion

Much of the modern world is built to maximize engagement, not clarity.

Algorithms reward attention. Platforms reward outrage. Institutions reward complexity.

When systems become opaque, people lose trust in them.

When people lose trust, they become angry.

When anger replaces understanding, societies fracture.

The Response

The answer is not to remove complexity.

The world is complex.

The answer is to build systems that make complexity legible.

Systems that help people understand problems, see tradeoffs, make decisions, and act with confidence.

Clarity restores agency.

Engineering for Sanity

This idea applies everywhere. In technology. In organizations. In public life.

Good systems reduce chaos. Bad systems amplify it.

When systems are designed well:

confusion → structure → clarity

When systems are designed poorly:

complexity → noise → frustration

Engineering, at its best, exists to push systems toward the first path.

What This Looks Like in Practice

A software team builds a feature. They write code, make architecture decisions, create documentation. The knowledge exists —in git commits, in markdown files, in session logs.

But the people who need to understand that work —stakeholders, partners, investors, customers —don't read repos. They don't open markdown files. They don't dig through commit history.

Documentation that nobody reads is documentation that doesn't exist.

The fix is simple: take the knowledge and put it somewhere people actually look.

A single web page. One URL. Opens instantly on a phone. Readable in 60 seconds. Printable to PDF.

Engineering knowledge (repo) → Shareable page (URL) → Human understanding (clarity)

This is the pattern applied:

An investor gets a feature brief instead of a sprint report
A partner gets a capabilities page instead of a slide deck
A customer gets a plain-language incident summary instead of a Jira ticket
A hiring candidate gets a role page instead of a job posting

Each page takes 30 minutes to create. Each one replaces hours of meetings, emails, and misunderstandings.

The knowledge already exists. The gap is always distribution.

The Multiplier

When you make information legible, behavior changes.

A partner reads a capabilities page before a call. They ask better questions. The meeting is productive instead of introductory.
An investor reads a progress brief. They understand what shipped without scheduling a call. Trust builds without overhead.
A team member reads a release summary. They know what changed. Alignment happens without a standup.

This isn't magic. It's reducing friction between knowledge and the people who need it.

Small improvements compound.

The Goal

We are not trying to fix the entire world. That would be unrealistic.

But we can make things a little less crazy.

And sometimes that's enough to help people find their footing again.

People aren't crazy.

The world is.

Let's make it a little less crazy.