How affordances of chatbots cross the chasm between social and traditional enterprise systems

Digital and agile companies widely use chatbots in the form of integrations into enterprise messengers such as Slack and Microsoft Teams. However, there is a lack of empirical evidence about their action possibilities (i.e., affordances), for example, to link social interactions with third-party systems and processes. Therefore, we adopt a three-stage process. Grounded in a preliminary study and a qualitative study with 29 interviews from 17 organizations, we inductively derive rich contextual insights of 14 affordances and constraints, which serve as input for a Q-Methodology study that highlights five perceptional differences. We find that actualizing these affordances leads to higher-level affordances of chatbots that augment social information systems with affordances of traditional enterprise systems. Crossing the chasm between these, so far, detached systems contributes a novel perspective on how to balance novel digital with traditional systems, flexibility and malleability with stability and control, exploration with exploitation, and agility with discipline.


Introduction
Over the last couple of years, chatbots have gained traction to improve productivity and efficiency among employees in the light of an increasing number of organizations, who adopt enterprise messengers such as Slack and Microsoft Teams (Hubbard and Bailey 2018;Riemer et al. 2018;Schatsky and Gratzke 2016;Tsai 2018;vom Brocke et al. 2018).Accordingly, the worldwide chatbot market size is forecasted to increase to 1.25 billion U.S. dollars until 2025 (Grand View Research 2017).In fact, Gartner predicts that "the average person will have more conversations with bots than with their spouse" by 2020 (Levy 2016).
This rise of chatbots within enterprise messengers needs to be seen in the light of the broader wave of digitalization.Specifically, a key tenant of digitalization is distributed innovation, which is characterized by balancing flexibility and openness with stability and control (Ciriello et al. 2018a;Tilson et al. 2010;Yoo et al. 2012).Further, the growing number of application programming interfaces (APIs) enable standardized digital communication and exchange between different information systems (Eaton et al. 2015;Ghazawneh and Henfridsson 2013).In the context of instant messengers (i.e.social information systems), this has led to numerous frameworks and API's that facilitate the development and installation of chatbots in both, the enterprise context (e.g., Slack apps and integrations, HipChat bots, and Microsoft bot framework for Skype/Microsoft Teams) and the consumer context (e.g., Facebook Messenger and Telegram Bot Platform).
The success of these enterprise messengers can be attributed, on the one hand, to their malleability and voluntariness as opposed to traditional enterprise systems which are designed to support dedicated business processes and work tasks (Koch 2008;Richter and Riemer 2013;Schmitz et al. 2016).On the other hand, a key factor for realizing organizational benefits is their integrability (Seddon et al. 2010).Taking advantage of the user-centered focus while at the same time increasing the productivity and efficiency of internal workflows are promising potentials that arise from integrating these social information systems into the enterprise landscape (Hubbard and Bailey 2018;Schatsky and Gratzke 2016).
For the sake of clarity, we now illustrate a chatbot use scenario in the context of a software developing organization (Lebeuf et al. 2018;Vehviläinen 2014).Imagine a company that integrates their software deployment workflows into their enterprise messenger.Bob, a software engineer, deploys software using an isolated command-line tool on his laptop.In contrast, imagine the same scenario, but with Bob initiating the deployment within the enterprise messenger by engaging in a textual conversation with a chatbot in a conversational group thread (accessible by other software engineers).Thus, chatbots extend the functional scope of enterprise messengers and offer new potentials.For example, by shifting from a siloed terminal into a conversational group thread, the workflow described above becomes transparent to team members.
Against this background, prior research pays little attention to two major areas.First, prior research lacks to investigate entanglements of social and traditional enterprise systems (Sedera and Lokuge 2017;Sedera et al. 2016).Yet, today's organizational IT landscape is transforming from single and monolithic enterprise systems into portfolios of information systems (Sedera et al. 2016).Given the above noted increasing possibilities to interlink different information systems and the growing relevance of distributed innovation, organizations need to explore ways to combine novel digital technologies such as social information systems with their traditional enterprise systems (Sedera and Lokuge 2017;Sedera et al. 2016).However, instead of investigating entanglements of social and traditional enterprise systems, existing information systems (IS) research largely emphasizes the contrasts between traditional enterprise systems and social information systems (Koch 2008;Mettler and Winter 2016).For instance, the latter are more user-centric than group-oriented, take in a bottom-up perspective of voluntary participation instead of top-down enforcements, enable co-evolvement of conventions and are available across projects and organizational silos rather than determining ways of working together (Koch 2008).Moreover, prior research illustrates how traditional enterprise systems enable alignment, control, interoperability, efficiency (Mettler and Winter 2016), while social information systems foster visibility, persistence, editability, and association (Treem and Leonardi 2012).In consequence, the interrelationship and the entanglement of traditional enterprise systems and social information systems remains, until now, unclear due to their complex dynamics (Limaj et al. 2016).Accordingly, research is needed to address this lack and to elaborate on how the existing chasm of traditional information systems and social information systems can be bridged.
Second, the existing body of literature on chatbots has a strong focus on the fields of education, psychology, and linguistics and lacks in academic research on chatbots in business (Io and Lee 2017).In particular, there is little empirical research that explores the usage of chatbots within enterprises and the possibilities of chatbots to extend the functionality of the existing IT landscape even though the relevance of enterprise messengers is increasing (Lebeuf et al. 2018;Tsai 2018).Accordingly, we apply affordance theory to take into account the material properties of our technological artifacts (i.e., chatbots within enterprise messengers such as Slack and Microsoft Teams) as well as their recursive effects on social mechanisms in an organizational context (Faraj and Azad 2012;Orlikowski and Scott 2008).To date, it remains unclear which action possibilities (i.e., affordances) chatbots offer within organizations and how they provide value.Consequently, we pose the following research question: RQ: Which affordances emerge for employees from the material properties of chatbots used within enterprises?
The goal of this research is to gain an in-depth understanding of what chatbots enable their employees to do by investigating how chatbots are actually used for everyday work in different organizational contexts.Consequently, we seek to explore novel possibilities for goal-oriented action that emerge for employees, i.e., affordances (Markus and Silver 2008).
While we take into consideration multiple enterprise messengers, Slack offers a particularly appropriate spawn and focal point for this research, because of their fast-growing ecosystem of Slack apps and integrations (Lebeuf et al. 2018;Tsai 2018).For example, they have attracted four million daily active users with a user growth of up to three and a half over the course of 2016 (The Economist 2016).Thereof, over one million users in thirty-three thousand teams operate on paid accounts (The Economist 2016) and around 90% of these paid teams actively use chatbots in the form of Slack apps and integrations (Slack Platform Blog 2016).Moreover, due to the fact that Slack apps and integrations are actively used since 2015, work practices of employees may be more established and stable compared to the more recent rise of Microsoft Teams in 2018 driven by the free availability in combination with Office 365 (Tsai 2018).
The remainder of this article is structured as follows: First, we introduce the theory of affordances as theoretical underpinning.Then, we put the technology under investigation (i.e., chatbots within enterprise messengers) into the broader context of the literature on social information systems.This allows us to discuss the results in a more general theoretical context, while still acknowledging the technological materiality of chatbots and the underlying enterprise messengers.Second, the research methodology is detailed along our three research phases.Third, the results are presented along the four identified categories of affordances.Fourth, we elaborate how chatbots augment social information systems with affordances of traditional enterprise systems and we discuss our results in the light of the affordance theory, before we end with a conclusion.

Theoretical background
Information technology (IT) artifacts are "man-made cultural objects that have enduring objectified quality through its physical materiality and institutionalized practices" (Yoo 2012, p. 136).In contrast to the relatively stable structures of physical artifacts (e.g., car), the structure of digital artifacts such as enterprise messengers is pliable, extensible, re-combinable and changes dynamically over time (Faulkner and Runde 2010;Yoo 2012).In particular, chatbots are not only designed and created by humans, but at the same time, can be dynamically put into different social contexts by humans (e.g., in different project related shared conversational threads within an enterprise messenger).It is for this reason, why a sociomateriality perspective is especially valuable and acknowledges that "(1) all materiality is social in that is was created through social processes and it is interpreted and used in social contexts and (2) that all social action is possible because of some materiality" (Leonardi 2012, p. 10).Applied to the context of this research, employees may shape chatbots and, in turn, chatbots may shape employees depending on the goals and capabilities of employees (e.g., programming skills).Furthermore, sociomateriality has to be seen in the context of a global world of technological and organizational networks in which corresponding structures (both technical and social) are increasingly interdependent (Orlikowski and Barley 2001;Orlikowski and Iacono 2001).Accordingly, we aim at "simultaneously understanding the role of human agency as embedded in institutional contexts as well as the constraints and affordances of technologies as material systems" (Orlikowski and Barley 2001, p. 158).To do so, and anchored in the objective to explore what chatbots afford employees to do, we ground this research in the theory of affordances (Gibson 1977).

Theory of affordances
Having its origins in the field of ecological psychology, it is guided by the logic that animals perceive what possibilities objects in their environment offer to them (Gibson 1977).This theoretical lens suits particularly well to pursue our explorative research for two reasons.First, taking up an affordance perspective guides us to mutually investigate: (1) the causal potentials of chatbots in the form of Slack apps and integrations, and (2) the goals, motivations, characteristics and capabilities of the considered employees in their contexts.Second, the relational nature of affordances is fruitful for shedding light on the conditions under which affordance emergence, perception and actualization takes place for different user groups.In doing so, the distinction between IT artifacts and actors (e.g., users) follows the call to bring back the IT artifact and its material properties to information systems (IS) research (Benbasat and Zmud 2003;Orlikowski and Iacono 2001).
As widely adopted in IS research (Markus and Silver 2008;Pozzi et al. 2014;Savoli and Barki 2013), we conceptualize affordances as "possibilities for goal-oriented action afforded to specified user groups by technical objects" (Markus and Silver 2008, p. 622).Hence, the concept of affordances is relational as visualized in Fig. 1 and considers both (1) a user with its abilities and goals as well as (2) the material properties (e.g., features) of the IT artifact (Bernhard et al. 2013;Strong et al. 2014).
Affordances are real, that is, they exist independently of the user's perception (Gibson 1977).Figure 1 illustrates the conceptual distinction between the emergence of action potentials (i.e., the existence of an affordance for a specified user), their recognition (i.e., the perception by the user) and their realization (i.e., the actualization by the user that may lead to certain effects) (Bernhard et al. 2013;Glowalla et al. 2014;Pozzi et al. 2014).Thereby, the existing possibilities for action that an IT artefact offers to specific users are neither infinite, nor always enabling (Strong et al. 2014).In fact, the offered possibilities may also be constraining to particular users depending on their abilities and goals (Strong et al. 2014).
Affordance perception is influenced by many factors (e.g., available information) and includes the perception of nonexistent affordances (Bernhard et al. 2013).Accordingly, the material properties of an IT artifact and the respective material agency, i.e., "ways in which a technology's materiality acts" (Leonardi 2012, p. 22) and the relation to an actor trying to engage with the IT artifact may result in the perception of affordances.Perceived affordances might be actualized, depending on a user's agency, and influenced by factors such as the expected outcome or the perceived efforts to take (Bernhard et al. 2013).
Both, IT artifacts as well as actors can be considered on various levels of granularity, thus, leading to the emergence of affordances at various levels (Bygstad et al. 2016).Extant literature on affordance theory in IS research acknowledges these different levels of granularity by introducing distinct affordance concepts.Strong et al. (2014) elaborate on individual and organizational level affordances.At any given moment, an individual that engages with technology "is part of various organizational structures, from local work groups engaged in collective tasks, to the far-flung multi-level hierarchy that is the modern organization" (Volkoff and Strong 2017, p. 4).Accordingly, for a given user, multiple affordances may emerge from a given IT artefact.Further, the actualization of these emerging affordances is influenced by the socio-technical context in which individual users are situated (Stoeckli et al. 2019) and, from an organizational perspective, the actualization might require adaptations of the socio-technical work system (Dremel et al. 2018).Furthermore, Leonardi (2013) distinguishes between individualized, collective and shared affordances.In contrast to individualized affordances, collective affordances are "collectively created by members of a group, in the aggregate, which allows the group to do something that it could not otherwise accomplish" (Leonardi 2013, p. 752).Shared affordances are shared within a group in the way that it represents similar use of a technology (Leonardi 2013).Finally, Savoli and Barki (2013) acknowledge that IT artifacts can be seen as assemblage of individual parts, hence, leading to feature-level and system-level affordances.Among these affordances on different levels of granularity, dependencies and interactions may occur, e.g., the potential of analyzing data requires having realized the potential of collecting data (Bygstad et al. 2016;Glowalla et al. 2014;Strong et al. 2014).Such dependencies and interactions allow this research to abstract affordances from a concrete to a higher and more generalized level (Bygstad et al. 2016).

