Rolling out a new comms tool to a shift-based team
Head-office rollouts assume everyone is at a desk. Here's the version that works for shifts.
Software rollouts are usually written for people with a laptop, a work email address and a quiet hour for training. Shift teams have none of those.
What follows is the order that actually works.
Start with one thing worth opening the app for
Don't launch nine features. Launch the rota, or the day's notices, or the one thing people currently have to ask a manager for.
Adoption follows usefulness, not training.
Sign-up must fit in a tea break
One link, name, email, password, done. No invite codes read out over the phone, no waiting for IT to create an account.
Put the managers on first, a week early
If the first question a new user asks gets a shrug, the rollout stalls. Give supervisors a week's head start so they can answer.
Retire the old channel on a date
Two channels means neither is trusted. Announce the date the old group chat closes, then close it.
Zenivo puts all of this in one app
Announcements with confirmations, team chat, guides, surveys and — on the paid plans — phone numbers, a shared text inbox and a company mailbox.
More to read
New articles by email
Leave your email and we'll send each new piece as it goes up.
One address, no sharing with anyone else. You can ask to be removed at any time.
