Here's a pattern I've seen more than once. Someone in ops reads about a breach, gets nervous, and signs up for a team password manager. They move their own logins in, feel good about it, and send a Slack message: "Hey all, we're using this now."
Three months later they're still the only real user. The shared spreadsheet is alive and well. The subscription quietly renews, or gets cancelled as "not a fit."
The tool usually wasn't the problem. The rollout was.
Why do password manager rollouts fail?
Mostly because they're treated as a purchase, not a change in habits. The common reasons:
- It stays a one-person project. The person who bought it uses it. Nobody else has a reason to.
- The old way still works. If the spreadsheet or group chat is still there, people use it. It's familiar and it's one click away.
- The first experience is annoying. Another account, another master password, another extension to install. People give up at the first friction.
- Nobody knows what goes in it. "Put your passwords in" is vague. Which ones? Personal? Shared? All of them?
Start with what people share, not what they own
This is the single biggest lever. Don't ask people to move their own passwords on day one. Instead, put the shared logins in first: the social accounts, the design tools, the supplier portals.
Why it works: when the only place to find the Canva login is the password manager, people open the password manager. Usage follows need. Personal passwords can come later, once the habit is there.
A rollout plan that actually sticks
Week 1: set it up properly
- Pick one owner. Not a committee. One person who cares.
- Connect it to your identity provider. If you're on Google Workspace, this means sign-in with Google and syncing your existing Groups, so teams get the right access from the start.
- Move all shared logins in, organised by team. Clean out dead accounts as you go.
Week 2: start with one team
- Choose a friendly team, ideally one with lots of shared accounts. Marketing is often perfect.
- Sit with them for 20 minutes. Install the extension together, show autofill, show how to share one item.
- Ask what's confusing. Fix it before the next team.
Weeks 3 to 4: everyone else
- Roll out team by team, not all at once.
- Add it to onboarding, so every new hire gets access on day one.
- Delete the old spreadsheet. Announce that you've done it.
That last step feels harsh. It's also the moment adoption jumps, every time.
How do you reduce friction on day one?
The first five minutes decide whether someone comes back. A few things help a lot:
- Reuse the login people already have. For Google Workspace companies, a password manager that signs in with the Google account removes the "new master password" hurdle entirely. Tools like Passwd are built around this.
- Autofill everywhere. If people have to copy and paste, they'll save passwords in the browser instead.
- Pre-filled vaults. Someone logging in for the first time should already see their team's logins waiting for them. An empty vault is a dead end.
- No approval queues for the basics. Let people save and share within their team without asking IT.
What should you measure?
You don't need a dashboard. Check three things after a month:
- How many people have logged in more than once. One login is curiosity. Repeated logins are adoption.
- How many shared items exist per team. If a team has zero, they're still using something else.
- Whether the old spreadsheet is really gone. Search Drive for "password" and "logins." You might be surprised.
If adoption is stuck with one or two people, go back to the shared-logins step. It almost always means the team has no reason yet to open the tool.
What about the people who push back?
There are usually two types.
"I have my own system." Fine for personal accounts. But company logins belong to the company, and they need to be accessible when that person is on holiday or leaves. Frame it as protecting them from being the single point of failure.
"This is slowing me down." Take this seriously; it often points to a real setup issue. The extension isn't installed, autofill isn't working on a certain site, or they don't have access to the right group. Fix the friction and the complaint usually goes away.
The real goal
A password manager isn't a security project with an end date. It's a habit. The goal is that three months from now, nobody asks "what's the login for X?" in Slack. They just open the vault, or better, autofill does it for them.
Get the shared logins in, delete the spreadsheet, and make the first five minutes painless. The rest mostly takes care of itself.
