How to Stop Work Slipping Through the Cracks Across Email and Slack
Work slips through the cracks because the place a commitment is made and the place it is tracked are different, and moving it between them is a manual step that a busy person skips.
That’s the entire problem. Someone asks for something in a Slack thread or an email, you intend to do it, and the intention never becomes a tracked item. Nobody decided to drop it. The handoff just never happened.
The fixes below are ordered by how much they actually change that, from least to most. We build this+that, which is the fourth approach, so read the last section knowing we have an interest in it. The first three are what most teams should try first.
Why it happens, specifically
Three conditions have to line up for something to be dropped, and in email and chat they line up constantly.
The request does not look like a task. It arrives as a sentence in the middle of a conversation. “Can you send the updated deck before Thursday” is a commitment, but it is formatted identically to the rest of the thread.
Nobody agrees to own it. In a channel with four people, a request addressed to the group is a request addressed to nobody. Everyone assumes someone else has it.
Capturing it costs more than reading it. Reading the message takes two seconds. Opening the task manager, writing a title, adding context and assigning an owner takes a minute. Under load, people read and defer.
The load is not modest. Microsoft’s study of the infinite workday puts the average at 117 emails and 153 Teams messages a day, with an interruption every two minutes. Any fix that depends on a person reliably performing a small manual step, 270 times a day, is not a fix.
Approach 1: Agree where work lives, and enforce it
The cheapest change is a rule: a request is not real until it is in the tracker. Say it out loud in team meetings, get everyone to agree to it, write it in the team handbook, print it on t-shirts, and have people reply in the thread with a link to the ticket.
What it fixes: ambiguity about ownership, and the “I thought you had it” failure.
What it does not fix: the capture cost. You have made the manual step mandatory without making it cheaper, so people follow the rule when they have slack in their week, and when they don’t they either skip it or get stressed keeping it up.
Worth doing anyway, because every other approach works better on top of a team that agrees where work lives.
Approach 2: Use the capture shortcuts your tools already have
Most task managers can create a task from a message without much typing. Slack’s Asana, Linear, Jira and Todoist integrations turn a message into a task from the message menu. Gmail can push a mail into Google Tasks. Superhuman, Shortwave and similar clients have their own versions.
What it fixes: most of the capture cost. A minute becomes a few seconds.
What it does not fix: noticing. Someone still has to recognize the sentence as a commitment and decide to act, in the two seconds before the next message arrives. Shortcuts help the messages you catch and do nothing for the ones you skim past.
This is the highest-value change for most teams, and it is free.
Approach 3: Follow-up and reminder tools
A layer that watches for sent messages with no reply and nudges you: “you asked about this four days ago.” Several email assistants do this well, and it is the core of tools like Fyxer and Serif.
What it fixes: the outbound half. Things you asked for that went quiet.
What it does not fix: the inbound half, which is usually bigger. A reminder about a message you sent does not help with the request someone made of you in a thread you read on your phone and never came back to.
Approach 4: Extraction, where the message itself creates the task
The last approach removes the manual step instead of shortening it. Software reads the message stream, recognizes the requests and commitments inside it, and creates tracked, assigned tasks without anyone deciding to capture anything.
This is what we build. this+that reads Gmail, Outlook, Slack, Microsoft Teams, Google Chat, and WhatsApp Business as one stream and turns the work inside them into tasks with an owner and a link back to the message they came from, then runs workflows against them.
What it fixes: noticing and capture together, which is the pair that actually causes the problem.
What it costs, honestly: you are trusting software to judge what counts as a commitment, so it will create tasks you would not have and occasionally miss ones you would. It needs access to your mail and chat, which is a real decision rather than a formality. And it changes where your team looks in the morning, which is a habit change no tool avoids.
Who else is in this space: Chaser does task tracking inside Slack, though tasks are created deliberately rather than extracted. Viktor executes work you ask it for in Slack or Teams. Task managers like Asana and Linear are where extracted work often belongs afterward.
Which one to pick
If your team has never agreed where work lives, start there. No tool fixes a team that tracks work in four places.
If you have agreed and things still slip, use the capture shortcuts. Free, immediate, and it addresses the biggest single cost.
If what slips is mostly things you asked others for, a follow-up tool is the targeted fix.
If what slips is mostly requests made of you and your team, across more than one channel, extraction is the only approach that addresses noticing. That is the case we built for, and it is also the case where the other three underperform, because they all assume a person spotted the request.
Frequently asked questions
Why do task managers not solve this on their own? Because a task manager starts from a task. Everything before that, noticing the request and writing it down, happens in the message thread and is still manual.
Does turning on more notifications help? It usually makes it worse. The problem is not that messages go unseen, it is that seen messages do not become tracked work. More alerts add interruptions to a day that already has one every two minutes.
What about asking people to send requests as tickets? It works inside a team that agrees to it and fails for anything arriving from outside: clients, suppliers, candidates. You do not control how other people ask you for things.
How do you track commitments made over chat automatically? Either a person captures them with an integration shortcut, or software reads the channel and extracts them. The first is reliable when someone remembers; the second does not depend on remembering.
Is there a free way to start? Yes. Agreeing where work lives costs nothing, and the message-to-task shortcuts in Slack, Gmail and most task managers are included in plans you already pay for.