Your Mileage May Vary: Case Study of a Robotic Telepresence Pilot Roll-out for a Hybrid Knowledge Work Organisation

Authors: Andriana Boudouraki, Joel E. Fischer, Stuart Reeves, Sean Rintel
Venue: CHI 2023

AThe study

Case study of a three-month pilot of mobile telepresence robots at a corporate research lab in the UK. The robots were meant to connect remote and on-site employees.

  1. Five robotsFive Double 3 robots, each a video call on a remotely driven base, one for each floor of the lab's building.
  2. Weeks of preparationSeveral weeks of overlapping work with health and safety, IT, facilities and other teams.
  3. Three-month pilotEmployees were invited through emails, posters and team presentations, and 15 signed up.
  4. Informal surveysNon-adopters around the office were informally surveyed, and remote users were asked why they stopped.

BThe roll-out

  1. Assess safetyHealth and safety assessors tried the robots remotely instead of visiting, and assessed potential hazards.
  2. Make the robots heardBells taped to the wheels chime as they turn, so a blind employee can tell when a robot is nearby.
  3. Control accessA security group controls who has access to the robots.
  4. Place the docksOne robot and its dock go on each floor, placed with care.
  5. Inform usersWritten and video instructions explain how to sign up and drive a robot.

The lab bought the robots and prepared the building for them. It did not build the robots.

CWhat the study found

Preparing the roll-outwork needed before anyone drove a robot

  • Safety assessors who tried the robots remotely rated all potential hazards as low risk.The assessors saw each other as robots in the office, so they saw both the remote user's view and the on-site view.
  • Bells on the wheels let a blind employee hear when a telepresence robot was nearby.The robots move almost silently. Sighted on-site employees also found the bells useful, having found the robots' stealthy movement unsettling.
  • Security of the telepresence robots could not be assured to the lab's standard.The robots give remote users mobile access to the building without passing physical security. There is no direct way to check who is at the remote end.

During the pilotwho used the robots, and why others did not

  • Of 15 employees who signed up, five never used the telepresence robots.Two used them once, and four used them a few times each but eventually stopped.
  • Non-adopters said they saw no reason to roam the office remotely.From an informal survey. Non-adopters also found sign-up complicated. Users were put off by poor audio and video, few suitable occasions and running a parallel video meeting.
  • The paper suggests hybrid staff socialised on office days and kept home days for focus.Fully remote staff wanted the connection, but fully remote non-adopters were hard to reach, so their views are missing.
  • The paper concludes the effort of using the robots probably outweighed their value.So little use makes this hard to say with certainty.

DKey takeaway

Technology linking remote and on-site staff can be safe and accessible yet still go unused when its value seems not worth the effort. Adoption may need a critical mass of people who share the effort and the benefits.

Made for this site with AI assistance from the verified research brief. It is not the paper's own figure.

Abstract

Organisations wishing to maintain employee satisfaction for hybrid collaboration need to explore flexible solutions that provide value for both remote and on-site employees. In this case study, we report on the roll-out of a telepresence robot pilot at Microsoft Research Cambridge UK to test whether robots would provide enjoyable planned and unplanned encounters between remote and on-site employees. We describe the work that was undertaken to prepare for the roll-out, including the Occupational Health and Safety assessment, systems for safety and security, and the information for employees on safe and effective use practices. The pilot ended after three months, and robot use has been discontinued after weighing the opportunities against low adoption and other challenges. We discuss the pros and cons within this organisational setting, and make suggestions for future work and roll-outs.

Research brief

By Andriana Boudouraki, Joel E. Fischer, Stuart Reeves, and Sean Rintel.

Takeaway: Office telepresence robots went largely unused because their value likely never outweighed the effort. Hybrid staff socialised on office days and wanted home days free for focus. Fully remote staff wanted the connection but found poor audio, few occasions to move around, and robots that couldn't join usual video meetings.

Why this matters

What was known
Earlier studies of mobile robotic telepresence in offices mostly reported users' experiences of temporary use. There have not, to our knowledge, been reports on what is involved in fully implementing a real-world MRP technology roll-out in a knowledge work organisation to directly support day-to-day hybrid work. (§1, p. 1)
What this paper adds
A case study of the preparation for a pilot roll-out of five robots (health and safety, accessibility, security, placement, user information) and of how employees responded. our study attempts to promote a change in the unit of analysis away from the device itself towards the device's organizational, social, situated embedding (§2, p. 2)
Who it matters to
Organisations designing hybrid workplaces and planning telepresence deployments, and researchers studying technology adoption at work. so we hope that the work we present here helps others be more prepared in what to expect (§7, p. 6)

