Technology Adoption and Organizational Change

Introduction

Digital transformation in human resource management is not achieved merely by purchasing software. It occurs when people understand, accept, use, and continually improve digital systems in ways that create organizational value. An HR information system, artificial-intelligence recruitment tool, learning platform, employee self-service portal, or workforce-analytics application may fail despite technical quality if employees distrust it, lack skills, perceive little benefit, or experience poorly managed change.

Technology adoption is therefore both a behavioural and organizational issue. HR professionals must assess stakeholder readiness, identify sources of resistance, communicate a credible purpose, design effective training, and reinforce new behaviours. This chapter integrates three technology-adoption perspectives—the Technology Acceptance Model (TAM), the Unified Theory of Acceptance and Use of Technology (UTAUT), and organizational-change frameworks including ADKAR and Kotter’s eight-step model.

Learning Objectives

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

1. Explain the relationship between technology adoption and organizational change.
2. Apply TAM and UTAUT to analyse stakeholder readiness and resistance.
3. Use ADKAR and Kotter’s framework to structure change interventions.
4. Develop communication, training, adoption, and digital-capability plans.
5. Evaluate ethical, governance, inclusion, and sustainability issues in HR technology change.
6. Recommend evidence-based actions for improving adoption and measuring outcomes.

1. Technology Adoption as a Socio-Technical Process

A socio-technical perspective treats technology, people, work processes, culture, leadership, and institutional rules as interdependent. Adoption is not equivalent to installation. A system is adopted when intended users incorporate it into routine work and when the organization obtains the expected benefits.

Four stages are useful:

• Awareness: stakeholders know that a change is planned and understand its broad purpose.
• Acceptance: stakeholders regard the change as legitimate, useful, and sufficiently safe.
• Use: stakeholders perform required activities through the new technology.
• Institutionalization: use becomes normal, supported by policies, leadership, metrics, and continuous improvement.

Stakeholders may include employees, line managers, HR specialists, executives, information-technology staff, works councils, employee representatives, vendors, and customers whose data are processed. Their interests differ. Executives may emphasize efficiency and analytics; employees may emphasize privacy and job security; managers may focus on workload and accountability; HR professionals may be concerned with professional judgement and service quality.

Resistance should not automatically be interpreted as irrational opposition. It can reveal genuine risks, inadequate consultation, poor system design, conflicting incentives, previous failed projects, or fears about surveillance and job displacement. Effective change management treats resistance as information while distinguishing constructive critique from deliberate obstruction.

2. The Technology Acceptance Model

The Technology Acceptance Model, associated principally with Fred Davis, explains users’ intention to use a technology through two central beliefs:

• Perceived usefulness (PU): the degree to which a person believes that using the system will improve job performance.
• Perceived ease of use (PEOU): the degree to which a person believes that using the system will require little effort.

These beliefs influence attitude and behavioural intention, which in turn influence actual use. External variables—such as training, interface quality, managerial support, and system reliability—affect adoption largely through PU and PEOU.

A simplified conceptual relationship is:

External conditions → perceived usefulness and perceived ease of use → attitude and intention → use

TAM is valuable because it directs managers to ask specific diagnostic questions. If employees believe an HR portal is useful but difficult to operate, training and interface redesign may be required. If it is easy to use but considered irrelevant, leaders must demonstrate job-related value and revise workflows. If both perceptions are positive but use remains low, organizational barriers such as lack of access, incompatible policies, or weak managerial reinforcement may be responsible.

TAM has limitations. It may understate social influence, organizational power, habit, facilitating conditions, emotions, and ethical concerns. It also risks treating adoption as an individual choice when employees may be required to use a system. Consequently, TAM should be used as a diagnostic lens rather than a complete change theory.

3. UTAUT and Stakeholder Readiness

The Unified Theory of Acceptance and Use of Technology, developed by Venkatesh and colleagues, integrates several earlier acceptance theories. Its principal constructs are:

UTAUT also recognizes that relationships can vary according to age, gender, experience, and voluntariness of use. These factors should not be used to stereotype users. They are prompts for inclusive investigation. For example, differences in adoption may reflect unequal access, disability, language, digital confidence, or work design rather than personal characteristics.

