Working Together vs. Working Simultaneously
The Hidden Cost of Keeping Your Head Down
Most teams aren’t actually working together. They’re working simultaneously.
This distinction sounds subtle, but it fundamentally changes everything about how organizations function.
I didn’t understand this until I experienced both. At one organization, I was part of a team that could disagree intensely about strategy in meetings, then grab drinks afterward with zero lingering tension. We knew each other. Beyond the work, beyond the roles.
My next job was different. Equally talented people, equally committed to the work, but we barely knew each other. And suddenly I understood: we weren’t collaborating. We were just coordinating separate efforts while pretending to be aligned.
The Distinction That Changes Everything
There’s a difference between working together and working simultaneously that most organizations never recognize. Working simultaneously looks efficient: everyone completes their tasks, minimal friction because there’s minimal real interaction, projects advance through coordinated individual effort. You know what people do, but not who they are.
Working together looks messier but produces something fundamentally different. Ideas build on each other organically. Healthy conflict strengthens outcomes instead of creating resentment. You understand the motivations behind positions, which means you can debate passionately without damaging relationships. Trust allows for vulnerability and creative risk-taking.
The difference isn’t about being friends with your colleagues or oversharing personal details. It’s about whether you see each other as complete humans or just functional roles.
Two Organizations, Two Outcomes
I’ve experienced both sides of this divide, and the contrast taught me everything I know about what makes teams actually work.
The Connected Team
At one organization, our team meetings were intense. We’d debate approaches passionately, challenge each other’s assumptions, push back on ideas we thought were off track. Sometimes voices got raised. Sometimes the discussion got uncomfortably direct.
And then we’d go grab drinks after work, and there would be zero tension.
We could disagree strongly about strategy in the afternoon and laugh about completely unrelated things that evening because we knew each other beyond our job titles. I understood that my colleague’s attention to risk wasn’t about being difficult; it came from their deep commitment to protecting what we were building. Another’s push for ambitious timelines wasn’t about creating pressure; it reflected their genuine belief in what we could accomplish together.
When you know what drives someone’s decisions, their positions stop feeling like obstacles and start feeling like valuable perspectives. We made better decisions because we could access everyone’s full thinking instead of just their surface positions. We moved faster because we didn’t waste time on assumptions and misunderstandings. We were more successful because we were genuinely collaborating, building on each other’s strengths and compensating for each other’s blind spots.
The Simultaneous Workers
At another organization, everyone was equally competent, equally professional, equally committed to doing good work. But we barely knew each other.
My colleagues didn’t make an effort to understand me beyond my daily tasks and how my work impacted theirs. I didn’t know what they cared about, what concerned them, what they were trying to protect or build. Every interaction stayed transactional: Can you get me this by Thursday? Did you finish that analysis? Where are we on the timeline?
The frustration built slowly. When someone questioned my approach, it felt like a personal attack because I had no context for their concern. When I disagreed with a decision, it created tension that lingered because we had no human foundation to metabolize that friction. Assumptions multiplied. Simple miscommunications became interpersonal conflicts.
We were all working hard, all doing our jobs, but we weren’t really working together. We were just working simultaneously in the same space, coordinating separate efforts rather than truly collaborating.
If we had been better connected, if we’d known each other as people rather than just functions, we would have been more successful. And so would the organization.
Why Teams Default to Distance
I understand why organizations fall into the “working simultaneously” pattern. It feels safer. Professional distance seems more efficient. We convince ourselves that boundaries make us more productive, that keeping things impersonal is what “professional” means.
We’re also afraid of the potential messiness of actually knowing each other. What if it gets awkward? What if people share too much? What if personal relationships complicate professional decisions?
And honestly, most of us don’t have frameworks for connecting in professional settings without it feeling forced or artificial. So we default to the path of least resistance: heads down, stay in your lane, keep it about the work.
The Hidden Costs
But working simultaneously carries costs that rarely show up on any metric we’re measuring.
When people are functional strangers, creative problem-solving suffers because psychological safety doesn’t exist. You can’t share half-formed ideas or acknowledge what you don’t know when you’re not sure how it will be received. Innovation requires the vulnerability to be wrong, to explore, to build on each other’s thinking. That doesn’t happen between strangers.
Decision-making becomes slower and less effective because everything operates on assumptions. You’re constantly trying to read between the lines, guess at motivations, interpret positions without understanding the person behind them. Meetings become performances where people advocate for predetermined positions rather than collaborative spaces where the best thinking emerges.
When challenges arise, teams working simultaneously have no resilience. There’s no trust foundation to fall back on, no goodwill built up, no shared understanding to help navigate difficulty. Instead, pressure reveals all the cracks that were hidden during easier times.
And the human cost? People leave because they’re tired of being seen only as a function, tired of the loneliness of working alongside people who remain strangers, tired of the inefficiency and frustration of coordination without genuine collaboration.
What Changes When Teams Actually Connect
The transformation isn’t about becoming best friends or knowing everyone’s life story. It’s about understanding what drives each person’s decisions and seeing different perspectives as valuable rather than threatening.
When a team actually connects, several things shift:
You start accessing collective wisdom instead of siloed knowledge. People build on each other’s ideas rather than defending their own positions. The conversation becomes genuinely collaborative rather than a series of individual presentations.
Conflicts resolve faster because you understand context. When a colleague pushes back on a timeline, you know it’s because they’re protecting something important, not because they’re being difficult. When another colleague advocates for a bold approach, you understand it comes from their vision for what’s possible, not from unrealistic expectations.
The team develops the ability to disagree without drama. You can challenge someone’s idea strongly without threatening your relationship because the relationship exists beyond any single interaction or disagreement.
Innovation becomes possible because people feel safe being uncertain, admitting what they don’t know, exploring ideas that might not work. Psychological safety isn’t something you manufacture through team-building exercises; it emerges naturally when people see each other as complete humans.
Moving from Simultaneous to Collaborative
This shift doesn’t happen by accident. It requires intentional space for connection beyond tasks and deliverables.
It needs professional frameworks that create safety for authenticity without the awkwardness of forced sharing. The question isn’t about “what do you do?” but “who are you beyond your role?” What do you care about? What are you trying to protect? What concerns keep you up at night? What possibilities excite you?
And critically, this foundation needs to be built before you need it. You can’t manufacture connection during a crisis when trust is required immediately. The teams that navigate challenges well are the ones that built human understanding during calmer times.
This is why team connection experiences exist: to create the human foundation that makes real collaboration possible. Not through trust falls or forced fun, but through professional frameworks that help people see each other as complete humans rather than just their job functions.
Is Your Team Working Together or Just Working Simultaneously?
Here’s how you know:
Can people on your team disagree without it feeling personal? When someone challenges your idea, does it land as “this idea needs work” or “you’re wrong and difficult”?
Do you know what motivates your colleagues beyond their job descriptions? Can you articulate what they care about protecting, what they’re trying to build, what drives their decisions?
Could your team navigate strong conflict and still grab drinks after? Or does tension from disagreements linger and compound?
Are you solving problems together or just coordinating separate tasks? When you leave a meeting, do you feel like you built something collaboratively, or just aligned on who’s doing what?
The Difference
The difference between those two organizations I worked for wasn’t talent, resources, or even leadership quality. It was whether people saw each other as complete humans or just functional roles.
The teams that truly collaborate aren’t doing something complicated. They’re just working together instead of working simultaneously. They know each other beyond job titles. They understand what drives each other’s decisions. They’ve built the human foundation that makes everything else possible.
And that changes everything: the quality of decisions, the speed of execution, the ability to navigate challenges, the satisfaction of the work itself. Real collaboration isn’t about being more coordinated in your separate efforts. It’s about genuinely building something together that none of you could create alone.
That only happens when you stop working simultaneously and start actually working together.
A Prompt to Try This Week
Here’s something you can explore with a colleague you want to understand better. It requires just 5-10 minutes and creates the foundation for actual collaboration:
“What aspect of your role matters most to you, and what are you trying to protect or build through that work?”
This question does something powerful: it moves from what people do to why they do it. It reveals motivations, concerns, and priorities without feeling intrusive. Most people are relieved to be asked. It’s often the first time someone’s been curious about what’s actually driving their decisions.
Try it and notice what shifts. You might discover that the colleague you thought was difficult is actually deeply committed to protecting something important. Or that the person who seemed disengaged cares intensely about outcomes you didn’t realize mattered to them.
That understanding is where real collaboration begins.
What about you? When you think about your own team, are you working together or working simultaneously? I’m genuinely curious about your experiences.