Most teams are told to "build trust over time." Project teams and taskforces don't have that luxury. They are assembled on demand, expected to coordinate within hours, and often disbanded before anyone learns a colleague's working style. The usual advice, that trust grows slowly through shared history, simply does not fit the way modern work is organised.
And yet these groups often do perform. The explanation lies in a form of trust that behaves differently to the kind we build with long-standing colleagues. Understanding how it works, and how quickly it can collapse, is one of the most useful things a leader of short-lived teams can learn.
In temporary teams there is little time to establish trust, yet many manage the challenge well. Lane4 points to flight crews, healthcare professionals and the military as examples of groups that perform immediately with people they have never met, by building what researchers call "swift trust" rather than waiting for it to develop over time.
The conventional model assumes trust is evidence-driven: we observe someone over many interactions and gradually update our judgement. Swift trust works differently. As the University of Cambridge research repository notes, it draws heavily on roles rather than relationships, with the predictability created by role-bound interactions doing much of the early work that history would normally do.
In practical terms, members extend provisional confidence based on roles, reputation and competence, then calibrate it as evidence arrives. This matters for both sides of the business. For individuals, it reduces the anxiety of walking into a room of strangers and needing to contribute straight away. For organisations, it means a taskforce can start delivering before anyone has had a chance to "gel", protecting momentum on time-sensitive work.
The research points to a small number of conditions that do most of the heavy lifting.
1. Clear roles and genuine interdependence. Research on multi-national disaster teams found that reputation, role and interdependence are central to building swift trust, and that swift trust formation rests on interdependence of tasks and goals, time constraints, professional role focus and central coordination. When each person's expertise is visibly necessary to the shared outcome, trust follows the logic of the task. By contrast, any blurring of roles or responsibilities adds ambiguity, which raises doubt and lowers trust.
2. Visible signs of competence. It is not enough to be an engineer; the Cambridge work suggests we trust the colleague who seems like a skilled engineer able to do the specific task at hand, and that this impression usually requires seeing them perform, even briefly. The practical implication is simple: distribute meaningful tasks early so people can see each other work, rather than saving the "real" collaboration for later.
3. The shadow of the future. Reputation carries weight precisely because people care how they will be seen afterwards. Lane4 argues that the more reliable, consistent and accurate a team's reputation is, the faster temporary members extend trust to it. Reminding people that their conduct here will shape how colleagues speak about them elsewhere quietly encourages trustworthy behaviour.
4. A simple way to signal how each person works. Because time is short, teams rely on quick categorisation of one another. A brief, structured way for members to share how they prefer to communicate, make decisions and receive feedback gives people something more accurate than guesswork to read on day one. This is where a tool such as the HPT by DTS Team Communication Map earns its place: it lets people surface their working style in minutes rather than learning it through trial and error over weeks. Our piece on why communication matters more than ever explores how understanding styles reduces early misunderstandings.
Here is the part leaders most often miss. Swift trust is useful, but it is not sturdy.
Across the literature, the dominant finding is that swift trust is fragile. Work on global virtual teams describes how its cognitive components render it fragile and in need of reinforcement and calibration through action. Research on human-AI teaming puts it plainly: swift trust is assumed provisionally on contextual cues like role and perceived competence, and can erode rapidly when behaviour is unclear, inconsistent, or perceived as unreliable.
It is worth noting the debate is not entirely settled. Some analysis argues swift trust can be fairly resilient rather than fragile, because high task focus and short timeframes reduce the opportunity for violations to occur and the time to dwell on them. The practical reading of both positions is the same: early confidence buys you a window, and what you do inside that window decides whether it holds.
The goal, then, is conversion. Early swift trust needs to be turned into durable, evidence-based trust before the initial impressions fade. Studies of virtual teams suggest the trust you create at the start shapes the trust you end with, meaning high swift trust early tends to support stronger traditional trust later in the project. The bridge between the two is demonstrated reliability: doing what you said you would, when you said you would, and re-contracting openly when circumstances change.
A simple setup routine for new teams
A first-meeting trust kickstart
Converting fragile confidence into durable trust
Swift trust is not a lesser form of trust; it is the right form for teams that must act before relationships exist. Treat it as a head start rather than a finish line. Clear roles, visible competence and simple ways to read one another get a team moving on day one. Reliability, follow-through and honest re-contracting are what keep it moving once first impressions fade.
The question worth sitting with is this: when your next project team forms, will you leave trust to chance and hope rapport arrives in time, or will you design the first hour so confidence is earned, visible, and built to last?