Redesigning Tasks Through Wu Wei and Simplicity

Welcome back. In the previous lesson, Cook Ding showed us what wu wei looks like inside a demanding activity: he does not abandon the task or rush through it; he notices its actual structure, follows its openings, and slows down at difficult joints. The result is not “zero effort,” but far less wasted effort.

This lesson adds a companion image from the Dao De Jing: the uncarved block, often rendered as pu. Cook Ding helps us work with a task as it really is. The uncarved block asks a prior question: which layers of complication did we add before we even began? By the end, you will have a practical, reversible redesign for one recurring task—one that preserves its real purpose while removing needless friction.

---

From the knife to the wood

The uncarved block is a deliberately plain image: wood before it has been shaped into a decorative object. It has grain, texture, and possibilities, but it has not yet been carved into an elaborate form.

In Daoist writing, this does not mean that all planning, structure, expertise, or cultivated skill is bad. Cook Ding himself is highly trained. Nor is it an instruction to make everything bare, cheap, or unfinished.

Instead, the image challenges a recurring human impulse: when something is unclear or difficult, we often add another layer.

We add:

• another category;
• another approval;
• another tool;
• another dashboard;
• another meeting;
• another notification;
• another exception to the existing rule;
• another elaborate explanation of what should have been simple.

Occasionally, that addition is necessary. But additions accumulate. A task that once served a clear purpose becomes difficult to see and difficult to perform. Its original grain disappears beneath the carving.

The Dao De Jing associates the sage with naturalness and plainness, using uncarved wood as one of its images.

A useful modern rendering is:

Simplicity is not the absence of structure. It is the presence of only the structure that serves the purpose.

That formulation keeps the Daoist image grounded. A deployment review, for example, may need a clear owner, an explicit rollback condition, and a safety check. Removing those would not be simplicity; it would be carelessness. But manually copying the same deployment status into three channels may be an ornamental carving rather than a real safeguard.

---

Wu wei and the uncarved block do different jobs

These ideas overlap, but they are not identical.

Image	Main question	Practical effect
Wu wei	“Given this reality, how can I act without fighting its actual contours?”	Changes the manner of action
Cook Ding’s joints and spaces	“Where are the real constraints, and where are the openings?”	Improves perception within a task
The uncarved block	“What complexity has been imposed that need not be here?”	Changes the design of a task

Suppose a weekly operational update is draining. A Cook Ding approach looks carefully at the workflow: which information is authoritative, where are decisions actually made, and at which point does the process become slow or ambiguous?

The uncarved-block approach then asks whether the task has accumulated unnecessary ornament:

• Is a long meeting being used to read information people could have seen beforehand?
• Are several manually formatted reports repeating the same data?
• Are people asked to choose among labels that make no operational difference?
• Does every update require a response, even when “no action needed” is the relevant result?
• Has a useful exception become a permanent rule?

Wu wei keeps you from hacking through the current process with greater exhaustion. Pu gives you permission to remove parts of the process that should not have become permanent in the first place.

---

“Simplify” is not always good advice

“Simplify” can become another slogan that forces a situation into a preferred shape. Daoist simplicity is more discriminating than that.

A task contains at least three kinds of elements:

Kind of element	What to do with it
Purpose-bearing	Preserve it. It is why the task exists.
Protective constraint	Understand it before changing it. It may guard safety, trust, quality, legality, or accountability.
Accidental friction	Test whether it can be removed, combined, delayed, or made visible earlier.

For instance, an incident-response process may feel cumbersome because it includes confirmation, communication, mitigation, documentation, and retrospective review. Some of this is essential. A quick but poorly understood mitigation can create a second incident; undocumented changes can damage later diagnosis.

Yet the process might also contain accidental friction: manually asking for an on-call owner when the schedule already exists, copying logs into several chat threads, or holding a status meeting with no decision-maker present. Removing these does not weaken the process. It lets attention reach the difficult joint where it is truly needed.

This is the difference between subtraction and neglect.

A sound simplification preserves what the task is for, and removes what merely makes the task feel important, busy, or familiar.

---

A modern reflection on subtraction

The following short video gives a contemporary, practical presentation of the uncarved block. Treat it as a reflection for everyday experimentation rather than as a substitute for the early texts.

The video’s “take things away” message is useful, with one qualification: do not remove a component merely because it is annoying. First identify its function. The most fruitful target is a step that adds effort without adding information, protection, coordination, or value.

---

The recurring-task redesign: an uncarving workshop

Choose one task that recurs at least weekly and is safe to modify for a few repetitions. It should be irritating enough to reveal friction, but not so high-stakes that a small experiment could affect security, health, legal obligations, or other people’s essential rights.

Possible candidates include:

• compiling a weekly work update;
• triaging incoming messages;
• preparing a recurring meeting;
• reviewing a backlog;
• organizing a household shopping list;
• planning meals;
• keeping a workspace usable;
• beginning a recurring administrative task that is routinely postponed.

Avoid choosing “my whole work life” or “all my inbox.” That is the beginner’s whole ox again. Choose a bounded activity: “prepare the Monday platform update” is much more workable.

1. State the purpose before touching the process

Write one sentence beginning:

“This task exists so that…”

For example:

“This weekly update exists so that the team can see current risks, completed work, and decisions that need an owner.”

This sentence is your guardrail. If a proposed simplification damages that purpose, it is not yet a good redesign.

Then write a second sentence:

“At the end, someone should be able to…”

In the example:

