Archive for June, 2010

ERP Implementation: The Importance of the Plan

Monday, June 28th, 2010

When you want to buy a new car, you make a plan. You take the time to search for what you want, why it fits your needs, and how you’re going to go about getting it. This might mean developing tactics to use with salespeople and in finance. In fact, just about everything of significance that we do in life incorporates some sort of planning very early on in the process.

Implementing an ERP software system is something that necessitates not only a strategy, but also a written strategy at that. Why is a written plan for ERP software implementation so important? Simple: It removes the ambiguity from the process, establishes deadlines for achieving key milestones, and provides a tool for ensuring that all individuals and departments stay on track. Furthermore, a written plan serves as both a guidepost and a guiding force behind the implementation. (more…)

ERP Implementation: Maximum Employee Buy-In — Unlocking Change

Monday, June 14th, 2010

Even when people know that change is necessary and/or good for them, they will often resist to some degree. Therefore, every successful ERP implementation must include a concerted effort to get employees to buy in to the new system.

Start by expecting some resistance to occur, and then seek to understand the reasons. For example, some people—especially those who have been on the job a year or more—may resist simply because it feels more comfortable doing things the old way. Others may feel the current system is working fine, so why fix what isn’t broken? A few may consider ERP an invasion of their turf and resist out of fear and/or company politics. The more you know about why people resist the change, the better you can address their issues and improve your chances of a successful implementation. (more…)