The first sixty days after an employee experience app launch

Launch week is a poor time to judge an employee experience app. Managers are asked to log in during a town hall. Someone walks the hall with a tablet. The vendor is still on the call. The counts look busy. Six to eight weeks later the picture is closer to ordinary work: some sites still open the check-in, others never finished the first password reset.

That is why we time a rollout usage review after week six, not during the ribbon-cutting.

Usual shapes

A first-open spike on the go-live date, a smaller spike on the first reminder, then a slide. Office groups remain. A plant with a QR code in a canteen that night shift does not use goes quiet. Contractors who were promised access still bounce at the login because they were never in the file. A Bahasa toggle left off for one module produces a neat English-only trail that HQ misreads as preference.

None of these shapes mean the app was a mistake. They mean the launch story and the roster were not the same document.

What to bring at week six

Bring first-open, repeat-open, and a list of groups that never appeared. Bring the training dates and the poster locations if you used posters. Bring any known signal problems. We would rather label a dead zone than invent a people-theory for it.

If a festive holiday ate a week of the window, write that on the map. A “drop” that sits on Hari Raya travel is not a rejection of the check-in.

The write-up from this kind of review is short on purpose. It is for the programme owner and the person who still has the vendor on speed dial. It names groups, not a second scoreboard.