A group of people can report to the same manager without ever becoming a team.

They attend the same meetings. They share goals. They answer the same Slack threads. They may even be called a team in every company document.

But they do not feel like one.

They are polite, capable co-workers who exchange information and complete their individual responsibilities. There is no real spark between them. They do not know much about one another beyond a role and a calendar. They rarely ask for help early, challenge an idea honestly, or show genuine curiosity about the person behind the work.

Nothing is visibly broken. Everyone may be delivering exactly what is expected. Yet something important is missing.

I have found myself in a group like this at one point in my career. It became personal for me because I knew how different work could feel. I had experienced the energy of people who genuinely cared about one another, challenged one another, and wanted to achieve something together. Being surrounded by capable colleagues without that connection made me ask a harder question: if the manager is not building the team, can someone else do it? Or is the only real option to find a way out?

That experience stayed with me. It is one of the reasons I care so much about the difference between people who merely work next to one another and people who feel they belong to something together.

A reporting line creates a group. It does not create a team.

What Changes When Co-Workers Become a Team

For me, a real team is not simply a group that gets along. It is a group whose members understand that their outcomes depend on one another and behave accordingly.

The personal dimension matters because collaboration is full of small interpersonal risks. Asking a basic question risks looking unprepared. Disagreeing risks creating tension. Admitting a mistake risks losing credibility. Requesting help risks appearing less capable.

When people know one another as humans, those risks become easier to take. Context replaces assumption. A short message is less likely to be read as hostility. A challenge can be interpreted as care for the work rather than a challenge to status.

This does not mean everyone must become close friends. The goal is not intimacy. It is relational trust: enough knowledge, care, and repeated evidence to believe that colleagues have good intent and will respond constructively.

The research supports this connection. A meta-analysis of 112 studies involving 7,763 teams found a positive relationship between trust within a team and team performance. Another meta-analysis of friendship and group performance found that friendship had a positive effect on performance, especially when the work required greater interdependence.

I do not take this research to mean “make everyone friends.” I take it to mean that relationships are not separate from performance when the work itself is interdependent.

The Manager Owns the Conditions, Not the Chemistry

So whose job is it to turn the group into a team?

I believe it is primarily the manager’s.

The manager shapes the environment more than anyone else. They decide what receives time, what behavior is rewarded, how conflict is handled, whose voice is heard, and whether asking for help is treated as responsible or weak.

Research on leader inclusiveness describes it as the words and actions through which leaders invite and value other people’s contributions. In a study of 23 clinical teams, leader inclusiveness predicted psychological safety and greater participation in improvement work. Earlier research across 51 work teams also connected psychological safety with learning behavior and identified team leader coaching and supportive structures as important inputs.

Here is what I believe the manager owns:

  • Giving the team a genuinely shared purpose, not a collection of individual targets
  • Making dependencies visible so people understand where partnership is required
  • Modeling curiosity, fallibility, and respect
  • Creating repeated opportunities for people to learn about one another
  • Protecting dissent and responding well when someone raises a problem
  • Addressing exclusion, cliques, disrespect, or chronic non-participation
  • Ensuring that team contribution is recognized alongside individual delivery

At the same time, I do not believe a manager can order chemistry into existence.

They cannot demand friendship, select who should feel close, or turn personal disclosure into a performance expectation. Their role is to make connection possible and safe, but not compulsory.

Why Some Managers Struggle With the Personal Part

I have met managers who fundamentally believe that personal connection is irrelevant: You are here to work, so work.

I can understand where that belief comes from. Many leaders were promoted because they were reliable experts. Their professional identity was built on competence, discipline, and keeping personal life separate. They may fear becoming intrusive, losing authority, appearing unproductive, or creating favoritism. Some simply never experienced good team building themselves.

Generational differences do exist. Leaders who entered the workforce at different times may have learned different expectations about authority, privacy, and the boundary between personal and professional life. But to me, generation is context, not an explanation. What matters more is whether a manager sees relationship-building as part of the job and whether they are willing and able to do it.

Research also gives us a reason to be careful with generational labels. A meta-analysis of generational differences in work attitudes, covering four generations and roughly 20,000 people, found that meaningful differences were generally small or absent. Within-generation differences are often greater than the differences between generations.

I think the more useful questions are behavioral:

  • Does this manager see relationship-building as legitimate work?
  • Do they have the skill to invite connection without forcing vulnerability?
  • Are they comfortable receiving feedback and admitting uncertainty?
  • Are they rewarded only for short-term output?
  • Do they have enough time and organizational support to lead a team, rather than merely distribute tasks?