Social information systems
From a technical materiality perspective, the research at hand investigates chatbots embedded in enterprise messengers such as Slack and Microsoft Teams.However, following the theoretical lens of affordances guides to give "equal play to the material as well as the social" (Faraj and Azad 2012, p. 238).Consequently, this research has to be seen in a broader context of literature, since the considered social technologies and their surrounding organizational social structures constitute social information systems (Schlagwein and Hu 2016;Schlagwein et al. 2011).Specifically, social information systems are information systems (IS) that amplify the social capabilities of actors by creating interaction possibilities to form communities and exchange information based on open collaboration (Kaplan and Haenlein 2010;Kim et al. 2010;Schlagwein and Hu 2016;Schlagwein et al. 2011;Shirky 2003;von Krogh 2012).
Prior research has shown that social information systems follow the principles of egalitarianism, social production and weak ties (Schmidt and Nurcan 2009), which we now illustrate in the light of the enterprise messenger Slack.
The principle of egalitarianism is understood as providing "equal rights to all members of a society and [is] tightly connected to democratic principles" (Schmidt and Nurcan 2009, p. 202).In the context of this research, egalitarianism is manifested by allowing each user to create and join channels as well as contribute to and consume content.Within Slack, chat rooms called channels visualized as a conversational thread of messages, including textual messages, images and files (see Fig. 2).The channel can be set as open for users to join, or privately shared per invitation only.As such, the creation of channels and content is a result of social production by the users of a corresponding Slack team.
The principle of social production emphasizes that the production of information and knowledge is organized collaboratively based on free flow rather than process-driven and topdown enforced ways of working together (Benkler 2006;Schmidt and Nurcan 2009;Tapscott and Williams 2008).Due to malleability (Richter and Riemer 2013;Schmitz et al. 2016), channels can be harnessed for various purposes (e.g., to organize conversations on specific topics of interest, technologies, projects and dedicated team channels).In turn, the visibility of open channels enables the creation of weak ties.
The principle of weak ties acknowledges the characteristic of social information systems to facilitate the spontaneous creation of links (i.e., ties) between non-predetermined individuals (Granovetter 1973;Schmidt and Nurcan 2009).Furthermore, users can react to any kind of message that is posted with smileys (emojis), add answers directly in the main thread or create replies in a corresponding sub-thread.They can send direct messages to one or multiple people and can engage in video calls.Further emphasis is put on the search functionality offered across any type of message and the drag and drop of files (Slack 2017b).
Fig. 1 Affordance concepts (Bernhard et al. 2013;Pozzi et al. 2014) Looking through a sociomaterial lens guided by the theory of affordance, we argue that contemporary enterprise messengers such as Slack and Microsoft Teams differ from previous forms of enterprise messengers in regard to the technical as well social structures.They offer powerful application programming interfaces (API) that allow developers to build conversational driven apps and integrations into these channels, that is, what we refer to as chatbots (see subsequent section on Chatbots).More specifically, by registering bot identities, developers can post messages into channels as chatbots.They can register commands to call third-party systems and establish bidirectional connections to send and receive messages of channels.The base functionality such as reacting with emojis is also applicable to messages posted by chatbots.In addition to textual messages, more and more visual elements are provided for chatbots, e.g., buttons (see Fig. 3) and menus with selectable options.Finally, today's enterprise messengers allow to share apps and integrations in their publicly available marketplaces, e.g., Slack's App Directory (Slack 2016a) and Microsoft's AppSource (Microsoft 2018).This has led to a growing ecosystem in terms of the number of users and the number of apps and integrations.For example, Slack's App Directory listed 150 apps in December 2015 and over 385 apps in April 2016 (Slack 2016b).With this ecosystem, contemporary enterprise messengers differ from previous enterprise messengers by offering chatbots to a broader audience of users, which may add apps and integrations from the public directory to their channels (i.e., putting chatbots into their working environment).

Chatbots
At the very core, bots can be understood as automated programs which "do not require a human operator", while chatbots in particular are automated programs that interact with chat services (Gianvecchio et al. 2011(Gianvecchio et al. , p. 1558)).Consequently, the focus lies on nonhuman actors that engage in conversations with human actors, whereas an actor is "any entity that acts" (Seymour et al. 2018, p. 956).In turn, a "fully computer-based entity that exhibits, at least to some degree, autonomous behavior" is widely known as an agent (Seymour et al. 2018, p. 955).
Accordingly, several authors adopt the concept of conversational agents (Gnewuch et al. 2017;Nunamaker et al. 2011;Schuetzler et al. 2014) and investigate, for instance, the use of conversational agents in the finance industry in the form of robo-advisory (Jung et al. 2018a;Jung et al. 2017;Jung et al. 2018b).Against this backdrop, a chatbot can be seen as a type of conversational agent that is text-based (Gnewuch et al. 2017).This conceptual distinction is relevant, because conversational agents are not limited to text, but include voice-driven systems such as Apple Siri, Microsoft Cortana, Amazon Alexa and Google Assistant (Dale 2016).Commonly, such conversational agents provide assistance to users ranging from basic user assistance to anticipating user assistance with varying degrees of interaction and intelligence (Maedche et al. 2016).Similarly, prior research distinguishes simple agents (i.e., agents that solely act according to pre-scripted behavior) from cognitive agents with sophisticated capabilities to understand the natural language from human actors and to respond accordingly (Seymour et al. 2018).
Furthermore, agents differ in their degree of realistic visual presence.Specifically, human actors may be visually (re-)presented at varying degrees of realism through avatars, while nonhuman actors may be visually presented as visual cognitive agents, i.e., "an interactive, real-time rendered human-like entity, on a screen or in a virtual environment" (Seymour et al. 2018, p. 956).Consequently, visual cognitive agents as well as avatar-represented human actors increasingly become visually believable artificial humans with high degree of presence, thus, create realistic visual presence (Seymour et al. 2018).Similarly, social presence describes the degree to which an actor is perceived as a real and present (Short et al. 1976).Prior research even suggests that humans perceive nonhuman actors with sufficient social cues as social actors; a paradigm referred to as computers-are-social-actors (Nass and Moon 2000;Nass et al. 1995Nass et al. , 1994)).In fact, team performance of human robot teamwork increases with a higher emotional attachment of humans to their robots (Robert 2018;You and Robert 2018).In this regard, studies also show various effects of avatars on the human perception of conversational agents.For example, facial expressions affect the perceived credibility (Cowell and Stanney 2005) and likability of avatars (Nunamaker et al. 2011).When using conversational agents for e-commerce, literature shows that avatars of sales agents not only influence satisfaction with retailers, but also the positive attitude towards products as well as greater purchase intentions (Holzwarth et al. 2006).
With the advent of automation, work is increasingly shaped by the interplay of humans and machines (Lehrer et al. 2018;vom Brocke et al. 2018).At the same time, conversational agents may not only be designed to assist humans, but with the goal to change human attitudes and behavior (Fogg 2002;Mirsch et al. 2017;Oinas-Kukkonen and Harjumaa 2009;Weinmann et al. 2016).Against this backdrop, machines increasingly take in dominant roles, which is why scholars argue that human agency may be reduced so that it becomes, in an extreme view, subordinate to automated executions: "it is humans that must react to technological stimuli rather than technology that must react to human stimuli" (Demetis and Lee 2018, p. 930).In this rather extreme perspective, humans are considered "artifacts shaped and used by the (system of) technology rather than vice versa" (Demetis and Lee 2018, p. 929).Consequently, aside from the varying degrees of (1) interaction, (2) intelligence and (3) realistic visual presence, conversational agents may differ in their dominance and persuasion, which influences (4) the degree of human agency.
To sum up, agents that engage in and assist in conversations with humans are not a novel phenomenon, per se.It is already fifty years ago, since the well-known program ELIZA replied to human input based on keyword recognition (Weizenbaum 1966).Aside from the introduced concepts, a plethora of related concepts have emerged over time, e.g., conversational interface (Knight 2016), chat agent (Crutzen et al. 2011), chatterbot (Mauldin 1994), and dialogue system (Litman and Pan 2002).However, "whether you call these things digital assistants, conversational interfaces or just chatbots, the basic concept is the same: achieve some result by conversing with a machine in a dialogic fashion, using natural language" (Dale 2016, p. 811).Nevertheless, over the years, the background of research on chatbots has changed in three major areas: First, the technologies to build chatbots have progressed.In particular, the capabilities of information technology, precisely artificial intelligence and machine learning, have advanced.Natural language processing capabilities can now be used to extract meaning from textual input and to form reasonable responses.Thus, social interactions between humans and machines are no longer limited to chatbots operating on fixed rule-based pattern matching and simple decision trees (Schuetzler et al. 2014).Chatbots become artificially intelligent agents (Crutzen et al. 2011).
Second, the social information systems in which chatbots are embedded have changed.Originally, text-driven instant messengers provided mainly desktop computer users with virtual spaces (i.e., chat rooms or channels), e.g., based on IRC, XMPP/ Jabber, MSN and AOL (Gianvecchio et al. 2011).In the meanwhile, contemporary technologies on mobile devices are increasingly pervasive and integrated into the everyday life at home and at work (Lyytinen and Yoo 2002;Yoo 2010).
Third, the use of chatbots has evolved against the backdrop of the changing technologies to build chatbots as well as the changing technologies in which chatbots are integrated.In the 1950's, the well-known Turing test has initiated the use of chatbots in experimental settings, in which an examiner decides if a subject in a conversation is a human or a machine (Turing 1950).Accordingly, a vast body of research is concerned with passing the yet not solved imitation game (Floridi et al. 2009).Since the rising adoption of messengers in the everyday life of people, research is not limited anymore to experimental settings.In fact, WhatsApp and Facebook Messenger are the most popular mobile messaging apps worldwide with more than 1300 millions monthly active users (Statista 2018).Accordingly, research reveals chatbots in various settings, e.g., customer support (Lasek and Jessa 2013), health (Crutzen et al. 2011), education (Kerly et al. 2007) and psychology (Pilato et al. 2005).In the enterprise context, prior research on chatbots has mostly focused on cost reductions and computer-based support for decision making (Watson 2017).
Against this backdrop, the research at hand differs from prior research in the following two ways.First, the focus of this research is on investigating chatbots within enterprises.In contrast, academic research on chatbots primarily focuses on the fields of education, psychology, and linguistics, while there is a lack of research on chatbots in business (Io and Lee 2017).As such, we empirically investigate the use of chatbots in practice in contrast to prior research that aims at designing and evaluating chatbots (André 2008;Gnewuch et al. 2017;Kerly et al. 2007;Kim et al. 2007;Serban et al. 2017).
Second, much research strives to optimize the human-like behavior (Floridi et al. 2009;Turing 1950), e.g., increasing the perceived humanness and engagement of conversational agents through adaptive responses (Schuetzler et al. 2014) and advancing the knowledge on human-like chatbot conversations (Crutzen et al. 2011).In practice, many of today's real world examples highlight the relevance of chatbots that are far away from being intelligent and offer simple linear flows (Budiu 2018).Even though humanness of chatbots may influence its effects, emerging enterprise messengers such as Slack, Microsoft Teams, and HipChat indicate that chatbots are by no means limited to, but do include, chatbots that strive to act as human-like as possible (Slack 2016a).Consider the illustrative case from the introduction section, where a chatbot initiates the deployment workflow triggered by commands within a textual conversation.This means that the intention behind chatbots may, but do not necessarily need to lie in increasing the humanness of their conversations.In addition, it has to be acknowledged that "there are three main approaches for conversations: unilateral, bilateral, or multilateral.Unilateral conversation is used for messages, which do not require responses" (Krempels et al. 2006, p. 395).
In summary, we draw on prior research (Dale 2016;Gnewuch et al. 2017;Krempels et al. 2006;Seymour et al. 2018) to conceptualize chatbots as nonhuman actors that act as conversational agents by engaging in unilateral, bilateral or multilateral text-based conversations with human actors.

