Ecaveo Working Papers, AI Adoption: The Higher-Order Issues
The Unit of Adoption
why Organisations Adopt Configurations, Not Models
Fractional Head of AI, Ecaveo
Abstract
Organisations do not adopt models. They adopt configurations of seven elements, of which the model is one, and because the other six vary across a business the same model can succeed at a desk and fail on a warehouse floor with nothing about the model changing. This paper names those elements as capability, interface and modality, channel and device, user capability, task, physical setting and organisational legitimacy, and groups them into the tool, the route, the work and the institution. It argues that the acceptance tradition, for all its explanatory power, compresses the material circumstances of use into a belief, so it can record that staff felt unsupported without capturing that the screen was small and their hands were full. A six-step pilot protocol follows: describe the baseline across all seven elements, vary one at a time, run in the setting where the work happens, keep a configuration log, read results by configuration, then adopt a named configuration with an owner. Pilot results should carry their configuration as laboratory results carry their conditions. The model is a synthesis and has not been tested as a whole.
Read the paper
This is the reading edition, complete and unabridged. The designed edition, with the full illustrated layout, is available from the original publication page.
Cite this paper
Download RIS Download BibTeX RIS opens in Zotero, Mendeley, EndNote and RefWorks
BibTeX, inline
@techreport{forrest2023theunitofado,
author = {Forrest, Paul},
title = {The Unit of Adoption: why Organisations Adopt Configurations, Not Models},
institution = {Ecaveo Services Ltd},
series = {Ecaveo Working Papers, AI Adoption: The Higher-Order Issues},
year = {2023},
month = {03},
pages = {26},
url = {https://papers.ecaveo.com/the-unit-of-adoption-why-organisations-adopt-configurations-not-models/}
}