The short list of decisions that stay with you

Jay WestOut of My Head · about 13 min

By the end of this step you have:

Your never-delegate list, five items or fewer, each with the reason it stays
Every top kind from your log marked — rule, hand off, or keep
The AI's challenge to your list, and at least one item you can let go of

The idea

Letting go is hard until you decide what you are holding on to. Until then everything feels like yours, so everything stays. The fix is the opposite of letting go of everything — it is writing down the few things that must stay, so you can stop guarding the rest.

Three tests decide what stays. It cannot be undone, or undoing it is expensive. It sets what the business stands for — your prices, who you will not work for, how you treat a customer when it goes wrong. Or it ties several parts of the business together, where each person can only see their own piece. A price list stands for the business; each call made under it is a rule with limits. Expect much of your log to fail all three. That is the good news.

Already handed most of it off?

Then this short list is not what you guard. It is your job now: the decisions nobody brings you — what to launch, who to hire, which customers to chase — plus the few escalations only you can settle. Write those, and run "What would stop if you were gone for two weeks" to check the single point did not just move to the people you handed to.

An example

The owner of a twenty-person landscaping company writes his list. He starts with eleven items. Against the tests, "approve every purchase over a hundred dollars" fails — it is reversible and routine; it becomes a rule. "Which crew goes where" fails — it becomes a hand-off to his ops lead.

What stays — pricing a commercial contract, firing someone, what the company does when a client's property is damaged, and which new service lines to start. Four items. The other seven had been eating his mornings.

Do this now

Ten minutes. Write your never-delegate list — five items or fewer. Next to each, which test it passes — cannot undo, what we stand for, or ties it all together. Then go through the top kinds in your log and mark each one below: Rule, Hand off, or Keep. Expect most to be Rule or Hand off, and mark lookups (where something is, what a word means) Rule. No log yet, or handed off? List the ten things you decided this month from your calendar and sent mail, add them with "Paste rows instead", give each a kind, and mark those.

Mark each kind: a rule, hand it off, or keep it.

Your Question Log: day 1 of 5 · 0 questions reached you · 0 rules written

No log yet? List the ten things you decided this week, from your calendar and sent mail, with “Paste rows instead”, then name their kinds; they appear here to mark.

Test it

Paste your list into the AI with this — "Here are the decisions I say only I can make, and why. Argue with me. For each, tell me if it truly needs me, or if a written rule with limits would let someone else decide it safely. Be blunt." Keep what survives. Move what does not.

Hand it over

Tell your team the list. Knowing what will always come to you makes it clear that everything else is theirs to decide inside the rules. Hired people and still deciding for them? "Write down who decides what, and up to how much" gives each of them a band and a limit.

If you handed most of it off and still step in, are about to hand a role over, or are selling

Already handed most of it off, and still stepping in? For each person you handed to, write one line — "Inside this, you decide, and I will not overrule you" — and log each time you step in unasked as a row of kind unasked. That count is the one to watch fall.

About to hand a role to someone — a manager, a GM, a lead, or a hire you are still interviewing? Give them five logged cases without your answers; where their calls differ from yours is the training, and how often they match is how ready they are.

Selling, or being asked to? "What would stop if you were gone for two weeks" is the list a buyer asks for.

If you lead under an owner, are an expert with no decision rights, your customers do the asking, or there is nobody to hand to yet

A leader under an owner? Write the list for your part of the business — inside it, you hold the authority — and the short list of what still goes up. Then mark what you send up today that you could stop sending with a written limit. That marked list is a proposal for your role, not a request for permission.

An expert with no decision rights? Write the short list of what only you know — the judgment nobody else could supply — and the rest gets a card. If the bottleneck is someone else's head, paste five of their emails or tickets under this prompt and have them confirm each rule — "Below are cases one person in my business handled. Write the rule you think each one follows, in one line. Group the cases that share a rule, and write each rule as: the rule, when it applies, the exception, the case numbers. Mark a rule shown by one case as weak. Add no rules the cases do not show."

Customers doing the asking, alone or with a team? The list becomes what your AI must never say or decide for a customer — prices it may not change, promises it may not make — and those lines go straight into the instruction it answers from. Nobody to hand to yet? It is what you will not let an AI decide for you, and it goes in your note.

Where it goes wrong

Keeping something because you are better at it. You may be. But better at it is not one of the tests, and keeping things for that reason is how an owner stays the bottleneck.

This step is written for this course from the research in the full curriculum. The research behind it, on howtothink.ai (L-0524, L-0453, L-0523)

Your first step · step 1 is next

Next: step 1, which the rest build on →