四、工作、创业与组织IV. Work, Founding & Organization

Start an agent today, add an automation tomorrow, try a new market the day after; every project can be prototyped in an afternoon, so the org keeps starting and rarely truly closes anything out

Be as careful at the end as at the beginning, and nothing will fail

AI lowered the cost of starting but not the cost of sustaining, coordinating, and bearing outcomes; a pile of half-finished things keeps draining attention and organizational complexity

Limit how many projects run at once; before launching a new project, decide which old one to stop; build closeout, maintenance, and exit costs into the project from the start; don't mistake a finished prototype for a finished product

AI generates a full plan in minutes, so managers assume the project takes only days; code can be generated but that's not shipping, a business plan can be generated but that's not users buying, an org plan can be generated but that's not people acting on it

Light promises bring little trust; treating much as easy brings much difficulty

Completeness at the level of language easily manufactures a sense of simplicity at the level of reality; AI made "describing a thing" easy without automatically removing the dependencies, conflicts, and long-term costs of execution

Separate plan generation from real delivery; for any AI plan, add dependencies, risks, and maintenance costs; the easier it looks, the harder you check hidden complexity; don't give the team unrealistic timelines just because AI promised speed

Swap the model today, rework the architecture tomorrow, redo the workflow the day after; each change executes fast, so the boss keeps churning the org; the team looks perpetually busy while the long-term direction grows ever less stable

Govern a great state as you would cook a small fish

Cooking a small fish, the cardinal sin is constant flipping; complex systems need continuity, and a lower cost of change doesn't mean the organizational cost of change vanished too

Set fixed cycles for strategic adjustment; distinguish tool upgrades from direction changes; don't rebuild the whole system the moment a new tool appears; give the team enough time to form a stable way of working

Dozens of agents running at once, a log for every step, a status for every task, every flow shown on a dashboard; people then assume that as long as the data is complete, the system is fully in hand

The world is a sacred vessel, not to be controlled; who controls it ruins it, who grips it loses it

A complex system isn't a static machine; every part can be correct while the whole still drifts off course; data can represent part of a system but cannot exhaust a living organization

Don't try to predefine all behavior; design boundaries, permissions, feedback, correction, and stop mechanisms; keep important decisions reversible; let anomalies and dissent be seen by the system; manage the overall goal rather than control every step

Some teams drift into micromanagement, approving every step; others drift into total laissez-faire, letting agents decide everything; neither actually solves governance

The Tao does nothing, yet leaves nothing undone

"Non-action" isn't not governing — it's not governing by constant intervention; truly advanced control rises from specific actions up to rules, boundaries, and feedback mechanisms

Set clear goals and inviolable boundaries; grant agents autonomy within the boundaries; auto-escalate high-risk cases to humans; cut daily micro-intervention; update rules from outcome feedback rather than issuing orders item by item

The research agent finished the research, the writing agent finished the article, the publishing agent published successfully; every step shows success, yet the final output may have served the original goal not at all

Who controls it ruins it, who grips it loses it; one who stands on tiptoe is not steady, one who overstrides cannot walk

Completing local tasks doesn't equal achieving the overall goal; the more an org relies on automation, the more easily it mistakes "process success" for "value success"

Set an overall value metric for the system; have humans periodically re-examine the original goal; assess not just whether agents finished tasks, but whether the tasks were worth finishing; prevent local optima from accumulating into overall drift