Seven email openers that sound like the person in charge
That email has been sitting unanswered in his inbox for six days now. You open a reply and type "Just checking in on this!" with an exclamation point, as if that proves you aren't irritated. Your frustration is obvious from the exclamation point alone. The follow-up restates the original, opening with an acknowledgment that the first note failed to register.
A note reading "Just checking in" neither makes a request, nor offers anything, nor names a deadline. It sounds like a gentle prod from someone who isn't sure she is entitled to send one. A leader doesn't check in. She states what happens next. Seven openers spanning five scenarios, all written with the same self-assurance, appear below.
1. Chasing a request that has gone unanswered in Nashville or anywhere else
Inviting but ineffective: "Just checking in on this!"
Firmer: "Flagging that I need your sign-off by Thursday to hold the vendor date." Or: "Resurfacing this. Unless I hear otherwise by Friday, I'll go ahead with option B.
Reason: each line pairs a deadline with a stated outcome. The former hands the reader an obvious action to take. The second converts his silence into a deliberate decision he has to make on paper, which is a very different thing from ignoring you.
2. Asking a senior colleague for some of their time
Tempting but vague: "I'd love to pick your brain sometime if you have a spare minute."
Here in Nashville, I want to raise a single point about the Q1 pricing decision. Twenty minutes next week?"
Here the subject, the duration and the window are all spelled out. Senior people say yes to bounded requests and let open-ended ones slide, since an open request is work they must scope before they can even turn it down.
3. Sending work out for review
Off-target: "Sorry to bother you, but here's a draft, let me know if you have any thoughts!"
SHORT Stronger: "Draft attached. Tighter: "I need your view on the pricing section; the rest is settled."
"Any thoughts" opens the door to a full rewrite of the document. Naming a single section secures a decision on that section, which is the thing you really needed, and it costs them much less time.
4. Delivering news nobody wants
Less effective: "Unfortunately there's been a bit of a delay, so sorry about this."
Preferable: "The launch has shifted to the 14th. Reason for the slip: the integration did not pass load testing. A fix is underway, and I will confirm on Monday." Or, for a fuller update: "There are two things you should know and one decision I need from you."
The apologetic wording makes the reader handle your emotions before they even learn what went wrong. The plain version states the fact, the cause, the plan and the date, letting them forward it up the chain as written.
5. Declining a request that is beyond your capacity
Excessively sorry: "I'm so sorry, I'm completely swamped right now, but maybe later?"
Direct: "I am unable to take this on this week. Lena has the bandwidth and the background, and I have copied her here."
Why: a no that includes a next step is a handoff, not a refusal. You addressed the sender's underlying need, which was the whole point of their message, and you managed it without a paragraph explaining your schedule.
The rule underlying all seven of these
Each message from someone in authority settles three things within its opening lines: the subject, what the reader must do, and the deadline. Once those elements are present, you can drop every "just," every "sorry" and every exclamation point you had been relying on to cushion the message. Nobody who reads it will come away feeling you were curt. They will think you were busy, which, in Nashville's fast-moving offices, is exactly what they expect.
Pass this along to the colleague on your team who recently sent a client a note that began "just checking in."