Hello and welcome to Episode 331 of The People Powered Business Podcast.

Do you ever catch yourself justifying a decision to your team three different ways before you've even finished the sentence? Or slip in an apology before giving a completely reasonable instruction? If that's you, you're not alone, and it's costing you more than you think.

I see this constantly with the business owners I work with: over-explaining, apologising, adding disclaimers to decisions. It feels considerate, it feels inclusive, it feels kind. But it's actually undermining your authority and changing how your team sees you as a leader, whether you realise it or not. Most of us do it because we don't want to be the boss who barked orders without any context, the boss none of us wanted to work for. This one flies under the radar because it looks like good manners rather than a leadership issue, so I wanted to unpick it properly, because I promise you, every business owner has done this at some point.

In this episode I walk through why over-explaining feels like good leadership but is actually the opposite, and the real difference between giving your team context, which is good leadership, and asking for their permission, which isn't. I talk about what your team actually hears when you apologise for asking them to do their job (it's not what you think), and why that habit compounds over time until you snap over something small and your team has no idea why. I bring in the Brené Brown line I use constantly with business owners, clear is kind, unclear is unkind, and share three practical ways to make a call and own it: leading with the decision instead of the explanation, cutting the disclaimers, and building yourself a few short, reusable phrases. If you're naturally direct this will come easily, if you're more considered by nature it'll take a bit more practice, and that's completely normal. I also touch on why silence isn't the enemy of good leadership, and a pattern I see all the time: most of us apologise to our lowest performers, not our best ones.

In this episode we cover:

• Why over-explaining feels like good leadership, but is actually the opposite
• The real difference between giving context and asking for permission
• What your team actually hears when you apologise for a reasonable request
• Three practical ways to make a decision and own it, starting today
• Why silence isn't the enemy of good leadership

Links & Resources:

💬 DM Kristy-Lee on Instagram @kristy.lee.billett

Connect with me on LinkedIn: https://www.linkedin.com/in/kristyleebillett/

Email me at hello@peoplepoweredbusiness.com.au

Book a 15-minute clarity call: https://calendly.com/kristyleebillett/chat

What this episode covers

Over-explaining, apologising and adding disclaimers to decisions might feel considerate, but it undermines a leader's authority and changes how a team responds to instruction. This episode breaks down the difference between giving a team context, which builds trust, and seeking their permission, which erodes it, and sets out three practical techniques for making a decision and communicating it with confidence. It's for small business owners who want their team to trust their decisions without needing to justify every one of them.

Key insight from this episode

Giving a team context builds trust; seeking their approval erodes it. The distinction sits in a simple question: is this explanation helping the team understand the decision, or is it seeking their sign-off on a decision that's already been made? Leaders who confuse the two train their teams to treat reasonable requests as negotiable, and to see normal expectations as impositions.

What you'll take away

• Recognise the difference between giving context and seeking permission when communicating a decision
• Understand why apologising for reasonable requests trains a team to resist them
• Learn a simple technique for leading with the decision before the explanation
• Build reusable phrases that communicate decisions clearly, without over-explaining or disclaimers
• Understand why silence during a difficult conversation is a leadership strength, not a weakness

Hello and welcome to Episode 333 of The People Powered Business Podcast.

Do you catch yourself giving instructions that come with a pre-packaged apology? "Sorry to be a pain, but..." "Sorry, I know you're flat out, but..." If every request you make of your team arrives wrapped in a sorry, this episode is for you.

And if you think that little apology is you being kind, I'd love you to keep reading, because it's doing the opposite of what you intend.

A couple of episodes back we talked about the risks of over-explaining yourself to your team, and I briefly mentioned that over-explaining often comes with an apology attached. As I've been working with my Power Boss clients over the last few weeks, I've realised just how many of us have fallen into apologising as a default. One client even emailed me to say it felt like I was looking straight at her.

We do this almost subconsciously, usually because we've worked for the barking-orders type of boss and decided we'd never be that person. The trouble is, nobody hands you the playbook for what to do instead.

In this episode I get into what that reflex sorry is really telling your team.

When an apology is attached to a completely reasonable instruction, it frames the task as an imposition, something negotiable, a personal favour that deserves something in return. I've seen it play out as "well, I did that thing for you, so can I leave early on Friday?" It also reads as uncertainty, and teams don't follow an unsure leader. Worse still, it muddies your standards, because you've effectively apologised for setting them.

I also cover why certain boss styles (my high S and high I DISC people, I see you) lean on this habit more than others, the times when sorry absolutely IS the right word, and a really simple language swap you can start using this week.

In this episode we cover:

• Why apologising before an instruction feels kind, and what it's actually signalling to your team
• The imposition effect: how a reflex sorry turns normal parts of the job into negotiable favours
• What default apologies do to your standards, your authority and your team's performance
• When an apology is exactly the right call, and why owning mistakes builds respect
• The quick word swap that replaces sorry with something warmer, clearer and more confident

Links & Resources:

💬 DM Kristy-Lee on Instagram @kristy.lee.billett

Connect with me on LinkedIn: https://www.linkedin.com/in/kristyleebillett/

Email me at hello@peoplepoweredbusiness.com.au

Book a 15-minute clarity call: https://calendly.com/kristyleebillett/chat

What this episode covers

Many small business owners soften every instruction to their team with an apology, believing it makes them a kinder boss. This episode explains why the habit forms, what a reflex "sorry" actually signals to employees, and how to give clear, warm direction without it. It's for any business owner or team leader who wants to be respected without becoming the overbearing boss they once worked for.

Key insight from this episode

When an apology is attached to a reasonable work request, it reframes that task as an imposition rather than a normal part of the job. Over time, employees begin treating core duties as favours that deserve reciprocity, and their sense of what the role requires shrinks. The apology intended as kindness ends up lowering standards, blurring expectations and depleting team performance.

What you'll take away

• Recognise the personality styles and situations where default apologising takes hold, including why high S and high I DISC profiles lean on it most
• Understand how apology-wrapped instructions train a team to see tasks as negotiable and leaders as unsure
• Know when an apology genuinely builds respect: owning mistakes and missteps, never decisions or instructions
• Apply a simple language swap, replacing "sorry to ask" with "thanks for picking this up", to change the energy of every request
• See the connection between apologising for standards and struggling to uphold them later