<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Applications of AI in sociotechnical work systems: Fundamental change or just a type of partial automation?</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Steven</forename><surname>Alter</surname></persName>
							<email>alter@usfca.edu</email>
							<affiliation key="aff0">
								<orgName type="institution">University of San Francisco</orgName>
								<address>
									<addrLine>2130 Fulton Street</addrLine>
									<postCode>94117</postCode>
									<settlement>San Francisco</settlement>
									<country key="US">USA</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Applications of AI in sociotechnical work systems: Fundamental change or just a type of partial automation?</title>
					</analytic>
					<monogr>
						<idno type="ISSN">1613-0073</idno>
					</monogr>
					<idno type="MD5">804B380EE96F2A489543F4C8E2DFB4D9</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2025-04-23T17:45+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Sociotechnical system</term>
					<term>artificial intelligence</term>
					<term>work system</term>
					<term>automation 1</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>This paper summarizes my keynote for the 10 th International Conference on Sociotechnical Perspectives in IS (STPIS '24), which I delivered via Zoom on16 August 2024. The keynote used a work system perspective to consider whether applications of AI in sociotechnical systems represent a fundamental change from previous applications of IT or whether they are viewed best as just a type of partial automation in that context. This paper uses the keynote's colloquial tone but it expresses serious concern for describing and evaluating AI applications based on ideas that can be used in real world situations. This paper applies a work system perspective (WSP) that evolved over several decades but it emphasizes recent extensions of WSP. The small number of papers cited here provide links to many related papers by many authors.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Making sense of AI applications in STSs requires clear concepts for describing systems and for describing the extent of machine intelligence in specific situations. It also requires examples to illustrate how to think about AI in the context of a specific sociotechnical work system. This paper tries to fill in some of the blanks.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">Basic concepts for describing sociotechnical work systems</head><p>These ideas about work systems have been published many times but are repeated here to provide an organized approach for talking about AI usage by sociotechnical systems.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Work:</head><p>The use of resources to produce product/services for others or for oneself.</p><p>Work system: A system in which human participants and/or machines use resources to produce product/services for internal and/or external customers or for themselves. The work in work systems may be structured to varying degrees, e.g., unstructured (designing a unique advertisement), semi-structured (performing typical medical diagnosis), workflows (processing invoice payments), or highly structured (manufacturing semiconductors or pharmaceuticals). The most important distinction in describing special cases of work system is the difference between a sociotechnical work system in which human participants perform some of the activities vs. totally automated work system where all activities are performed by machines and where the slot for participants is blank. Information systems, projects, service systems, self-service systems, and some supply chains (interorganizational work systems) are important special cases. For example, software development projects are work systems designed to produce specific product/services and then go out of existence.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Work system method (WSM).</head><p>Many of the ideas in WSM were developed with the help of MBA and Executive MBA students who used successive versions of a work system-oriented analysis outline to produce over 700 management briefings related to work systems in their organizations between 2003 and 2017 (e.g., <ref type="bibr" target="#b2">[3]</ref>). The same fundamental approach was organized around the same six steps even when different versions of WSM were used.</p><p>1. Identify the smallest work system that has the problem or opportunity at hand. 2. Summarize the "as-is" work system using a work system snapshot, a stylized onepage summary that that identifies six work system elements 3. Evaluate the work system's operation using perceived strengths and weaknesses, metrics, key incidents, social relations, and other factors. 4. Drill down further as necessary using any relevant ideas, including both WSM tools and other tools and approaches that are not specifically related to work systems, e.g., BPMN, design thinking, and Six Sigma methods. 5. Propose changes by producing a work system snapshot of a proposed "to be" work system that should perform well. 6. Describe likely performance improvements and explain why the effort of creating the new work system or making the proposed changes seems justified.</p><p>That set of generic steps provides guidance for analyzing almost any work system. Detailed analysis of a work system requires ideas that support deeper understandings of how a work system operates and how work systems change over time.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Work system theory (WST).</head><p>This set of ideas forms the basis of WSM. Figure <ref type="figure">2</ref> shows WST's three components: the definition of work system, the work system framework, and the work system life cycle model <ref type="bibr" target="#b3">[4]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Definition of work system.</head><p>A system in which human participants and/or machines perform work (processes and activities) using information, technology, and other resources to produce specific product/services for internal and/or external customers and/ or for themselves.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Work System Framework Work System Life Cycle Model (WSLC)</head><p>Figure <ref type="figure">2</ref>: Three components of work system theory</p><p>The work system framework identifies elements of a basic understanding of a work system's form, function, and environment during a period when it retains its identity even though incremental changes may occur, such as minor personnel substitutions or technology upgrades. The work system life cycle model summarizes the evolution of a work system, which combines planned change through projects and unplanned change through adaptations and workarounds. Life cycle phases may be performed in different ways. Typical activities and responsibilities (e.g., designing, debugging, training, etc.) associated with specific phases apply for different development approaches such as waterfall, agile, prototyping, and use of off-the-shelf applications even when phases overlap or iterate.</p><p>Work system perspective (WSP). This involves more than just thinking about a situation as though it involves a work system. WST is the core of WSP, which also includes an evolving series of extensions that start with work system characteristics, evaluation criteria, and phenomena that apply to work systems as a whole or to work system elements. Separate papers have discussed extensions such as a service value chain framework, a theory of workarounds, a system interaction theory, the idea of facets of work, an agent responsibility framework, an IS usage theory, service system axioms, a proposed systems analysis toolkit, and so on. Several of those extensions are discussed later in relation to STSs and AI.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">Basic concepts for describing automation and AI applications</head><p>Automation. This is execution of tasks by machines. Th term automation is used in different senses, e.g., automation of manufacturing includes both human use of devices to perform specific tasks in sociotechnical manufacturing systems and manufacturing that is performed completely by machines. Thus, work performed by people with the help of computers is partially automated. Tasks performed by computers may have been performed partially or entirely by people in the past (e.g., summarizing a document), but also may be impractical or impossible for people to perform manually (e.g., second-to-second control of a rocket).</p><p>Algorithm. An algorithm is a detailed method for achieving specified goals within stated or unstated constraints by applying specific resources such as data inputs. It is often unclear whether an algorithm is an application of AI. For example, assume that vendors offer seemingly reliable algorithms for deciding which applicants should be accepted by universities, identifying individuals using biometric features, or selecting defective items on a conveyor belt. Assume that potential users can test the algorithms carefully before deciding to use them. How would they know whether the algorithms were the product of AI if the vendor provided no evidence of how the algorithm was produced? And why would that matter anyway if the goal was to perform a task efficiently, reliably, and ethically?</p><p>Agent. In the context of work systems, an agent is a human or nonhuman entity that performs tasks delegated by another entity (which may be human or nonhuman) and can sense, decide, and act autonomously. Reactive agents take immediate action based on environmental stimuli. Proactive agents take initiative and may plan actions in advance.</p><p>Digital agent. Digital agents operate by executing algorithms encoded in software. A digital agent can be viewed as a work system because it performs work using information, technologies, and other resources to produce products/services for its direct customers, which may be human or nonhuman entities.</p><p>AI usage by a work system. This is a work system's usage of a digital agent created by using AI-related techniques. Not proposing a definition of AI is actually beneficial here because it avoids unnecessary constraints and focuses on what matters more in STS world, i.e., how an STS actually uses and maintains a digital agent to achieve beneficial purposes.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">A hypothetical hiring system as an illustrative example</head><p>A hypothetical example illustrates how AI applications fit into STSs. As summarized in Table </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Major activities and processes</head><p>• AlgoComm publicizes the position.</p><p>• Applicants submit resumes to AlgoComm.</p><p>• AlgoRank selects shortlisted applicants and sends the list to the hiring manager. • Hiring manager decides who to interview.</p><p>• AlgoComm sets up interviews.</p><p>• Interviewers perform interviews and provide comments about applicants. • AlgoRank evaluates candidates.</p><p>• Hiring manager makes hiring decision.</p><p>• AlgoComm notifies applicants.</p><p>• Applicant accepts or rejects job offer.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Participants Information Technology</head><p>• Hiring manager</p><formula xml:id="formula_0">• Applicants • Interviewers • Job requisition • Job description • Advertisements • Job applications • Cover letters • Applicant resumes • Applicant short list • Information and impressions from the interviews • Job offers • Rejection letters • AlgoComm • AlgoRank • Office software • Internet</formula><p>The work system snapshot in Table <ref type="table" target="#tab_0">1</ref> shows that the hiring system involves much more than the two digital agents. Aspects of the hiring system are automated, but the hiring system remains an STS that relies heavily on people. That is not the only possibility, however. If XYZ Corp wants to hire easily replaced workers from a large pool of applicants it might move toward a totally automated system where some version of AlgoComm handles applicant communications and some version of AlgoRank decides who to hire. The work system and digital agents would still be implemented and maintained by people, but the totally automated hiring system would no longer be an STS regardless of whether the digital agents are mundane IT applications or are AI-based.</p><p>Figure <ref type="figure" target="#fig_1">3</ref> shows how the work system life cycle model can be used to describe this work system's ongoing evolution. The main point is that the same concerns apply regardless of whether a new or improved STS uses mundane IT applications or AI-based digital agents. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Roles of digital agents, facets of work, and an agent responsibility framework</head><p>A deeper understanding of a sociotechnical work system that uses AI-based digital agents calls for additional ideas. This section identifies different roles that digital agents might play, different facets of work that they might support, and an agent responsibility framework that can help in identifying important combinations of roles and facets.</p><p>Roles of digital agents. Digital agents can perform many different roles for an STS. The following generic roles are organized along a spectrum from the lowest to the highest direct involvement in the execution of activities within a different hiring STS:</p><p>• Monitoring the work system might occur with no direct involvement in the work system's operation and might provide information for management processes or assure worker safety, but also might support micromanagement.</p><p>• Providing information might involve paper documents, PDFs, computer-based reports, computerized datasets, or even voice recordings or videos.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Begin creation or revision of the work system</head><p>Develop or revise the AI algorithm and other resources needed to improve the work system, including the AI algorithm Implement the revised work system including the (revised) AI algorithm</p><p>Operate and maintain the work system, including the (revised) AI algorithm Don't forget about adaptations and workarounds</p><p>• Providing capabilities enables work system participants through capabilities for tasks such as analyzing information or creating and analyzing models. • Controlling activities in the work system might involve displaying information, providing immediate feedback, enforcing business rules, producing alarms when conditions go out of bounds, or notifying managers. • Coproducing activities involves achieving results through complementary responsibilities of people and digital agents. Coproduction might occur though different modes of engagement, as explained later. • Executing activities occurs when a digital agent that is an automated work system component performs a work system activity or when a work system activity is delegated completely to a digital agent external to the work system.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Facets of Work.</head><p>Most activities in work systems involve one or more common types of activities such as making decisions, communicating, and processing information. Activity components can be viewed as facets of work if they satisfy criteria: they apply to both sociotechnical and totally automated work systems; they are associated with many concepts that are useful for analyzing system-related situations; they are associated with evaluation criteria and typical design trade-offs; they have sub-facets that can be discussed; they bring open-ended questions that are useful for starting conversations. Table <ref type="table" target="#tab_1">2</ref> shows 18 facets of work that are identified in <ref type="bibr" target="#b5">[6]</ref>. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Agent Responsibility Framework.</head><p>A digital agent's responsibilities in relation to an STS that it supports can be described in terms of a two-dimensional agent-responsibility (AR) framework <ref type="bibr" target="#b6">[7]</ref> shown in Figure <ref type="figure" target="#fig_2">4</ref>. The horizontal dimension is a spectrum of roles that goes from the lowest to the highest direct involvement of a digital agent in the execution of a work system's activities. The vertical dimension is different facets of work. Figure <ref type="figure" target="#fig_2">4</ref> shows only 6 of the 18 facets to help in visualizing what the AR framework means.</p><p>Combining the AR framework's two dimensions helps in pinpointing design issues, e.g., the extent to which a digital agent should have responsibilities such as monitoring decisions, providing capabilities for making decisions, or making decisions automatically. Those choices apply to just one facet of work -making decisions -but almost any digital agent role might be applied to any facet. Users of the AR framework can apply the two dimensions to identify possible areas of interest. Practicality implies that only combinations that are important for a specific work system should be considered. The same thought process would apply regardless of whether an imagined or proposed digital agent was based on AI. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>&lt;&lt;&lt; Facet of work &gt;&gt;&gt;</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Making</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6.">Smartness of devices and systems</head><p>The topic of AI calls for meaningful ideas about the smartness or intelligence of devices and systems, especially with the proliferation of hyperbole-infused terms such as smart phones, smart contracts, smart cities, smart water bottles, intelligent databases, intelligent buildings, intelligent agents, and so on. A conceptualization of smartness in <ref type="bibr" target="#b7">[8,</ref><ref type="bibr" target="#b8">9]</ref> addresses that challenge by describing the smartness of devices and systems based on two ideas: identification of different capabilities that might be smart to different extents and different degrees of smartness for any capability.</p><p>Capabilities that might be built into devices or systems can be divided into four categories. Each of those categories includes between five and seven separate capabilities that may exist independently or may be intertwined with other capabilities. Note that each of the capabilities in each of the following four groups applies to both STSs and digital agents:</p><p>• Information processing. Capture, transmit, store, retrieve, delete, manipulate, and display information (7 capabilities) The smartness built into a device or system for any of the above capabilities can be characterized along the horizontal dimension in Figure <ref type="figure" target="#fig_2">4</ref>. Most work systems with human participants operate with a nontrivial level of smartness for most of those capabilities (with the possible exception of work systems whose activities are totally routine and repetitive). In contrast, very few AI-based digital agents exhibit a high level of smartness for any of those capabilities. The design challenge of using AI-based or non AI-based digital agents to make work systems smarter involves designing digital agents whose limited smartness nonetheless enhances the smartness of a work system that uses them. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7.">Alternative modes of engagement with digital agents</head><p>A final idea is alternative modes of engagement between human STS participants and digital agents. Figure <ref type="figure" target="#fig_4">6</ref> shows that those modes of engagement can be compared in terms the degree of initiative that the STS delegates to people or machines. Both ends of the spectrum of possibilities in Figure <ref type="figure" target="#fig_4">6</ref> involve no engagement, i.e., either all activities are performed by digital agents or are performed by humans. Between those extremes, responsibilities of people or machines can be characterized as machine-in-the-loop, mixed initiative interactions, and human-in-the-loop <ref type="bibr" target="#b8">[9]</ref>. The two-headed arrows in Figure <ref type="figure" target="#fig_4">6</ref> indicate possibilities for incremental changes in one direction or another. The modes of engagement that involve interactions deserve a few comments. With human-inthe-loop the digital agent performs the most important activities autonomously, but requests confirmation or instructions from work system participants upon encountering situations requiring human judgment. With mixed initiative interactions, both digital agents and people may take the initiative. For example, a digital agent monitoring a process might issue a warning about suspicious conditions and might request a response about whether corrective action is needed. From the other side, a person might initiate an interaction to identify and explore potentially important status or history information. With machine-in the-loop, people perform the main steps and occasionally interact with digital agents to request status or performance information or suggestions related to alternatives.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="8.">Conclusion</head><p>This keynote responded to AI hyperbole by explaining how STS applications of AI can be viewed in depth as the use of digital agents. More detailed coverage of these and related ideas can be found in <ref type="bibr" target="#b8">[9]</ref>. The ideas presented here are meant as part of a practical approach for treating AI applications simply as digital agents used by STSs, ideally to enhance STS efficiency, effectiveness, and reliability while applying traditional STS values in treating STS participants and customers equitably and ethically. The incredible nature of AI-related developments in recent years deserves admiration (and a bit of fear) without imagining that AI applications should be viewed as magic.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Which AI tool are you talking about when you generalize about AI?</figDesc><graphic coords="2,121.05,85.05,351.51,176.60" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: Charting the ongoing evolution of a work system</figDesc><graphic coords="6,200.02,284.15,205.19,131.35" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 4 :</head><label>4</label><figDesc>Figure 4: Agent-responsibility framework showing six roles and six of the 18 facets of work</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 5 :</head><label>5</label><figDesc>Figure 5: Different degrees of smartness for any capability</figDesc><graphic coords="9,163.22,155.98,293.25,145.04" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 6 :</head><label>6</label><figDesc>Figure 6: Different modes of engagement between human work system participants and digital agents in sociotechnical systems</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1</head><label>1</label><figDesc>1, XYZ Corp uses an AI-based hiring application provided by an external vendor that developed AlgoComm and AlgoRank. AlgoComm provides capabilities for posting job ads, receiving applications, setting up interview appointments, and performing other applicant communication. AlgoRank ranks candidates based on job criteria and a database of job qualifications, salaries, and other data. AlgoRank might be seen as an AI application, whereas AlgoComm seems more like typical information processing even though certain parts of it apply AI technologies such as natural language processing (NLP). The vendor delivers AlgoComm and AlgoRank as software, but XYZ Corp implements AlgoComm and AlgoRank to operate as digital agents that can be viewed as work systems in their own right. Work System Snapshot of a sociotechnical hiring system<ref type="bibr" target="#b4">[5]</ref> </figDesc><table><row><cell>Customers</cell><cell>Product/services</cell></row><row><cell>• Applicants • Hiring manager • Larger organization • HR manager (who use the applications to analyze the nature of applicants)</cell><cell>• Applications (which may be used for subsequent analysis) • Job offers • Rejection letters • Hiring of the applicant</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 2</head><label>2</label><figDesc></figDesc><table><row><cell>18 Facets of work</cell><cell></cell><cell></cell></row><row><cell>Making decisions</cell><cell>Communicating</cell><cell>Providing information</cell></row><row><cell>Representing reality</cell><cell>Learning</cell><cell>Coordinating</cell></row><row><cell>Performing physical work</cell><cell>Providing service</cell><cell>Applying knowledge</cell></row><row><cell>Planning</cell><cell>Improvising</cell><cell>Performing support work</cell></row><row><cell>Creating value</cell><cell>Thinking</cell><cell>Controlling execution</cell></row><row><cell>Processing information</cell><cell>Interacting socially</cell><cell>Maintaining security.</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_2"><head>• Action in the world. Sensing</head><label></label><figDesc></figDesc><table><row><cell>, actuation, coordination, communication, control, and</cell></row><row><cell>physical action (6 capabilities)</cell></row><row><cell>• Internal regulation. Self-detection, self-monitoring, self-diagnosis, self-correction,</cell></row><row><cell>and self-organization. (5 capabilities)</cell></row><row><cell>• Knowledge acquisition. Sensing or discovering, classifying, compiling, inferring or</cell></row><row><cell>extrapolating from examples, inferring or extrapolating from abstractions, testing, and</cell></row><row><cell>evaluating. (7 capabilities)</cell></row></table></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Validating Generalizations about AI and Its Uses</title>
		<author>
			<persName><forename type="first">S</forename><surname>Alter</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of HICSS</title>
				<meeting>HICSS</meeting>
		<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<title level="m" type="main">Navigating the jagged technological frontier: field experimental evidence of the effects of AI on knowledge worker productivity and quality</title>
		<author>
			<persName><forename type="first">F</forename><surname>Dell'acqua</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2023">2023</date>
			<biblScope unit="page" from="24" to="37" />
		</imprint>
		<respStmt>
			<orgName>Harvard Business School</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">Technology and Operations Mgt. Unit Working Paper</note>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Systems analysis for everyone else: Empowering business professionals through a systems analysis method that fits their needs</title>
		<author>
			<persName><forename type="first">D</forename><surname>Truex</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of ECIS</title>
				<meeting>ECIS</meeting>
		<imprint>
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Work System Theory: Overview of Core Concepts, Extensions, and Challenges for the Future</title>
		<author>
			<persName><surname>Alter</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of the Association for Information Systems</title>
		<imprint>
			<biblScope unit="volume">14</biblScope>
			<biblScope unit="page" from="72" to="121" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Understanding artificial intelligence in the context of usage: Contributions and smartness of algorithmic capabilities in work systems</title>
		<author>
			<persName><forename type="first">S</forename><surname>Alter</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International Journal of Information Management</title>
		<imprint>
			<biblScope unit="volume">67</biblScope>
			<biblScope unit="page" from="1" to="10" />
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Facets of Work: Enriching the Description, Analysis, Design, and Evaluation of Systems in Organizations</title>
		<author>
			<persName><forename type="first">S</forename><surname>Alter</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Communications of the Association for Information Systems</title>
		<imprint>
			<biblScope unit="volume">49</biblScope>
			<biblScope unit="page" from="321" to="354" />
			<date type="published" when="2021">2021</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Responsibility modeling for operational contributions of algorithmic agents</title>
		<author>
			<persName><forename type="first">S</forename><surname>Alter</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of AMCIS</title>
				<meeting>AMCIS</meeting>
		<imprint>
			<date type="published" when="2022">2022</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Making sense of smartness in the context of smart devices and smart systems</title>
		<author>
			<persName><forename type="first">S</forename><surname>Alter</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Information Systems Frontiers</title>
		<imprint>
			<biblScope unit="volume">22</biblScope>
			<biblScope unit="page" from="381" to="393" />
			<date type="published" when="2020">2020</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Making cyber-human systems smarter</title>
		<author>
			<persName><forename type="first">S</forename><surname>Alter</surname></persName>
		</author>
		<idno type="DOI">10.1016/j.is.2024.102428</idno>
		<idno>doi:</idno>
		<ptr target="https://doi.org/10.1016/j.is.2024.102428" />
	</analytic>
	<monogr>
		<title level="m">Information Systems</title>
				<imprint>
			<date type="published" when="2024">2024</date>
		</imprint>
	</monogr>
	<note>preprint</note>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
