Learning Japanese, or Stopping Mistakes Before they are Made

Poka-yoke – I never had heard the word before, but I was delighted to discover it two weeks ago in a Harvard Business Review article written by Michael Schrage.

Poka-yoke is Japanese for “mistake-proofing.” Think of the “In Case of Fire Break Glass” boxes found in office buildings. Because they include a wee stick with which to break said glass, they would qualify as poka-yoke.

Best of all, your employees will experience minimal downtime and very little lost productivity.

In business, Schrage explains, poka-yoke is the “simplest, cheapest, and surest way to eliminate foreseeable process errors.” He urges managers to perform a poka-yoke audit of their own department.

“What are the persistently simple — and simply persistent — dumb mistakes we make that our technologies can help us catch and destroy?” he asks.

Here’s where I believe IT managers should start: the help desk.

Say your company is planning an Office 2007 migration, and you, as CIO, have decided that because of the current economic climate, assistance isn’t needed. After all, your reliance on internal help desk staff during previous Office upgrades didn’t turn out disastrously. [Read more...]

Office 2007 Migration: Finish What You Started, Pt. 4

Perhaps this scenario describes your desktop software situation: Half of your end users use Office 2007, and the rest are still running Office 2003. All you’ve heard from the former are “Where’s the file menu?” and “How do I save a document?” From the latter, you’ve likely listened to endless grumbling about their frustration with Office 2003-incompatible files created by colleagues.

Final post in a four-part Office 2007 migration series.

It needs to be said: Finish what you started.

In June 2009, PC Helps partnered with CIO.com to communicate the myths and realities of an Office 2007 migration and eight service levels needed to prove migration ROI. Since the recent release of Windows 7, We have updated the Office 2007 myths and realities white paper to include actual call statistics and adoption considerations for Windows 7 as well.

IT leaders cannot afford to approach an Office 2007 or Windows 7 migration blindly. The user interface is radically different and guarantees that your employees will flounder just trying to perform basic tasks. Separate the facts from the myths, and learn how to get the most return on your investment. Download the free, updated white paper now.

Read the series: Finish What You Started.

MORE INFO IN: Office 2007 Migration Case Study | Office 2007 Migration Assurance Program | Migration Readiness Checklist | Migration Competitive Analysis | Contact PC Helps

Office 2007: Finish What You Started, Pt. 3

Perhaps this scenario describes your desktop software situation: Half of your end users use Office 2007, and the rest are still running Office 2003. All you’ve heard from the former are “Where’s the file menu?” and “How do I save a document?” From the latter, you’ve likely listened to endless grumbling about their frustration with Office 2003-incompatible files created by colleagues.

Third in a four-part Office 2007 migration series.

It needs to be said: Finish what you started.

In part one of this series, I highlighted the reasons an estimated 50 percent of enterprise-sized IT departments are running mixed Microsoft Office end-user environments. Part two offered information on how to complete the migration with minimal downtime. This post lays out a project timeline and readiness checklist.

You want successful transition to Office 2007 and early ROI. In order to meet those goals, you need to keep your employees informed and trained before, during and after deployment. With a plan in place, you will minimize or eliminate dips in productivity and give your workers confidence to use the tools they rely on every day. This is what you should expect from a migration partner: [Read more...]

Office 2007: Finish What You Started, Pt. 2

Perhaps this scenario describes your desktop software situation: Half of your end users use Office 2007, and the rest are still running Office 2003. All you’ve heard from the former are “Where’s the file menu?” and “How do I save a document?” From the latter, you’ve likely listened to endless grumbling about their frustration with Office 2003-incompatible files created by colleagues.

Second in a four-part Office 2007 migration series.

It needs to be said: Finish what you started.

In part one of this series, I highlighted the reasons an estimated 50 percent of enterprise-sized IT infrastructures are running mixed Microsoft Office end-user environments. This post offers information on how to complete the migration while minimizing downtime and frustration.

Most IT leaders realize that an Office 2007 deployment requires coordination, planning and oversight. As a result, many bring in a third party for migration assistance.

The support options and partnerships are abundant, including training companies, consulting firms, domestic and offshore outsourcers, and certified Microsoft Office 2007 migration launch partners. [Read more...]