Chapter 9: Human–Computer Interaction and Socio-Technical Adoption

1. Introduction

Information technology is often described in terms of hardware, software, networks, data, and algorithms. Yet technological systems do not create value through technical capability alone. They create value when people can understand, use, trust, adapt to, and embed them in meaningful activities. Human–computer interaction (HCI) examines the relationship between people and interactive technologies, while socio-technical adoption examines how technologies become accepted, resisted, adapted, or transformed within organizations and societies.

A system may be technically reliable and still fail because it conflicts with users’ mental models, imposes excessive cognitive effort, excludes people with disabilities, disrupts established work practices, or redistributes authority in unacceptable ways. Conversely, a modest technology can produce substantial benefits when it fits users’ goals, institutional arrangements, cultural expectations, and organizational incentives. Doctoral study of HCI therefore requires more than interface design. It requires analysis of cognition, behavior, accessibility, culture, power, institutions, organizational change, and ethics.

This chapter develops an integrated perspective. It first explains the meaning and foundations of HCI and socio-technical adoption, then examines theories and methods, applications, managerial implications, and emerging issues. The central argument is that technology outcomes are produced through interaction between technical artifacts and social systems. Design and adoption must therefore be treated as connected, iterative, and politically informed processes.

2. Learning Objectives

By the end of this chapter, the reader should be able to:

1. Explain the scope and significance of HCI and socio-technical adoption.

2. Apply principles of cognition, usability, accessibility, and interaction design.

3. Compare major technology acceptance, diffusion, innovation, and organizational theories.

4. Analyze how culture, institutions, power, and organizational behavior influence technology outcomes.

5. Design an evidence-based process for evaluating and improving interactive systems.

6. Assess ethical, governance, and inclusion issues in technology adoption.

7. Develop strategic recommendations for responsible digital transformation.

3. Meaning and Concept

Human–computer interaction is the interdisciplinary study, design, and evaluation of interactive computing systems for human use. It draws on computer science, psychology, design, sociology, ergonomics, anthropology, communication, and organizational studies. HCI is concerned not only with screens and controls but also with the contexts in which interaction occurs: workplaces, homes, public services, vehicles, hospitals, classrooms, and immersive environments.

Usability refers to the extent to which specified users can achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use. Usability is contextual. A system that is easy for an expert in a quiet office may be unsuitable for a novice working under time pressure, using a mobile device, or operating in a noisy environment.

Accessibility concerns whether people with diverse abilities can perceive, understand, navigate, and operate a system. It includes visual, auditory, motor, speech, cognitive, and neurological dimensions. Accessibility is not a specialist add-on; it is part of quality, equity, legal compliance, and responsible design.

Socio-technical adoption refers to the process by which individuals, groups, organizations, and communities accept, reject, modify, normalize, or appropriate technology. Adoption is not simply a psychological decision. It is shaped by resources, professional norms, leadership, regulation, infrastructure, social influence, trust, identity, work practices, and distributions of power.

A socio-technical system consists of technical elements and social elements that are mutually dependent. Technical elements include applications, data, devices, interfaces, algorithms, and infrastructure. Social elements include users, roles, routines, skills, values, incentives, authority structures, policies, and informal networks. System performance emerges from their interaction rather than from either domain in isolation.

4. Fundamental Principles

4.1 Human-centeredness

Design begins with human goals, capabilities, limitations, and contexts rather than with available technology. Human-centered design treats users as participants in inquiry and evaluation. It asks what people are trying to accomplish, what constraints they face, and what consequences follow from alternative designs.

4.2 Context matters

Interaction is influenced by physical, social, organizational, cultural, and temporal conditions. A clinical interface used during an emergency must support rapid recognition and error recovery; a financial planning interface may support extended reflection and comparison. Requirements should therefore describe context, not merely features.

4.3 Visibility and feedback

Users need to know what actions are possible, what the system is doing, and what resulted from their actions. Clear status information reduces uncertainty. Feedback should be timely, understandable, and proportionate to the significance of the action.

4.4 Consistency and standards

Consistent terminology, layout, behavior, and control conventions reduce learning effort and cognitive load. Standards also support transfer of knowledge across systems. Consistency, however, should not be applied mechanically when it conflicts with task needs or accessibility.

4.5 Error tolerance and recoverability

Errors are inevitable. Good systems prevent serious errors where possible, make errors understandable, preserve user control, and support recovery. Confirmation dialogs are not sufficient if they are frequent, vague, or routinely ignored. Prevention may involve constraints, previews, undo facilities, version history, and meaningful warnings.

