Blog

At work weā€™re making a collective effort to get better at responding to messages in a more prompt manner.

Iā€™m sure my boss Matt appreciates the helpful countdown timer I attached to my most recent email to him, then.

Or maybe Iā€™m doing it wrong?

Blog

At work weā€™re making a collective effort to get better at responding to messages in a more prompt manner.

Iā€™m sure my boss Matt appreciates the helpful countdown timer I attached to my most recent email to him, then.

Or maybe Iā€™m doing it wrong?

Blog

How email became the most reviled communication experience ever

This is an interesting read.

At Google I/O in 2009 Google introduced Google Wave, a re-imagining of email. I still maintain this was a much better tool for business communication than email is. The product was killed off only about a year later. Wave had some great technology, but Google failed to even try to sell it to the enterprise. Ultimately the problems Wave solved werenā€™t technical ones, they were business ones.

That all being said, is the way to solve the current problems with email overload really to replace it with a different tool? I donā€™t know the solution, but I certainly agree thereā€™s a problem.

How email became the most reviled communication experience ever

Blog

Prevent Forwarding, Replying or Reply-All in Outlook

About a month ago I wrote a post that detailed how to prevent attendees from forwarding your Outlook meetings to other people.

Since then Iā€™ve expanded upon it slightly on my own computer: in addition to the option to prevent meetings from being forwarded, Iā€™ve added similar buttons to the new email toolbar that can prevent forwarding, replying or replies to all.

Preventing people from hittingĀ ā€œreply allā€ is sometimes a great tactic if youā€™re sending an email to particularly large group and you donā€™t want everybody to get caught up in any follow-up. By contrast, preventing replies (thus forcing people to use ā€œreply allā€ instead) is great if you want the opposite, and for everyone to be kept in the loop.

My previous post details the process of setting all this up, but below is the code for the four macros. The first disables forwarding, the second disables replies, the third disables reply all and the final re-enables all response options. By default, nothing is disabled on new items unless you hit the relevant button to run the macro.

Enjoy!

Sub DisableForwarding()
    ActiveInspector.CurrentItem.Actions("Forward").Enabled = False
    X = MsgBox("Forwarding of this item has been disabled", vbInformation, "Forwarding Disabled")
End Sub

Sub DisableReply()
    ActiveInspector.CurrentItem.Actions("Reply").Enabled = False
    X = MsgBox("Replies to this item have been disabled", vbInformation, "Forwarding Disabled")
End Sub

Sub DisableReplyAll()
    ActiveInspector.CurrentItem.Actions("Reply to All").Enabled = False
    X = MsgBox("Reply All has been disabled for this item", vbInformation, "Forwarding Disabled")
End Sub

Sub EnableAllResponses()
    ActiveInspector.CurrentItem.Actions("Forward").Enabled = True
    ActiveInspector.CurrentItem.Actions("Reply").Enabled = True
    ActiveInspector.CurrentItem.Actions("Reply to All").Enabled = True
    X = MsgBox("Forwarding, Replies and Reply All have been enabled for this item", vbInformation, "Forwarding Disabled")
End Sub
Blog

Meeting Pre-Work (and Why Iā€™m Bad at It)

Last week I linked to and wrote about an article
that gave some tips on running effective meetings.

In addition to posting it here I also posted it, in advance,
to my workplaceā€™s internal social media platform to share it with my team and
get their thoughts on meeting best practices.

My boss Matt
commented that one of his tips was to highlight any meeting pre-work that may
exist: information that participants need to bring with them to the meeting, or
documents they should review in advance, for example. Matt suggested that it
may sometimes even be worthwhile to go so far as to include these expectations
in big bold text within the invite so they jump out.

image

This was an interesting topic to me, because I am certainly
an occasional offender in this regard.

Basically, if you send me an email that includes a call to
action
then I will notice it and deal with it appropriately. I may not take
the requested action immediately, of course, but Iā€™ll flag the email for
follow-up when I know Iā€™ll have time to get it done, or maybe even schedule
some time in my calendar if the situation warrants it.

