The most important team member you need in-house to run a successful ERP project is some form of Solution Architect. Vendors will often take care of most roles for the implementation itself. But someone on the inside needs to be mapping the solution to the organization’s needs.
The most obvious example of why this is necessary is right up front. The organization needs to know which vendor to go with in the first place. An organization shouldn’t let an outside sales department manage the ERP selection process. The Solution Architect should start with the organization’s requirements, then use that as the basis for the search.
Even at that point, the organization can’t just pick a vendor and hand everything off to them. They need a definitive set of measurable statements. They also need a project charter that outlines Why the solution is necessary, What requirements need to be in the final product, and How to manage it on the organization’s side.
Once underway, the Solution Architect should continue to manage the project, especially when it comes to adopting the solution. Just recently we witnessed a company who couldn’t name who was in charge of integrating the ERP into the organization’s suite of solutions. When it came down to it, it was apparent this was just being left to the vendor.
Situations like these are why, even in the most extreme scenario where an organization trusts a vendor to provide the ERP project team, there must be a point person from within who adapts their approach to the needs and realities of the organization itself.
If you’d like additional information on effective project management practices or to learn more about what WiserWulff can do for your operations, please let us know. We can sit down with you to discuss your options and find a solution perfectly suited to your organization.
The Most Important Role for Every ERP Project
The most important team member you need in-house to run a successful ERP project is some form of Solution Architect. Vendors will often take care of most roles for the implementation itself. But someone...
What is Project Management? (And why do you need it?)
Projects are what deliver organizations to their future vision. So the #1 thing holding organizations back is project failure. That’s where project management comes in. This post covers the basics you need to know...
How to Overhaul a Culture of Project Malpractice
Expectations around project success are historically low across organizations. Poor results in the past have led many companies to believe that only a few projects will pan out, and executives often respond by thinking...
Project Phases and The Project Lifecycle
There are a variety of approaches used to define a project from start to finish and break it down into phases. This post will review some alternate approaches to project lifecycles. Project Phase Deliverables...
What Makes a Project Successful?
A lot of organizations struggle at judging how a project went. This article covers the textbook approach to evaluating the success of a project. Check out our blog post The Third Dimension of Project...
The Effects of Poor Leadership in Project Management
The effects of poor leadership in project management have ripple effects throughout an organization. Many of the most common project ailments–including a lack of clear requirements, regular miscommunication and lagging schedules and bloated budgets–all...
4 Roadblocks Stopping Organizations from Realizing Project Benefits
The most important element of a successful project is meeting the business case and original scope of the project. But that’s easier said than done. The bad news is that organizations often find it...
Leadership’s Crucial Role in Project Success
A portfolio of projects is the vessel that delivers the vision of an organization strategy. Projects are intricate endeavors involving individuals, components, and processes. Bringing them to fruition requires meticulous planning and expertise. Considering...