4.6 Recognition over recall

Interfaces should make relevant options, information, and system states visible. Requiring users to remember commands, codes, or hidden procedures increases cognitive burden and error probability.

4.7 Inclusive and equitable design

Design should account for variation in ability, language, age, literacy, technical experience, connectivity, culture, and socioeconomic conditions. Inclusion also requires examination of who defines the problem, whose data are used, and who bears risks.

4.8 Respect for human agency

Automation should assist rather than silently displace human judgment where meaningful judgment is required. Users should understand important system behavior, challenge decisions when appropriate, and retain control over consequential actions.

5. Major Components / Elements

Users and stakeholders

Users include direct operators, indirect beneficiaries, administrators, maintainers, subjects of data collection, and people affected by system decisions. Stakeholder analysis must include marginalized groups and those who may lack formal authority but possess essential practical knowledge.

Tasks and goals

Task analysis examines activities, sequences, decisions, dependencies, exceptions, and sources of error. Goals describe desired outcomes, while tasks describe the actions and reasoning used to achieve them. A system designed around organizational procedures may fail if actual work depends on informal coordination.

Interaction modalities

Interaction may occur through graphical interfaces, command languages, touch, voice, gesture, haptic feedback, sensors, conversational agents, or multimodal combinations. Each modality creates opportunities and constraints. Voice interaction, for example, can support hands-free use but may create privacy problems and recognition errors.

Information architecture and representation

Information architecture determines how content is organized, labeled, searched, and navigated. Representation includes typography, color, icons, charts, alerts, spatial arrangements, and feedback. Representations influence interpretation and can privilege certain categories or decisions.

Physical and cognitive environment

Ergonomics addresses posture, reach, lighting, noise, fatigue, and physical safety. Cognitive design addresses attention, memory, workload, comprehension, decision-making, and situation awareness.

Organizational and institutional environment

Policies, performance measures, professional roles, budgets, procurement rules, regulations, and leadership practices affect adoption. A technically usable system may be rejected if it increases surveillance, threatens professional autonomy, or conflicts with incentives.

6. Process / Framework / Methodology

A rigorous HCI and adoption process is iterative rather than linear.

Step 1: Define the problem and context

Researchers identify stakeholders, environments, goals, constraints, risks, and existing practices. Contextual inquiry, observation, interviews, document analysis, and diary studies can reveal work that formal requirements omit.

Step 2: Analyze users and activities

Personas, user journeys, task models, workflow diagrams, and capability profiles help represent variation without reducing users to simplistic demographic categories. Researchers should distinguish user characteristics from barriers created by the environment.

Step 3: Establish requirements

Requirements should include functional, usability, accessibility, privacy, security, interoperability, and organizational requirements. Quality criteria should be measurable, such as task completion rate, error recovery time, learnability, or accessibility conformance.

Step 4: Co-design alternatives

Workshops, participatory design, storyboards, paper prototypes, wireframes, and service blueprints allow stakeholders to explore alternatives before expensive implementation. Participation should include decision authority, not merely symbolic consultation.

Step 5: Prototype and evaluate

Low-fidelity prototypes support rapid exploration; high-fidelity prototypes test realistic interaction. Evaluation methods include heuristic inspection, cognitive walkthroughs, usability testing, accessibility testing, field trials, analytics, and interviews. No single method reveals every problem.

Step 6: Implement with organizational preparation

Implementation includes training, communication, migration, support, role clarification, governance, and revision of performance measures. Technical deployment without social preparation often produces workarounds and resistance.

Step 7: Monitor adoption and consequences

Evaluation should continue after launch. Measures may include active use, task success, satisfaction, help requests, error rates, workarounds, equity outcomes, privacy incidents, and unintended changes in authority or workload.

Step 8: Learn and adapt

Adoption is an evolving process. Feedback should inform redesign, policy adjustment, training, and sometimes withdrawal of a harmful feature or system. Post-implementation review should examine both intended benefits and unintended consequences.

7. Important Theories and Models

7.1 Mental models and cognitive theories

A mental model is a person’s internal understanding of how a system works. Users predict outcomes based on this understanding. When system behavior matches the mental model, interaction is easier; when it does not, users experience confusion and error. Designers use conceptual models, feedback, and familiar metaphors to support accurate mental models.