A calendar invite is different, though. No matter how hard
you try and how good your writing skills are, the instruction in the body of
the invite is not the primary call to action when I receive it: instead, thatā€™s
something thatā€™s defined for me by Outlook (or your client of choice) which is
demanding that I choose to accept, tentatively accept or decline the invite
itself. Once Iā€™ve done one of those things the invite is forever gone from my
inbox, and the meeting (along with whatever instruction you provided) is now on
my calendar.

Iā€™ll get to your email on whatever schedule my workload
allows for, but my calendar by its very nature is a schedule, and it tells me when I should get to something. The
next time Iā€™ll look at your meeting invite is probably going to be two minutes
before it starts, when Iā€™m looking for conference line details or checking
which room itā€™s in. By then of course itā€™s too late.

Recently Iā€™ve started employing a new trick to deal with
this kind of thing for meetings that I host. First I send an email to the group
explaining what needs to be done (pre-work), suggesting that we collectively
discuss to share our thoughts, and mentioning that I will set up some time to
achieve this. Then I immediately follow-up with a meeting invite, into which I
embed that first email.

I havenā€™t heard any comments, good or bad, but it seems to
be working.

What does everyone think, though? Am I spamming people and
over-contributing to their already burgeoning inboxes? Am I solving a problem
that people donā€™t actually have and unfairly assuming that everyone shares the
same lack of organizational skills that I possess?

Let me know in the comments below, or contact me!

Blog

The Trials and Tribulations of my Connected World

Iā€™ve written many times on this blog about ROWE (the results only work
environment). Itā€™s the structure under which I work, and Iā€™m a big fan. One of
the key tenets of ROWE is that itā€™s available to everyone: itā€™s not something
reserved for those at a certain paygrade, itā€™s not restricted to leaders, itā€™s
not something you have to apply to be a part of, or provide some kind of
justification of your particular circumstances to gain entry. There should be
no barrier to entry.

When I first
wrote about ROWE on this blog
, I lamented that at my organization there is
a barrier to entry, to a certain extent. Not by design, but simply because our
communication mechanisms are restricted by our firewall and access to them from
outside the corporate network is barred. The barrier to entry, as I see it, is
having a company-issued cellphone. If you have one you can be available from
wherever you might happen to find yourself, and if you donā€™t youā€™re tied to
your computer.

I didnā€™t have a company-issued cellphone when I wrote that,
but I do now. There it is above. Itā€™s the one with the darker wood effect
amongst my bamboo effect personal devices.

I love it, and I hate it. I donā€™t want it, and I wouldnā€™t
give it back. Read on to learn why!

Why I Love It, and How it Supports ROWE

Quite simply, when I thought not having this device
constituted a partial barrier to ROWE entry, I was right. Last week Flo and I
went to Winnipeg and I worked from there for the week. I spent most mornings
sitting in Floā€™s sisterā€™s kitchen working at my laptop, then weā€™d typically go
for lunch together and Iā€™d spend the afternoons with my extended family. I was
available throughout to respond to emails and IMs. If somebody called my office
phone number then their call was seamlessly forwarded to the phone in my
pocket. Most of the work people I interacted with would have had no idea I wasnā€™t
at my desk, let alone that I wasnā€™t even in the same time zone. That wouldnā€™t
have been possible if I didnā€™t have this phone.

Why I Hate It, and How it Contradicts ROWE

The point ROWE is that Iā€™m an adult, and I work how, when
and where I choose to. I could be
working at any time and from any place. Having the phone feels a little bit
like I am working at all times, from all
places. Essentially having the phone means the thing I find most challenging about
working in a ROWE ā€“ knowing when to switch off ā€“ is magnified exponentially.
Obviously the phone has an ā€œoffā€ button and, being an adult and all, I am free
to use it as I choose, but I simply donā€™t find it as easy as that. Take last
week as an example: when I was out spending my afternoons with family every now
and then Iā€™d receive a work-related message of some description. I probably
dealt with 80% of them right away, because 80% of my job is more about getting
the right people in contact with one another than it is about actually doing
something myself. The remaining 20% I flagged to deal with the following morning.
The inward flow of these messages is not overwhelming, but it is constant. If I
disconnect entirely, even for an afternoon, the sheer volume of stuff that
builds up is overwhelming. I donā€™t
like to feel overwhelmed, so I keep my phone on because itā€™s easier to take a
couple of minutes out of what Iā€™m doing a few dozen times than it is to try to
deal with a few dozen things at once when I eventually choose to reconnect.

