The Second Mouse Gets the Cheese

There’s an old saying that has been sitting with me lately.

The early bird gets the worm, but the second mouse gets the cheese.

It’s not the kind of line you put on a corporate development poster. It’s a little sharp. A little uncomfortable. Maybe even a little cynical at first.

But there’s wisdom in it.

We spend a lot of time celebrating the person who goes first. The first to raise their hand. The first to try the new process. The first to take on the messy assignment. There’s something admirable about that.

But going first comes with a cost. The first person usually finds the gaps. The unclear expectations. The missing hand-offs. The assumptions no one named out loud. The trap, so to speak.

The second mouse steps into a clearer path because someone else exposed what needed to be learned.

I’ve been a second mouse most of my career.

For thirty years in corporate America, the work I’ve been asked to do has rarely involved building from scratch. It’s almost always involved stepping into something that wasn’t quite working. Some teams were stuck. Some processes were broken. Some were functioning but not the way they needed to. In many cases, it wasn’t just the workflow that needed repair. It was the people doing the work who needed some too.

I’ve stopped pretending this is coincidence.

There’s a phrase I’ve started using with myself for the role I keep taking on: the fixer. Not in the dramatic, scrub-in-and-save-the-day sense. More like the person who shows up to a system already in motion, looks at what’s been creating friction, and tries to figure out how to make it move more cleanly without breaking what’s already working.

I’ve wondered for years why I keep being drawn to this work. The honest answer goes further back than my career.

When I was a boy, I was walking to school with a friend. His dad met us in the parking lot. It was the mid-1970s, and corporal punishment wasn’t questioned the way it is now. My friend had failed to walk his sister to school that morning, and his father strapped him to the wheel of the car and spanked him right there, in front of the building, in front of the children walking in.

I stood there. I didn’t do anything. I couldn’t. I was a small boy watching an adult discipline a child in a way I knew was wrong, in a place where no other adult intervened.

What I felt that day wasn’t shame, though I called it that for a long time. It was helplessness. The recognition, for the first time, that I cared about what I was seeing and could do nothing to change it.

My parents would have intervened. They set a high standard of care for other people, and they showed me what it looked like to act on it. What I learned in that parking lot wasn’t that adults stood by. I knew, from my own home, that they didn’t have to. What I learned was that I was not yet one of them.

That memory has never left me.

I don’t think it made me who I am. That would be too neat a story. But I do think it taught me something that most of my career has been an answer to: the gap between caring and being able to act is intolerable. And the only way to close that gap is to be in a position where I’m allowed to act when it matters.

So I keep stepping into systems that need fixing. Not because I love broken things, but because I’ve come to understand that fixing them, when it’s done right, isn’t really about the system. It’s about the people inside it.

My first chance to act on this in any real way came early in my management career.

I had just been promoted into my first people leader role. My new boss had taken a chance on me. She’d chosen me over a candidate that internal colleagues had been pushing for, and I knew I had something to prove. The team I was building was brand new. Young. Untested. I had no template for what a manager was supposed to look like, and I didn’t particularly want one.

I’d describe myself, in those years, as an unconventional leader.

I would bring the team down to the green space at the front of the office for lunch. We played games. We de-stressed at the end of hard weeks. I ran a round-robin tournament of a volleyball-styled sport during lunch breaks. Other teams would walk by and ask us to quiet down. We were apparently having too much fun.

We also set the standard for metrics. Most calls handled. Best turn time. Highest customer satisfaction. The team I was building wasn’t being unserious. They were rowing the boat together in the same direction because they saw each other as more than work colleagues.

It was during those years that I lost my father.

And it was during those years that one of my team members lost his.

I sat with him. I told him what I was going through. He told me, years later, how much that conversation had meant. How it had helped him carry the grief in a way he hadn’t been able to before. Some of the people from that team are managers themselves now, and I still get messages from them about how that period of their early careers shaped who they became.

I sometimes wonder whether the manager I am now would have hired the manager I was then.

I don’t know the answer. I’ve changed. The expectations of leadership have changed. But what I know is that what I was doing without a name for it was stewardship. I just didn’t have the language yet.

Peter Block writes that stewardship is being accountable for the well-being of the larger organization by operating in service rather than control. That’s the cleanest articulation of it I’ve found. But the way I’ve come to live it is simpler.

Stewardship is careful, responsible management of something entrusted to me, rather than possessed by me.

In every team, every project, every role I’ve been handed over thirty years, that’s the orientation I’ve tried to hold. Not always perfectly. But it’s the north star I keep returning to. The work, the metrics, the deliverables: those matter. But what matters more is the long-term health of the people doing the work. Their dignity. Their autonomy. Their capability after I’m gone.

For the most part, I will own the mistakes of the people in my care while coaching them to grow past those mistakes. The exceptions are when someone makes an unethical decision. That’s theirs to carry. But the day-to-day errors of people trying to do their best? Those are mine to absorb. That’s the deal I’ve always made with the teams I’ve led.

Which brings me to this year.

Earlier this year, I was asked to take over a role inside our operation that wasn’t quite working. The process wasn’t broken exactly. People were doing the work, progress was being made, the role had a purpose. But it had been built for a different time, and the way the organization had evolved had outpaced what the role was equipped to handle.

So I did what I’ve done many times before. I stepped in. I listened. I worked with the people doing the work. Not around them, not above them, but with them. We made changes that were uncomfortable before they became useful. Friction before flow.

Over time, the role started functioning the way it needed to. The conversations got clearer. The hand-offs improved. The teams collaborated more effectively. It became something I was proud of.

Then my boss floated the idea of handing it off to someone else.

And I was disappointed.

That disappointment is what made me write this.

Because the moment I felt it, I recognized something in myself I should have caught sooner: I had stopped holding the work as a steward and started holding it as an owner. The whole philosophy I’d built a career around — entrusted to me, not possessed by me — and I’d quietly drifted from one to the other without noticing.

That’s the part stewardship doesn’t tell you about. The slip is silent. You don’t wake up one morning and decide to start gripping something. You just start caring about it, and the care builds, and somewhere along the way the caring tips into ownership, and you don’t notice until someone tries to take it from you.

In corporate life, we attach our value to what we own. My role. My process. My dashboard. My improvements. My way of doing things. The pronouns are seductive.

But real impact isn’t always measured by how tightly we hold something. Sometimes it’s measured by what becomes possible after we let it go.

If something only works because I’m personally holding it together, then I’ve created dependency. If something can be handed off, sustained, and improved by someone else, then I’ve helped create capability.

That’s a different kind of reward. And it’s the only one that actually proves I was doing the work as a steward.

The handoff is still difficult. I don’t want to pretend otherwise. Pride and loss can sit at the same table.

But pride and loss aren’t the same thing as ownership and grief. Pride is allowed to stay. Ownership is what I need to let go of.

So I’m letting go.

The work will be carried forward by someone else. They’ll find things I missed. They’ll bring perspectives I didn’t have. They’ll improve what I built, the same way I improved what was there before I arrived.

That’s the second mouse. Always was.

And maybe that’s the real lesson behind the saying.

Sometimes you’re asked to go first. Sometimes you’re asked to learn from the person who did. And sometimes you’re asked to build something strong enough that the next person can step in and make it better still.

That last one might be the hardest.

It might also be the clearest evidence that you held the work the way it was supposed to be held.

Not as yours.

As theirs, in your care, for a while.