How to Actually Use Common Sayings About Success And Failure in Everyday Conversations
I started collecting sayings about success and failure back in 2019 when I was managing a small team at a logistics startup. Half the people on the floor had just lost a major account, and the other half had somehow closed a deal that wasn't supposed to be closable. HR sent around a motivational email with a quote about perseverance and failure. It landed like a ton of bricks. Nobody read past the first line. That's when I realized most people don't actually use these sayings correctly — they just drop them in conversation like decoration, and it comes off as hollow or even insulting. Here's what I learned about using these sayings well, and when to keep them to yourself.
Why These Sayings Actually Carry Weight (When You Use Them Right)
The sayings about success and failure work because they compress decades of observed patterns into a single sentence. "The only way to do great work is to love what you do" isn't deep philosophy — it's a pattern recognition shortcut. People have been repeating it for centuries because it tracks with reality. The problem is that when you say it without context, it sounds like a greeting card. When you say it after describing the specific situation, it hits differently. I've found that the most effective sayings are the ones that acknowledge failure as part of the process, not as an endpoint. "Fall seven times, stand up eight" is far more useful than "failure is not an option," which is just naive and sets people up for shame when they inevitably stumble. The second saying actually makes people hide their mistakes, which is the opposite of what you want in any team environment. One specific edge case I ran into: I once told a developer who'd just shipped a buggy feature that "fail fast, fail often" to encourage them not to be discouraged. They responded by shutting down entirely and refusing to talk about the project for three days. What I should have done was pair the saying with concrete next steps — a postmortem template, a specific fix to try first, a willingness to sit with them and review the code. The saying alone was an empty gesture. After that, I started always coupling any saying about failure with an actionable follow-up before delivering it to someone.
The Core Sayings and What They Really Mean in Practice
Fail Early, Fail Often
This one gets misused as encouragement to just launch broken things recklessly. The actual practice is about shortening the feedback loop. In software development, this means running tests before shipping, not shipping and then finding out. The saying is about reducing the cost of failure by making failures cheap and frequent rather than rare and catastrophic. I worked with a product manager who took this literally and launched a feature without any QA. The failure was expensive — it cost us $40,000 in refunds and three weeks of engineering time fixing the fallout. The saying doesn't mean skip quality checks. It means don't spend six months building something nobody will use. Often attributed to Winston Churchill, though the exact origin is murky. The practical application is simpler than it sounds. When someone's on a winning streak, remind them that momentum doesn't equal immunity. When someone has blown a big opportunity, remind them that one loss doesn't define the whole run. The real challenge is hearing this said to you when you're in the middle of either extreme — success feels good and you don't want to be sobered up, and failure feels terrible and you don't want a bumper sticker telling you it's not fatal. I keep this one in my back pocket for performance reviews, specifically the mid-year check-in where someone's having an unusually good quarter and might start believing their own press. Attributed to Mark Twain. This seems almost too obvious to include, which is exactly why it's useful. Most people I know who are waiting for the right moment to pursue something are actually waiting for a feeling of readiness that never arrives. The saying is a reminder that the first step isn't conditioned on confidence or perfect information. I use this with anyone who's been planning the same side project for over a year without taking any concrete action. Not as a criticism, but as a neutral observation: the barrier they're describing isn't a lack of knowledge or resources, it's the invisible threshold between thinking about doing and actually doing. Crossing it requires no special preparation.
Collecting sayings is different from hoarding them. I keep a simple text file on my phone with the saying, where I heard it used effectively, and what situation it fits. When I encounter a new one, I don't add it unless I can immediately think of at least one real situation where it would apply. Empty quotes are just noise. The sayings about success and failure that are most useful tend to share a few traits: they're specific enough to paint a picture, they don't romanticize struggle, and they don't promise outcomes. The ones to avoid are the ones that sound good but collapse under scrutiny — "just believe in yourself" is the worst offender. Belief without a plan is just optimism, and optimism without a plan is what gets people bankrupt.
A Word About When to Stay Silent
Sayings about success and failure lose all value when the person hearing them needs something other than a pithy summary. If someone just lost their job, they don't need "what doesn't kill you makes you stronger." They need a referral contact, a copy of their resume, or someone to sit with them for twenty minutes without offering advice. The saying can come later, maybe, when they're in a position to actually absorb it. Using a saying as a conversational shortcut to avoid sitting with someone's difficulty is one of the most common mistakes I see, and it's also one of the easiest to correct once you notice it happening. I'll leave it at that. The sayings stick when they're earned through use, not when they're recited for appearance.
