The Two-List Rule: How to Make the Big Calls and Stop Making the Small Ones

Leadership & Decision Making

On a ship, not every decision belongs to the same person. The officer of the deck doesn't wait on the captain to change course for a fishing boat crossing the channel. But if the ship is heading into contested water, that call goes up the chain — fast, and to the right person.

Most solo business owners never learned that distinction. You built the business, so every decision feels like it has to run through you — what font goes on the invoice, whether to raise your rates, which CRM to use, who to hire, whether to walk away from a bad client. It all lands on the same desk. Yours.

That's not discipline. That's a bottleneck. And it's the reason a lot of owners are exhausted by decisions that shouldn't have taken more than thirty seconds, while the decisions that actually move the business get made in a rush, late at night, with half the facts.

Two Kinds of Decisions, Not One

Every decision your business faces falls into one of two categories. Once you can sort them fast, you stop treating a $40 software choice with the same weight as a decision that could sink the year.

The test is simple: if this goes wrong, how long does it take to fix, and what does it cost me to fix it? If the answer is "an afternoon and a few dollars," it's a Watch Decision. If the answer is "months and real money," it's a Command Decision.

Why Owners Get This Backward

In my coaching practice, I see the same pattern over and over: owners agonize over the reversible stuff and rush the irreversible stuff. It's backward, and it's not because they're bad at business. It's because Watch Decisions feel urgent — there's an email sitting in the inbox, a form waiting to be filled out — while Command Decisions feel uncomfortable, so they get pushed to "when I have more time." That time rarely comes on its own. It has to be made.

The fix isn't working harder. It's changing what you let take up your bandwidth.

How to Handle Each One

For Command Decisions:

• Give it real time. Sleep on it at least once before you commit.
• Write down what you'd need to be true for this to work — then check whether it actually is.
• Talk it through with someone who isn't afraid to tell you it's a bad idea. Not a cheerleader. A second set of eyes with no stake in the outcome.
• Decide the timeline before you decide the answer. A deadline keeps a Command Decision from turning into a permanent state of "still thinking about it."

For Watch Decisions:

• Set a rule once, and stop re-deciding it. If you've picked an invoicing tool, you're done. Don't reopen it every quarter.
• Give yourself a time cap — five minutes, ten minutes — and go with your gut when the clock runs out.
• If you have any help at all — a contractor, a part-time assistant, a spouse who helps with the books — hand these off. Give them the boundaries, then let them decide inside those boundaries without checking back with you.

Delegation Isn't Abdication

A lot of owners avoid delegating Watch Decisions because they're afraid it means losing control. It doesn't. It means defining the boundaries clearly enough that someone else can operate inside them without you standing over their shoulder. Give them the intent — what you're trying to accomplish and why — and let them figure out the "how." That's not losing control. That's how you get your time back for the decisions that actually need you.

If you're a business of one right now, you can still apply this. "Delegating" a Watch Decision might just mean setting a personal rule so you're not re-deciding it every time it comes up, or using a template instead of writing every email from scratch. The goal is the same: protect your attention for the decisions that are actually hard to reverse.

The Bottom Line

You didn't start this business to spend your energy on decisions that don't matter in six months. Sort your decisions before you make them. Give the big ones the time and scrutiny they deserve. Get the small ones off your desk. That's not a productivity hack — it's how you protect the judgment you're going to need when a real Command Decision shows up.