A readiness assessment can combine interviews, surveys, observation, system data, and stakeholder workshops. Questions should address:

1. What organizational outcome is the technology intended to improve?
2. Which users experience the greatest benefit and burden?
3. Do users believe the system is accurate, secure, and fair?
4. Do they have time, equipment, skills, and support?
5. Which leaders, peers, or professional groups influence adoption?
6. What previous experiences shape trust or resistance?

A simple readiness matrix can classify stakeholders by influence and current readiness:

4. Understanding Resistance to Change

Resistance may be individual, group-based, structural, or technological. Common causes include:

• fear of redundancy or loss of status;
• uncertainty about altered roles and performance expectations;
• inadequate skills or previous negative learning experiences;
• increased administrative burden;
• distrust of algorithms, data collection, or management motives;
• poor interoperability and duplicated work;
• perceived unfairness in automated decisions;
• lack of consultation or weak leadership credibility.

HR professionals should avoid assuming that communication alone will solve resistance. A communication campaign cannot compensate for unreliable technology, unrealistic workloads, unsafe data practices, or a change that has no credible benefit. Resistance analysis should therefore examine both attitudes and objective conditions.

A useful distinction is between adoption barriers and change objections. An adoption barrier prevents effective use—for example, inaccessible design or missing permissions. A change objection challenges the legitimacy or consequences of the project—for example, concern that an algorithm disadvantages disabled applicants. The first may require technical remediation; the second may require governance review, redesign, or a decision not to proceed.

5. ADKAR: Individual Change Progression

The ADKAR model, associated with Prosci, describes five outcomes needed for individual change:

1. Awareness of why change is necessary.
2. Desire to participate and support the change.
3. Knowledge of what to do and how to do it.
4. Ability to apply knowledge in the work environment.
5. Reinforcement to sustain the new behaviour.

ADKAR is particularly useful for planning interventions around specific user groups. If employees lack awareness, leaders should explain the business and human reasons for change. If awareness exists but desire is weak, managers should listen to concerns, clarify consequences, and involve users in design. If knowledge is absent, training and guidance are required. If knowledge exists but performance remains poor, users need practice, coaching, system fixes, or workload adjustments. If use declines after launch, reinforcement through feedback, recognition, metrics, and ongoing support is necessary.

ADKAR’s strength is its practical focus on individual experience. Its limitation is that it can appear linear and may not fully explain political conflict, organizational structure, or repeated cycles of experimentation. Change teams should use it alongside organizational and governance analysis.

6. Kotter’s Eight-Step Framework

Kotter’s framework provides an organization-level sequence:

1. Create a sense of urgency.
2. Build a guiding coalition.
3. Form a strategic vision and initiatives.
4. Enlist a volunteer army and communicate the vision.
5. Enable action by removing barriers.
6. Generate short-term wins.
7. Sustain acceleration.
8. Institute change in organizational culture.

For an HR technology project, urgency should be evidence-based rather than manufactured. It may arise from compliance requirements, poor employee experience, insecure legacy systems, or an inability to make timely workforce decisions. The guiding coalition should include HR, IT, legal or privacy specialists, line managers, employee representatives, and affected users.

Short-term wins should be meaningful and ethically obtained. A pilot may demonstrate faster case resolution, fewer duplicate data entries, or improved accessibility. However, speed alone is not success if data quality falls or less digitally confident employees are excluded. Institutionalization requires updated policies, job expectations, onboarding, performance support, ownership, and resource allocation.

Kotter and ADKAR are complementary. Kotter emphasizes organizational momentum and leadership; ADKAR emphasizes individual adoption. For example, Kotter’s barrier-removal step may create help-desk capacity, while ADKAR’s ability stage examines whether a particular employee can complete a transaction correctly.

7. Designing an Adoption and Capability Plan

A robust plan links business outcomes, user needs, interventions, and measures.

7.1 Diagnose and segment

Map stakeholder influence, readiness, digital access, role-specific tasks, risks, and support requirements. Segment users by work activities rather than relying only on organizational position. A payroll administrator, warehouse employee, recruiter, and senior executive require different learning experiences.

