Weighing the Alternatives
By Carla Garnett
On the Front Page...
Is there anybody working here who wouldn't like an extra day off every week or so? Weekends are grand, of course, but if we had a weekday off, some of us think, we could get a head start on that seemingly endless line at the bank. We could take our rightful turn as Class Parent at Junior's pre-K, avoid that hellish Monday morning commute, log in some volunteer work we've always vowed to try or simply accomplish the myriad other tasks best done during "regular" work hours Monday through Friday. We wouldn't even mind working an extra hour or two each day to earn the day off.
These thoughts are certainly not new. In fact, according to a 1994 NIH Policy Manual by the Office of Human Resources Management, such meanderings of the mind -- formally dubbed "alternative work schedules" -- have been under consideration for government employees for more than a generation now.
Nothing New Under the Sun
"Since the mid-1960's," says the manual, "there has been a growing interest in nonstandard, more flexible work hours to relieve traffic congestion, improve productivity, expand hours of service to the public, and provide greater employment opportunities for those who cannot work standard fixed work hours." In 1994, spurred by a National Performance Review recommendation, President Clinton championed AWS in a memo, calling for "a more family-friendly workplace to be created by expanding opportunities for federal workers to participate in flexible work arrangements consistent with the mission of the executive branch to serve the public."
A number of NIH'ers, however, had already heeded the call.
"I began working AWS in 1990," recalls Beth Rosso, an administrative officer at NLM for the past 10 years. "I think it has changed the way I do my job, improving the organization of my 9-hour work days. It gives me the ability to prepare for my day off. Small segments of annual leave for personal business, or sick leave for doctor's appointments, have all but been eliminated because I can schedule two or three appointments on one day off."
For NIAMS Administrative Officer Andrea Ricche, it was just a matter of formalizing in October 1992 an arrangement made necessary by her daily commute. "My husband works downtown," she explains. "We carpool to the NIH campus and he takes the subway. I was always here early and staying later than my schedule. When I was offered AWS, it just made sense. I find that the extra hour per day allows me the time to finish tasks that otherwise would have had to wait until the next day."
"I chose AWS because it allows me to plan and schedule appointments during normal work time and know that I will be available at a designated time," adds NLM Cataloguer Dorothy White. "It has not changed how I do my job. Since I am at work for 9 hours, I have no problems coordinating with my coworkers. Scheduling meetings has not posed a problem because the staff is aware of my day off. My quality of worklife has improved because I don't have to take as much annual leave and there is less stress."
AWS Picks Up Speed...
In 1997, HHS Secretary Donna Shalala encouraged AWS in her Quality of Worklife Initiative. Just months ago, the President directed agencies to review work scheduling practices again "to make maximum use of existing flexibilities to allow federal employees to plan and take time off to perform community service as the public business permits."
Boosted by support from the highest levels, the program quickly gained momentum. Most employees who had changed their work schedules sung its praises, and many workers not offered the option wondered to supervisors, "Why can't I?"
Notwithstanding all the endorsements, widely offering AWS can present some big problems, explains Marvene Horwitz, OHRM deputy director and head of NIH's quality of worklife committee.
"The topic is a bit complicated," she says. "There are the conflicting sides of employees wanting flexibility and managers feeling that people aren't available to get the work done, although there are many managers who handle it well. The QWL committee is looking for ways to publicize these tools for managers and employees, but we also want both sides to understand the other's needs."
What is important to keep in mind is that AWS is an employee benefit, not an entitlement. It is a tool managers can use to accomplish certain goals: enhance customer service by extending hours of availability, relieve traffic congestion during peak commuting times, relieve on-campus parking shortages, reduce tardiness and absenteeism, improve staff morale, and help employees balance work and family responsibilities. It is up to managers to administer the program efficiently and to make sure AWS does not have an adverse impact on NIH's mission. It can be a difficult call.
...But Not for Everyone
"Our office first implemented AWS in a 6-month trial period about 5 years ago," recalls Michael Rosenthal, NICHD personnel officer. "We tried it again, in another 3-month pilot, about 3 years ago. Unfortunately, after assessing its advantages and disadvantages, I decided not to implement it in my office on a permanent basis. The major problems we encountered were two: First, the relatively small size [seven workers] of our office made it difficult to achieve optimal staff coverage when the 'AWS day-off' was added to the normal mix of sick and annual leave usage and staff being away from the office at meetings or training. Second, our office is service-oriented. Our customers were not very pleased when a staff member to whom they needed to speak was out on his or her 'AWS day-off' when the customer needed information or advice. When the pilot ended and I decided not to implement AWS, I believe that the staff was disappointed, but I believe they understood the basis upon which my decision was made."
Managers and supervisors are not the only ones who may have troubles with AWS. Sometimes coworkers who don't use AWS can end up holding down the fort shorthandedly (usually Mondays and Fridays, by far the most popular AWS days off). As some employees point out, if a person's job is such that others must constantly "cover" for him/her on the day off, then maybe AWS is not a good idea for the worker.
"I think AWS can be a great tool for rewarding hardworking employees," says Ricche. "It shows that one is trusted enough to be able to balance day-to-day assignments with the day off. I don't believe that every position is right for AWS nor is every person -- it is strictly up to the supervisor and the individual to figure out if it works for them."
Up to Top