Operations Room: Difference between revisions

From titipi
Jump to navigation Jump to search
mNo edit summary
Line 4: Line 4:
An Operations Room is a situation designed to interrogate the impact of a specific computational infrastructure and its implementations on the operations of a (public) institution, organisation, or collective. Participants with divergent interests, and expertise across scales are invited to study an infrastructure that matters to them and to the (public) institution which deploys it. An Operations Room uses a mix of transdisciplinary methods such as code-inspection, decolonial critical discourse analysis, dependency mapping, creative experiments, and interface analysis. Participants can include engineers, organizers, activists, designers, labourers, accountants, policy people and other users. Together they utilize the prism of "operations" to arrive at an integrated understanding of how a technology manages operations, through what a technology currently does, might do in the future and how it does so. Examples of technologies that could be the subject of an Operations Room: a videoconferencing platform for higher education; a keycard system for managing transactions in refugee camps; a mobile health management tool; a protocol for registering and communicating vaccination status. An Operations Room lasts up to a day and could take place on-line but is ideally physically located in a space relevant to the institution that deploys the technology. Great care is taken in curating the group of participants and mix of methods, preparatory research, selecting tools for documentation, scenography of the room and overall hosting of the situation. An Operations Room can be proposed by an organisation, a concerned individual or follow from a Drop-in Clinic; an outcome of an Operations Room might be a bugreport or a proposal for further participatory research.
An Operations Room is a situation designed to interrogate the impact of a specific computational infrastructure and its implementations on the operations of a (public) institution, organisation, or collective. Participants with divergent interests, and expertise across scales are invited to study an infrastructure that matters to them and to the (public) institution which deploys it. An Operations Room uses a mix of transdisciplinary methods such as code-inspection, decolonial critical discourse analysis, dependency mapping, creative experiments, and interface analysis. Participants can include engineers, organizers, activists, designers, labourers, accountants, policy people and other users. Together they utilize the prism of "operations" to arrive at an integrated understanding of how a technology manages operations, through what a technology currently does, might do in the future and how it does so. Examples of technologies that could be the subject of an Operations Room: a videoconferencing platform for higher education; a keycard system for managing transactions in refugee camps; a mobile health management tool; a protocol for registering and communicating vaccination status. An Operations Room lasts up to a day and could take place on-line but is ideally physically located in a space relevant to the institution that deploys the technology. Great care is taken in curating the group of participants and mix of methods, preparatory research, selecting tools for documentation, scenography of the room and overall hosting of the situation. An Operations Room can be proposed by an organisation, a concerned individual or follow from a Drop-in Clinic; an outcome of an Operations Room might be a bugreport or a proposal for further participatory research.
</onlyinclude>
</onlyinclude>
See for an example: [[Operations Room Hangar]]
[[Category:Methods]]
[[Category:Methods]]

Revision as of 15:52, 13 July 2023

Operations Room

An Operations Room is a situation designed to interrogate the impact of a specific computational infrastructure and its implementations on the operations of a (public) institution, organisation, or collective. Participants with divergent interests, and expertise across scales are invited to study an infrastructure that matters to them and to the (public) institution which deploys it. An Operations Room uses a mix of transdisciplinary methods such as code-inspection, decolonial critical discourse analysis, dependency mapping, creative experiments, and interface analysis. Participants can include engineers, organizers, activists, designers, labourers, accountants, policy people and other users. Together they utilize the prism of "operations" to arrive at an integrated understanding of how a technology manages operations, through what a technology currently does, might do in the future and how it does so. Examples of technologies that could be the subject of an Operations Room: a videoconferencing platform for higher education; a keycard system for managing transactions in refugee camps; a mobile health management tool; a protocol for registering and communicating vaccination status. An Operations Room lasts up to a day and could take place on-line but is ideally physically located in a space relevant to the institution that deploys the technology. Great care is taken in curating the group of participants and mix of methods, preparatory research, selecting tools for documentation, scenography of the room and overall hosting of the situation. An Operations Room can be proposed by an organisation, a concerned individual or follow from a Drop-in Clinic; an outcome of an Operations Room might be a bugreport or a proposal for further participatory research.


See for an example: Operations Room Hangar