Research methodology
Our research adopts an explorative approach, because prior research on chatbots, in general, and enterprise messengers such as Slack apps and integrations, in particular, is scarce.Accordingly, a qualitative empirical research design is applied with the objective to enlighten this so far unexplored phenomenon inductively with rich contextual insights (Paré 2004;Yin 2008).Grounding our research in the interpretative paradigm allows us to gain a deeper understanding of the meaning that individuals assign to the phenomenon of interest (Klein and Myers 1999;Walsham 1995).

Phase 1: Preliminary study
Following the call to take the IT artefact as serious as its potential effects (Orlikowski and Iacono 2001), we started with a preliminary study to explore Slack and its apps and integrations in regard to its materiality.This involved examining the documentation of Slack and its API to gain an understanding of the material features.We then built a crawler, which we used to parse the Slack App Directory (Slack 2016a) on October 11, 2016.From that, we collected the names, descriptions and the associated categories (one or more from 17 categories) for each of the available apps and integrations.After an initial exploration of each category, we calculated the number of chatbots per category as well as association rules to determine how the categories relate to each other.Later in the research process, we run the crawler again before Phase 3 (Dec.2018).
Our findings, which include the full list of publicly available Slack apps and integrations from two points in time (i.e., 2016 and 2018), allowed us to visualize the corresponding development over time (see Fig. 16).We find that a large share of available integrations is targeted at software developers.In the first run, we collected 722 Slack apps and integrations, whereas most of them were assigned to the categories of productivity (n = 223), social and fun (n = 188), communication (n = 157), developer tools (n = 146) and bots (n = 130).
Overall, the preliminary study adds to the research at hand in two ways.First, we obtained an understanding of the potential user groups relevant for the recruitment of interviewees and participants of the Q-Methodology study as well as it served as initial overview of potential use scenarios of apps and integrations within Slack.Second, the preliminary study helps in the interpretation of our results and enriches the discussion.

Data collection
We conducted 29 semi-structured interviews with employees from 17 companies to investigate their usage of chatbots within their work context (see Table 1).The interviews were conducted in two phases from May 2016 to January 2017 and from October 2018 to November 2018 (see Phase 2a and 2b in Fig. 4).
The interviewee selection process was as follows.The overarching goal was to collect empirical data from multiple social and organizational contexts, because our objective is to explore a broad range of affordances, which are, per se, contextual.Consequently, we selected interviewees form different organizational contexts so that a variety of industries and company sizes is included.All interviewees were recruited using Snowball sampling to obtain a sufficient set of interviewees (Myers and Newman 2007).In doing so, we only included interviewees that have used the corresponding enterprise messenger (i.e., Slack, Microsoft Teams or Telegram) as well as the corresponding chatbots (e.g., Slack apps and integrations).
In Phase 2a, we searched for employees in organizations that use Slack together with Slack apps and integrations.Thereby, the interviewee selection process was based on the findings from the preliminary study.Specifically, crawling the Slack App Directory showed that a large share of available integrations is targeted at software developers (e.g., 146 apps and integrations are assigned to the category developer tools).
To prevent an overemphasis on affordances for software developers, we selected about the same number of interviewees with and without programming skills (see Table 1).In Phase 2b, the interviewee selection process followed a theoretical sampling approach that is grounded in three purposes.First, roughly two years after conducting the first interviews we aimed at exploring how the usage of chatbots within enterprise messengers evolved over time.This is why we conducted 4 additional interviews with interviewees from companies that participated already in Phase 2a (see Alpha and Gamma in Table 1) as well as 4 interviews with employees working in a fast-growing company (see Iota in Table 1).More specifically, we selected Alpha and Gamma, since both organizations experienced changes such as growth and office relocation.In both companies (i.e., Alpha and Gamma), we interviewed at least one interviewee twice to compare the perceptional changes of the same person over time.Second, we aimed at exploring distributed, virtual and extended team settings, which is why we conducted 4 additional interviews (i.e., Interview #21 to #24).Third, we strived to understand differences in tooling.To do so, we conducted 5 additional interviews with employees of organizations that rely on Microsoft Teams and Telegram (i.e.,Interview #25 to #29).In total, we conducted 17 additional interviews in Phase 2b (leading to an overall number of 29 interviews).
The interview process was as follows.The interviews lasted between 30 and 100 min (with an average of 48 min) and were recorded as well as transcribed right after conduction.To prevent misunderstandings and to increase the expressiveness of the statements, we either conducted the interviews in German or English depending on the native tongue of the interviewee.Grounded in open-ended questions, the interviewees were initially asked to describe how their enterprise messenger and chatbots are embedded in their everyday work.Accordingly, we characterize the studied enterprises in Table 1 in regard to the assimilation of their enterprise messenger in terms of adoption (i.e., decision to use), acceptance (i.e., committed to use), routinisation (i.e., frequent use), and infusion (i.e., comprehensive and sophisticated use) (Wang et al. 2012).
Due to the semi-structured nature, we were able to dig deeper when the interviewees mentioned interesting and unexpected ways to harness chatbots for their routines (Paré 2004).In the beginning, we asked general questions to get to know the interviewees, e.g., their job position and tasks.Then, we asked what role the corresponding enterprise messenger in general plays in their daily work, e.g., by probing work practices and typical workday journeys.Questions relating to chatbots ranged from today's perceived action possibilities, benefits as well as disadvantages and constraints.Finally, we moved from questions that referred to today's use towards Fig. 4 Research approach with three phases at a glance questions that addressed changes in usage over time as well as planned and expected future use potentials of chatbots to accomplish individual and organizational goals.From about a quarter of the organizations, at least one interviewee additionally showed us on a tablet or computer how their team uses chatbots.
In Phase 2b, we additionally employed card sorting of the emergent list of identified affordances (Fincher and Tenenberg 2005).Specifically, each identified affordance (i.e., 14 affordances across 4 categories) was printed on card and together with two concrete examples from Phase 2a.Category by category the interviewees had to comment on their perceptions of each affordance, while sorting the cards by perceived relevance for their organizational context.Finally, the interviewees sorted the four categories of affordances by relevance.

Qualitative data analysis
To proceed in a rigorous way, we have collected and analyzed data iteratively until a coherent picture emerged (Corbin and Strauss 1990;Klein and Myers 1999).During the data analysis we performed an interwoven three-step approach for our qualitative data analysis consisting of open, axial and selective coding resulting in a total of 1613 codes (Corbin and Strauss 1990).In the open coding procedure, we inductively coded concepts to condense the transcripts and obtain an overview (Yin 2008).During the axial coding procedure, the coding structure was based on our theoretical underpinning: properties of the IT artifacts, properties of the actors (related to their goals, capabilities and contexts), and perceived and actualized affordances as well as constraints.In this process, the identified axial codes were grouped in categories (e.g., Category 1 to Category 4 presented in the results section).Through iteratively making connections between the fractured codes, a core theme emerged (Strauss and Corbin 1990).That is, different higher-level affordances and constraints emerge for members of a group channel as a consequence of the actualization of a lower-level affordance in this channel by a (potentially other) user.Consequently, we sharpened the relations between the identified affordances and constraints in the selective coding procedure.Following the principle of theoretical sensitivity (Corbin and Strauss 1990;Strauss and Corbin 1990), we built on Bygstad et al. (2016) to analyze how the actualization of lower-level affordances and constraints results in higher-level mechanisms.Specifically, our coding structure was extended with higher-level affordances, while continuing to strengthen the codes relating to relevant properties of IT artifacts and actors.
During the entire coding procedure, we triangulated multiple sources of evidence with the software MAXQDA 12 (Yin 2008).This included the transcribed interview recordings, notes and observations, with supplementary data provided by the companies: (1) screenshots of chatbots in use, (2) lists of chatbots in use, (3) documentations, (4) blog articles referred by one of the interviewees (which is also the author of the blog article), and (5) a video recording of a practiceoriented conference presentation (team of Company Beta) on how they harness chatbots for software development and operations.This allowed us to examine chatbots in use from different sides and in different embedded contexts (Klein and Myers 1999;Orlikowski and Iacono 2001).
Sensitivity, that is, the authors ability "to identify what data is significant and to assign it a meaning" (Halaweh 2012, p. 36) is crucial for interpretative research that relies on human interpretations and meanings (Walsham 1995).Sensitivity can come "from experience, especially if the researcher is familiar with the subject under investigation" (Halaweh 2012, p. 36).From this point of view, it was an advantage that the first and third author of this article use Slack apps and integrations in their daily lives, because it helped them to understand the statements made by the study participants.On the other hand, to minimize salience bias as well as to maintain a critical distance between the personal use of Slack apps and integrations of the researchers and the views of interviewees, we cross-checked the transcriptions with the second author (not an active user of enterprise messengers) and generated a shared meaning through multiple interactions in which we engaged back and forth with the empirical data, theory and our emergent coding schema (Walsham 1995(Walsham , 2006)).

Phase 3: Q-methodology study
To further explore in more detail the mental models that employees have developed when using chatbots (i.e., integrations into conversational threads), we have chosen to apply a mixed-method approach called Q-methodology, as it offers a rigorous and systematic way for capturing human subjectivity (Mettler and Wulf 2018;Stephenson 1935Stephenson , 1986)).
Though Q-methodology is particularly used in other research fields as IS research, for instance health services research (Baker et al. 2014;Stenner et al. 2003), a small number of articles have proven its usefulness for IS research.Specifically, adopting a Q-methodology in IS research has proven to be valuable to investigate differences in the decision-making of project managers (Tractinsky and Jarvenpaa 1995), to segment the ecommerce industry based on the subjective assessment of e-commerce providers (Storey et al. 2000), and to explore user resistance in enterprise implementation (Klaus et al. 2010).In particular, when exploring affordances which technological artifacts provide, it proved a useful tool to systematically analyze the subjective perception of these artifacts (cf.Mettler et al. 2017;Mettler and Wulf 2018).Both of the latter studies draw on the affordance theory to study the attitudes towards adopting service robots (Mettler et al. 2017) and to explore the mental models of employees who are faced with the introduction of physiolytics (Mettler and Wulf 2018).
Q-methodology is deemed as suitable for in-depth study of situations where the subjective perception of a study's participants is of special interestin our cases the perception and actualization of affordances (McKeown and Thomas 2013;Tractinsky and Jarvenpaa 1995).Thus, Q-methodology attaches particular importance to the sampling of subjective statements.Yet, it allows to construe generalization while at the same time maintaining a high level of phenomenology as well as acknowledging and considering the subjectivity of respondents (Dziopa and Ahern 2011;Wingreen et al. 2009).As such, Q-methodology can be seen at the interception of quantitative and qualitative research (Klaus et al. 2010).Finally, Q-methodology often uncovers unusual or counterintuitive patterns which are not related to a study participant's characteristics and may thus be neglected by typical survey-based studies (Zabala and Pascual 2016).
Figure 5 highlights four main parts of Q-methodology studies (Brown 1993;Van Exel and De Graaf 2005): (1) collecting a wide range of perspectives on a topic and selecting a set of statements referred to as the Q-sample or Q-set, (2) purposefully selecting a set of participants referred to as the P-set, (3) asking the participants to conduct a comparison and ranking of the statements referred to as the Q-sort, and, finally, (4) analyzing and interpreting the results by performing statistical factor analysis.We will now describe how we conducted these steps.

