<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Shadow IT: Steroids for Innovation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mario Silic</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dario Silic</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Goran Oblakovic</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Institute of Information Management (IWI), University of St. Gallen</institution>
          ,
          <country country="CH">Switzerland</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Zagreb School of Economics and Management</institution>
          ,
          <addr-line>Zagreb</addr-line>
          ,
          <country country="HR">Croatia</country>
        </aff>
      </contrib-group>
      <fpage>113</fpage>
      <lpage>120</lpage>
      <abstract>
        <p>Shadow IT is relatively new and emerging phenomenon which is bringing number of concerns and risks to the organizational security. Past literature has mostly explored the “negative” effects of the Shadow IT phenomenon, including, for example, the security aspect where Shadow systems are said to undermine the official systems and endanger organizational data flows. But, they are also said to increase innovation. However, the current literature does not provide any evidence of a possible innovation increase. We used three methods to understand if Shadow IT can be an important source of innovation for firms: 1) Single case study with international firm that adopted Shadow IT; 2) Interviews with 15 IT executives and 3) Focus group using twitter as enabling tool to interact with 65 IT professionals. Our study reveals that Shadow IT can be an important source of Innovation for organizations. Finally, our research brings new theoretical contributions for researchers and important insights for practitioners. We also provide limitation and future directions for research.</p>
      </abstract>
      <kwd-group>
        <kwd>Shadow IT</kwd>
        <kwd>software</kwd>
        <kwd>organizational IT</kwd>
        <kwd>shadow systems</kwd>
        <kwd>information security</kwd>
        <kwd>innovation</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Shadow IT represents all software, hardware, or any other solutions used by
employees inside of the organizational ecosystem which did not receive any prior formal
IT department approval. “I got to do my job, I have to do it fast and I’m confident that
the benefits will outweigh the risks.” - is a typical answer to the question of why
employees are using something that is non-approved and consequently, is illegal.</p>
      <p>
        User of these Shadow systems can be any employee that is looking to solve its own
needs. Sometimes, this user innovation can be source of a successful commercial
product. Sports equipment such as the rodeo kayak [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], mountain bike [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], snowboard
[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], and surfboard [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], medical equipment [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], juvenile products such as the baby
jogger [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], services such as computerized commercial banking services [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], computer
games [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], and films in the animation genre [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] are few examples where user
innovations was a success. Can Shadow IT really be considered as an important source of
innovation for firms? Shadow IT is relatively a new and emerging phenomenon which
is bringing number of concerns and risks to the organizational security. Past literature
has mostly explored the “negative” effects of the Shadow IT phenomenon, including,
for example, the security aspect where Shadow systems are said to undermine the
official systems [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] and endanger organizational data flows [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. But, they are also
said to increase productivity and innovation. However, the current literature does not
provide any evidence of a possible innovation increase. We are missing a deeper
understanding of the phenomenon and its link with innovation.
      </p>
      <p>
        The objective of this paper is to show that the Shadow IT is an important source of
innovation for organizations result of illegal activities performed by employees. To
achieve our objective we are using a triangulation approach combining three different
methods 1) revelatory qualitative case study [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] with a global firm that had
successfully adopted Shadow IT innovation process; 2) Interviews with Chief Information
Officers (CIOs) and 3) Online focus group using Twitter as enabling tool.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Theoretical background</title>
      <p>
        Shadow IT defines the same autonomous developed systems, processes and
