Story 1 — Large Mailbox Migration
Use for: changing requirements, unexpected problem, pressure, customer communication, proactive improvement.
Search keywords: large mailbox migration changing requirements pressure unexpected problem customer
30-second answer
During an Exchange-to-cloud migration at Dinotronic, we discovered that one user's mailbox was much larger than our normal process could handle. I raised the risk early instead of letting it delay the batch. We agreed on an interim approach: restructure the mailbox so the user could continue working, while older email was handled separately with Microsoft backend support. The migration stayed on schedule, and afterward we started identifying unusually large mailboxes earlier during planning.
STAR answer
Situation
We were migrating users in batches from Exchange to the cloud. During one migration, we discovered that one user's mailbox was much larger than our standard migration process was designed for. There was a risk that this single mailbox could delay the whole batch.
Task
My priority was to keep the overall migration schedule on track while making sure the user could continue working normally.
Action
I raised the issue immediately with our customer-success team and discussed the available options instead of waiting for the migration to fail or hoping it would finish eventually.
We agreed on an interim approach. We restructured the mailbox folders so the user could continue working with current email, while older email was handled separately with support from Microsoft's backend team.
The key decision was to separate the user's immediate business need from the technical migration problem.
Result
The main migration stayed on schedule, and the user had no disruption to their current email workflow.
Afterward, we changed the planning process so unusually large mailboxes were identified earlier and the potential impact was communicated before migration started.
Lesson
When an unexpected technical problem appears, I prefer to raise it early, separate immediate business impact from the technical root cause, and work with the relevant stakeholders on a practical solution.
Good follow-up points
- Why didn't you just wait? Because the mailbox could affect the batch schedule, so the risk needed to be handled early.
- What did you personally do? I identified/escalated the risk, worked through the options with customer-success, and helped agree on the interim approach.
- What changed afterward? Large mailboxes became an earlier planning and communication checkpoint.