For years, across different roles and different managers, I kept getting the same note. Not the same words every time, but close enough that I started to hear it before it was said.

"You're a perfectionist. You're intense. You'd go further if you loosened up a little."

I remember sitting with that last one the longest. Loosen up. It was stated as if the thing that was responsible for the stellar work I produced, the thing I was actually being paid for, was also the thing standing between me and being liked. 

Nobody ever told me to loosen up on the deliverables. It was just on myself and that distinction mattered a lot.

In this episode, I tell the story of how I learned that what I was receiving wasn't really feedback at all. It was a personality judgment presented as performance feedback. 

This is the pattern that shows up again and again for women in leadership: the qualities that help men look decisive and strong often get women labelled as difficult, abrasive, intense, or too much. The same behaviour that gets men promoted gets women told to soften, be more agreeable, and be easier to like.

The real problem is that leaders are using language that confuses a person's traits with a performance issue. Once you have the language for it, you can see it everywhere.

In this episode, I talk about:

• Why the feedback wasn't about my work
• The competence-likability bias and the social cost of being both capable and warm
• The difference between a trait and a behaviour, and why that distinction matters
• The five-part test I now use before I give or receive feedback
• The practical rewrite process that turns vague judgments into actionable guidance

I also walk through the research that makes this pattern impossible to dismiss. 

The most important distinction here is this: a trait is a label. A behaviour is something someone can actually do differently. A person can learn to change a behaviour. They cannot develop themselves out of the personality category someone else has assigned to them.

This is why I got serious about a new standard for feedback, which I share in this episode.

This week's permission: You are allowed to reject the version of feedback that asks you to shrink yourself to be easier to manage. Being effective is not the same thing as being easy. Being clear is not the same thing as being difficult. And the part of you that makes your work land is not a flaw to be corrected.

Somewhere in your business is a hundred-hour puzzle you built and are proud of. And you're the only one who's allowed to touch it because you're good at it and you keep telling yourself no one could complete it quite the way that you do. 

In this episode, I share the years I spent running a college registrar's office, building the entire class schedule myself, three times a year, close to a hundred hours a shot, convinced I was some kind of unicorn nobody else could replace. Then I tell you about the event that changed how I saw all of it. It's the choice I still carry.

This episode names the pattern clearly: what looks like competence is often just control wearing a more palatable outfit. The women who hold on longest to work they should hand off are typically the most capable people in the room, which is exactly what makes "nobody else can do this like I can" so easy to believe, even when you're the one saying it to yourself.

I also bring in my client Nicki, who ran her own version of this for eight years, sixteen hours a month across three retail stores. 

In this episode:

• The question I ask myself now that finally gets me to loosen my grip on something I'm holding too tightly
• Why "nobody can do it like I do" is almost always a control story 
• Nicki's inventory story, and the moment she admitted that letting go felt like operating in the dark 
• The math behind her sixteen hours a month, and what it added up to in working days at her peak with three stores
• A simple tool for deciding how much to hand off and to whom, so you're not stuck choosing between doing it all yourself and dropping it completely
• What I'd say to the version of me still sitting in that office that pivotal afternoon 

This week's permission: You are allowed to let something be done well by someone other than you. Being the only one who can do it isn't a compliment. It's a cost, and you're the one paying it.

People pleasers can't be trusted.

They're not dishonest on purpose. They're someone whose "yes" comes from the fear of disappointing you rather than saying "no".

In this episode, I share the story of a December I spent hand-painting a 4-foot Christmas trunk for my boss's sister, night after night, into the early hours of the morning, on top of one of the busiest stretches of our year. I said yes in about 30 seconds and resented every hour of it. And when the bow wasn't big enough, I painted a second one.

This episode names the pattern clearly, which is how saying yes when you mean no doesn't make you kind or helpful. It makes you unreliable, because the people around you can't trust an answer that was never a fully  explored decision. I get into why so many smart, capable women who lead default to yes this fast, and why flattery is one of the most effective delivery systems for an unreasonable request.

I also walk through a client's story: an invitation to speak on a panel, a friend doing the asking, and the opportunity-cost math that turned an automatic yes into an honest no, without losing the friendship.

In this episode:

• Why worry starts to feel like loyalty, and how that keeps people pleasing women who lead saying yes to things they don't want to do
• The sequence I use to turn an automatic yes into an actual decision
• The two questions I ask before committing to anything
• The client story of declining a friend's invitation to speak, and the exact words she used to say no without damaging the relationship
• What I do differently now when I feel the pull of flattery or the instinct to say yes too fast

This week's permission: You are allowed to say no without an essay of reasons attached to it. A clean no protects a relationship. A resentful yes can wreck it.

She lies down at 10 at night. At 1 in the morning she's still running scenarios.

The rollout. The training schedule. Who's going to quit over this. 

Every one of those is getting the same grip, the same attention, and the same tightness in her chest including the ones that were decided 1,200 kilometres away by people whose table she wasn't invited to join.

