<!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>
      <journal-title-group>
        <journal-title>M. Ishadi)</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Unveiling Dynamics Between Robotic Process Automation and Process Knowledge Loss</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mirispelakotuwa Ishadi</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Queensland University of Technology, School of Information Systems</institution>
          ,
          <addr-line>2 George Street, Brisbane</addr-line>
          ,
          <country country="AU">Australia</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0003</lpage>
      <abstract>
        <p>As organisations execute robotic process automation (RPA) enabled processes over time, a vital but less conspicuous challenge arises: process knowledge loss (PKL). PKL signifies the loss of essential process knowledge that employees need to perform tasks independently in the absence of automation. PKL brings significant negative organisational impacts, like hindering continuous process improvement, reducing productivity, and limiting the realisation of expected benefits. While scholars and industry practitioners hint at the symptoms of RPA-related PKL, studies do not specifically focus on investigating this phenomenon in depth. Thus, this PhD research seeks to explore the impact of the use of RPA technology within organisations on PKL. A qualitative case study methodology is used to interpret the phenomenon of RPA-related PKL through the experiences of process participants. Findings to date highlight that PKL is a contemporary phenomenon within the RPA context, identifying a set of factors and their interrelationships. The overall findings will contribute to developing a theoretical framework that explains the complex dynamics between RPA and PKL. The findings will also ofer practical guidance for organisations to devise strategies that address and mitigate PKL during RPA implementation.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Robotic Process Automation (RPA)</kwd>
        <kwd>Process Knowledge Loss</kwd>
        <kwd>Conceptual Model</kwd>
        <kwd>Work System Theory (WST)</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Robotic process automation (RPA) is gaining traction in the corporate sector as a task-level approach to
