Search

ABSTRACTSelf-service technologies allow organizations to shift work from employees to the consumer, creating a coproduction environment where the consumer is an active participant in the delivery of a service, which they ultimately consume. While these technologies can have benefits for both consumers and the organizations, they can also present challenges (e.g., value erosion, feelings of coercion) that may give rise to consumer resentment. This study, using the theory of reasoned action as its theoretical lens, is one of the first in information systems to explore coproduction resentment. In particular, this study investigates the coproduction resentment within the context of self-checkout continuance intention. The study also investigates the effect of technology anxiety, fear of confrontation due to misuse, and technology-driven job losses on coproduction resentment. The study found support for the seven proposed hypotheses.

ABSTRACTThe number of brick and mortar retailers that have closed their doors or filed bankruptcy is staggering and crosses virtually every retail segment. As consumer demographics evolve and more consumers move to online purchasing, the question arises as to what role brick and mortar stores will play in the future. This pressure has driven retailers to employ new technology aimed at improving efficiency, reducing costs, and enhancing the consumer’s experience. This study, using diffusion of innovation as its theoretical lens, explores the impact of consumer confusion on the adoption of mobile self-checkout (MSCO) technology. A total of 217 responses were collected using crowdsourcing from respondents residing in the United States. Findings indicate that consumer confusion impacts usage intention through relative advantage (reducing consumer confusion) and compatibility. Relative advantage (saving time) positively impacts compatibility. Trialability and compatibility directly impact MSCO usage intention.

The article discusses software development in the context of issues related to project management, examining the role that project scoping plays in the success or failure of software development projects. Project scoping is defined by the authors as an activity that defines a project's boundary through the identification of software elements expected to be delivered and problem domains needs to be met. A 1994 report found that only 16% of IT (Information Technology) projects were successful. Also discussed is the use of outcome-based scoping (OBS) to reduce the chance of scoping-caused project failure.