Set the Columns You Live By: How Smart Constraints Turn Chaos Into Choice

Apr 15, 2026

9 min read

3 views

65%

Why a single cell reference can teach you more about freedom than a philosophy book

Have you ever stared at a blank spreadsheet and felt both power and panic: the power to make anything, the panic of not knowing where to begin? Now imagine someone asked you, out of nowhere, a life ending question: would you have chosen to be born? The two moments are strange mirrors. In both you face a vast space of possibility and the dizzying realization that choice without structure can feel like paralysis, or worse, an affront so raw it elicits a single syllable of profanity: fuck.

This article argues that real freedom is not the absence of constraints. Instead, freedom is the capacity to choose within structures that make choice meaningful. We will explore how the art of crafting rules for a spreadsheet offers a surprisingly precise model for designing a life, building organizations, and engineering better habits. By the end you will have a practical framework for setting the right constraints, testing them, and using them to magnify agency rather than diminish it.

The tension at the center: choice versus structure

The everyday experience of freedom contains a paradox. When options are unlimited, we feel both liberated and overwhelmed. When constraints are rigid, we feel safe but boxed in. The tension is not between freedom and constraint. The tension is between arbitrary constraint and intentional constraint.

Arbitrary constraint is a rule imposed without regard for the shape of the problem. It is a list typed into a cell because you can, not a selection based on patterns. Intentional constraint is a rule designed to highlight the important differences and hide the irrelevant noise. In spreadsheet terms, arbitrary constraint is manually typing every cell format for each case. Intentional constraint is choosing the row, locking the column, unlocking the row where it matters, and letting the rule do the work for you.

Think about absolute and relative references in a formula. Lock the column. Leave the row flexible. That small decision transfers a single rule across a whole dataset with predictable behavior. Now translate that move into how you set boundaries with people, design a schedule, or create policies. Lock the values you cannot or will not change. Leave the variables you expect to adapt. The result is a system that scales and stays readable, instead of a tangled mess of exceptions.

A visceral reaction to existential choice captures the same moment. Facing the question of whether one would choose existence prompts a raw emotional response, because the stakes are not hypothetical. It is not just about picking from a menu. It is a confrontation with the conditions that make any choice meaningful in the first place. When people flinch with expletives, they reveal that meaning is produced by the structure around choices, not by choice alone.

From spreadsheets to lives: the mechanics of useful constraints

Let us build a vocabulary that will let you apply this idea to real problems. I will use spreadsheet metaphors, but the terms are meant to be portable.

Locking versus unlocking: This maps to what you declare immutable and what you allow to evolve. Locking a column in a spreadsheet sets an invariant. Locking a principle in your life creates a predictable frame. Unlocking a row corresponds to tactical adaptability.
Rule based selection versus manual enumeration: Selecting a row region and applying a conditional format is a rule based approach. Typing a list element by element is manual enumeration. The first scales. The second does not.
Context aware rules: In spreadsheets you often refer to the cell in relation to others. The equivalent in life is making rules that depend on context, not absolute thresholds. A schedule that adjusts for travel days is context aware. A schedule that insists on the exact same hour every single day is context blind.
Default behavior and exception handling: A good rule creates sensible defaults and then specifies how to handle exceptions. Conditional formatting often highlights anomalies so you can focus on them. A good policy does the same: set the expected behavior, and then design focused mechanisms for exceptions.
Testability and rollback: In spreadsheets you try a conditional rule on a subset of rows, then expand it. In life you pilot a new constraint for a week, then scale if it works. The capacity to test and roll back is a core part of resilient design.

Concrete analogy: imagine you want to stop losing time to email. An arbitrary constraint would be to force zero inbox by 9 am every day. An intelligent, spreadsheet like constraint would be: lock the column labeled "responses that require decisions"; unlock the row labeled "low priority newsletters"; apply a rule that filters messages older than 48 hours into an archive and flags anything from a chosen list of people. The rule reduces cognitive load while preserving meaningful choices. It is not about removing choice. It is about ensuring the choices you make are the ones that matter.

Another example: hiring in a small company. Manual enumeration is interviewing anyone who looks interesting. A rule based selection approach would be to lock the required competencies that matter to the role, leave the cultural fit dimension adjustable, and build a small test that reveals competence. That structure speeds hiring and prevents bias from creeping in as ad hoc exceptions.

Constraints are not walls. They are templates for action. When chosen well, they convert a sea of options into a map with clear trails.

Framework: Designing constraints that expand freedom

Here is a practical framework to design constraints that do what you actually want them to do. Think of it as the conditional formatting rule for your life.

Step 1: Identify the invariant

