Collaboration Tools We Actually Use

Every year, someone promises the next Slack killer or the Notion replacement. We try them, get excited for a week, and then go back to what we know. The collaboration tool graveyard is full of good ideas with bad execution.

This isn't a list of every tool we've tried. It's the ones we use daily after years of experimentation. Your mileage may vary, but these have earned their spot in our workflow.

Communication: Slack (Still)

We've tried Discord, Teams, and various alternatives. Slack isn't perfect, but it's become the default for a reason. The threading works well, the integrations are extensive, and everyone already knows how to use it.

Our Slack rules that keep it useful:

• Channels have purposes - We don't create channels for everything. Each one has a clear reason to exist.
• DMs are for private stuff - Work conversations happen in channels so others can follow along.
• Threads for everything - Reply in threads. Always. It keeps channels readable.
• Status updates matter - Set your status when you're heads down or out. It reduces interruptions.

For client communication, we often use their preferred tool. Some love Slack, others prefer email. We adapt.

Video Calls: Zoom or Google Meet

Both work fine. We default to Google Meet because it's already in Calendar and doesn't require a separate app. Zoom for larger calls or when recording quality matters.

Our meeting philosophy: fewer is better. Most updates can be async. We save calls for discussions that would take 10 messages to resolve, or when we need to see each other's screens.

Documentation: Notion

We resisted Notion for a while. It seemed over-hyped. Then we actually migrated and realized why people love it. Having docs, databases, and wikis in one place with decent search is valuable.

What we use Notion for:

• Project documentation and specs
• Meeting notes with action items
• Client resources and onboarding
• Internal knowledge base
• Templates for repeated processes

What we don't use it for: task management. Notion's project boards are fine, but Linear is better for development work.

Design Collaboration: Figma

Figma ended the "which design tool" debate for us. It's collaborative by default, runs in the browser, and has become the industry standard. When clients share designs, they're almost always in Figma now.

Dev mode has been a game-changer for handoff. Inspecting designs, grabbing CSS values, and exporting assets without bothering designers. It's not perfect, but it's way better than the old screenshot-and-guess approach.

For quick mockups and diagrams, we also use Excalidraw. It's free, fast, and the hand-drawn style makes it clear that sketches are sketches, not final designs.

Code Collaboration: GitHub

GitHub isn't just for code hosting. We use it for:

• Pull requests - Code review with inline comments
• Issues - Bug tracking and feature requests
• Actions - Automated testing and deployment
• Discussions - Longer-form technical conversations

The key is keeping code-related discussion close to the code. When a bug report is in GitHub Issues with links to the relevant code, it's much easier to fix than a vague Slack message.

File Sharing: Google Drive

For documents that need real-time collaboration, Google Docs still wins. Multiple people editing a doc simultaneously, commenting, suggesting changes. It just works.

We use Drive for client-shared folders, contracts, and anything that non-technical stakeholders need to access. Everyone has Google accounts, so there's no friction.

For internal design assets and larger files, Figma handles most of it now.

Quick Sharing: Loom and Screenshots

Loom has saved us hours of meetings. Instead of scheduling a call to walk through something, record a 3-minute Loom. The viewer can watch at 2x speed and pause when needed. Async video beats sync calls for most explanations.

For screenshots and quick annotations, we use the built-in macOS screenshot tools plus CleanShot X for more advanced captures. Being able to quickly share what you're seeing is underrated.

Time Zones and Scheduling

Working with clients and team members across time zones requires coordination. We use:

• Calendly - For scheduling external calls without the back-and-forth
• World Time Buddy - Quick reference for time zone math
• Google Calendar - With time zone display for remote team awareness

What We've Abandoned

Tools that didn't make the cut:

• Basecamp - Good philosophy, too rigid for our workflow
• Confluence - Slow, clunky, Notion does it better
• Teams - Only when clients require it
• Discord - Great for communities, not great for client work
• Trello - Too simple for dev work, Linear replaced it

Integration Matters

The best tools play well together. Our workflow:

• GitHub PR created → notification in Slack
• Linear issue updated → reflects in GitHub
• Calendar event → automatic Zoom/Meet link
• Figma comment → notification to the team

When tools don't integrate, you end up copying information between systems. That's where things fall out of sync.

The Actual Secret

The tools matter less than how consistently you use them. A team that diligently uses basic tools will outperform a team with fancy tools they ignore.

Pick tools that:

• Your team will actually use
• Integrate with your existing workflow
• Don't require constant maintenance
• Are flexible enough to grow with you

Then commit to them. Tool-hopping wastes more time than suboptimal tools.