Invariants and Values

In engineering, an invariant is a condition that must always be true. It's something you can depend on, no matter what else changes.

In life and work, your invariants are the core principles that define who you are. They're non-negotiable. They don't change based on circumstances, convenience, or pressure.

Your invariants are your identity.

What Are Invariants?

Invariants are the boundaries you won't cross. The principles you won't compromise. The truths that remain constant while everything else flexes.

They're different from goals or preferences:

• Goals change as you achieve them
• Preferences shift with context
• Invariants remain constant

Examples of personal invariants:

• "I don't lie to customers"
• "I treat people with respect, even when disagreeing"
• "I take ownership of my mistakes"
• "I prioritize long-term relationships over short-term wins"
• "I don't compromise on quality for expediency"

Examples of organizational invariants:

• "We ship working software"
• "We protect user data"
• "We communicate transparently"
• "We make decisions based on data, not politics"
• "We value craftsmanship"

Why Invariants Matter

Without invariants, you're reactive:

• Every decision becomes a negotiation
• You're pulled by the loudest voice or strongest pressure
• Identity becomes fuzzy and inconsistent
• Trust erodes because people don't know what you stand for

With clear invariants, you're grounded:

• Decisions become simpler—does this violate an invariant?
• You move faster because the boundaries are clear
• People know what to expect from you
• Trust builds because you're consistent

Invariants give you the foundation to be flexible everywhere else. When you know what won't change, you can adapt everything that can.

Values vs. Invariants

People often confuse values with invariants. They're related but different:

Values are ideals you aspire to:

• "We value innovation"
• "We value teamwork"
• "We value customer satisfaction"

Values are important, but they're often vague. What does "innovation" actually mean in practice? How do you trade it off against stability? Values give direction but not boundaries.

Invariants are concrete lines you won't cross:

• "We don't ship features without tests"
• "We don't make promises we can't keep"
• "We don't blame individuals for system failures"

Invariants are specific, actionable, and enforceable. You know immediately when one is violated.

The relationship: Values inspire. Invariants protect. Values point you toward what's good. Invariants keep you from what's bad.

You need both. But invariants are what actually shape behavior day-to-day.

Choosing Your Invariants

Start with integrity:

What are the things you'd be ashamed to compromise?

• Honesty in critical moments?
• How you treat people when no one's watching?
• Quality of work you put your name on?
• Promises you make to others?

Consider your non-negotiables:

What would make you quit or walk away?

• Practices you refuse to participate in?
• Environments you won't tolerate?
• Behaviors you won't accept from yourself or others?

Test them:

Are they actually invariant, or just strong preferences?

• Would you hold this line under pressure?
• Would you hold it even if it cost you something?
• Would you hold it even when inconvenient?

If it's truly an invariant, the answer is yes.

Examples of Invariants in Practice

Personal:

• "I don't ghost people—if I'm not interested, I say so clearly"
• "I apologize when I'm wrong, even if it's uncomfortable"
• "I don't talk badly about people behind their backs"
• "I show up when I commit to showing up"

Professional:

• "I don't release code I wouldn't want to maintain"
• "I give credit where it's due"
• "I speak up when I see something unsafe or unethical"
• "I don't sacrifice team health for short-term results"

Organizational:

• "We don't cut corners on security"
• "We don't ship dark patterns that trick users"
• "We don't punish people for bringing bad news"
• "We don't make commitments without understanding feasibility"

Living Your Invariants

Make them explicit:

Write them down. Share them with your team. Make sure everyone knows what lines you won't cross.

When invariants are implicit, they're easy to forget under pressure. When they're explicit, they're harder to violate.

Enforce them consistently:

If something is truly invariant, you hold the line. Every time. No exceptions for convenience, pressure, or expediency.

The moment you make an exception "just this once," it's no longer an invariant. It's a preference.

Use them to simplify decisions:

When facing a hard choice, check your invariants first:

• Does this violate any invariant? → Don't do it.
• Does this uphold my invariants? → Consider it.

Invariants remove entire classes of options from consideration, making decisions faster and clearer.

When Invariants Conflict

Sometimes invariants can appear to conflict:

• "Be honest" vs. "Be kind"
• "Move fast" vs. "Do quality work"
• "Respect autonomy" vs. "Maintain standards"

When this happens, you need to clarify:

• Are these truly invariants, or is one a preference?
• Can you redefine them to be compatible?
• Is one more fundamental than the other?

True invariants rarely conflict when properly defined. Usually, the conflict reveals fuzzy thinking about what's actually invariant.

Invariants Aren't Rigid

Having invariants doesn't mean being inflexible. It means being consistently flexible within clear boundaries.

You can:

• Experiment with new approaches
• Adapt to changing circumstances
• Try different solutions
• Iterate and improve

As long as you stay within your invariants.

Think of invariants like the banks of a river. The river flows freely, adapts to obstacles, changes course over time—but it stays within the banks. The banks don't restrict the river; they define it.

The Questions to Always Ask

"What are my invariants?" "Am I living them consistently?" "Does this decision violate any invariant?" "What would I never compromise?"

If you can't name your invariants, you're at risk of drifting. If you can name them but don't live them, they're not actually invariant.

Your goal isn't to have perfect invariants. It's to have clear invariants and to honor them even when it's hard.

---

Once you know your invariants, everything else becomes easier. You know who you are and what you stand for—and that clarity guides everything else.

---

Christian Blank
San Francisco · Updated May 2026
christian@blank.dev | www.blank.dev
Co-written and formatted with AI