In this episode, I share the story of my client Juanita, a branch manager who found out by email that her company was rolling out a new software system, four years after the last rollout went badly enough that people still talk about it. She'd been asked for her input early in the process and then later she spent a week working a full-time second job in her head on a decision that had already been made.

This episode explores what is happening when something big lands on us and we don't sort it. Instead, we carry the parts we could move today with exactly the same grip as the parts that were never ours to even influence let alone control, so the things we can actually change end up with whatever energy is left over. And the leaders who do this most are rarely the avoidant ones. They're the most conscientious people on the team, which is what makes it so hard to catch in yourself.

I get into the three beliefs underneath it, all of which sound completely reasonable from the inside, and the exercise I walk clients through with a sheet of paper and 15 minutes. 

In this episode:

• Why worry starts to feel like loyalty, and what it costs to keep the fire going as proof that you still care
• The difference between preparing for something and rehearsing it on a loop at 1 a.m. when you can't sleep
• Why confusing having a voice with having a vote is the most expensive mistake of the three, and how it disguises itself as accountability
• The three circles exercise, what Epictetus and Stephen Covey each contributed to it, and the third circle I added
• The question I now ask myself out loud when I catch myself spun up about something

This week's permission: You are allowed to put it down. Being aware of something and feeding it are two different things, and your best two hours belong to the work that's in your control.

In this episode, I share the semester I spent chasing an instructor in my faculty for every report he owed me, the conversation I finally sat down and had with him over the break, and the four months afterward when I watched him slide right back into the pattern and said nothing. 

This episode is about how the conversation is one afternoon and holding the line is every day after it. When someone slips back and you stay quiet, rather than thinking you're not being generous with them, understand that you're teaching them that your standards have an expiry date. And most of the leaders doing this aren't avoidant by nature. They're the ones who care most about being fair, which is exactly what makes it so hard to see in yourself.

I get into the three reasons this happens, the ones that sound completely reasonable from the inside, and the accountability ladder I use now so that a missed standard has somewhere to go besides another round of the same conversation.

In this episode:

• Why the first slip after the conversation is the entire ballgame, and what your silence in that moment teaches the other person
• The difference between nagging and accountability, and why one comes from powerlessness and the other from a prior agreement
• What letting it slide costs you with your strong performers, long before it costs you anything with the person who missed the deadline
• The four-rung accountability ladder, with a script framework for each rung
• The one thing I now do during the conversation, while the person is still sitting in front of me

This week's permission: You are allowed to bring it up again. The conversation you had was the start of something, not the end of it, and following up on an agreement someone made with you is the job of being a leader.

Two people can look like the exact same kind of talent from the outside. One of them executes brilliantly. The other builds from nothing.

Promote the wrong one into the other's job, and you don't just lose a great performer. You could break them and the team around them.

In this episode, I share the story of a client, Carolyn, who did everything a good leader is supposed to do. She promoted from within. She picked the person everyone agreed was the obvious choice. Within months, she was watching a five-year superstar quietly come undone in a role that should have been a natural next step.

This episode names the pattern clearly: the difference between a tactician, who executes brilliantly inside a system someone else built, and a strategist, who builds the system in the first place. I talk about why smart, well-intentioned leaders keep making this exact misstep, the reasons that sound completely sensible in the moment, and what it actually costs when the best tactician on your team ends up drowning in a strategist's seat.

I also get into the rare case that trips up even careful leaders: the person who genuinely has both skillsets, and why that's almost never an even split.

In this episode:

• The real difference between a tactician and a strategist, and why intelligence isn't the same as either one
• Five reasons leaders keep promoting the wrong skillset into the wrong role, and why each one feels reasonable at the time
• What it actually costs a team when a builder's role gets handed to someone who was never built anything before
• The rare hybrid case, and why mistaking that person for a tactician will cost you them too
• The one question I ask before I recommend anyone move into a role that requires building something new

This week's permission: You don't owe a promotion to whoever is best at their current job. You owe the role the person who can actually do it.

Trying hard and producing results look like the same thing.

The problem is, they aren't. And rewarding the first when you need the second is how a leader can end up doing someone else's job for a year.

In this episode, I share the story of Nathan, one of our new hires everyone was excited about who tried hard, talked constantly about his plans, but never produced deliverable work. I kept fixing it myself instead of sending it back, for an entire year. Stating that effort ≠ results isn't some theory. It's a pattern I lived from the inside and eventually had to unlearn.

This episode names the pattern clearly: rewarding effort instead of results teaches your team that trying hard is the finish line, not the starting point, and it puts you on the hook for the gap they never learn to close.

I talk about the four reasons this feels reasonable in the moment and what it really costs.

In this episode:

• The story of the year I spent doing a new hire's job instead of holding him to a standard he was expected to meet 
• The four reasons that make rewarding effort over results feel completely reasonable, and why all four are wrong
• The five elements of fair leadership, and the one I was missing that let the pattern go on for a year
• What I do differently now
• The permission to stop treating effort as proof that the job got done

This week's permission: You are allowed to name the gap between effort and results without feeling unreasonable and demanding for doing it. Effort is not the finish line. Results are. Your job as a leader is to hold the standard, and let them meet it.

