How does collective memory coordinate knowledge across group boundaries and differing knowledge domains?

The core mechanism is knowing who knows what

When representatives from different knowledge domains work together, the practical problem is not just sharing information but keeping track of it. A transactive memory system solves this by functioning as a collective memory for knowledge coordination: members develop a shared understanding of which person or subgroup holds which expertise, and they route questions and tasks accordingly [1]. This is less like a shared database and more like a shared directory.

That directory matters most at knowledge boundaries, the seams where one specialty's assumptions meet another's. The development of a transactive memory system in cross-functional teams is shaped by how those boundaries are handled, which is why coordination depends on more than goodwill or good communication tools [1]. The same underlying idea appears in distributed work across organizational boundaries, where knowledge is coordinated in multiple ways rather than flowing through a single channel [5].

Shared memory also defines the group itself

Collective memory is not only a practical index of expertise. It can be a body of knowledge about a topic, an image of a people often rooted in an origin story, and an ongoing process in which people dispute how the past should be remembered [3]. These three facets matter for boundary crossing because they tell members what they share and what distinguishes them from outsiders.

Because collective memory is held within individuals but shaped by group membership, it can form a strong part of personal identity [3]. That helps explain why coordination across groups is not purely informational: agreeing on facts is entangled with agreeing on who "we" are. The same body of knowledge can also shift across generations, so what a group treats as common ground is not fixed [3].

Boundaries are renegotiated, not just crossed

In real conflicts, groups actively revise memories, narratives, and symbols to fit a new situation, and doing so means renegotiating group boundaries. In the pro-Ukraine movement in Sweden, both Ukrainian and Russian diasporas reframed themselves through memories and narratives tied to earlier events, including the 2014 annexation of Crimea and prior diasporic mobilizations, and solidarity patterns shifted during mobilization [2]. Here collective memory is doing boundary work rather than simple knowledge transfer.

Collective memory can also be enacted spatially. Among Jews in Toronto, collective memory schemas were examined as a way of enacting social boundaries, with residential patterns as the visible expression of those boundaries [4]. This is a different outcome from team coordination, but it shows the same underlying move: shared memory marks where a group ends and another begins.

Why shared memory helps and where it strains

Put together, these findings suggest two linked functions. Internally, collective memory coordinates knowledge by distributing expertise and tracking who holds it, as in transactive memory systems [1]. Externally, it coordinates by defining the group's shared perspective and its differences from other groups [3]. Both are needed when people from different domains or backgrounds must work together.

The strain appears when the two functions pull apart. A group may share a vivid collective memory yet disagree about how the past should be remembered, since collective remembering can reveal disputes and contestations [3]. And when boundaries are being actively renegotiated, as in diaspora mobilization, the shared memory that enables solidarity can also redraw who counts as an ally [2]. The evidence indicates that collective memory supports coordination, but it does not establish that shared memory alone is sufficient, nor that it always smooths cross-boundary work.

Sources used in this answer

Related research questions