IT Workers to Management: NOW Can We Telecommute?
IT helps others to work remotely but rarely gets to join in. Is that fair?
Crumbling infrastructure, increased traffic congestion, urban sprawl that extends to the hinterlands, more frequent superstorms bringing sustained damage -- more than ever, getting from home to work can be a dicey proposition.
This could well be telework's finest hour. According to the Telework Research Network, the number of teleworkers jumped 57% between 2005 and 2012, from 1.8 million to 3.1 million.
So are IT employees at last being allowed to join in? The answer, according to a range of telecommuting consultants and IT executives, is "it depends."
In the earliest days of telecommuting, the gating factor for all workers was technology: You could take a floppy disk home and work on a document, but not much else. Those barriers have long since fallen, telecommuting consultants and IT executives confirm. With the ubiquity of broadband networking, VPNs, Skype, Web-ready cameras, videoconferencing and the explosion in ownership of personal mobile devices, most technological barriers to telework have long since fallen for many workers.
Similarly, the nature of both work in general and IT specifically has changed as well. In a world where corporations are functioning with fewer people wearing more hats, whose job is tied to one office or one location anymore? In a globalized world, whose colleagues sit close by? In a world of cloud and colocation, of offshore and nearshore developers, what's "remote"?
In short, sweeping technological and cultural change has finally shifted the attitude toward working remotely, says Gil Gordon, a consultant, now retired, who has followed the telework movement for decades. "There is [now] a basic understanding that people can work together without being physically together," he says. "Offices will never become extinct, but the notion of mobility is entrenched."
For IT specifically, globalization, outsourcing and the increased use of colocation facilities has made the idea of a dispersed workforce seem reasonable rather than radical, Gordon says.
The remaining barriers to telecommuting for IT workers are more managerial and procedural than technical, agrees David Annis, CIO of Garvin Promotion Group inScottsdale,Ariz., who has seen IT telecommuting succeed and seen it fail. It's his opinion -- shared by other IT leaders and rank-and-file tech workers -- that those barriers are by no means impossible to overcome.
In at least some IT departments, barriers need to fall fast, because workers with in-demand tech skills have become more demanding. "Some companies that have never offered telecommuting before for their IT staffs are now considering it," says John Reed, senior executive director for Robert Half Technology, an IT executive search firm. The reason is simple: IT applicants are rejecting jobs that don't offer telework as an option. (Indeed, inComputerworld's annual Salary Surveys, telecommuting consistently ranks in the top five job priorities for respondents.)
Which techies get to telecommute?
Does that mean CIOs can simply fling open the doors to the enterprise and set their people free? Not exactly, experts caution.
In deciding who can and can't work remotely, sources agree that it depends on the employee's level of hands-on work and collaboration. "Supervisory roles, roles that involve hardware management or strategy and business planning -- those people need to be close to the action," says RHT's Reed. "Roles that require writing code and doing phone-based technical support are easier to do remotely."
That means anyone dealing with deskside support -- never. Business analysts and project managers charged with collaborating with users -- rarely. IT managers -- rarely.
Annis agrees that it's "difficult, but not impossible" for IT managers to work remotely. What's more feasible is telecommuting once a week. "It's important that I'm here," he says. "I'm the eyes and ears of development" -- which means it's important for him to interact face-to-face with the business side when necessary. Occasionally, though, he'll steal away from the office to work on a specific project.
In fact, many CIOs who have implemented telework for their IT staff recommend this. "Any work that requires your full concentration but does not require collaboration is better suited to be done off-site," says Niraj Jetly, CIO at Edenred USA, theU.S. division of a global developer of employee benefits and incentive solutions inNewton,Mass.
"A task that requires four to five hours of concentration can easily take two business days in the office," Jetly observes. "If I have to write an RFP response, and I've already brainstormed with the functionality team and I just need to write it down, it's ideal to do it from home."
That said, there's one group of employees who shouldn't work remotely, regardless of their job responsibilities: employees whose productivity drops off outside the office. This happens for several reasons, IT executives say.
Sometimes employees lack an isolated workspace at home and can't escape family members, pets and other distractions. "For some people, the office may be quieter than the house," says Peter Campbell, senior vice president of IT at Sprint inOverland Park,Kan.
Other employees lack the discipline to work without physical supervision -- which they're sometimes aware of, though not always. "Some employees will self-select out of telework," says Nancy Crouch, deputy CIO at Wake Forest University in Winston-Salem,N.C. "They'll admit they're not disciplined."
Other times, the discovery process is more cumbersome. Annis revoked the telecommuting privileges of a couple of employees who didn't perform when they were first given such privileges, then ended up terminating those employees later when they couldn't perform internally either. "Telecommuting wasn't the issue," says Annis. "It was their work ethic."
Telework as a corporate problem-solver
At times, telework isn't just a perk for deserving employees but a problem-solver for the organization.
For example, Sprint uses telecommuting to address overcrowding. More than 30% of the 2,500 IT staff members work from home on any given day, saysCampbell; up to 70% either work from home either permanently or periodically. That includes everyone from hourly to salaried workers.
"We were crowded," Campbell reports. "With the confluence in interest in working remotely, improvements in unified communications technology and the reality of our physical space constraints, we set up hoteling facilities in our headquarters with whiteboards and beanbags."
"It's had a tremendous impact on our real estate requirements in IT, and we've gained significant savings."Campbell doesn't have a figure solely for IT, but companywide, he estimates $30 million in real estate savings overall.
Other times, a remote workforce is the only workforce a company can attract. Annis knows this situation all too well from his experience as senior vice president of IT at his previous employer, Scottsdale, Ariz.-based Universal Technical Institute (UTI). It used Progress Software for application development, but developers were not easy to find. "We couldn't convince enough of those developers to move toPhoenix," he says. "If we had an open position, and the applicant was inTampa, it didn't matter."
Eventually, somewhere between one-third and one-half of the developers, project managers and quality assurance staff were remote. UTI flew its remote Progress developers intoPhoenixevery six to eight weeks in order to foster relationships, which kept everyone connected and collaborative.
Experts give that strategy high marks. Organizationally, it's important to schedule regular confabs for remote employees, they say -- everything from quarterly in-person meetings to a regularly scheduled weekly check-in call between employee and supervisor. Sometimes, as with agile scrums among developers, a daily call works best to assess progress.
All those strategies help reduce the danger of invisibility to remote employees, RHT's Reed says. "If you work remotely all the time, you miss the opportunity to engage, to build camaraderie, to take part in face-to-face meetings. There's a danger to being out of sight and out of mind. You may still have to make yourself available, and make time to be in the office."
“Philosophically, and in terms of architectural viewpoints, CIOs have realized that the software-defined enterprise or software-defined datacenter has arrived. However, mass adoption of Software-defined Data centers will take time.”
CISOs have been hearing for some time now that they need to learn how to "speak the language of business" better. It is one way to gain respect and avoid being viewed mainly as a scapegoat.
When the Cloud Security Alliance (CSA) launched in 2008, the questions around cloud computing centered around whether cloud was secure enough to be trusted, how it could be managed securely and in such a way as to keep regulators happy. There was also plenty of talk about whether cloud would fully displace traditional enterprise data centers.