Q-set development procedure
The foundation of each Q-Methodology study lies in collecting subjective statements (i.e., opinions, tastes, preferences, sentiments, motives, but not facts) that represent the perceptions of a certain topic of interest, which is referred to as the concourse (Brown 1993).According Q-Methodology, these statements can come from various sources (e.g., derived from interviews, participant observations, literature, media reports, or created from scratch) and can be presented in various formats (e.g., text, pictures, paintings, music, videos) (Brown 1993;Donner 2001;Van Exel and De Graaf 2005).Then, a subset of the statements is drawn from the concourse to develop the Q-Set.
In our research, we ground the development of the Q-Set in the rich qualitative insights gathered in Phase 2 of this research that comprises interviews 24 h of interviews with users of chatbots within enterprise messengers (e.g., apps and integrations within Slack) across 17 organizations (see previous section).From that, a set of 28 statements was derived that covers employees' views on affordances (14 statements) and constraints (14 statements).By considering both affordances as well as constraints, our Q-Set covers a heterogeneous set of statements that broadly represent perceptions that proved to be relevant (Watts and Stenner 2005).Furthermore, we relied on guidelines to ensure that the formulation of the statements is similar in style (Donner 2001).Specifically, we choose a framing of the statements so that each makes an assertion about an Fig. 5 Overview of Q-methodology concepts and procedure of this study How affordances of chatbots cross the chasm between social and traditional enterprise systems action/ value potential or constraint/ limitation of chatbots/ integrations within enterprise messengers (Watts and Stenner 2005).For example, the statement that corresponds to affordance AFF-01 was formulated as follows: "I perceive integrations into Slack, HipChat or similar as valuable for receiving status notifications and updates from third-party systems within channels".On the other hand, constraint CON04 was formulated as follows: "I perceive Slack, HipChat or similar messenger integrations as constraining, since they lead to information overload".P-set recruitment procedure Q-Methodology studies are conducted with a relatively small number of participants (Stephenson 1935;Van Exel and De Graaf 2005) that is usually smaller than the Q-set of statements (Brouwer 1999) and that enables the comparison of the resulting factors with each another (Brown 1980).Following this methodological backdrop, and similar to Phase 2, a purposeful sample of 28 information-rich participants was recruited to take part in the Q-sort survey.Note that the key consequence of non-random sampling is that inferences are only made about the viewpoints of the participating groups on the given subject (i.e., the factors that influence the perception of chatbots within enterprise messengers), but not about the wider population and the distribution of the viewpoints among the respondents (Baker et al. 2006;Davies and Hodge 2007;Watts and Stenner 2012).
Next, we selected employees who are expected to have a clear and distinct view on chatbots within enterprises messengers.Namely, we focused on knowledge workers that perform mainly digital work, that is, "[an] effort to create digital goods or that makes substantial use of digital tools " (Durward et al. 2016, p.283) and that use chatbots within enterprise messengers as part of their daily work.Accordingly, the descriptive statistics of our list of respondents shows that 96% of the participating knowledge workers engage in work with digital input and output, while 4% of them engage in physical work (i.e., consultants that conduct face-to-face workshops).75% of the respondents use their enterprise messenger for work in a dispersed, distributed, or extended team setting, whereas 25% use it locally.Furthermore, 39% of the participants work in micro enterprises (fewer than 10 employees), 36% in small enterprises (10 to 49 employees), 18% in medium-sized enterprise (50 to 249 employees), and 7% in large enterprise (250 or more employees).Within these work contexts, 57% of the study participants use their enterprise messenger as their main collaboration tool at work (i.e., replaces internal email), while 43% use it as a complementary tool.Moreover, most of them were somewhat familiar with programming integrations (71%).Lastly, 21% were females and 79% males.

Q-sort study procedure
All participants received links to a Q-Sort survey tool (see Fig. 6), which was setup using a fork1 of the open source software Easy-HtmlQ2 that allows working with the database system Firebase.
Aside from configurational changes (e.g., introduction text, guidance through the individual steps, statements), we additionally adjusted the source code of the tool so that color priming is minimized (i.e., we removed the red and green color to ensure that participants are not primed to agree on the provided statements) and usability is increased (i.e., we implemented a hover feature for statements that were already sorted).
Each participant was guided through five steps.
Step 1 introduced the background, the goal and the expected duration of the study as well as author-related contact information.In Step 2 each statement was shown individually to the participants (in random order), which then had to select "agree", "neutral" or "disagree" by either using drag and drop or by pressing the corresponding keyboard shortcuts.Following the widely established procedure of using forced-choice quasinormal distributions in Q-methodology studies (McKeown and Thomas 2013), Step 3 comprised sorting the statements into the five levels of agreement ranging from +2 (agree) to −2 (disagree).The instructions guided the participants to start with the agree pile, read the statements again, select the four statements that participants mostly agree with and place them on the right side of the score sheet below the +2 (see Fig. 6).This process was continued with sorting statements into the piles for statements that are perceived as most disagreed (−2), partly agreed (+1), disagreed (−1) as well as neutral (0).Step 4 involved commenting on the four most agreed and disagreed statements.Finally, in Step 5, the participants were asked to answer a set of descriptive questions (e.g., age, sex, job role, industry, company size) as well as indicate the relevance of chatbots for different types of channels on a scale from 1 to 5 (e.g., project team channels, inter-organizational channels).

Quantitative data analysis
We used the software Ken-Q Analysis Desktop Edition (KADE) (Banasick 2019) which offers dedicated calculation functionalities for the analysis of Q-Methodology studies (Version 1.0.0).We started by exporting all Q-Sort survey records from the Firebase database and calculated the correlations between the respondents, which resulted in a by-person correlation matrix (Watts and Stenner 2005).At the core of Q-Methodology, the correlation matrix lies the foundation to apply factor analysis to determine a set of basically different Q-sorts that are evident in the data (Brown 1993).Note that the way factor analysis is applied is on a by-Q sort (i.e., byperson) level, which means that each record is transposed so that the statements are in rows and the sort values (i.e., from −2 to +2) are in columns (i.e., one column for each participant) (Mettler and Wulf 2018).
To perform the factor analysis, we used principle components analysis (PCA) with Varimax rotation of seven factors to maximize statistical differences (McKeown and Thomas 2013).To do so, on the one hand, we calculated eigenvalues, the explained variance (in percent) as well as the cumulative explained variance (in percent) for each factor so that we were able to extract seven factors with eigenvalues greater than 1.00.This is a widely applied criteria for initially selecting factors (Coogan and Herrington 2011;Donner 2001), however, scholars commonly agree to critically reflect the number of factors to include in the final selection (McKeown and Thomas 2013).
Therefore, we proceeded with calculating the idealized Qsorts for each factor and read carefully through the corresponding statements.Basic statistics on normal distributions suggests to perform calculations with a standard error of 2.58 for the 99.5 percentile point.To decide on the Q-Sorts to include for each factor, we calculated the value for significant factors loadings as follows: 2.58 * 1/√ (number of statements) = 2.58 * 0.189 = 0.488.Accordingly, a Q-sort was included if greater than 0.488 for a given factor.For each factor we calculated the distinguishing statements with p < 0.05 and p < 0.01 and checked for which statement the z-Score is higher or lower compared to all of the other factors.With this foundation, we applied theoretical or so-called judgmental rotation, which is recommended to harness domain knowledge to consider the factors from different angles before choosing a factor solution (e.g., Baker et al. 2006;Brown 1980Brown , 1993)).
Finally, we extracted five factors with eigenvalues greater than 1.00 and a cumulative explanation of 67% of the variance.With this decision we are in line with the eigenvalue criteria (Coogan and Herrington 2011;Donner 2001) and we ensure that at least two Q-sorts loadings are significant per factor (Watts and Stenner 2012).As such, these five factors represent five distinct interpretations of the relationship between employees and chatbots, since each factor can be understood as a viewpoint that is commonly shared between groups of similarly minded employees (i.e., they have similarly sorted the affordances and constraints statements into the forced-choice quasi-normal distribution).Going carefully through the idealized Q-sorts and comparing the distinguishing statements with the respondents (given their descriptive statistics and comments) allowed us to assign appropriate names to the factors.

