13 Jul 2008 09:42 PM EDT
[ Tags: green ]

Most of what is written on Green IT concentrates on how the IT Department can reduce the carbon footprint of its operations, primarily through reducing Data Center power consumption. While this is important as IT operations makes up 2-3% of global power consumption, our efforts to reduce our environmental impact should not end with the data-center. As well as including the end-point into Green IT planning (something I covered in a previous entry), IT can have a role in enabling Green business practices such as the paper-less office, Remote Collaboration (thus reducing the need for business travel) and Telecommuting.

Its this last practice, Telecommuting, which I want to discuss in more detail. For one thing, its something that we can do as individuals (work and management permitting, of course) as well as on a cross-company, cross-industry and even national basis. It fits in with the "think globally, act locally" mantra, with the emphasis on "local".

The Telecommuting trend has for some time been more tied to employee satisfaction, work-life balance and increasingly recruitment strategies (such as "homesourcing"). However, the rapid increase in the price of oil has made the cost of commuting to work a much larger percentage of household budgets, and therefore more noticeable to the average Joe or Jane. While many of us may wish that people would find other motivations to reduce their carbon footprint other than the hip-pocket nerve, rising costs will probably have the most realistic chance of effecting widespread change.

Increasing the number of employees that telecommute rather than drive to the office can cause a significant reduction in the fuel consumption, and therefore carbon emissions, of those individual employees. While this may seem obvious, you can read a detailed study conducted by the University of California....back in 1988! As well, more recent EPA studies have shown that even a 10% reduction of cars during peak hours can reduce the fuel consumption of those vehicles still traveling to the office, as the improved traffic flow results in less time burning fuel in gridlock. To get an idea of how this works, think about how much better your own commute is during school vacation periods.

While this shows there there would be significant benefits to the environment if a greater proportion of the workforce spent at least some time of the working week telecommuting, how practical is this generally, and in specific job roles? If your job does not involve "face time" with customers, telecommuting is probably a more practical option for you than those involved in regular customer interaction. That being said,  there are a number of organizations allowing call-center agents to work from home, such as Cox Communications.

While I have regularly telecommuted over the last decade or so, as well as introduced telecommuting programs for employees doing Tech Support and Customer Care, I have decided to use a period where I need to work remotely to try to measure (at least to qualify if not to quantify) the effectiveness of the technologies used to enable telecommuting. Over the next few weeks, I will blog on my experience based on the following criteria:

  • Voice: How can I remain in verbal contact with staff, colleagues and customers? How do they get in contact with me without having to know whether I am in the office or not?
  • Applications: How does my app performance vary when not in the office? What impact does occasional offline access make to this?
  • Security: What would happen if my laptop or home PC was stolen or otherwise compromised? How do I set up my physical facilities to minimize security risks?
  • Collaboration: How important are those "water-cooler" discussions and other face-to-face formal and informal interactions? If they are important, how do you replicate this when remote?

I have experienced challenges with each of these criterion in my own experiences as well as those relayed to me be customers.
While most of the technologies I will be using come from Citrix (partly because we like to eat our own dog food but mainly because we have been a long-time enabler remote work practices such as telecommuting), I will be also looking at other products and technologies to fill any gaps or compare.

I mentioned earlier that I want to use this as an opportunity to discuss telecommuting. As such, I would really appreciate your comments and suggestions on what I should be testing (technologies, criteria and scenarios), what your own experiences have been, and whether you think an increased proportion of your work time as telecommuting would have a benefit to you, your employer, customers/partners and the environment. Please contribute to this discussion by posting comments to this entry. In a later entry I will add a forum address if there is sufficient interest in this topic.

Permalink | Comments (5) |

James,

Great article and very timely topic since many organizations are looking to be more "green" and at the same time many organizations are also trying to figure out pandemic planning exercises that largely relies on working from home.  I think Citrix can do a lot more to assist in this regard to provide managed state detection for online, slow link (either low bandwidth or decent bandwidth, but high latency), or fast link and then make an application available in an appropriate way (streamed or via XenApp).  All we have today is dual-mode streaming, which frankly is useless because it doesn't take into account network conditions.  Thoughts?

