A client once needed something by the next morning. It was urgent — genuinely, emphatically urgent, the kind of urgent that comes with several exclamation points and a "sorry for the short notice but this is critical." So we rushed it. We compressed a job that deserved a couple of days into an overnight scramble, skipped the steps that make work good, and delivered on time, exhausted, with something noticeably worse than we'd have made with room to breathe. And then the thing sat. It wasn't used the next day, or the day after. When it finally went out, more than a week had passed — a week in which the "urgent" deadline that had cost us quality and sleep turned out to have been completely arbitrary. Nobody had needed it the next morning at all. The urgency was invented, and we'd paid full price for it.
I've since come to believe that most urgency is like this: manufactured, not real. "I need it yesterday" is less often a description of an actual deadline than a default mode, a reflex, a culture that treats everything as urgent because urgency feels like seriousness and speed feels like good service. And the reflex is enormously expensive, in ways that stay hidden because the cost is spread out and the "on-time delivery" is visible. We celebrate hitting the urgent deadline and never account for what the rush cost — the quality that suffered, the people who burned out, the way constant firefighting quietly slows everything down. The bill gets paid; it just gets paid somewhere you're not looking.
Here's the claim: treating everything as urgent produces worse work, exhausts the people doing it, and — paradoxically — makes everything slower over time, all in service of deadlines that mostly aren't real. The "always fast, always responsive" posture that looks like excellent service is frequently the opposite, because it sacrifices the conditions that good work actually requires in order to satisfy an urgency that, examined honestly, usually evaporates. Speed isn't free, and we act like it is.
I'm not saying deadlines don't matter or that urgency is never real — sometimes it genuinely is, and I'll get to how to tell. I'm saying that the reflexive, everything-is-urgent default costs far more than the occasional real emergency ever would, and that learning to distinguish manufactured urgency from real deadlines is one of the highest-leverage things a business or a person can do. Here's what rushing actually costs, why we do it anyway, and how to stop paying for urgency that isn't real.
Key Takeaways
- Most urgency is manufactured, not real. "I need it yesterday" is usually a reflex or a culture, not an actual deadline — and the rushed thing often isn't even used soon.
- Rushing quietly degrades quality. Good work needs time for iteration, judgment, and the second look. Compress that away and the output is worse, every time.
- Constant urgency exhausts people and slows everything. A permanent firefighting mode burns out the people doing the work and, paradoxically, makes the whole operation slower through redos and depletion.
- "Always fast, always available" isn't great service. It looks like it, but it sacrifices the conditions good work requires, so the client who demands speed usually gets worse work.
- Learn to tell real deadlines from fake ones. Ask what actually happens if it's a day later. Most "urgent" things fail that test — and reserving real speed for real emergencies protects everything else.
Most Urgency Is Manufactured
Start with the uncomfortable observation that most of the urgency in professional life is invented. There's a small category of genuinely urgent things — real external deadlines with real consequences, actual emergencies — and then there's the vast, sprawling category of things that are labeled urgent but aren't: arbitrary deadlines, requests that feel pressing but could easily wait, work rushed because rushing has become the default mode rather than because anything actually requires it.
The tell is what happens after. Genuinely urgent things are used the moment they're delivered, because that's what made them urgent. Manufactured-urgent things sit — the "I need it by tomorrow" deliverable that isn't touched for a week, the "critical" request that turns out to have no real deadline behind it. If you start noticing this, you'll see it everywhere: a huge share of the urgency people impose and accept has no actual deadline underneath it. The urgency was real as a feeling and fictional as a fact.
There's a reason this default exists, and it's worth naming because it's rarely about a real deadline. Urgency often stands in for poor planning — work that could have been paced was left late, and the lateness gets relabeled as urgency to transfer the pressure. It stands in for anxiety and a need for control — treating things as urgent feels like taking them seriously, like being on top of things. And it stands in for a belief that speed equals good service, so being fast and responsive becomes an identity rather than a considered choice. Almost none of these has anything to do with an actual external deadline, which is why so much urgency evaporates the moment you ask what really happens if it's a little later.
What Rushing Actually Costs
The reason manufactured urgency matters is that rushing is expensive, and the expense is mostly hidden. Here's the bill.
The first cost is quality. Good work needs time — not because people are slow, but because quality comes from a process that can't be fully compressed: the iteration, the judgment, the second look, the space to notice what's not working and fix it. Rush that away and you get first-draft work delivered as final, because there was no time for the passes that make it good. I've written before about how long good editing actually takes and why the timeline isn't padding but the actual requirement of quality; rushing doesn't remove that requirement, it just removes the quality. [BACKLINK PLACEHOLDER → suggestion: internal link to article #21, how long video editing actually takes by format / why quality takes real time] There's solid research showing that time pressure, contrary to the myth of the productive crunch, actually reduces creative thinking — people under the gun do more rushing and less real problem-solving. [BACKLINK PLACEHOLDER → suggestion: external link to a credible source on time pressure and creativity, e.g. Teresa Amabile's research "Creativity Under the Gun" / HBR] The rushed version isn't the same work delivered faster. It's worse work, and the difference is the thing the deadline felt too urgent to allow.
The second cost is people. Constant urgency means constant firefighting, and a team living in permanent crisis mode burns out. This is slower to show up than the quality hit but more damaging, because a depleted team does worse work on everything, not just the rushed job — the cost of one manufactured emergency is paid partly by every project that follows it, made by tireder people. An always-urgent culture is an always-exhausted one, and exhaustion is corrosive to exactly the judgment and care that good work depends on. This is part of why learning to stop doing things — including stop rushing things — is a marker of a business maturing rather than one slacking off. [BACKLINK PLACEHOLDER → suggestion: internal link to article #13, six things I stopped doing in year two / protecting sustainability]
And the third cost is the paradox: rushing everything makes everything slower. A firefighting culture never has time to do things right, so it does them twice — the rushed job that needs redoing, the corner cut that causes a problem later, the quality shortfall that generates a new round of work. Perpetual urgency feels fast and productive and is neither; it's a treadmill where the constant rushing prevents the careful work that would actually let you move quickly. The businesses that seem to move fast and well are usually the ones that resist manufactured urgency, protect their process, and therefore rarely have to redo anything.
Why "Always Fast" Isn't the Service It Looks Like
There's a specific version of this worth calling out, because it's dressed up as a virtue: the "always fast, always available, quick turnaround" posture that agencies and service providers wear as a selling point. It looks like excellent service — who wouldn't want a provider who's endlessly responsive and fast? But it usually delivers worse outcomes, because a provider who treats every request as urgent has, by definition, given up the paced, considered process that produces their best work.
The client who demands maximum speed is, without realizing it, demanding worse work, because they're asking the provider to sacrifice the conditions quality requires. And a provider who competes on always being fast is competing on the wrong thing — the same way a provider who competes on unlimited revisions or the lowest price is signaling the absence of the judgment you actually want. The best providers are protective of their process precisely because they care about the outcome, and part of that protection is resisting manufactured urgency rather than reflexively submitting to it. The client relationships that produce the best work are usually the ones with enough trust to allow a real timeline, not the ones running on perpetual rush. [BACKLINK PLACEHOLDER → suggestion: internal link to article #4, why fast-approving clients churn fastest / speed without substance] Responsiveness is genuinely valuable, but responsiveness in service of manufactured urgency is just a shared agreement to make everything worse, faster.
🎬 Embed a short breakdown of a rushed deliverable versus the same work with a real timeline, and the specific quality differences the rush erased.
How to Tell Real Urgency From Manufactured
The whole thing turns on one skill: distinguishing genuine deadlines from invented ones, because the response to each should be completely different. Real urgency deserves real speed; manufactured urgency deserves a calm timeline. Confusing them — rushing the fake and thereby having no capacity for the real — is the core error.
The diagnostic is simple: ask what actually happens if this is delivered a day or two later. For genuinely urgent things, the answer is concrete and consequential — a real external deadline is missed, a real opportunity is lost, a real problem worsens. For manufactured-urgent things, the honest answer is "nothing much," or "someone would feel anxious," or a vague sense that later is worse with no actual consequence attached. Most urgency fails this test the moment you apply it, which is exactly why nobody applies it — the urgency survives only as long as it goes unexamined. Asking the question dissolves most false urgency and reveals the rare real deadline clearly.
Once you can tell them apart, the response follows. For the small category of real urgency, move fast — that's what the reserved capacity is for, and real speed for real emergencies is genuine, valuable service. For the large category of manufactured urgency, resist: give the work a real timeline, push back gently on the invented deadline, and protect the conditions good work requires. The buyer who learns to stop manufacturing urgency gets better work; the provider who learns to stop reflexively accepting it protects both quality and sanity. And everyone benefits from the fact that when you're not rushing everything, you actually have the capacity to move fast when it genuinely matters — manufactured urgency is what leaves you with nothing left for the real thing.
