How personal principles reduce decision fatigue (and where they don’t)

Decision fatigue is not a character flaw that shows up on a bad day. It is what happens after a run of decisions have all gone through the same slow process — weigh the options, imagine the outcomes, pick, live with a little doubt about it — one after another, with no discount for the tenth time you have solved a version of the same problem. A personal principle helps with a specific slice of that load: the decisions that keep recurring in roughly the same shape. It does this by moving the actual deciding to a calmer moment, once, and leaving only the applying for the tired version of you later. It does not touch the decisions that are genuinely new each time, and pretending otherwise is where the idea gets oversold.

What is actually being spent

The tiring part of a decision is rarely the choosing itself. It is the run-up: noticing there is a decision to make, retrieving what you believe about it, weighing that against whatever pressure is present in the moment, and then living with having chosen under some uncertainty. Do that dozens of times in a day — what to answer a colleague, whether to say yes to a favor, whether tonight is the night you finally have the hard conversation — and the fatigue is not really about any single one of those. It is about paying the full setup cost every single time, for questions that, if you are honest, keep landing in nearly the same shape.

This is different from being tired in general. You can be well-rested and still run out of a very specific kind of patience by 4pm, because the thing that depletes is not energy in the abstract, it is the willingness to keep re-deriving an answer you have effectively already worked out before, several times, under slightly different disguises.

What a principle actually removes

A principle does not remove the decision. It removes the re-deriving. "I do not take on work I would resent doing" is the output of a decision you already made, probably after getting burned by saying yes to the wrong thing more than once. The next time an ambiguous request shows up, you are not starting from zero — you are checking a single stored answer against the specifics of this one case, which is a much smaller task than working out from first principles, again, what you think about obligation and resentment and money and being liked.

That is the actual mechanism, and it is worth being precise about it: a principle written down and genuinely believed converts a class of decisions from live to settled. A live decision still has to be argued with yourself in real time. A settled one only has to be applied, and applying is cheap compared to arguing.

Why this only works for decisions with real repeats

The saving only exists if the situation actually recurs in a similar enough shape that one rule can cover it. "Should I take this specific job" is not a repeating decision — it happens a handful of times in a life, and every instance has enough unique detail that a stored answer would be actively misleading. "Should I say yes to a request I already resent before I have even started" repeats constantly, in dozens of different costumes, which is exactly the shape a principle is built to catch.

Where the same idea makes fatigue worse, not better

This is the part that gets left out when the idea is presented as a pure hack, and it is the honest reason to be careful with it.

Too many principles is its own tax

A stored rule is only cheap to apply if you can actually recall it in the moment without effort. Past somewhere around five to eight, most people cannot hold the list in mind under real pressure, and now checking "which of my principles applies here" has become a new decision layered on top of the old one — which defeats the entire point.

A vague principle does not settle anything

"Be a good colleague" gives you nothing to check a request against, so the moment still has to be worked out from scratch, except now it also carries the mild guilt of having a principle that failed to help. A principle only offloads work if it is specific enough to actually rule some options out. If it can agree with almost any choice, it was never doing the job, it was just decoration.

Applying a principle to a genuinely new situation is not free either

The saving is real for the ordinary, recognizable instance of a recurring pattern. It shrinks toward nothing for the edge case that does not quite match — and forcing an edge case through a rule that was not built for it, out of a wish to avoid deciding again, is how principles start producing answers that are fast but wrong. Fast and wrong is not a win over slow and right; it just moves the cost to later, usually with interest.

How to actually get the offloading effect

Write the principle at a moment when you are not deciding under pressure — after a bad week, on a slow Sunday, anywhere but in the middle of the situation it is meant to cover. That single sequencing choice is most of the benefit: you are doing the effortful weighing exactly once, in cold blood, instead of once per occurrence in whatever state you happen to be in when it shows up. Then keep the list short enough to actually recall — most people do better with five to eight principles they can name without checking than with fifteen that require looking something up, which reintroduces the exact deciding you were trying to skip. And write each one specific enough to rule something out; if you cannot think of a real situation where it would tell you no, it is not offloading anything yet.

What this does not replace

A principle is a shortcut for a decision you have already made, not a way to stop deciding new things. The genuinely novel situation — the one that does not resemble anything you have already worked out — still needs the full, slow, tiring process, and that is fine, because it is a small minority of the decisions in an average week. The point of offloading the recurring ninety percent is to have the patience left for the ten percent that actually deserves it, not to reach for a rule so it does not have to be thought about at all.

This is close to what a creed inside CreedOS is doing structurally: a principle you wrote once, with two or three behavior standards underneath it that turn "what should I do here" into "did I do the thing I already decided," checked in under a minute rather than re-argued. It is free, with no in-app purchases.