Why Specialist Teams Protect Product Memory

Specialist Teams Protect Product Memory

Specialist teams can protect product memory, but specialization alone is not enough.

Repeated exposure lets a person notice small differences that a general process may miss. A footwear specialist remembers which material change created a fit problem two launches ago. A claims specialist recognizes the innocent field value that will break downstream handling. A mobility operator knows which access failure becomes a support emergency at midnight.

That knowledge often lives partly in records and partly in judgment.

E114 raised the concern through Nike. Dalton argued that moving away from dedicated sport and technical groups contributed to a loss of product edge. The transcript does not establish that organizational change as a proven cause of Nike's results. Product mix, leadership, distribution, incentives, competition, geography, and demand also matter.

The useful claim is narrower: a reorganization can improve coordination while weakening the conditions that produced technical judgment.

Product memory is distributed

Team research provides a better model than the simple choice between specialists and generalists.

A transactive memory system is a shared understanding of who knows what and how the group accesses that expertise. Research commonly describes three parts: specialization, credibility, and coordination.

Specialization means knowledge is differentiated. Credibility means people trust the relevant expertise. Coordination means the group can bring that knowledge into the work when it matters.

flowchart TD
    A["Repeated specialist exposure"] --> B["Differentiated knowledge"]
    B --> C["Credibility: the team trusts who knows"]
    C --> D["Coordination: expertise enters the decision"]
    D --> E["Product memory changes the tradeoff"]
    E --> F["Outcome returns as new experience"]
    F --> A

Specialization becomes useful product memory when the organization can identify, trust, coordinate, and refresh it.

A 2018 field study of 61 knowledge teams found that specialization and credibility were associated with knowledge transfer, which in turn related to team performance. A separate study of 236 information-systems personnel found that mature transactive memory systems were associated with communication, coordination, and project-team performance.

Neither study proves that Nike needed a particular structure. They support the operating principle that differentiated knowledge creates more value when the team knows where it lives and can coordinate it.

Consolidation can erase the map

Combining teams may reduce duplication, standardize tools, make staffing more flexible, and resolve obvious handoff problems. Those are real benefits.

The risk appears when the new structure treats expertise as interchangeable capacity.

People rotate before they see the result of their decisions. Technical reviews become optional. A general owner receives several domains but lacks enough repeated exposure to recognize the quiet failure. Documentation records the decision without preserving the sensory, contextual, or customer evidence behind it.

The organization has not necessarily lost all knowledge. It has lost the map that makes knowledge available at decision time.

Silos are not the answer

Specialist teams can hoard information, create local optimization, defend weak practices, and force customers through unnecessary boundaries. Deep expertise without coordination can be as dangerous as coordination without depth.

The goal is not to protect every historical team. It is to protect the learning mechanism.

Before consolidating a technical group, identify the decisions that depend on repeated exposure. Name the people whose judgment is trusted. Define where their review enters the process. Keep them close enough to users and outcomes to refresh what they know. Give the wider team a clear route to find them.

Then watch what happens after the reorganization. If decisions move faster but defects, reversals, escalations, or customer confusion rise, the structure may have removed friction that was carrying information.

A small diagnostic

Ask four questions before changing the team boundary.

Who owns the consequential tradeoff? Who has seen this failure pattern before? Where is that expertise required to enter the decision? How will the person who made the choice observe the result?

If the new design cannot answer those questions, a cleaner org chart may be hiding lost product memory.

This remains a working theory in the Nike context. The research supports specialization, credibility, and coordination as parts of team memory. It does not prove a single organizational cause for Nike's performance or prescribe permanent silos.

Continue the series

The E114 episode story places specialist memory inside Nike's broader product and distribution system. The company-recovery guide shows how to restore evidence and decision rights without reenacting the past. Episode 119 adds the importance of seeing decisions survive real conditions.

Sources and disclosure

The team-memory framework uses a 2018 field study of knowledge transfer and team performance, a 2012 study of information-systems development teams, and a 2007 study of 104 work teams. Nike's historical example uses the company's account of Bill Bowerman's repeated product experimentation.

Dalton Anderson's preserved E114 transcript controls the Nike observation. The team studies support the narrower memory framework, not a causal verdict about Nike. AI assisted with research organization and drafting; the working theory, limits, and final editorial decisions remain Dalton's.