data.day
burnout / communication-hygiene / productivity / boundaries

Rant: 'Can You Do This Real Quick' Is How Burnout Gets Booked

Ambiguous urgency is not leadership; it is stress outsourcing. Stop accepting 'quick favors' and start demanding structured requests.

Marta Clarity Marta Clarity

Urgency Without Clarity is Just Noise

I have a rule. If a request comes in via DM with the words “quick favor,” I automatically deprioritize it.

Why? Because “quick” is a feeling, not a spec.

When a manager asks for a “quick report,” they are not managing. They are panicking. They are outsourcing their stress to you. They haven’t defined what they need; they just know they need something to soothe their anxiety.

The Chaos: The Hidden Cost of “Quick”

When we say yes to the “Real Quick,” we break the operational flow.

  • The Context Switch: It takes 23 minutes to recover focus after an interruption. A 5-minute task actually costs 30 minutes of cognitive load.
  • The Queue Jumper: The “quick” task cuts in line in front of the strategic project. We delay the important to serve the urgent.
  • The rework: Because the request was vague (“Just pull the sales numbers”), the output is usually wrong (“Oh, I meant net sales, not gross”). Now we do it twice.

[Image of a timeline showing deep work being fragmented by small interruptions]

The System: The Standardized Request

We fix this by installing a speed bump. I call it The Request Standard.

We do not accept work via chat. We accept work via a Ticket or a Brief. It must contain three things. If one is missing, the request is rejected.

1. The Goal (What does “Done” look like?)

Do not tell me the activity. Tell me the outcome.

  • Bad: “Look at the data.”
  • Good: “Provide a CSV of Q3 churn rates for Enterprise clients.”

2. The Constraints (What are the guardrails?)

This prevents the “Real Quick” from becoming a week-long saga.

  • Example: “Do not spend more than 1 hour on this.”
  • Example: “Must use the new brand template.”

3. The Deadline (When do you really need it?)

“ASAP” is not a time. “End of Day” is vague (whose day? mine or yours?).

  • Requirement: Date and Time.
  • Logic: If the deadline is in 2 hours, Then you must explain why this is an emergency.

Implementation: The polite “No”

You teach people how to treat you. When the DM comes in, I use a script.

The Script: “I can help with that. To make sure I prioritize this against the Q3 launch, please drop this into the Request Form [Link]. Once I see the specs and deadline, I’ll slot it in.”

This filters the noise.

  • Half the time, they won’t fill out the form because it wasn’t actually important. Problem solved.
  • The other half, they fill it out, and you have clear instructions. Problem solved.

Structure is self-defense.

FAQs

What if it actually takes 2 minutes?

Then do it yourself. If you are delegating it, it takes time to explain, track, and review. That is not 2 minutes.

I don't want to be a bureaucrat.

Asking for clarity is not bureaucracy. It is professionalism. Vague requests are the enemy of quality.

My boss hates filling out forms.

Your boss hates bad results more. Show them that the form leads to faster delivery. Results sell the process.