Slack is our source of truth. If it's not in Slack, it doesn't exist.

I'm a designer. Slack + GitHub replaced Figma for design alignment. We iterate in a thread, the dev pushes, the PR lands in the same thread, we validate there. From first iteration to production, no Figma file to maintain.

Unexpected benefit: AI. I connect Claude to Slack through the connector, so a thread becomes a Notion note, a spec, a Figma feature with before/after screenshots, or a vision prototype update, without copy-pasting. As AI does more of the work, the human job becomes alignment, and Slack is where that happens.

It's the last barrier before the in-person meeting. If communication fails in Slack, you book a meeting and waste everyone's time to align. So we try hard to make it work in Slack. The interface is simple, fast, search works, new people just read the channels to onboard. That's the ROI. Review collected by and hosted on G2.com.

Two things.

Notification noise: you have to fight the defaults to get a quiet day, and the onboarding doesn’t help, nobody tells a new user which settings to change. Slack should ship with a quiet preset.

And threads: decisions happen in threads nobody follows, so people miss them even if search finds them later, and we end up re-aligning in a meeting. A “decision” flag on a thread that posts back to the channel would fix most of it.

Also, Slack’s own AI is limited to Slack. When I need an answer that lives half in a thread, half in the repo or in Figma, I go through Claude, not Slack AI.

Performance itself is not the problem: fast, stable, never down. Review collected by and hosted on G2.com.