Plenty of values hierarchies look impressive on paper and fail completely in practice. The gap between a hierarchy that exists as an exercise and one that actually works — that genuinely changes how you decide day to day — comes down to a set of practical failure points that most people never address. This piece is specifically about making a hierarchy operational: not how to construct its logical structure, but how to ensure the structure you built actually functions in the messy reality of your life rather than sitting in a notebook while you keep deciding the way you always have.
Make It Specific Enough to Discriminate Between Options
The first reason hierarchies fail in practice is vagueness: values stated so broadly that they cannot actually distinguish between the options you face. A working hierarchy must be specific enough to discriminate.
A hierarchy only works if its values are defined specifically enough to favour one real option over another, because vague values like "growth" or "happiness" endorse almost any choice and therefore guide none of them. The test of a usable value is whether it can ever rule an option out — a value that approves of everything is decoratively present but operationally useless. If "growth" sits atop your hierarchy but you have not defined what growth means for you, then nearly any option can be framed as growth, and the value discriminates nothing. To make it work, define it concretely: growth as expanding specific capabilities, or as increasing responsibility, or as deepening mastery in a particular domain. Now the value can actually distinguish — this option offers real growth in the defined sense, that one only appears to. Go through each value in your hierarchy and ask whether it is specific enough that you could point to a real option it would reject. If not, sharpen it until it can discriminate. A working hierarchy is built from values precise enough to actually choose between the options your life presents, not abstractions that bless whatever you were already inclined to do.
Connect the Hierarchy to Actual Decision Triggers
A hierarchy fails in practice when it lives in a separate mental compartment from your actual decisions, consulted in reflective moments but forgotten when choices actually arrive. Making it work requires connecting it to the moments where decisions happen.
For a hierarchy to function, you must build the habit of consulting it at the moment of decision, because a hierarchy that is never invoked when a choice arises has no effect on your choices regardless of how well it is constructed. The hierarchy does its work only at the point of decision, so the operational challenge is bridging the gap between having a hierarchy and remembering to use it when it counts. Identify your recurring decision triggers — the kinds of choices where the hierarchy should be applied — and build cues that bring it to mind in those moments. This might mean a literal pause-and-check habit when you notice a values conflict, a written copy of the hierarchy where you make significant decisions, or a deliberate practice of asking which ranked value a decision implicates before choosing. The mechanism matters less than the outcome: the hierarchy must actually fire at the moment of choice. Without this connection, you have a hierarchy you admire and a decision-making process that ignores it — which is no better than having no hierarchy at all. Making it work means closing the gap between possession and application.
Keep It Short Enough to Hold in Mind
A practical hierarchy must be short enough that you can actually hold it in your head, because a hierarchy too long to remember cannot be applied in the moment when memory is all you have.
A working hierarchy is short enough to recall instantly, because in real decision moments you rarely have the chance to consult a long written list, so an unmemorable hierarchy fails exactly when you need it. The constraint of memory forces useful prioritising — a hierarchy of five clear values you can hold in mind beats one of fifteen you cannot. If your hierarchy contains a dozen finely distinguished values, you will not be able to bring the whole structure to bear in the moment a decision arrives. The solution is ruthless consolidation: identify the small number of values that actually drive most of your important decisions — usually somewhere between three and six — and build your working hierarchy around those. Lesser values can still inform decisions, but the core ranked structure you carry in your head should be short enough to recall instantly and apply on the spot. This is not a loss of nuance but a gain in usability, because a hierarchy that lives in your memory and fires in the moment accomplishes infinitely more than an elaborate one that stays in a drawer. Make the core hierarchy memorable, and it becomes a genuine working tool rather than an admired artifact.
Build In a Way to Override When Reality Demands It
A hierarchy that works in real life includes a principled way to override itself in genuinely exceptional circumstances, because rigid application of any ranking will occasionally produce a clearly wrong result.
A working hierarchy includes a deliberate override mechanism for rare exceptional situations, because mechanically applying any fixed ranking will sometimes produce a result that is clearly wrong, and refusing to allow for that makes the hierarchy brittle. The discipline is to permit overrides only as rare, conscious exceptions you can justify — not as routine escape hatches that would quietly dissolve the hierarchy altogether. Occasionally a situation will arise where following your hierarchy strictly leads somewhere you can see is genuinely mistaken — an emergency, an unusual circumstance the hierarchy was not built to handle. A brittle hierarchy that admits no exceptions will either be followed into error or abandoned entirely the first time it fails. A working hierarchy instead permits deliberate, justified overrides: rare moments where you consciously decide that this particular situation warrants departing from the usual ranking, with a clear reason you could defend. The key is that overrides remain genuinely exceptional and consciously reasoned, never a routine convenience for avoiding a hard choice. This controlled flexibility is what lets the hierarchy function reliably across the unpredictable variety of real life, holding firm in the ordinary case while bending in the rare case that genuinely requires it.
Review Whether It Is Actually Changing Your Decisions
The ultimate test of whether your hierarchy works is whether it is actually changing your decisions, and a practical hierarchy includes periodic honest review of this question.
Regularly check whether your hierarchy is actually altering decisions you would otherwise have made differently, because a hierarchy that never changes any decision is not working, no matter how good it looks. The proof of a functioning hierarchy is evidence that it has redirected real choices — if you cannot point to such a case, the hierarchy is decorative rather than operational. Periodically examine your recent significant decisions and ask whether the hierarchy genuinely influenced them, or whether you decided as you would have anyway and merely invoked the hierarchy afterward to justify the choice. A working hierarchy will sometimes lead you to decisions you would not otherwise have made — choosing the option that serves your highest-ranked value over the one you were instinctively drawn to. If you cannot find any such cases, your hierarchy is not actually operating; it is being used as a post-hoc rationalisation rather than a genuine decision tool. This review keeps the hierarchy honest and functional, ensuring it remains a real instrument that shapes your choices rather than a comfortable story you tell yourself about values you are not actually deciding by.
From Artifact to Instrument
Building a values hierarchy that actually works for your life means addressing the practical failure points that separate a functioning instrument from an admired artifact: making the values specific enough to discriminate between real options, connecting the hierarchy to your actual decision triggers, keeping it short enough to hold in mind, building in a principled override for genuinely exceptional cases, and reviewing whether it is truly changing your decisions. A hierarchy that passes these tests does what a hierarchy is supposed to do — it shows up at the moment of choice, distinguishes between your real options, and reliably redirects you toward what you most value. The difference between a hierarchy that works and one that does not is rarely the quality of its logical structure; it is whether you made it operational. Do that work, and your hierarchy stops being something you have and becomes something you actually decide by.