Cognitive load theory distinguishes intrinsic load associated with task complexity, extraneous load caused by poor presentation, and germane effort devoted to learning. HCI seeks to reduce unnecessary load while supporting understanding. Attention is limited, working memory is constrained, and interruptions can damage performance. These principles are particularly important in safety-critical and high-pressure environments.

7.2 Norman’s principles and usability heuristics

Normative HCI principles include visibility of system status, correspondence between system and real world, user control, consistency, error prevention, recognition, flexibility, minimalist design, error recovery, and help. Heuristic evaluation uses trained evaluators to inspect an interface against such principles. It is efficient but may miss problems that arise only in real contexts.

7.3 Technology Acceptance Model

The Technology Acceptance Model explains behavioral intention primarily through perceived usefulness and perceived ease of use. Perceived usefulness concerns whether a technology improves performance; perceived ease of use concerns the effort required. The model is valuable for identifying beliefs that influence adoption, but it may understate institutional constraints, power relations, habit, culture, and mandatory use.

7.4 Unified Theory of Acceptance and Use of Technology

UTAUT extends acceptance analysis through performance expectancy, effort expectancy, social influence, and facilitating conditions, with factors such as age, experience, gender, and voluntariness sometimes moderating relationships. It is useful for structured organizational analysis, although researchers should avoid treating its variables as universal explanations.

7.5 Diffusion of Innovations

Rogers’ diffusion theory explains how innovations spread through communication channels over time within a social system. Adoption is influenced by relative advantage, compatibility, complexity, trialability, and observability. Innovators, early adopters, early majority, late majority, and laggards describe adoption patterns, not fixed personal types. The theory highlights social networks and perceived compatibility.

7.6 Theory of Planned Behavior

The Theory of Planned Behavior proposes that intention is influenced by attitudes, subjective norms, and perceived behavioral control. Perceived control is especially important where access, skills, authority, or resources constrain action. The model helps distinguish unwillingness from inability.

7.7 Task–Technology Fit

Task–Technology Fit argues that performance improves when technological capabilities match task requirements. A system may be easy to use but poorly suited to the work, or powerful but too complex for routine use. Evaluation should therefore examine actual task demands rather than acceptance attitudes alone.

7.8 Socio-technical systems theory

Socio-technical systems theory emphasizes joint optimization of social and technical subsystems. It rejects the assumption that technical efficiency can be maximized independently of human work organization. Principles include meaningful work, responsible autonomy, boundary management, and designing groups and technologies together.

7.9 Structuration and appropriation perspectives

Structuration theory views technology and social structures as mutually shaping. Technologies embody rules and resources, but users may interpret and appropriate them in unexpected ways. A collaboration platform designed for formal reporting may become an informal coordination tool. These perspectives explain why implementation outcomes cannot be predicted solely from design intentions.

7.10 Institutional and power perspectives

Institutional theory highlights coercive pressures from regulation, normative pressures from professions, and mimetic pressures to imitate prestigious organizations. Power perspectives ask who defines requirements, controls data, sets standards, benefits from automation, and bears risk. Adoption may appear successful while concealing compliance, fear, or unequal outcomes.

8. Practical Applications

In healthcare, HCI supports medication ordering, electronic records, diagnostic visualization, and patient portals. Designers must address interruptions, terminology, workload, privacy, and error consequences. In education, learning platforms should support instructors and learners without reducing teaching to surveillance metrics. In public administration, accessible digital services must accommodate language diversity, low digital literacy, disability, and citizens who require non-digital alternatives.

In manufacturing and logistics, interfaces must support situation awareness, rapid exception handling, and safe coordination between workers and automation. In banking and commerce, persuasive interface techniques should not manipulate customers into unwanted purchases or obscure important financial information. In enterprise systems, adoption depends on integration with roles, incentives, data quality, and existing processes.

9. Examples

A university may introduce an online assessment platform. If it focuses only on feature availability, it may overlook students with limited bandwidth, screen-reader users, instructors who need flexible grading workflows, and privacy concerns associated with remote proctoring. A socio-technical approach would include accessibility testing, alternative assessment procedures, transparent data governance, training, and evaluation of differential impacts.

A factory may deploy wearable devices to improve maintenance. Workers may resist not because the devices are difficult to use, but because they interpret them as instruments of surveillance. Consultation, limits on data use, worker representation, and separation of safety data from disciplinary monitoring may influence adoption more than interface refinement alone.

10. Technology and Digital Applications

