Your ERP team already has a day job: how to plan the workload

Ben Langley, NetSuite consultant

An ERP project needs more than a consulting team. It also needs time from people who already keep the business running. Ben Langley, founder and CEO of Suite Generation, talks to Joanna England about project resourcing, internal capacity, retaining business knowledge and finding the right balance between employees and external specialists.

Part 3 of 5 in the series Phase zero – before you implement.

This interview has been edited and condensed for clarity.

Project resourcing: key takeaways

  • ERP project resourcing has to count the time employees give the project, not just the consultants’ work.
  • A resource assessment covers people, time, knowledge and experience, external resourcing and the extra operational load.
  • If a long-serving employee leaves mid-implementation, knowledge that was never written down can leave with them.
  • Ben Langley favours capable internal people, strong department heads and a client-side project or programme manager, supported by specialists where appropriate.

Where do businesses underestimate the workload?

Ben: They look at the work the consultants will do without fully considering what their own people need to contribute. An implementation needs decisions, process knowledge and time from employees throughout the business.

Those employees already have jobs. If you expect them to spend several hours a day on the project, you need to understand how that fits alongside their existing responsibilities.

Otherwise, you are effectively asking them to do a second job. The work can spill into evenings and weekends, which affects morale and makes an already demanding change harder to manage.

What should a project resourcing assessment cover?

Ben: Start with whether you have enough people and whether they have enough time. Then look at whether they have the knowledge and experience the project requires.

External resourcing needs attention too. Saying that you will bring in a contracting team is only the beginning. You need to know where to find those people and who will handle the search.

Internally, the question is whether the business can manage the additional operational load. A plan that depends on people continually working beyond their normal hours is asking a great deal of them.

Why does losing an employee matter so much during implementation?

Ben: Someone who has worked in the business for years may carry a huge amount of knowledge that has never been written down. They know how things happen and what to do when something unusual comes up.

If that person leaves before sharing what they know, the knowledge leaves with them. The project then has to spend time reconstructing the process, often with additional consulting work.

This is why workload and morale are practical implementation concerns. You need the people who understand the business to remain involved and able to contribute, rather than becoming overwhelmed by the change.

For project resourcing, is it better to recruit employees or hire contractors?

Ben: It depends on the business and what it needs over the longer term. Strong permanent employees bring continuity and focus. The business is their main commitment, and they can keep contributing after the implementation finishes.

Contractors bring specialist experience for a particular period. They can be valuable when you need expertise that is not available internally, but their time is expensive and they may have other clients.

I would look at the balance. You need capable people inside the business, supported by specialists where appropriate. Hiring consultants does not remove the need for internal leadership.

An employee who understands the operation is contributing something different from a consultant who understands the software. The project needs both kinds of knowledge to make progress together.

What does good internal leadership look like?

Ben: Strong heads of department who can bring their teams together and understand the processes they are responsible for. They need to be supported and treated well because their contribution extends beyond the project itself.

I also favour having a good project or programme manager on the client’s side. Someone needs to keep track of what the consultants are delivering and whether the work matches what has been agreed.

That includes checking progress and understanding where the time is going. You are paying for specialist help, so there needs to be someone inside the business managing that relationship.

How do you make the schedule more realistic for employees?

Ben: Ask about their day job when discussing a deadline. It sounds simple, but it changes the conversation from when you would like something finished to when someone can reasonably do it.

People may need input from colleagues or third parties before they can complete a task. Those dependencies need to be understood too.

The ERP may eventually help the business manage its workload more effectively. Getting there still requires additional effort. That is something to plan for early, including whether you need more permanent staff or temporary expertise. You cannot assume that the future efficiency of the system creates spare capacity in the team implementing it today.

Frequently asked questions

What is project resourcing in an ERP implementation?

It is working out whether the business has enough people, with enough time, knowledge and experience, to contribute to the project alongside their day jobs, and where any external help will come from.

For project resourcing, should you recruit employees or hire contractors?

It depends on the business and its longer-term needs. Permanent employees bring continuity and focus; contractors bring specialist experience for a period but are expensive and may have other clients. Look for a balance: capable people inside the business, supported by specialists where appropriate.

Why does staff turnover matter during an ERP implementation?

Long-serving employees often hold knowledge that has never been written down. If they leave before sharing it, the project has to reconstruct those processes, often with additional consulting work.

How do you set realistic ERP deadlines for employees?

Ask about their day job when discussing a deadline, and understand what they need from colleagues or third parties before they can finish a task.

Does an ERP implementation need a dedicated ERP project manager?

A project or programme manager on the client’s side is strongly advisable. An ERP project manager inside the business keeps track of what the consultants are delivering, checks that the work matches what was agreed and manages the relationship the business is paying for.

Related reading

About Ben Langley

Ben Langley is a NetSuite consultant and the founder and CEO of Suite Generation – 30+ implementations, multiple OneWorld accounts, and over 200 automations built inside NetSuite. Follow him on LinkedIn for more thought leadership on ERPs and NetSuite.

Author

  • Joanna England, Marketing & Growth Operations Lead at SuiteGeneration

    Joanna England is Marketing & Growth Operations Lead at Suite Generation and an award-winning tech and business journalist with more than 25 years' experience. A former Editor-in-Chief of Insurtech Insights, Fintech Magazine and Insurtech Digital, she was named one of MPVR's Top 30 Journalists in Fintech & Insurtech in 2023.

Follow us on LinkedIn

New NetSuite field notes, UK pricing guidance and implementation practice, as we publish them.

Follow →
Chapter contents:

Netsuite Playbook

From blueprint to go-live, get the play-by-play in our NetSuite Playbook.

Want to be featured on our blog? Get in touch via email hello@suitegeneration.net