David’s Road Warrior Toolkit

The consulting business being what it is, it’s not unusual to spend a lot of time on the road, in airports, hotels, and at client sites far from home.  And my addiction to technology being what it is, I have accumulated a sizable collection of software and hardware tools to make life on the road easier and more productive.  Friends that know of my fondness for gadgets ask from time to time for advice on gear, so I thought I’d post what I’m carrying these days.  No, sadly, none of the manufacturers of the products mentioned here is paying me a thin dime for an endorsement.

Read more of this post

ERP Benefits Still Falling Short?

Computerworld reported a couple of weeks ago on a recent study of the business benefits of ERP conducted by Panorama Consulting Group. Their findings were less than encouraging:

More than half of companies that implement ERP systems end up getting no more than 30% of the business benefits they expected…  Of the 1,600 organizations surveyed, 72% said they were "fairly satisfied" with their ERP package. But this can be misleading, according to the study: "Some executives are just happy to complete projects… and give little thought to whether or not the company is better off with the new software or whether or not they’re getting as much out of the system as possible." More than half (51.4%) of ERP projects went over budget, the survey found, and about 35% of the respondents said their projects took longer than expected.

Depending on whether you believe research from sources like Standish, these figures may simply be representative of broader issues with the success rate of software projects—small consolation, given the central role ERP plays in running today’s businesses.

What to do about it?  The article summarizes the report’s recommendation’s:

ERP customers can avoid surprises by taking the time to pin down a project’s real costs, which go far beyond software licenses. Three quarters of a project’s budget typically goes toward implementation, hardware upgrades, customization and other needs, according to Panorama. Customers should also "identify pockets of resistance within the company and determine the organizational change management needed to make the project successful," Panorama suggested. Altimeter Group analyst Ray Wang agreed. "People do not invest enough in change management," he said. The length of ERP projects can exacerbate dissatisfaction, he added, noting that users’ requirements might change a great deal between the time the vendor is selected and the time the system is deployed.

It’s interesting the degree to which change management continues to be identified as a major point of failure in ERP implementations. Not that I’m suggesting that change management is easy to pull off, mind you—far from it.  But the problem identified here doesn’t seem to be properly funded change management failing in the attempt. Change management has been widely and publicly discussed as a—perhaps even the—critical success factor for ERP success for at least a decade now, since the media coverage of several troubled projects in the late 90s. If there remains widespread underinvestment in it, there must surely be systematic reasons for that—reasons built into the standard ways companies select and design ERP projects. Several likely factors come to mind, but I haven’t seen a widespread, detailed study of why underinvestment continues over time. That’s some research I’d like to see.  If anyone knows of some, please let me know in the comments, I’d love to check it out.

As for the factors I think are at work, I’ll address that in a future post (or posts).

Ed Yourdon on Death March Software Projects

If you missed Michael Krigsman’s post about it a few weeks back, you might want to check out the Ed Yourdon’s presentation on “death march” software projects (which I’ve embedded below).  Those of you who have been on a death march will feel right at home as he describes them, and you may find the advice he offers very useful the next time you find yourself stuck in one.  The presentation is full of though-provoking tidbits… I think my favorite part is the section on system dynamics modeling (slides 89-96).  It outlines why project team dynamics are so complex and so easily underestimated.  Slide 72, “Worst Practices” is also worth a look, especially if you are involved in project leadership, whether as a manager or sponsor.  From that page comes: “Don’t expect to recover from a schedule slip of more than 10% without acknowledging a disproportionately greater reduction in software functionality to be delivered."  I wince to think how often that principle is ignored.

New Collaboration Features in MS Office 2010

The Microsoft Office Word team blog has a short video up describing the new coauthoring features in OneNote, Word, and PowerPoint.  It does sound a bit like collaboration nirvana.  As anyone who has worked jointly on a training document, a proposal, or a presentation can attest, version control and the merging of changes can be a major time sink.  Web services have had similar collaboration features for a while, but those sites lack the reach and/or functionality offered by the Office tools.

On the other hand, these new collaboration features will require a change in work styles which that will present the usual training and change management issues.  For example, if you are assigned to work on part of a client proposal for example, will you be reluctant to share your early drafts with the entire team, including senior executives?  Will people delay publication of changes to shared documents, limiting the feature’s utility?  I’ll be interested to see how quickly Office 2010 is adopted, and how these capabilities are used once it is.

ComputerWorld: How to Make Your ERP Roll-out Succeed

