Some regard more the rigour of the game than the winning of it, but to the world the discredit of the final failure does away with any recognition of the previous care. The victor need not explain... A good end gilds everything.
Baltasar Gracián, 1647 (tr. Joseph Jacobs, 1892)
An uncomfortable maxim, best held with both hands. The world is an outcomes auditor: it does not review your process, your diligence, or your bad luck; it looks at how the thing ended and reasons backward. The project that limped to a good finish is remembered as well-run; the beautifully-run project that died is remembered as a failure with excuses attached. The honest use of this asymmetry is not cynicism about means, your own conduct rules stand, but ferocity about landings: allocate disproportionate effort to the final ten percent, the delivery, the transition, the last impression, because that is where the world's entire verdict is minted.
Practice
- Budget for the landing explicitly: reserve real energy and calendar for the last phase, where most teams arrive exhausted and spend nothing.
- When a venture is failing, engineer the best available ending rather than defending the process; a well-managed retreat is a kind of victory the record respects (maxim 38's cousin).
- Resist explaining lost causes at length; the world has stopped listening, and the explanation spends dignity without purchasing the verdict.
Use this when
- Use this on everything with a visible finale: projects, events, tenures, disputes; the finale is the findable part.
- Use it in career storytelling: frame your record by how things ended, because every listener already does.
Ignore this when
- Don't let "ends gild everything" license bad means; the gate rulings and maxim 29 outrank this maxim on that question, permanently.
- Don't apply the world's harsh arithmetic to yourself in private; process is exactly what YOU should grade yourself on, since it is what you control (maxim 50's tribunal uses different books).
A picture of it
Two teams in a firm each run a hard year. Team A executes beautifully for eleven months and stumbles in the final delivery week, one botched migration, visible to every client. Team B improvises through a mediocre year and lands the ending immaculately: flawless handover, glowing closure note, a thank-you event. The annual review speaks of A's "execution issues" and B's "strong delivery culture". Unfair, entirely. Predictable, entirely. The wise team the next year does both: November is declared sacred, and the landing gets the fresh legs.
The world reads only the last page carefully. Write it with your best ink.