Start here / NINEHOUND JOURNAL
Confucius on Haste and Small Gains: Speed Is Not the Whole Question
A quick action may be useful. A quick visible result may also divert attention from the purpose that made the action worth taking.
The advice begins with a question about governing
In Zilu, Zixia serves as administrator of Jufu and asks about governing. Confucius advises against seeking haste and looking at small gains, then connects haste with failing to arrive and small gains with failing to accomplish a larger undertaking. The setting is specific. It is not a universal limit on how fast every action should be performed.
The wording does not praise slow walking or endlessly delayed replies. It places two attractions beside one another: immediate achievement and a smaller benefit in view. Quoting only the familiar sentence about haste loses the second concern. A contemporary application needs to examine both what is being rushed and what result is directing attention.
Ask what arrival would actually mean
Speed can be measured while accomplishment still needs a purpose. Without a defined task, almost any short term result can be presented as progress: saved files, sent messages, written pages. Each may be a real action. None automatically establishes that the original question was answered or the intended thing delivered.
This is our application of the passage’s tension between speed and arriving, not a claim that Confucius defined modern project metrics. For an explanation of a classical saying, a reader should be able to find the source and understand the context and limits. For a tool, the intended function should work. Acceptance depends on the particular task, rather than a single checklist governing every kind of work.
A small gain may be real and still distract
The smaller benefit does not have to be fabricated or pursued with bad intentions. It may genuinely feel rewarding while using time, trust, or conditions needed for the larger purpose. That is why the relation between the two deserves inspection. The fact that something is a real benefit does not settle whether it belongs in the present plan.
Imagine trying to understand a classic while selecting only memorable short sayings. This is hypothetical. Each saying may offer value, but repeated immediate satisfaction can displace reading its context. Conversely, a small achievement may be exactly the next part of a larger undertaking. Neither size nor the label small gain settles the choice. We still need to explain how the benefit relates to the purpose.
Separate timely action from premature success
A missing quotation can be checked promptly, an unclear commitment clarified, and a verified error corrected. Such actions do not become wrong simply because they are quick. Delaying them may make later work harder. The passage can therefore sharpen action without making speed and reliability inevitable opponents.
Haste becomes a different problem when an important condition is skipped: writing an explanation before reading, announcing cooperation before receiving a reply, or claiming completion before delivery. These are illustrative categories, not accusations about a real person. A smaller next step can retain a clear acceptance condition. Record what actually happened and leave what has not happened unresolved, even when a favourable result is strongly desired.
Waiting needs a reason as well
Using the saying to excuse indefinite delay is no better. If waiting is warranted, name what is awaited: a source, a reply, or a fixed observation window. Time passing without a specific condition to inspect does not automatically create better judgement. At review, compare evidence of progress rather than the sensation of being busy or careful.
Ask which condition was obtained, which question became clearer, and which cost requires adjustment. Reconsider both ineffective waiting and ineffective rushing. The complete Analects exchange offers more than an instruction to slow others down. It lets us ask whether the wish for an immediate satisfying result has displaced the undertaking itself. Pace should serve that undertaking, and a visible intermediate count should remain distinct from its successful completion. An acknowledgement, a prepared draft, and a usable delivery can each be recorded honestly without allowing the earlier stage to stand for the later one.
Sources and further reading
Interpretation of received text; modern workflow examples are hypothetical and no activity count is presented as verified success.