There are certainly times where I hate remaining available
and connected and doing so gets in the way of other things Iā€™m doing at that
moment, but despite that the logic above kicks in and even when I need a break
I end up being reluctant to take one. And, as I mentioned, the inward flow of
messages really is constant. With most of the people I work with also being in
a ROWE it starts at about 6am and continues until about 1am, each one bringing
with it a little ā€œdingā€ noise. I feel like Pavlovā€™s dog sometimes.

Why I Donā€™t Want It

Despite the occasional strength of my negative feeling
toward my phone, none of that has anything to do with why I donā€™t want it. The
benefits outweigh the drawbacks, and the issues I have with it are a function
of my choices, not of the technology. I can get better with it, and over time I
will.

The reason I donā€™t want it is that I have a perfectly good
phone already. You may have noticed it in the photo up top: itā€™s the bamboo
effect one in the middle. Why do I need to carry two phones with me? Thereā€™s no
technical barrier to my company turning on the ability to support a ā€œbring your
own deviceā€ policy, and in fact the technology required is already in place. Itā€™s
disabled, because the policy is that the IT department wonā€™t allow you to get
email on your phone unless they have the ability to remotely wipe the whole
thing. Not just securely erase company data, but securely erase everything. I
assume this is a case of policy failing to keep up with emerging business trends.
Iā€™d think they must realise that weā€™re going to have to BYOD policy someday, so
I get hung up trying to understand why they wonā€™t just get it done right away.
Iā€™ll continue to advocate for a BYOD policy in my workplace, exceptā€¦

Why I Wouldnā€™t Give it Back

My inability to switch off was a minor problem when I
carried a laptop. When that laptop was supplemented with a phone it became a
bigger problem. If that work-only device were replaced with an app on my
personal device through which I access work stuff? It could be disastrous. I
never switch my work phone off, but I do leave it at home when we go out
somewhere in the evening or on weekends. I take my personal phone with me
everywhere though. I assume that BYOD technology includes functionality that
would let me turn ā€œworkā€ off while keeping ā€œpersonalā€ switched on, but am I
disciplined enough to use that function? Probably not.

Blog

If you’re a regular reader you may or may not have already guessed that I typically write these posts in advance and then set them to publish on a schedule. It’s not really a hard and fast rule, but if I have a couple of posts to publish in a week then I’ll usually schedule them on a Tuesday and a Thursday at the start of the workday here in the Mountain timezone so that they catch the end of the workday in Europe.

The reason I mention this is because the post I published yesterdayĀ ā€“Ā Voicemail: A Beginner’s GuideĀ ā€“ was actually written last Sunday before I left for my business trip. As it turns out it was extremely prophetic because I spent Tuesday and Wednesday with other leaders from my workplace talking about our culture and how we become better at leveraging the values we already hold, ensuring that the work we do for our internal customers (all my customers are internal) translates correctly and has a positive impact on our end-user customers.

The session was excellent and hugely valuable, and I’m not doing it justice in my description.

I mention it mostly because the overuse of email and the underuse of the phone became something of a common theme, as did intentionality and using your own behaviours to drive the right behaviours in others.

Great minds think alike, hey?

Blog

If you’re a regular reader you may or may not have already guessed that I typically write these posts in advance and then set them to publish on a schedule. It’s not really a hard and fast rule, but if I have a couple of posts to publish in a week then I’ll usually schedule them on a Tuesday and a Thursday at the start of the workday here in the Mountain timezone so that they catch the end of the workday in Europe.

The reason I mention this is because the post I published yesterdayĀ ā€“Ā Voicemail: A Beginner’s GuideĀ ā€“ was actually written last Sunday before I left for my business trip. As it turns out it was extremely prophetic because I spent Tuesday and Wednesday with other leaders from my workplace talking about our culture and how we become better at leveraging the values we already hold, ensuring that the work we do for our internal customers (all my customers are internal) translates correctly and has a positive impact on our end-user customers.

The session was excellent and hugely valuable, and I’m not doing it justice in my description.

I mention it mostly because the overuse of email and the underuse of the phone became something of a common theme, as did intentionality and using your own behaviours to drive the right behaviours in others.

