How to Stop Dropping Balls at Work (Spoiler: Better Lists Won't Help)
Why dropped tasks aren't a discipline problem and what actually works to stop dropping balls at work. A forensic look at where follow-ups die.
By Ellis Keane · 2026-03-25
If you're searching for how to stop dropping balls at work, here's the part that none of the productivity advice wants to say out loud: you are going to keep dropping them, and it's not because you lack discipline or because you need a better app. The balls get dropped because the systems you work inside were never designed to hold them in the first place.
That framing shifts the problem from personal discipline to system design – and once you make that shift, you can start looking at where the drops actually happen. The answer is almost always depressingly mundane.
Anatomy of a Dropped Ball: Tuesday, 2:47 PM
A product manager – let's call her the PM, because I'm not naming names here – mentions during a standup that the onboarding flow needs copy updates before the next release. She says it in the Slack huddle, briefly, between two other topics. The engineering lead nods. The designer (who joined three minutes late) catches the tail end.
Nobody writes it down. Not because they're lazy, but because it didn't feel like a "task" yet – it felt like a thought, a direction, something that would get fleshed out later. The PM assumes the designer heard it. The designer assumes the PM will create a Linear issue. The engineering lead assumes someone else will follow up because it's not an engineering task.
By Thursday, the PM asks in a Slack channel: "Hey, did anyone start on the onboarding copy?" And now it's a fire drill.
This is the most common failure mode I've seen when people struggle with how to stop dropping balls at work. It's not that anyone forgot. It's that the commitment existed in a conversation, the tracking lived in a different tool, and the bridge between the two was a human being's working memory.
The Gap Between Saying and Tracking
Here's what's interesting about that Tuesday standup: if you went back and searched the Slack huddle transcript, the commitment was technically there. The PM said the words. But "said the words in a conversation" and "tracked in a system where someone is accountable" are two fundamentally different things, and the gap between them is where almost every dropped ball lives.
I started paying attention to this pattern after we kept running into the same failure mode at Sugarbug (well, to be fair, at every company I've worked at – Sugarbug just made me more conscious of it). The drop doesn't happen at the point of execution. Nobody sits down to write onboarding copy and decides not to. The drop happens at the point of capture – the moment between "someone said a thing" and "that thing became a tracked commitment."
"The drop doesn't happen at the point of execution. Nobody sits down to write onboarding copy and decides not to. The drop happens at the point of capture." – Ellis Keane
Working memory is severely limited – Nelson Cowan's research suggests roughly four items at a time – and in a typical standup you're processing updates from three to five people while also thinking about your own update and what you're going to say when it's your turn. The idea that you'll simultaneously identify every implied action item, assess whether it's yours, and write it down in the right tool is (and I say this with genuine affection for the human brain) optimistic to the point of delusion.
Why Better To-Do Lists Won't Stop You Dropping Balls at Work
The standard advice for how to stop dropping balls at work is some variation of: write everything down, use a single source of truth, review your list daily, and follow a system like GTD or bullet journaling. And look, that advice isn't wrong exactly – if you actually did all of that perfectly, you'd catch more things. But it fails for a reason that's so obvious it's almost embarrassing to state: you can only write down what you noticed, and in a room with three people and two competing conversations, "what you noticed" is a wildly unreliable dataset.
The PM in our Tuesday example noticed the commitment because she made it. The designer didn't notice it because she joined late. The engineering lead noticed but categorized it as "not mine" and let it go. Three people, three different mental models of what just happened, and no system in the world can fix that unless it's operating at the layer where the conversation happened – not the layer where someone later remembers to create a task.
This is why "just use Linear" or "just use Notion" or (honestly) "just use any single tool" doesn't solve the dropped ball problem. The tools work fine for things that make it into them. The problem is everything that doesn't.
The Three Places Balls Actually Drop
After watching this pattern repeat across every team I've worked with (ours included, repeatedly), I've come to think there are really only three places where things fall through:
1. The conversation-to-task gap. Something gets discussed in Slack, a meeting, or an email thread, but nobody creates a formal task. This is the most common drop and the hardest to fix with discipline alone, because it requires someone to recognize that a conversation contained an actionable commitment – in real time, while the conversation is still happening.
2. The cross-tool handoff. A task exists in one tool but the follow-up needs to happen in another. The designer gets feedback in a Figma comment, but the fix needs to be tracked in Linear. The engineer merges a PR in GitHub, but the PM needs to update the release notes in Notion. Every handoff is a potential drop – and we've somehow built an entire industry around creating more of these boundaries while simultaneously complaining about them, which is its own kind of achievement.
3. The ownership ambiguity. Everyone heard it, nobody owns it. This is the classic "I thought you were handling that" failure, and it happens most often with cross-functional tasks that don't clearly belong to one team. It's not that people are passing the buck – it's that shared ownership functionally means no ownership unless someone explicitly claims it.
You'll notice that none of these are solved by trying harder, setting better reminders, or adopting a new productivity framework. In each case, the failure point is the same: no owner, no ticket, no follow-up trigger. If you're trying to figure out how to stop dropping balls at work, these three gaps are where to start looking.
What Actually Helps (Without Buying Anything)
I'm not going to pretend there's a silver bullet here, because there isn't (and if someone tells you their tool is the silver bullet, they're selling you something). But there are patterns that reduce the drop rate meaningfully:
Assign during the conversation, not after. If someone says "we need to update the onboarding copy," the next sentence should be "who's taking that?" Not later, not in a follow-up thread – right then, while everyone's context is fresh. This is simple and unglamorous, and in my experience it catches more dropped tasks than any reminder system I've tried.
Make the task tracker the default response. When something comes up in Slack, the instinct should be to create a task immediately, even if it's rough and incomplete. A half-formed Linear issue titled "onboarding copy – see Slack thread" with a link is infinitely better than a mental note that evaporates by the time you finish your coffee.
Run a weekly "what fell through" retrospective. Not a blame session – a genuine pattern review. For each drop, note: where the commitment originated (Slack, meeting, email), which gap it fell through (capture, handoff, ownership), and how many days elapsed before someone noticed. Over time, you'll start to see which gaps are your team's particular weakness, and that's diagnostic information you can actually act on – which is more than most retrospectives produce, in my experience.
Reduce the number of tool boundaries. This one's harder because nobody wants to give up the tools they love (and honestly, most teams shouldn't – Linear is better for issue tracking than Notion, and Notion is better for documentation than Linear, and that's fine). But every additional tool boundary is another place where context can leak, so at minimum, be intentional about which boundaries exist and how information crosses them.
Why This Breaks at Larger Team Size
The strategies above work for small teams with short feedback loops. When your team is five people and you're all in the same Slack channels, "just assign it in the meeting" is practical advice. But as your team grows, the number of conversations multiplies, the number of tool boundaries increases, and the gap between "discussed" and "tracked" widens in ways that no amount of individual discipline can bridge.
The teams that handle it best tend to have some kind of connective layer – something that watches the conversations and the task trackers and the documents and identifies when a commitment exists in one place but not the other. Whether that's a dedicated ops person, a carefully configured automation, or something more intelligent, the principle is the same: you need a system that operates at the gap, not at the individual tools.
Measure Time-to-Detection, Not Perfection
The goal isn't zero dropped balls. That's not achievable, and chasing it leads to the kind of over-tracking obsession where you spend more time managing your task system than doing actual work. The goal is fast recovery – noticing a drop quickly enough that it doesn't become a crisis.
The difference between a dropped ball that costs you a Tuesday afternoon fire drill and one that costs you a client relationship is almost always time-to-detection. If the PM had asked about the onboarding copy on Tuesday evening instead of Thursday, the impact would have been negligible. The ball still dropped, but someone picked it up within hours instead of days.
If you want to know how to stop dropping balls at work, start by measuring how quickly you notice them. Track the median time from when a commitment is mentioned to when it becomes a tracked task – that gap is the real vulnerability, and it's the one most teams never measure.
If you're interested in how dropped tasks relate to broader systems problems (and not just personal habits), we wrote a companion piece on why dropped balls are a signal problem, not a people problem that digs into the structural side.
Stop relying on human memory to bridge the gap between conversation and task. Sugarbug watches for commitments across your tools and surfaces them before they get lost.
Q: Why do I keep dropping balls at work even with a to-do list? A: Most dropped balls aren't forgotten tasks – they're tasks that live in a different tool from where the follow-up happens. A to-do list captures what you remember to write down, but the real drops happen when a Slack message implies an action item that never makes it to your task tracker. The gap between conversation and tracking is where the drops live, and no list can capture what you didn't notice in the first place.
Q: Does Sugarbug help prevent dropped balls across multiple tools? A: Yes. Sugarbug builds a knowledge graph across your tools – Linear, GitHub, Slack, Notion, and others – and surfaces tasks, commitments, and follow-ups that would otherwise fall through the gaps between them. Instead of relying on someone to manually create a task after every conversation, Sugarbug watches for commitments and flags when something discussed hasn't been tracked.
Q: What's the difference between a dropped ball and a missed deadline? A: A missed deadline is visible – everyone knows it's late, there's usually a date on a calendar and a notification when it passes. A dropped ball is invisible until someone notices the absence. The task was never tracked, the follow-up was never assigned, or the commitment lived only in a conversation that scrolled off-screen. Dropped balls are harder to catch precisely because there's no system expecting them.
Q: Can Sugarbug track commitments made in Slack conversations? A: Sugarbug ingests Slack messages and uses its knowledge graph to identify commitments, action items, and implied follow-ups that were discussed but never formally tracked in a project management tool. It connects the conversation layer to the task layer so that things discussed in Slack don't stay only in Slack.
Q: Is it possible to completely eliminate dropped balls at work? A: Honestly, no – and that's OK. The goal isn't zero drops; it's fast recovery. Even the most disciplined teams with the best tooling will occasionally miss something. What matters is how quickly you notice and how efficiently you recover. Teams that measure time-to-detection rather than trying to achieve perfection tend to perform better and stress less about the inevitable occasional miss.