Shawn

Thanks for the comments and suggestions, Shawn. I agree with what you say about being able to determine the most appropriate application delivery method based on network state. I'd actually go beyond that by saying that the "Nirvana" solution would also include extending the capabilities we have in SmartAccess to base that delivery method on the end-point state as well as that of the network connection.

A common complaint from end-users is that "I have to change the way I get to my apps and data when I am different places". We tend to assume that as it is easy for us to remember to VPN in and use a particular delivery method based on location and network state, that our less tech savvy users find it as logical as we do. We expect them to make a technical assessment of their local infrastructure and then configure their session settings and steps. Why?

This becomes even more of a problem during pandemics or even the more common minor workforce disruptions results in users with little or no experience in remote access suddenly having to work out how to stay connected. Those "lucky" enough to know the external number for the IT helpdesk invariably swamp the helpdesk with calls.

Having a mechanism that can analyze the users situation and then seamlessly connect them would probably reduce the number of help desk calls (especially for occasional teleworkers) and improve user satisfaction. While their app experience won't be 100% consistent across the different delivery methods, at least their method of getting access would be.

Does this approach make sense to you? 

I'll see if I can rope in some of our App Receiver and Access Gateway folks into this conversation to get their views and (hopefully) plans. 

James. 

Good idea, James.  I think it depends on the team and type of work.  I'm curious about the impact telecommuting has on the "intangibles."  For example, if your department doesn't really have a good telecommuting plan or culture in place, there's the risk of being "out of sight, out of mind."  I also think, in some organizations, there still might be a negative connotation with telecommuting...that managers question the productivity level of telecommuters.

So, during your research, it'd be great if you could record the impact telecommuting has on the "office dynamics" and other   For example, did you feel more out-of-the-loop?  Did communication between you and other team members decrease once you started telecommuting?  Were organizing and holding meetings more of a hassle? 

Posted by Anonymous at Jul 14, 2008 16:14 | Reply To This

Thats a really good point. Recently I read a report that showed that, while productivity of new teleworkers went up an average of 20%, their colleagues perception of their productivity went down! My own take on this is that many people are still caught up in the "what I see is all what happens", which I believe happens less in organizations that are geographically dispersed (thus used to working with people who "aren't there").

About 7 years ago, I started allowing certain staff to work from home a few days a week. This was pretty new to me as well as most people in the office. To address their and my own concerns, I started to measure (and report on) these workers by their output rather than activities. This approach actually helped me become a much more effective people manager for my "local" and remote staff, which was important as within 2 years I was directly managing staff in 6 offices as well as pure telecommuters.

For telecommuting to properly work, a similar change in mindset needs to happen with staff as well as management. This being said, I also like your suggestion on measuring the team dynamics and effectiveness of communication and interaction during the weeks that I am telecommuting. At this point, I think the 2 critical issues will be "water-cooler conversations" and not having visual contact when talking to people. My plan is to use the phone to talk more often where normally email would do. I am also interested in using IP video conferencing tools like Alice Streetfor "face-time".

Sounds good!  Yeah, I couldn't think of every possible impact, but you get the gist of it.  Personally, I like being in the office for the interpersonal communication, but due to the nature of my work, there are times when I'd like to be isolated to avoid interruptions, distractions, etc. 

Also, if your department meets frequently, meeting equipment can be an issue--some conference rooms just don't have good telephony equipment.  Sometimes it's a hassle to dial in and attempt to hear people in the room.  Obviously, something like Cisco Telepresence would be ideal, but of course, the cost makes it out of reach for many organizations.  I'm going to check out that Alice Street though.  But this day and age, connectivity should not be an issue. 

Posted by Anonymous at Jul 15, 2008 09:52 | Reply To This