HomeField notes › Drowning in Too Many Work Tools? Here's the Way Out

Drowning in Too Many Work Tools? Here's the Way Out

By the founder · an operator who automated their own worklife

I built Standfast because I was drowning in too many work tools. Not metaphorically — I'd open my laptop in the morning and stare at six tabs, each one holding things that were quietly mine to handle. Email. Calendar. The project tracker. The CRM. A shared doc someone left a comment on. A chat thread that scrolled past three days ago with a question still hanging in it. None of them talked to each other, and all of them assumed they were the only thing I'd open that day.

If that feels familiar, you're not disorganized and you're not behind. You're an operator without a chief of staff, holding accountability across more systems than any one head can track. The tools didn't make you more productive. They spread you thinner and called it visibility.

Why drowning in too many work tools is a structural problem, not a discipline problem

The usual advice for this is some flavor of "just be more disciplined." Get to inbox zero. Time-block your calendar. Adopt a methodology. I tried all of it, and here's what I learned: the problem isn't your willpower. The problem is that work that needs you is scattered across tools that each demand a full sweep to surface anything.

Think about what it actually takes to answer one simple question — what needs me today? You open email and skim forty threads to find the four that are genuinely waiting on you. You open the project tracker and scan for cards assigned to you or blocked on you. You check the CRM for the renewal that's gone quiet. You glance at the calendar to see which of today's meetings needs prep. Each tool is its own triage pass. By the time you've done all of them, you've spent ninety minutes and you haven't actually done anything yet. You've just located the work.

That's the trap. Every additional tool multiplies the surface area you have to scan, and none of them know what the others are holding. The cost isn't the tools themselves — most of them are fine. The cost is the integration work your brain does for free, every single morning, with no leverage and no memory.

The three things that actually slip through the cracks

When I started paying attention to what I dropped when I was overloaded, it was always one of three categories:

Notice that none of these are about doing more work. They're about not losing track of the work that's already yours. The volume isn't the enemy. The scatter is. If you want a sharper system for catching these, I wrote a separate piece on how to stop dropping the ball at work that goes deeper on the open-loop problem.

How to get out from under it (even without a new tool)

You don't need to buy anything to start fixing this. Here's the manual version of what eventually became the product I built.

1. Stop treating every tool as a separate to-do list

The mistake is letting each tool own a slice of your attention on its own schedule. Email pings, so you live in email. A card moves, so you live in the tracker. Instead, pick one moment — once in the morning is enough — to pull from all of them into a single view. A page. A doc. A notebook. The format doesn't matter; the consolidation does.

2. Triage by "does this need a decision from me," not by recency

Most tools sort by newest. That's exactly backward for an operator. The newest thing is rarely the most important; it's just the loudest. When you pull everything into one place, sort by a different question: does this need me specifically, or could it move without me? Anything in the second bucket isn't yours to carry today.

3. Decide once, then close the loop

For each item that's genuinely yours, do one of three things immediately: reply, delegate, or schedule. The thing that kills operators isn't the deciding — it's re-deciding. Every time you re-read the same email and think "I'll deal with that later," you pay the full cost of context again. Touch it once, make the call, move on.

Why I stopped trusting tools that promised to "run" my work

There's a whole category of software now that says it'll handle the overload for you — automatically reply, automatically triage, automatically act. I went looking for exactly that, because I was tired. And then I imagined it sending something in my name to a client I'd been managing carefully for two years, and I closed the tab.

The problem with drowning in too many work tools is real. But the answer isn't handing your judgment to something that doesn't have the context you have — the history with that customer, the politics of that deal, the reason you'd phrase this one carefully. The answer is getting your context in one place fast, so you can make the calls quickly. That distinction — counsel versus autopilot — is the whole reason I built what I built, and it's the subject of why I'll only trust AI that drafts but doesn't send.

This is the thing I want you to take away: you are not failing because you can't keep up with six tools. No one can keep up with six tools by sweeping each one by hand every morning. What you need isn't more discipline or another app to check. You need one brief that reads across everything and tells you what's on fire, who's waiting, and what's blocked — so the scatter becomes a single ten-minute decision instead of a ninety-minute hunt.

That's what I'm building Standfast to do: read across your email, calendar, tracker, and CRM each morning and hand you one brief of what actually needs you — with the reply already drafted in your voice, ready for your call. It never sends on its own. If you're tired of drowning in too many work tools and want it to feel like a decision instead of a swim, join the early-access list.

Stop being your own assistant.

One daily brief of what needs you, with the replies already drafted in your voice. It drafts. You decide. Nothing is sent without you.

Join the early-access list

More field notes

What Needs Me Today at Work: A System That WorksA Chief of Staff for Founders and Operators (No Hire)AI That Drafts Email But Doesn't Send: The Case