The super user is the role that makes UAT work, keeps the spreadsheets from coming back and turns hypercare into a fortnight instead of a quarter. Who to pick, what they actually do in each phase, what it costs the business, and why it should be recognised in their pay.
If you read our other pieces on where testing and training sit and hypercare, one role keeps appearing: the super user. It is the single most important role on the customer side of a Business Central project, and it is the one that is most often filled by whoever was free, unpaid, on top of their day job. Here is how to do it properly.
A super user is a member of staff, one or two per department, who knows how their part of the business actually works, is trained on the new system as it is built, and becomes the person their colleagues go to first. They are not IT. They are not the project manager. They are the finance assistant who knows every exception in the purchase ledger, the warehouse supervisor who knows which bins are really used, the sales administrator who knows which customers have special terms and why.
The best super users share four things. They know the process in detail, including the exceptions, because the exceptions are what break systems. They are respected by their colleagues, who will take "this is how we do it now" from them. They are curious enough to click on things and not afraid of a screen. And they are staying: there is no point investing six months in someone who is leaving in nine.
They are not usually the manager. Managers know the policy; super users know the practice. They are not usually the most senior person. And they are not "whoever is least busy", because that person is least busy for a reason.
Over a six-month project a super user will spend roughly a day a week on it, rising to most of their time in UAT and the first fortnight after go-live. For a project with eight super users that is a real cost, and the department has to be backfilled or the day job slips. Businesses that do not plan for this get super users who skip the workshops, turn up to UAT cold, and sign off things they have not tested, which is how UAT becomes a formality.
Against that, the super user is what makes UAT real, what makes training stick, what keeps hypercare to a fortnight, and what keeps the project from depending on the consultant forever. A business with good super users needs about half the consultancy days after go-live of one without. They pay for themselves several times over.
Recognise it. The role is extra responsibility and extra hours for six months, and it is visible to the whole department. The businesses that do this well do one or more of: a project allowance for the duration (a few hundred pounds a month is typical in UK mid-market businesses); a one-off bonus at go-live sign-off; the role written into the person's objectives and appraisal, so it counts towards their next pay review; and, afterwards, a standing "system champion" role with a modest permanent uplift, because the job does not end at go-live. What does not work is asking for it on goodwill alone and then being surprised when the goodwill runs out in UAT.
Make it a position people want. In most businesses the super user on a successful ERP project is the next team leader, because they are the person who understands how the whole department works.
Super users only work if the partner treats them as colleagues rather than testers: trains them early and properly, lets them into the design conversations, gives them the sandbox, takes their feedback seriously and hands them the keys at the end. That is how we run every project, and it is why our hypercare periods are short. If you are planning a project and have not yet named your super users, that is the first thing to do, before the partner is chosen. Happy to talk it through.