Results
Our research reveals 14 lower-level affordances and 14 constraints of chatbots within enterprises.In the following these affordances and constraints are illustrated along four categories by providing empirical evidence from exemplary actualization contexts (see Tables 2, 3, 4, and 5).We find that the actualization of these lower-level affordances as well as constraints in group channels offer higher-level affordances that emerge for the members of this channel (see Fig. 7).It is in the very nature of affordance theory that technologies provide different possibilities to different people.Accordingly, the second part of the results section reveals how employees weigh the identified affordances and constraints against each other by pointing out similarities and differences in perception along five factors identified in the Q-Methodology study.2) emerge from chatbots that post messages into conversational channels with information from third-party systems and outcomes of automated workflows.
Higher level affordances Being able to integrate messages from multiple chatbots and humans in one place affords to consolidate and unify communication flows."I know that all the important things that I have to be aware of end up [in the corresponding Slack channel]" (Interview #15).This yield "a tremendous saving of time.Instead of gathering information up from emails and hundreds of third-party systems, I have everything at a glance" (Interview #15)."I see everything that happened over night, this is cool because conversations are sorted by project [channel] and I can go through by priority" (Interview #5).Furthermore, it relieves employees from "switching between monitors and programs all the time" (Interview #16) and "it redeems from informing someone that you have pushed [source code], because it happens automatically" (Interview #1).Thus, affording to automate information flows and, consequently, to uncouple information flows from individual employees.
In addition, our interviewees expect that actualizing Affordances 1.1 to 1.4 can collectively lead to increased ambient awareness.Chatbots "help team members to be more aware of the load they are putting on others" (Interview #4).An interviewee perceived that receiving build and continuous integration updates brings business and technology closer for salesso, it certainly creates proximity to the software development team" (Interview #3).Also, within teams, "I notice what is going on in other repositories [from my team] where I'm not directly involved" (Interview #1).
Moreover, teams created dedicated channels, e.g., a channel for major errors, where "I know exactly, if something goes wrong, then, we really have a major problem which absolutely has to be resolved" (Interview #15).As described by the interviewees, this nicely coalesces with the possibility to react to any posted content (e.g., with emojis, replies).For the interviewees, this is how it affords them facilitating discussions, as well as faster and shorter feedback cycles, which "is key in today's world.When a developer gets aware of what user x thinks about our product at the same time as I do, then, the communication simply flows much faster.And this is something we cannot achieve differently, even if I would tell it in every daily [Scrum meeting], which would be completely inefficient" (Interview #13).Here, the affordance to uncouple such information flows from individual employees was described with positive side effects, namely, "it also feels better [when the information of bad product reviews comes from the bot instead of the boss]" (Interview #13).
Finally, posting metrics and key performance indicators makes undisciplined behavior and violations against reference values visible (see Fig. 8).This enables to enforce discipline and compliance, because "they could see the problems" (Interview #4).Accordingly, possibilities to shape the organizational culture emerge.
Constraints By having machines post messages to channels, a risk of producing information overload exists.It "is basically a question of [applying the] push or pull principle... do I really have to know when someone builds, or do I look it up when I need it?"(Interview #12).Therefore, integrating chatbots that post messages has to be well thought out, to prevent the messages from becoming constraining.In fact, "messages regarding the build processes were only interesting in 20% of the time" (Interview #12).Our results indicate that the way incoming chatbot messages are perceived (e.g., as an affordance or a constraint) strongly depends on the individual workflow and current context, which is not necessarily aligned with the other subscribers of a channel.Project status meeting agendas generated from metadata are perceived as "semi-interesting because I spend at least some hours on that project every day, but for people that are less involved it is very useful to run a meeting" (Interview #5)."These are my daily working tools, I don't need an integration that tells me hey your project has reached 50% of the billable hours, because [as a manager] I'm using this software every day" (Interview #12).This plays well together with the possibility of Slack to mute individual channels.Therefore, "we have thought about creating a separate channel for our chatbot and if it annoys you, then you can simply leave or mute the channel" (Interview #1).However, "if a separate channel is used, then, you risk not being able to reach all team members anymore.It has to be balanced how important it is that everyone sees it" (Interview #1).Interviewees expect to be able to "create some sort of digest, which means that I would be able to choose getting information [i.e., chatbot messages for a certain channel] only once per day, week, only during nights or just if it matches certain filter criteria" (Interview #15).Some interviewees perceived incoming information to be redundant, and thus, distracting."At a certain point I had to say okay if I get this notification also here [within Slack] and I have already seen it before [notifications of the third-party system on mobile and desktop], then it distracts more than it is useful" (Interview #3).Furthermore, the textual representation of information was perceived as a constraint."I like having information graphically prepared" (Interview #15).

Category 2. Affordances and constraints related to getting triggers
Next, three affordances (AFF-05 to AFF-07 in Table 3) ground in the potential of chatbots to allow setting and getting triggers.2.00 avg.sort position (with 1 being the most relevant of 3 cards) in Phase 2b.0.93 avg.Q-Sort ranking (from +2 to −2) in Phase 3.
Setting and getting nudges/ triggers to action with possibilities to resolve it (AFF-07) Context (Gamma).Time tracking is a common task of employees.However, it often gets forgotten and is difficult to do later.To prevent this, a chatbot is used.Outcome.Reminders to capture working hours are posted and can be resolved by responding to the chatbot.
1.71 avg.sort position (with 1 being the most relevant of 3 cards) in Phase 2b.0.96 avg.Q-Sort ranking (from +2 to −2) in Phase 3. Higher level affordances Setting reminders was perceived as affording automation of repetitive message flows and, thus, to relieves employees from repetitive work."So that not every day someone has to write [to remind of the daily scrum meeting]" (Interview #3).Also, getting reminded to perform some task together with the potential to resolve it, was perceived as a chance to increase efficiency."If I get reminded every evening [to capture the hours I worked], then everything is done in 3 seconds" (Interview #7)."I see a lot of potential for activities which are made regularly, but not every day" (Interview #6).Furthermore, it was perceived as enforcing team discipline and compliance.As such, it provides "advice in accordance with our development culture" (Interview #4).For example, it includes problem areas and undisciplined behavior, such as unassigned pull requests or unassigned issues.Thus, it affords to shape the organizational culture.An interviewee stated that "sometimes something goes forgotten and then you get daily a reminder" and has compared it to previous situations in which "a project manager had this [...] job to run after all to say why are there no labels and why is this like that" (Interview #5).
On the one hand, such chatbots are perceived as tools to relieve managers from repetitive micromanagement tasks, which are then executed automatically in a consistent and exact way."It is mainly a tool that helps our managers to enforce discipline.For me as a developer it is much less useful than for him" (Interview #5).On the other hand, the technology is perceived as an actor that "keeps its eyes on us and barks when it saw a slip in discipline" (Interview #4).However, "as soon as it becomes quantitative, employees begin to play out the whole thing.If you tell me one gets points for each movement on the [Kanban] board, then, I can create micro issues and move them through" (Interview #5).
Constraints On the one hand, certain teams "want to keep up the degree of freedom so that we do not really want to squeeze ourselves into processes" (Interview #16).On the other hand, many bot-specific constraints were perceived, such as a lack of usability.The chatbot "only asks, I give the input and then it disappears.It should also be visually recognizable what I have entered.[...] But basically I think it is good when you are able to directly resolve things" (Interview #6).As a consequence, other technical artifacts often afford similar goal-oriented actions, e.g., "my calendar reminds me as well with a popup" (Interview #6).
Furthermore, interviewees expected "an official communication to everyone or for a certain group that informs what we want to achieve, and then that applies to all.[...] And that did not exist in this case, there was no communication.Suddenly, there was a bot who has asked me now and then what I do" (Interview #6).

Category 3. Affordances and constraints related to queries and invocations
Additional four affordances (AFF-08 to AFF-11 in Table 4) are reveal potentials to query and invoke functionality of thirdparty systems.
Higher level affordances Being able to capture data into thirdparty systems directly from Slack was perceived as valuable to achieve everything in one place, but not necessarily act as a substitute for the third-party systems."We do not want to replace it, we still open Trello but we have the possibility to capture tasks [directly within Slack].This makes it much easier, because you can mark something, copy, and quickly pass it over [to Trello]" (Interview #16).Accordingly, it relieves employees from application switching.
Moreover, being able to query and invoke functionality from third-party systems was perceived as a possibility for rapidly building prototypes without having to develop and introduce yet another employee-facing user interface.It is useful "for new features that we develop and try out.So, you can prototype faster" (Interview #5).It was also used to provide a broader audience with access to third-party systems so "that they have an interface to pull information easily [from the database]" (Interview #15).
Using commands (or natural language) to invoke functionality within Slack does not only afford the accomplishment of the invocation itself, it also simultaneously affords visibility to all members of the team channel.For example, when directly deploying from the project channel within Slack, then, the information about who is deploying when is disclosed."It saves to say I now have pushed a new version, because it happens automatically" (Interview #1).Hence, it affords automation and consequently ensures certain information flows.At the same time, invocations become traceable and searchable in real-time, thus, facilitating ambient awareness within the teams."Usually just before 7, I open Slack and see what my colleagues in India have already done" (Interview #5).In turn, reactions and discussions enable fast feedback cycles.
Furthermore, possibilities to introduce gatekeepers arise, e.g., the default Slack bot tracks the status of people and intervenes when someone sends a message to ask if Slack should really push a notification, even though the user status is set on "do not disturb".This is helpful "in general to reduce noise, like a personal assistant as a gatekeeper" (Interview #5).In addition, invocations might be verified, delayed or prevented.In fact, chatbots afford to separate different organizational units (e.g., developers from the production environments of customers) and glue them back together.
Constraints In the long run, querying information within Slack was found to be constraining, as compared to dedicated tools."The company has grown now.For the beginning it was relatively simple and also easily possible [for the sales team to query data within Slack], but the more customers and the bigger the customers, you need proper tools for data processing, aggregation, and evaluation" (Interview #15).
Passing parameters with commands to invoke functionality was also perceived as constraining."We then started to build our own tools, because it is annoying to pass numerous parameters with commands and they [i.e., existing Slack apps and integrations] are often not really configurable" (Interview #15).
Non-technical interviewees often expressed difficulties to obtain an idea about how certain Slack apps and integrations may create value."What is missing are cases that point out how teams work with this and that and thus showing how it [i.e., the Slack app and integration] creates added value" (Interview #3).

Category 4. Affordances and constraints related to enriching messages
Finally, three affordances (AFF-12 to AFF-14 in Table 5) relate to enriching outgoing messages of human actors.
Higher level affordances In the majority of the considered organizational contexts, variations of chatbots enrich messages with appropriate gif images to increase the expressive power of textual communication.Using them affords to foster team cohesion, spirit and fun, because "especially in a distributed team, it is relatively difficult to promote interpersonal communication" (Interview #5).Assuming that "you have forgotten something, then, a gif is shown from Barack Obama where he drops his microphone.This is just to promote interpersonal communication and to not having quite such a dry business context" (Interview #5).It is "just for fun, but I think to a relatively large extent, it helps to keep the people together" (Interview #15).
Having messages processed and enriched with additional information, was found to play well together with the basic functionality of Slack, e.g., by automatically importing files posted as links within a message to enable searches on it.Access to files can be simplified by automatically sharing it with channel members.Overall, it affords linking and consolidating third-party systems within Slack, e.g., traditional enterprise systems such as customer relationship management systems.
Constraints It was stated that "much is about playing a bit and a bit of fun, but what is the real value added?" (Interview #3).Accordingly, the use has decreased over time."When we introduced Slack, it almost exploded for three days, because for

Understanding perceptional similarities and differences among employees
Conducting physical card sorting as part of the interviews of Phase 2b and the subsequent Q-Methodology study in Phase 3 reveals patterns of how employees weigh the perception of affordances against the perception of constraints that emerge from chatbots within enterprises.Specifically, our empirical data highlights both similarities as well as differences among employees in the perception of chatbots within enterprises.Perceptional similarities can be summarized along two dimensions.
First, we find that on average employees perceive affordances related to receiving messages from thirdparty systems (i.e., Category 1) as higher compared to all other affordances.This finding is true for both conducted card sorting studies (see the heatmap of values from Phase 2 and Phase 3 in Appendix).Though we explored the use of alternative messenger platforms aside from Slack (i.e., Microsoft Teams and Telegram), the identified affordances and constraints within the enterprise context remained rather constant.However, aside from chatbots, Microsoft Teams provides tabs as an alternate form of messenger integrations with third-party systems, which offer similar affordances, e.g., both tabs as well as chatbots may be used to receive metrics and key performance indicators within Microsoft Teams (Interviews #26 and #27).
Second, throughout the participants of the Q-Study, the relevance of chatbots is assessed as highest in group channels that relate to projects at work (see Fig. 9).In contrast, the variance in the assessed relevance of chatbots was much higher for all other types of group channels.In fact, this variance in the relevance of certain channels is also reflected in the qualitative interviews.For example, an interviewee explained that inter-organizational channels became relevant when they moved to a new co-working space that promoted such a channel (Interview #2).We find that changes of the socio-technical context over time (e.g., hiring new co-workers, changing the office location, introducing new third-party systems) alter the coordination needs and, thus, the perception of chatbots by employees.In turn, this leads over to the perceptional differences studied in our Q-Methodology study.Context (Alpha, Delta, Theta).Teams working with file management services (e.g., Dropbox, Google Drive) use apps and integrations to extend the functional scope.Outcome.Posted messages with links to files are processed (e.g., imported) and enriched (e.g., meta-information).
Having messages processed and replaced (AFF-13) Context (Beta, Delta, Eta).As a response to the limiting interpersonal communication with textual messages, chatbots such as Giphy provide potentials to increase the expressive power of textual messages.Outcome.Using the available commands together with a keyword replaces the message with a topic-related gif image.
Having messages processed and visually enriched with user interface elements (AFF-14) Context (Iota, Kappa, Lambda, Mu, Nu).Gathering feedback within teams by creating short polls and surveys is a frequent task of employees.However, when doing so by asking a simple question it is difficult to keep an overview of replies.Outcome.Polls are created within a channel of choice by employees can vote/ participate by using buttons, while the votes are visually aggregated.

Fig. 9 Relevance of chatbot integrations per channel type
Our results highlight five factors that represent perceptional differences among employees in the form of five distinct viewpoints on chatbots.Specifically, we find that chatbots within enterprise messengers are viewed (1) as operational assistants, (2) as central information hubs, (3) as difficult to use black boxes and worse alternatives to dedicated tools, (4) as shadow IT in restrictive and closed legacy environments, and (5) as spammy and process-enforcing burden.In the following we elaborate each of the five viewpoints and present the idealized Q-Sort in Figs. 10,11,12,13,and 14.

Viewpoint 1 -as an operational assistant at a central point of team coordination
The first viewpoint reveals a group of employees that perceive chatbots within enterprise messengers as operational assistants that help them invoking functionality from thirdparties, setting and getting reminders within channels, receiving real-time information and having messages processed as well as visually enriched (e.g., in the form of polls): "Sometimes we need to create a poll to decide about some things as a team.That's why it's very useful that we can do it in here where all team members have access to and can come back to see the result" (Participant 19).In line with the identified higher-level affordance of relieving employees from application switching, one participant commented on the Q-Sort as follows: "It is particularly helpful, because I do not need to open a new program and, hence, I can save a lot of time" (Participant 8).A second thought pattern that is shared among this group of employees is the value that arises from the central point of team coordination: "If one starts a deployment to production, another needs to confirm in Slack.Once it's done, a quality assurance engineer needs to confirm that everything is ok.All information of a deployment is easily visible in the Slack channel and one can comment on it" (Participant 15).Accordingly, the Q-Sort shows that employees of this group strongly disagree with the assertion that information is repetitive due to alternate systems such as email.Comments reveal that organizations of this group of employees have mostly replaced emails: "I'm often using Slack instead of Email" (Participant 5).
CON-05 Repetitive information since I often already know the information from alternative sources such as notifications.
CON-02 My company constraints the usage of such messengers.
CON-14 It is more about playing and having fun than real value added.
CON-09 Information is concealed after I sent the message.
CON-13 It is difficult to know how to use them.
CON-04 They lead to information overload.
CON-06 Repetitive information since I use these systems in my everyday work.
CON-08 They introduce process-orientation and reduce my autonomy.
CON-10 I can achieve the same results with dedicated tools.
AFF-09 Querying information from third-party systems within channels.
AFF-12 Having messages processed and enriched with additional information.
AFF-03 Receiving aggregated information from third-party systems within channels.
CON-11 Lack of rich user interface elements for entering data.
AFF-11 Adding gatekeepers that validate access to functions of third-party systems.
AFF-08 Capturing data in third-party systems from within channels.
CON-07 The presented information lacks graphical and visual richness.

Viewpoint 2 -as a central information hub for the coordination of human and machine work
The second viewpoint highlights the value of chatbots in contemporary enterprise messengers to keep pace with what is going on at work by automating status notifications and updates."When I log on, I quickly see what I've missed" (Participant 21)."It is super convenient to have all notifications in one place.I don't like to check all tools every day to see if something has come up" (Participant 16).In line with the very nature of "instant" messengers to facilitate real-time information between humans, chatbots extend this possibility with real-time information from third-party systems: "Issues and GitHub commits are reported live and give an overview of what is currently going on" (Participant 28).Similar to employees that perceive chatbots as operational assistants, members of this group heavily rely on chatbots in their work practices: "When I know that Slack will send me a message when my build fails, then I don't check the other tools.Thus, the confidence in the integration must be so good that you no longer have to check the other tool" (Participant 2).A further perspective that is taken is the that information from humans and machines come together in one place: "So far I found no other tool that allows me to integrate information from all other systems and, at the same time, can be used as a communication channel" (Participant 16).Following this line of thought suggests that employees like switching back and forth between passively following work activities and actively coordinate work: "With HipChat it is possible to collect all information about a topic and to discuss problems (e.g., build errors) immediately.That's why I notice HipChat notifications more than mail notifications."(Participant 24).Consequently, this viewpoint goes along with task dependencies: "It raises awareness when someone contributed or finished a part of work that is relevant for one's own task" (Participant 5).
Viewpoint 3 -as a difficult to use black box and a worse alternative to dedicated tools The third viewpoint reflects the opinion of a critical group of users that shares concerns regarding usability and that is skeptical that chatbots provide an added value in comparison to dedicated tools with richer user interfaces.On the one hand, the Q-Sort highlights agreement with constraints in the ease of use of chatbots that are integrated into the conversational thread: "most of the integrations I don't use, because it's not worth the effort, I prefer to use the original application" (Participant 20).On the other hand, information is concealed after messages are exchanged: "It's very hard to keep track of information, there is no system, only the chronology of the messages" (Participant 20)".As such, the perspective of this group is in contrast to the previous two viewpoints, even though all three groups compare chatbots with alternate tools: "probably I could achieve the same result with other tools, but not in the same time, e.g., if I would have to check one system for my alerts, talk to my colleagues in another tool and, then, analyze it further in a third tool, I would need much more time" (Participant 11).Nevertheless, this rather skeptical CON-08 They introduce process-orientation and reduce my autonomy.
CON-13 It is difficult to know how to use them.
CON-03 Most of my work is not digital.
CON-01 Most software at work is not open enough and has limited integrations with messenger.
CON-05 Repetitive information since I often already know the information from alternative sources such as notifications.
CON-10 I can achieve the same results with dedicated tools.
CON-02 My company constraints the usage of such messengers.
CON-07 The presented information lacks graphical and visual richness.
CON-14 It is more about playing and having fun than real value added.
AFF-12 Having messages processed and enriched with additional information.
AFF-11 Adding gatekeepers that validate access to functions of third-party systems.
AFF-09 Querying information from third-party systems within channels.
CON-04 They lead to information overload.
CON-11 Lack of rich user interface elements for entering data.
AFF-13 Having messages processed and replaced.
CON-12 Lack of configuration possibilities without programming customized integrations.
CON-09 Information is concealed after I sent the message.
AFF-07 Setting and getting nudges/ triggers to action and possibilities to resolve it within the channel.
AFF-03 Receiving aggregated information from third-party systems within channels.
AFF-08 Capturing data in third-party systems from within channels.
AFF-04 Receiving metrics and key performance indicators from third-party systems within channels.
AFF-10 Invoking functions from third-party systems and make this invocation visible within channels.AFF-14 Having messages processed and visually enriched with user interface elements.
AFF-01 Receiving status notifications and updates from third-party systems within channels.
AFF-02 Receiving real-time information from third-party systems within channels.
AFF-05 Setting and getting reminders within channels.
AFF-06 Setting and getting nudges/ triggers to action within channels.
Fig. 11 Idealized Q-sort for viewpoint 2 -central information hub How affordances of chatbots cross the chasm between social and traditional enterprise systems group shares the perception that chatbots are valuable for receiving real-time information and as a means for having messages processed and replaced (e.g., through a Giphy integration): "Most things are easier in a dedicated tool, but the most important thing for integrations are notifications and message enhancements" (Participant 1).
Viewpoint 4 -as shadow IT in a restrictive and closed legacy environment The forth viewpoint can be symbolically described as "driving with the handbrake on".Namely, it represents the perceptions of employees, which use enterprise messengers in (large) -2 -1 0 1 2 CON-14 It is more about playing and having fun than real value added.
CON-03 Most of my work is not digital.
AFF-10 Invoking functions from third-party systems and make this invocation visible within channels.
CON-02 My company constraints the usage of such messengers.
AFF-06 Setting and getting nudges/ triggers to action within channels.
CON-12 Lack of configuration possibilities without programming customized integrations.
CON-08 They introduce process-orientation and reduce my autonomy.
CON-04 They lead to information overload.
CON-01 Most software at work is not open enough and has limited integrations with messenger.
AFF-11 Adding gatekeepers that validate access to functions of third-party systems.
AFF-12 Having messages processed and enriched with additional information.
AFF-05 Setting and getting reminders within channels.
AFF-08 Capturing data in third-party systems from within channels.
AFF-01 Receiving status notifications and updates from third-party systems within channels.
AFF-07 Setting and getting nudges/ triggers to action and possibilities to resolve it within the channel.
AFF-09 Querying information from third-party systems within channels.
AFF-04 Receiving metrics and key performance indicators from third-party systems within channels.
CON-07 The presented information lacks graphical and visual richness.
CON-10 I can achieve the same results with dedicated tools.
CON-05 Repetitive information since I often already know the information from alternative sources such as notifications.
AFF-03 Receiving aggregated information from third-party systems within channels.
CON-06 Repetitive information since I use these systems in my everyday work.
AFF-14 Having messages processed and visually enriched with user interface elements.
CON-11 Lack of rich user interface elements for entering data.
AFF-02 Receiving real-time information from third-party systems within channels.
AFF-13 Having messages processed and replaced.
CON-09 Information is concealed after I sent the message.
CON-13 It is difficult to know how to use them.AFF-01 Receiving status notifications and updates from third-party systems within channels.
CON-13 It is difficult to know how to use them.
CON-14 It is more about playing and having fun than real value added.
AFF-04 Receiving metrics and key performance indicators from third-party systems within channels.
AFF-05 Setting and getting reminders within channels.
CON-11 Lack of rich user interface elements for entering data.
CON-08 They introduce process-orientation and reduce my autonomy.
CON-04 They lead to information overload.
CON-07 The presented information lacks graphical and visual richness.
AFF-06 Setting and getting nudges/ triggers to action within channels.
CON-12 Lack of configuration possibilities without programming customized integrations.
CON-09 Information is concealed after I sent the message.
AFF-10 Invoking functions from third-party systems and make this invocation visible within channels.
AFF-03 Receiving aggregated information from third-party systems within channels.
AFF-11 Adding gatekeepers that validate access to functions of third-party systems.
CON-06 Repetitive information since I use these systems in my everyday work.
CON-10 I can achieve the same results with dedicated tools.
AFF-07 Setting and getting nudges/ triggers to action and possibilities to resolve it within the channel.
AFF-14 Having messages processed and visually enriched with user interface elements.
AFF-09 Querying information from third-party systems within channels.
AFF-08 Capturing data in third-party systems from within channels.
CON-05 Repetitive information since I often already know the information from alternative sources such as notifications.
AFF-02 Receiving real-time information from third-party systems within channels.
CON-02 My company constraints the usage of such messengers.
AFF-13 Having messages processed and replaced.
AFF-12 Having messages processed and enriched with additional information.
CON-01 Most software at work is not open enough and has limited integrations with messenger.companies that constraint the usage of such enterprise messengers.In addition, the perceptions are shaped by barriers that result from the available IT infrastructure with a portfolio of enterprise software that is not open enough and lacks integrations into these enterprise messengers.Participants that agree to CON-01 and CON-02 in their Q-Sort comment this viewpoint as follows: "The current legacy systems are not made for such cloud-based tools.Currently I'm working at a big insurance company where most of their systems do not work with Slack or a similar tools" (Participant 7)."Unfortunately, I cannot even connect our ticketing or CRM system to Slack or other messenger systems due to data security reasons.I can of course understand the reasoning behind this decision, but it would be possible to properly handle such integrations (with some more effort) to be compliant with obligations we have towards our customers" (Participant 4).Accordingly, the value of chatbots in such work environments is limited."We use some closed software that would be neat to integrate to Slack, but which cannot be done.If it would be possible, the value of integrations would be higher" (Participant 26).
Viewpoint 5 -as spammy and process-enforcing burden The fifth viewpoint represents a drawback from using chatbots to receive messages from third-party systems.This group of employees shares the feeling that such integrations lead to information overload: "I can't work when I'm bombarded by everything that is happening around me. Important messages are already conveyed through phone or in person.If there is a real issue, people will notice" (Participant 14).At the same time, employees point out the importance of a proper configuration of chatbots to keep employees engaged in team channels: "I hate getting automated messages as they end up in spamming the whole channels and no one reacts to updates anymore" (Participant 27).Further differences in viewpoints become apparent in how employees perceive the introduction of processorientation within social information systems.One standpoint is shaped by perceptions of employees that suffer from a reduced degree of autonomy, since chatbots are "another way for people to leave a paper trail which you have to follow" (Participant 14).This is heavily in contrast to other participants from other organizational settings: "At least in our company, all the integrations are complementary, and employees are not enforced to use it.
The ones that see a benefit in it are using it, the other ones can do the same stuff with proprietary dedicated applications" (Participant 3).Lastly, participants explain that the perception of information overload depends on the job profile and employment type: "One issue is that part-time employees are not interested in getting the information about a certain project on the days they don't work for this project" (Participant 25).

Discussion and implications
Our results show higher-level affordances that emerge for members of group channels in which the identified 14 CON-07 The presented information lacks graphical and visual richness.
CON-09 Information is concealed after I sent the message.
AFF-12 Having messages processed and enriched with additional information.
AFF-13 Having messages processed and replaced.
AFF-05 Setting and getting reminders within channels.
AFF-07 Setting and getting nudges/ triggers to action and possibilities to resolve it within the channel.
CON-08 They introduce process-orientation and reduce my autonomy.
CON-05 Repetitive information since I often already know the information from alternative sources such as notifications.
AFF-11 Adding gatekeepers that validate access to functions of third-party systems.
AFF-14 Having messages processed and visually enriched with user interface elements.
AFF-03 Receiving aggregated information from third-party systems within channels.
CON-04 They lead to information overload.
AFF-06 Setting and getting nudges/ triggers to action within channels.
Fig. 14 Idealized Q-sort for viewpoint 5 -spammy and process-enforcing burden How affordances of chatbots cross the chasm between social and traditional enterprise systems lower-level affordances are actualized.Grounded in the emergence of higher-level affordances, we now discuss broader implications of our insights.
Crossing the chasm: chatbots augment social information systems with affordances of traditional enterprise systems Figure 15 illustrates how the identified higher-level affordances of chatbots within enterprise messengers enable organizations (1) to facilitate alignment by integrating information (e.g., by receiving messages that consolidate information flows), (2) to provide control mechanisms (e.g., by getting and setting triggers that enforce discipline), (3) to enable interoperability (e.g., by querying and invoking functionality in order to unify access to third-party systems), and (4) to increase efficiency (e.g., by enriching messages to relieving employees from repetitive work).In turn, these four dimensions (i.e., alignment, control, interoperability, efficiency) are well-known affordances of traditional enterprise systems (Mettler and Winter 2016).We therefore argue that chatbots augment social information systems of organizations (e.g., enterprise messengers such as Slack and Microsoft Teams) with affordances of traditional  enterprise systems.This is achieved by enabling the linkage of social interactions within enterprise messengers with thirdparty systems and business processes.Hence, chatbots can be seen as valuable to cross the chasm between traditional enterprise systems and social information systems.
Triangulating this insight with our results from the preliminary study in which we crawled the full list of publicly available Slack Apps and Integrations enables a discussion of broader implications.Figure 16 shows the number of Slack Apps and Integrations (and their absolute growth) per category.In particular, the categories related to communication and coordination, human resources (HR), and project management have grown tremendously over the past two years, which may not only affect the corresponding enterprise systems, but also the corresponding research streams.However, this also applies to categories such as marketing, distribution and customer support, which doubled in the number of integrations with third-party enterprise systems.

Implications for theory
Augmenting social information systems with affordances of enterprise systems contrasts prior research that highlights traditional enterprise systems that are enhanced with social features.For example, social features are added to business process management (BPM) systems (Bruno et al. 2011;Schmidt and Nurcan 2009), business intelligence (BI) software (Alpar et al. 2015), enterprise resource planning (ERP) systems (Shankararaman and Kit Lum 2013), and inter-organizational systems such as supply chain management (SCM) software (Gonzalez 2013;Steinhueser et al. 2015).In contrast, our research puts social information systems at the focal point (e.g., Slack and Microsoft Teams) and explains how chatbots augment these social information systems with affordances of traditional enterprise systems.Therewith, we contribute a novel perspective on the integration and entanglement of social and enterprise systems that has four essential implications for theory.
First, crossing the chasm between social and traditional enterprise systems has broader implications that extend the discourse on paradoxical tensions (Ciriello et al. 2018b;Smith et al. 2017).Namely, we offer a novel perspective on how organizations may balance novel digital with traditional systems, flexibility and malleability with stability and control, exploration with exploitation, and agility with discipline approaches.More specifically, our results show how novel digital technologies can be combined with traditional enterprise systems (Seddon et al. 2010;Sedera and Lokuge 2017;Sedera et al. 2016).This is particularly relevant, since organizations are moving away from monolithic enterprise systems into portfolios of interlinked information systems and digital platforms, which provide them with an "ecosystem of providers and suppliers of tools, techniques, and practices, beyond the conventional boundaries of traditional corporate IT" (Harris et al. 2012;Sedera et al. 2016, p. 367;Yoo et al. 2012).Further, our results point out that enterprise messengers as social information systems are not limited to their well-known characteristics of flexibility and malleability (Richter and Riemer 2013;Schmitz et al. 2016).In fact, chatbots can help organizations in their digital and distributed innovation endeavors which demand for carefully balancing flexibility and malleability with stability and control (Ciriello et al. 2018a;Tilson et al. 2010;Yoo et al. 2012).In a broader perspective, this may enable organizations to balance their exploration (innovation) and exploitation (efficiency) activities, thus, to improve their organizational ambidexterity (Andriopoulos and Lewis 2009;March 1991;Tushman and O Reilly 1996).Finally, agile software development approaches are characterized by self-organizing and cross-functional teams that rely on rapid feedback and change to continuously design, improveme, and test software (Conboy 2009;McHugh et al. 2011;Tripp et al. 2016;Wang et al. 2012).However, a central challenge of agile teams is to find the right degree of formalization and coordination within project teams (Strode et al. 2012) and between self-managed teams (Ingvaldsen and Rolfsen 2012).In particular, research is needed on how to scale agility and balance agility with discipline and plan-driven approaches (Boehm and Turner 2003;Dingsøyr et al. 2018;Gerster et al. 2018).Our results show how agile teams adopt enterprise messengers in practice and reveal that for some employees chatbots act as a central hub to coordinate human and machine work (Viewpoint 2), while for others they become a process-enforcing burden (Viewpoint 5).
Second, our results have implications for research on distributed and virtual work.Namely, prior research on distributed (Cummings et al. 2009;Srikanth and Puranam 2011;Vlaar et al. 2008) and virtual work (Bailey et al. 2012;Griffith et al. 2003;Jarvenpaa and Leidner 1999;Maznevski and Chudoba 2000) emphasizes the growing relevance of digital technologies to overcome the challenge of spatial and temporal distances.Our results illustrate novel work practices that go beyond human-tohuman collaboration and include machine-to-human as well as human-to-machine collaboration.The identified affordances may contribute to impede the problems faced in distributed and virtual work.Namely, prior research suggests the separation of work in distributed teams impedes the ability of employees to communicate effectively (Meyer et al. 2015).Cramton (2001) distinguishes five types of mutual knowledge problem that distributed teams face: failure to communicate and retain contextual information, unevenly distributed information, difficulty communicating and understanding the salience of information, differences in speed of access to information, and difficulty interpreting the meaning of silence.Identified higher-level affordances such as 'consolidating information flows', 'increasing visibility and ambient awareness', 'facilitating feedback as reactions and discussions', 'ensuring information flows through uncoupling', and 'unifying access to third-party systems' suggest that chatbots may contribute to impede these problems.Furthermore, distributed teams are known to face trust issues (Jarvenpaa and Leidner 1999;Newell et al. 2007).The identified higher-level affordances such as 'increasing visibility and ambient awareness', 'facilitating feedback as reactions and discussions', and 'fostering team cohesion' suggest that chatbots may also contribute to impede trust issues in distributed teams.
Third, our results contribute to ongoing discourse on automation of work and the interplay between humans and machines (vom Brocke et al. 2018).We do this by pointing out higher-level affordances of chatbots that are characterized by their potentials for task automation (e.g., consolidating information flows, ensuring information flows through uncoupling, and relieving employees from repetitive work).Anchored in the principle of egalitarianism within social information systems, each member can add and use chatbots in the context of their conversational threads.As such, the principle of social production in social information systems goes beyond traditional user-generated content and includes the co-creation of automated information and workflows within shared conversational threads.Hence, we demonstrate how chatbots are a powerful instrument to enable organizational automation from bottom-up (rather than topdown).This is relevant, because automation is a key pillar of the current discourse on future work, which is increasingly performed by machines (vom Brocke et al. 2018).In this context, prior research has discussed how big data analytics technologies become generative digital technologies that enable service innovation (Lehrer et al. 2018), how hybrid intelligent decision support systems should be designed (Dellermann et al. 2018), and how the underlying logic of work is changing (Tumbas et al. 2018).In addition, we contribute a novel perspective on the interplay of people and machines that extends the ongoing discourse on hybrid arrangements of work.We do this by highlighting how social information systems (e.g., Slack and Microsoft Teams) are key organizational resources to enable bottom-up driven automation of communication, coordination and collaboration.
Fourth, our results have implications for performance feedback literature.Both academic literature (Levy et al. 2017;Schleicher et al. 2018) and practice-oriented literature (Armitage and Parrey 2013;Buckingham and Goodall 2015;Cappelli and Tavis 2016) emphasizes that traditional performance management lacks to be in line with current business cycles in providing timely feedback.The identified affordances reveal how chatbots (1) enable computer-generated feedback through automated information flows, and (2) facilitate computer-mediated feedback between employees through reactions and discussions.Given this use of chatbots to facilitate timely feedback, they can be seen as a complementary alternative to computer-mediated digital feedback systems such as dedicated feedback apps (Stoeckli et al. 2019).Therewith, our findings respond to calls for research to increase our understanding of informal day-to-day feedback and to investigate technology usage for performance management (Ashford and Cummings 1983;Levy et al. 2017;Schleicher et al. 2018).For example, the chatbot in organization Beta calculates velocity measures and posts the relative movement of each project to conversational threads (see Fig. 8).Also, the companies Epsilon, Eta and Theta harness chatbots to post analytics data, reviews and ratings from app stores to the corresponding project channels.These automated feedback flows described in the present research can be interpreted as computer-generated feedback that comes from the job (Hackman and Oldham 1976) rather than from other coworkers (Hackman and Lawler 1971).These findings are in line with literature that investigates chatbots dedicated to feedback exchange (Lechler et al. 2019).However, the implications of this research are much broader.Figure 16 highlights the diversity of integrations with numerous enterprise systems (e.g., software for distribution, customer support, marketing, accounting, and design), which may be used to assess the performance and generate feedback.As such, chatbots can be seen as feedback facilitating digital technologies that facilitate self-monitoring of teams (Hermsen et al. 2016).This, in turn, is particularly interesting in the light of agile practices that institutionalize feedback (McHugh et al. 2011;Tripp et al. 2016).

Implications for practice
Chatbots provide value potentials for organizations to improve internal workflows and collaboration through facilitating and enabling to harness enterprise systems affordances (i.e., facilitating alignment, providing control, enabling interoperability, and increasing efficiency) in the context of social information systems (e.g., Slack).
This has three key implications for practitioners in the light of an increasingly digital world that demands for distributed innovation.First of all, firms should leverage the social features of their (existing) social information systems to integrate their enterprise systems through chatbots rather than enrich each traditional enterprise system with social features.Second, our findings underline the relevance of opening up traditional enterprise systems through the conscious design of corresponding interfaces (e.g., API's) to allow bridging the world of traditional enterprise systems and social information systems.This in turn, allows to harness our identified affordances.Third, organizations should be aware that while traditional enterprise systems were usually top-down driven, social information systems are bottom-up driven.While chatbots do bridge this chasm, this may have positive and negative consequences.On the one hand, employees can harness chatbots for bottom-up driven automation.On the other hand, employees may integrate traditional enterprise without awareness of its consequences (e.g., introducing a chatbot that posts feedback in the form of metrics in group channels should be well thought-out, since it has severe consequences on job satisfaction and motivation).

Affordance-theoretical peculiarities of chatbots
Interpreting the results through the affordance theory reveals further characteristics of chatbots in general.

Affordance-related dependencies between individual actors
The perception of affordances depends on the available information (Bernhard et al. 2013).Markus and Silver (2008), for example, emphasize the symbolic expressions that are communicated by IT artifacts to a potential user to reveal meaning and potential uses.In this regard, chatbots have a major disadvantage, because their symbolic expressions are rare (especially for chatbots of Category 3 and Category 4).First, the information on available chatbots is hidden and has to be polled by the user through interaction with the chatbot.Second, for a given chatbot, our interviewees indicated struggles with recognizing the available possibilities for action.Interestingly, our results reveal affordances of chatbots with the characteristics that their actualization within a shared conversational thread leads to effects that are disclosed to other members of the channel.This either occurs 1) when the outcome of the actualization is posted into the shared conversational thread (e.g., creating video conference by invoking functionality and making invocation visible as described in Affordance 3.4), and 2) when the text entered by the actualizing user is disclosed in the conversational thread (e.g., "/poll 'Do you like this article so far?' 'Yes' 'No').Therewith, the information about the availability of the actualized action potential becomes visible to others.From an affordance point of view, this indicates that the actualization of lower-level affordances by User 1 may lead to its perception by User 2 (see Fig. 17).
Emergence of individualized, collective, and shared affordances While technical users may develop and install custom chatbots, most users may simply install publicly available chatbots (e.g., from the Slack App Directory).However, in both cases, adding a chatbot to a conversational thread leads to the emergence of new affordances for the other members of this channel.The channel in which a chatbot is added to and in which the corresponding affordances are eventually actualized is socially determined by the actualizing user.Thus, the same IT artifact can be put into different social contexts by the appropriating user and, thus, different kinds of affordances may emerge, e.g., individualized, collective or shared affordances (Paul M Leonardi 2013) as well as constraints.For example, a chatbot to capture a Trello task within Slack (Affordance 3.1) may be used individually, thus, leading to an individualized affordance.However, a user may put the same chatbot to a shared conversational thread.Shared affordances describe the similar use of the features of an IT artifact by all considered actors (Paul M Leonardi 2013) and emerge "as soon as several individuals know a function" (Balci et al. 2014, p. 8).Collective affordances are collectively created by all actors of a group allowing the group to achieve something, which otherwise would not be possible (Balci et al. 2014;Paul M Leonardi 2013).As such, the characteristic described above (i.e., visibility of the actualization by one user for other users) can be seen to facilitate shared as well as collective affordances.However, our results show how these higher-level affordances may not only be enabling, but also constraining, e.g., if members of a shared conversational thread do not share the same goals.This is where we see the biggest value and likewise the biggest challenge arising from chatbots that are integrated in shared conversational threads (e.g., by facilitating reactions, discussions, ambient awareness).
High actualization effort Prior research suggests that the actualization and, accordingly, the realization of effects, is influenced by the actualization effort and the expected outcome (Bernhard et al. 2013).In our research, the perceived expected outcome depends on how other members of the channel act.In fact, our results reveal constraints, such as information overload.At the same time, the perceived expected outcome can also change over time.Affordances have to be seen in the context of the alternatives, because employees constantly compare affordances (Glowalla et al. 2014).Thus, our results indicate, that the actualization effort has to be in balance with the perceived expected outcome to facilitate the actualization of the respective affordances and thus the successful use of the IT artifact.

Implications for theory
Through backing our research endeavor with the affordance theory, we contribute three important theoretical implications to the extant body of knowledge.First, though several authors focus on the interrelationship of affordances (e.g., through an affordances dependency diagram (Strong et al. 2014)), it remains unclear how the actualization of affordances affects the context-specific perception of affordances and constraints of other users (Bloomfield et al. 2010;Strong et al. 2014).Against this backdrop, our research illuminates how the actualization of one user may facilitate the emergence and the consecutive perception by another user.In contrast, prior research has shown dependencies between individual affordances (Glowalla et al. 2014) and dependencies between different unit Fig. 17 The actualization of an affordance by one user may facilitate its perception by another user of analyses, e.g., individual and organizational affordances (Strong et al. 2014).Second, drawing on the concept of individualized, shared, and collective affordances of Leonardi (2013), we detail how the use of chatbots in diverse social contexts may lead to the emergence of either individualized, shared, and collective affordances through affecting the technoorganizational context.Third, following the thinking of Bygstad et al. (2016) the manipulation of the techno-organization context (i.e., entangled networks of human, social and technical objects) through the actualization of affordances is supposed to affect not only the emergence, perception, and actualization of affordances but also the emergence of constraints.Through eliciting the constraints of the use of chatbots, we contribute empirical insights on how the actualization of an affordance affects the technoorganizational context and, in turn, the emergence, perception, and actualization of affordances.

Implications for practice
These findings have implications for organizations that design instance messengers and chatbots as well as for organizations that use chatbots.First, designers of instant messengers need to acknowledge that, given a chatbot, members of group channels perceive different higher-level affordances and constraints (see Fig. 8 within results).Our results suggest that offering options to individually mute channels does not solve this issue, because the perceived constraints (e.g., message postings leading to information overflow) are not in line with the perceived relevance of human conversations in group channels (e.g., muting its team channel may not be an option for its manager, however, a chatbot that floods the corresponding channel with operational details may be perceived as constraining).Furthermore, providing chatbot developers with graphical user interface elements may help to reduce the relatively high actualization effort.Second, designers of chatbots should consider the affordance-related dependencies between individual users to counter the disadvantage of rare symbolic expressions (while preventing information overflow).Specifically, we have shown that the visibility of the actualization of an affordance by one user may lead to its perception by other users (and hence, may foster adoption), or also to the emergence of constraints such as information overflow.Furthermore, designers of chatbots should try to foster affordance actualization by reducing the relatively high actualization effort through the exploitation of graphical user interface elements (e.g., reducing effort for data input through buttons).Third, the three discussed affordance-theoretical peculiarities of chatbots need to be considered by organizations that use chatbots.In particular, the social context in which chatbots are introduced (i.e., the group channel) influence to a large extend what higher-level affordances and constraints emerge.Before introducing chatbots, employees should consciously consider their set of group channels and the corresponding needs of group members.

Conclusion and future research
In summary, we shed light on the previously unexplored and novel phenomenon of chatbots in the context of enterprise messengers by pointing out 14 lower-level affordances and constraints along four categories: receiving messages, getting and setting triggers, executing queries and invocations, and enriching messages.Our results further reveal patterns in the form of similarities and differences in how employees weigh the perception of these identified affordances against the perception of constraints.Perceptional similarities include that employees perceive affordances related to receiving messages from third-party systems as higher compared to all affordances and that the relevance of chatbots is assessed as highest in group channels that are related to projects at work.Perceptional differences among employees are highlighted along five different factors that show that chatbots within enterprise messengers are viewed (1) as operational assistants, (2) as central information hubs, (3) as difficult to use black boxes and worse alternatives to dedicated tools, (4) as shadow IT in restrictive and closed legacy environments, and (5) as spammy and process-enforcing burden.Emergent from the actualization journeys of the lower-level affordances and constraints, we elaborate higher level affordances, such as consolidating communication (e.g., have messages from multiple people and third-party systems in a chronologic thread) and automating information and work flows (e.g., ensure discipline, relieve employees, shorten feedback cycles).
We contribute to the body of social information systems by elucidating how chatbots augment social information systems with the affordances of traditional enterprise systems proposed by Mettler and Winter (2016).In a broader perspective of paradoxical tensions, we contribute a novel perspective on how to balance novel digital with traditional systems, flexibility and malleability with stability and control, exploration with exploitation, and agility with discipline.Further, we contribute to the body of affordance literature by discussing affordancetheoretical peculiarities of chatbots, e.g., how the actualization of an affordance by one user may affect the affordance perception of other users (Fig. 8).At last, the paper at hand informs practitioners about affordances as well as constraints of enterprise messengers such as Slack and Microsoft Teams as well as by discussing implications for practice within the dedicated sections.
Nevertheless, our findings are subject to limitations.Due to the qualitative and interpretive research design, exhaustiveness cannot be guaranteed, and we cannot provide a verified theory.Therefore, future quantitative studies can further enrich our results in drawing on them and critically reflecting and verifying them.While our research considered multiple enterprise messengers, the focus was on one tool, that is Slack, within different organizational contexts.This may lead to biases in the identified affordances and constraints.On the one hand, other tools may simply have different material properties leading to the emergence of different affordances and constraints.On the other hand, the selection of the tool may influence the sample of users in that they have special characteristics.Finally, our viewees were mainly based in Germany and Switzerland, which might affect our research findings.As counter measure, we conducted a preliminary analysis of the Slack directory, and triangulated our findings with material provided by our interviews.Anchored in the split of the Glaserian school (Glaser 1992) from the Straussian school of grounded theory (Corbin and Strauss 1990;Strauss and Corbin 1990), the following question arises: "At what point does the researcher's intervention or techniques force, instead of allow for, emergence?"(Walker and Myrick 2006, p. 553).By following Strauss and Corbin (1990), we strived to "never impose anything on the data" (p.94) and, at the same time, applying their principle of theoretical sensitivity that encourages the use of analytic tools such as the affordance theory in order to allow for emergence of insights.Still, the use of analytical tools such as existing theory goes along with the risk to force the data in preconceived ways, thus, potentially leading to confirmation-bias.
We see four avenues for future research.First, we acknowledge the fruitful avenue for design-oriented research in the context of chatbots.Our research illuminating the affordances emergence of chatbots in the enterprise context as well as the discussed affordance-related peculiarities could be used as a starting point for eliciting and developing design propositions and a design theory for chatbots.In particular, it would be interesting how design decisions for chatbots have to be depended on the techno-organizational context to reduce the effort needed to actualize the affordances of chatbots and how these propositions need to take contextual conditions into account under which constraints emerge from chatbots in shared conversational threads.
Second, as enterprise messengers such as Slack become available for a broader audience of users (aside from software developers), future research can investigate how chatbots can be used to assess the work conducted by employees and to provide timely automated feedback.Furthermore, prior research has shown that the visibility and transparency on the progress of tasks (e.g., through agile practices such as daily stand-ups) have self-motivating effects (McHugh et al. 2011).Future research should clarify if this applies as well to feedback provided by chatbots (e.g., the chatbots in Fig. 5 discloses velocity metrics).
Third, as we selected Slack as representative enterprise messenger platform, future research is needed to confirm and extend our research findings using additional platforms (e.g., Microsoft Teams) and organizational contexts.Specifically, different quantitative approaches can be adopted for verification.
Fourth, future research should investigate further domainspecific enterprise systems that benefit from an integration in social information systems.For example, research on product development is emphasizing the increasing need for collaboration, knowledge exchange and communication within and across geographically distributed teams and suggests that social software applications can support tasks across various phases of the new product development process (Bertoni and Chirumalla 2011;Ming et al. 2008;Roch and Mosconi 2016;Rohmann et al. 2014).Chatbots may be harnessed to integrate domain-specific enterprise systems, e.g., Computer Aided Design (CAD) systems and Product Lifecycle Management (PLM) systems into social information systems.
Appendix.Heatmaps of Cards Sorting Values from Phase 2 and Phase 3

Fig. 6
Fig. 6 Q-sort survey tool used to conduct the Q-methodology study

Fig. 7
Fig.7Contextual emergence of lower-level and higher-level affordances and constraints "If the channel is relatively important, [...], then you cannot mute it" (Interview #5).Oftentimes, "it depends on your job role, personally I have muted many of the channels in which chatbots regularly post messages except for the project [channels] where I'm responsible for.I have two projects where I as the architect have the technical responsibility and do have to know what my software developers commit and what bug reports are created" (Interview #5).

Fig. 10
Fig. 10 Idealized Q-sort for viewpoint 1 -operational assistant information since I use these systems in my everyday work.

Fig. 12
Fig. 12 Idealized Q-sort for viewpoint 3 -difficult to use black box & worse than dedicated tools

Fig. 13
Fig. 13 Idealized Q-sort for viewpoint 4 -shadow IT in a restrictive and closed legacy environment

Fig. 15
Fig. 15 Chatbots augment social information systems with affordances of traditional enterprise systems

Fig. 16
Fig. 16 Development of slack apps and integrations from 2016 to 2018 (sorted by absolute growth)

Fig. 18
Fig. 18 Results of physical card sorting from phase 2

Table 1
List of interviews (#1 to #29) with details on interview partners and the context of chatbot usage E.Stoeckli et al.

Table 2
Affordances related to receiving information and outcomes of automated workflowsContext (Alpha, Beta, Delta, Epsilon, Eta).In software developing teams, chatbots were used to post status updates from version control systems (e.g., Git), issue tracking systems (e.g., Jira), build and continuous integration systems (e.g., TeamCity).Outcome.Status update (e.g., source code was committed, issue was resolved, new version was deployed) is automatically posted to a team or dedicated separate channel.To better understand individual test users, chatbots were used to trace a customer along a buying process.Outcome.Each step of a customers' journey is posted to a Slack channel.Context (Beta).Fetching information from various sources (e.g., Kanban board) and preparing a structured meeting agenda for status meetings is a repetitive task that is done by a chatbot.Outcome.Automatically generated meeting agenda is posted to project channel.Gathering lunch menus of nearby cafeterias is done by a chatbot.Outcome.Automatically fetched meals are posted to channel.Context (Beta).Velocity measure as amount of functionality scrum teams deliver is repeatedly calculated by a chatbot.Outcome.An overview of the relative movement of each project is posted to a channel.Analytics data and reviews/ratings from app stores are fetched by chatbots.Outcome.This feedback to the own product or service is posted to Slack (either immediately or aggregated).

Table 3
Affordances related to getting and setting triggers and reminders

Table 4
Affordances related to queries and invocations within Slack channels Instead of creating video conference (e.g., join.me,appear.in)followed by sharing access details, bots are used to achieve both in one step.Outcome.Available commands to create and share access to a video conference within the corresponding channel.Context (Beta).Instead of initiating software deployments from the isolated console, chatbots are harnessed to initiate deployments within Slack channels (e.g., the corresponding project channel).Outcome.Available commands to initiate deployment within Slack channels, which makes it is visible and traceable.Adding gatekeepers (AFF-11) Context (Beta).Due to separation of duties, developers were separated from production environments with sensitive data and glued back together using chatbots.Outcome.Authorized legal responsible uses chatbot to confirm and trigger the provisioning of software to customer environments.
every word, you found [someone posting] a gif, which has led to whole conversations composed of GIFs, but this is not useful, just funny, what in turn is fine as well" (Interview #11).

Table 5
Affordances related to the enrichment of messages Score for the statement is higher than in all other factors z-Score for the statement is lower than in all other factors