Contents
In 2010, 33 miners were trapped underground in Chile. The rescue required geologists, drill operators, government officials, engineers, medical staff, families, and specialists from multiple countries. Many had never worked together. The problem did not care.
They had to become a team faster than trust usually forms.
This is a different kind of teamwork than the corporate offsite celebrates.
The Story
Amy Edmondson’s TED talk describes “teaming”: people coming together quickly to solve urgent, unfamiliar problems. It is not the same as being a stable team. It is a capability for temporary coordination under uncertainty.
Modern work needs this constantly.
A production incident begins at 2:13 AM. The database team, payments team, infrastructure team, support lead, and incident commander join a call. Some people know each other. Some do not. The system is failing while the group is still forming.
The difference between a group of people and a team appears in the first ten minutes: who names uncertainty, who owns coordination, who speaks up, who documents, who asks for help, who keeps the room from splitting into parallel confusion.
Three Ways This Appears
In everyday life: A medical emergency in a public place turns strangers into a temporary team. One person calls emergency services. One clears space. One finds equipment. Nobody has a reporting line. The work organizes around the problem.
In technology: A cross-functional launch team forms around a regulatory deadline. The technical, legal, product, and operational risks cannot be solved in sequence. The team must learn together while moving.
In organizations: A company enters a new market. The people required to understand it sit in different departments. The formal structure is too slow. Temporary teaming becomes the actual strategy.
The Pattern
Teaming requires rapid shared context.
Stable teams can rely on history. Temporary teams need substitutes: clear roles, visible uncertainty, psychological safety, disciplined communication, and a shared representation of the problem.
The failure mode is assuming that putting capable people in the same channel creates a team. Capability is individual. Teaming is relational.
The Cross-Domain Connection: Emergency Rooms
Emergency medicine depends on teams that form around patients. People rotate. Cases differ. Time is scarce. The system uses protocols, role clarity, checkbacks, and shared language to create coordination faster than familiarity could.
Organizations that face novel problems need similar scaffolding. Not bureaucracy. Scaffolding.
The Framework: Rapid Teaming Conditions
Why This Matters Outside Technology
Climate events, public health crises, cyber incidents, family emergencies, and community problems all require people to coordinate before they have earned the comfort of long familiarity.
The future belongs partly to teams that do not yet exist. The question is whether they can form quickly enough when the problem arrives.
The Memorable Sentence
A team is not a group of capable people; it is a group that can create shared context fast enough to act.
Closing Question
If a serious cross-functional problem appeared tomorrow, what would help your organization become a team in the first ten minutes?
- Edmondson, A.C. (2017). How to turn a group of strangers into a team. TED Salon: Brightline Initiative.
- Edmondson, A.C. (2012). Teaming: How Organizations Learn, Innovate, and Compete in the Knowledge Economy. Jossey-Bass.
- Weick, K.E. (1993). The collapse of sensemaking in organizations: The Mann Gulch disaster. Administrative Science Quarterly.
By 2031, teams will form around incidents, launches, and AI-human workflows with little time for traditional bonding. The useful capability will be rapid context formation: clear roles, shared facts, visible uncertainty, and enough trust to act before certainty arrives.