
You challenged someone's work before checking the facts. Or you dismissed a concern that later proved useful. Now you need to address your part.
To apologise as a manager, name what you did, acknowledge the impact, take responsibility and explain the repair. Then give the other person room to respond. The aim is a clear account of what happened and a change they can observe.
Identify the action you need to own
Start with the specific incident. Write down what you said or did, where it happened and who was affected. Keep your account separate from assumptions about anyone's intentions.
“I interrupted your explanation three times” names an action. “The meeting became difficult” leaves your contribution unclear. You can acknowledge your conduct even when other parts of the discussion remain unresolved.
Next, consider the practical impact. Did your comment leave an inaccurate impression of someone's work? Did an unannounced change create avoidable rework? Describe what you know, and leave space for the person to explain what you missed.
Avoid announcing feelings on their behalf. “You must have felt humiliated” may not match their experience. Try: “I criticised the draft in front of the group without hearing your explanation. I want to understand the impact.”
You do not need to apologise for every disagreement. A manager can maintain a reasonable work expectation while apologising for how they communicated it. Make that distinction clear without using the expectation to excuse the conduct.
Prepare a short apology and choose the setting
Draft the apology before arranging the conversation. Use four prompts: What did I do? What impact can I acknowledge? What responsibility is mine? What will I do to put it right?
Keep the first version brief enough to say without reading a speech. Remove the background details that mainly defend your intentions. If context matters, discuss it after you have clearly acknowledged your action.
Choose a setting where the employee can respond without an audience. You might say, “I owe you an apology about yesterday's review. Would you prefer a short conversation or a written message first?” Respect their preference where possible.
If your mistake created a public misunderstanding, consider what needs correcting with the same group. Check with the affected person before sharing details about their experience. A correction should not expose more than necessary.
Do not delay simply because the wording feels uncomfortable. If you still need to check facts, acknowledge the part you already know. Avoid filling gaps with a confident account you may later need to withdraw.
Use wording that connects responsibility with repair
Here is a hypothetical example. A manager told colleagues that a designer had ignored agreed changes. The manager later discovered that they had opened an older file.
A specific apology could sound like this:
“I said you had ignored the agreed changes before checking the latest file. That was my mistake. I gave the team an inaccurate account of your work, and I am sorry. I will correct that with them today and check the file version before future reviews.”
Follow with one invitation: “Is there anything about the impact that I have missed?” Then listen. The employee may focus on something different, such as the time they spent defending a decision they had already implemented.
Avoid adding “but the deadline was tight” to the apology. The deadline may explain the circumstances, but it does not transfer responsibility. Likewise, “I am sorry you took it that way” leaves your action unaddressed.
Do not ask the employee to reassure you that you are a good manager. They may accept the apology, remain reserved or want time. None of those responses removes your responsibility to complete the repair.
Make the repair visible in everyday work
Choose a repair that matches the incident. Correct inaccurate information, restore missing credit or clarify a change you communicated poorly. Avoid a sweeping promise such as “This will never happen again” when a specific working practice is more credible.
Name what you will do and when. In the file example, the immediate repair is correcting the team's understanding. The continuing practice is checking the current version and asking the designer to explain unresolved points before commenting.
Separate your action from requests for the employee. An apology should not become a list of things they must do to prevent your mistake. You can discuss shared improvements later, after taking responsibility for your part.
Offer a proportionate follow-up. “I will check in after the next review to ask whether the process was clearer” gives the conversation a practical return point. Avoid repeatedly asking whether the relationship is now repaired.
A second mistake needs another honest acknowledgement. Refer to the action you agreed, identify where it failed and adjust it. Repeating an apology without changing the practice leaves the original problem unresolved.
Reflect on your response without turning it into a label
After the repair, use a private handwritten note to examine the moment before your mistake. What did you notice? What did you assume? What could you check before acting next time?
For example, replace “I am a bad listener” with “I responded before the person had finished explaining the file history.” The second statement identifies something you can practise. Choose one action, such as summarising what you heard before offering a judgement.
If you want an additional exploratory perspective, handwriting analysis is optional. Begin with informed consent, a natural handwriting sample and a joint review with a graphologist. Treat any report themes as prompts, then compare them with your perspective, role expectations and real examples.
Handwriting interpretations are not validated measures of performance, suitability, personality or future behaviour. They cannot establish why an incident happened or whether an apology is sincere. Human judgement remains essential; agree one practical action and review it through later conversations and observable conduct.
SoulEra's Leadership service describes a development approach that brings reflection alongside work examples and the individual's perspective. It is an optional avenue for reflection, while the apology and repair remain yours to carry out.
Begin with the action you need to own. Say what happened plainly, hear the impact and complete the repair you promised. At the next similar moment, practise the specific change you chose. That gives the other person something concrete to assess over time.