Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Map of every login and account store in use
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most organisations that think they have one directory actually have five: a Microsoft or Google tenant, an old on-premises Active Directory, the HR system, and dozens of apps holding their own usernames and passwords.
First tasks
- List the directories and tenants you already administer, with their admin URLs
- Export a year of software charges from finance and add every app found
- Record the sign-in method and admin owner for each app on the list
- Flag the ten apps that hold customer, financial or HR data
Choosing a workforce identity provider
The identity provider becomes the front door to every app, so switching later is a multi-month migration nobody wants. Comparing two or three serious candidates against your real app list, directory, device estate and budget, rather than a feature grid, means the choice holds for the next five years.
First tasks
- Write the requirements list from the account store map
- Shortlist three providers and request trial tenants
- Connect your three hardest apps to each trial tenant
- Record the decision with pricing tier and reasons the others lost
Deciding the authoritative source for staff records
Accounts drift when two systems both think they own a person's name, title and manager. Deciding that the HR system creates people and the identity provider creates logins, or the reverse for a small team without HR software, settles every later argument about which record is right.
First tasks
- List the core identity fields and where each one is edited today
- Book a 45-minute session with the HR lead to agree field ownership
- Draw the sync direction between HR, directory and identity provider
- Write the correction rule and get both leads to sign it