“At the end, people should be able to identify any current risk, its owner, and the next decision required.”

Notice how this avoids treating the report itself as the purpose. The report is only one possible vessel.

2. Describe the current task without judging it

For one recurrence, record the activity in no more than seven moves. Use observable language.

For a weekly update, the list might be:

1. Open several dashboards and tickets.
2. Copy selected numbers into a document.
3. Ask colleagues for missing information.
4. Reformat the document for readability.
5. Send it in a chat channel.
6. Discuss it in a meeting.
7. Copy decisions into another location.

Do not redesign yet. This is Cook Ding’s attentive stage: seeing distinctions that were previously compressed into “this update always takes forever.”

3. Mark the joints, spaces, and carvings

Now inspect each move using three labels:

• Joint: a point requiring genuine judgment, coordination, or care.
• Space: an existing opening through which the task can move cleanly.
• Carving: a layer added by habit, anxiety, legacy, or appearances rather than by the task’s purpose.

In the example:

Current element	Likely reading
Identifying a real risk	Joint: it needs attention and informed judgment
Using an authoritative dashboard	Space: information already exists in usable form
Reformatting the same metrics every week	Possible carving: investigate whether it changes decisions
Discussing unresolved risks with the right owners	Joint: conversation may be necessary
Repeating every status item aloud in a meeting	Possible carving: perhaps the meeting could focus on exceptions and decisions
Recording decisions once in a shared place	Protective structure: preserve it

The labels are hypotheses, not verdicts. You may discover that an apparently redundant step is the only moment when someone notices a problem. In that case, retain its function, but perhaps change its form.

4. Remove one thing, not everything

A Daoist experiment should be small enough to observe. Pick one subtractive change for the next two or three repetitions.

Good candidates include:

• removing a duplicate manual transfer;
• replacing a broad status request with one specific prompt;
• reducing a report to exceptions, risks, and decisions;
• eliminating a notification that rarely changes action;
• replacing many equivalent choices with a sensible default;
• making the source of truth visible early, rather than gathering it late;
• separating “information to read” from “decision that requires a meeting.”

For someone building ML infrastructure or agent workflows, an important caution is worth making explicit: the first answer to friction is not necessarily another automation. A new agent, integration, dashboard, or orchestration layer can be a fresh carving that requires monitoring and maintenance. Sometimes the more Daoist design is a deleted handoff, a clearer default, or one canonical source of information.

5. Make the experiment reversible

Write the new version in a compact form:

Design field	Example
Purpose preserved	Risks and decisions remain visible to the relevant people
One subtraction	Stop manually copying stable metrics into the weekly document
Replacement, if needed	Link the existing dashboard; summarize only changes and exceptions
Trial length	Three weekly cycles
Guardrail	If a risk is missed or an owner is unclear, restore or revise the removed step
Observation	Time spent, interruptions, missed information, decision quality, and felt strain

The guardrail matters. Non-forcing is responsive, not stubborn. If the change reveals that an old step served a genuine function, the appropriate response is not to defend simplification ideologically. It is to learn from the resistance.

---

A worked example: turning a status ritual into a decision practice

Imagine a team’s recurring Friday status routine. It takes forty-five minutes to prepare and thirty minutes to discuss. Everyone dislikes it, yet no one wants to remove it because “visibility matters.”

The purpose sentence reveals something more exact:

“The routine exists to surface operational risks and unblock decisions before the next week.”

The current process has become carved: a detailed narrative report, manually copied metrics, a meeting that reads the report aloud, and a decision log updated afterward.

A first redesign does not remove visibility. It preserves visibility while subtracting duplication:

• Stable metrics remain on the existing dashboard.
• The written update contains only material changes, risks, and decisions needed.
• Participants read the update before the meeting.
• The meeting is reserved for unresolved trade-offs and ownership.
• Decisions are recorded in one place during the meeting rather than transcribed afterward.

The task may still require thought. A genuine risk is still a difficult joint, and it may require slower, more exact discussion. But the team is no longer hacking through repeated narration and manual formatting simply because that is how the ritual evolved.

This is pu in practice: not a glamorous productivity system, but a return to the task’s grain.

---

What to notice during your experiment

For the next few repetitions, keep a short note. Do not aim to prove that the redesigned task is superior immediately. Simply collect evidence.

Record:

• whether the original purpose was met;
• where time and attention were spent;
• whether the deleted step was actually missed;
• whether a new problem appeared;
• whether the remaining difficult point became clearer;
• whether the task felt calmer because of less friction, or merely emptier because something essential was removed.

This final distinction is crucial. A process can be shorter yet worse. Daoist simplicity is not a reduction in the number of steps at any cost; it is a better fit between action and the reality the action must serve.

---

Key takeaways

The uncarved block, pu, is an image of naturalness and plainness before excessive shaping. In a recurring task, it invites you to notice how useful work accumulates unnecessary distinctions, rituals, tools, and demands.

Together with wu wei, it offers a practical discipline:

• Begin with the task’s real purpose.
• Observe the current process closely enough to distinguish genuine joints from habitual friction.
• Preserve protective constraints rather than mistaking them for clutter.
• Remove one unnecessary layer through a small, reversible experiment.
• Let the results revise your design rather than forcing simplicity as an ideology.

Cook Ding taught that mastery finds openings within a task. The uncarved block adds that we should be wary of building needless obstacles around the task in the first place.

Next, we turn from action and simplicity to judgment: a famous lost-horse story will challenge the reflex to label events immediately as good or bad.