2
2 Comments

A simple rule I use to decide if something needs a decision today or can wait

Not a FounderFlow pitch, just a framework I've found useful and wanted to share.

When something lands in front of me, I ask one question: does this need me, specifically, today? Not "is this important" (almost everything feels important in the moment), but does it require my judgment, my signature, or my relationship with a specific person, and does today matter more than this week.

If the answer is no to either half, it waits, gets delegated, or gets batched with similar things later in the week. If yes to both, it jumps the queue no matter how small it looks.

It sounds almost too simple, but it's cut down a lot of the "everything feels urgent" paralysis I used to have running more than one business at once. I ended up building this rule into FounderFlow so it does the first pass for me, but the rule itself works fine on paper too.

Would love to hear if others have a similar filter, or a completely different one.

on July 14, 2026
  1. 1

    I like the question because it separates urgency from ownership.

    One thing I've started asking myself alongside it is, why does this need me?

    Sometimes the answer is that it genuinely requires my judgment. Other times it turns out the process simply isn't clear enough for someone else to handle confidently.

    That second answer has become especially interesting to me, because it often points to an opportunity to improve the system rather than just making another decision myself.

    1. 1

      "Why does this need me" is a great gut check, it's basically the next layer after what FounderFlow already automates for me. Half the time the honest answer is the process isn't clear enough for someone else to run it, not that it actually needs my judgment. That's usually the more useful thing to fix.