21.02.2013 Views

Cisco - TABPI

Cisco - TABPI

Cisco - TABPI

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

NEWS&ANALYSIS<br />

Peter Coffee: Port Scans<br />

The case for rest<br />

As i looped around the east edge of phoenix,<br />

heading home from the GigaWorld IT Forum,<br />

I heard NPR’s salute to National Night Shift<br />

Workers Day conclude with a poem by Karen<br />

Jane Glenn. “Let us now praise the night shift,”<br />

she began. “Those on the 8-to-4, the 10-to-6 ... the sleepdeprived<br />

... the wired.” I could relate. It seems as if every<br />

week brings me more e-mail messages that are timestamped<br />

during the interval that Navy men call the midwatch,<br />

from midnight to four in the morning. And I<br />

have to admit that I’m also sending more of those<br />

midwatch messages myself.<br />

As it happened, the theme of the conference I’d<br />

just attended was “Deliver more with less.” I don’t remember seeing “less sleep”<br />

as a formal part of the agenda—but as I listened to Glenn’s poem, it seemed as if<br />

that topic should have been addressed. After all, National Science Foundation<br />

statistics estimate U.S. adults averaging<br />

less than 7 hours’ sleep at night;<br />

other studies point to sleep-deprivation<br />

effects that include difficulty following<br />

discussions; poor judgment in complex<br />

situations; difficulty in devising a<br />

new approach to a stubborn problem;<br />

and failure to notice changes in situations.<br />

In practical terms, this means that<br />

people aren’t functioning as well as<br />

they should in everyday situations<br />

such as planning a project, responding<br />

to a cyber-attack, debugging an application<br />

or monitoring network operations.<br />

Spread thin by staff reductions, and<br />

losing formerly productive time to diversions<br />

such as extra security delays in airports,<br />

people are putting in 10-hour and<br />

even 20-hour days for what used to be<br />

considered 8 hours’ pay. That may not<br />

be as good a deal for the employer as<br />

it first seems, if the extra hours represent<br />

neutral or even negative contributions.<br />

Yes, it’s great that people can work<br />

at any time, from anywhere, but sleepdeprived<br />

zombies aren’t the shock troops<br />

40 eWEEK n MAY 26, 2003<br />

of enterprise success—whether they’re<br />

“the wired” of Glenn’s poem or not.<br />

International operations can approach<br />

the 24-hour day as a relay race, rather<br />

than a marathon. IBM, for example,<br />

has adopted a two-shift approach to some<br />

of its software development efforts, with<br />

teams in Seattle setting daily work<br />

specifications for offshore teams in India,<br />

China, Latvia and Belarus. Overnight offshore<br />

development returns product to<br />

Seattle the next day for review, and the<br />

cycle continues.<br />

The company says this process<br />

reduces development cycles by 35 percent,<br />

yielding time-to-market benefits<br />

that are worth even more than the reduc-<br />

tions in development cost. Note well that<br />

this is not about stretching a given number<br />

of people across a greater number of<br />

hours: It’s about taking advantage of<br />

the 24-hour day in operations that circle<br />

the globe.<br />

The problem with success stories like<br />

this is that smaller companies may feel<br />

that they must do likewise. I’m reminded<br />

of former Avis CEO Robert Townsend’s<br />

warning that some corporate behaviors<br />

don’t scale well from large to small organizations.<br />

The smaller company that<br />

decides to open an office in Bangalore,<br />

or outsource some of its operations to<br />

a contractor in Tel Aviv, may find that<br />

it has blunted its competitive edge of<br />

being able to get close to its customers<br />

and thoroughly understand their needs.<br />

Being just like IBM, only a hundred<br />

times smaller, is like being a miniature<br />

elephant in an ecological niche that’s better<br />

suited to a fox.<br />

In organizations of every size, managers<br />

need to avoid letting IT push their<br />

people across the line that separates anytime/anywhere<br />

flexibility from all-thetime/everywhere<br />

expectation. When<br />

intermediate deadlines start being<br />

regarded as purely pro forma, and everyone<br />

knows that the real schedule<br />

squeezes three days on the timetable<br />

into a 24-hour all-nighter at the end of<br />

every product cycle, that’s a cultural<br />

problem that has to be solved by cultural<br />

forces. When managers treat<br />

crash-and-burn schedules as a sign of<br />

commitment and not as a problem to<br />

be fixed, that’s a cultural force that<br />

PETER_ COFFEE@ZIFFDAVIS.COM<br />

Sleep-deprived zombies aren’t the shock<br />

troops of enterprise success—whether<br />

they’re wired or not.<br />

pushes in the wrong direction.<br />

C. Northcote Parkinson was right:<br />

Work does expand to fill the time<br />

available. IT can make that available<br />

time appear to be “all the time.” I’m not<br />

saying that our e-mail systems need a<br />

curfew. I am saying that the human side<br />

of management includes making it clear<br />

that you want good hours, not just more<br />

of them. ´

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!