7.2 Define the target behaviours

Describe observable behaviours, such as “managers approve leave through the portal within two working days” or “recruiters document the reason for overriding an algorithmic recommendation.” Behavioural descriptions are more actionable than “users will embrace the system.”

7.3 Build a communication plan

Communication should answer five questions: Why is the change occurring? What will change? What will not change? How will people be affected? Where can they obtain help or challenge a decision?

Use a channel mix: town halls for shared meaning, manager briefings for local interpretation, demonstrations for practical understanding, written guides for reference, and confidential feedback routes for concerns. Messages should be timely, accessible, multilingual where necessary, and honest about uncertainty. Overpromising damages trust.

7.4 Design training and performance support

Training should be role-based, practice-oriented, and accessible. Effective methods include sandbox exercises, simulations, short modules, peer coaching, job aids, office hours, and train-the-trainer programmes. Training needs analysis should identify required knowledge, existing capability, language needs, disability accommodations, device availability, and opportunities to practise.

Training is not a substitute for system usability. If users repeatedly make the same error, the problem may be confusing workflow design rather than insufficient motivation. Post-training observation and help-desk data should guide revisions.

7.5 Pilot and scale

A pilot should test technical performance, workflow fit, user experience, accessibility, data quality, and unintended consequences. Establish entry and exit criteria before the pilot begins. Include representative users, including those with limited digital access or additional support needs. Scale gradually when evidence supports it, while retaining a controlled fallback for critical processes.

7.6 Reinforce and improve

Adoption measures may include active use, completion rates, error rates, support requests, time to competence, user confidence, process-cycle time, data quality, and equity outcomes. Metrics should be interpreted carefully. High log-in rates do not prove meaningful use, and low usage may indicate that a process is appropriately infrequent.

8. Illustrative Case: Introducing an Employee Self-Service Platform

Background

A fictional organization, Northbridge Services, employs 2,400 people across offices, field locations, and remote work sites. HR plans to replace paper-based leave, address changes, and payslip distribution with a mobile-enabled self-service platform.

Problem

Senior leaders expect reduced administration and faster data updates. However, field employees report limited connectivity, some managers fear losing control over approvals, and employee representatives question whether location data will be used for performance monitoring. Previous software projects were introduced with minimal training, creating scepticism.

Analysis

A TAM assessment finds high perceived usefulness among HR administrators but low ease-of-use expectations among field employees. UTAUT analysis identifies weak facilitating conditions: shared devices, inconsistent connectivity, and limited local support. ADKAR interviews show awareness is moderate, desire is mixed, knowledge is low, and ability cannot yet be assessed. The project also presents privacy and inclusion risks.

Approach

Northbridge establishes a coalition of HR, IT, operations, employee representatives, privacy specialists, and field employees. It publishes a clear data-use statement, limits location tracking, and creates a process for correcting records. The organization pilots the platform in two sites with different connectivity conditions. It provides kiosks, offline procedures, accessible training, local champions, manager coaching, and a staffed help desk. Managers receive dashboards showing approval status rather than unnecessary employee surveillance.

Communication explains the administrative purpose, limits of data collection, fallback arrangements, and complaint channels. The pilot measures completion accuracy, processing time, support demand, accessibility, and employee confidence—not merely log-ins.

Outcome

The pilot reveals that the mobile interface performs well in offices but poorly under weak connectivity. The organization delays wider deployment, introduces offline functionality, and simplifies authentication. After a second pilot, adoption improves and paper processing declines without removing a non-digital alternative for employees who need it.

Learning points

The case demonstrates that readiness depends on perceived value, usability, social support, and actual facilitating conditions. Ethical safeguards are adoption enablers, not obstacles. A staged pilot can reveal structural barriers that training cannot solve. Finally, success should be defined by service quality, inclusion, trust, and organizational outcomes rather than technology use alone.

9. Ethical, Legal, and Governance Considerations

HR technology processes sensitive information, including identity, compensation, health, performance, and sometimes biometric or behavioural data. Governance should address purpose limitation, data minimization, accuracy, security, retention, access control, transparency, and accountability. Applicable privacy and employment laws vary by jurisdiction, so HR professionals must consult relevant legal requirements rather than assuming that a vendor’s compliance statement is sufficient.

