Skip to main content

Six words that define your leadership

I was listening to the Coaching for Leaders podcast recently, and Scott Keller shared something that stopped me mid-stride: the six-word story exercise.

His example was the famous Ernest Hemingway line (though its true authorship is debated): "For sale: baby shoes. Never worn."

Six words. An entire world of heartbreak, hope deferred, a nursery that stayed empty. I must have read that sentence three times, feeling the weight of everything left unsaid.

And then Keller posed the challenge: What's your six-word leadership story?

I sat with my notebook open. Pen ready. And... nothing.

The power of constraint

There's something almost unfair about this exercise. Six words feels impossibly small. I've written mission statements, vision documents, strategic plans that span pages. I've crafted carefully worded emails, given presentations with dozens of slides. Six words?

But that's exactly the point.

When you have six words, you can't hide behind corporate speak. You can't use "synergy" or "leverage" or "stakeholder engagement." You can't qualify, hedge, or explain. You have to choose what matters most.

The constraint is the gift.

It forces you to ask: What is the essence of who I am as a leader? What story am I actually living, not the one I wish I was living? If someone had to understand my leadership in a single breath, what would they need to know?

Why this matters for leaders

We live in an age of information overload. Our teams sit through hours of meetings, wade through endless Teams messages, navigate competing priorities from every direction. As leaders, we contribute to this noise constantly—often without realizing it.

But clarity cuts through chaos.

When I think about the leaders who've shaped me most, they weren't the ones with the most detailed strategies or the longest speeches. They were the ones who could distill complex ideas into simple truths. Who knew what they stood for and could articulate it in a way that stuck.

Six words is an exercise in that kind of clarity.

It's also an exercise in honesty. Because your real six-word story isn't necessarily the one you want it to be. It's the one that's true right now. The one your team would write about you if you asked them. The gap between those two versions? That's where the growth happens.

My attempt (So far)

I've been trying to write mine for the past week. Here's what I've learned: it's harder than it looks.

My first attempts were too aspirational:

  • "Empowering others to reach their potential."
  • "Building teams that change the world."

They sounded nice. They weren't true. Not yet, anyway.

Then I tried being clever:

  • "Coffee first. Strategy second. People always."

Too cute. Too clever by half.

I'm currently sitting with something more honest:

  • "Still learning. Often failing. Always trying."

Is that it? I'm not sure. It feels closer. It feels true to where I am right now—leading imperfectly, figuring things out, committed to growth even when it's uncomfortable.

But I'm not ready to lock it in. And maybe that's okay. Maybe the value isn't in having the perfect six words. Maybe it's in the wrestling match to find them.

Your turn

I want to challenge you to write your six-word leadership story.

Not the one that would look good on a motivational poster. Not the one you'd put on your LinkedIn profile. The real one. The true one.

Sit with it. Try a few versions. Notice which ones feel aspirational and which ones feel accurate. Notice the gap.

Ask yourself:

  • What do I actually do, not what do I wish I did?
  • What would my team say about me?
  • What matters most in how I show up?
  • What story am I living right now?

If you're brave, share it with someone you trust. Ask them if it rings true. Their reaction will tell you everything.

And if you're really brave, share it with your team. Not as a proclamation, but as an invitation. "This is what I'm working toward. Hold me to it."

The unfinished story

I'm ending this post without my final answer, and that feels right. Because leadership isn't a destination—it's a practice. My six words today might not be my six words a year from now. Growth means the story changes.

But the exercise of distilling it down, of getting ruthlessly clear about who you are and who you want to become?

That stays with you.

For sale: baby shoes. Never worn.

Six words. A universe of meaning.

What's yours?

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         ...

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) ...

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,...