Skip to content

Permission as a Variable: Why the same robot pays off in one plant and fails in another

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

Projects that install the same robot model report labor-productivity gains an order of magnitude apart. Studies of robot adoption stop at the firm or the plant, so the gap between two plants with the same robot sits below the level they measure. Engineering studies stop at the machine. The missing variable sits between them: what a plant allows a specific robot to do on its own, on a specific job. That permission is set after the purchase, by people in the plant. Two plants can set it differently for the same robot, and no survey records it. Whether it moves afterward, as products, shifts and software change, is something this paper proposes to measure. It introduces the Habitat Readiness Score, which reads four organizational conditions for one permitted action against the job's stated requirement, and reports a profile rather than a total. It places the instrument beside safety readiness, which assesses an organization's readiness to manage risk and does not measure one action's permission against a job requirement. An archive of 295 documented robot projects, compiled by Hayashi from public handbooks, shows that the spread inside a single robot model is wide and that the pages do not report the evidence that would explain it. A three-step study is set out. Nothing here is tested. The paper offers the instrument that would make the claim testable. Working paper, version 0.20. Prepared for CORA 2026, the Conference on Robots and Automation, ZBW Leibniz Information Centre for Economics, Kiel, 28 September 2026, Session 2, Diffusion and Productivity. Case data compiled by Professor Ryuichi Hayashi, Kobe Gakuin University, from the METI and JARA Robot Introduction Demonstration Project handbooks, 2016 to 2018, used with his permission. The author has a commercial interest in this area through startup activity he invests in and helps build. JEL: O33, O14, D24, L23.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.