We have taken a fresh approach and used Design Thinking to built a two day Workshop to deliver Microsoft Teams adoption. Supporting employee with adopting it as a way to get work done.
We have developed a two-day workshop which uses Design Thinking methods developed by our GamesSquad to get Microsoft Teams adopted by employees across the customer organisation. We use a “learning by doing” approach and focus not on Microsoft Teams as a tool but rather what the tool is used to accomplish. We uncover the initial use-cases which will allow all employees to fully realise the value of Microsoft Teams. We will achieve the following deliverables and outcomes through this two-day course. We develop a group of employees to be Microsoft Teams Champions and continue to instil it as a way of working across the organisation. The workshop provides a set of use cases which are directly related to the way the employees work, their priorities coupled with the Microsoft Teams Application functions. We build a clear roadmap of installing the relevant use cases across the related business area with a set of activities to achieve this.
Agenda: Day 1 • Welcome Meet & Greet and introductions • Imagine our future of collaboration • Understand the organisation structure and map deliverables to roles and areas • Break • Map out the current ways of working and what we feel we should start, stop and explore doing • Lunch • Connect how information and work flows across the organization • Build “How might we .... “statements around ways of working • Break • Show and tell of Microsoft Teams and explain where it fits into the context of all Office 365 tools
Day 2 • Welcome back and recap • Exploring the collaboration solution space identifying use cases • Break • The how and when part to use Microsoft Teams in order to define and narrowing down on the crucial use cases and their importance • Connecting our chosen use cases to Microsoft Teams • Lunch • Build out low fidelity prototyping of a set of use cases • ‘Think aloud testing’ of the use cases • Break • We build out the requirements, timelines, risks and critique our ideas in a safe space using Concept Posters