If your team lives in Slack, you've had this exact moment: someone asks for something in a channel, five emoji-replies later everyone is sure someone is on it, and a week later you're scrolling 300 messages up to find out who that someone was.
Slack is where work is discussed. Kanban is how work moves. Teams want both in one place — that's why "slack kanban board" is such a common search. Here's what's genuinely possible in 2026, what each approach costs you, and where each one falls apart. No affiliate links, no "ultimate top-10" stuffing — just how these setups behave after the first month.
First: does Slack have a kanban board?
Not really. Slack has canvases, lists (in paid plans), and Workflow Builder — none of which are a real kanban board with work-in-progress limits, per-card ownership, or aging/stuck tracking. Slack is a communication layer. Anything kanban-ish you run inside Slack is either an app integration or a workaround that decays within weeks.
That leaves three real options.
Option 1: Emoji-reaction "kanban" (free, breaks in ~2 weeks)
The classic DIY: 👍 = will do, 👀 = working on it, ✅ = done.
What works: zero setup, zero cost, fine for a 2-person duo for a fortnight.
What breaks: cards can't be reordered, there's no board view, history dies in the scroll, and "who owns this" is still a guess. By week three, the channel is both your chat and your filing cabinet — and bad at both.
Verdict: a stopgap, not a system.
Option 2: Slack-first task apps (better, still chat-trapped)
Apps that create tickets from messages via slash commands and manage them mostly inside Slack.
What works: capture is instant — a message becomes a task before it scrolls away. Assignment and reminders happen where people already are.
What breaks: the board. Most Slack-native tools treat the kanban view as a secondary web screen nobody opens. And the two questions a board exists to answer — who owns what, and what's been stuck for a week — stay buried. No WIP limits, no aging alerts, no real flow metrics. You've digitized the pile, not organized it.
Verdict: great inbox capture, weak management layer.
Option 3: Slack for capture + a real kanban board for management (what we'd recommend)
The pattern that survives month two: Slack stays the front door, a dedicated kanban board runs the back office. Messages become cards via slash-command; the board holds the truth about status, ownership, and stuck work; a short digest posts back to Slack so nobody has to "go check the tool."
This is the model behind Otper's Slack integration: /otper create-card drops a message onto the board, every card gets exactly one owner (not "the team"), any card idle for 7 days flags itself amber, and reports generate from the board itself — so the Monday "what's everyone doing" meeting mostly evaporates. It's free for 3 teammates, which covers most small teams trying this for the first time.
What works: you keep Slack's speed and gain the board's memory. Ownership is explicit, stuck work surfaces itself, and you finally get throughput/aging numbers instead of vibes.
What costs: one more tool tab open. That tab is the point — it's where work lives; Slack is where talk lives.
Quick chooser
Team state
2 people, 1 project, 2 weeks of work
Capture is the pain (requests die in threads)
Management is the pain (ownership, stuck work, status meetings)
Right call
Emoji reactions, don't over-tool
Slack-first task app
Slack capture + real board (Option 3)
The takeaway
Slack will never be your project manager, and it shouldn't be — it's the hallway where work is mentioned. The fix isn't a "Slack kanban"; it's a kanban that Slack feeds: capture in the channel, manage on the board. The signal to watch the first month: if you still need a status meeting to know what's late, the setup failed. If the board tells you before anyone asks, it worked.
Disclosure: I build Otper, one of the Option-3 tools mentioned above. The analysis of Options 1–2 is honest anyway — we started building Option 3 precisely because we watched them break.
