Team & People
Team Password Manager and MFA Rollout: Retire Shared Passwords, Plan Exceptions and Backups
Intermediate | 4 whiteboard pages · Task board: 4 columns (4 parent tasks, 12 subtasks)
Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.
Take shared passwords out of spreadsheets and chat and roll out a password manager and multi-factor authentication (MFA) to the whole team in weekly stages. The end state is that everyone signs in with an authenticator app or passkey, and every remaining exception sits in a table with a reason and a deadline. Start with a few people, then widen to office, field, and contractor staff week by week. SMS codes are weaker than authenticator apps and passkeys, so treat them as a stopgap with a deadline. Traps to check include stalling on SMS, exceptions that bring shared passwords back, support requests landing on one day, and a single password manager admin. Not sure where to begin? Copy only the service names and users from the sheet or chat that holds shared passwords, never the passwords. The whiteboard has 4 pages. The task board has four columns - not started, preparing, switching over, and verify it sticks - with 4 parent tasks and 12 subtasks.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Team Password Manager and MFA Rollout Board
How to use (4 pages): ① Write the goal and gather shared logins and pain points (sections①–⑤) → ② Compare methods and backups, and check the pitfalls (sections⑥–⑨) → ③ Set the order and exception deadlines (sections⑩⑪) → ④ Draw the timeline, weekly support, and admin handover (sections⑫–⑭)
1/4 Survey what is shared today
① Goal and scope of the rollout (start writing here)
- Goal e.g. Remove shared passwords from spreadsheets and chat, so everyone signs in with multi-factor authentication
- People covered and period e.g. 12 employees and 2 contractors. Roll out to everyone over 9 weeks
- Lead and contact e.g. The lead is the office administrator. The contact for trouble is the contracted IT vendor
② Shared logins (never write the passwords themselves)
| Where it lives now | Who uses it | MFA today | |
|---|---|---|---|
| Accounting software | e.g. Row 3 of the shared spreadsheet | e.g. Two in accounting and the owner | e.g. None |
| Inquiry mailbox | e.g. Pinned chat message | e.g. Five sales staff | e.g. SMS only |
| Official social accounts | e.g. The person in charge's notebook | e.g. One PR person and one contractor | e.g. None |
| Domain management | e.g. Only the previous owner knows it | e.g. Unknown. Check with the contracted vendor | e.g. Unknown |
③ Field staff pain points
- e.g. Asked to log in at a client's office and searching chat for the password
- e.g. Worried about being locked out when the phone battery dies
- Who you asked and date: ____
④ Office and accounting pain points
- e.g. Passwords known to someone who left were never changed
- e.g. Nobody knows who can get into which service
- Who you asked and date: ____
⑤ Contractor and part-timer pain points
- e.g. No company phone, and unwilling to install the app on a personal one
- e.g. Three people take turns on the reception device
- Who you asked and date: ____
2/4 Design the rollout
⑥ Compare authentication methods (pick what fits the services in ②)
| Best for | Watch out for | Backup | Fits services in ② | |
|---|---|---|---|---|
| Passkey | e.g. People used to face or fingerprint unlock on phones and PCs | e.g. Some services do not support it. Check each service's latest guidance | e.g. Also register a second device | e.g. Inquiry mailbox |
| Authenticator app | e.g. People who use a phone for work | e.g. Before changing phones, check that the accounts are moved or the app is backed up (see the app's latest guidance) | e.g. Generate backup codes in each service's settings, print them, and keep them in a locked cabinet | e.g. Accounting software |
| Security key | e.g. Admins and people who move money | e.g. If lost, you cannot get in. Prepare 2 keys per person | e.g. Keep the second key in a locked cabinet | e.g. Password manager admins |
| SMS code | e.g. People who cannot install the app, as a bridge until they move | e.g. Better than nothing, but weaker than authenticator apps and passkeys | e.g. Fix the registration before changing numbers. Keep backup codes too | e.g. Official social accounts (for now) |
⑦ Pitfall: stalling on SMS codes
- [What happens] e.g. You start with SMS, feel safe, and a year passes without moving to an authenticator app or passkey
- [How to check] e.g. Where a service shows each person's method in its admin screen, look there. Otherwise ask them, and count who is still on SMS
- [How to prevent] e.g. Treat SMS as a bridge until they move and write a deadline in the table in ⑪
- [Check result] e.g. 5 people on the inquiry mailbox are still on SMS. Owner: ____
⑧ Pitfall: exceptions pile up and it reverts
- [What happens] e.g. You keep granting exceptions for "it is urgent" or "no smartphone", and shared passwords are back six months later
- [How to check] e.g. Once a month, count the rows in the table in ⑪ and the rows past their deadline
- [How to prevent] e.g. Always write a reason, a substitute safeguard, and a deadline, and allow no exception without a deadline
- [Check result] e.g. 2 exceptions have no deadline. Owner: ____
⑨ Pitfall: everyone at once floods support
- [What happens] e.g. You ask everyone to switch on the same day, requests that someone cannot log in pile up in one day, and work stops
- [How to check] e.g. In the table in ⑬, compare the number switching per week with the number of support staff
- [How to prevent] e.g. Try with 3 people first, fix the guide, then widen week by week
- [Check result] e.g. The first plan had 11 people in weeks 3 and 4. Split it in two. Owner: ____
3/4 Set order and exceptions
⑩ Rank the services in ② (importance by ease of rollout)
Vertical axis: Importance (how bad if it leaks) / Horizontal axis: Ease of rollout
- Plan and proceed e.g. Domain management. Check the registrant and how to reach the admin screen with the vendor, then switch in phase 2
- Do first e.g. Accounting software and the inquiry mailbox. Switch them in phase 1 with an authenticator app
- Can wait e.g. Unused trial accounts. Make them candidates to cancel if not needed
- Do along the way e.g. Official social accounts. Add MFA when you move them into the password manager
⑪ Exception table (from the pain points in ③ to ⑤, write the reason, substitute safeguard, and deadline)
| Reason | Substitute safeguard | Deadline | |
|---|---|---|---|
| No smartphone | e.g. Cannot use a personal phone for work | e.g. Lend one company security key | e.g. Review at the end of phase 3 |
| Shared device | e.g. Three people share the reception device | e.g. Split into per-person logins and always lock the device when stepping away | e.g. Review in one month |
| Unsupported system | e.g. An old booking system does not support MFA | e.g. Share a long password in the password manager and limit it to 2 users | e.g. Until the day we ask the vendor about support plans |
| Traveling | e.g. SMS may not arrive at the destination | e.g. Switch to an authenticator app before departure | e.g. The week before departure |
4/4 Expand in phases
⑫ Timeline (from the order in ⑩ and exceptions in ⑪, write the weeks and the sign to move on)
- Start e.g. Monday of week 1. The lead and 2 admins set up the password manager
- Phase 1 e.g. Weeks 1-2. Try the ⑩ "Do first" services first, and move on once the guide is in one place
- Phase 2 e.g. Weeks 3-4. Office and accounting. Move on when "cannot log in" requests settle at 2 a day or fewer
- Phase 3 e.g. Weeks 5-6. Field staff and contractors. Move on once keys are lent to the people in the ⑪ exceptions
- Phase 4 e.g. Weeks 7-8. Check everyone's registration in the admin screen, then delete the passwords in the shared spreadsheet and chat
- Goal e.g. Week 9. Everyone signs in with MFA, and only 2 exceptions remain, both with deadlines
⑬ People, services, and support for each week
| People switching | Services switching | Support owner and hours | |
|---|---|---|---|
| Weeks 1-2 | e.g. 3 people including the lead | e.g. Password manager, accounting software, inquiry mailbox | e.g. The lead. 30 minutes from 4 p.m. daily |
| Weeks 3-4 | e.g. 5 people in office and accounting | e.g. Password manager, accounting software, domain management | e.g. The lead and 1 person who tried it first |
| Weeks 5-6 | e.g. 4 field staff and 2 contractors | e.g. Password manager, inquiry mailbox, official social accounts | e.g. The 3 who tried it first take 2 people each |
| Weeks 7-8 | e.g. The people in the ⑪ exceptions | e.g. The remaining services. Delete shared passwords, and change any that many people saw or that someone who left knew | e.g. The lead. Check the exceptions closest to their deadline first |
⑭ Pitfall: only one admin on the password manager (set the handover)
- What happens e.g. If the admin leaves or is away for long, nobody can touch the shared vault or the recovery settings
- How to check e.g. In the password manager's admin screen, look at how many people hold admin rights and who they are
- How to prevent e.g. Make two admins, and have anyone leaving hand over rights before their last day. Check the recovery steps in the tool's latest guidance and keep them on paper in a locked cabinet
Task board contents
Not started 16 items
Map shared logins
On page 1, write the goal and scope, then collect where shared logins live, who uses them, and each team's pain points. The list you build here feeds the comparison, order, and exceptions on the later pages. Press Ctrl+F (⌘F on Mac) and type "3/4" to jump to page 3.
Copy shared logins
A task you can start by opening one place. Open the spreadsheet or pinned chat message that holds shared passwords and copy the service, location, and users into the table in section ②. Never copy the passwords. Done when 4 rows are filled.
Set goal and scope
In section ①, write the goal, the people and period covered, and the lead and contact. Once the headcount and period are set, you can build the weekly plan on page 4.
Gather team issues
In sections ③ to ⑤, write two pain points each for field staff, office and accounting, and contractors and part-timers. Done when each has who you asked and the date. These feed the exception candidates in section ⑪.
Design the rollout
On page 2, compare each authentication method by who it suits, what to watch for, and the backup, then check the easy-to-hit pitfalls first. Page 3 applies the shape you set here to each service.
Compare methods
In the table in section ⑥, write who each of passkeys, authenticator apps, security keys, and SMS codes suits and what to watch for. Note that SMS is weaker than authenticator apps and passkeys.
Set backup methods
In the backup column of section ⑥, write how to get back in for each method if the device is lost. Done when you have decided where the backup codes are kept.
Check the pitfalls
For each of the three pitfalls in sections ⑦ to ⑨, write what happens, how to check, how to prevent it, and the result of the check. The results feed the tables on pages 3 and 4.
Order & exceptions
On page 3, rank the services from section ② by importance and ease, then put anyone or anything that cannot switch into an exception table with a reason, a substitute safeguard, and a deadline. Leaving no exception without a deadline is the key to this step.
Sort services in 4
Place the services from section ② in the four areas of section ⑩. Those in Do first become the targets of phase 1 on page 4.
List exceptions
From the pain points in sections ③ to ⑤, write what cannot switch right away as rows in section ⑪, then fill in the reason, substitute safeguard, and deadline.
Announce deadlines
Tell each person in a row of section ⑪ the substitute safeguard and the deadline, and get their agreement. Done when everyone has been told.
Roll out in phases
On page 4, draw the timeline from start to everyone, set the people and support owner for each week, and write a handover so that there is never only one admin. Track people who switched in the Switching over column and move them to Verify it sticks once requests settle.
Draw the timeline
In the six steps of section ⑫, write each phase's weeks and the sign to move on, based on the order in section ⑩ and the exceptions in section ⑪. Put the people and services in section ⑬. Done when the goal step has the end state.
Plan weekly support
In the table in section ⑬, write who and which services switch each week, plus the support owner and hours. Done when the number switching in a week is what one support owner can handle.
Set admin handover
In section ⑭, write what happens, how to check, and how to prevent it when the password manager has only one admin, then name a second admin. Done when the admin screen shows two admins.