Swift Trust in Distributed Ad Hoc Teams

PDF

Authors
  1. Adams, B.D.
  2. Waldherr, S.
  3. Sartori, J.
  4. Thomson, M.
Corporate Authors
Defence R&D Canada - Toronto, Toronto ONT (CAN);Humansystems Inc, Guelph ONT (CAN)
Abstract
Swift trust is trust developed quickly even without direct and personal experience with another person and has been increasingly posited in the literature to be one way in which members of ad hoc teams can quickly form trust (Meyerson, Weick & Kramer, 1996). This pilot study explored whether the regimental identity of teammates could influence levels of “swift” trust within teams. The secondary focus of this experiment was the impact of potential trust violations. Twenty-four teams of CF reservists each conducted four tactical assault missions in a first-person gaming laboratory. Each 4-person team was composed of 2 CF personnel and 2 confederate researchers (purported to be CF personnel). Members of the team worked in a simulated distributed environment (separated by partitions), and were initially introduced to each other only using a 1 page written profile that described their background and operational experience. Their task in the computer game was to operate as 2 separate fire teams approaching the target area from 2 different sides in order to engage and destroy terrorists. Teammates communicated via radio only but interacted within the simulated mission area through their computer avatars. In order to manipulate regimental identity, the 2 confederate members of the newly formed and distributed team were reported to come from either the same regiment or a different regiment as the actual CF participants. In addition, to investigate whether trust violations affected

Il y a un résumé en français ici.

Keywords
Swift trust;Trust violations;Regimental identity;Violation of trust;Canadian Forces
Report Number
DRDC-TORONTO-CR-2007-139 — Contractor Report
Date of publication
04 Oct 2007
Number of Pages
107
DSTKIM No
CA030416
CANDIS No
528962
Format(s):
Electronic Document(PDF)

Permanent link

Document 1 of 1

Date modified: