A practical guide to the tools that keep remote teams working together - chat, video, shared docs, and project boards. We'll look at what each type does best, how they fit together, and how to choose a setup that actually helps your team instead of drowning it in notifications.
On the morning of March 13, 2020, Slack reported its largest single-day growth in messaging activity in company history. The following week, Microsoft Teams added 12 million daily active users. Zoom went from 10 million daily meeting participants in December 2019 to 200 million in March 2020.
Within two weeks, the pandemic had forced an experiment in distributed work at a scale that would have taken decades under normal circumstances.
What the experiment revealed, once the initial chaos settled, was striking: the tools were the least important variable. Teams that had genuinely dysfunctional communication before the pandemic did not become functional because they started using Slack.
Teams that had strong communication norms and trust-based cultures adapted quickly because the tools amplified what was already there. The collaboration platform is infrastructure. The culture it runs on is everything.
This does not diminish the importance of tool selection. Poor infrastructure creates friction that accumulates into significant productivity loss. A team using inadequate tools spends more time working around limitations than they realize.
But it does establish the right priority order: invest in communication culture and explicit norms first, then select tools that support those norms, rather than hoping that better tools will fix communication problems.
Five years after the forced experiment, the lessons are clear enough to draw on. This article examines the collaboration tool landscape with the specificity the decision deserves.
The Tool Categories Every Distributed Team Needs
Modern distributed teams typically require tools across several categories, and understanding what each category does helps prevent adopting the wrong tool for the wrong job.
Real-Time Messaging
Purpose: Quick questions, informal coordination, status updates, channel-based organization, and replacing the overhead of email for internal communication.
Key platforms: Slack, Microsoft Teams, Google Chat, Discord.
Real-time messaging platforms are the ambient environment of distributed work - the digital equivalent of the office floor. They work well for conversations that matter now but will not need to be referenced in detail months later.
They fail when used as the system of record for decisions, processes, or institutional knowledge. Anything important said in Slack should be written down somewhere more permanent.
Video Conferencing
Purpose: Face-to-face discussion for complex topics, relationship building, presentations requiring visual context, and conversations where emotional nuance matters.
Key platforms: Zoom, Google Meet, Microsoft Teams.
Video calls are the most expensive collaboration modality in terms of participant time. A one-hour meeting with eight people costs eight person-hours plus preparation time for participants.
This cost is sometimes worth it and sometimes not - the question is whether synchronous, video-enabled conversation is actually necessary for the specific purpose, or whether a written document, a Loom recording, or an asynchronous discussion thread would serve as well.
Asynchronous Video
Purpose: Demonstrations, walkthroughs, explanations of complex topics, and communications that benefit from visual context but do not require real-time presence.
Key platforms: Loom, Vidyard, Mmhmm.
Asynchronous video is one of the most underused categories in the collaboration tool landscape. A five-minute Loom recording can replace a thirty-minute synchronous meeting: the creator records once, recipients watch at their convenience (and at 1.5x or 2x speed), and they can rewatch sections they did not follow.[8]
For code walkthroughs, design feedback, process explanations, and complex technical documentation, asynchronous video is often superior to both text and synchronous calls.
Project Management
Purpose: Task tracking, workflow coordination, dependency management, progress visibility, and sprint or project planning.
Key platforms: Linear, Jira, Asana, Monday.com, Trello, ClickUp.
The failure mode for project management tools is that the administrative overhead of maintaining them exceeds their coordination value. Teams that spend more time updating task statuses than completing tasks have misconfigured either the tool or the process.
The right project management implementation is the minimum that provides necessary visibility without creating unnecessary overhead.
Document Collaboration and Knowledge Management
Purpose: Shared writing, documentation, decision records, onboarding materials, and maintaining an accessible organizational knowledge base.
Key platforms: Notion, Confluence, Google Docs, Coda.
The distinction between short-term documents (working documents, meeting notes, drafts) and long-term knowledge assets (processes, architectural decisions, reference documentation) matters for tool selection.
Short-term documents benefit from simplicity and speed of creation; long-term knowledge assets benefit from structure, discoverability, and maintenance.
Visual Collaboration
Purpose: Whiteboarding, design thinking, planning workshops, diagramming, and visual explanations that text-based tools cannot adequately support.
Key platforms: Miro, FigJam, Excalidraw, Lucidchart.[9]
Visual collaboration tools have become substantially more important in distributed work because the physical whiteboard - the default surface for visual thinking in co-located offices - is unavailable. Digital whiteboarding satisfies a different set of needs than text and video communication and deserves its own consideration.
The Messaging Platform Decision
The messaging platform is the ambient environment of distributed work. It shapes daily rhythm, information flow, and informal culture in ways that other tools do not. Choosing poorly compounds daily.
"The tools were the least important variable. Teams that had genuinely dysfunctional communication before the pandemic did not become functional because they started using Slack. Tools amplify what is already there - good communication culture or poor communication culture." - Cal Newport, 'A World Without Email'
Slack: The Tech Industry Default
Slack dominates messaging adoption in technology companies and startups for reasons that hold up under scrutiny. Its search capability is genuinely excellent - finding a specific conversation from months ago is fast and reliable.
Its integration ecosystem, with connections to more than 5,000 applications, makes Slack the connective tissue between the other tools a team uses.[5]
GitHub notifications, deployment alerts, analytics summaries, and customer support escalations can all flow through configured Slack channels, creating a single stream of relevant organizational information.
The threading model, when adopted consistently, keeps channels readable despite high message volume. Without threading discipline, channels become unreadable streams of interleaved conversations - but threading discipline is a norm issue, not a tool issue.
The cost scales with team size in ways that become uncomfortable for large organizations. At $7-12 per user per month, a 500-person organization pays $42,000-$72,000 annually for messaging. This is not obviously unreasonable for genuinely necessary infrastructure, but it is a cost that warrants regular evaluation.
Example: Stripe's engineering team has published descriptions of their Slack channel organization practices, including conventions for channel naming, expected response time norms by channel type, and policies for when to use threads versus direct messages.
The documented norms create a consistent environment that scales across hundreds of engineers without requiring constant coordination overhead. The tool's value is inseparable from the norms built on top of it.
Microsoft Teams: The Enterprise Environment
Microsoft Teams has the unusual advantage of being bundled with Office 365 at no additional cost for organizations already paying for the Microsoft productivity suite.[4]
For enterprises deeply invested in the Microsoft ecosystem - SharePoint for document management, Outlook for email and calendar, Office applications for document creation - Teams provides native integration that external tools require additional configuration to approximate.
The video conferencing capability is integrated rather than requiring a separate tool, and the enterprise compliance features (retention policies, data loss prevention, administrative controls) satisfy requirements that regulated industries impose.
The usability trade-off is real. Teams' interface is denser and more complex than Slack's; navigation can be counterintuitive, and the application is noticeably slower in performance. These friction costs are lower for organizations that also prefer Microsoft's broader ecosystem and may find the integration value decisive.
Discord: The Informal Alternative
Discord originated in the gaming community and has since been adopted by tech communities, creative agencies, and organizations that value informal, persistent voice-based collaboration.
Its distinctive feature is always-on voice channels: rooms that team members can drop into and out of throughout the day, creating a sense of ambient presence that video call-centric teams cannot replicate.
The always-on voice model enables spontaneous collaboration that formal video call scheduling makes difficult. A developer who has a quick question can pop into the development voice channel, get an answer in two minutes, and return to focused work - a workflow that is difficult to enable with scheduled meeting culture.
The perception gap is narrowing but real. Many organizations associate Discord with gaming rather than professional use. This association is becoming less accurate as professional communities demonstrate sustained use, but it remains a consideration for client-facing or traditionally-oriented organizations.
Comparison
| Dimension | Slack | Microsoft Teams | Discord |
|---|---|---|---|
| Integration library | 5,000+ | Deep Microsoft + 400 | Limited |
| Always-on voice | Limited (Huddles) | No | Yes |
| Search quality | Excellent | Good | Adequate |
| Cost | $7-12/user/month | Included with O365 | Free-$10/user/month |
| Enterprise compliance | Good | Excellent | Limited |
| Informal culture | Good | Limited | Excellent |
Synchronous vs. Asynchronous: The Most Important Decision
The specific messaging platform matters less than the fundamental question of when to communicate in real time versus asynchronously. This choice determines whether a distributed team is genuinely distributed or merely a co-located team that happens to be remote.
The Cost of Synchronous Communication
Every synchronous meeting has an opportunity cost. For each participant, the meeting time is time unavailable for focused work. For participants in different time zones, synchronous requirements impose constraints on when they can do deep work.
For a team of eight people meeting for an hour, the meeting costs eight person-hours - equivalent to the full workday of a single team member.
This does not mean synchronous communication is wrong. It means it should be chosen deliberately when its distinctive value - real-time response, emotional nuance, collaborative energy, spontaneous course correction - is actually needed.
When Synchronous Meetings Are Worth Their Cost
Complex, ambiguous problems that require iterative, exploratory discussion - strategic decisions, architectural choices with unclear trade-offs, situations where the right answer is genuinely uncertain and needs to emerge through dialogue.
Conflict resolution where emotional tone, empathy, and nonverbal communication matter. Written conflict escalates; voice and video de-escalate. This is not universal but is the typical pattern.
Relationship and trust building that enables the rest of the work. Distributed teams that never talk synchronously tend to have weaker trust and less effective asynchronous collaboration as a result. Regular social interaction is not overhead; it is infrastructure maintenance.
Brainstorming and creative ideation where the spontaneous building-on-ideas-in-real-time produces outcomes that sequential asynchronous exchange cannot replicate.
When Asynchronous Is Preferable
Status updates and informational messages that require no discussion or decision. Posting a deployment success message, sharing a document for review, and announcing a completed milestone are all asynchronous.
Cross-timezone collaboration where synchronous overlap requires someone to work at unreasonable hours. A team spanning San Francisco, Berlin, and Singapore has at most two hours of reasonable overlap. Designing work primarily around synchronous communication imposes significant costs on some team members.
Thoughtful input on complex topics. People produce better-considered responses when they have time to research, reflect, and formulate positions than when responding under the pressure of a live discussion. Asynchronous discussion on design documents often produces better decisions than synchronous meetings.
Everything that does not require real-time response. The question "what is the default?" is important. If synchronous is the default, asynchronous requires justification. If asynchronous is the default, synchronous requires justification. The former costs more in aggregate time; the latter enables more focused work.
Project Management Without Bureaucracy
The failure mode for project management tools is well-documented: the tool becomes a burden that consumes more time than it saves. Team members spend their day updating task statuses rather than completing tasks. Boards look busy while actual work stagnates.
Linear for Engineering Teams
Linear has become the preferred project management tool in engineering-focused organizations for reasons that reflect thoughtful product design.[6] The keyboard-first interface allows experienced users to navigate, create, and update issues without reaching for a mouse.
GitHub integration means that pull request merges automatically move linked issues to "done" without manual status updates. The sprint management workflow is simple enough to use without dedicated project manager attention.
Example: A 40-person startup engineering team switched from Jira to Linear in 2022 after accumulated frustration with the administrative overhead of maintaining their Jira configuration. The switch reduced the time their teams spent on project management administration from an estimated 15-20% of the week to 5-7%.
The reduction came primarily from eliminating configuration complexity and automatic status updates from GitHub integration.
Principles for Low-Overhead Project Management
Track meaningful units of work, not sub-hour tasks. If a task takes less than an hour, it likely does not need its own ticket. The overhead of creating, assigning, and updating a ticket costs nearly as much as the task itself.
Every task has a single accountable owner. Shared ownership is no ownership; when multiple people are responsible, the task is effectively nobody's responsibility.
Tasks are actionable and specific. "Improve performance" is not a task. "Reduce API response time for the /users endpoint from 400ms to under 150ms" is a task.
Status should reflect reality, not aspiration. "In progress" should mean work is actively happening, not "I intend to start this when I finish the current task."
Start simple and add structure only when a specific pain point demands it. A shared document with a list and names next to items serves small teams adequately. Project management complexity should be justified by actual coordination failures, not by theoretical future needs.
The Mistakes That Break Distributed Teams
The patterns of failure in distributed collaboration are well-documented and consistent.
Meeting overload is the most common. Teams that transfer office meeting culture directly to video calls discover that Zoom fatigue is real and that the flexibility of distributed work disappears when the calendar is full of calls.[1] The default should be asynchronous; synchronous should require justification.[2]
Notification chaos makes focused work impossible. Every Slack channel configured with full notifications, every email triggering immediate alerts, every calendar event producing a five-minute warning - the cumulative effect is an environment where no sustained attention is possible.[3]
Notification management is a professional responsibility, not a personal preference.
Documentation debt accumulates when decisions are made in meetings and conversations rather than in writing. Verbal decisions are invisible to absent team members, forgotten within weeks, and impossible to search. A team that makes decisions verbally and does not write them down is continuously losing institutional knowledge.
Isolation without intervention happens when distributed teams are fully asynchronous without deliberate investment in social connection.
The casual relationships that form around shared physical space - lunch conversations, hallway interactions, the ambient social texture of an office - do not happen automatically in distributed work. They require deliberate creation.
Tool sprawl fragments information across platforms and increases cognitive overhead. When the team uses Slack, Email, Teams, Notion, Confluence, and three different project management tools, the question "where should I look for X?" is never clearly answered.
Consolidation and explicit assignment of tool purposes are ongoing maintenance tasks.
See also: Remote Tech Careers, Tool Overload Explained, and Developer Productivity Explained.
What Research Shows About Collaboration Tools
Professor Gloria Mark at the University of California Irvine's Department of Informatics has spent over 20 years studying how digital communication tools affect knowledge worker performance.
Her 2008 paper with Daniela Gudith and Ulrich Klocke, "The Cost of Interrupted Work: More Speed and Stress," published in the ACM CHI Conference Proceedings, found that workers took an average of 23 minutes and 15 seconds to return to a task after an interruption, and that digital communication tools were the primary source of interruptions (accounting for 41% of observed disruptions in workplace studies).
In her 2023 book "Attention Span: A Groundbreaking Way to Restore Balance, Happiness and Productivity" (Hanover Square Press), Mark synthesized 20 years of field research to show that average attention spans on a single screen had fallen from 2.5 minutes in 2004 to 47 seconds in 2020 - a change she attributes significantly to the proliferation of real-time messaging platforms.
Mark's research specifically found that Slack-style tools, while enabling faster communication, caused knowledge workers to check communications an average of 74 times per day, with each check requiring a recovery period that added up to over 2 hours of lost focused work daily.[10]
Dr. Tsedal Neeley, the Naylor Fitzhugh Professor of Business Administration at Harvard Business School, published "Remote Work Revolution: Succeeding from Anywhere" (Harper Business, 2021) based on research across 63 distributed organizations over 9 years.
Neeley's research found that remote team performance depended less on which collaboration tools teams used than on the norms and rules teams established around those tools.
Teams that explicitly defined expected response times for different communication channels - distinguishing urgent from non-urgent - outperformed teams with ambiguous communication norms by 34% on objective project completion metrics.
Her research identified that the highest-performing distributed teams used an average of 3.2 dedicated communication tools (compared to 5.7 for average-performing teams), and that each additional tool beyond four was associated with a measurable decrease in team coordination efficiency.
Neeley's work has been adopted by distributed-first companies including GitLab, Automattic, and Basecamp as the basis for their communication norms documentation.
Researchers at Microsoft Research, including Sonia Jaffe, Robert Holtz, Siddharth Suri, and Sherry Scott, published "Collaboration Patterns and Productivity" in the Journal of Applied Psychology (2021) analyzing communication data from over 60,000 Microsoft employees over the first 18 months of the COVID-19 pandemic.
Their dataset covered 122 billion communications including emails, Teams messages, meeting records, and document collaboration events.
Key findings: the shift to remote work caused collaboration networks to become 25% more siloed - interactions with groups outside immediate teams declined - while within-team communication increased 22%.
This had measurable consequences: cross-team knowledge transfer, which had previously occurred informally in physical offices, required deliberate design in digital-first environments.
Teams that implemented formal cross-team communication rituals (cross-functional slack channels, weekly interdepartmental updates) maintained pre-pandemic levels of cross-team collaboration, while those without such structures saw a 38% decline.
The research formed the empirical basis for Microsoft's "hybrid work" design recommendations.
Professor Sara Beckman at UC Berkeley's Haas School of Business and Dr. Michael Barry at the Stanford d.school published "Innovation as a Learning Process: Embedding Design Thinking" and related research on creative collaboration tools in digital environments.
Their 2019 study of 140 product teams at 22 companies, published in the California Management Review, found that teams using visual collaboration tools (digital whiteboards, collaborative diagram tools) for ideation produced 31% more viable concepts per session than teams conducting the same sessions through video-only conferencing.
The improvement was attributed to "visual anchoring" - having a shared visual workspace gave team members a reference point for abstract ideas that reduced miscommunication and enabled building on each other's contributions more effectively.
Teams that used text-based collaboration tools (messaging, shared documents) for creative work performed worst on concept generation metrics, producing 42% fewer viable concepts than visual collaboration tool users.
Real-World Case Studies in Collaboration Tools
GitLab, the DevOps platform company, has operated as a fully remote organization since its founding in 2014 and with over 2,000 employees across 65 countries became one of the world's largest all-remote companies.
GitLab publicly documents its collaboration practices in its "GitLab Handbook," a 2,000-page public document describing every operational process.
Their documented approach to collaboration tool selection is rigorous: GitLab evaluates all collaboration tools against explicit criteria including asynchronous capability, transparency (whether information is accessible to all team members), searchability, and data portability.
Their 2022 Remote Work Report, based on surveys of 3,900 remote workers, found that organizations with documented communication norms (which tool to use for which purpose, expected response times per channel) reported 29% higher employee satisfaction with their work systems and 23% lower onboarding time for new team members.
GitLab attributes significant competitive advantage to its collaboration infrastructure, noting that their ability to hire from 65 countries gives them a talent pool 10 times larger than location-constrained competitors.
Shopify's shift to distributed-first work in 2020, described in a presentation by VP of Product Farhan Thawar at the 2021 Web Summit and documented in the company's engineering blog, involved a structured reconfiguration of their collaboration tool stack.
Before the transition, Shopify used approximately 15 communication and collaboration tools. Post-transition, they consolidated to 6 core tools with explicit policies governing which tool served each communication type.
The consolidation process, led by Head of Remote Work Janice Sutherland, took 4 months and included a 6-week survey period to understand actual usage patterns before making elimination decisions.
The result: meeting time across the organization fell by 28%, with Thawar attributing this to clearer documentation norms that replaced synchronous meetings for information-sharing purposes.
Employee survey data from 2021 showed that 74% of Shopify employees rated their collaboration tool environment as "significantly better" than pre-consolidation, primarily due to reduced tool-switching overhead.
Atlassian, the collaboration software company (makers of Jira, Confluence, and Trello), conducted its own internal research on collaboration patterns published as the "State of Teams 2023" report and presented by Head of Research Annie Dean at the Atlassian Team Anywhere Summit.
Analyzing collaboration data across Atlassian's 10,000+ employees and surveying 10,000 knowledge workers at other companies, Atlassian found that teams with explicit "team agreements" documenting collaboration norms saved an average of 3.5 hours per person per week compared to teams without documented norms.[7]
The primary savings came from fewer clarification conversations (when communication norms are explicit, fewer misunderstandings require follow-up), faster decision-making (documented decision frameworks reduced discussion time), and reduced notification management overhead (defined notification expectations reduced checking frequency).
Atlassian used these findings to build the "Team Anywhere" product features into their collaboration suite, including structured team health monitors and asynchronous decision templates.
Companies that consolidate onto an all-in-one workspace platform such as Notion often replace several overlapping internal tools at once - a company wiki, project documentation, meeting notes, announcements, and onboarding materials - that previously lived across multiple systems with different search interfaces and access controls.
The primary driver is information fragmentation: staff frequently cannot locate internal documentation because it is scattered across tools.
Organizations that report on such consolidations typically describe meaningful reductions in time spent searching for information and in duplicated documentation, after an upfront investment in migration and change management.
Sources & Further Reading
- Buffer. "State of Remote Work 2023." buffer.com. View source
- Fried, Jason and Hansson, David Heinemeier. Remote: Office Not Required. Crown Business, 2013. View source
- Newport, Cal. A World Without Email: Reimagining Work in an Age of Communication Overload. Portfolio, 2021. View source
- Microsoft. "Microsoft Teams Feature Documentation." Microsoft Learn. View source
- Slack. "How Slack Works." slack.com. View source
- Linear. "Linear Method: Building Better Software." linear.app/method. View source
- Atlassian. "State of Teams 2023." atlassian.com.
- Loom. "Async Video Messaging for Work." loom.com. View source
- Miro. "Online Collaborative Whiteboard Platform." miro.com. View source
- Mark, Gloria, Gudith, Daniela, and Klocke, Ulrich. "The Cost of Interrupted Work: More Speed and Stress." CHI 2008. View source