Algorithmic tools require additional scrutiny. Organizations should assess whether training data or design choices produce discriminatory outcomes, whether affected individuals can obtain explanations, and whether human review is meaningful rather than ceremonial. Automated recommendations should not eliminate professional accountability. Vendors should disclose relevant model limitations, update practices, security controls, and audit rights.

Digital transformation can also intensify work, exclude people with disabilities, widen digital inequality, or create excessive monitoring. Impact assessments should therefore consider vulnerable groups, accessibility standards, psychological safety, and the right to challenge decisions. Consultation with employees and representative bodies can improve both legitimacy and system quality.

10. Contemporary Developments and Professional Implications

Generative AI, predictive analytics, robotic process automation, digital learning, and employee-experience platforms are expanding the scope of HR technology. These tools may improve personalization and administrative efficiency, but they also increase the importance of data literacy, critical thinking, model oversight, and change capability.

Future HR professionals will need to act as translators between business strategy, technology teams, employees, and governance functions. Their capabilities should include stakeholder analysis, process mapping, facilitation, instructional design, data interpretation, privacy awareness, vendor evaluation, and ethical reasoning. Digital capability is not simply the ability to operate software; it includes the ability to judge when technology is appropriate, identify harmful effects, and redesign work responsibly.

Challenges and Limitations of Adoption Frameworks

TAM and UTAUT may overemphasize intention and understate compulsion, power, collective norms, and structural inequality. ADKAR may simplify complex emotional and political processes into sequential outcomes. Kotter’s model can appear top-down and may not fit agile, iterative, or highly distributed organizations. None of these frameworks guarantees successful change.

They should therefore be combined with participatory design, process analysis, accessibility assessment, privacy impact assessment, pilot evidence, and continuous evaluation. Frameworks are maps, not substitutes for professional judgement. The quality of diagnosis, the credibility of leadership, and the fairness of implementation remain decisive.

Chapter Summary

Technology adoption in HR is a socio-technical process involving beliefs, behaviours, work design, leadership, infrastructure, and governance. TAM highlights perceived usefulness and ease of use. UTAUT extends the analysis through performance expectancy, effort expectancy, social influence, and facilitating conditions. Resistance may signal fear, inadequate resources, poor design, ethical concern, or legitimate disagreement.

ADKAR structures individual change through awareness, desire, knowledge, ability, and reinforcement. Kotter provides an organization-level approach based on urgency, coalition-building, vision, communication, barrier removal, short-term wins, sustained acceleration, and institutionalization. Effective adoption plans segment stakeholders, define target behaviours, communicate honestly, provide role-based practice, pilot responsibly, measure meaningful outcomes, and reinforce new routines.

HR professionals must also protect privacy, accessibility, fairness, security, and human accountability. Digital transformation succeeds when technology improves work and organizational outcomes while maintaining trust, inclusion, and responsible governance.

Key Terms

Technology adoption: The process through which intended users accept, use, and sustain a technology.

Socio-technical system: A system in which technology and social, organizational, and human factors interact.

Perceived usefulness: Belief that a technology will improve job performance.

Perceived ease of use: Belief that a technology can be used with limited effort.

Technology Acceptance Model (TAM): A model explaining technology use through usefulness, ease of use, attitudes, and intention.

UTAUT: A unified model explaining acceptance through performance expectancy, effort expectancy, social influence, and facilitating conditions.

Performance expectancy: Belief that technology will produce valued performance outcomes.

Effort expectancy: Perceived ease associated with using a technology.

Social influence: Perceived expectation or encouragement from important others.

Facilitating conditions: Organizational and technical resources supporting use.

Stakeholder readiness: Capacity and willingness of affected groups to participate in change.

Resistance to change: Behavioural, emotional, or cognitive opposition or concern regarding a change.

ADKAR: A change model consisting of awareness, desire, knowledge, ability, and reinforcement.

Kotter’s model: An eight-step organizational change framework.