Research questions

Method and data

Design
Case study of an organisational pilot roll-out of mobile robotic telepresence.
Setting
A corporate research lab in the UK, which bought five Double 3 robots, one for each floor of its building.
Participants / data
15 new users signed up. Non-adopters around the office were informally surveyed, and remote users were asked why they stopped.
Duration
The pilot ran for three months. Preparation tasks took several weeks.
Analysis
Descriptive account of the preparation work and of employees' responses, drawing on informal surveys and user comments.

Findings

Questions this paper answers

Do telepresence robots work for hybrid offices?
Not easily. They can be made safe and accessible, but adoption depends on whether the benefit justifies the effort. In a three-month research-lab pilot, most of the 15 who signed up never used them or soon stopped, and the lab discontinued them. Other settings may suit them better. (See §5, p. 4; §5, p. 4; §7, p. 7.)
What does it take to roll out telepresence robots in an office?
Several weeks of work with health and safety, IT and facilities. It covered a risk assessment, accessibility fixes such as bells on the wheels, and rules for moving abandoned robots. It also covered a security group for access, careful dock placement, and written and video instructions. (See §4.1, p. 2; §4.2, p. 2.)
Why might a workplace technology fail even when it works as designed?
Because adoption depends on effort versus value for everyone involved. A telepresence robot needs remote and on-site colleagues, bystanders and building staff to support it. Without a culture of use, a remote user may log in and find no one to interact with and nothing to do. (See §5, p. 4; §7, p. 7.)
Are telepresence robots a security risk for companies?
They can be. They give a remote user mobile access to a building without passing physical security, and there is no direct way to control who is at the remote end. After a pilot, one research lab paused use until enhanced security processes exist. (See §4.4, p. 3.)

Quantitative results

MeasureResultWhere
Robots purchasedfive Double 3 robots§2, p. 2
New users who signed up15 new users in total§5, p. 4
Robot speed limit1.8mph§4.3, p. 3

Contributions and implications

Limitations

›

Concepts

Mobile Robotic telePresence (MRP)
Videoconferencing on a remotely driven mobile robot, letting a remote user move around an office. (§1, p. 1)
Effort vs. value
Grudin's explanation for why systems for collaborative work fail: the disparity between the work required to make a system function (and who has to do that work) and its benefits (and who receives them) (§6.1, p. 5)
Critical mass
Enough users for a communication technology to be adopted. For a telepresence robot, that means more than the remote user: However it is a medium for interactions, and therefore both the remote and on-site parties need to collaborate to make it work, as well as all peripheral members such as bystanders and building management. (§6.2, p. 5)
Non-use
Drawing on Satchell and Dourish, the varied reasons people do not adopt a technology, from disinterest to active resistance. Why they matter: Non-users' perspectives can teach just as much as those of users. (§6.3, p. 6)

Figures

A telepresence robot with a sign on its back, enlarged: 'Does this robot look abandoned?' and numbered steps to check no one is using it, lift it by the pole, place it near a wall and Wi-Fi hub, and whom to contact.
Figure 3: Instructions posted on the back of the robots, for onsite employees encountering abandoned robots in the office From the paper, Fig. 3, p. 3.
Close-up of a robot's wheel with a small bell taped inside it, so the robot chimes as it moves.
Figure 2: Cat bells were attached to the robots' wheels From the paper, Fig. 2, p. 3.

How to cite

Andriana Boudouraki, Joel E. Fischer, Stuart Reeves, and Sean Rintel. 2023. Your Mileage May Vary: Case Study of a Robotic Telepresence Pilot Roll-out for a Hybrid Knowledge Work Organisation. CHI 2023. https://doi.org/10.1145/3544549.3573871

This brief was prepared with AI assistance and published by Sean Rintel. It is not the authors' published text. Page numbers refer to this PDF.

BibTeX

@inproceedings{boudouraki2023your,
author = {Boudouraki, Andriana and Fischer, Joel E. and Reeves, Stuart and Rintel, Sean},
title = {Your Mileage May Vary: Case Study of a Robotic Telepresence Pilot Roll-out for a Hybrid Knowledge Work Organisation},
booktitle = {CHI 2023},
year = {2023},
month = {April},
publisher = {ACM},
url = {https://doi.org/10.1145/3544549.3573871},
doi = {10.1145/3544549.3573871},
}