Proximity Is Not Teamwork And Here's Why

You can be in the same room and still not be on the same team.You can have meetings, roles, group chats, project boards, and shared calendars — and still feel like the mission is heavier than it should be.Because proximity is not teamwork.In this episode of Crossing the Threshold, James Wilson Jr. and JC Fowler unpack one of the biggest hidden breakdowns inside teams: assuming that working near each other means we are actually sharing responsibility with each other.They explore the difference between a working group and a real team, why good people can still struggle to work well together, and how unclear work and unnamed worry slowly create drift, disconnection, mistrust, and poor performance.This conversation is for leaders, teams, pastors, founders, nonprofit leaders, and anyone who has ever wondered:“We’re together all the time… so why does this still feel so heavy?”In this episode, we talk about:• Why proximity does not automatically create teamwork• The difference between giving updates and making commitments• Why good people and a meaningful mission are not always enough• The two kinds of weight every team carries: workload and worry• How unclear work leads to dropped balls, duplicate effort, and bottlenecks• How unnamed worry leaks into hallway conversations, passive-aggressive comments, and quiet withdrawal• Why psychological safety matters for honesty, trust, and performance• The wrong fixes teams often reach for, including “communicate more,” “just trust each other,” and “collaborate on everything”• Two simple questions that can help reset a team this weekKey idea:A team is not just a group of people working together.A team is a group of people sharing responsibility for the mission.Real teamwork begins when the work gets clarified and the worry gets named.Memorable lines from this episode:“Proximity is not teamwork.”“A working group gives updates. A real team makes commitments.”“Good people are not enough if the team doesn’t know what they’re carrying together.”“Even if the workload is clear, if the worry remains hidden, teamwork breaks down.”“What does not get named in the room usually leaks outside the room.”“You may not be lacking a team. You may just be lacking shared language for the weight you’re carrying.”“Teamwork is honest alignment around meaningful work.”Crossing the Threshold Questions:What work am I carrying that needs to be clarified?What worry am I carrying that needs to be named?You do not have to solve everything today. But you can take one honest step toward healthier teamwork.Resource Mentioned:Threshold Thoughts is our twice-monthly leadership email designed to give you a quick leadership win in under two minutes.It is built to help you pause, name what matters, and take one clear next step.Join Threshold Thoughts here:→ https://cttleadership.kit.com/thresholdthoughtsTimestamps:00:00 — Opening question: How do you know when something is off in a team?01:28 — Why proximity is not teamwork02:05 — Working group vs. real team04:45 — A working definition of a team06:15 — The two kinds of team weight: workload and worry08:04 — How teams drift slowly over time09:21 — Psychological safety and why it matters13:57 — What breaks down teams: unclear work17:27 — Why unnamed worry leaks outside the meeting22:41 — The cost of unclear work and unnamed worry23:51 — Wrong fix #1: “We just need to communicate more”25:06 — Wrong fix #2: “We just need to trust each other”26:04 — Wrong fix #3: “We need to collaborate on everything”27:24 — Two questions to reset your team28:09 — Threshold Thoughts invitation Crossing the Threshold Leadership PodcastReal life. Real leadership. One threshold at a time.You don’t have to stay stuck leading from reaction. This week, take one honest step toward the leadership, team, and life you’re called to build.Subscribe and share this episode with a mission-driven leader who needs language for the weight they’re carrying.Download the free Threshold Starter Guide:→ https://thresholdstarterguide.cttleadership.comWork with us:→ www.cttleadership.comQuestions or feedback:→ [email protected]