Skip to main content
← All Insights
Project Management5 min read

ERP Key Users: Free Up Your Best People Before the Project Needs Them

ERP projects run on key users who still have a day job. How to choose them, free up real time, give them decision rights and keep them after go-live.

Every ERP project plan has a line for key users. Usually it is one line: names next to departments, and an assumption that they will find the time. Then the workshops start, the day job does not stop, and the people who know the business best become the bottleneck nobody planned for.

Key users decide what the system will do for their department. They write and run the tests. They train their colleagues and answer their questions after go-live. If they do that in the margins of a full week, the project gets their margins.

Why key users run out of time

Companies pick their best people as key users, and for good reason: they know the process, the exceptions and the customers. They are also the people the business can least spare. The project does not replace their work, it adds to it.

The result is predictable. Workshops get moved. Decisions wait a week for one person. Test scenarios are written by the consultants because the key users did not get to them. Requirements turn into "keep it like the old system", because there was no time to think about anything better.

None of that shows up as a red line on the plan until testing, when it is expensive to fix.

Choose the right people

A good key user is not simply the most senior person in the department.

  • They know the daily work. Someone who does the process, or supervised it recently, not only someone who approves it.
  • Their colleagues listen to them. After go-live, they are the first person people ask. That only works if people trust them.
  • They can say "we will stop doing this". A key user who defends every old habit turns the new system into a copy of the old one.
  • They will still be there. Losing a key user halfway through a project costs more than the time they spent.

One key user per main flow is usually enough. Two people sharing one flow often means nobody owns it.

Free up real time, in writing

"They will make time" is not a plan. Agree the capacity up front, per phase, with their manager:

  • Design and workshops: a fixed share of the week, on fixed days, so the department can plan around it.
  • Testing: close to full time for the test weeks. This is where most plans underestimate.
  • Go-live and the first weeks after: available on the floor, not in meetings.

Then decide what they stop doing. Some work can move to a colleague. Some routine work, like data entry, reconciliations or master data clean-up, can be taken over for the duration by someone outside the company. What a remote team can take over covers the kind of steady, rule-based work that fits.

What a remote team can take over

If nothing is taken off their plate, the time was never freed up. It was only promised.

Ben Van Aken ran a 20-FTE distribution department at Sip-Well, now part of Culligan, so he has also been the manager asked to free up his best people for a project.

Give them decision rights

A key user who has to check every choice with a manager slows the whole project. Agree in advance what they can decide alone:

  • how a standard flow runs in their department
  • which reports and fields they really need
  • whether a test scenario has passed

And agree what goes up: anything that changes cost, affects another department, or adds a customisation. How to keep those requests tied to a business result is covered in ERP Scope Creep: When Every User Request Gets a Yes.

ERP Scope Creep: When Every User Request Gets a Yes

Support them, do not replace them

The project team, internal or external, is there to make the key users effective, not to do their thinking for them. In practice that means preparing workshops so decisions take one session instead of three, writing test scripts with them rather than for them, and keeping a short list of open decisions per key user.

An independent project lead can tell management, without office politics, when the capacity they signed off is not really there, and say it before testing rather than during it. That is the moment the plan can still be fixed.

Plan for after go-live

Key users are also the first line of support once the system is live. Colleagues will keep their own spreadsheets next to the system if nobody helps them, a pattern covered in ERP user adoption and the Excel next to the system.

ERP user adoption and the Excel next to the system

Agree before go-live how long they stay available, what they handle themselves and what goes to the partner or support team. What Happens After Go-Live sets out how that handover works.

What Happens After Go-Live

A short checklist

  1. Choose key users who know the daily work and are trusted by their colleagues.
  2. Assign one owner per main flow.
  3. Agree capacity per phase with their manager, in writing.
  4. Decide which work they stop doing, and who takes it over.
  5. Define what they decide alone and what goes up.
  6. Prepare every workshop so decisions are made in the room.
  7. Plan their role and availability for the weeks after go-live.

The bottom line

An ERP system is only as good as the decisions made while building it, and most of those decisions are made by key users. Give them the time, the mandate and the support before the project needs them, not after the plan starts to slip.

Comments

Loading comments…

Starting an ERP or CRM project and worried your key users will not have the time?

Talk to Ben Van Aken, freelance ERP/CRM project lead, on-site, hybrid or remote. Details at swiftly-business-consulting.com.

Currently accepting new engagements, starting now and into 2027.