FAQ6 questions
Deployment, rollout and change management
Rollout
How fast can we get MuchSkills running?
The MuchSkills platform is live in days. Full professional onboarding runs from two to twelve weeks, depending on the number of users and how complex the setup is. The two figures describe different things: days gets you an account, your org chart and a starting taxonomy, and the onboarding window gets you completed profiles, agreed proficiency definitions, manager validation where it matters, and reports people use.
What does MuchSkills professional onboarding include?
MuchSkills onboarding is a paid service that every sales-led plan starts with, sized to your organisation: Guided for up to 100 people, Professional for 101 to 500, and Enterprise above 500 with a named project manager and change management. Standard data import is included at every level. The work is taxonomy design (which skills you track and in how much detail), configuring imports and integrations, training, and running the launch so profiles get completed rather than just announced. Teams of up to 100 on the self-serve Starter plan can use the published how-to guides instead. More on professional onboarding.
Will our employees resist a skills platform?
Employees resist skills systems that are done to them, especially if the last one was used to rank people. MuchSkills is built to be useful to the employee first: each person sees which skills their role needs, which skills lead to the role they want, and gets a development plan with AI guidance on the next step. People see and update their own profile, so it reads as their record. Before launch, say plainly what managers can see and how the data will and will not be used, including that any use in reviews is one input among several and never scored by MuchSkills.
Who owns MuchSkills internally after go-live?
Give MuchSkills named owners after go-live, one or two people or a small group, with time set aside for it: usually an HR or L&D lead, or in consultancies a delivery or resourcing lead, because staffing decisions carry commercial weight there. Managers still use it every day. The owners run the taxonomy decisions, such as adding a skill, merging duplicates or retiring one nobody has claimed in a year, so a manager who wants a skill added asks them. That keeps the taxonomy consistent instead of fragmenting.
How do we get managers to use MuchSkills?
Train managers on their own team. In the first session, run a live search on their people, such as "who holds an AWS certification and is free in four weeks?" or "which certificates expire before the audit?", so they see an answer to a problem they had yesterday. Then train them to use MuchSkills in one-to-ones and development talks, the most important habit to build, and give clear guidance on how your organisation uses the data. A mandate from above without training and a clear policy rarely sticks.
What happens in MuchSkills when people join or leave?
Joiners and leavers flow through your HR system import: a joiner appears when the HR feed adds them, and a leaver is removed from your organisation's view when the feed flags them. Removing a person is separate from deleting their data, so records your organisation needs, such as certificates kept as audit evidence, stay available under your retention rules. A joiner starts with an empty profile, so build profile completion into the first-week induction checklist instead of chasing it months later.