Great minds think alike, hey?

Blog

Voicemail: A Beginnerā€™s Guide

This week Iā€™ve been travelling for work. I left Calgary early Monday morning, and I returned home late last night.

On Sunday night as I was preparing for my trip I briefly considered setting an ā€œout of officeā€ email alert and changing my outgoing voicemail message to advise people of my unavailability. I quickly dismissed this plan though, for the simple reason that I really wasnā€™t all that unavailable. Sure I was away from my physical desk in Calgary, but I rarely work from there anyway. And sure my calendar was full, but thatā€™s not unusual either. Setting up unavailability alerts would have been a misuse of the tools available to me.

As I was thinking about all this, it put me in mind of a post I wrote about seven months ago titled Weird Workplace Etiquette. In it, I complained about the fact that nobody just picks up the phone and calls me without first sending me a message (or worse, booking some time in my calendar) to ensure that Iā€™m going to pick up the phone and talk to them.

Now that Iā€™ve had some time to think about it, the reason seems obvious to me. We can lay blame firmly on voicemail. Subconsciously or otherwise people hate it, because everybodyā€™s had a bad experience with it. Think about how it normally goes between a couple of busy people ā€“ you leave a voicemail for me in which you ask me to call you back, I call you back and get your voicemail, and so it continues ad infinitum.

Happily, this is pretty easy to fix in my opinion, and the ROWE course I took not too long ago teaches us the way: itā€™s merely a matter of breaking some bad voicemail habits that almost everyone has. Even more happily, you (mostly) donā€™t need other people to read my advice ā€“ you only need concern yourself with what you do. If you do it right, others should fall into line.

Read on to get started!

Everything starts with your outgoing voicemail message. What does it say now? I assume itā€™s something along the lines of ā€œIā€™m sorry Iā€™ve missed your call, please leave me a message and Iā€™ll get back to you.ā€ To be blunt, thatā€™s not good enough.

Firstly, youā€™re not sorry youā€™ve missed somebodyā€™s call. You were busy doing something more important than picking up the phone, and thatā€™s OK! Apologising for it is a meaningless platitude and everyone knows it, but more importantly it sets the wrong tone for what weā€™re trying to accomplish. Youā€™re a (wo)man of action, not the kind of person who spews forth wet apologies for failing to be idly sitting around by your phone when somebody somewhere kind of vaguely hoped thatā€™s what you might be doing. If anything, you should apologise when you are available to answer the phone!

Instead, your outgoing voicemail message should reflect that yes, you were too busy to take the call and also yes, youā€™re too busy to engage an endless game of phone-tag. Instead of asking callers to leave you ā€œa message,ā€ be specific about what youā€™re looking for from them.

ā€œYouā€™ve reached Jason. Please leave a message detailing how I can help you and by when you need a response, and Iā€™ll get back to you as appropriate.ā€

The same goes for when youā€™re leaving a voicemail for somebody. Just because their outgoing message is vague doesnā€™t mean the message you leave for them should be too. Think about how you want somebody to react when they listen to your message. Do you want them to immediately get to work on what youā€™re asking of them, or do you want them to have to call you back and speak with you first so they can find out what you needed? Tell them what you want, and tell them to get back to you once they have it!

Iā€™ve been using these tips for a little while now and I have to say theyā€™re working well for me. Voicemail is a vastly improved experience as a result ā€“ although itā€™s still under-utilised, because people still do all they can to avoid using the tool at all if they can at all help it. Most people never even get to hear my outgoing message and come to the realisation that Iā€™m changing their lives for the better.

Regardless, the more I think about it the more I think I may actually kick things up a notch. Long-time readers may recall another post on this blog from the distant past in which I talked about how people (me) canā€™t possibly hope to read, understand and respond to every email they get in as timely a fashion as they might like. Email, in a typical workplace (certainly in mine) is a vastly overused tool. Voicemail, though? Thanks to everybody shying away from it, a voicemail is out of the ordinary and will get somebodyā€™s attention. If I can do voicemail well, it could become a fantastic method for making my messages to people a higher priority than everyone elseā€™s.

All Iā€™ll have to concentrate on is not using it for evil.