A younger manager can be emotionally unavailable. An older manager can be deeply relational. For me, the real problem is not a birth year. It is a management model that treats human connection as decoration.

Can a Teammate Take the Lead?

Often, someone does. I have also found myself wondering whether that someone should be me.

One person remembers birthdays, welcomes newcomers, asks the question nobody else will ask, or notices when a colleague has gone quiet. This informal relational leadership can be enormously valuable. I believe teams are stronger when care and cohesion are distributed rather than flowing only through the manager.

There is something empowering in realizing that a teammate does not need a title to change the quality of a group. A person can begin asking better questions, create small moments of connection, offer help, and make it safer for others to be more human. Sometimes that changes the dynamic. Sometimes others begin to participate and the manager follows.

But there is also a limit to what one teammate can repair. A colleague cannot change what the manager rewards. They cannot create psychological safety if the manager punishes disagreement. They cannot solve unfair workloads, persistent exclusion, or a leader who has no interest in knowing the team. Trying harder in that environment can slowly become emotional labor with no real authority behind it.

But there is a danger: this work is frequently invisible, unequally carried, and disproportionately expected from women or naturally empathetic colleagues.

The manager should not quietly outsource culture to “the social one.” Nor should they appoint a permanent team-morale owner, which can make connection feel artificial and let everyone else opt out.

The model I believe works best is manager-sponsored, team-owned:

  • The manager remains accountable for the conditions and intervenes when the system is unhealthy.
  • Any teammate can initiate connection, improve a ritual, or model care.
  • Small responsibilities rotate: welcoming a new joiner, facilitating a retrospective, planning a learning conversation, or opening a meeting.
  • Relational contributions are recognized as real work, without turning them into unpaid emotional labor.

Team culture is too important to be purely the manager’s activity. It is too consequential to be nobody’s accountability.

And if you are the teammate trying to carry it alone, I think it is fair to eventually ask whether the environment is willing to meet you halfway. If you have named the gap, tried small changes, invited others in, and asked the manager for support, but nothing moves, the answer may not be to try even harder. Sometimes finding a way out is not giving up on the team. It is recognizing that one person cannot create a team in a system committed to remaining a group.

Where to Start: Build Through the Work

When a team feels flat, the instinct is often to add an event: drinks, a trivia session, an offsite, an icebreaker.

Those experiences can help. But connection built outside the work rarely compensates for poor dynamics inside the work.

I would start with how the team actually operates.

1. Name the Gap Without Blaming the People

A manager can say:

We deliver, but I do not think we yet use one another as a real team. We tend to bring work together late, ask for help only when something is already stuck, and know little about how each person works best. I would like us to change that together.

This frames the issue as a shared design challenge, not a verdict that people are insufficiently friendly.

2. Create a Real Shared Outcome

If every goal belongs to one person, co-workers have little reason to become partners.

Choose one outcome that requires joint ownership. Clarify why it matters, how roles connect, and what success requires from the group, not only from each individual.

Interdependence gives relationships a purpose. The team starts learning one another through meaningful work rather than forced disclosure.

3. Write a Small Team Agreement

I would not begin with values on a poster. I would agree on observable behavior:

  • We ask for help before the deadline is at risk.
  • We challenge the idea without diminishing the person.
  • We do not let silence stand for agreement.
  • We give context when a message could be misread.
  • We discuss tension with the person involved, not around them.
  • We learn enough about one another to collaborate with care.

Five useful agreements are better than fifteen aspirational words.

4. Add Human Context in Small Doses

Connection grows through repeated, low-pressure moments rather than one dramatic exercise.

Use one-to-ones to learn what motivates each person, how they prefer to receive feedback, what drains their energy, and what support looks like to them. In team settings, invite questions that are personal enough to create context but safe enough to answer honestly:

  • What helps you do your best work?
  • What is something colleagues often misunderstand about your working style?
  • What have you learned recently outside your role?
  • When you are under pressure, what support is actually useful?

I would always allow people to pass. Psychological safety includes the safety to remain private.

5. Design Meetings for Contribution

Do not ask, “Any thoughts?” after the most senior person has spoken for ten minutes.

Share context before decisions. Ask people to write independently before discussion. Rotate who opens. Invite the least-heard perspectives without putting individuals on the spot. Close with what changed because of the conversation.

