When your project team is scattered over multiple time zones,
just telling each other when something is supposed to happen
can become confusing. "I'll call you at 3" just won't
do. Which time zone did you mean? AM or PM? Adopting a conventional
way of referencing times eliminates confusion and makes life
easier for everybody.
f I normally work in Boston, and Jim normally works
in San Jose, and Rachel normally works in Austin, we live in
three different time zones. When we talk to each other pairwise,
and cite specific times to each other, we have to be careful
to avoid confusion. I might decide, for example, to always quote
my times in the Eastern time zone. And I might even be careful
about saying so: "I'll call you at 10 Eastern." When
I'm talking to Rachel, she has to subtract three hours to figure
out whether 10 Eastern works for her. I have to remember to say
"Eastern" and Rachel has to hear it, and remember that
Eastern is three hours ahead of her (not behind). If we both
do everything right, all is well. Then she has to shift gears
when she talks to Jim, because he's in Central.
Adopting a convention about how project team members quote
times to each other reduces the chances of confusion. If a project
team can pick a time zone that will be the project's time zone,
and always cite times in that time zone, life is easier.
There isn't much chance of confusion about time
zones in email headers or in software, because most software
is aware of the issue and can present times in a variety of formats.
The real problem happens in verbal communication and in text
that we type into documents and messages. So let's look at how
adopting a "Project Time" can save you trouble and
reduce confusion.
"Project Time"
is the conventional time zone that everyone agrees to use when
communicating with project team members. For example, if most
of the team is based in the Central Time Zone, it would make
sense to quote all times in Central Time. This does require that
everyone learn how to convert back and forth between Central Time and the zone
they're in. But that's all they have to learn.
Since nobody ever quotes a time in Eastern Time, somebody who
lives in the Pacific Time Zone will never have to make a conversion
from Eastern to Pacific. If you travel to another time zone away
from your home base, you'll have to start to make conversions
between Central Time and your temporary base. But that's your
responsibility, nobody else's.
Having a Project Time helps you avoid having
to know where everyone else is, and knowing how to convert the
times they quote. All you have to know is where you
are. And nobody else has to know where you are. All they
have to know is where they are.
Glitches are still possible, even when you decide
to have a Project Time. For example, sometimes people work on
two or more projects. One project might decide to use Central
Time, and another might decide to use Pacific Time. When this
happens, the people who work on both projects have to keep straight
which is which. To avoid this problem, quote project time by
its real name, rather than as "project time." For example,
if Project Time is Pacific, say "The conference call is
at 10 am Pacific Time," rather than "The conference
call is at 10 am Project Time." This makes it easier for
people who work multiple projects.
What alternative
approaches are there?
There are a few alternatives to Project Time:
Always cite times in the listener's time zone, adding the name of the zone
Always cite times in my own time zone, adding the name of the zone
If you use the listeners' time zones, you face several problems:
There could be more than one listener, and they could be
in different time zones. This can happen in a conference call. Which one do you choose?
The listeners might not be at their own home bases. They could
be visiting another time zone temporarily, and you might have
to correct for that on the fly. Unless you're very, very good,
you'll eventually make a mistake. And you have to keep track of what zone they're in, too.
You might not know the listeners' time zones.
You might think you know the listeners' time zones, but you could be mistaken.
If the team is international, you might not be familiar with
everyone's time zones, and daylight savings time conventions
vary around the world.
Using your own time zone instead is also problematic:
You might not be in your home time zone.
The listener might not know your time zone, so you have to
remember to identify it.
You put the responsibility on the listener to convert from
whatever time zone you use to wherever they are, and to know what your daylight savings time conventions are. They might not
know how to do that. After you cite a time, you can sometimes
see them glaze over and lose the thread of the conversation as
they punch the calculation into their mental calculators.
Both of these approaches are more likely to lead to confusion
than using Project Time.
What is Zulu time?
The US Military has had to deal with this same problem for many years. They long
ago adopted what they call "Zulu" time. Essentially,
Zulu is the time at 0° of longitude, at the Royal Naval Observatory
in Greenwich, UK. Zulu time is actually a time called Universal
Time (UTC), if you're interested in the technicalities. If your
team is international, and especially if you work with the military
or if your team spans the prime meridian, Zulu time is a good
choice for Project Time. But if nobody on your team actually
uses Zulu, it's probably better to pick the time zone that most
people use.
Questions, suggestions, experiences to share?
Nightmare stories you'd like me to add to this essay? Contact me to discuss your specific situation, by email at rbrenner@ChacoCanyon.com or by telephone at (617) 491-6289, or Toll-free at (866) 378-5470 in the continental US.
Reprinting this article
Are you a writer, editor or publisher on deadline?
Are you looking for an article that will get people talking and get compliments flying your way? You can have 500 words in your inbox in one hour. License any article from this Web site. More info
Projects never go quite as planned. We expect that, but we don't expect disaster. How can we get better at spotting disaster when there's still time to prevent it? How to Spot a Troubled Project Before the Trouble Starts is filled with tips for executives, senior managers, managers of project managers, and sponsors of projects in project-oriented organizations. Check it out!
The key to managing virtual or global teams is creating a sense of team despite the obstacles of separation. Read my tips booklet, 303 Tips for Virtual and Global Teams, to learn how to make your virtual global team sing. Newly revised and updated for 2008! Check it out!
Are your projects always late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips & techniques for organizational leaders. Check it out!
Are you doing work you love? Are you less in love with the job? Bad boss, long commute, troubling ethical questions, hateful colleague? Read Go For It! Sometimes It's Easier If You Run to learn what we can do when we love the work but not the job. It helps you get moving again!
A Tip a Day arrives by email each business day. It's 20 to 30 words at most, and gives you a new perspective on the hassles and rewards of work life. Most tips also contain links to related articles. Free!
Do you ever wonder if all these meetings are really necessary? (They aren't) Or whether there isn't some better way to get this work done? (There is) Read 101 Tips for Effective Meetings to learn how to make meetings more productive — and more rare. Check it out!
Are you fed up with tense, explosive meetings? Are you or a colleague targets of a bully? Read 101 Tips for Managing Conflict to learn how to make peace with conflict. Check it out!