Would you groom a poodle only halfway? Not finishing your Office 2007 migration is just as nonsensical.

According to a leading industry source, more than 50 percent of enterprise-sized IT infrastructures are running mixed Microsoft Office end-user environments. The reasons are many: the recent “econolypse” spurred IT leaders to cut budgets and lay off workers, leaving Office 2007 deployments incomplete; IT management underestimated the amount of work that a migration required, and they reacted by halting phased rollouts; and some CIOs and other IT leaders who were not mandated to deploy the new version to the entire company doled it out in a “drip” fashion.

The result is an enterprise that looks something like this: Half of your employees 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 endured endless grumbling about their frustration with Office 2003-incompatible files created by colleagues.

It’s not just user aggravation you have to worry about either. Running two versions invites compatibility issues, minimizes the return on your Office 2007 investment, and keeps your internal help desk semi-knowledgeable about the software.

We’ve compiled a kit that will show you how to cost-effectively finish your Office 2007 migration while minimizing the end-user and help desk learning curve, increase productivity and more accurately project call volume. You can view it here.

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

admin Finish What You Started CIO, econolypse, Office 2007 migration, ROI

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

admin Finish What You Started, Office 2007 Migration Assurance Program CIO, migration, Office 2007, white paper, Windows 7

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…

admin Finish What You Started, Office 2007 Migration Assurance Program Help Desk, learning curve, Office 2003, Office 2007, recession, shadow support, the Ribbon, Training

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…

admin Finish What You Started, Office 2007 Migration Assurance Program Help Desk, learning curve, Office 2003, Office 2007, shadow support, the Ribbon

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.

Part one of a four-post Office 2007 migration series.

It needs to be said: Finish what you started.

According to a leading industry source, more than 50 percent of enterprise-sized IT infrastructures are running mixed Microsoft Office end-user environments. The reasons are many.

The Recession: During the past two years, IT budgets were cut and some employees were let go, leaving Office 2007 deployments incomplete.

Misjudgment: IT leaders were unaware of the amount of work that went into a migration. A dearth of internal resources to handle increasing call volume and demand for training halted phased rollouts.

Choice: IT leaders who weren’t mandated to deploy Office 2007 to the entire company chose to migrate in more of a “drip” fashion. Only those who requested the upgrade received it.

It’s not just user frustration you have to worry about either. Managing a staff that is running two versions causes pain for the company in other ways: compatibility issues, limited return on your Office 2007 investment and a semi-knowledgeable internal help desk.

Below is a sampling of the most common Office 2007 issues for end users. Read more…

admin Finish What You Started, Office 2007 Migration Assurance Program learning curve, migration, Office 2003, Office 2007, recession