The team learns whether its voice matters from what the manager does next.

6. Build a Learning Rhythm

Teams become closer when they solve problems honestly together.

Run a short monthly retrospective:

  • What helped us work as a team?
  • Where did we operate as separate individuals?
  • What did we avoid discussing?
  • What is one experiment we will try next month?

Psychological safety is not the same as comfort. In a study of 104 field teams, safety supported performance through learning behavior and team efficacy. The point is not simply to feel good. It is to make candor, help-seeking, experimentation, and recovery possible.

Where to Stop

Team building becomes unhealthy when belonging turns into conformity.

Stop before:

  • Personal disclosure becomes mandatory
  • Social participation outside work affects opportunity or status
  • “We are a family” is used to weaken professional boundaries
  • Harmony becomes more important than disagreement
  • Close relationships create an inner circle
  • The team expects emotional availability at all hours
  • The manager becomes a therapist rather than a leader

A strong team does not require everyone to relate in the same way. Some people will become friends. Others will remain warmly professional. Both can belong fully.

The goal is not sameness. It is a reliable experience of respect, contribution, and mutual care.

How to Measure Whether a Team Is Becoming a Team

I would not measure the number of social events. I would measure whether the team’s behavior is changing.

A short anonymous pulse every six to eight weeks can ask people to rate:

  1. I can ask this team for help before a problem becomes urgent.
  2. I can disagree with my manager or colleagues without negative consequences.
  3. People on this team show genuine interest in me as a person.
  4. We understand how our work depends on one another.
  5. When something goes wrong, we learn rather than look for someone to blame.
  6. Every member has a meaningful opportunity to influence our work.
  7. I would choose to work with this team again.

Keep the pulse small and stable enough to observe trends. Discuss the results with the team. Choose one action. Report back on what changed. A survey without a visible response teaches people that honesty has no value.

Fast-Growing SaaS and the 10,000-Person Enterprise

In my view, the fundamentals do not change with company size. The design does.

In a Fast-Growing SaaS Company

Speed, hiring, reorganizations, and shifting priorities constantly disrupt familiarity. A team may change before trust has time to form.

The answer is not more culture events. It is faster relational onboarding:

  • Make roles, dependencies, and decision rights explicit immediately.
  • Pair new joiners with more than one colleague so connection is not manager-dependent.
  • Protect a recurring reflection rhythm even during intense delivery periods.
  • Rebuild the team agreement after significant membership or strategy changes.
  • Watch for “temporary urgency” becoming the permanent excuse for transactional relationships.

In a high-speed environment, connection is not a luxury that begins after execution stabilizes. It is part of the infrastructure that makes speed sustainable.

In a Large, Established Enterprise

The challenges are different: hierarchy, functional silos, long tenure, distributed locations, and processes that can make team life feel impersonal.

Here, I think the local team matters even more. No employee experiences “10,000 people” as a relationship. They experience a manager, a handful of colleagues, and the norms of the smallest group where work happens.

In a company this size, a corporate team-building program will not solve a weak local dynamic. The organization needs to hold every people manager accountable for the health of their team, give managers practical support when teams form or change, and step in when the same problems continue. How each team builds connection can vary. The expectation that a manager leads a functioning team should not.

What People Ops Must Do

I do not think a company can say teamwork matters while promoting only individual heroes, overloading managers, and measuring only delivery, then be surprised when teams remain collections of co-workers.

People Ops can make team building more likely by:

  • Selecting and promoting managers for relational leadership as well as expertise
  • Teaching managers to facilitate, receive challenge, and repair trust
  • Measuring team health without turning it into surveillance
  • Recognizing collaboration and culture-building in performance decisions
  • Giving newly formed or reorganized teams an intentional reset process
  • Holding senior leaders to the same behavioral expectations

Connection cannot survive as an extracurricular activity. The operating system has to support it.

Final Thought

The teams I remember were not created in a workshop. They became teams over time, through ordinary but important moments: a manager admitting they were wrong, a colleague asking for help early, a disagreement handled with respect, someone remembering what matters to another person, or a difficult week carried together.

The manager must begin the work. The team must eventually own it. The organization must make room for it.

And when those conditions are consistently absent, people should not blame themselves for failing to create the spark alone. I wish more employees heard this clearly: you can influence a team, but you cannot single-handedly compensate for a manager who will not lead one.

People do not need to become best friends to do extraordinary work together.

But they do need to become real to one another.