How To Estimate ProductivityBy Peter Edmonston | Posted 2002-09-16 Email Print
Re-Thinking HR: What Every CIO Needs to Know About Tomorrow's Workforce
Workbook: Time is money. Whether it's a sales-automation application or a document-sharing system, most internal software projects get pitched as a way to trim labor costs and give employees extra time to generate more business for the company.
Time is money.
Whether it's a sales-automation application or a document-sharing system, most internal software projects get pitched as a way to trim labor costs and give employees extra time to generate more business for the company.
|How much time do you really save with productivity-enhancing software? Use our online calculator to crunch the numbers.|
"Admittedly, productivity can be hard to measure," says Tom Pisello, president and CEO of Orlando, Fla., ROI software vendor Alinean. Still, he and many other experts argue that productivity-enhancing projects should be vetted with the same ROI-based benchmarks as any other potential expenditure.
A company needs to consider an array of factors, including the number of employees affected by a project, how much each is paid, and the amount of time each is expected to save. Often neglected in such calculations, however, is a key aspect of human nature: the primordial urge to waste time. In the real world, employees are likely to fritter away a sizable chunk of any newfound productivity by taking more breaks, leaving early or bidding on eBay.
To compensate for such inevitable time-wasting, Pisello recommends slashing at least 50% from any raw savings forecast. Or, consult a correction-factor table, such as the one developed by Nucleus Research (see chart).
Companies also must understand that increased productivity alone won't fatten the bottom line. Corporate profits will improve only if added productivity generates higher revenuefor instance, allowing a law firm to handle more fee-paying clients with the same number of attorneysor helps lower costs, which usually means job cuts.
Of course, job cuts are a delicate matter, and failure to follow through is a common reason for lower-than- expected project returns.
"At the end of the day, a company could easily discover they didn't make the cuts they were supposed to," says Pisello. "But if a project doesn't let you reduce head count or otherwise lower costs, where is the real impact?"