Chapter 14. Organizational Readiness and Technology Adoption
14.1 Introduction
A technology can be technically sophisticated, scientifically credible and commercially attractive while nevertheless failing within an organization. This occurs because technology adoption is not simply a purchasing decision. It is an organizational transformation process involving people, structures, resources, workflows, leadership, culture, governance and institutional objectives.
The acquisition of a technology represents only the beginning of the adoption process. An organization must subsequently determine how the technology will be integrated into existing systems, how employees will use it, how responsibilities will be allocated, how risks will be controlled, how performance will be monitored and how the technology will be maintained and eventually replaced. Consequently, the evaluation of technology must include an assessment of the organization's capacity to absorb and sustain technological change.
Successful implementation may require strong leadership, adequate financial and human resources, appropriate infrastructure, relevant skills, supportive organizational culture, compatible processes, effective governance, communication, training and structured change management. These factors interact with one another. A shortage in one area may undermine performance in another. For example, an organization may have sufficient funding to purchase an advanced artificial-intelligence platform but lack employees with the expertise required to configure, validate, interpret and govern it.
Weiner (2009) conceptualizes organizational readiness as a shared psychological and behavioural state concerning commitment to implementing change and collective capability to do so. This perspective is important because readiness is not simply an individual characteristic. It can exist at the organizational, departmental, team and project levels and can vary across different groups within the same institution.
Organizational readiness should therefore be treated as a multidimensional construct. It involves not only willingness to adopt a technology but also the actual capability to implement and sustain it responsibly. An organization may be enthusiastic about innovation while simultaneously lacking the infrastructure, expertise or governance required for successful implementation. Conversely, an organization may possess considerable technical capability but have low employee acceptance because the purpose of the technology has not been adequately communicated.
AMTEF consequently treats organizational readiness as a central component of technology evaluation rather than as an issue to be addressed after a technology has been selected.
14.2 Technology Readiness Versus Organizational Readiness
Technology readiness and organizational readiness are related but distinct concepts. Technology readiness asks whether a technology is sufficiently mature, reliable and demonstrated for its intended purpose. Organizational readiness asks whether the organization is sufficiently prepared to implement, operate, govern and sustain that technology.
A technologically immature system may require further research, laboratory testing or controlled experimentation before operational deployment. A technologically mature system may nevertheless require organizational capability development before it can be implemented successfully.
The relationship can be understood through a two-dimensional framework. When both technology readiness and organizational readiness are low, the appropriate organizational response is generally continued research, exploration and controlled experimentation rather than immediate implementation. When technology readiness is high but organizational readiness is low, the organization may need to focus on capability development, infrastructure, training, governance and change management before large-scale adoption. When both technology and organizational readiness are high, the organization may be positioned to proceed toward implementation and scaling, subject to the results of the wider AMTEF assessment.
This distinction prevents a common technological fallacy: assuming that because a product is commercially available, the organization is automatically ready to use it.
14.3 Technology Readiness Levels
Technology Readiness Levels, commonly known as TRLs, originated within NASA and have subsequently been adapted in different forms by governments, research institutions and technology-development organizations. TRL approaches generally describe a progression from basic principles and early concepts toward laboratory validation, prototype development, demonstration and operationally relevant systems.
TRLs provide a useful way of communicating technological maturity. They can help evaluators distinguish between an early-stage research concept and a technology that has been demonstrated under realistic operating conditions.
However, TRL primarily evaluates technological maturity. It does not necessarily establish whether an organization possesses the skills, funding, infrastructure, governance, stakeholder acceptance or ethical capacity necessary for adoption. Nor does a high TRL automatically establish that a technology is economically sustainable, socially desirable or environmentally responsible.
AMTEF therefore complements rather than replaces technology-maturity approaches. TRL can answer the question, "How mature is the technology?" AMTEF extends the question to include, "How effective, safe, affordable, sustainable, ethical, governable and organizationally feasible is the technology in this particular context?"
14.4 Innovation Adoption
Rogers (2003) identified several characteristics that influence the adoption of innovations, including relative advantage, compatibility, complexity, trialability and observability. These concepts remain useful for organizational technology evaluation because they provide a structured way of understanding why organizations and individuals respond differently to technological innovations.
Adoption is rarely determined by technical performance alone. Employees and managers may evaluate whether a technology actually improves their work, whether it fits established practices, whether it is difficult to use, whether they can test it before making a major commitment and whether its benefits can be observed.
The adoption process should therefore be understood as both a technological and social process. Organizations evaluate not merely the technical characteristics of an innovation but also what the innovation means for their existing structures, responsibilities and professional practices.
14.5 Relative Advantage
Relative advantage refers to the degree to which a new technology is perceived to provide meaningful improvement over an existing approach. Such improvement may involve lower cost, improved quality, increased speed, greater accessibility, enhanced safety, improved decision-making, better customer or student experience, greater productivity or improved resource utilization.
However, perceived advantage should be distinguished from demonstrated advantage. Vendors may present technologies as transformative, revolutionary or highly efficient, but organizational decisions should be based on evidence appropriate to the intended application.
For this reason, AMTEF encourages organizations to establish a baseline before implementation. The organization should identify current performance and subsequently determine whether the new technology produces measurable improvement.
For example, if an organization claims that an AI system will reduce administrative processing time, the evaluator should establish current processing times and define how post-implementation performance will be measured. Without a baseline, claims of improvement may be difficult to verify.
14.6 Compatibility
Compatibility concerns the degree to which a technology fits an organization's existing values, processes, policies, infrastructure and professional practices.
A technology that is highly effective in one organization may be difficult to implement in another because the organizational environments differ. Compatibility therefore includes technical compatibility, workflow compatibility, cultural compatibility, policy compatibility and professional compatibility.
A system requiring fundamental changes to established workflows may generate greater implementation risk. However, incompatibility should not automatically be interpreted as a reason for rejection. Sometimes technological transformation is intended to change existing practices. The appropriate question is whether the organization has sufficient capacity to manage the required transformation.
Compatibility assessment should therefore distinguish between manageable adaptation and fundamental organizational disruption.
14.7 Complexity
Complex technologies may require specialist skills, extensive training, technical support, organizational restructuring and continuous maintenance. Complexity can increase implementation costs and may create additional opportunities for human error.
The important issue, however, is not simply whether a technology is objectively complex. Complexity should be considered in relation to organizational capability. A technology that appears highly complex to a small organization with limited technical expertise may be routine for a large institution with a mature information-technology department.
Technology evaluation should therefore assess the relationship between technological complexity and organizational competence.
Complexity also has a governance dimension. When technologies become increasingly complex, it may become more difficult for managers and users to understand how decisions are generated. This is particularly important for artificial intelligence, automated decision systems and advanced analytics.
14.8 Trialability
Trialability refers to the extent to which an organization can experiment with a technology before committing to full-scale implementation.
Pilot projects, sandbox environments, prototypes, controlled trials and limited deployments can reduce uncertainty. They allow organizations to identify technical problems, workflow disruptions, user concerns, security vulnerabilities and unexpected costs before large-scale investment occurs.
Trialability is particularly valuable when the consequences of failure are substantial. A university introducing an AI-based student-support system, for example, may begin with a limited pilot involving selected departments before extending the system institution-wide.
Pilot projects should nevertheless be designed carefully. A poorly designed pilot may produce misleading evidence. The pilot should therefore specify its objectives, evaluation criteria, duration, participating users, risks, data requirements and decision rules for continuation or modification.
14.9 Observability
Observability refers to the extent to which the benefits or consequences of an innovation can be seen and demonstrated. Organizations are generally better positioned to evaluate technologies when evidence of performance is visible and measurable.
Pilot projects should therefore produce meaningful evidence rather than simply demonstrating that a technology can function. The organization should investigate whether the technology produces the intended outcomes, whether users actually adopt it, whether unexpected consequences emerge and whether the financial and operational assumptions remain realistic.
Observability also supports organizational learning. Visible evidence allows decision-makers to communicate results, refine implementation strategies and determine whether scaling is justified.
14.10 Organizational Capacity
Organizational capacity refers to the resources and capabilities available to implement and sustain a technology. It includes financial resources, infrastructure, human resources, knowledge, leadership, management capability, operational systems and institutional support.
Capacity should be considered both in the short term and over the entire technology lifecycle. An organization may have sufficient resources to purchase a system but lack the financial capacity to maintain it for ten years. Similarly, an institution may have enough employees to implement a technology but insufficient personnel to provide long-term technical support.
Capacity assessment should therefore include acquisition, implementation, operation, maintenance, upgrading, security, training, monitoring and eventual replacement.
14.11 Leadership
Leadership plays an important role in technology adoption because leaders establish strategic direction, allocate resources, communicate priorities, assign accountability and provide organizational legitimacy.
Effective leadership does not mean simply announcing that a technology will be adopted. Leaders should understand the evidence supporting the technology, the uncertainties surrounding it and the risks associated with implementation. They should also establish mechanisms through which concerns can be raised and investigated.
Technology leadership therefore involves evidence-informed decision-making. Leaders should ask what problem the technology is intended to solve, what alternatives exist, what evidence supports expected benefits, what risks are present and what organizational capabilities are required.
Leadership also has an important ethical responsibility. Where technology can affect employees, students, patients, customers or citizens, organizational leaders should ensure that implementation is subject to appropriate governance and accountability.
14.12 Organizational Culture
Organizational culture influences how people respond to technological change. A culture that supports learning, experimentation, collaboration, evidence and responsible innovation may facilitate adoption.
However, a culture that discourages questioning may create significant risks. Employees may hesitate to report technological failures or challenge automated decisions. This is particularly concerning when organizations depend upon high-impact technologies.
A healthy innovation culture should therefore combine openness to experimentation with willingness to question evidence and identify risks. Responsible innovation is not equivalent to accepting every new technology. It involves creating an environment in which technological possibilities can be explored while concerns can be raised without inappropriate organizational pressure.
14.13 Skills and Competence
Technology adoption frequently creates new competence requirements. These may include data literacy, artificial-intelligence literacy, cybersecurity awareness, systems thinking, technical maintenance, analytical capability, digital communication and ethical decision-making.
The skills required will depend upon the technology and the roles of different users. A technical administrator may require advanced configuration skills, while a general employee may require sufficient understanding to use the system appropriately and recognize potential errors.
Training should therefore be considered part of the technology's total cost rather than as an optional activity. Training may include initial orientation, technical instruction, role-specific education, cybersecurity awareness, ethical guidance and continuing professional development.
In high-impact environments, competence should also be assessed after training. Completion of a training programme does not necessarily demonstrate operational competence.
14.14 Infrastructure
Infrastructure includes hardware, software, networks, electricity, connectivity, data systems, physical facilities and technical support.
Technology evaluation should identify infrastructure dependencies before adoption. A cloud-based system may depend upon reliable connectivity. An AI system may depend upon substantial computing capacity and high-quality data. An automated manufacturing system may require specialized equipment and environmental controls.
Infrastructure assessment should also consider resilience. Backup systems, redundancy, disaster recovery, cybersecurity and continuity planning may be necessary where technology becomes critical to organizational operations.
14.15 Change Management
Technology adoption frequently requires behavioural and organizational change. Employees may need to modify workflows, develop new skills, communicate differently or assume new responsibilities.
Kotter (1996) emphasizes elements such as establishing urgency, building coalitions, developing a vision, communicating change, empowering action and institutionalizing new practices. Although change-management models should not be applied mechanically to every organization, they demonstrate the importance of treating implementation as a human and organizational process.
Change management should also recognize that organizations contain multiple stakeholder groups with different interests. Senior managers may focus on strategic value, technical staff may focus on system performance and security, employees may focus on workload and professional autonomy, while customers or students may focus on accessibility and service quality.
Effective implementation therefore requires communication across these different perspectives.
14.16 Stakeholder Readiness
Stakeholder readiness may vary substantially within the same organization. Senior leadership may be highly supportive while operational employees remain uncertain. The IT department may possess substantial technical capability while faculty members or administrative employees require additional training.
For example, in a university, senior leadership may demonstrate high readiness, the IT department may demonstrate high technical readiness, academic staff may demonstrate moderate readiness, students may demonstrate varying levels of readiness, and administrative personnel may require additional support.
Such differences should be identified before implementation. A single institutional readiness score can conceal important variations among stakeholder groups.
Stakeholder readiness assessment should therefore investigate knowledge, attitudes, perceived benefits, concerns, skills, workload implications and willingness to participate.
14.17 Resistance to Technology
Resistance should not automatically be interpreted as irrational opposition to innovation. Resistance may represent legitimate concerns about workload, job security, privacy, professional autonomy, training, implementation quality, cost or organizational priorities.
Employees may also resist technologies because previous implementation projects failed to deliver promised benefits. In such cases, resistance may reflect organizational learning rather than unwillingness to innovate.
Evaluators should therefore investigate the underlying causes of resistance. A useful distinction can be made between resistance arising from misinformation, resistance arising from inadequate communication and resistance arising from legitimate structural concerns.
This approach can transform resistance into an information source. Concerns raised by users may reveal weaknesses that were overlooked during initial technology evaluation.
14.18 Technology Acceptance
The Technology Acceptance Model proposed by Davis (1989) emphasizes perceived usefulness and perceived ease of use as important determinants of technology acceptance. These concepts remain relevant because users are more likely to adopt technologies that they perceive as useful and manageable.
Later models expanded this perspective. Venkatesh et al. (2003), for example, developed the Unified Theory of Acceptance and Use of Technology, incorporating constructs such as performance expectancy, effort expectancy, social influence and facilitating conditions.
Technology-acceptance models can provide useful evidence concerning user behaviour, but they should not be treated as complete organizational evaluation frameworks. Acceptance does not necessarily demonstrate safety, effectiveness, ethical legitimacy or long-term sustainability.
An organization should therefore distinguish among technical feasibility, organizational readiness, user acceptance and responsible governance.
14.19 Digital Capability
Digital capability refers to the organizational ability to use digital technologies effectively, securely and strategically.
It can include digital infrastructure, data governance, technology leadership, employee skills, cybersecurity, innovation processes, systems integration and digital strategy.
Organizations increasingly require digital capability not only to operate individual technologies but also to manage interconnected technology ecosystems. Cloud platforms, AI systems, enterprise applications, analytics, Internet-of-Things devices and communication systems may depend upon one another.
Digital capability should therefore be assessed before large-scale digital transformation. An organization with fragmented data systems, weak cybersecurity and limited technical expertise may encounter significant implementation problems even when the selected technology is mature.
14.20 Organizational Readiness Matrix
Organizational readiness can be evaluated across several dimensions. Leadership readiness may range from limited support, through general support, to strong and sustained sponsorship. Skills readiness may range from significant capability gaps to partial capability and eventually strong organizational competence.
Infrastructure readiness may similarly range from inadequate infrastructure through partially sufficient infrastructure to fully adequate infrastructure. Financial readiness can range from uncertain funding through available funding to secure and sustainable financing.
Cultural readiness can range from organizational resistance through mixed attitudes to a strongly supportive culture. Governance readiness may range from weak arrangements through developing structures to established governance mechanisms.
Data readiness can range from poor-quality or inaccessible data through moderate capability to strong data governance and data quality. Finally, change capability can range from low capacity to manage organizational transformation, through moderate capability, to high institutional capacity for sustained change.
The purpose of such a matrix is not necessarily to reduce readiness to a single score. Rather, it identifies areas of strength and weakness and helps organizations determine what capability development is required before adoption.
14.21 Adoption Risk
Adoption risk arises when the conditions necessary for successful implementation are not adequately understood or managed. Risks may include unrealistic expectations, insufficient resources, inadequate training, weak governance, poor integration, employee resistance, cybersecurity weaknesses, technology failure and dependence upon vendors.
A technology-adoption risk register can provide a structured mechanism for identifying these risks. Each risk can be examined in terms of its source, potential consequences, likelihood, existing controls, responsible owner and proposed mitigation.
Importantly, adoption risk should not be assessed only before implementation. New risks may emerge during deployment. Consequently, adoption risk management should continue throughout the technology lifecycle.
14.22 Total Adoption Cost
The purchase price of a technology rarely represents its total organizational cost. A comprehensive assessment should consider acquisition, implementation, integration, training, change management, maintenance, cybersecurity, governance, monitoring, upgrades, user support and eventual replacement.
There may also be indirect costs associated with temporary productivity reductions during implementation. Employees may require time to learn new systems, processes may initially become slower, and existing systems may need to operate alongside new systems during a transition period.
Technology evaluation should therefore consider the total cost of ownership and total cost of adoption rather than focusing exclusively on acquisition expenditure.
14.23 Technology and Work
Technology can transform work in multiple ways. It may automate certain tasks, augment employee capabilities, create new occupational roles, eliminate some activities, redistribute responsibilities and alter professional identities.
Autor (2015) emphasizes that technological change should not be understood simply as a binary choice between jobs and no jobs. Technologies can substitute for particular tasks while complementing other tasks performed by workers.
Organizations should therefore conduct task-level analysis rather than simplistic job-level analysis. The relevant question is often not whether an occupation will disappear but how the composition of tasks within that occupation may change.
This distinction is particularly important for artificial intelligence. AI may automate information retrieval, document classification, pattern recognition or routine analysis while increasing the importance of human judgement, communication, contextual interpretation and ethical oversight.
14.24 Human-AI Collaboration
The adoption of artificial intelligence requires particular attention to the relationship between human and machine decision-making. Organizations should examine whether AI supports human judgement, creates excessive dependence, changes accountability or alters professional expertise.
The goal should not automatically be maximum automation. In some contexts, human augmentation may produce a more appropriate balance between technological capability and human responsibility.
For high-impact decisions, organizations should determine when human review is required, what information decision-makers receive, how errors can be challenged and who remains accountable for outcomes.
Human-AI collaboration should therefore be evaluated as a socio-technical arrangement rather than simply as an AI-performance question.
14.25 Organizational Learning
Technology adoption should generate organizational learning. Organizations should systematically document what was expected, what occurred, which assumptions were correct, which assumptions were incorrect and what changes are required.
Learning can occur through pilot evaluations, user feedback, incident reporting, performance monitoring, audits and post-implementation reviews.
This creates a continuous learning cycle:
Implementation → Evidence → Reflection → Adjustment → Learning → Improvement → Re-evaluation
Organizations that treat implementation as a one-time project may fail to capture important lessons. Organizations that treat technology adoption as a continuous learning process can adapt more effectively as technologies and organizational conditions change.
14.26 Vendor Dependence and Technology Lock-In
Technology adoption can create dependence upon vendors. Organizations may become reliant upon proprietary software, specialized hardware, subscription models, cloud platforms or vendor-specific data formats.
Technology evaluation should therefore examine interoperability, portability, contractual conditions, data ownership, exit costs and availability of alternative providers.
Vendor lock-in can become particularly significant when an organization integrates multiple systems into a single technological ecosystem. Changing one component may subsequently require changes to several interconnected systems.
Long-term organizational readiness therefore includes the capacity to manage technological dependence and maintain strategic flexibility.
14.27 Data Readiness
Many contemporary technologies depend upon data. Artificial intelligence, analytics, decision-support systems and automated processes may perform poorly when data are incomplete, inaccurate, inconsistent or poorly governed.
Data readiness should therefore include data availability, quality, relevance, accessibility, security, privacy, interoperability and governance.
Organizations should also identify who owns, manages and is accountable for organizational data. Data governance becomes especially important when information is shared across departments, external vendors or cloud platforms.
14.28 Cybersecurity Readiness
Increasing technological dependence creates corresponding cybersecurity requirements. Organizational readiness should therefore include the ability to protect systems, detect threats, respond to incidents and recover from disruptions.
Cybersecurity readiness involves technical controls but also human behaviour. Employees require awareness of phishing, authentication, password management, data handling and incident reporting.
Organizations should therefore evaluate cybersecurity as an organizational capability rather than treating it solely as an IT responsibility.
14.29 Ethical and Governance Readiness
Organizations adopting emerging technologies may face ethical questions concerning privacy, fairness, autonomy, transparency, accountability, discrimination, surveillance and human oversight.
Ethical readiness requires more than a general statement of organizational values. Institutions need procedures through which ethical concerns can be identified, assessed and addressed.
Governance readiness may include policies, committees, approval procedures, audit mechanisms, accountability structures and reporting systems. The appropriate arrangements depend upon the technology and its consequences.
High-impact technologies require particularly clear governance because errors or misuse may produce substantial consequences.
14.30 Sustainability of Technology Adoption
Organizational readiness should also include long-term sustainability. An organization may successfully implement a technology but fail to maintain it because funding declines, skilled personnel leave, infrastructure becomes obsolete or vendor support ends.
Sustainability assessment should therefore consider the full expected lifecycle. Questions should include whether the organization can continue funding the system, maintain required skills, replace obsolete components, manage environmental consequences and adapt the technology as organizational needs change.
This connects organizational readiness with the sustainability principles developed in Chapter 13.
14.31 Technology Adoption Lifecycle
A practical organizational technology-adoption process can begin with problem identification. The organization should first define the problem or opportunity rather than starting with a particular technology.
Technology scanning can then identify possible technological responses. Preliminary assessment should examine technical feasibility, evidence, cost, risks and alternatives.
Stakeholder consultation should identify concerns, requirements and readiness conditions. A detailed AMTEF evaluation can then examine technical, functional, economic, organizational, human, social, ethical, environmental, security and governance dimensions.
A pilot can subsequently be implemented where appropriate. The organization can use pilot evidence to conduct a more detailed readiness assessment and identify remaining capability gaps.
Implementation can then proceed at an appropriate scale, followed by monitoring, evaluation and possible scaling. Reassessment should occur periodically because technology, organizational conditions, costs, risks and stakeholder expectations can change.
The complete process can therefore be expressed as:
Problem identification → Technology scanning → Preliminary assessment → Stakeholder consultation → AMTEF evaluation → Pilot → Readiness assessment → Implementation → Monitoring → Scaling → Reassessment
14.32 Case Study: University AI Adoption
Consider a university that decides to introduce artificial intelligence across administrative and academic functions. The technological readiness of available AI systems may be relatively high, but organizational readiness may initially be moderate.
The university may require an institutional AI policy, faculty development, student guidance, assessment redesign, data-governance arrangements, cybersecurity controls, procurement standards and academic-integrity procedures.
The university should also determine where AI use is appropriate and where additional human oversight is required. For example, AI may support administrative communication, learning resources or data analysis, while decisions affecting academic progression, disciplinary matters or other high-impact outcomes may require clearly defined human accountability.
The appropriate organizational response is therefore neither automatic rejection nor immediate institution-wide deployment. A more systematic process involves identifying capability gaps, conducting controlled pilots, collecting evidence, consulting stakeholders, strengthening governance and progressively expanding implementation where evidence supports doing so.
This case demonstrates the difference between technology readiness and organizational readiness. A university can have access to highly capable AI systems while still needing substantial institutional development before responsible adoption can occur.
14.33 Organizational Readiness Assessment
A comprehensive readiness assessment should examine leadership, strategy, resources, people, infrastructure, culture, governance, risk and change capability.
Leadership assessment should determine whether senior decision-makers understand the technology, its evidence base, its limitations and its strategic implications. Strategy assessment should determine whether adoption is connected to clearly defined organizational objectives rather than driven solely by technological enthusiasm.
Resource assessment should establish whether adequate financial, human and technical resources are available. People assessment should examine whether employees possess the necessary competencies or whether training and recruitment are required.
Infrastructure assessment should determine whether existing systems can support the technology. Cultural assessment should examine whether the organization supports learning, experimentation, questioning and responsible innovation.
Governance assessment should identify whether responsibilities, policies, oversight and accountability mechanisms are established. Risk assessment should identify technical, financial, operational, ethical, cybersecurity and reputational risks.
Finally, change-capability assessment should determine whether the organization can manage the behavioural and structural changes required by implementation.
14.34 Technology Adoption and Organizational Strategy
Technology adoption should be connected to organizational strategy. Organizations sometimes acquire technologies because they are fashionable, because competitors have adopted them or because vendors describe them as transformational.
A strategic approach begins with organizational objectives and then considers whether technology can contribute to achieving them.
This distinction is particularly important in the context of artificial intelligence and digital transformation. The existence of a technological capability does not establish that the capability addresses an important organizational problem.
AMTEF therefore encourages the sequence:
Organizational problem → Desired outcome → Evidence requirements → Technology alternatives → Evaluation → Adoption decision
rather than:
New technology → Search for a problem to solve
The first sequence reduces the risk of technology-driven decision-making that lacks a clearly established organizational purpose.
14.35 Technology Portfolio Management
Large organizations rarely operate a single technology. They manage portfolios consisting of legacy systems, emerging technologies, experimental projects, cloud platforms, information systems and infrastructure.
Technology evaluation should therefore consider interactions among technologies. Introducing one system may create dependencies upon another. Replacing a legacy system may affect data structures, cybersecurity, workflows and employee competencies.
Portfolio evaluation can therefore help organizations identify duplication, technological debt, excessive vendor dependence, security gaps and opportunities for integration.
The portfolio perspective also encourages organizations to balance investment between maintaining essential infrastructure, improving existing systems and experimenting with emerging technologies.
14.36 Technology Failure and Post-Implementation Evaluation
Not every technology adoption project will achieve its original objectives. Failure may result from technical limitations, unrealistic expectations, poor implementation, insufficient resources, inadequate training, cultural resistance, weak governance or external changes.
Post-implementation evaluation should therefore ask whether the original problem was actually addressed, whether expected benefits were achieved, what unexpected effects occurred and whether the technology remains appropriate.
Importantly, failure should not automatically be attributed to the technology itself. A technically capable system can fail because the organizational implementation environment was inadequate.
Post-implementation evaluation therefore provides important evidence for improving future technology decisions.
14.37 AMTEF Organizational Readiness Model
The organizational component of AMTEF can be represented through several interconnected dimensions. Strategic alignment asks whether the technology addresses an important organizational objective. Leadership readiness examines sponsorship and accountability. Resource readiness evaluates financial and human capacity. Infrastructure readiness considers technical and physical systems.
Human-capability readiness examines knowledge, skills and training. Cultural readiness considers attitudes toward innovation, learning and change. Process readiness examines workflow compatibility. Data readiness considers data quality, accessibility and governance.
Governance readiness evaluates policies and accountability. Risk readiness considers whether the organization can identify and manage major risks. Finally, sustainability readiness considers whether the organization can maintain, adapt and eventually retire the technology.
The model can therefore be expressed conceptually as:
Technology capability → Strategic alignment → Leadership → Resources → Infrastructure → People → Culture → Processes → Data → Governance → Risk management → Sustainability → Responsible adoption
The sequence should not be interpreted as strictly linear. These dimensions interact continuously. Weakness in one dimension may affect several others.
14.38 Research Questions
Research into organizational readiness can examine how readiness influences technology adoption and whether different dimensions of readiness have different effects under different technological conditions. Researchers can investigate how technology maturity and organizational readiness should be evaluated together and how organizations can distinguish technological limitations from implementation failures.
Further research can investigate the causes of technology-adoption failure and identify the relative contribution of leadership, culture, skills, infrastructure, resources and governance. Another important area concerns resistance to technology and the distinction between legitimate resistance and barriers arising from misinformation or inadequate communication.
Research should also examine how workforce transformation can be incorporated into technology evaluation. This is particularly important as artificial intelligence and automation alter the composition of tasks across professional and administrative occupations.
Additional research can explore how organizational readiness changes over time and whether readiness should be treated as a fixed characteristic or as a dynamic capability that can be deliberately developed.
14.39 Chapter Summary
Technology adoption is fundamentally an organizational process. Technical maturity does not automatically create organizational readiness, and commercial availability does not establish implementation capability.
Technology readiness concerns the maturity and demonstrated capability of a technology, whereas organizational readiness concerns the capacity of an organization to implement, operate, govern, sustain and evaluate that technology.
Successful adoption requires attention to leadership, strategy, financial resources, infrastructure, skills, organizational culture, processes, data, governance, cybersecurity and change management. User acceptance is important, but acceptance alone does not establish technical effectiveness, ethical legitimacy or sustainability.
Resistance should also be interpreted carefully. It may reveal legitimate concerns concerning workload, professional autonomy, privacy, security, training or previous implementation failures. Consequently, stakeholder feedback should form part of the evidence base for technology evaluation.
The total cost of technology adoption extends beyond acquisition. Implementation, integration, training, cybersecurity, maintenance, governance, monitoring, upgrading and eventual replacement must all be considered.
The adoption of AI and automation further demonstrates the importance of evaluating tasks rather than simply predicting whether entire occupations will disappear. Technology may substitute for certain tasks while complementing others and creating new forms of professional activity.
The central AMTEF principle emerging from this chapter is therefore that responsible technology adoption requires alignment among technological capability, organizational readiness, evidence, governance, human capability and sustainability.
14.40 Discussion Questions
What is the fundamental difference between technology readiness and organizational readiness, and why is the distinction important for technology evaluation? Why can a technically mature technology fail when introduced into an organization? How should organizational culture influence the implementation of emerging technologies? What factors should be considered when evaluating resistance to technological change? How can organizations determine whether resistance represents legitimate concern, inadequate communication or insufficient training? What should be included when calculating the total cost of technology adoption? Why should training be treated as part of technology evaluation rather than as an activity that occurs after technology selection? How should leadership influence responsible technology adoption? Why is stakeholder readiness likely to differ among departments and professional groups within the same organization? How can organizations evaluate the balance between automation and human augmentation? What role should cybersecurity and data governance play in organizational readiness? How can universities evaluate their readiness for artificial-intelligence adoption? Finally, how can the AMTEF framework help organizations move from technological enthusiasm toward evidence-based, sustainable and responsible technology adoption?