If you have been around ERP implementations for a while, you can be forgiven a sense of deja vu as you read this ComputerWeekly article, which says that training and change management “can be the difference between success and failure.”  Poor change management has been recognized as a leading element in project failure for at least a decade now, ever since the high-profile teething pains experienced by SAP and other vendors in the 1990s.  Many articles were written about the challenges faced by Hershey, Whirlpool, and other companies that struggled with their new systems because of primarily organizational challenges, and both ERP vendors and their implementation partners responded by improving their ability to prepare people for the changes a new system introduces. 

The real news then, isn’t that good change management is a critical part of making your multi-million dollar ERP investment.  It’s that ten years later, it remains such an impediment to ERP success:

Read more of this post

Dragon Speech-to-Text Arrives for the iPhone

image I occasionally suffer from writer’s block, and have been using Dragon NaturallySpeaking speech-to-text software (now owned by Nuance Communications) for something like 10 years now to get around it.  Whether I’m trying to write a blog post that’s just not coming together, the explanation of a tricky concept in a training guide, or a proposal, I’ve found the key is to get the ball rolling—get something down, after which the words come more easily.  And for me at least, talking through the first draft is often easier than typing it out. 

I bring this up because Nuance has just released an iPhone app that uses the same technology. 

Dragon Dictation is an easy-to-use voice recognition application powered by Dragon NaturallySpeaking that allows you to easily speak and instantly see your text or email messages.  …You can also update your Facebook status, send notes and reminders to yourself, or Tweet to the world.

Transcriptions can be sent by SMS or e-mail or copied into any other app that accept text from the clipboard.  Not only does this bring a welcome element of portability to the Dragon line, it comes at a price that’s hard to beat: Dragon Dictation is free.  You can get download it from the iTunes store.

Microsoft Project 2010 at First Glance

Microsoft’s Office 2010 Engineering blog ran a nice overview of Project 2010 back in October, a quick read that highlights some of the new features in the upcoming release.  Now that the public beta has been available for a few weeks, I’ve finally had a chance to see what they’re talking about—and I must say I’m impressed.  Changes to Project have been positively glacial in many ways, especially compared to the pace of change in the Office suite.  Project for Windows debuted in 1990, for example, yet it wasn’t until sixteen years later that users gained the ability to Undo more than a single action arrived. 

It is immediately apparent when you open Project 2010 that this time is different: there’s a lot here that’s new.  Consider, for example, some of the changes you see as soon as you fire the program up and load a plan:

Read more of this post

How Long to Develop An Hour of Training?

Estimation is one of the more challenging aspects of project management, and is central to project success.  Formally or informally, most project work is tracked and evaluated against the expectations set up front for cost and time required.  Inaccurate estimates can have serious consequences for an organization, the project team—and the project manager.

The typical PM learns two things about estimation early in his or her career:

  1. It’s a bad idea to offer estimates before you have enough information to properly scope the project, because once people hear numbers coming out of your mouth, they will remember them forever.
  2. People will insist you do it anyway.

Good practice says that estimates, especially early ones, should be given as a range, with the width of the range set by the uncertainty of the estimate.  Even then, you still need a starting point.  Enter the rule of thumb.  For those times when you need a ballpark figure to gauge the size of a training project, many managers and organizations have history doing similar work they can draw upon to get started. 

But what if you are just getting started as a training manager, or have never developed a particular type of training before?  What if you want to gauge your personal experience against industry norms?  Back in 2003, Karl Kapp conducted a survey of learning professionals, and wrote an article that compiled estimates for developing of an hour of training using various techniques.  Kapp and Robyn Defelice have recently updated the original article with findings from a new survey.  The initial response pool isn’t huge (47 participants), so the results should probably be used cautiously, but it’s some of the best public data I’ve seen, and the new article covers a broader range of development approaches.  The authors note that estimate duration for several training types of development have increased since the 2003 survey, and suggests that issues with scope and change management—in both the project management and organizational sense—may be responsible. 

It’s also worth noting that the authors are continuing to collect estimates, so if you’d like to contribute to the study, follow the link to the article above and scroll down, or visit the survey directly here.

Should You Hire Technologists for Their Industry Knowledge?

Pat Ferdinandi questions the current trend.

About David Gaw

David Gaw I’m a learning professional with more than 15 years experience developing and delivering training and change programs for clients in nearly every industry you can think of, as well as the public sector.  I have worked for IBM and Deloitte Consulting in their Human Capital practices, and have been involved with—and intrigued by the potential of—e-learning technologies since long before anybody called them that.  As Manager of Technology Consulting for DDS Inc./Metamor Knowledge Solutions, I led product design and sales support for our portfolio of e-learning products, and supported technology implementations on five continents.  I am a PMI-certified Project Management Professional (PMP), an avid traveler, and I couldn’t hit a golf ball to save my life.