Search

Previous literature has treated software functionalities as a binary choice between informating and automating, based on Zuboff's definitions. We suggest that the space between the role of a user engaging with a system (informate) and what the system can accomplish for the user (automate) has increasingly become blurred, moving toward a more nuanced continuum. We present a user-system interaction framework that analyzes this continuum with a focus on the user's perspective. Using cases from archival data, this paper provides an analysis of what goes well and badly in the locus of control handoff between users and systems, highlighting the implications of software that is created in one region but used globally. The paper contributes to the literature by extending Zuboff's informate vs. automate discussion and identifying design decisions that could help to avoid potentially catastrophic design errors. Using the interaction framework, we argue that it would be beneficial for system designers to move toward the informate end of the continuum, when designing systems for users with a high level of domain knowledge and expertise, and when there are significant differences between the environment in which the system is designed and the one in which the system is used. [ABSTRACT FROM AUTHOR]