That line stayed with me, and it keeps turning into a question I want to put to you: What would you do differently if you didn't mind what happens?

Where the energy goes

Most of us spend a surprising amount of energy fighting things that have already happened. The reorg that just got announced. The meeting that went sideways. The feedback we didn't see coming. We argue with it in the car, replay it at night, and rehearse what we should have said. The fight feels like engagement, but it's mostly resistance, and resistance is expensive.

When you stop fighting what's already here, that energy comes back to you. You can spend it on seeing the situation clearly and responding to what's actually in front of you, instead of what you wish were there.

Not minding isn't not caring

This idea is easy to misread. Not minding what happens is not indifference, and it's not giving up. You can care deeply about an outcome and still not mind what happens. Caring is about what you put in. Minding is about how tightly you grip what comes back. Leaders who don't mind still hold high standards, still push for what matters, and still feel disappointment. They just don't spend the first hour of every setback insisting it shouldn't have happened.

The learner's advantage

Language teachers know this one well. The learners who become fluent fastest are rarely the ones who never make mistakes. They're the ones who don't mind making them. Fear of sounding wrong makes people speak less, risk less, and learn more slowly. The learners who let mistakes happen get more practice, more feedback, and more fluency.

Leadership works the same way. When you mind every awkward silence, every pushback, and every plan that doesn't land, you hold back. When you don't mind, you're free to listen instead of defend, to ask the real question, and to make the call without needing a guaranteed result. People around you feel that steadiness, and they often borrow it.

Try this week: Pick one thing you're currently fighting: a decision you disagree with, a conversation you're dreading, or a result that let you down. Ask yourself, "If I didn't mind that this happened, what would I do next?" Then do that.

That predictability doesn't come from personality. It comes from principles.

Write down how you want to show up

One of the most useful things you can do as a leader is to name a few principles for how you want to show up: the kind of presence you want people to experience when they work with you. Not values on a poster, but short, personal commitments. For example:

• I listen to all opinions, even the ones that make me uncomfortable.
• I focus on the problem, not the person.
• I make everyone feel valued, no matter how "important" their role is on the project.

You won't have them all on day one

Your principles take shape as you lead. Some will come from moments you're proud of, others from moments you'd rather forget. Keep the list open. Add to it, edit it, and let go of the ones that don't ring true anymore. Keep the ones that resonate most.

Say them out loud

Here's the part people skip. Read your principles regularly, out loud, to yourself. Anyone who has learned a second language knows that fluency doesn't come from understanding a phrase once. It comes from repetition until the words become yours. Principles work the same way. The more you revisit them, the more your mind starts operating from them without effort, especially in the moments that test you.

Principles build gravity

Over time, these principles quietly shape how you lead and how others perceive you. And they have a powerful side effect: they create gravity.

People who share those principles are drawn toward you. They want to belong to your team and to the vision you're building. Those who don't connect with that way of working tend to drift away on their own. No confrontation, no forcing. Just a natural sorting.

That's what makes it easier to build a team around your vision. You're not convincing people one by one. You're showing up consistently, and letting the right people find their way in.

Try this week: Write down three principles for how you want to show up. Read them aloud each morning for seven days, and notice which ones you actually lived.

I noticed the same pattern again and again. First came a quiet phase, where people understood more than they could say. Then came translation, where every sentence was built in their first language and converted, slowly and effortfully, into the new one. Somewhere in there came a painful feeling many of them named out loud: "I feel less intelligent in English."

They weren't less intelligent. They were mid-acquisition.

Years later, I became a leadership coach, working mostly with people who had been promoted because they were excellent at something else. Skilled clinicians, sharp specialists, the person everyone went to for answers. And I kept hearing a familiar sentence in a new form: "I don't feel good at this."

That's when it clicked. These new leaders weren't failing. They were translating. They were taking situations like a tense conversation, a struggling team member, or a decision with no clear answer, and running them through their first language, the language of expertise, where there's usually a right answer and you're the one who knows it. Leadership doesn't work that way. It has its own grammar, one of questions, trust, ambiguity, and influence over control.

Here's what language learning taught me that I wish every new leader knew: the awkwardness is not evidence that you don't belong. It's evidence that you're learning. Fluency doesn't arrive through information alone. It comes through immersion, practice, mistakes, and eventually a day when you realize you stopped translating.

That's what this space is about. Leadership as a second language: how capable people learn to lead, and more quietly, how they become someone new along the way. Some posts will be short notes like this one. Some will be longer pieces about how our workplaces and institutions help or get in the way. Eventually there'll be conversations with people who have made the shift themselves.

If you're somewhere in the middle of that shift right now, still translating, I'd love to hear from you. What's your "first language," and what's been hardest to leave behind?

— Saeed