Publishing in-app guidance takes about a minute: tick the boxes in the editor, press publish. The return only starts when the people it was built for know it exists, know why it helps them and go looking for it. On the builds we deliver (Fiducia is a certified WalkMe partner), the launch is the step most likely to fall into a gap, because the build contract usually ends at acceptance and the business assumes the project team has it covered.
Because nobody told the users it was there. One of our delivery leads tells the story of an early project where the team built exactly what the client asked for, suggested announcing it, and was told there was no time. A month later the question came back: why is nobody using this? The guidance was fine. Nobody had introduced it.
The structural reason is that change communication sits outside most fixed-price build contracts, reasonably enough, since the builder does not know the culture or the channels. The gap between "out of scope for the builder" and "owned by someone in the business" is where launches quietly fail. Gallagher's 2026 Employee Communications Report, drawing on more than 1,300 communications and HR professionals across 40 countries, found that 61 per cent of organisations have no formal approach to change communication, even though respondents ranked change management as their most valued communications skill. Assume there is no plan until you have seen one.
The sponsor, in writing, with team leads repeating it. Prosci's benchmarking research has placed active and visible sponsorship at the top of the list of contributors to change success in every report since 1998, and its participants say employees want to hear about a change from two people: the person they report to and a leader at the top. Senior leaders are the preferred senders for the business reasons behind a change.
In practice that means the project team drafts the launch message and asks the sponsor to send it under their own name. People are far more likely to open an email from a senior leader than to read a newsletter item. Then ask the super users or team leads to give their own teams a thirty-second heads up at the next regular meeting.
What is in it for the person reading it, in their words. Not "we have deployed a digital adoption platform". Something closer to "the system will now show you what goes in each field as you go, so fewer requests bounce back". Write the sentence that answers "why would I bother?" first, and keep the message to one idea.
Resist urgency. Gallagher's report also found that 83 per cent of respondents believe information overload is a growing problem, and William Ziebell of Gallagher warned that "if every message carries a sense of urgency, employees begin to tune out rather than listen closer". Optional help announced as a crisis will be ignored like one.
The ones people already read, plus the platform itself. The strongest launch channel for in-app guidance is in-app: a short announcement (WalkMe calls these ShoutOuts) that appears when someone opens the system, with a one-click tour that points to where the help now lives, the action bar, the menu, the question mark. It meets people at the moment of need, and it is a good first build for the client's own team.
Around it, use what exists: a teaser banner for the week before go-live, the newsletter or Teams channel people actually read, the sponsor's email, the team lead's mention. A video is fine if your people watch videos. We have seen polished ones go completely unwatched, so treat it as optional rather than the centrepiece.
Usually no. Super users earn their keep in testing, and they are the wrong launch audience. Guidance is built for the people who do not know the system well, and the experts' reaction will be that they do not need it. Launch to everyone in scope at once, with the super users briefed to field questions.
Set the baseline and the readout window before go-live, and confirm the tracking is recording correctly before you announce anything. Then measure what the guidance was built to change: how many people start a walkthrough and how many finish it, smart tip views, the in-guidance thumbs up or down, and help requests through the support form, each against the pre-launch baseline.
Choose the readout date with care. A go-live in the second week of December followed by a thirty-day readout gives you holiday numbers and a sponsor who thinks the thing failed. Pick the window that reflects normal working, agree it with the sponsor, and put it in the diary.
Fiducia is a certified WalkMe partner. We build and launch in-app guidance for organisations that want the systems they have already paid for to pay back.
Tell us what you are rolling out and where adoption, automation or AI is sticking. We will come back with a clear plan for the first steps, what success looks like, and what it costs. No fifty-slide pitch.
Book a call