The context identification tool helps adopters determine the general purpose of the disruptive technology adoption in the public administration and set up the assessment context and the team involved in the process. It helps adopters answer questions such as why adopt a disruptive technology in the first place, what will be the consequences (both positive and negative) and who are the best persons to involve during the adoption process.
Why is important to assess the context drivers
- Will help to understand the different ethical, legal and societal implications and the types of impacts to consider, based on the context driver assessed.
- Will help with the further assessment of the relevant principles and risks in the next phases.
- Will help to better tailor the service in tune with the end-users’ needs.
- Will help understand the cybersecurity needs and other development requirements based on the technology considered.
Stage of adoption | Roles | Methodology |
---|---|---|
Ante-adoption | Overseeing roles, Technical Roles, Engaging roles |
|
Example of context identification table
Context Drivers | Examples of instances | Examples of questions to discuss during the assessment |
---|---|---|
Scope of application | Internal vs External service |
|
The level of service provision | Local or national |
|
The class of the functions of government | Defence, Health, Education, etc. (see COFOG[1]) |
|
The service’s frequency of use | Daily, weekly, monthly, annually |
|
The stakeholders involved/impacted | Public servants, developers, users, society, regulatory bodies |
|
The type of final user | Citizens, data scientists, researchers, public servants |
|
The type of DT adopted | AI, including chatbots, big open data analytics, autonomous devices (e.g. robots) |
|
[1] https://ec.europa.eu/eurostat/statistics-explained/index.php?title=Glos…)
Categorisation
Type of document
Guideline
Login or
create an account to comment.