An HRIS rollout is not really a software project. The software works on the first day; adoption is what takes time, and it fails in predictable ways. The two groups you need are managers and employees, and they need different things from you.
Managers decide whether this works
HR owns the system, but managers make or break it. If approving a request feels slower than answering a chat message, some managers will keep answering the chat message, and you will be back to two sources of truth with extra steps. Brief them before the employee announcement, not at the same time: they will be asked questions, and they should not be hearing about it for the first time alongside their team.
Keep the brief to what they actually have to do, and tell them plainly what they will and will not be able to see, using the access rule you settled in Lesson 2. Managers usually imagine they can see more than they can, and saying so early avoids an uncomfortable conversation later.
Employees need three things explained
Not a feature tour. Three practical things:
- What they do differently from Monday. Leave requests go here now. Their own details are theirs to keep up to date. Training is assigned here.
- How they sign in. Multi-factor authentication is required at every sign-in, on every plan. Confirm during setup exactly how the second factor reaches people, then put that in the announcement. It is a small, reasonable step that generates a surprising volume of confusion when it arrives unexplained on a Monday morning.
- What happens to their data. Someone will ask, and it is better answered once to everybody than five times in private. Their records sit in a dedicated environment in the EU, hosted in Ireland, used by your company alone. Lesson 6 gives you the detail to answer properly.
Write the announcement badly on purpose, then cut it
Draft everything you think people need to know, then remove everything that is not one of the three items above. The announcement that works is short, names the date, names the person to ask, and says what changes on Monday. The announcement that does not work explains the platform.
Check, rather than assume, two weeks in
Two weeks after the portal opens, go and find out how it is actually going, because the failures are quiet ones and nobody reports them.
Ask your managers whether requests are still reaching them another way. A request sent by chat was never in the platform, so asking is the only way to find out. If the answer is yes, that is a conversation with that manager rather than anything to reconfigure.
Ask the people running your onboarding flows whether the assigned tasks are actually being done, or quietly skipped. A task that is always skipped is either unclear or genuinely unnecessary, and either is worth knowing.
Find out whether people have signed in at all. Ask your setup contact what the platform can show you here, because it is the single most useful number in the first month: if a third of your team has never signed in, your announcement did not land, and sending it again costs you nothing.
None of this is visible if you only ask people whether it is going well. They will say yes.