Is Wabi-Sabi just an excuse for sloppy work?

No, and the guard against that reading is practice 1. The standard is better than the current state, measured. That is a harder bar than perfect in one specific way: it has to be demonstrated every time.

When should I not use this?

When the decision is irreversible or the failure is unbounded. Safety, regulatory filings, anything affecting a person’s health or money. Use the Greek ideal there and use it deliberately.

How do I tell intelligent failure from waste?

Three tests. Was the cost bounded before you started, did it produce information you did not have, and was there a stated hypothesis. Two out of three is waste with good intentions.

My team is afraid to ship anything unfinished. Where do I start?

Practice 3. As-is documentation is the lowest-stakes place to break the perfect-or-nothing habit, because nobody’s work is being judged, only described.

Does this conflict with quality standards?

Only if quality is defined as an ideal rather than a threshold. Define the threshold, measure against it, and shipping at threshold stops feeling like a compromise.

Part II · Teams, Systems & Hybrid Work

Wabi-Sabi

Wabi-Sabi is the Japanese aesthetic of imperfection, impermanence and incompleteness.

What it diagnoses

Perfectionism operating as a delivery system.

Wabi-Sabi is the Japanese aesthetic of imperfection, impermanence and incompleteness. Set against it is what Leonard Koren calls the Greek ideal: the pursuit of flawless execution and unchanging excellence, which treats imperfection as defect and incompleteness as inadequacy. Western business culture runs on the second one by default.

In an operation, that produces a specific failure. Nothing ships until it is right, documentation waits for the optimal process, and decisions wait for certainty. The work is not stalled by lack of capability. It is stalled by a standard nobody set deliberately and nobody can meet.

The framework diagnoses three things. Whether your team can ship at partial. Whether failure is treated as information or as fault, because if it is fault nobody will run an experiment that might produce it. And whether the standard being applied was ever actually specified, or whether it is somebody’s private definition of good enough doing the work of a release criterion.

McKinsey’s strategy work makes a version of this argument at the enterprise level, arguing for imperfectionism, accepting the ambiguity of incomplete knowledge and making a series of small moves that build knowledge as they go, with the explicit expectation that some will fail. Their point about cadence is the operative one: an annual approach to strategy is not running at the speed the business is running at.

How to run it

The book runs five practices.

Replace perfect-or-nothing with better than yesterday. The release criterion becomes a comparison against the current state, not against an ideal. If the new version is better than what is in production, it ships, and the next version improves it.
Implement intelligent failure recognition. Not all failure is equal and treating it as though it is guarantees you get less of the useful kind. Intelligent failure is bounded in cost, produces information you did not have, and was run against a stated hypothesis. Everything else is just a loss. Name the difference explicitly so people can tell which one they are being asked to risk.
Document as-is instead of waiting for perfect. An accurate description of the messy current process is worth more than an aspirational description of a clean one that does not exist. As-is documentation can be improved. A fiction cannot.
Build learning loops into every initiative. Decide before you start what you will look at, when, and what would change your mind. A review scheduled at the end is an autopsy.
Reframe mistakes as course corrections. This is a language practice with a structural effect. If the vocabulary around a miss is blame, the reporting of misses goes down and the misses do not.

How operators misuse it

They read it as permission to lower the bar. Wabi-Sabi is about shipping cadence and honest documentation, not reduced standards. It pairs with a measurement system precisely so that better than yesterday stays a measured claim rather than a feeling.

They apply it where reversibility does not exist. Shipping imperfect works when the cost of being wrong is bounded and recoverable. In a regulated filing, a safety system, or anything you cannot take back, the Greek ideal is correct and this framework does not apply. Knowing which regime you are in is the operator’s call.

They celebrate failure generically. A team that has been told failure is fine, without being told what separates intelligent failure from waste, produces expensive experiments nobody designed. The permission has to arrive attached to a hypothesis requirement.

What the pattern shows

The documented pattern sits in two places, and they point at the same mechanism from opposite ends.

Harvard Business Review’s work on crisis decision-making is blunt about the timing problem: when conditions change by the day or the hour, there is no time for perfection, and perfectionism actively slows a leader down at the moment speed matters most. The failure is not that the perfectionist produces worse work. It is that the work arrives after the window it was aimed at has closed.

HBR’s research on perfectionist managers points at the second-order cost, which lands on the team rather than the leader. The behavior propagates. People working under a standard they cannot predict or meet stop surfacing partial work, which removes exactly the early signal a leader needs to correct anything.

McKinsey’s strategy research approaches it from the enterprise side and lands on the same fix. They describe progress as a rugby sequence, forward, backward and sideways moves, with the knowledge accumulating through the sequence rather than preceding it. The strategic implication is that waiting for sufficient knowledge before moving is not caution. It is a decision to learn later than your competitors.

Read together: perfectionism is not a personality quirk with a productivity cost. It is a cadence failure that shows up as missed windows, suppressed reporting, and knowledge acquired after it was useful.

Where it lives in the book

Framework 13, Chapter 4, page 207. The Acceptance of Process. It closes Chapter 4 and closes Part II, which is the right position: Kaizen supplies the cadence, SMART supplies the destination, and Wabi-Sabi is the permission that lets the first two actually run.

Questions operators ask

Is Wabi-Sabi just an excuse for sloppy work?: No, and the guard against that reading is practice 1. The standard is better than the current state, measured. That is a harder bar than perfect in one specific way: it has to be demonstrated every time.
When should I not use this?: When the decision is irreversible or the failure is unbounded. Safety, regulatory filings, anything affecting a person’s health or money. Use the Greek ideal there and use it deliberately.
How do I tell intelligent failure from waste?: Three tests. Was the cost bounded before you started, did it produce information you did not have, and was there a stated hypothesis. Two out of three is waste with good intentions.
My team is afraid to ship anything unfinished. Where do I start?: Practice 3. As-is documentation is the lowest-stakes place to break the perfect-or-nothing habit, because nobody’s work is being judged, only described.
Does this conflict with quality standards?: Only if quality is defined as an ideal rather than a threshold. Define the threshold, measure against it, and shipping at threshold stops feeling like a compromise.

Sources

Score it

Take the Burnout Diagnostic Get The Resilience Engine: $27

Pairs with

SMART Goals. Measurable targets plus permission to ship imperfect. Permission without measurement drifts, measurement without permission produces paralysis.
Kaizen. Continuous improvement requires permission to fail intelligently.
Situational Leadership II. Permission to iterate plus a diagnostic to iterate toward.