Field Note #3: Teams Are Built Through Friction
- Nicholas Harnish
- Jun 8
- 4 min read
"Coming together is a beginning, staying together is progress, and working together is success."— Henry Ford
Every spring, as camp staff begin arriving and leadership teams shift from planning to execution, I am reminded that teams are not built during meetings. They are built through shared experiences. Planning sessions, onboarding materials, organizational charts, and training schedules all play an important role, but none of them create trust on their own. Trust emerges when people begin working together under real conditions.
At the beginning of a season, optimism comes easily. New staff arrive energized by possibility. Returning staff reconnect with friends and colleagues. Goals are ambitious. Expectations are high. Everyone can see the potential of what the team might become. It is an exciting phase because conflict has not yet appeared, weaknesses remain hidden, and success feels almost inevitable.
This is what psychologist Bruce Tuckman described as the Forming stage of team development. People are learning names, establishing relationships, and orienting themselves to a common purpose. There is enthusiasm, curiosity, and often a degree of cautious politeness. Most teams enjoy this phase because it feels productive and positive.
Eventually, however, reality arrives.
Schedules become demanding. Communication breaks down. Assumptions are exposed. Personalities clash. Expectations that seemed aligned during planning suddenly reveal important differences. The pressure of accomplishing real work begins testing both individuals and systems. The team enters what Tuckman called the Storming stage.
Over the years, I have watched many leaders react to this phase with concern. The appearance of conflict is often interpreted as evidence that something is failing. Questions emerge quickly. Why is morale dropping? Why are people frustrated? Why is communication becoming more difficult? Why is the team struggling when everyone seemed so aligned just weeks earlier?
The answer is often simpler than it appears.
Nothing is necessarily broken.
The team is simply becoming real.
Storming is not evidence of dysfunction. More often, it is evidence of development. Friction exposes gaps that optimism conceals. It reveals unclear expectations, inefficient systems, competing assumptions, and unresolved tensions. In doing so, it provides leaders with valuable information about what needs attention before the team can reach higher levels of performance.
This realization has become increasingly important in a culture that often treats discomfort as something to avoid. We have become conditioned to view tension as inherently negative, yet some forms of tension are essential to growth. Muscles strengthen through resistance. Skills develop through challenge. Teams mature through navigating difficulty together.
The strongest teams I have worked with were not teams that avoided conflict. They were teams that learned how to engage conflict constructively. They developed the ability to have difficult conversations without damaging relationships. They learned how to disagree without becoming divided. They became comfortable identifying problems because they trusted one another enough to solve them collectively.
I often see this process play out among youth leaders. A newly formed group may begin with excitement and enthusiasm, but eventually they encounter challenges that require real collaboration. Someone misses a deadline. A plan falls apart. A disagreement emerges about priorities. At first, these moments can feel discouraging. Yet when guided appropriately, they often become the experiences that strengthen the group the most. Through adversity, individuals learn accountability. Through disagreement, they learn communication. Through shared challenges, they learn trust.
The same principle applies to organizations. Every team eventually encounters moments that test its cohesion. Staffing shortages, unexpected changes, limited resources, shifting priorities, and operational stress are not anomalies. They are part of the environment. The question is not whether friction will appear. The question is how the team will respond when it does.
Teams that view friction as failure often become trapped by it. Teams that view friction as information learn from it.
This distinction matters. Leaders who interpret every challenge as evidence of dysfunction often spend their energy trying to eliminate discomfort. Leaders who view challenges as opportunities for learning focus instead on adaptation. They ask different questions. What is this tension revealing? What assumptions have been exposed? What systems need refinement? What conversations have been avoided?
Those questions move a team forward.
Over time, successful teams transition into what Tuckman described as Norming and Performing. Communication becomes more natural. Expectations become clearer. Trust deepens. Members understand one another's strengths and compensate for one another's weaknesses. The team becomes capable of handling challenges that would have overwhelmed it earlier in its development.
Importantly, this transformation rarely occurs despite friction. It occurs because of it.
Every high-performing team carries the scars of challenges it learned to overcome together. The trust present within those teams is not built upon comfort but upon evidence. Members trust one another because they have already navigated uncertainty together. They have experienced setbacks, solved problems, and adapted under pressure. They know from experience that the group can endure difficulty and continue moving forward.
As camp season approaches, I find myself reflecting on this lesson once again. The moments that ultimately define a team are rarely the moments when everything goes according to plan. They are the moments when plans change, conditions become difficult, and people must decide whether they will retreat from the challenge or grow through it.
The strongest teams choose growth.
They understand that friction is not the enemy of progress. More often than not, it is the path to it.
_edited.png)



Comments