Are you contributing to implementation failure?

Posted by Margaret Bolding

Nobody begins a software implementation with the goal of failure. Why, then, is failure a likely outcome? You'll inadvertently set yourself up for failure if you have improper planning and unclear communication with your team.

Have you ever had a bad implementation experience? As a brainstorming activity, think with me for a moment about reasons implementation projects might fail:

• Poor expectations set, communicated, and understood by everyone
• Poor communication within each team
• Poor communication when issues arise

Clearly, communication is paramount to a successful implementation.

When implementation issues arise, communication is key

Occasionally, implementation failures are the result of technical difficulties that cannot be overcome.  However, more often than not, implementations struggle when clear expectations are not set and communication is lacking. Some examples of issues when communication is inadequate include:

• Finding the issue and pressing on toward resolution too long
• Waiting too long to ask for help
• Not devoting enough time to resolution as the issue lingers and becomes stale

It's hard to keep momentum with an old task when so many new tasks demand attention. As a result, new tasks seem to get our energy and time.

Resolving implementation issues (or not)

When implementation issues aren't resolved, they can lead to budget and time overages, frustration on all sides, and muddled, unmanaged communication. Additionally, not all parties have the same information or a clear understanding of the issues. Instead, too much time is spent saving face when disclosure and responsibility are needed. Avoiding a failed implementation is an easy task; plan, communicate and make sure you cover the basics.

InterDyn Artis provides ERP and CRM solutions and we realize the effect communication has on implementation outcomes. Part of our process is putting forth extra effort to ensure the groundwork is set and communication is an open avenue before even starting an implementation.

​Good processes must be in place, but we have to remember that good communication is a journey, not a final destination.

---