By Ritvars Mētra, Founder of ReadinessCompassSuper users are usually selected the same way. An email goes to managers asking for nominations, and the names that come back are the people who could most easily be spared.
That single sentence explains most of what goes wrong afterwards. The role that determines whether a hundred people can work is being staffed by whoever had the lightest week in March.
What the role actually requires
A super user is not the most technically capable person in the team. They are the person colleagues already ask when something is unclear — which is a different attribute and usually a different individual.
Three criteria, in order of importance:
- They are already consulted. Ask a team who they go to with a question about the current process. The answer takes ten seconds and is more accurate than any nomination form.
- They know the exceptions. Anyone can learn the standard path. Value comes from the person who knows what the team does when the customer is on credit hold and the order has to ship today.
- They are willing to say the new way is worse, when it is. A super user who only relays official messaging is a communications channel, and the team will treat them as one.
Seniority is not on that list, and neither is enthusiasm. The most enthusiastic volunteer is frequently the person least representative of how the median colleague will experience the change.
Train them to teach, not just to do
Super user training is normally the standard end-user course delivered earlier. That prepares them to perform the task and leaves out the part of the job that is actually hard.
The distinct skills are diagnostic. Working out what a colleague is actually trying to achieve when the question they asked is about a button. Knowing when to answer and when to escalate. Explaining without taking the keyboard — which is the single most important habit, because a super user who completes the task for someone has produced a dependency rather than a capability.
This is also where practice beats explanation. The meta-analysis by William McGaghie and colleagues in Academic Medicine found simulation-based education with deliberate practice outperformed traditional clinical education with a pooled effect size of 0.71 across fourteen studies, results the authors describe as powerful, consistent and without exception. Have super users practise being asked: role-play the awkward questions, including ones with no good answer.
The release has to be written down
Every super user model fails the same way: the role is treated as something done alongside the day job, and the day job is the one that is measured.
This is not a motivation problem. Baldwin and Ford’s review of transfer of training in Personnel Psychology identifies the work environment — supervisory and peer support, and the constraints and opportunities to perform — as one of the three determinants of whether training transfers at all. An unreleased super user has no opportunity to perform the role, so the investment in training them does not transfer.
What works is unglamorous and has to happen weeks in advance: a written release of a stated percentage of time, agreed with the manager who owns their targets, with the backfill or the reduced target named. If a manager will not agree it, that is a finding about business readiness rather than an administrative obstacle — and it belongs in front of the people making the go-live decision.
Keeping them, and the concentration risk
Super users are, by construction, capable and visible. Within a year a proportion of them will have been promoted, moved or left, taking the knowledge with them.
Markus and Tanis name this directly, listing excessive dependence on a small number of knowledgeable key users among the characteristic problems after go-live — the organisation leans on individuals instead of building capability across all operational staff. A super user network that succeeds too well produces exactly that failure, and the overload that follows is the visible symptom.
Four things that help, none of which is a recognition scheme:
- Two per team, not one. One is a single point of failure and cannot take leave.
- Make it count. The role should appear in objectives and be discussed at review. Unrecognised effort ends when the manager changes.
- Require them to write things down. Every recurring question becomes a job aid. This converts individual knowledge into organisational knowledge, which is the whole point.
- Plan the succession before you need it. Name and train replacements at six months, while the original cohort is still there to teach them.
What the role is for
The purpose of a super user network is not to answer questions indefinitely. It is to raise capability across a team fast enough that the questions stop — and a network still handling the same volume of “how do I” queries in month six has not succeeded, however busy it looks.
That is the measure worth reporting: not how many questions super users answered, but whether the mix shifted from navigation to genuine exceptions, and whether anyone else in the team can now answer the common ones.
More on capability and support in the Adoption Risk Hub, or see how super users fit into the wider day-one support model.