organizational units developed without awareness, acceptance, knowledge and support of the
IT department [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. Shadow IT phenomena can be seen as an important security
threat [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. It is also an “insider-threat” where there is strong non-compliance
behavior of employees related to the information security policies [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. “If users do not
comply with ISsec policies, ISsec measures lose their efficacy” [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. Furthermore,
Shadow IT has an important dual-use context [
        <xref ref-type="bibr" rid="ref17 ref18 ref19">17-19</xref>
        ] where its use can have positive
and negative consequences. On the possible negative consequences there is the
possibility to undermine the official system [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ], endanger organizational data and
processes [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. On the positive side, Shadow IT can be very efficient and effective
when used instead of the formal and standard systems in place [
        <xref ref-type="bibr" rid="ref20 ref21">20, 21</xref>
        ]. Shadow IT is
usually situated at the organization borders where it fills the existing gap between
users and the solutions provided by the IT department [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]. This is typically business
and IT alignment domain which should reveal the organizational capability to fulfil
business needs with IT capabilities [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. That means that IT should be the enabler of
business objectives and should strive achieving them in the most efficient way [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ].
The lack of alignment between business and IT creates an ideal environment for
Shadow Users for the creation of the Shadow Innovations.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Research design</title>
      <p>This paper utilizes a triangulation approach that combines three different methods in
order to improve accuracy and strengthen our findings.</p>
      <p>
        Firstly, we wanted to collect insights from real-life examples where Shadow IT has
been implemented. As currently, Shadow IT studies in the innovation context are
scarce, we wanted to study one case in depth that would provide us rich understanding
of the phenomenon. Single case studies allow researchers to get unique and deep
insights of the case under study, especially if the case is extreme, unique, or revelatory
[
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. The organization that we studied was an appropriate case as it openly adopted
Shadow IT by incorporating it within its information systems (IS) policies.
Organization is a medium size international company that has 1,500 employees.
      </p>
      <p>
        Secondly, we aimed to understand the practitioner’s perspective about the Shadow
IT topic. We used qualitative method which was appropriate given the high degree of
uncertainty surrounding the phenomenon under study. That means, not enough was
known a priori about Shadow IT usage and its impact on Shadow Innovations to
quantitatively measure it or pre-specify its outcomes. Therefore, qualitative method
provided a very rich understanding of the underlying mechanisms, activities, and
behaviors that define Shadow IT use actions by Shadow Users. This involved the
collection and analysis of empirical data using a qualitative research approach.
Qualitative research is defined as “the use of qualitative data such as interviews,
documents and participant observation data to understand and explain social phenomena”
[
        <xref ref-type="bibr" rid="ref25">25</xref>
        ]. [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ] observed that qualitative research methods are designed to help researchers
understand people and the social and cultural contexts within which they live. [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ]
also notes that “interviews can be useful tools for unpacking motives and
experiences”.
      </p>
      <p>Thirdly, as we wanted to leverage the generalizability of our findings we created an
online focus group by using Twitter platform. With this approach we were able to
target and involve high number of CIOs (already members of the highly visited CIO
web portal).
3.1</p>
      <sec id="sec-3-1">
        <title>Data collection</title>
        <p>We conducted semi-structured interviews for the single case study (1 interview with
CIO and 1 with Vice President of IT) and the interviews with executives (15
interviews) that were selected from different organizations: large firms (40%), security
companies (20%), governmental agencies (20%), and independent experts (20%). Out
of 15 interviewee, 12 were CIOs and 3 were IT executives (1 IT director, 1 VP of IT
and 1 Chief Technical Officer - CTO).</p>
        <p>For the focus group study we used Twitter as a platform where any CIO was able
to post its comments. We had 65 different CIOs that posted at least one tweet (post on
Twitter) with a total of 320 unique tweets.</p>
        <p>Interviews were designed as set of open ended questions with an idea to cover the
Shadow IT topic in depth. Overall, the interviews duration was between 38 and 72
minutes, with an average of 53 minutes. Interviews were conducted between February
2013 and September 2014. All interviews were recorded except one (interviewee
declined to be recorded – notes were taken).
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Results</title>
      <p>In this section, we will present the results.</p>
      <sec id="sec-4-1">
        <title>Single case study</title>
        <p>Results from the single case study clearly pointed out that Shadow IT is an important
source of innovation. For interviewee (C1): “Shadow IT is innovative. We are
pioneering new ways for employee to do their Job. Their job tasks are no more
restrictive by the IT tools deployed by IT.</p>
        <p>With shadow IT, the methods of collaboration with outside clients, the ability to
share files and use mobile devices to communicate whilst integrating with our
infrastructure anywhere are innovative ways of how employees are doing their jobs. Their
jobs scan be done anytime, anywhere and most of the time by any devices are all
possible because of Shadow IT tools and services.". However, as pointed out by (C2)
Shadow IT needs to be promoted and encouraged with the organization as by doing so
new innovation solutions will appear: “With the proliferation of social media and rich
media contents, creation and distribution of media assets are now done beyond the
confines of an IT local infrastructure. To allow employees to work beyond the
boundaries of the local infrastructure and systems, Shadow IT will need to be encouraged.
This will further enable the IT organization within a media organization to
collaborate with shadow IT clients to build innovation IT solutions to meet users/clients
expectations.”</p>
        <p>Still, perception of Shadow IT in light of all the risks remains relatively negative
and organizations tend not to unleash the potential behind Shadow IT and enable
Shadow employees to be freer in the employee-IT relationships when it comes to
leveraging shadow practices. Indeed, for (C1) companies are still reluctant to adopt Shadow
IT “because most of the products that are used in Shadow IT are consumer graded
and the security modules that are in the free offerings are not sufficient for data
security. Additionally, when users are involved in technology selection, business processes
are not necessarily taken into consideration.”.
4.2</p>
      </sec>
      <sec id="sec-4-2">
        <title>Interviews</title>
        <p>From the interviews it became clear that Shadow IT is not really such a new
phenomenon in itself as users were always trying to bypass IT to come up with their own
solutions and tools enabling faster job processes. However, what has recently changed
is the arrival of the new technologies such as cloud services, software-as-a-service
tools, mobile apps that enabled people to be more innovative through the technology.
For example, (A4) says that “…the phenomenon is nothing really new…however we
are witnessing a plethora of new tools and services. Hence, it is more about your job
performance and how to optimize it using the innovative technologies available out
there. But also, what is the role of IT in this new structure – how IT should be
positioned: to allow or disallow?”.</p>
        <p>For most of the interviewees the right question is how to expand the innovation
teams to a wider population of all employees as good idea can come from any
employee and not just from a limited number of people. (A9) argues that “…in our
organization we count over 50,000 employees and if I compare that number with a
limited number of people working in innovation labs, it is clear that the focus should
shift to the entire organization.”.</p>
        <p>There was an overall consensus that this new way of approaching the Shadow IT
clearly opens the doors to innovation from unexpected angles. In other words, any
department, any employee may have hidden talents that can turn to be very
innovative. One example came from (A2): “we just had an employee from the financial
department who had some very advanced IT programming skills…he came with a small
application that automated a process where 6 people were previously involved to
have it done….it saves us huge amount of time but also money…he was using
unauthorized programs to build the App…but nobody really questioned that part”.
4.3</p>
      </sec>
      <sec id="sec-4-3">
        <title>Focus group</title>
        <p>Overall, participants noted that the time for change has arrived and there is a need for
IT departments to adapt to the new realities brought by the latest technological
advances which can unleash and spark employee innovation. Clearly, Shadow IT should
be driven, explained and encouraged by CIOs.</p>
        <p>For (FG1) IT department is not innovating “IT dept. today is still on run mode with
lost resources just maintaining. NOT innovating” and one possible reason for this non
innovation driven direction is because there is a breakdown in the communication
flow between different partners – e.g. (FG20): “Shadow IT is clearly an indication of
the breakdown in communication or trust w/IT”. For (FG12) it is time so shed light
on what Shadow IT is and what it can bring “I argue CIOs should not prohibit
shadow IT but rather shed a light on it”. Another tweet from (FG32) pointed out the need
to embrace and not to block the Shadow users.</p>
        <p>Overall, there was a general consensus about the benefits of encouraging Shadow
IT where majority of participants said that Shadow IT can spark the innovation which
in this new context would come not only from one single department or lab, but could
be generated and driven by a much larger group of people. One participant
commented (FG62) “SIT sparks innovation. And it is now available to anyone” and
another one (FG55) added “security could be an issue. But benefits could be simply very
high”.
5</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>Discussion</title>
      <p>
        Is Shadow IT an important source of innovation for firms? We tackled this research
question by using three different methods: 1) single case study; 2) interviews and 3)
focus group. By triangulating the findings from these three methods we can see that
Shadow IT can be an important source of innovation for firms. There is a clear link
between the Shadow Users (employees) and innovation process. While, these Shadow
Users are considered to be benign non-malicious insiders threating Information
Systems (IS) and violating IS security policies with benevolent intentions [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ], they can
also be important and new source of innovation. Indeed, so far, organizations were
typically mostly relying on their innovation departments or labs to produce
innovations. Interestingly, these user driven innovations benefit innovators (Shadow users)
themselves. Hence, users tend to develop fundamentally different innovations because
they will alone have benefits from using the innovation [
        <xref ref-type="bibr" rid="ref28">28</xref>
        ]. Typically, when Shadow
user, for instance, creates a new excel-macro the first user of this newly innovated
tool will be the Shadow user.
      </p>
      <p>Our research reveals that Shadow IT is an important driver of innovations within
an organization. From the single case study, where we analyzed a global firm which
openly adopted Shadow IT use, we could see that encouraging employees to propose
and suggest their innovative processes led to creating new benefits to the entire
organization. This was achieved through an active promotion of Shadow practices where
strong alignment between different stakeholders was created in order to have the
process secured from end to end. And benefits were manifold. Not only employee’s
creativity was unleashed but also IT benefited from this end user empowerment as IT
department in the newly created environment was much more consulter and became a
much stronger gatekeeper for all processes related to Shadow practices. Furthermore,
external customers had seen positive effects as tools or services they were using in
their organizations, with the new Shadow IT approach, are now marked as allowed.
This opened new and more efficient ways for communicating increasing productivity
and enabling fast job tasks execution.</p>
      <p>Interviews with IT executives were particularly useful as they revealed that
Shadow IT phenomenon is currently in a strong expansion with a plethora of new
products, services or tools. And it is not a question anymore how to prevent the Shadow
use but rather how to cooperate and free employees innovation. It is evident that
organizations in order to stay competitive or to keep their competitive advantage need to
innovate, and one possible direction is to rely on the entire population of employees.</p>
      <p>
        Focus group approach provided a bit higher level of the relationship and risks
behind Shadow IT. It is clear that for innovation to happen it has to be further
encouraged and this process should be top-down driven. IT department needs to be strongly
involved in this transformational process. On the other side, it was also pointed out
that Shadow IT is still relatively an unknown phenomenon despite the fact it is
nothing really new. And when something is unknown it tends to bring certain risks that are
actual risks. Mostly, it relates to how to efficiently handle security challenges behind
these “external” systems or processes use such as, for instance, cloud services [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ].
More than anything it is the question of trust. In cloud context the question is “who
would trust their essential data out there somewhere?” [
        <xref ref-type="bibr" rid="ref30">30</xref>
        ]. Same applies to Shadow
IT where risks related to such practices could also be very high and may diminish all
the positive effects behind the innovation idea.
      </p>
      <p>
        Overall, there should be a very strong alignment across the entire organization
before any Shadow IT practices are implemented. Past research showed that users
innovate as they expect benefits [
        <xref ref-type="bibr" rid="ref28">28</xref>
        ] or due to their expertise and knowledge [
        <xref ref-type="bibr" rid="ref31 ref32">31, 32</xref>
        ]. In
Shadow IT, users innovate as they have to fulfill their job needs by doing the job
faster and more efficient. To achieve that Shadow users mostly use greynet
(communication applications such as Skype), content apps (e.g. PDF tools) or various tools (e.g.
Facebook chat) to satisfy these job needs [
        <xref ref-type="bibr" rid="ref33">33</xref>
        ].
      </p>
      <p>Finally, how to approach Shadow IT user driven innovation process is already a
burning topic as it is not a question anymore whether organizations should promote,
encourage and implement the phenomenon, but rather, how to do it. As not only, if
done smartly, the already pending risks may be decreased, but above all,
organizations may spark innovation from unexpected places and people. Conclusion</p>
      <p>Our research investigated the Shadow IT being and important source of innovation
for firms. The study offers novel insights on the role of Shadow users in the
organizational innovation process and how they contribute to new innovations by using
Shadow IT. We provide several theoretical directions that could benefit from could build
upon our theoretical findings. Also, practitioners may benefit from the study as it
offers interesting insights on the role that Shadow IT may have when encouraged,
promoted and implemented in the entire organizational ecosystem where innovations
may come from unexpected places and people.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Baldwin</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hienerth</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Von Hippel</surname>
          </string-name>
          , E.:
          <article-title>How user innovations become commercial products: A theoretical investigation and case study</article-title>
          .
          <source>Research Policy</source>
          <volume>35</volume>
          ,
          <fpage>1291</fpage>
          -
          <lpage>1313</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Luthje</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Herstatt</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Von Hippel</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>The dominant role of" local" information in user innovation: The case of mountain biking</article-title>
          . (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Shah</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Sources and patterns of innovation in a consumer products field: innovations in sporting equipment</article-title>
          .
          <source>Sloan Working Paper</source>
          (
          <year>2000</year>
          ). (Accessed:
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Franke</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Shah</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>How communities support innovative activities: an exploration of assistance and sharing among end-users</article-title>
          .
          <source>Research Policy</source>
          <volume>32</volume>
          ,
          <fpage>157</fpage>
          -
          <lpage>178</lpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Lettl</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Herstatt</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gemuenden</surname>
            ,
            <given-names>H.G.</given-names>
          </string-name>
          :
          <article-title>Learning from users for radical innovation</article-title>
          .
          <source>International Journal of Technology Management</source>
          <volume>33</volume>
          ,
          <fpage>25</fpage>
          -
          <lpage>45</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Shah</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tripsas</surname>
            ,
            <given-names>M.:</given-names>
          </string-name>
          <article-title>The accidental entrepreneur: The emergent and collective process of user entrepreneurship</article-title>
          .
          <source>Strategic Entrepreneurship Journal</source>
          <volume>1</volume>
          ,
          <fpage>123</fpage>
          -
          <lpage>140</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Oliveira</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>von Hippel</surname>
          </string-name>
          , E.:
          <article-title>Users as service innovators: The case of banking services</article-title>
          .
          <source>Research Policy</source>
          <volume>40</volume>
          ,
          <fpage>806</fpage>
          -
          <lpage>818</lpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Jeppesen</surname>
            ,
            <given-names>L.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Molin</surname>
            ,
            <given-names>M.J.</given-names>
          </string-name>
          :
          <article-title>Consumers as co-developers: Learning and innovation outside the firm</article-title>
          .
          <source>Technology Analysis &amp; Strategic Management</source>
          <volume>15</volume>
          ,
          <fpage>363</fpage>
          -
          <lpage>383</lpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Haefliger</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jäger</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Von Krogh</surname>
          </string-name>
          , G.:
          <article-title>Under the radar: Industry entry by user entrepreneurs</article-title>
          .
          <source>Research Policy</source>
          <volume>39</volume>
          ,
          <fpage>1198</fpage>
          -
          <lpage>1213</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Strong</surname>
            ,
            <given-names>D.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Volkoff</surname>
            ,
            <given-names>O.:</given-names>
          </string-name>
          <article-title>A roadmap for enterprise system implementation</article-title>
          .
          <source>Computer</source>
          <volume>37</volume>
          ,
          <fpage>22</fpage>
          -
          <lpage>29</lpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Oliver</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Romm</surname>
          </string-name>
          , C.T.:
          <article-title>ERP systems in universities: rationale advanced for their adoption</article-title>
          . Idea Group Publishing, Hershey, PA (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Dubé</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Paré</surname>
          </string-name>
          , G.:
          <article-title>Rigor in information systems positivist case research: current practices, trends, and recommendations</article-title>
          .
          <source>MIS quarterly 597-636</source>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Rentrop</surname>
          </string-name>
          , C.,
          <string-name>
            <surname>van Laak</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mevius</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Schatten-IT: ein Thema für die interne Revision</article-title>
          .
          <source>Revisionspraxis-Journal für Revisoren</source>
          , Wirtschaftsprüfer, IT-Sicherheits-und
          <string-name>
            <surname>Datenschutzbeauftragte</surname>
          </string-name>
          68-
          <fpage>76</fpage>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Györy</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cleven</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Uebernickel</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Brenner</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Exploring the Shadows: IT Governance Approaches to User-Driven Innovation</article-title>
          . In: ECIS, pp.
          <fpage>222</fpage>
          . (
          <year>Year</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Warkentin</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Willison</surname>
          </string-name>
          , R.:
          <article-title>Behavioral and policy issues in information systems security: the insider threat</article-title>
          .
          <source>European Journal of Information Systems</source>
          <volume>18</volume>
          ,
          <fpage>101</fpage>
          -
          <lpage>105</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Puhakainen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Siponen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Improving employees' compliance through information systems security training: an action research study</article-title>
          .
          <source>Mis Quarterly</source>
          <volume>34</volume>
          ,
          <fpage>757</fpage>
          -
          <lpage>778</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Silic</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Dual-use open source security software in organizations - Dilemma: Help or hinder?</article-title>
          <source>Computers &amp; Security</source>
          <volume>39</volume>
          ,
          <string-name>
            <surname>Part</surname>
            <given-names>B</given-names>
          </string-name>
          ,
          <fpage>386</fpage>
          -
          <lpage>395</lpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Silic</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Back</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Information Security and Open Source Dual Use Security Software: Trust Paradox</article-title>
          .
          <source>Open Source Software: Quality Verification</source>
          , pp.
          <fpage>194</fpage>
          -
          <lpage>206</lpage>
          . Springer (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Silic</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Back</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>The Influence of Risk Factors in Decision-Making Process for Open Source Software Adoption</article-title>
          .
          <source>International Journal of Information Technology &amp; Decision Making 1-35</source>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Behrens</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sedera</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Why do shadow systems exist after an ERP implementation? Lessons from a case study</article-title>
          .
          <source>In: 8th Pacific Asia Conference on Information Systems</source>
          , Shanghai, China. (
          <year>Year</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Harley</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wright</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hall</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dery</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Management Reactions to Technological Change The Example of Enterprise Resource Planning</article-title>
          .
          <source>The Journal of Applied Behavioral Science</source>
          <volume>42</volume>
          ,
          <fpage>58</fpage>
          -
          <lpage>75</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Behrens</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Shadow systems: The good, the bad and the ugly</article-title>
          .
          <source>Communications of the ACM</source>
          <volume>52</volume>
          ,
          <fpage>124</fpage>
          -
          <lpage>129</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Henderson</surname>
            ,
            <given-names>J.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Venkatraman</surname>
          </string-name>
          , N.:
          <article-title>Strategic alignment: Leveraging information technology for transforming organizations</article-title>
          .
          <source>IBM Systems Journal</source>
          <volume>32</volume>
          ,
          <fpage>4</fpage>
          -
          <lpage>16</lpage>
          (
          <year>1993</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Luftman</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kempaiah</surname>
            ,
            <given-names>R.:</given-names>
          </string-name>
          <article-title>An Update on Business-IT Alignment:" A Line" Has Been Drawn</article-title>
          .
          <source>MIS Quarterly Executive</source>
          <volume>6</volume>
          , (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Myers</surname>
            ,
            <given-names>M.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Avison</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Qualitative research in information systems</article-title>
          .
          <source>Management Information Systems Quarterly</source>
          <volume>21</volume>
          ,
          <fpage>241</fpage>
          -
          <lpage>242</lpage>
          (
          <year>1997</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Hardman</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>An exploratory case study of computer use in a primary school mathematics classroom: new technology, new pedagogy?: research: information and communication technologies. Perspectives in Education: Recearch on ICTs and Education in South Africa: Special Issue 4 23</article-title>
          , p.
          <fpage>99</fpage>
          -
          <lpage>111</lpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Willison</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Warkentin</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Beyond deterrence: an expanded view of employee computer abuse</article-title>
          .
          <source>MIS quarterly 37</source>
          ,
          <fpage>1</fpage>
          -
          <lpage>20</lpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Von Hippel</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          :
          <article-title>The sources of innovation</article-title>
          . Springer (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <surname>Takabi</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Joshi</surname>
            ,
            <given-names>J.B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ahn</surname>
          </string-name>
          , G.-J.:
          <article-title>Security and Privacy Challenges in Cloud Computing Environments</article-title>
          .
          <source>IEEE Security &amp; Privacy</source>
          <volume>8</volume>
          ,
          <fpage>24</fpage>
          -
          <lpage>31</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <surname>Armbrust</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fox</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Griffith</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Joseph</surname>
            ,
            <given-names>A.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Katz</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Konwinski</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lee</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patterson</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rabkin</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stoica</surname>
            ,
            <given-names>I.:</given-names>
          </string-name>
          <article-title>A view of cloud computing</article-title>
          .
          <source>Communications of the ACM</source>
          <volume>53</volume>
          ,
          <fpage>50</fpage>
          -
          <lpage>58</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31.
          <string-name>
            <surname>Lüthje</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Herstatt</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>The Lead User method: an outline of empirical findings and issues for future research</article-title>
          .
          <source>R&amp;D Management</source>
          <year>34</year>
          ,
          <fpage>553</fpage>
          -
          <lpage>568</lpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          32.
          <string-name>
            <surname>Lüthje</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Herstatt</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Von Hippel</surname>
          </string-name>
          , E.:
          <article-title>User-innovators and “local” information: The case of mountain biking</article-title>
          .
          <source>Research Policy</source>
          <volume>34</volume>
          ,
          <fpage>951</fpage>
          -
          <lpage>965</lpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          33.
          <string-name>
            <surname>Silic</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Back</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Shadow IT-A view from behind the curtain</article-title>
          .
          <source>Computers &amp; Security</source>
          <volume>45</volume>
          ,
          <fpage>274</fpage>
          -
          <lpage>283</lpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>