Put a review date beside the aphorism

TL;DR: An aphorism can point you towards a useful behaviour. Add a review date and a reason to change course before treating it as an operating rule.

The Naval-attributed carousel collects compact advice about work, ownership and attention. One principle has a clear original source: in Work As Hard As You Can, Naval says, “Impatience with actions, patience with results.” He explains that individual action can be prompt while markets, products and relationships take time to develop.

That is useful advice for builders who confuse a slow response with a failed effort. It also leaves a practical decision with the reader: how do you distinguish a result that needs time from an assumption that needs replacing?

I would put an expiry date on the assumption, rather than on the ambition. That is my proposed addition to the principle. You can keep wanting the outcome while changing the route you expected would produce it.

Take a hypothetical internal developer tool. I would be impatient about making the first workflow usable and asking colleagues to try it. I would give them a reasonable period to encounter the task in their normal work, instead of demanding daily usage immediately.

But I would also set a review date. If nobody returns, the review should ask whether the task recurs, whether access is awkward and whether the tool actually removes work. Another month of patience is justified by an answer to one of those questions, not by the attractiveness of the original idea.

This is the trade-off compact advice tends to hide. Changing direction too quickly prevents learning; refusing to change lets commitment substitute for evidence. A scheduled decision makes room for both action and observation.

I checked this principle against Naval's original discussion, not every attribution in the carousel. The proposed review method is my interpretation, not a tested formula from that source.

Be patient with the outcome while keeping your explanation for the delay open to challenge.