Slack Migration Retro Thoughts

Manssur94 commented 5 days ago

What went well:

Very Organized and well prepared (great playbook)
Project team (Matt and Jill) were around most of the time and replied to questions quickly
Great team collaboration
Quiet channel after Day 1-2 shows great stakeholder management (comms & expectation setting)
Overall process was well planned and executed (give folks time to flag any channels missed, then start with migration)

Manssur94 commented 5 days ago

What didn't go well:

No way for stakeholders to check status of their channel (which workspace)
Overload for specific team members (Specifically Matt and Workflows team who all worked extended hours several times)
Escalated Team Expectations
- Partly not enough context on guidelines/expectations (e.g. intentionally remove access to certain channels to come through escalated support) - could have been more aligned here and communicate this with stakeholders and our team (e.g.
- E.g. BPO escalated channels - got a lot of requests to bridge channels, but there was no clear communication that this shouldn't be done. For BPOs and Escalated Teams in general, expectations should have been with stakeholders and within our teams when channels should be bridged
Workflows team being very busy Day 3-5 without leveraging Channel folks, even though channel was very quiet

Manssur94 commented 5 days ago

What could we do differently:

Create enablement/tooling resources that allow stakeholders to check status of their Slack Channels only
More detailed information on how to support channel in advance
- Tone, Positioning, usage of available resources etc.
- Feedback was given at later time to not share and quote resources
- In discussion in channel it was mentioned to not apologize, but later we were told to show more empathy etc.

Manssur94 / Manssur-Personal-Tasks