Marilyn ran a cleaning services company with a small, tight-knit team of eight people she genuinely cared about, including a couple of close friends. She wanted everyone to feel like they belonged. And by the time she came to me, she was exhausted, resentful, and covering for team members she couldn't hold accountable, while her best people quietly absorbed the gap.

In this episode, I share Marilyn's story and use it to walk through a pattern I see all too often in leaders who lead with warmth: the moment "we're a family here" stops being a culture statement and starts being the reason you can't have a hard conversation, enforce a standard, or let someone go without it feeling like a betrayal.

I break down the six-step cycle that traps well-intentioned leaders into this exact position, and the distinction that changes everything once you can see it: there's a real difference between a culture that feels like family and one you're actively trying to build into a family. One is a byproduct of leading well. The other is a structure that eventually collapses under its own metaphor.

I also walk through what it sounds like to shift from family rules to team rules including a real example of how the same missed-deadline conversation goes completely differently depending on which one you're operating from.

In this episode:

• The difference between being friends and being friendly; and why losing that line costs you your ability to lead
• The six-step cycle that turns a well-intentioned "family" culture into resentment, burnout, and quiet mutiny
• Why your most reliable team members are the ones who pay the price when underperformance goes unaddressed
• The one distinction that changes everything: a culture that feels like family versus one you're building into a family
• What you're actually building whether you mean to or not 
• How the exact same missed-deadline conversation sounds under family rules versus team rules

This week's permission: You don't have to dismantle the closeness you've built. What you need to do is to stop calling it family so you can finally lead it like the team it needs to be.

For two years, Monica was a rock star at her company. Then she started missing deadlines, forgetting conversations, and seeming scattered in meetings.

Her boss’s first thought: She’s gotten complacent. She’s checked out.

She hadn’t. Her nervous system had.

In this episode, I share Monica’s story. She's a senior leader who hadn’t lost her skill or her drive, but had lost access to her own regulated nervous system after a series of events in her personal life collided over the same six weeks. What looked like disengagement from the outside was overwhelm on the inside, and no amount of accountability or performance conversation was going to reach her there.

I get into why mindset work, the tool most of us reach for first, only works when your nervous system is regulated enough to use it. I walk through the difference between mindset work and nervous system regulation, why one sits on top of the other, and the predictable reasons high-achieving women who lead stay stuck trying to think their way through a state their body hasn’t caught up to yet.

I also share the specific practices I use before, during, and after hard conversations to check my own state first, drawn from years studying embodied processing and root cause therapy.

In this episode: 

• Why dysregulation looks like disengagement from the outside, and what’s actually happening underneath it 
• The moment a “what’s wrong with her performance” conversation has to become a “what’s happening to her capacity” conversation instead 
• Why mindset work depends entirely on your current state, and what happens when you try to use it without one 
• The four reasons high-achieving women who lead stay stuck applying mindset tools to a nervous system problem 
• The real distinction between mindset work and nervous system regulation, and why one can’t do the other’s job 
• My own before, during, and after practices for checking my nervous system state before a hard conversation

This week’s permission: You don’t have to think your way out of a nervous system in crisis. Before your next hard conversation, stop asking what you should say and start asking what state you’re actually in. Regulate first. The strategy will still be there.

Becka had been working 60-hour weeks for three years. She cared deeply about her team. She was constantly available. And one day, her best performer quit.

Not because Becka wasn't trying but because Becka had no system.

In this episode, I share Becka's story about a leader who was present, invested, and working herself into the ground, and still failing the people on her team in a way she couldn't see until someone walked out and told her directly. The problem wasn't her effort or her intentions. It was the absence of a rhythm for communication. Without one, the people who were loudest got her attention and the ones who quietly did their jobs went weeks without meaningful contact. And her best performer eventually stopped waiting to be noticed.

What changed everything for Becka was something I call the Clarity Scaffold, a structured rhythm for all your leadership communication so nothing falls through the cracks. In this episode, I walk through one of its most important pillars: the monthly performance check-in. It's the one leaders who are already doing weekly one-on-ones most often skip. And it's the one that handles what weekly check-ins can't. These include the patterns, the bigger picture, and the developmental conversation that only becomes possible when you zoom out.

I share exactly how a monthly check-in is structured, the three rules that make it work, and what it feels like for your team when they finally stop playing the guessing game of whether you're happy with their work.

In this episode:

• Why available and structured are two different things, and which one your best performers are asking for
• The pattern that keeps high performers from speaking up until it's too late
• How the Clarity Scaffold creates a rhythm that catches problems before they become crises
• The structure of a monthly performance check-in: what gets discussed, who leads it, and how long it takes
• Three rules that determine whether monthly check-ins work
• Why documenting these conversations matters more than most leaders realize and the simple follow-up habit that creates shared clarity

This week's permission: You don't have to earn your team's trust by being endlessly available. You earn it by being consistently present in a way they can count on. Block the time, create the rhythm, and let the structure do what good intentions alone never could.