1 min lesson
Sequence to minimize disruption and gaps
Use the lesson to respond to this: "Scenario: 'We just acquired a 40-person company. Integrate their IT into ours in 30 days.' Walk through your plan and the risks you're actively managing." Keep the answer plain.
Step 1 of 2
Sequence to minimize disruption and gapsthe part that shows you've done it
The risk in any cutover is twofold: locking people out of tools they need and leaving a security gap during the transition (two IdPs both live, stale admin accounts, devices half-enrolled). Sequence so each step is reversible and the window where both old and new systems are active is as short as you can make it.
- Phase, don't flag-day
- Migrate by team or app, validate each wave before the next
- Rollback per step
- Every cutover step has a defined undo, so a bad wave doesn't strand people
- Close the seams
- Disable the old IdP path and stale admin accounts the moment a wave completes - don't leave both live
- Communicate relentlessly
- Acquired employees are anxious; clear comms on what changes and when reduces tickets and friction
Expect a scenario like "how would you integrate a 40-person acquisition in 30 days." Don't dive into one tool - walk the playbook: inventory, consolidate identity/domains, migrate to least-privilege (not a copy of their access), re-enroll devices via MDM, de-dupe SaaS. Then volunteer the two risks you're managing - lockout and the security gap of running two IdPs - and your phased, reversible sequencing with relentless comms. Naming the failure modes unprompted is what shows you've actually done an integration.