Why Some Technology Projects Fail

Don't forget to subscribe to the blog (no charge) to receive educational content!

We know that people can make or break an organization’s purchase-to-pay strategies. However, even when the right people are on board, a technology project might not turn out as expected. Following are three reasons why, tips, and specific advice for an AP automation pursuit.

Unrealistic Expectations

The trouble can begin early on when an organization thinks technology will solve all their issues, but they fail to identify the root causes of problems. As an example, consider the common problem of slow internal invoice approval. Technology is not the magic answer for this. While technology can make approvals easier to do, the slow people will probably continue to be slow unless they are held accountable to a defined timeline. 

Tip

Determine your biggest pain points and explore why they occur. Do you need a change in policies and/or procedures? Do employees need more training? To what extent will technology help resolve the problem?

Haste

Rushing to select and implement a technology solution often means that an organization fails at multiple levels during a project. You might overlook elements needed by stakeholders or the complete picture of how a process works (and where new technology is most critical). If you skip doing thorough system testing, manageable hiccups can turn into emergencies when the system goes live. 

Tips

  • Assign the project manager role to someone who is equipped with project management knowledge and skills.

  • Document existing processes, stakeholder requirements, goals, etc.

  • Address how you will resolve any conflicting requirements between stakeholders. What will take precedence?

  • Develop and follow test scripts to ensure the technology works as expected before fully implementing. 

Lack of Communication

No list of pitfalls is complete without the proverbial lack of communication. This could mean forgetting to revise relevant policies and procedures, a lack of training to system users, failing to communicate with affected suppliers, and more.

Tips

The obvious action is to turn this around by communicating effectively throughout the organization and with suppliers. 

  • Note who will be impacted by the technology and, therefore, need training.

  • Offer a clear place to go if people have questions.

  • Explain the purpose of the new technology.

  • Monitor how users are handling the technology and the common errors.

Frustration with a technology project is more likely to occur if your organization does not do solid advance planning.

Frustration with a technology project is more likely to occur if your organization does not do solid advance planning.

AP Automation Advice

When it comes to AP automation:

  • Ensure you will have dedicated IT support throughout the project.

  • Try out/demo different solutions before committing to one.

  • Verify that all your applicable systems will be compatible with each other.

  • Anticipate that AP will receive a spike in questions until users are comfortable; plan staffing accordingly.

  • Be assertive with suppliers regarding rules for invoice submission.

  • Do a longer pilot period before rolling out to everyone. 

“The first rule of any technology used in a business is that automation applied to an efficient operation will magnify the efficiency. The second is that automation applied to an inefficient operation will magnify the inefficiency. ”

— Bill Gates