Relevant applications include accessible web and mobile systems, enterprise resource planning, electronic health records, collaborative platforms, conversational agents, recommender systems, wearable computing, augmented and virtual reality, digital public services, and AI-supported decision systems. In each case, design must address interaction quality and the broader system of practices, data, accountability, and institutional authority.

AI systems require particular attention to explainability, uncertainty, contestability, and automation bias. A visually elegant dashboard may still produce poor decisions if data are incomplete or if users interpret probabilistic outputs as certainty. Conversational systems must address ambiguity, privacy, cultural variation, and the risk that users attribute human understanding to a statistical system.

11. Strategic / Managerial Importance

HCI and adoption analysis improve return on technology investment by reducing failure, rework, training costs, support demands, and resistance. They also improve safety, service quality, employee experience, innovation, and organizational legitimacy. Managers should treat usability and accessibility as strategic quality dimensions rather than cosmetic concerns.

Successful transformation requires sponsorship, participation, realistic implementation plans, appropriate incentives, and measurement beyond deployment. Leaders should ask whether the technology improves work, who benefits, who is burdened, and what new dependencies or vulnerabilities are created. Governance should connect design decisions with risk management, procurement, compliance, and organizational learning.

12. Detailed Case Study

Background

The following is a fictional case for educational purposes. Northbridge Municipal Health Service introduced a digital appointment and triage platform intended to reduce telephone congestion and improve access to primary care.

Problem

After launch, online bookings increased, but missed appointments and complaints also rose. Older residents, people with limited English proficiency, and patients with disabilities reported difficulty using the platform. Clinicians complained that triage information was incomplete. Managers initially attributed the problems to user resistance.

Analysis

A multidisciplinary team conducted observation, usability tests, accessibility audits, interviews, and workflow analysis. The platform used medical terminology unfamiliar to patients, required long forms, timed out during completion, and offered no clear route to human assistance. The language translation was incomplete. Clinicians received structured data that did not match their triage workflow and therefore relied on telephone follow-up.

The analysis also identified institutional and power issues. The project had been governed by an information technology unit with limited patient and clinician representation. Performance indicators rewarded the percentage of digital bookings but did not measure completion equity, clinical usefulness, or patient safety. Some staff feared that reporting problems would be interpreted as opposition to modernization.

Strategy / Solution

Northbridge established a joint governance group including patients, clinicians, accessibility specialists, service staff, and technical personnel. The team simplified terminology, shortened forms, added save-and-return functionality, improved keyboard and screen-reader support, provided multilingual content, and introduced a prominent human-support option. It redesigned triage categories with clinicians and added a telephone and in-person alternative for people unable or unwilling to use the platform.

The organization revised metrics to include successful completion across user groups, triage completeness, waiting time, abandonment, accessibility defects, and patient satisfaction. Staff received training, and a policy clarified that platform data would not be used to penalize employees who documented limitations.

Outcome

Completion rates improved overall and the gap between demographic groups narrowed. Clinicians reported that triage information was more useful, while telephone demand became more manageable rather than disappearing entirely. The service also identified that some cases should not be digitized because they required sensitive conversation or professional judgment.

Learning Points

The case demonstrates that adoption is not equivalent to login or transaction volume. Usability problems can reflect organizational design, language, accessibility, workflow mismatch, and governance. Meaningful participation reveals hidden requirements, while inclusive metrics prevent apparent efficiency from masking unequal access. Digital services should complement, not automatically eliminate, human channels.

13. Advantages / Benefits

Human-centered and socio-technical approaches can improve effectiveness, efficiency, satisfaction, safety, accessibility, trust, and adoption. They identify problems early, reduce costly redesign, support better fit with work practices, and expose unintended consequences. They also strengthen organizational learning by treating users as sources of knowledge rather than passive recipients.

At a societal level, inclusive design can improve access to education, healthcare, public services, employment, and information. Participatory governance can increase legitimacy and reveal risks that technical teams alone may not detect.

14. Limitations / Challenges

HCI research can be time-consuming and expensive, especially when diverse users and real-world contexts must be included. Findings from small samples may not generalize, while quantitative metrics may overlook meaning, emotion, or power. Stakeholders may disagree, and participation can be constrained by organizational hierarchy.

Adoption models may oversimplify behavior or assume voluntary choice. Usability improvements cannot solve inadequate infrastructure, poor data quality, harmful policies, or resource shortages. Accessibility standards provide important guidance but do not guarantee a satisfactory experience for every person. Finally, organizations may use the language of human-centered design while retaining centralized decision-making.