Decide what you are trying to preserve across situations. This is the column you will lock. In life this might be core values, non negotiable goals, or essential relationships. Be sparing. The fewer invariants you lock, the more flexible the system becomes. Locking too many things is like freezing every column in a spreadsheet. Nothing moves, and the dataset becomes unreadable.

Example: If you care about health, lock sleep and exercise as non negotiables. Let diet be flexible within a range. You now have a framework that guides daily decisions without micromanaging every meal.

Step 2: Define the pattern, not the list

Instead of producing exhaustive rules, craft patterns that can be applied to many situations. In spreadsheets this is the difference between typing a whole list of values and writing a formula that recognizes a pattern. Patterns scale.

Example: Rather than making a rule for every person you might meet about how to respond to requests, make a pattern rule: prioritize requests that have a clear outcome within two weeks, require a 15 minute decision ritual for anything else. This pattern handles many cases without need for rules for every single person.

Step 3: Build defaults and exception paths

For each rule define the default behavior and then the minimal path for exceptions. Use flags to highlight exceptions. This frees up attention for the rare but important deviations.

Example: The default might be that meeting requests without an agenda are declined. Exception path: if the requester is a mentor or the meeting originates from someone you are actively helping, accept with a request for a 10 minute agenda.

Step 4: Pilot, measure, iterate

Try the rule on a small sample, see how it behaves, and adjust. In spreadsheets you never finalize a rule without testing it on a sample. Do the same with life constraints.

Example: Try a 30 day experiment where you only accept meetings with agendas. Measure how many meaningful partnerships progressed. Adjust the rule if you find bottlenecks.

Step 5: Make the structure visible

Conditional formatting draws attention to the important cells. Make your constraints explicit so others and your future self can see them. Visibility reduces accidental violation and creates a shared reality.

Example: Post your work hours in your email signature or calendar. That way colleagues know the constraint and can self select to match it.

When constraints go wrong and how to rescue them

Not all constraints produce freedom. Some make life brittle. Here are the common failure modes and how to rescue a system.

Failure mode 1: Over locking

Problem: You declare too many invariants. The system becomes rigid and cannot respond to new evidence. It feels like a rule book written for a different season.

Rescue: Audit your invariants quarterly. Ask whether each locked column remains essential. Unfreeze what no longer serves.

Failure mode 2: Over engineering

Problem: You build a thousand micro rules that try to anticipate every exception. The cognitive load of following the rules becomes higher than solving the problem.

Rescue: Return to patterns. Replace clusters of micro rules with a single pattern that captures their essence.

Failure mode 3: Invisible defaults

Problem: People do not know your rules. Without visibility, default behavior fills the vacuum and often it is the opposite of what you intended.

Rescue: Make the rule explicit. Post it. Automate it if possible.

Failure mode 4: No rollback plan

Problem: You commit to a constraint as if it were forever. When it fails you double down out of pride.

Rescue: Build testability into every rule. If a constraint cannot be piloted and rolled back, it is too costly to implement.

A small rescue example: If your rule about no email after 7 pm causes clients to panic, pilot a change where you auto send a note acknowledging receipt and promising a next morning reply. You keep the boundary while managing expectations.

Key Takeaways

Lock the minimal set of invariants that preserve identity and direction. Treat these like fixed columns in a sheet: hold them steady, but only the ones you truly need.
Prefer pattern based rules to long lists. Patterns are formulas that scale; lists are manual edits that break as the dataset grows.
Design defaults for typical cases and small, clear exception paths for unusual cases. Use visible flags to highlight exceptions so attention is focused where it matters.
Pilot new constraints on a small sample, measure the outcome, then iterate or roll back. Testability is a constraint that pays for itself.
Make your constraints visible. A rule that no one knows about will not produce the desired behavior.

A closing thought: the ethics of designing our own formats

When faced with the deepest questions about whether existence would be chosen, the magnitude of the question can feel unbearable. That raw reaction is not a failure of thinking. It is a signal: the question is asking you to reckon with the structure that makes preference possible.

That is the lesson of the spreadsheet. The magic is not in infinite choice. The magic is in a few well chosen rules that render a confusing landscape legible. Choose the columns you live by. Let some rows remain fluid. Build patterns that scale. Pilot your rules and make them visible.

If you do this you will discover something counterintuitive: constraints, when chosen intentionally, multiply possibilities. They do not reduce freedom. They give freedom a shape that the human mind can carry.

Remember, the next time you feel overwhelmed by the blankness of possibility, you do not have to type every answer. Select the row, lock the meaningful column, and write one rule that lets the rest take care of itself. It may not answer whether you would choose to be born. It will, however, give you the tools to make the most honest, focused, and humane choices in the life you have.