The document discusses the impact of consumerization on enterprise applications, emphasizing that employees are now more knowledgeable and creative in managing their work. It highlights the challenges and complexities of integration, data formats, security, privacy, and vendor lock-in while proposing measures like complexity reduction and education to improve enterprise IT. The ultimate message is the need for organizations to adapt to a changing IT landscape driven by employee engagement and technological advancements.

1. Alliander IT CIO Office
Michel de Goede
The Influence of Consumerization on Enterprise Apps

2. Situation
2

3. The Pressure
3

4. What does this button do?
4
Video: www.youtube.com/watch?v=WkDCS8xeobg

5. IT is a part of your employees daily life
Your employees have become
computer literate. And reviewed or
rated apps are available 24/7.
5

6. Your employees know better how to perform work
safely and efficiently than you or your IT department
Source: Alliander Annual Report 2014
6

7. Your employees are creative and involved
Trying to stop your employees from
creatively managing their work is like
pushing water uphill with a rake.
7

8. Before: IT in the lead
See also ISO/IEC 25010 for Software Quality considerations
8

9. Now: user in the lead
See also ISO/IEC 25010 for Software Quality considerations
9

10. What could possibly go wrong?
Image: www.taxistartup.com
1. Back-end integration
2. Data and file formats
3. API’s
4. Security
5. Privacy
6. Vendor lock-in
7. Non-functionals
10

11. 1. Back-end integration then
11

12. 1. Back-end integration now
12
Source: Marcel van Driel, Eduard Lagendijk, Alliander

13. 1. Back-end integration forseeable future
13
Source: Marcel van Driel, Eduard Lagendijk, Alliander

14. 1. Complexity
‘The complexity of a system is a
function of the number of states in
which that system can find itself’.
Source: Roger Sessions, Object Watch
14

15. 1. More complexity
Source: Roger Sessions, Object Watch
‘Glass’ Law states that for every 25%
increase of complexity in the problem
space, there is 100% increase of
complexity in the solution space’.
Roughly a power of 3.1!!!!
15

16. Counter measure 1: complexity reduction
Adaptation of material from Roger Sessions, Object Watch. Productivity comparison: ISBSG
Total system complexity is a function
of the number of business functions,
the number of system connections
and the complexity of the platform.
Calculation: bf3.1+ sc3.1+ pc3.1
16

17. Counter measure 1: more complexity reduction
Source: Roger Sessions, Object Watch
17

18. 2. Data and file formats
• Prezi is a great tool, but can you REALLY
combine it with Powerpoint (corporate standard)?
• Your home-baked customer switching app is
great, but does it connect to (the Dutch legally
obliged) EDINE messaging services?
• Are you sure that the transactional integrity in the
ERP part of your BigSQL back-end is OK?
18

19. Counter measure 2: decouple on interface
specification
Images: Query Surge, Object Watch, Journal Dev, Microsoft, Free Powerpoint Templates, BI Tools
19

20. 3. API’s
20
Quote from James Governor, RedMonk for TechTarget / Search SOA
‘it is like API management is the new SOA’

21. Counter Measure 3: maximally autonomous
microservice API’s
21
Image: http://www.grahamlea.com/2015/03/microservices-tyro-evolution-presentation/

22. 4. Security = goal - risk
22

23. 4. Cyber security = goal - a lot of risk
23

24. Counter measure 4: stop fortification, be resilient
24
Resilience can be obtained by moving away from typical barrier enhancement
risk-measures. Consider the following options:
• Ignore, the ostrich ‘see-no-evil-hear-no-evil’ tactic;
• Accept, the potential impact of some risks may be deemed acceptable to your organization;
• Reduce, e.g. the potential impact or probability of occurrence of a risk, like the banking app;
• Transfer, use insurance or subcontracting to transfer potential consequences of risk;
• Avoid, not entering the type of business that may incur potential risk impact deemed too high;
• Exploit, risk is also an opportunity and high risk investments may yield high returns.

25. 5. Privacy
25
Source: EU

26. 5. Privacy
26
35 percent of IT leaders and 25 percent of IT
professionals are not confident that their
organization's BYOD policy is compliant with data
and privacy protection acts, supra national
legislation or other mandated regulations.
Adaptation from www.cio.com

27. Counter measure 5: Educate
27
You cannot stop water from flowing, but you CAN
educate your staff on privacy concerns.

28. 6. Vendor lock-in
28
Images: SAP, Nest, Samsung, Oracle, Apple, Google, Amazon

29. 29
6. Vendor lock-in
Images: Kotler, www.startitup.co, www.bmimatters.com

30. Counter measure 6: manage orchestration
30
Image: https://jcastellssala.wordpress.com/2012/03/27/webservices-orchestration-choreography/

31. 31
7. Non-functionals
1. Security
2. Service Level
3. OTAP
4. Capacity Estimates
5. Management
6. Disaster Recovery
Source: IBM

32. 32
Counter measure 7: shared responsibility
Image: www.plainadventure.com

33. 33
Seven measures
1. Complexity reduction
2. Decouple on interface
3. API autonomy
4. Be resilient
5. Educate
6. Manage orchestration
7. Shared responsibility

34. One key
Image: www.motomatrix.co.uk
34

35. Enterprise IT has moved from a monopoly to
perfect competition
Image: http://hubhomedesign.com/difference-between-monopoly-and-oligopoly
35

36. E=Q*A
36
You may have to change 9-5 into output driven
You may have to introduce IT behavior related KPI’s
You may have to educate your employees
But you MUST have your employees on board or else…..

37. Questions?
Thank you!
37