Digital capability: The knowledge, skills, judgement, and infrastructure needed to use technology effectively and responsibly.

Change champion: A person who supports, explains, models, and encourages adoption among peers.

Pilot: A controlled, limited implementation used to test a change before scaling.

Algorithmic accountability: Responsibility for the design, operation, effects, and review of algorithmic systems.

Institutionalization: The point at which a new practice becomes embedded in routines, policies, culture, and systems.

Review Questions

5 Short Answer Questions

1. Define perceived usefulness and perceived ease of use in TAM.
2. What are the four principal UTAUT constructs?
3. List the five stages of ADKAR.
4. Why should resistance not automatically be treated as irrational behaviour?
5. Identify two ethical risks associated with HR technology adoption.

5 Long Answer Questions

1. Compare TAM and UTAUT as tools for diagnosing stakeholder readiness.
2. Explain how ADKAR and Kotter’s framework can be used together in an HR technology project.
3. Discuss the components of an effective communication and training plan.
4. Explain why pilot testing is important before organization-wide implementation.
5. Evaluate the role of privacy, accessibility, and algorithmic accountability in digital HR transformation.

3 Analytical / Application Questions

1. A new performance-management platform is easy to use but employees do not believe it improves their work. Use TAM to diagnose the problem and recommend interventions.
2. Design a stakeholder-readiness matrix and adoption plan for introducing an AI-supported recruitment system.
3. Using the Northbridge Services case, identify the main adoption barriers and propose measures for evaluating whether the second pilot is ready for scale.

Multiple Choice Questions with Answers

Question 1

Which concept in TAM refers to the belief that a system will improve job performance?

A. Perceived usefulness

B. Social influence

C. Facilitating conditions

D. Reinforcement

Correct Answer: A. Perceived usefulness

Question 2

Which UTAUT construct concerns the availability of resources, access, and support?

A. Performance expectancy

B. Effort expectancy

C. Social influence

D. Facilitating conditions

Correct Answer: D. Facilitating conditions

Question 3

In ADKAR, which stage follows awareness?

A. Ability

B. Desire

C. Knowledge

D. Reinforcement

Correct Answer: B. Desire

Question 4

Which action best represents Kotter’s step of building a guiding coalition?

A. Installing software without consultation

B. Recruiting leaders and representatives from affected groups

C. Measuring log-ins after launch

D. Replacing all existing procedures immediately

Correct Answer: B. Recruiting leaders and representatives from affected groups

Question 5

Why is resistance potentially valuable during technology change?

A. It always proves that the project should be cancelled

B. It can reveal risks, design problems, or inadequate support

C. It eliminates the need for training

D. It guarantees faster adoption

Correct Answer: B. It can reveal risks, design problems, or inadequate support

Question 6

Which is the strongest example of a target behaviour?

A. Employees will embrace innovation

B. Managers will appreciate the platform

C. Managers will approve leave through the portal within two working days

D. The organization will become digital

Correct Answer: C. Managers will approve leave through the portal within two working days

Question 7

Which measure best assesses meaningful adoption rather than simple system access?

A. Number of software licences purchased

B. Number of launch emails sent

C. Completion accuracy and process-cycle time

D. Size of the implementation team

Correct Answer: C. Completion accuracy and process-cycle time

Question 8

A user has received training but cannot complete tasks because system permissions are missing. Which ADKAR issue is most directly indicated?

A. Ability and facilitating conditions

B. Awareness only

C. Social influence only

D. Urgency only

Correct Answer: A. Ability and facilitating conditions

Question 9

Which practice best supports responsible use of an HR algorithm?

A. Allowing the vendor to make all employment decisions

B. Removing human review to increase speed

C. Auditing outcomes and preserving meaningful human accountability

D. Collecting unlimited personal data

Correct Answer: C. Auditing outcomes and preserving meaningful human accountability

Question 10

Why should HR technology pilots include users with limited connectivity or accessibility needs?

A. To make the pilot unnecessarily complex

B. To identify inclusion and infrastructure barriers before scaling

C. To avoid measuring technical performance

D. To replace all training activities

Correct Answer: B. To identify inclusion and infrastructure barriers before scaling