business process automation (BPA) that uses software bots [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. RPA is globally adopted by organisations
from telecommunication companies [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] to companies from the forestry sector [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. The global RPA
market projects growth of USD 64.47 billion by 2032 from USD 18.18 billion in 2024 [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        RPA stands out from other BPA technologies due to three distinct features: it is non-invasive, allowing
seamless integration with existing systems through user interfaces; it is user-friendly, requiring minimal
technical expertise to develop; and it can replicate human actions, making it particularly versatile [
        <xref ref-type="bibr" rid="ref1 ref2">2, 1</xref>
        ].
      </p>
      <p>
        Prior studies highlight several benefits of RPA, including cost reduction, improved employee
satisfaction, enhanced traceability of business processes, greater operational eficiency, and support for
business continuity [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ].
      </p>
      <p>
        Although RPA ofers substantial benefits, recent academic literature and practice commentaries have
drawn attention to various challenges associated with its use [
        <xref ref-type="bibr" rid="ref3 ref5">5, 3</xref>
        ]. One prominent concern is process
knowledge loss (PKL), which has been emphasised in both scholarly literature [
        <xref ref-type="bibr" rid="ref3 ref5 ref6 ref7 ref8 ref9">6, 3, 7, 8, 5, 9</xref>
        ] and by
RPA practitioners [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. This study examines the impact of RPA on PKL, a phenomenon that occurs
within process participants due to the loss of process knowledge [
        <xref ref-type="bibr" rid="ref10 ref3">3, 10</xref>
        ].
      </p>
      <p>
        Research emphasises that RPA-related PKL is a critical concern due to its significant threat to
organisational performance [
        <xref ref-type="bibr" rid="ref3 ref5 ref7">3, 7, 5</xref>
        ]. The decrease in employee productivity due to dificulties in
retaining end-to-end process knowledge is a significant consequence highlighted in the literature [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
Process execution delay is another consequence [
        <xref ref-type="bibr" rid="ref5 ref9">5, 9</xref>
        ]. Oshri and Plugge [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] identified that task visibility
issues result in employees losing their understanding of the automated tasks. Consequently, employees
struggle to troubleshoot errors and handle exceptions if a bot fails, due to insuficient process knowledge
[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Reversing the impacts by “introducing employees to the same process will cost the employer additional
working hours”, reducing the cost-efective benefits of RPA [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Given the criticality of organisational
consequences of RPA-related PKL, it demands both scholarly and practical attention.
      </p>
      <p>
        RPA-related PKL is an emerging topic in the literature. Scholars [
        <xref ref-type="bibr" rid="ref3 ref5 ref6 ref7 ref8 ref9">6, 3, 7, 8, 5, 9</xref>
        ] and industry
practitioners [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] have only hinted at the symptoms and impacts of PKL in the context of RPA. There
are several calls for research in this area. Vu et al. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] argued that knowledge loss is a significant cause
of increasing complexities in RPA maintenance. Therefore, it is suggested that a theory be developed to
explain the varying impacts of BPA technologies, such as RPA [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. Zelenka and Vokoun [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ] emphasised
the importance of researching the challenge of losing employees’ knowledge and skills after RPA is
implemented. Eulerich et al. [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] call for research on the negative impacts of using RPA, emphasising
PKL as a critical area that requires scholarly attention. Although there was no specific research on this
topic exploring RPA-related PKL, scholars have recognised the importance of studying this topic.
      </p>
      <sec id="sec-1-1">
        <title>1.1. Problem Statement and Research Questions</title>
        <p>As organisations implement RPA-enabled processes over time, a crucial yet less conspicuous challenge
emerges - PKL. PKL occurs when RPA software bots replace repetitive and rule-based tasks that have
been performed by process participants over a period of time. PKL impacts organisational performance
by undermining productivity, process adaptability, and long-term improvement eforts. Despite its
significant implications for the long-term efectiveness of automation eforts and several calls for
research in this area, research on RPA-related PKL is still at a nascent stage. There is a critical need
to investigate how PKL occurs in the RPA context and to identify strategies organisations can use to
mitigate its impact. Therefore, this study aims to address the following overarching research question
(RQ) and three sub-questions.</p>
        <p>RQ: How does the use of robotic process automation technology within organisations impact process
knowledge loss?</p>
        <p>
          RQ1: What are the factors impacting RPA-related PKL?
RQ2: What are the interrelationships between RPA-related PKL factors and PKL categories?
RQ3: How can organisations mitigate the risk of RPA-related PKL?
1.2. Contributions of the Study
• Theoretical contribution: A theoretical framework will be developed, extending the notion
of roles and facets of work in work system theory (WST) (refer to section 5.1 for more details
on WST), contextualizing these components to low-code automation technologies. As per [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ],
a type IV (explanation and prediction) theory will be developed to understand the underlying
causes and predict ’how’ PKL occurs when process participants and RPA bots play various roles
and perform various facets of work.
• Practical contribution: This study informs organisations that RPA-related PKL is a
contemporary phenomenon that compromises the intended benefits of RPA implementation. The overall
ifndings of this PhD research will help organisations to develop efective RPA governance policies
and mitigation strategies to prevent or overcome PKL.
        </p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>2. A Brief Summary of the Related Work</title>
      <p>
        Recent studies both in academia [
        <xref ref-type="bibr" rid="ref3 ref5 ref6 ref7 ref8 ref9">6, 3, 7, 8, 5, 9</xref>
        ] and industry [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] suggest that RPA-related PKL is a
contemporary phenomenon that surfaces with extended use of RPA. For example, Asatiani et al. [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]
argue that PKL surfaces when employees lose the logic behind executing a process once the tasks are
allocated among employees and bots for a period of time. A study by Oshri and Plugge [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] in the
banking sector indicates that a prolonged end-to-end implementation of RPA may lead to employees
losing their comprehensive understanding of the overall process.
      </p>
      <p>
        A few scholars ofer fragmented insights into the causes of RPA-related PKL. For instance, Marciniak
and Stanisławski [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] and Clair [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] link PKL to weak governance and documentation, while Oshri and
Plugge [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] and Asatiani et al. [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] emphasise that task division reduces employees’ understanding of
overall processes. Yet, no study has comprehensively examined these factors or the interrelationships.
Consequently, the existing studies do not provide a comprehensive understanding of how to mitigate
PKL and sustain the benefits of RPA. Furthermore, the existing literature does not ofer a detailed,
theory-driven explanation of PKL factors or their connections to diferent PKL categories.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Research Design</title>
      <p>
        This study takes an exploratory approach, as little is known about the phenomenon of RPA-related PKL.
As Eisenhardt [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ] elaborates, case studies are appropriate when little is known about a phenomenon to
build more powerful theories incrementally. Therefore, to interpret the phenomenon of RPA-related PKL
through the experience of people (i.e., process participants), the case study approach [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] in qualitative
research is chosen [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ].
      </p>
      <p>The overall research design includes three (3) sequential stages: stage 1 – problematisation, stage
2 – development of contextual understanding and conceptual model, and stage 3 – theorisation. The
research has now progressed to the completion of both stage 1 and stage 2.</p>
      <p>
        Stage 1: Problematisation: This study used the problematisation methodology of Alvesson and
Sandberg [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ] over a gap-spotting approach, challenging fundamental assumptions necessary for
generating innovative questions as presented in section 1.1.
      </p>
      <p>
        Stage one of the research design aligned with the six (6) principles of the problematisation
methodology, namely, 1) identify a domain of literature, 2) identify and articulate assumptions, 3) evaluate
assumptions, 4) develop alternative assumptions, 5) relate assumptions to the audience, and 6) evaluate
alternative assumptions [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. In line with the principles 1 and 2 [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], a preliminary literature review
was conducted, identifying key papers on RPA-related PKL. It was identified that there is a dearth
of literature specifically focusing on this phenomenon. To avoid the risk of a wasted efort, it was
decided to further explore and validate the literature findings using industry insights. Hence, seven (7)
exploratory interviews were conducted with RPA experts across several industries. Principles 3 to 6 [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]
were followed here. The findings of exploratory interviews confirmed the primary assumption that PKL
exists in the context of RPA. Then, alternative assumptions linking BPA and PKL were generated. This
process allowed us to develop a clear problem and research questions that can significantly contribute
to the existing knowledge on a contemporary phenomenon: RPA-related PKL.
      </p>
      <p>
        Stage 2: Development of contextual understanding and conceptual model: Stage 2 focused on
iteratively developing a conceptual model in two phases, answering RQ 1. First, a systematic literature
review (SLR) was conducted using the RPA, BPA, and general knowledge management literature on
knowledge loss, following the guidelines of Bandara et al. [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]. The SLR facilitated prior specification
of constructs/themes. This phase led to the development of an initial conceptual model that includes
ten (10) themes.
      </p>
      <p>
        A priori specification of constructs informs the initial design of the theory-building studies [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
Thus, following the guidelines of [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ], the case study and interview protocols were designed to align
with the themes in the initial conceptual model. An exploratory case study was conducted with a global
apparel manufacturing company [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ], allowing new insights to emerge that were not readily apparent
with other research methods [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. Then, the conceptual model was further refined as shown in Figure 1.
      </p>
      <p>
        Stage 3: Theorisation: The objective of this stage is to conduct multiple case studies following the
guidelines of Yin [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] for theorisation, answering RQ 2 and 3. Case studies are appropriate for theory
building under situations where there is a lack of empirical substantiation related to a phenomenon
[
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. Despite advocating the use of a single case study to describe unique, under-researched, and
extreme phenomena [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ], multiple case studies were chosen to allow comparisons [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. The research is
currently in the data collection phase for the second case study. The data analysis of the first case study
is currently in progress. In phase 2, it was revealed that PKL difers across various types of processes
and process participants. Hence, WST, particularly the roles of algorithmic agents, facets of work [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ],
and mode of engagement [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ] are selected to explain the findings of the multiple case studies.
      </p>
    </sec>
    <sec id="sec-4">
      <title>4. Findings to Date</title>
      <p>
        First, a clear definition of ’what is PKL’ was established to address the inconsistencies in the existing
explanations of PKL in the literature. Eulerich et al. [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] define PKL as the inability of employees to
perform tasks independently once bots take over, while Marciniak and Stanisławski [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] explain it as the
‘organisational amnesia’ resulting from full automation. However, these views focus narrowly on full
automation and overlook hybrid contexts where both bots and employees are involved. To address this
limitation, the first publication of this PhD ofered a more comprehensive definition; “the intentional or
unintentional loss of knowledge related to the processes" [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ]. The same study [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ] also discovered that
process knowledge is not entirely lost due to RPA, and various elements of it are still being preserved.
Hence, building on prior literature, the second publication of this PhD research [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ] further enhanced
the definition, incorporating three types of process knowledge: coordination knowledge (sequence
of activities), contextual knowledge (influences from other contingency factors), and experiential
knowledge (practical, hands-on experience). Earlier PKL definitions did not distinguish between these
types. Therefore, PKL was redefined as “the intentional or unintentional loss of coordination, contextual,
and experiential knowledge from extending RPA use in end-to-end and task-level automation" [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ].
      </p>
      <p>
        To address RQ1, an initial conceptual model was developed through SLR. Drawing from the overall
literature, ten (10) factors were discovered, namely, 1) employee turnover, 2) knowledge hiding, 3)
resistance to learning, 4) automation complacency, 5) top management support, 6) employee
redeployment, 7) IT outsourcing 8) RPA governance, 9) task division, and 10) level of process expertise. The
literature demonstrated that process knowledge is accumulated and retained by employees through the
hands-on execution of processes [
        <xref ref-type="bibr" rid="ref5 ref9">5, 9</xref>
        ] and learning [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. Thus, in many cases, PKL was characterised
as a phenomenon that occurs due to task division among employees and bots, as a result of reduced
employee involvement in automated processes [
        <xref ref-type="bibr" rid="ref5 ref6 ref7 ref9">6, 7, 5, 9</xref>
        ]. Figure 1 depicts the initial conceptual model.
      </p>
      <p>The initial conceptual model was enhanced via the findings of an exploratory case study. The enhanced
model incorporates additional factors (e.g., process architecture), new sub-factors (e.g., task control,
process segmentation), ten (10) relationships to PKL, and two (2) factor interrelationships as shown in
Figure 1. The previous model did not specify which process knowledge types were afected. To address
this, the enhanced model incorporates three key types of process knowledge: coordination, contextual,
and experiential. It builds on the PKL categories (i.e., intentional and unintentional), identifying
relationships between factors and PKL categories. Findings revealed that RPA-BPM integration is linked
to intentional PKL, whereas the remaining factors are associated with unintentional PKL.</p>
      <p>A further look into how RPA impacts PKL through the data analysis of the multiple case study 1
(stage 3 in progress) revealed that PKL varies based on the ’levels of automation’, and diferent roles
played by employees and RPA bots.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Work in Progress and Future Steps</title>
      <p>
        In stage 3 (theorisation), data collection is in progress for the second case study, and data analysis is
underway for the first case study. A cross-case analysis [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] will be conducted to allow comparison of
the findings of the two case studies. The following is an overview of the publication plan:
      </p>
      <sec id="sec-5-1">
        <title>5.1. Application of the Theory</title>
        <p>
          The WST [
          <xref ref-type="bibr" rid="ref20 ref21">20, 21</xref>
          ] will serve as the theoretical lens for explaining the findings.
        </p>
        <p>
          • Roles of the algorithmic agents: There are six roles defined by [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ] that are delegated to
information systems by work systems (WS). This study will use/ extend the roles defined by Alter [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]
contextualising in the RPA domain.
• Facets of work: There are 18 facets of work derived by Alter [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]. The facets of work will be
used/extended to identify and categorise various facets done by bots and process participants
when performing each of the six roles listed above.
• Mode of engagement: Findings to date of the first case study (stage 3) revealed that PKL varies
with the level of automation. Thus, the modes of engagement are aligned to reflect the level of
automation. Accordingly, how PKL occurs when bots and process participants play various roles,
conducting various facets of work at each mode of engagement, will be explained in this research.
        </p>
        <p>At the BPM doctoral consortium (DC), it is intended to discuss the conceptualisation of using WST in
this PhD research. Specifically, it is aimed to gather feedback on using WST (particularly the roles, facets
of work, and mode of engagement) as the theoretical lens to explain a phenomenon in the RPA context,
which is a form of BPA, including its weaknesses and challenges. The outcomes of this discussion will
inform my next publication and the theoretical underpinning of the entire research.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion</title>
      <p>This PhD study explores an emerging organisational challenge - PKL, which arises when bots take over
tasks previously conducted by employees. The case study approach in qualitative research is used to
explore the phenomenon. Findings to date highlight that PKL is a contemporary phenomenon within
the RPA context, developing an enhanced conceptual model. Future work will focus on theorisation
using multiple case studies. This PhD research will contribute to theory building in the RPA domain,
explaining the dynamics between RPA and PKL. The research will also provide practical guidance for
organisations to create strategies that address and mitigate PKL during RPA implementation.</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgments</title>
      <p>This PhD research is supervised by Dr. Rehan Syed and Prof. Moe T. Wynn at the Queensland University
of Technology (QUT) under the scholarship scheme of QUT Postgraduate Research Award (domestic).</p>
    </sec>
    <sec id="sec-8">
      <title>Declaration on Generative AI</title>
      <p>The author(s) have not employed any Generative AI tools.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>R.</given-names>
            <surname>Syed</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Suriadi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Adams</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Bandara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. J.</given-names>
            <surname>Leemans</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Ouyang</surname>
          </string-name>
          ,
          <string-name>
            <surname>A. H.</surname>
          </string-name>
          <article-title>ter</article-title>
          <string-name>
            <surname>Hofstede</surname>
            , I. van de Weerd, M. T. Wynn,
            <given-names>H. A.</given-names>
          </string-name>
          <string-name>
            <surname>Reijers</surname>
          </string-name>
          ,
          <article-title>Robotic process automation: contemporary themes and challenges</article-title>
          ,
          <source>Computers in Industry</source>
          <volume>115</volume>
          (
          <year>2020</year>
          )
          <fpage>103162</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M. C.</given-names>
            <surname>Lacity</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. P.</given-names>
            <surname>Willcocks</surname>
          </string-name>
          ,
          <article-title>Robotic process automation at telefonica o2</article-title>
          ,
          <source>MIS Q. Exec</source>
          <volume>15</volume>
          (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>P.</given-names>
            <surname>Marciniak</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Stanisławski</surname>
          </string-name>
          ,
          <article-title>Internal determinants in the field of rpa technology implementation on the example of selected companies in the context of industry 4.0 assumptions</article-title>
          ,
          <source>Information</source>
          <volume>12</volume>
          (
          <year>2021</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <article-title>[4] FortuneBusinessInsights, Robotic process automation (rpa) market</article-title>
          .,
          <year>2025</year>
          . URL: https://www. fortunebusinessinsights.
          <article-title>com/robotic-process-automation-rpa-market-102042.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>I.</given-names>
            <surname>Oshri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Plugge</surname>
          </string-name>
          ,
          <article-title>What do you see in your bot? lessons from kas bank</article-title>
          ,
          <source>in: Digital Technologies for Global Sourcing of Services. Global Sourcing</source>
          <year>2019</year>
          , volume
          <volume>410</volume>
          <source>of LNBIP</source>
          , Springer, Cham,
          <year>2020</year>
          , pp.
          <fpage>145</fpage>
          -
          <lpage>161</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>A.</given-names>
            <surname>Asatiani</surname>
          </string-name>
          , E. Penttinen,
          <string-name>
            <given-names>T.</given-names>
            <surname>Rinta-Kahila</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Salovaara</surname>
          </string-name>
          ,
          <article-title>Implementation of automation as distributed cognition in knowledge work organizations: Six recommendations for managers</article-title>
          ,
          <source>in: International Conference on Information Systems (ICIS)</source>
          , volume
          <volume>7</volume>
          ,
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>M.</given-names>
            <surname>Eulerich</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Waddoups</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Wagener</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. A.</given-names>
            <surname>Wood</surname>
          </string-name>
          ,
          <article-title>The dark side of robotic process automation (rpa): Understanding risks and challenges with rpa</article-title>
          ,
          <source>Accounting Horizons</source>
          <volume>38</volume>
          (
          <year>2024</year>
          )
          <fpage>143</fpage>
          -
          <lpage>152</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>M.</given-names>
            <surname>Zelenka</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Vokoun</surname>
          </string-name>
          ,
          <article-title>Information and communication technology capabilities and business performance: The case of diferences in the czech financial sector and lessons from robotic process automation between 2015 and 2020, Review of Innovation and Competitiveness:</article-title>
          <source>A Journal of Economic and Social Research</source>
          <volume>7</volume>
          (
          <year>2021</year>
          )
          <fpage>99</fpage>
          -
          <lpage>116</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>A.</given-names>
            <surname>Asatiani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Penttinen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Ruissalo</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Salovaara</surname>
          </string-name>
          ,
          <article-title>Knowledge workers' reactions to a planned introduction of robotic process automation-empirical evidence from an accounting firm</article-title>
          ,
          <source>in: Information Systems Outsourcing</source>
          , Springer, Cham,
          <year>2020</year>
          , pp.
          <fpage>413</fpage>
          -
          <lpage>452</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>C. L.</given-names>
            <surname>Clair</surname>
          </string-name>
          , The Forrester Wave™: Robotic Process Automation,
          <year>Q2 2018</year>
          :
          <article-title>The 15 Providers That Matter Most And How They Stack Up</article-title>
          ,
          <source>Technical Report, Forrester</source>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>H.</given-names>
            <surname>Vu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Haase</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Leopold</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mendling</surname>
          </string-name>
          ,
          <article-title>Towards a theory on process automation efects</article-title>
          ,
          <source>in: International Conference on Business Process Management</source>
          , Springer, Cham,
          <year>2023</year>
          , pp.
          <fpage>285</fpage>
          -
          <lpage>301</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>S.</given-names>
            <surname>Gregor</surname>
          </string-name>
          ,
          <article-title>The nature of theory in information systems</article-title>
          , MIS quarterly (
          <year>2006</year>
          )
          <fpage>611</fpage>
          -
          <lpage>642</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>K. M. Eisenhardt</surname>
          </string-name>
          ,
          <source>Building theories from case study research</source>
          ,
          <source>Academy of management review 14</source>
          (
          <year>1989</year>
          )
          <fpage>532</fpage>
          -
          <lpage>550</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>R. K.</given-names>
            <surname>Yin</surname>
          </string-name>
          ,
          <source>Case Study Research Design and Methods</source>
          , volume
          <volume>5</volume>
          , SAGE,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>U.</given-names>
            <surname>Flick</surname>
          </string-name>
          ,
          <article-title>An introduction to qualitative research</article-title>
          ,
          <source>Sage Publications</source>
          ,
          <year>2023</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>M.</given-names>
            <surname>Alvesson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Sandberg</surname>
          </string-name>
          , Generating research questions through problematization,
          <source>Academy of management review 36</source>
          (
          <year>2011</year>
          )
          <fpage>247</fpage>
          -
          <lpage>271</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>W.</given-names>
            <surname>Bandara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Furtmueller</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Gorbacheva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Miskon</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Beekhuyzen</surname>
          </string-name>
          ,
          <article-title>Achieving rigor in literature reviews: Insights from qualitative data analysis and tool-support</article-title>
          ,
          <source>Communications of the Association for Information systems 37</source>
          (
          <year>2015</year>
          )
          <article-title>8</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <surname>I. Mirispelakotuwa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Syed</surname>
          </string-name>
          , M. T. Wynn,
          <article-title>Is rpa-related process knowledge loss real?</article-title>
          ,
          <source>in: Proceedings of the 32nd European Conference on Information Systems (ECIS)</source>
          ,
          <source>AIS</source>
          ,
          <year>2024</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>I.</given-names>
            <surname>Benbasat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. K.</given-names>
            <surname>Goldstein</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Mead</surname>
          </string-name>
          ,
          <article-title>The case research strategy in studies of information systems</article-title>
          , MIS quarterly (
          <year>1987</year>
          )
          <fpage>369</fpage>
          -
          <lpage>386</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>S.</given-names>
            <surname>Alter</surname>
          </string-name>
          ,
          <article-title>Re-conceptualizing information system usage as usage by (increasingly automated) work systems</article-title>
          ,
          <source>Communications of the Association for Information Systems</source>
          <volume>54</volume>
          (
          <year>2024</year>
          )
          <fpage>1094</fpage>
          -
          <lpage>1123</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>S.</given-names>
            <surname>Alter</surname>
          </string-name>
          ,
          <article-title>Making cyber-human systems smarter</article-title>
          ,
          <source>Information Systems</source>
          <volume>127</volume>
          (
          <year>2025</year>
          )
          <fpage>102428</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <surname>I. Mirispelakotuwa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Syed</surname>
          </string-name>
          , M. T. Wynn,
          <article-title>Is rpa causing process knowledge loss? insights from rpa experts</article-title>
          ,
          <source>in: BPM 2023: Business Process Management: Blockchain and Robotic Process Automation Forum</source>
          , Springer, Cham,
          <year>2023</year>
          , pp.
          <fpage>73</fpage>
          -
          <lpage>88</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>R.</given-names>
            <surname>Seethamraju</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Marjanovic</surname>
          </string-name>
          ,
          <article-title>Role of process knowledge in business process improvement methodology: a case study</article-title>
          ,
          <source>Business Process Management Journal</source>
          <volume>15</volume>
          (
          <year>2009</year>
          )
          <fpage>920</fpage>
          -
          <lpage>936</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>