6099 comments
2357 subscribers
6264 on Twitter
Subscribe! Feed reader E-mail

Proactive communication: Five tips for following up

Isabelle’s manager wanted her to get better at proactive communication. She’s comfortable e-mailing people, but she has a hard time following up when people don’t respond. Timezone differences between team members in Singapore and in the US compound delays. She reached out to me for advice, and I suggested a few things that might help:

1. Clear, dated requests. When asking for help or a response through e-mail, specify a target date instead of leaving it open-ended, and give a reason for that date if possible. This makes it easier for people to prioritize working on your task. (Don’t always ask people to get back to you TODAY, though. It looks like you don’t plan well.)

2. Clear, dated responses and priorities. If you’re working with other people on some lower-priority tasks, those tasks might never be finished. Clarify the relative priority of a task with your manager: it might turn out to be higher-priority than you thought. If it really is a low-priority project, contact the people you need to collaborate with and get an estimate of when they might be able to work on their part of the project. Find out what other important projects they’re working on, too. This will allow you to:

  • give clearer reasons for delays (“We can only work on the report next week because we have to finish the keynote presentation this week”)
  • negotiate better solutions (“I can do that part of the presentation if you can do this part of the report”)
  • re-negotiate priorities with your manager (“Actually, this report is more important than adding animation to the presentation”), and
  • give you dates for following up (“John is working on the presentation now, but he promised to work on the report on Monday, and I’ll follow up with him then”).

3. Status reports. They’re good for your manager and for you. Keep track of where you are on projects: what your next actions are, what you’re waiting for, and what you’ve accomplished. Share this with your manager frequently, so there are no surprises.

4. Concrete follow-ups. When you’re waiting for a response, schedule a follow-up so that it doesn’t slip through the cracks. Follow up by e-mail, and then move up to following up by phone or instant message if needed. I don’t do this for all of my tasks, but I do this for tasks I “own,” and it helps.

Concrete follow-up dates also help you write better status reports. Instead of reporting “Waiting for response”, you can report “Waiting for response; will follow up on ____ by e-mail and _____ by phone.” Clear follow-up plans make people feel more confident that the task won’t be forgotten.

5. Tactful escalation. When people don’t respond, sometimes you need to find other ways to get things going. Isabelle had learned how to cc:ing her manager so that her manager could stay updated, but she wasn’t comfortable with cc:ing the other person’s manager because it felt like escalation. If done tactfully, though, escalation can be a good tool.

How to escalate: Give people the benefit of the doubt, and acknowledge that they might be busy working on priority projects. Send them a gentle reminder, cc:ing their manager. In the note, explain to the manager that you understand that the original contact may be busy or your request might be a better fit for someone on the team, and ask who might be the best person to talk to.

Hope that helps!

2010-08-24 Tue 10:20

Short URL: http://sachachua.com/blog/p/7320
  • Raymond Zeitler

    Great advice. About #5, I’ve had managers request a cc every time I’d e-mail their subordinates. They don’t want someone on their team who lets things slip. And it helps the managers plan the work.

  • http://sachachua.com Sacha Chua

    Absolutely! A comment on my internal blog shared a similar insight – if you see managers as people who can help with resource allocation, it makes perfect sense to reach out to them when you might be dealing with someone who’s overloaded. It’s not about getting the other person into trouble, it’s about helping the team work more effectively.

On This Day...

  • 2012: Paint-the-shed weekend — We painted the shed. Level up – I learned more about proper brush technique when painting edges, although my first [...]
  • 2011: Practising drawing — I didn’t grow up drawing. Now’s as good a time as any to catch up. Here’s me working through chapters [...]
  • 2011: Mailing non-Emacs users your Org notes — Andras uses Emacs Org-mode to take notes during meetings, and wanted to know how to share those notes (including tables) [...]
  • 2009: Improv 101, class 4: Characterizations — It occurred to me that I hadn’t written about my fourth class in Improv, which was two weeks ago. (I [...]
  • 2009: Exercising my network — My manager is very much an extrovert. I think he’s amused by my reflections on networking as an introvert, the [...]
  • 2008: Weekly review: August 16 to August 23 — My second and last week in the Philippines was more relaxed, but it was just as enjoyable as the first [...]
  • 2008: Just ordered a tablet — I’ve just ordered the Cintiq 12WX, a 12.1″ pressure-sensitive tablet that also includes a screen so that you can see [...]
  • 2007: Weekly review — This week has been a tumultuous one. Trying to sort out lots of different issues took up a lot of my [...]
  • 2006: Starting your own business — @BarCampEarthToronto, Brooke Gordon, serial entrepreneur Business plan. You are trading money for value. You need to be able to clearly articulate [...]
  • 2006: Building a community — @BarCampEarthToronto: Search engine optimization Terrific idea! Ryan McKegney identified the top 1% in his RedFlagDeals.com community, rewarded them with stickers and [...]
  • 2006: Win-win-win: The power of asking — The problem with conferences is that I always, always run into scheduling conflicts. I really, really wanted to go to the [...]
  • 2006: BarCampEarthToronto: Search engine optimization — @BarCampEarthToronto: Search engine optimization I’m learning a lot from the session. Some points: Primary domains are better than subdomains because Google tries [...]
  • 2006: BarCampEarthToronto: Networking for Introverts — I ran a terrific session on networking for introverts at BarCampEarthToronto. I shared a few stories about blogging and conversation-starting [...]
  • 2006: Livening up your laptop lid: self-adhesive reusable surface — All you need to transform your laptop lid into a reusable surface where you can display your latest doodles are: one [...]
  • 2006: Sweeeet! WordPress.org bought ad space on my laptop! — Remember my crazy idea to sell advertising space on my laptop during BarCampEarthToronto? Well, Matt Mullenweg of WordPress.org – *WORDPRESS.ORG!* [...]
  • 2005: Begging for money on a street corner — Begging for money on a street corner was a lot more tiring than I expected. Starving grad student looking for alternative [...]
  • 2004: Another KittenWhoMustNotBeNamed ! — Dearest Sacha, As Kathy would say, it was raining little animals yesterday. Papa was on his way home from a meeting when [...]

Get the highlights as a PDF!

Stories from my Twenties: Highlights from a Decade of Blogging

Free sample!