15. Ethical and Governance Considerations

Ethical HCI requires informed participation, privacy protection, security, accessibility, transparency, fairness, and accountability. Researchers should minimize data collection, explain purposes, obtain appropriate consent, and protect vulnerable participants. Design should avoid dark patterns that manipulate users through hidden costs, confusing choices, or obstructive cancellation procedures.

Automated systems raise questions about bias, explainability, human oversight, contestability, and responsibility. Governance should specify who can access data, who can alter models, how errors are reported, and how affected people can appeal decisions. Organizations should assess distributional effects: a system may improve average performance while disadvantaging a minority.

Power must be made visible. Design choices determine whose knowledge is encoded, whose behavior is monitored, and whose interests define success. Ethical review should therefore include affected communities, not only technical and legal experts.

16. Current and Emerging Trends

Generative AI is changing conversational interaction, content creation, programming, and decision support. Its benefits depend on calibrated trust, verification, provenance, and clear boundaries between assistance and authority. Explainable interfaces are evolving toward explanations that are useful for the user’s decision rather than merely technically detailed.

Extended reality introduces spatial interaction, embodiment, immersion, and new safety concerns. Wearable and ambient computing make interaction more continuous but increase privacy and consent challenges. Neuroadaptive and affective systems may infer attention or emotion, creating significant risks of misinterpretation and surveillance.

Inclusive design is expanding toward neurodiversity, multilingual interaction, low-connectivity contexts, and participatory design with communities. Organizations are also using digital twins, process mining, and workplace analytics; these tools require careful governance because visibility into work can become control over workers.

17. Best Practices

1. Define success in terms of human and organizational outcomes, not feature counts.

2. Study real work and real contexts before finalizing requirements.

3. Involve diverse users throughout research, design, testing, and governance.

4. Build accessibility, privacy, security, and safety into initial requirements.

5. Use multiple evaluation methods and test with representative participants.

6. Design for errors, recovery, uncertainty, and exceptional situations.

7. Measure adoption quality, equity, and consequences rather than usage alone.

8. Provide training, support, alternatives, and mechanisms for feedback.

9. Make data practices, automated decisions, and accountability understandable.

10. Reassess systems after implementation and retire harmful or ineffective features.

18. Future Scope

Future research will increasingly connect HCI with AI alignment, organizational theory, public policy, disability studies, environmental sustainability, and data governance. Important questions include how to design meaningful human control over autonomous systems, how to measure equitable adoption, and how to support collective rather than purely individual interaction.

Researchers will also need methods for studying long-term effects. Short usability tests may not reveal dependency, deskilling, institutional change, or shifts in professional identity. Longitudinal, participatory, comparative, and mixed-method research will be essential. Sustainable HCI should consider energy use, device lifecycles, electronic waste, and the social costs of continuous digitalization.

19. Chapter Summary

HCI studies how people interact with computing systems, while socio-technical adoption explains how technologies become embedded in social and organizational life. Effective systems depend on cognition, usability, accessibility, task fit, trust, institutional conditions, culture, and power. Human-centered design is iterative and evidence-based, but it must be joined with organizational preparation and ethical governance.

Major theories—including mental models, cognitive load, acceptance models, diffusion theory, planned behavior, task–technology fit, socio-technical systems theory, structuration, and institutional perspectives—offer complementary explanations. No single model captures all adoption outcomes. Responsible practice therefore combines technical evaluation with contextual inquiry, participation, equity analysis, and continuous learning.

20. Key Terms

1. Accessibility: The degree to which a system can be used by people with diverse abilities.

2. Adoption: Acceptance, use, adaptation, or institutionalization of a technology.

3. Cognitive load: Mental effort required to process information and perform a task.

4. Context of use: The users, goals, environment, tools, and conditions surrounding interaction.

5. Dark pattern: A design technique that steers users toward choices against their interests.

6. Human–computer interaction: The study and design of interaction between people and computing systems.

7. Human-centered design: Design based on users’ needs, contexts, participation, and evaluation.

8. Interaction modality: A channel of interaction such as touch, voice, gesture, or text.

9. Mental model: A user’s internal understanding of how a system operates.

10. Participatory design: Design in which affected users actively contribute to decisions.

11. Socio-technical system: A system formed by interacting technical and social elements.

12. Task–technology fit: The correspondence between technology capabilities and task requirements.

13. Usability: Effectiveness, efficiency, and satisfaction in a specified context.

14. User experience: The perceptions, emotions, responses, and outcomes associated with interaction.

