-
Notifications
You must be signed in to change notification settings - Fork 3
/
onepager-why-adoption-projects-fail.md`
53 lines (36 loc) · 2.12 KB
/
onepager-why-adoption-projects-fail.md`
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
# Why adoption projects fail
## key messages:
* organisations want to roll out Microsoft 365 to solve a broad variety of business problems like for instance information silos, unconnected workforce, waste of time etc., but problems persist if we only assign software licenses to users and don't take new working behavior into account
* the issue is not to learn how to use new tools to achieve a new behavior, but to know why we need to evolve ways of working (to solve different problems)
* usual approaches to achieve adoption are not sustainable, because users will quickly fall back in old behavior.
* usual approaches are also just scratching the surface, because they focus on quick wins instead of aiming to resolve organizational issues in a meaningful way
* same old thinking same old problems
> image
## sketchnote icebergmodel M365 pre
1: more busy than productive
lack of focus
2: workaround for dysfunctional processes, communication patterns, and organizational structures.(multitasking, task switching, unconnected workforce)
3: hierarchy that does not reflect workflow, segmentation (information silos)
4: command & control, knowldge is power (this system is broken)
## our way: 'from 😱 to 😎'
* discovering organizational problems
* verbalizing corporate culture and values that support our mission and business goals
* investigating which structures can foster these goals and unblock employees
* defining how we can leverage Microsoft 365 concepts to support business outcomes
* transforming dysfunctional structures and patterns into meaningful collaboration & purpose-driven- working behavior
## audience
* C-Level
* IT Decision Makers
* IT administrators
## key facts
* 5 half-day workshops
* 10 person max
* 2 days documentation of workshop outcome
* 2 days concept for actionable next steps
= 13 days
## goals
* gain insights of challenges and how to overcome them in Microsoft 365 adoption
* become aware of complex organizational systems
* achieve problem solving competence
* prepare for sustainable change to future-readiness
* recognize patterns, structures and corporate culture as main driver of digital transformation