Brad Holmes web developer, designer and digital strategist.

Dad, husband and dog owner. Most days I’m trying to create fast, search-friendly websites that balance UX, Core Web Vitals, and digital strategy from my studio in Kettering, UK.

If you’re here, you either found something I built on Google or you’re just being nosey. Either way, this is me, the work, the thinking, and the bits in between.

Brought to you by Brad Holmes

Gmail screenshot - i know your busy but

“I Know You’re Busy, But…” The Email Opener That Says It All

Brad Holmes By Brad Holmes
4 min read

“I know you’re busy, but…”

The sentence that makes your shoulders tense before you even reach the next line.

Every professional hears it weekly. It’s meant to sound polite. It never does. Because what it actually means is:

“I’m aware you have too much on, but here’s something else.”

The irony is it’s rarely sent by people trying to be rude. It’s sent by people trying to be nice. The problem is, it’s polite in theory and inconsiderate in practice.


It’s a Guilt Trip Disguised as Empathy

When someone starts an email with “I know you’re busy but…” what they’re really doing is shifting the weight of the ask onto you. It’s an emotional disclaimer.

You now have to read the rest of the message while deciding whether ignoring it makes you the bad guy.

It’s a clever piece of social engineering not malicious, just habitual. We’ve all done it. But it’s the reason inboxes feel heavier than they should.

You don’t need to remind people they’re busy. They know.
You just need to tell them why your email matters enough to cut through that busyness.


It’s a Red Flag for Unclear Intent

“I know you’re busy, but could you take a quick look?”
Translation: I’m not sure how important this is, so I’ll let you decide.

The people who write that line aren’t lazy they’re usually unsure how to frame urgency. But that uncertainty makes their message harder to act on.

Professionals don’t resent being asked for things. They resent vague asks that come wrapped in guilt.

If you need something reviewed, approved, or signed off, just say it. Clarity isn’t rude. Hesitation is.


How to Ask Without Apologising

You can be polite and direct. They’re not opposites.
Here’s what works better:

  • Be specific: “Can you review this before 3pm so we can ship it?”
  • Show context: “This version fixes the analytics issue you spotted last week.”
  • Set tone: “No rush on this just flagging it for when you get a gap.”
  • Respect focus: “This needs a quick read, not a deep dive 2 minutes max.”

It’s not about being blunt. It’s about respecting time and removing friction.

Politeness isn’t in the wording. It’s in how easy you make it for the other person to help you.


The Follow-Up Offender

The funniest (and most painful) part?
The people who open with “I know you’re busy but” are often the same ones who follow up two days later with “Just circling back on this…”

You can’t start with guilt and end with pressure. Pick one.

If your message was clear, it wouldn’t need chasing. If it wasn’t, no amount of “bumping this up” will help.


Don’t Be Polite, Be Useful

The fix is simple: don’t apologise for asking. Just make your ask worth answering.

  • If you need a decision, say so.
  • If you need feedback, tell me what kind.
  • If you’re unsure, frame it as a check-in not a cry for help.

Your reader will appreciate the honesty. Nobody minds an ask that’s clean, relevant, and easy to respond to. What drains people is the uncertainty hidden behind politeness.


The Bottom Line

I don’t dislike people who write “I know you’re busy but.”
I dislike that modern work has made people feel they need to.

If you respect someone’s time, don’t apologise for being in their inbox act like it.
Get to the point, give context, and make it easy to say yes.

Because if you already know I’m busy…
don’t make me prove it.

Related Articles

Brad Holmes

Brad Holmes

Web developer, designer and digital strategist.

Brad Holmes is a full-stack developer and designer based in the UK with over 20 years’ experience building websites and web apps. He’s worked with agencies, product teams, and clients directly to deliver everything from brand sites to complex systems—always with a focus on UX that makes sense, architecture that scales, and content strategies that actually convert.

Thanks Brad, I found this really helpful
TOP