15. Technology acceptance: Willingness or intention to use a technology.

16. Automation bias: Tendency to favor or overtrust automated outputs.

17. Accessibility audit: Systematic assessment of barriers affecting access and use.

18. Institutional pressure: Regulatory, professional, or imitation-based influence on organizational behavior.

21. Review Questions

Short Answer Questions

1. Define human–computer interaction and explain why it is interdisciplinary.

2. What is the difference between usability and accessibility?

3. Explain the importance of mental models in interface design.

4. What does task–technology fit mean?

5. Why is technology adoption a socio-technical process?

Long Answer Questions

1. Compare the Technology Acceptance Model, UTAUT, and Diffusion of Innovations theory.

2. Explain how cognitive limitations influence the design of interactive systems.

3. Discuss the role of organizational culture, institutions, and power in technology adoption.

4. Describe an iterative human-centered design and evaluation process.

5. Analyze the ethical and governance challenges of AI-supported interaction.

Analytical / Application Questions

1. A hospital introduces an AI triage system that clinicians find accurate but difficult to interpret. Analyze the problem using usability, mental-model, task–technology-fit, and trust perspectives. Recommend an evaluation plan.

2. A government agency reports high digital-service usage, but rural residents and people with disabilities have lower completion rates. Develop a socio-technical diagnosis and propose inclusive interventions and measures.

3. An organization introduces employee-monitoring wearables and faces resistance. Analyze the role of power, privacy, culture, perceived usefulness, and institutional trust in the outcome. Propose a responsible adoption strategy.

22. Multiple Choice Questions with Answers

Question 1

Which statement best describes a socio-technical system?

A. A technical system evaluated without considering users

B. A system in which technical and social elements interact and jointly shape outcomes

C. A system used only by technically trained professionals

D. A system that eliminates human decision-making

Correct Answer: B. A system in which technical and social elements interact and jointly shape outcomes

Question 2

Which design principle primarily reduces the need for users to remember hidden commands?

A. Recognition over recall

B. Maximum automation

C. Institutional conformity

D. Data minimization

Correct Answer: A. Recognition over recall

Question 3

According to the Technology Acceptance Model, which two beliefs are central to technology acceptance?

A. Security and privacy

B. Relative advantage and trialability

C. Perceived usefulness and perceived ease of use

D. Social influence and facilitating conditions

Correct Answer: C. Perceived usefulness and perceived ease of use

Question 4

A system is easy to operate but does not support the actual sequence of professional tasks. Which concept best explains the problem?

A. Task–technology fit

B. Diffusion threshold

C. Cognitive realism

D. Institutional isomorphism

Correct Answer: A. Task–technology fit

Question 5

What is the primary purpose of accessibility design?

A. To make every interface visually identical

B. To ensure people with diverse abilities can perceive, understand, and operate the system

C. To reduce the number of system functions

D. To replace usability testing with legal compliance

Correct Answer: B. To ensure people with diverse abilities can perceive, understand, and operate the system

Question 6

Which method is most appropriate for discovering informal work practices and contextual constraints?

A. Contextual inquiry and observation

B. Counting software features

C. A purely technical performance benchmark

D. Randomly changing interface colors

Correct Answer: A. Contextual inquiry and observation

Question 7

A worker rejects a wearable device because it may be used for disciplinary surveillance, even though it is easy to use. This most directly illustrates the importance of:

A. Screen resolution

B. Power, trust, and organizational context

C. Recognition over recall

D. File compression

Correct Answer: B. Power, trust, and organizational context

Question 8

Which practice best supports responsible AI-supported interaction?

A. Concealing uncertainty to increase user confidence

B. Removing human appeal mechanisms

C. Providing understandable explanations, oversight, and contestability

D. Measuring success only by system speed

Correct Answer: C. Providing understandable explanations, oversight, and contestability

Question 9

In Diffusion of Innovations theory, compatibility refers primarily to:

A. The physical size of a device

B. The fit between an innovation and existing values, practices, and needs

C. The number of available software licenses

D. The speed of a network connection

Correct Answer: B. The fit between an innovation and existing values, practices, and needs

Question 10

Why should adoption metrics include equity and completion rates across user groups?

A. Usage totals alone may conceal unequal access and unintended harm

B. Equity metrics eliminate the need for usability tests

C. They guarantee universal acceptance

D. They measure only technical reliability

Correct Answer: A. Usage totals alone may conceal unequal access and unintended harm