Sorry Is Not a Strategy: How Reflex Apologising Undermines Your Authority

There is a particular kind of workplace apology that has nothing to do with wrongdoing. It arrives before a question, before an idea, before a perfectly reasonable request. It is the "sorry to bother you" that opens an email, the "sorry, can I just say" that precedes a contribution in a meeting, and the "sorry to chase" that softens a follow-up which should not need softening at all.

In UK professional culture, this reflex is often read as good manners. It is not always experienced that way. Over time, habitual apologising becomes what might be called an apology tax: a small but recurring deduction from your authority, your decision-making speed and your reserves of energy. The tax is rarely visible on any single occasion. It accumulates.

The cost is rarely the word itself

The problem is not that apologies exist. Genuine accountability requires them. If you have missed a deadline, overlooked a commitment or caused a colleague extra work, a clear and specific apology is appropriate. It repairs trust and demonstrates maturity.

The difficulty arises when apology becomes a default linguistic wrapper for ordinary professional activity. Asking for information is not an imposition. Contributing an idea is not an interruption. Following up on an agreed action is not an offence. When these things are framed as apologies, the underlying message changes. The sender implies that their needs are a nuisance and that their presence in the conversation requires permission.

This has practical consequences. Decisions slow down because questions arrive hedged and recipients are unsure whether a response is genuinely required. Authority erodes because the person with the expertise presents themselves as an interruption rather than a contributor. And stress rises because the apologiser is constantly performing a small act of self-diminishment in order to be heard.

The irony is that many capable professionals apologise precisely because they care about being considerate. The intention is good. The habit is costly.

Distinguish accountability from reflex

A useful test is to ask whether the apology names an impact and a remedy. Genuine accountability sounds like: "I missed the deadline I agreed to. That left you unable to brief the client on time. I have sent the revised document this morning and will confirm receipt with you by noon." It is specific, owned and forward-looking.

Reflexive apologising sounds like: "Sorry, just sending this now." It does not name an impact because there may not be one. It simply places the speaker in a smaller position than the situation warrants.

Teams can help by making this distinction explicit. Managers who model clean accountability, and who do not reward unnecessary self-blame, create a culture in which people can be direct without being discourteous. That is particularly valuable in UK workplaces, where politeness is often used as a proxy for professionalism. Courtesy and clarity are not opposites.

Three replacement scripts

The aim is not to eliminate apology but to reserve it for moments that genuinely require it. The following replacements work because they retain warmth while removing unnecessary self-diminishment.

1. In email: replace "sorry to bother you" with a clear request and reason

Instead of: "Sorry to bother you, I just wanted to check whether you had any thoughts on the draft."

Try: "I would value your view on the draft by Thursday. Your comments on the client section will help me finalise it before the deadline."

The second version respects the recipient's time and makes the request easy to act on. It also removes the implication that the sender is a nuisance for asking a normal work question.

2. In meetings: replace "sorry, can I just..." with a direct contribution

Instead of: "Sorry, can I just add something?"

Try: "I would like to add a point about the implementation timeline."

This is not aggressive. It is simply a contribution introduced as a contribution. If the meeting is busy, you can add a brief rationale: "I would like to add a point about the implementation timeline, because it affects the resource estimate." The chair can still manage time. You have not apologised for having a relevant view.

3. In requests: replace "sorry to chase" with a factual follow-up

Instead of: "Sorry to chase again, but have you had a chance to look at this?"

Try: "Following up on the action agreed on 14 October. Could you confirm by Friday whether the figures are approved, so I can proceed with the schedule?"

This version is courteous and precise. It references the agreement, states the needed confirmation and explains why the timing matters. It treats the request as part of a shared process rather than a personal imposition.

Make it a team norm, not a personal project

Changing a verbal habit is easier when the surrounding culture supports it. In team meetings, leaders can invite direct contributions without requiring elaborate prefacing. In written communication, teams can agree that requests will include a clear action and deadline. In one-to-ones, managers can gently reflect back when a colleague apologises for something that does not require an apology, asking: "What would it sound like if you simply made the request?"

The goal is not a workplace without apology. It is a workplace where apology retains its weight. When sorry is used for genuine accountability, it means something. When it is used as verbal padding, it trains everyone to hear it as noise.

For UK professionals, the shift can feel uncomfortable at first. Politeness is deeply embedded in how we manage relationships at work. But courtesy does not require self-erasure. The most respectful version of a request is often the clearest one. Removing the apology tax is not about becoming harder. It is about spending your authority on the work that matters rather than on repeated permission-seeking.