Welcome to ARIIA First Nations Hub
Aboriginal and Torres Strait Islander people should be aware that this website contains images, voices and names of deceased persons.
Aboriginal and Torres Strait Islander people should be aware that this website contains images, voices and names of deceased persons.
During the implementation phase of a technology project, a product is formally introduced and begins to be used under real-world conditions and circumstances by its intended users. [1] Depending on the complexity of the technology, this phase might require a range of structured activities aimed at increasing acceptance by end-users and integrating it into routine use where it may deliver on its promised benefits. [2]
Effective implementation requires careful planning to ensure any potential barriers to success are anticipated, and either avoided or reduced. [3] Ideally, planning for implementation begins in parallel with, or is firmly based on, the needs assessment and design phases. [1, 4] This ensures the focus of implementation remains on users and their needs, as well as the organisation's strategic goals. [3, 5] Ongoing monitoring activities throughout the implementation project are also critical for identifying problems as they arise and adapting the product or adopting processes to counter them. [6]
A technology implementation project aims to introduce a new product in a way that increases its chances of being used as intended and delivering on its expected benefits. [3] All activities up to this point—the needs assessment, the business case, and the design and testing process—have been laying the groundwork for successful implementation.
In a well-planned implementation project, end-users will have a clear understanding of the purpose of a technology and how it relates to their needs, values, and goals. At a very early stage, the project team will have identified potential barriers to success, such as staff or care recipient resistance, and put strategies in place to counter them. Therefore, at the end of the implementation phase, the product is more likely to be:
Potential barriers to successful implementation exist across all phases of a technology acquisition (or development) project. [8] Some of the common individual, organisational, and technology-related barriers are outlined below, followed by suggestions for reducing their risk for successful implementation of the product.
Various human factors, such as how people think and feel about technology, can affect how they interact with a new product and whether they accept and use it. [9]
People can have negative attitudes about technology, either generally or about a specific product. This may be for a range of reasons. Some may expect a technology to be difficult to use without having tried it, or based on negative past experiences. [10] Others might not believe in its promised benefits, feel it is not suitable for them, or expect it to be burdensome to engage with. [9] Staff may also have negative attitudes towards technology if they view it as a threat to their job security. [11]
People receiving care may worry about increased dependence on technology or fear a particular type of technology, such as a monitoring device with a built-in camera, might violate their privacy. [12] Some may view visible alarms or monitors worn on the body as stigmatising evidence of decline. [8] Informal carers may resist working with a technology for reasons related to ethnicity or culture, or if they perceive it to represent an additional workload [4], (e.g., constantly monitoring reminder systems). [9] People with dementia may not see a product as appropriate for their needs or expect more from it than what it can realistically offer. [9]
People with limited previous exposure to technology are also less likely to want to engage with it. [10] They may expect it to be challenging or fear the consequences of making mistakes. Lack of digital literacy (or ‘tech savviness’) can be a major barrier to technology adoption that should be assessed and planned for within the aged care setting. [8]
People may reject or be reluctant to engage with a technology for ethical reasons. Clinical staff might, for example, view the introduction of telehealth consultations as a threat to their professional autonomy or a risk to patient safety due to the inability to conduct an accurate physical examination. Care recipients or their informal carers might view constant monitoring or tracking technologies as restricting their freedom or privacy. [9] Technologies may also raise personal or data security concerns. [13] Older people may see some overt devices designed to keep them safe as drawing attention to their limitations and dependency, thereby stigmatising, or infantilising them. [9] For many older people in aged care, decisions around the use of technologies may be made for them, rather than involving them, thereby reducing their autonomy and freedom to choose. [14]
In the aged care context, technologies to be used by the care recipient may be rejected due to physical and/or cognitive decline, frailty, or vision or hearing impairment. [9] It is therefore important to introduce technologies that have been specifically designed for older people and in collaboration with them. This includes people with a range of impairments that may limit their ability to operate a device or engage with a digital program.
An organisation’s structure, culture, procedures, or policy environment can also impede implementation success, often through inadequate planning for this phase.
Strong leadership commitment to a project is shown to be a key factor in implementation success. [15, 16] This support is demonstrated by effective communication regarding the purpose and value of the technology, [6] as well as visible leadership involvement in implementation processes. [17] Leaders can show support by:
Preparing an organisation for change is an important part of planning for the implementation of a new product. [5] This means engaging with those likely to be affected by the introduction of a new technology and communicating about the potential benefits, trade-offs, how the change might affect them, and what the anticipated timeline is. Without this information, people may be less incentivised to adopt the product. [8] Part of the implementation plan should focus on ensuring end-users from each stakeholder group are involved at each stage of the process to improve acceptance and promote a sense of ownership. [15, 19]
If implementation projects are inadequately funded, this may compromise the technical quality of the product or the infrastructure to support it. For example, there may not be enough physical workstations for staff to input data into a new clinical data management system, or newly introduced mobile devices or telehealth might be rendered unreliable by low bandwidth or Wi-Fi blackspots. [6] Funding requests, which form part of the business case, should also allow for more than the capital outlay on the technology. They should factor in ongoing technical support from the vendor (or design support from a developer), [19, 20] the potential time and resources needed to optimise the technology and train end-users, [19] and the capacity for continued monitoring of the product’s use, benefits, and costs. [6]
Implementation efforts need to be underpinned by adequate resources for staff or care recipient training. People also need time to gain confidence and proficiency in using new products. [6] This includes preparing for increased technology engagement by gauging the digital readiness of the workforce or care recipients ahead of implementation. It also includes the provision of responsive mentors, support groups, or champions that people may turn to at the point of need. Without adequate planning for the human factors that hamper uptake, people are unlikely to use a product, or not use it to its full potential.
Implementation projects need to include mechanisms for tracking how well the product has been implemented into the organisation or a care recipient’s routine. This feedback is needed on an ongoing basis to maintain or improve, the fit between the technology and its intended purpose. [10] It is also needed as evidence that the technology provides value for money and should therefore continue to be maintained by the organisation. However, monitoring requires a reasonable period of time [5] as potential benefits may not be immediately apparent. [21]
The project team can obtain valuable information about the use and acceptance of a technology through verbal or written feedback from stakeholders. Meanwhile, objective, clearly defined and measurable indicators may provide evidence of effectiveness. [19] These indicators may be especially illuminating when benchmarked against an old process. For example, an organisation might choose to record:
It is also important to monitor the quality of the implementation process to know if the technology has been implemented successfully, or if more work is required. This might be done by asking end-users and other stakeholders about their perceptions of training and the introduction of new processes. [22] Another evidence theme in this series (Monitoring use over time) provides more information on this topic.
For effective implementation, people must be able to work with the product. Ideally, any flaws in hardware, software, functionality, or content would be detected before the implementation phase if enough attention has been paid to multi-step user testing with real end-users representing all stakeholder groups. [19, 20, 23] However, if the testing phase has been overlooked, the product may not work optimally or be too complex. Design problems that may appear during the implementation phase include:
The implementation phase should not focus solely on the new technology and its functionality. This is also an opportunity to assess any issues end-users are experiencing with it and work with them to resolve them. [25] By anticipating some of the common barriers to implementation success, the project team can devise and document strategies for preventing them or mitigating their impact at the outset.
People may be less resistant to the introduction of a new technology if they understand the reasons why it is needed, how it may benefit them personally, and if it will affect their work or routines. [26] This highlights the importance of using a communication strategy to keep people informed and engaged with a project of this kind, rather than assuming they will automatically understand its goals. This strategy should, ideally, originate with the leadership group and run across the duration of the project. [17] The communication strategy can help to ensure messages are clear, consistent, and appropriately tailored to each stakeholder group. Each message might give the ‘big picture’, reiterate the problem being improved by the technology, and explain how its features and functionality align with the values and needs of individuals and the organisation. [9] Benefits, potential trade-offs, and anticipated timelines should also be described using realistic terms to keep expectations in check. [15, 19] Managing expectations from the start is important as any discrepancies between people’s expectations and actual functionality can lead to a lack of acceptance. [27]
Communication should work in two directions. People are more likely to engage with an implementation project if they believe their input is valued. [28] The perspectives of those closest to the product are also likely to reveal initial issues with processes or something potentially missing in care delivery. [29] For these reasons, the implementation team should consider building feedback mechanisms across all stages of the project that people are aware of and encouraged to use.
Appointing local champions—individuals who volunteer or are appointed to ‘enthusiastically’ promote and facilitate the implementation of an innovation [30]—may also work to overcome resistance in an organisational context. [6] These local leaders might be respected colleagues and end-users rather than management. [19] Ideally, a champion will work between the different levels of an organisation including management, clinical, and information technology (IT) staff groups. [15, 19]
Some staff may be more motivated to adopt a change brought by technology if offered incentives or rewards. [3, 31] These could be in the form of money, prizes (e.g., vouchers), or simple public acknowledgement of their efforts.
An organisation might assess staff ability and readiness for working with digital technologies ahead of an implementation project using a tool such as Be Connected Network’s Digital Skills Checker. Tools of this type can highlight gaps in knowledge that might be targeted for pre-implementation training (e.g., the ability to use an app on an iPad to input resident data).
The digital readiness of the organisation and its overall capacity to support new technologies are also important factors in implementation success. This may require adopting cloud capabilities or introducing or extending broadband and Wi-Fi access across residential facilities. [32]
Another strategy to support people to engage with a product is to give them ample and unpressured time to familiarise themselves with it before the formal implementation stage begins. [10, 19] Lack of time to learn to use a technology effectively has been highlighted as a major barrier to staff, care recipients, and informal carer uptake of new technologies in Australian aged care settings. [14] Allowing people time to practice, play around with the product, ask questions, and make mistakes without consequences, can gradually increase confidence. For example, evidence suggests that people with dementia and their informal carers are more likely to accept and use telehealth technologies if they receive help setting up the equipment at home and are given training and time to familiarise themselves before any scheduled appointment. [33]
Other strategies that are important to helping people engage with a new technology include:
According to Cresswell [5], training during implementation should consume about 40% of the implementation budget but rarely reaches this proportion. This highlights the need to adequately resource the training phase within the business case and planning stage of implementation.
Rather than a single, one-off event, implementation is something that occurs over time in stages. These stages may overlap, and their timing and order will depend on organisational needs and context, as well as the complexity of the project. Some flexibility is needed because unforeseen setbacks, such as product failure, can also send a project back to an earlier stage. [22] One guideline for implementation [22] divides the process into four simple stages:
A documented plan for implementation can keep the project on track and help to anticipate and counter barriers at an early stage. Naturally, more complex technology projects will require more elaborate and detailed plans. The list below provides suggestions for what might be considered in the implementation plan.
Establishing a governance structure for an implementation project that documents lines of responsibility can prevent any confusion over roles, tasks, and resources required during the implementation phase. The governance structure might cover:
For each process during the implementation phase, it may be helpful to document:
In developing a communication strategy within the implementation plan, the project team might consider asking:
In addition to governance and communication plans, the following considerations (many covered in the business case) might be documented in the implementation plan:
If the product is central to operations, it may be important to have a backup plan organised (or pre-planned workarounds) in case the product does not work at all at the implementation stage. [15]
A technology implementation project within an aged care setting may benefit from having an implementation plan in place to guide considerations and processes. This plan may be simple or elaborate, depending on the type of product and the number of people and processes affected by its introduction. There can be no one-size-fits-all approach to successful implementation due to the relationships between the technical, human, and organisational factors in complex care settings such as aged care. [15] However, conducting a needs assessment, developing a business plan, and considering potential barriers and enablers ahead of implementation may improve the likelihood of product uptake and acceptance. [20]
This PubMed topic search is focused on research conducted in aged care settings (i.e., home care and residential aged care). You can choose to view all citations or free full-text articles.