Organize workshop
Kenno is a tool that helps identify questions of responsibility in projects that make systematic use of data, digital technology, AI or algorithms.
Kenno is built around thematic modules and a handbook, which together form the basis for a workshop. The modules contain questions on different themes, which are answered through shared discussion in small, multidisciplinary groups. The handbook helps document the discussion, define the necessary actions and return to important questions at different stages of the project.
Kenno is not a box-ticking exercise that gives a ready-made answer to whether a project is responsible or not. The idea behind Kenno is to bring together people from different professional backgrounds to reflect on a project’s goals and impacts, and on whether they are being pursued in appropriate and responsible ways. The value of Kenno comes from shared discussion and shared observations.
Modules

Choices and responsibilities
The module on this theme looks at the fundamental questions of the project: why is the project being carried out, what is it aiming for and what does it seek to achieve? Responsible algorithmic automation also involves identifying responsibilities within the organisation: who decides, who implements, and are the key choices and responsibilities aligned? This module should be covered first, immediately after the Values module, regardless of the other modules chosen or their order.

Automation
The module on this theme looks at the automation being implemented in the project. Automation can be algorithmic or rule-based and can be implemented with different technologies. What matters is that the module explains and builds an understanding of why the automation is being done, how it works and what it is intended to replace.

Data and Data Management
The modules on this theme deal with the data the project needs and uses. Why is data being collected, how are its quality and currency ensured, and how is it used? Data is one of the most important factors behind successful automation, so the module focuses in particular on what makes the data used high-quality for the needs of the automation in question. This also helps examine biases and whether they are desirable or undesirable for the project. Note! The questions on this theme are split across two modules!

Dependencies
The modules on this theme look both at the project's dependencies on other systems and at the dependencies the project creates. Here, systems refers broadly to wholes in which technology, data, people and processes interact: for example information systems, automation solutions, registers, platforms or other digital tools. This module helps map out the consequences of dependencies and ways to prepare for them. Note! The questions on this theme are split across two modules!

Communication
The module on this theme considers how the project's goals, operating principles and impacts are, and should be, communicated to different audiences, such as employees, citizens, customers and users. The questions help consider whether communication aspects have been thought through, and what kind of communication serves the project's goals. At its best, communication builds trust and helps identify and address possible concerns and misunderstandings.

Participation and Transparency
The module on this theme focuses on the impacts of the automation project on stakeholders, meaning employees, citizens, customers and users. The questions help assess who has the opportunity to influence the project's design, implementation and evaluation. The key is to consider how different perspectives are taken into account and how the workings of the automation project can be made transparent to those it affects.

Expertise and Autonomy
The modules on this theme look at how the project and the systems it produces change the organisation's division of labour, the roles of experts and people's ability to use their own judgement. The key questions concern human skills, responsibility and decision-making power in relation to the recommendations or decisions produced by automated systems. An automation project and its impacts often look very different from one role to another, so it is also essential to consider how the impacts on different groups of employees and stakeholders are identified and taken into account. Note! The questions on this theme are split across two modules!

Sustainability
The module on this theme looks at the environmental impacts of the project from the perspective of its entire life cycle. The focus is on the use of energy, hardware and other material resources, and on how the choices made in the project now affect sustainability and resource use over the whole life cycle.

Resistance
The module on this theme considers the criticism, concerns and dissenting views directed at the project. These perspectives may also come up during the workshop. Responsible development involves understanding different views and the reasons behind them. The questions help consider how resistance can be responded to openly and constructively.

Outcome
The module on this theme goes through the conditions for moving forward with the automation project based on the discussion held in the workshop. The observations made are important for the responsibility of the automation project as a whole. Concrete actions may also emerge throughout the workshop, in which case they should be written down immediately in the handbook's documentation templates. This module should be covered last, after the Resistance module, regardless of the other modules chosen or their order.