Barack Obama wore the same two suits. Steve Jobs wore a black turtleneck every day. The popular interpretation is that these were stylistic quirks. The actual reason both gave, explicitly: eliminating clothing decisions preserved decision-making energy for decisions that mattered.
This is decision fatigue research translated into practice. Roy Baumeister’s work on ego depletion established that willpower and decision-making draw from the same finite resource. The resource depletes with use. A trivial decision, what to eat, which file name to use, whether to respond to this email now or later, costs the same resource as a complex strategic decision, just a smaller amount.
For a solo operator making 200+ daily decisions while managing client work, business development, administration, and personal life simultaneously, the cumulative depletion is significant. By the afternoon, the decisions that require your best judgment, pricing, scope, client communication, strategic direction, are being made with a depleted resource. The investment in systematizing the trivial decisions pays direct dividends in the quality of the important ones.
The One-Week Decision Tracking Protocol
Carry a small notebook or open a running note on your phone. For one full work week, track every decision you make. Write it down in real time, not from memory at the end of the day.
A decision is any moment where you chose between two or more options. Include micro-decisions:
- Which task to do next
- Whether to respond to a message now or later
- Which folder to put a file in
- What to name a document
- Whether to bill for the extra 30 minutes
- Which template to use for this client type
- Whether to say yes to a request
You’ll fill pages. By the end of the week, you’ll have 50–100+ recorded decisions, and you’ll notice patterns before you even analyze the data.
At the end of the week, go through your list and categorize each decision as one of three types:
Recurring: This decision happens weekly or more often. You’re making the same choice repeatedly.
Unclear-values: This decision took more than 5 minutes, required real deliberation, or created anxiety. It signals that you don’t have a clear principle for this category.
Doesn’t matter: The outcome is genuinely irrelevant. Either option was fine. You deliberated on something that didn’t deserve deliberation.
Category 1: Recurring Decisions, Write the Rule
Any decision you make more than once per month should have a standing rule. You write the rule once and follow it automatically thereafter.
Examples of recurring decisions and the rules that replace them:
“When do I send invoices?” Rule: Invoices go out on the same business day as project milestone completion, always. No batch billing at month-end, no “I’ll send it this week.” Milestone hits, invoice goes out. One rule, zero recurring decisions.
“What do I do with this new file?” Rule: Every deliverable goes in [Client] > [Project] > [Deliverable Name + Date]. Every reference document goes in [Client] > [Background]. Every internal document goes in [Internal] > [Category]. One correct location for every file type, no deciding.
“Should I follow up with this prospect?” Rule: Every prospect gets two follow-ups after a proposal: one at 5 business days, one at 10 business days. If no response after follow-up 2, move to “Closed Lost” and remove from active attention. No case-by-case decisions about whether to follow up and when.
“Should I take this call?” Rule: Any call not booked through my scheduling link gets declined with the scheduling link sent. No ad-hoc calls. One rule, zero decisions.
“Should I discount for this client?” Rule: My rates are my rates. No discounts for scope, no discounts for “potential future work,” no “we’ll pay you back on the next project.” The rule eliminates the recurring internal negotiation.
For each recurring decision you identify: write the rule in a “Standing Rules” document (one page in Notion, a sticky note, wherever you’ll see it). After 30 days of following the rules, they become automatic.
A rule isn’t about being rigid. It’s about pre-deciding in a moment of clarity so you don’t have to decide in a moment of pressure. The version of you who writes the rule has more perspective than the version of you who faces the situation in the moment.
Category 2: Unclear-Values Decisions, Document the Framework
Decisions that take more than 5 minutes signal that you don’t have a clear principle for that domain. The solution isn’t to decide faster, it’s to clarify the underlying value once, so the decision is easier next time.
Examples:
“Should I take this project?” This takes a long time if you haven’t defined your acceptance criteria. Write them once: minimum project value ($X), client type (B2B only, or specific industries), timeline requirements (minimum X weeks lead time), scope type (what you do and don’t take on). With written criteria, project evaluation takes 5 minutes instead of 30.
“Should I raise my rates?” This creates anxiety if you haven’t decided what triggers a rate increase. Write the trigger criteria once: rate increases happen when my booking rate exceeds 80% for 2 consecutive months, or annually on January 1st at minimum 10%, whichever comes first. Decision made. No more case-by-case agonizing.
“Is this scope creep or part of the project?” This is a values question about what you agreed to. Solve it at the contract stage (specific scope definition in every contract) rather than every time a request comes in. With a clear scope definition, the decision is a comparison: does this request fall within the defined scope? Yes or no.
For each unclear-values decision you identify: write the framework, the criteria and principles that should govern decisions in that category. Store it in your Standing Rules document. Revisit it when you face a new instance of that decision type.
Category 3: Doesn’t-Matter Decisions, Eliminate or Randomize
Some of your decisions literally don’t matter. The outcome is the same either way, or the outcome is so minor that deliberation is a pure waste.
Examples:
- Which font to use in an internal document
- What order to tackle your email responses
- Which coffee shop to work from
- What to name a draft file that only you will see
- Whether to reply to a non-client email now or in 20 minutes
The elimination protocol for doesn’t-matter decisions: pick any option immediately, or create a randomizer (flip a coin, alternate, always pick the first option). The deliberation time is always wasted, the outcome doesn’t justify the cognitive cost.
This sounds trivial, but accumulated across a week, doesn’t-matter decisions represent a surprising amount of time and mental noise. Track them for a week and you’ll see the pattern. Most solos find 15–20 genuinely inconsequential daily decisions that they’ve been treating as meaningful choices.
The 30-Day Reduction Protocol
Week 1: Track all decisions as described. Don’t change anything, just observe.
Week 2: Write standing rules for every recurring decision identified in week 1. Start following the rules.
Week 3: Write decision frameworks for every unclear-values decision identified. Test them against the current week’s instances.
Week 4: Implement the doesn’t-matter elimination protocol. For every item in that category, write “always pick [option] or randomize” next to it.
After 30 days: Re-run the tracking for one day (not a full week). Count how many of the decisions you’re still making individually versus following a rule. The gap is your reduction.
Most solos find after 30 days that 30–50% of their recurring decisions are now automatic (rule-following), 20–30% of unclear-values decisions are faster because the framework exists, and virtually all doesn’t-matter decisions are eliminated from active consideration.
The Three Categories Most Solos Can Eliminate Immediately
If the full one-week audit feels like too much right now, start with these three. They represent the highest decision volume in most freelance businesses:
1. Scheduling. Set up Calendly or equivalent. Every scheduling request gets the link. No more back-and-forth about availability, no more “does Tuesday work for you?” threads. One setup, zero recurring scheduling decisions.
2. Billing timing. Decide once: when do you invoice? On milestone completion, on the first of the month, on delivery? Pick one and write the rule. Never decide billing timing again.
3. File naming and storage. Create a folder structure template and a naming convention document. Every new project gets the template applied on day one. Every file has one correct location based on the convention. No more “where did I put that?” and no more “what should I name this?”
These three alone cover 20–40 daily micro-decisions for most solos. The cognitive energy recovered is immediate and real.
Decision fatigue isn’t just about being tired. It’s about the quality of your judgment degrading in ways you can’t detect in the moment. The decision you make at 4pm on a Friday is made with a depleted resource. Systematize what can be systematized, protect the resource for what can’t.
What Happens When the Rules Are Wrong
Standing rules will occasionally produce the wrong outcome. A specific situation will arise where your “always invoice on milestone day” rule creates a problem, or your “no discounts ever” rule costs you a project you genuinely should have taken.
The response isn’t to abandon the rule, it’s to update it. “No discounts ever” might become “no discounts for standard projects; volume discounts considered for contracts over $20K on a case-by-case basis.” The rule still handles 95% of cases automatically; you’ve just defined the exception category explicitly.
Rules get better over time as you encounter edge cases. A rule with known exceptions is better than no rule, it’s explicit about when the exception applies rather than letting every situation be a fresh decision.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
