Skip to main content

Why you can't have a ‘work self’ and a ‘home self’

There's a question that comes up in nearly every leadership workshop, every team development session, every coaching conversation about authenticity:

Should I be thinking about my professional values or my personal values?

It's an understandable question. We've been conditioned to believe in compartmentalization—that we can be one person at work and another at home, that we can hold one set of principles in the boardroom and a different set at the dinner table.

But here's what Brené Brown names so clearly in Dare to Lead: We have only one set of values.

Me and the other me

The idea that we might have separate value systems for different areas of our lives is appealing. It would make things so much easier, wouldn't it? We could be competitive at work but collaborative at home. We could prioritize results over relations in business but reverse that in our personal relationships.

Except that's not how integrity works. That's not how we work.

Our values aren't like clothes we change depending on the occasion. They're more like our DNA—the fundamental code that determines who we are, how we show up, and what we stand for, regardless of where we're standing.

Living our values

The challenge isn't choosing between professional and personal values. The challenge is living in alignment with our one set of values across every context—even when it's difficult, even when it costs us something, even when the people around us hold different values.

This is where the rubber meets the road:

  • That moment when your company asks you to compromise on something you believe in
  • When your friends pressure you to go along with something that doesn't sit right
  • When a family member expects you to prioritize loyalty over honesty
  • When a stranger's behavior at the line in the grocery store tests your commitment to respect and kindness

These moments of conflict aren't signs that we need different values for different settings. They're invitations to clarify what we truly value and to find the courage to honor those values even when it's uncomfortable.

The freedom in one set of values

Here's the good news: while having only one set of values is challenging, it's also deeply liberating.

When you stop trying to maintain multiple versions of yourself, you free up enormous energy. You no longer have to remember which version of yourself you're supposed to be in which context. You no longer have to manage the cognitive dissonance of behaving in ways that contradict your core beliefs.

You simply get to be you—fully, consistently, courageously.

Next time

So the next time you're faced with a values-based decision, don't ask yourself whether this is about your professional or personal values. Instead, ask:

  • What do I actually value most?
  • Am I honoring those values in this moment?
  • If there's misalignment, what needs to change—my behavior or my situation?

Your values aren't situational. They're not negotiable based on context. They're the throughline of your life, the non-negotiables that define who you are when no one's watching and when everyone is.

The work isn't to have different values for different parts of your life. The work is to identify your true values and then find the courage to live them—everywhere, with everyone, all the time.

Merry Christmas!

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more