⏰ AI Made Everything Feel Urgent. Most of It Isn't.

There used to be a natural pace to work that came from the friction embedded in doing it. Drafting something took time, so a request for a draft naturally sat in a queue for a while before it could be addressed. Research took time, so a question requiring research had a built-in delay before an answer could arrive. This friction wasn't designed as a prioritization system, but it functioned as one anyway: things that required more effort naturally got triaged and sequenced, because they couldn't all happen immediately.

AI has removed a significant amount of that friction, and in doing so, it's removed the informal prioritization system that used to come with it. Nearly everything can now be actioned immediately. And immediate actionability is quietly getting mistaken for immediate necessity, in a pattern that's driving a specific and underexamined form of overwhelm.

------------- Context -------------

Before AI, the time required to complete a task functioned as a natural filter on what could realistically happen right now versus what had to wait. A request that would take three hours to fulfill couldn't be actioned in the next ten minutes, regardless of how urgently it was framed, simply because the work took time. This created an implicit form of triage: things got sequenced by a combination of actual priority and practical feasibility, and the feasibility constraint did a lot of quiet work in keeping the pace of a day manageable.

AI has collapsed the feasibility constraint for a huge range of tasks. A request that used to require hours can now be actioned in minutes. This is a genuine advantage in many cases. But it also means that the natural pacing mechanism that used to exist alongside the feasibility constraint is gone, and nothing has automatically replaced it. Everything that arrives now carries an implicit invitation to be handled immediately, because immediate handling is now technically possible in a way it never used to be.

The psychological effect of this shift is significant and underappreciated. When something is technically actionable right now, there's a pull toward treating it as though it should be actioned right now, even when the actual priority of the task hasn't changed at all. Feasibility and urgency are different things, but in a world where almost everything has become instantly feasible, the distinction is easy to lose.

------------- The False Urgency That Accumulates Across a Day -------------

A consultant who felt persistently reactive despite genuinely valuing the speed AI gave her traced the feeling to exactly this dynamic. Client requests that used to sit for a day or two before she addressed them, because addressing them properly took real time, were now things she felt compelled to handle within the hour, because handling them within the hour had become technically possible. Nothing about the actual urgency of most of these requests had changed. Her sense of obligation to respond immediately had changed, driven entirely by the fact that immediate response was now available as an option.

Across a full day, this pattern meant she was constantly interrupting more important, less time-sensitive work to handle things that felt urgent purely because they were now fast to address, not because they were genuinely time-critical. Her actual priorities, the strategic thinking and relationship work that mattered most to her business, were being crowded out by a stream of lower-priority tasks that had simply become newly capable of demanding immediate attention.

Her fix was deliberately reintroducing artificial friction: a rule that non-critical requests, even ones she could technically handle in minutes, would be addressed in a specific batch later in the day rather than immediately upon arrival. This wasn't about working slower. The tasks still got handled quickly once she reached them. It was about restoring a triage step that AI's speed had inadvertently eliminated.

------------- Rebuilding Deliberate Prioritization -------------

The skill this requires is essentially a reconstruction of what used to happen automatically: separating what's genuinely time-sensitive from what merely feels urgent because it's now fast to address. This distinction doesn't come naturally in an environment where almost everything is instantly actionable. It has to be deliberately maintained.

The most effective practices for doing this involve reintroducing structured pauses between a request arriving and a response happening, specifically to interrupt the automatic pull toward immediate action. This isn't about delay for its own sake. It's about creating the space for an actual priority judgment to happen, rather than letting technical feasibility make the priority decision by default.

------------- Practical Moves -------------

First, notice the specific feeling of pull toward immediate action and ask explicitly whether the underlying task is actually time-sensitive, or whether it just feels urgent because it's now fast to address. This distinction, made consciously, catches a significant portion of false urgency.

Second, build a deliberate batching practice for non-critical requests: a specific time later in the day or week when lower-priority items get addressed together, rather than each one pulling immediate attention as it arrives.

Third, protect your highest-priority work with time blocks that are genuinely defended against the pull of newly-fast, lower-priority tasks. The defense needs to be structural, a real calendar block with real boundaries, not just an intention to focus.

Fourth, periodically audit what's actually been consuming your time and ask how much of it was genuinely urgent versus merely fast. This audit usually reveals the gap between actual priority and felt urgency clearly.

Fifth, communicate response-time expectations proactively to clients and colleagues, so that the newly available option of immediate response doesn't become an unspoken obligation. Making the timeline explicit removes the ambiguity that drives reactive behavior.

------------- Reflection -------------

The friction that used to slow work down wasn't purely a cost. It performed a quiet, valuable function: naturally sequencing what got attention and when. AI has removed a lot of that friction, which is genuinely valuable for the tasks that actually benefit from speed. But it's also removed the informal prioritization system that came along with it, and nothing replaces that system automatically.

The professionals managing this well have rebuilt deliberate prioritization consciously, rather than letting technical feasibility quietly make priority decisions on their behalf. That reconstruction takes effort, but it's the difference between AI speed serving your actual priorities and AI speed dictating them by default.

How much of what pulled your attention today was genuinely urgent, and how much simply felt urgent because it had become fast to address?

8 comments

⏰ AI Made Everything Feel Urgent. Most of It Isn't.