HomeField notes › What Needs Me Today at Work: A System That Works

What Needs Me Today at Work: A System That Works

By the founder · an operator who automated their own worklife

Every morning, the only question that really matters is also the hardest one to answer: what needs me today at work? Not what's in my inbox. Not what's on my calendar. Not what's in the tracker. What — across all of it — actually requires a decision, a reply, or a nudge from me specifically, before the day moves on without it?

I spent years answering that question the slow way: by opening every tool and reading everything until the important items surfaced by attrition. It works, in the sense that you eventually find what's urgent. It also costs you the first ninety minutes of your day and a meaningful chunk of the focus you were going to spend on real work. This is a piece about answering the question faster, and answering it well.

Why "what needs me today at work" is so hard to see

The honest reason is that no tool is designed to answer it. Each one is designed to answer a narrower question. Email shows you what arrived. The calendar shows you what's scheduled. The project tracker shows you what's in flight. The CRM shows you the state of deals. Every one of them gives you a partial view, sorted by its own logic — usually recency — and none of them knows what the others are holding.

So the integration happens in your head. You become the join function across four databases, run by hand, from memory, before coffee. And because you're doing it by hand, you make the predictable human errors: you over-weight the loud thing that just arrived and under-weight the quiet thing that's been waiting four days. You handle what's in front of you instead of what's most important. The scatter doesn't just cost time — it distorts your priorities. I wrote more about that structural problem in drowning in too many work tools; here I want to give you the system I use to cut through it.

The three-bucket brief: a system you can run by hand

Here's the core idea. Instead of asking "what's new," ask three sharper questions and sort everything you find into three buckets. This is the same structure I eventually built into the product, but you can run it manually starting tomorrow.

Bucket one: what's on fire

These are the things that will get worse if you don't touch them today. A client who emailed twice. A deal that's gone silent past the point of comfort. A teammate blocked on your answer. A deadline that quietly moved up. The test for this bucket is simple: does the cost of ignoring this compound? If yes, it's on fire, and it goes to the top regardless of which tool it lives in.

Bucket two: who's waiting on me

This is the bucket operators lose most. These are the people who asked you something and won't ask again — the small approval, the redline, the intro, the "let me know what you think." Nobody re-pings you for these, so they vanish under newer noise, and you slowly become the bottleneck for half a dozen people without ever deciding to be. To find this bucket, scan specifically for open questions addressed to you across email and chat. Not threads you're cc'd on — threads where someone is waiting on your specific reply.

Bucket three: what's blocked on me

Work that can't move until you do one small thing. A sign-off. A decision between two options. A document only you can send. These are usually the shortest items on your list and the highest-leverage, because clearing them unblocks other people's whole day. The trap is that because they're small, they feel skippable. They're not — they're the best return on ten minutes you'll get.

How to actually run the brief in ten minutes

The buckets only help if pulling them together is fast. Here's the routine:

That's the whole system. The discipline that makes it work is refusing to let "read everything" creep back in. You are not trying to be caught up on all information. You are trying to know what needs you, and ignore the rest with confidence.

The part that's hard to do by hand

I'll be honest about where the manual version strains. Doing this well every single day requires you to hold the state of four tools in your head, remember who you were waiting on, notice what went quiet, and not be fooled by recency — at 8am, repeatedly, forever. Some mornings you nail it. Plenty of mornings you're rushed, you skim, and a bucket-two item slips because nobody re-pinged you.

That's the gap I built Standfast to close. The system above is sound; the problem is that humans are inconsistent at running it by hand under load. So I made something that runs the sweep for me — reads across email, calendar, tracker, and CRM each morning and hands me the three buckets already assembled, with a recommended move and a reply drafted in my voice for each one. I read it, I make the calls, I'm done in about ten minutes. It never sends anything on its own; every send is my tap, through my own account.

You can build the manual habit today and it'll genuinely help — start with the three buckets tomorrow morning. And if you'd rather have the brief built for you so the question "what needs me today at work" answers itself before you sit down, 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

Drowning in Too Many Work Tools? Here's the Way OutA Chief of Staff for Founders and Operators (No Hire)AI That Drafts Email But Doesn't Send: The Case