How to offer a good apology

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
2
down vote

favorite
1












This morning I ended up missing a teleconference that I regularly host with two peers on another continent. I was doing research and lost track of time. I rely heavily on my Outlook notifications but I turned them off at some point for this series of occurences. Regardless of the reason this was an obnoxious error on my part. Without a doubt an apology was in order and the below apology has been sent.




I am very sorry for missing the meeting today. I just realized that recently my outlook has not given me a reminder notice for our meetings as this feature was turned off. I rely heavily on this feature as I get so engrossed in what I’m doing that I lose track of time.



I sincerely value our weekly meeting and appreciate your contributions
to this project. I apologize for wasting your time and have taken
steps to ensure that it doesn’t happen again by turning the reminder
notification on.




This got me thinking. In the workplace effectively acknowleding when you drop the ball is a crucial skill. What are the keys to a good apology? Does it change if the apology is directed to a manager/peer/subordinate?







share|improve this question


























    up vote
    2
    down vote

    favorite
    1












    This morning I ended up missing a teleconference that I regularly host with two peers on another continent. I was doing research and lost track of time. I rely heavily on my Outlook notifications but I turned them off at some point for this series of occurences. Regardless of the reason this was an obnoxious error on my part. Without a doubt an apology was in order and the below apology has been sent.




    I am very sorry for missing the meeting today. I just realized that recently my outlook has not given me a reminder notice for our meetings as this feature was turned off. I rely heavily on this feature as I get so engrossed in what I’m doing that I lose track of time.



    I sincerely value our weekly meeting and appreciate your contributions
    to this project. I apologize for wasting your time and have taken
    steps to ensure that it doesn’t happen again by turning the reminder
    notification on.




    This got me thinking. In the workplace effectively acknowleding when you drop the ball is a crucial skill. What are the keys to a good apology? Does it change if the apology is directed to a manager/peer/subordinate?







    share|improve this question






















      up vote
      2
      down vote

      favorite
      1









      up vote
      2
      down vote

      favorite
      1






      1





      This morning I ended up missing a teleconference that I regularly host with two peers on another continent. I was doing research and lost track of time. I rely heavily on my Outlook notifications but I turned them off at some point for this series of occurences. Regardless of the reason this was an obnoxious error on my part. Without a doubt an apology was in order and the below apology has been sent.




      I am very sorry for missing the meeting today. I just realized that recently my outlook has not given me a reminder notice for our meetings as this feature was turned off. I rely heavily on this feature as I get so engrossed in what I’m doing that I lose track of time.



      I sincerely value our weekly meeting and appreciate your contributions
      to this project. I apologize for wasting your time and have taken
      steps to ensure that it doesn’t happen again by turning the reminder
      notification on.




      This got me thinking. In the workplace effectively acknowleding when you drop the ball is a crucial skill. What are the keys to a good apology? Does it change if the apology is directed to a manager/peer/subordinate?







      share|improve this question












      This morning I ended up missing a teleconference that I regularly host with two peers on another continent. I was doing research and lost track of time. I rely heavily on my Outlook notifications but I turned them off at some point for this series of occurences. Regardless of the reason this was an obnoxious error on my part. Without a doubt an apology was in order and the below apology has been sent.




      I am very sorry for missing the meeting today. I just realized that recently my outlook has not given me a reminder notice for our meetings as this feature was turned off. I rely heavily on this feature as I get so engrossed in what I’m doing that I lose track of time.



      I sincerely value our weekly meeting and appreciate your contributions
      to this project. I apologize for wasting your time and have taken
      steps to ensure that it doesn’t happen again by turning the reminder
      notification on.




      This got me thinking. In the workplace effectively acknowleding when you drop the ball is a crucial skill. What are the keys to a good apology? Does it change if the apology is directed to a manager/peer/subordinate?









      share|improve this question











      share|improve this question




      share|improve this question










      asked Sep 24 '14 at 15:07









      Myles

      25.4k658104




      25.4k658104




















          3 Answers
          3






          active

          oldest

          votes

















          up vote
          5
          down vote













          Your apology needs a little work. First, it has passive tense in it: this feature was turned off. Part of apologizing is owning your mistakes. Second, it has too much detail, they don't really care why you missed it. The reason you missed it is it wasn't top priority in your mind and you got caught up with something else. Third, you wait too long to address the emotional aspects of your error, putting it after your detailed technical explanation that implies it wasn't your fault.



          A good apology:



          • starts with "sorry" or "I apologize" and then immediately states the action and the meaning of that action


          My apologies for missing our meeting today. I realize I must have wasted your time while you waited for me, and possibly delayed the project.




          • goes on to clarify the emotions involved


          I sincerely value our weekly meeting and appreciate your contributions to this project.




          • optionally explains how it happened, retaining ownership of your mistakes


          I was a little too enthusiastic with a new no-interruptions approach, so my technology didn't remind me of the meeting




          • closes by just assuring that it won't happen again, or detailing steps you're taking to prevent it from happening again


          I will make sure not to suppress reminders about this meeting in future.




          That said, this is an overapology for missing a meeting. I would not send this email to be filed and referred to later. Instead, I would call each person as soon as I realized what happened and say




          I've just realized I missed our meeting this morning! I'm so sorry. Is there anything urgent we need to cover before the next meeting? I'll make myself available whenever you need to talk.




          Generally you will have to work extra to make up for this, and that's as it should be.






          share|improve this answer




















          • It's a bit bigger than an in person missed meeting. As the host if I'm not there the other parties are waiting on a blank line until I show up or they give up. Also these peers are assisting and supporting my project with little to no gain for themselves or their home site so IMO it's assenine to fail to be ready to receive help that you ask for. Other than that, nice answer. How do you decide on the "optionally explain how it happened"?
            – Myles
            Sep 24 '14 at 16:07










          • I decide whether or not to explain why it happened based on whether they are likely to "get it" and identify with me over it. Car trouble, power outage and other unavoidable things are great reasons to mention. Technical details or your own personality traits are not. Anything that sounds like a flimsy excuse is not.
            – Kate Gregory
            Sep 24 '14 at 16:12










          • Isn't sounding flimsy pretty subjective on the audience? This is between a group of engineers so I would assume that the technical details would definitely be something they "get" (and probably expect).
            – Myles
            Sep 24 '14 at 16:21










          • for sure. There's no recipe you can follow absolutely, there's always your judgement. But remember they can always ask for details, or even just "but how did this happen?" if they care.
            – Kate Gregory
            Sep 24 '14 at 16:31

















          up vote
          1
          down vote













          When it comes to apologies, I tend to call the offended parties instead of emailing. Two reasons - a call is more personal and it (usually) doesn't get recorded. Last thing you want is a reminder somewhere that you, one day, dropped the ball.






          share|improve this answer
















          • 1




            While I tend to agree, in this case calling internationally is probably not best, if they cost the company money.
            – thursdaysgeek
            Sep 24 '14 at 15:23










          • More personal I get but not wanting it recorded takes away from the "take accountability for your actions" aspect of an apology.
            – Myles
            Sep 24 '14 at 15:26










          • If it is the same company they may have IP phones that won't incur costs. But it is a good point.
            – user1220
            Sep 24 '14 at 15:26






          • 2




            @Myles - I disagree. The fact that you called and apologized in my view is taking enough accountability.
            – user1220
            Sep 24 '14 at 15:27

















          up vote
          0
          down vote













          Your apologies are quick, to the point and leave no room for misunderstanding: just as it is blindingly obvious that you screwed up, it has to be blindingly obvious that you are apologizing. No parsing of the words, no excuses, no escape clauses, no vaseline, no shock absorbers. Go straight to the heart of the matter, and drive that stake into that vampire's heart :)



          There are exceptions: I have delivered apologies where I made it clear that the fault wasn't mine and apologies that were non-apologies because I sure as hell wasn't going to take the fall for what somebody outside my command chain did and was liable to do it again.






          share|improve this answer




















            Your Answer







            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "423"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: false,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            noCode: true, onDemand: false,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );








             

            draft saved


            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f34142%2fhow-to-offer-a-good-apology%23new-answer', 'question_page');

            );

            Post as a guest

























            StackExchange.ready(function ()
            $("#show-editor-button input, #show-editor-button button").click(function ()
            var showEditor = function()
            $("#show-editor-button").hide();
            $("#post-form").removeClass("dno");
            StackExchange.editor.finallyInit();
            ;

            var useFancy = $(this).data('confirm-use-fancy');
            if(useFancy == 'True')
            var popupTitle = $(this).data('confirm-fancy-title');
            var popupBody = $(this).data('confirm-fancy-body');
            var popupAccept = $(this).data('confirm-fancy-accept-button');

            $(this).loadPopup(
            url: '/post/self-answer-popup',
            loaded: function(popup)
            var pTitle = $(popup).find('h2');
            var pBody = $(popup).find('.popup-body');
            var pSubmit = $(popup).find('.popup-submit');

            pTitle.text(popupTitle);
            pBody.html(popupBody);
            pSubmit.val(popupAccept).click(showEditor);

            )
            else
            var confirmText = $(this).data('confirm-text');
            if (confirmText ? confirm(confirmText) : true)
            showEditor();


            );
            );






            3 Answers
            3






            active

            oldest

            votes








            3 Answers
            3






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            5
            down vote













            Your apology needs a little work. First, it has passive tense in it: this feature was turned off. Part of apologizing is owning your mistakes. Second, it has too much detail, they don't really care why you missed it. The reason you missed it is it wasn't top priority in your mind and you got caught up with something else. Third, you wait too long to address the emotional aspects of your error, putting it after your detailed technical explanation that implies it wasn't your fault.



            A good apology:



            • starts with "sorry" or "I apologize" and then immediately states the action and the meaning of that action


            My apologies for missing our meeting today. I realize I must have wasted your time while you waited for me, and possibly delayed the project.




            • goes on to clarify the emotions involved


            I sincerely value our weekly meeting and appreciate your contributions to this project.




            • optionally explains how it happened, retaining ownership of your mistakes


            I was a little too enthusiastic with a new no-interruptions approach, so my technology didn't remind me of the meeting




            • closes by just assuring that it won't happen again, or detailing steps you're taking to prevent it from happening again


            I will make sure not to suppress reminders about this meeting in future.




            That said, this is an overapology for missing a meeting. I would not send this email to be filed and referred to later. Instead, I would call each person as soon as I realized what happened and say




            I've just realized I missed our meeting this morning! I'm so sorry. Is there anything urgent we need to cover before the next meeting? I'll make myself available whenever you need to talk.




            Generally you will have to work extra to make up for this, and that's as it should be.






            share|improve this answer




















            • It's a bit bigger than an in person missed meeting. As the host if I'm not there the other parties are waiting on a blank line until I show up or they give up. Also these peers are assisting and supporting my project with little to no gain for themselves or their home site so IMO it's assenine to fail to be ready to receive help that you ask for. Other than that, nice answer. How do you decide on the "optionally explain how it happened"?
              – Myles
              Sep 24 '14 at 16:07










            • I decide whether or not to explain why it happened based on whether they are likely to "get it" and identify with me over it. Car trouble, power outage and other unavoidable things are great reasons to mention. Technical details or your own personality traits are not. Anything that sounds like a flimsy excuse is not.
              – Kate Gregory
              Sep 24 '14 at 16:12










            • Isn't sounding flimsy pretty subjective on the audience? This is between a group of engineers so I would assume that the technical details would definitely be something they "get" (and probably expect).
              – Myles
              Sep 24 '14 at 16:21










            • for sure. There's no recipe you can follow absolutely, there's always your judgement. But remember they can always ask for details, or even just "but how did this happen?" if they care.
              – Kate Gregory
              Sep 24 '14 at 16:31














            up vote
            5
            down vote













            Your apology needs a little work. First, it has passive tense in it: this feature was turned off. Part of apologizing is owning your mistakes. Second, it has too much detail, they don't really care why you missed it. The reason you missed it is it wasn't top priority in your mind and you got caught up with something else. Third, you wait too long to address the emotional aspects of your error, putting it after your detailed technical explanation that implies it wasn't your fault.



            A good apology:



            • starts with "sorry" or "I apologize" and then immediately states the action and the meaning of that action


            My apologies for missing our meeting today. I realize I must have wasted your time while you waited for me, and possibly delayed the project.




            • goes on to clarify the emotions involved


            I sincerely value our weekly meeting and appreciate your contributions to this project.




            • optionally explains how it happened, retaining ownership of your mistakes


            I was a little too enthusiastic with a new no-interruptions approach, so my technology didn't remind me of the meeting




            • closes by just assuring that it won't happen again, or detailing steps you're taking to prevent it from happening again


            I will make sure not to suppress reminders about this meeting in future.




            That said, this is an overapology for missing a meeting. I would not send this email to be filed and referred to later. Instead, I would call each person as soon as I realized what happened and say




            I've just realized I missed our meeting this morning! I'm so sorry. Is there anything urgent we need to cover before the next meeting? I'll make myself available whenever you need to talk.




            Generally you will have to work extra to make up for this, and that's as it should be.






            share|improve this answer




















            • It's a bit bigger than an in person missed meeting. As the host if I'm not there the other parties are waiting on a blank line until I show up or they give up. Also these peers are assisting and supporting my project with little to no gain for themselves or their home site so IMO it's assenine to fail to be ready to receive help that you ask for. Other than that, nice answer. How do you decide on the "optionally explain how it happened"?
              – Myles
              Sep 24 '14 at 16:07










            • I decide whether or not to explain why it happened based on whether they are likely to "get it" and identify with me over it. Car trouble, power outage and other unavoidable things are great reasons to mention. Technical details or your own personality traits are not. Anything that sounds like a flimsy excuse is not.
              – Kate Gregory
              Sep 24 '14 at 16:12










            • Isn't sounding flimsy pretty subjective on the audience? This is between a group of engineers so I would assume that the technical details would definitely be something they "get" (and probably expect).
              – Myles
              Sep 24 '14 at 16:21










            • for sure. There's no recipe you can follow absolutely, there's always your judgement. But remember they can always ask for details, or even just "but how did this happen?" if they care.
              – Kate Gregory
              Sep 24 '14 at 16:31












            up vote
            5
            down vote










            up vote
            5
            down vote









            Your apology needs a little work. First, it has passive tense in it: this feature was turned off. Part of apologizing is owning your mistakes. Second, it has too much detail, they don't really care why you missed it. The reason you missed it is it wasn't top priority in your mind and you got caught up with something else. Third, you wait too long to address the emotional aspects of your error, putting it after your detailed technical explanation that implies it wasn't your fault.



            A good apology:



            • starts with "sorry" or "I apologize" and then immediately states the action and the meaning of that action


            My apologies for missing our meeting today. I realize I must have wasted your time while you waited for me, and possibly delayed the project.




            • goes on to clarify the emotions involved


            I sincerely value our weekly meeting and appreciate your contributions to this project.




            • optionally explains how it happened, retaining ownership of your mistakes


            I was a little too enthusiastic with a new no-interruptions approach, so my technology didn't remind me of the meeting




            • closes by just assuring that it won't happen again, or detailing steps you're taking to prevent it from happening again


            I will make sure not to suppress reminders about this meeting in future.




            That said, this is an overapology for missing a meeting. I would not send this email to be filed and referred to later. Instead, I would call each person as soon as I realized what happened and say




            I've just realized I missed our meeting this morning! I'm so sorry. Is there anything urgent we need to cover before the next meeting? I'll make myself available whenever you need to talk.




            Generally you will have to work extra to make up for this, and that's as it should be.






            share|improve this answer












            Your apology needs a little work. First, it has passive tense in it: this feature was turned off. Part of apologizing is owning your mistakes. Second, it has too much detail, they don't really care why you missed it. The reason you missed it is it wasn't top priority in your mind and you got caught up with something else. Third, you wait too long to address the emotional aspects of your error, putting it after your detailed technical explanation that implies it wasn't your fault.



            A good apology:



            • starts with "sorry" or "I apologize" and then immediately states the action and the meaning of that action


            My apologies for missing our meeting today. I realize I must have wasted your time while you waited for me, and possibly delayed the project.




            • goes on to clarify the emotions involved


            I sincerely value our weekly meeting and appreciate your contributions to this project.




            • optionally explains how it happened, retaining ownership of your mistakes


            I was a little too enthusiastic with a new no-interruptions approach, so my technology didn't remind me of the meeting




            • closes by just assuring that it won't happen again, or detailing steps you're taking to prevent it from happening again


            I will make sure not to suppress reminders about this meeting in future.




            That said, this is an overapology for missing a meeting. I would not send this email to be filed and referred to later. Instead, I would call each person as soon as I realized what happened and say




            I've just realized I missed our meeting this morning! I'm so sorry. Is there anything urgent we need to cover before the next meeting? I'll make myself available whenever you need to talk.




            Generally you will have to work extra to make up for this, and that's as it should be.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Sep 24 '14 at 15:32









            Kate Gregory

            105k40232334




            105k40232334











            • It's a bit bigger than an in person missed meeting. As the host if I'm not there the other parties are waiting on a blank line until I show up or they give up. Also these peers are assisting and supporting my project with little to no gain for themselves or their home site so IMO it's assenine to fail to be ready to receive help that you ask for. Other than that, nice answer. How do you decide on the "optionally explain how it happened"?
              – Myles
              Sep 24 '14 at 16:07










            • I decide whether or not to explain why it happened based on whether they are likely to "get it" and identify with me over it. Car trouble, power outage and other unavoidable things are great reasons to mention. Technical details or your own personality traits are not. Anything that sounds like a flimsy excuse is not.
              – Kate Gregory
              Sep 24 '14 at 16:12










            • Isn't sounding flimsy pretty subjective on the audience? This is between a group of engineers so I would assume that the technical details would definitely be something they "get" (and probably expect).
              – Myles
              Sep 24 '14 at 16:21










            • for sure. There's no recipe you can follow absolutely, there's always your judgement. But remember they can always ask for details, or even just "but how did this happen?" if they care.
              – Kate Gregory
              Sep 24 '14 at 16:31
















            • It's a bit bigger than an in person missed meeting. As the host if I'm not there the other parties are waiting on a blank line until I show up or they give up. Also these peers are assisting and supporting my project with little to no gain for themselves or their home site so IMO it's assenine to fail to be ready to receive help that you ask for. Other than that, nice answer. How do you decide on the "optionally explain how it happened"?
              – Myles
              Sep 24 '14 at 16:07










            • I decide whether or not to explain why it happened based on whether they are likely to "get it" and identify with me over it. Car trouble, power outage and other unavoidable things are great reasons to mention. Technical details or your own personality traits are not. Anything that sounds like a flimsy excuse is not.
              – Kate Gregory
              Sep 24 '14 at 16:12










            • Isn't sounding flimsy pretty subjective on the audience? This is between a group of engineers so I would assume that the technical details would definitely be something they "get" (and probably expect).
              – Myles
              Sep 24 '14 at 16:21










            • for sure. There's no recipe you can follow absolutely, there's always your judgement. But remember they can always ask for details, or even just "but how did this happen?" if they care.
              – Kate Gregory
              Sep 24 '14 at 16:31















            It's a bit bigger than an in person missed meeting. As the host if I'm not there the other parties are waiting on a blank line until I show up or they give up. Also these peers are assisting and supporting my project with little to no gain for themselves or their home site so IMO it's assenine to fail to be ready to receive help that you ask for. Other than that, nice answer. How do you decide on the "optionally explain how it happened"?
            – Myles
            Sep 24 '14 at 16:07




            It's a bit bigger than an in person missed meeting. As the host if I'm not there the other parties are waiting on a blank line until I show up or they give up. Also these peers are assisting and supporting my project with little to no gain for themselves or their home site so IMO it's assenine to fail to be ready to receive help that you ask for. Other than that, nice answer. How do you decide on the "optionally explain how it happened"?
            – Myles
            Sep 24 '14 at 16:07












            I decide whether or not to explain why it happened based on whether they are likely to "get it" and identify with me over it. Car trouble, power outage and other unavoidable things are great reasons to mention. Technical details or your own personality traits are not. Anything that sounds like a flimsy excuse is not.
            – Kate Gregory
            Sep 24 '14 at 16:12




            I decide whether or not to explain why it happened based on whether they are likely to "get it" and identify with me over it. Car trouble, power outage and other unavoidable things are great reasons to mention. Technical details or your own personality traits are not. Anything that sounds like a flimsy excuse is not.
            – Kate Gregory
            Sep 24 '14 at 16:12












            Isn't sounding flimsy pretty subjective on the audience? This is between a group of engineers so I would assume that the technical details would definitely be something they "get" (and probably expect).
            – Myles
            Sep 24 '14 at 16:21




            Isn't sounding flimsy pretty subjective on the audience? This is between a group of engineers so I would assume that the technical details would definitely be something they "get" (and probably expect).
            – Myles
            Sep 24 '14 at 16:21












            for sure. There's no recipe you can follow absolutely, there's always your judgement. But remember they can always ask for details, or even just "but how did this happen?" if they care.
            – Kate Gregory
            Sep 24 '14 at 16:31




            for sure. There's no recipe you can follow absolutely, there's always your judgement. But remember they can always ask for details, or even just "but how did this happen?" if they care.
            – Kate Gregory
            Sep 24 '14 at 16:31












            up vote
            1
            down vote













            When it comes to apologies, I tend to call the offended parties instead of emailing. Two reasons - a call is more personal and it (usually) doesn't get recorded. Last thing you want is a reminder somewhere that you, one day, dropped the ball.






            share|improve this answer
















            • 1




              While I tend to agree, in this case calling internationally is probably not best, if they cost the company money.
              – thursdaysgeek
              Sep 24 '14 at 15:23










            • More personal I get but not wanting it recorded takes away from the "take accountability for your actions" aspect of an apology.
              – Myles
              Sep 24 '14 at 15:26










            • If it is the same company they may have IP phones that won't incur costs. But it is a good point.
              – user1220
              Sep 24 '14 at 15:26






            • 2




              @Myles - I disagree. The fact that you called and apologized in my view is taking enough accountability.
              – user1220
              Sep 24 '14 at 15:27














            up vote
            1
            down vote













            When it comes to apologies, I tend to call the offended parties instead of emailing. Two reasons - a call is more personal and it (usually) doesn't get recorded. Last thing you want is a reminder somewhere that you, one day, dropped the ball.






            share|improve this answer
















            • 1




              While I tend to agree, in this case calling internationally is probably not best, if they cost the company money.
              – thursdaysgeek
              Sep 24 '14 at 15:23










            • More personal I get but not wanting it recorded takes away from the "take accountability for your actions" aspect of an apology.
              – Myles
              Sep 24 '14 at 15:26










            • If it is the same company they may have IP phones that won't incur costs. But it is a good point.
              – user1220
              Sep 24 '14 at 15:26






            • 2




              @Myles - I disagree. The fact that you called and apologized in my view is taking enough accountability.
              – user1220
              Sep 24 '14 at 15:27












            up vote
            1
            down vote










            up vote
            1
            down vote









            When it comes to apologies, I tend to call the offended parties instead of emailing. Two reasons - a call is more personal and it (usually) doesn't get recorded. Last thing you want is a reminder somewhere that you, one day, dropped the ball.






            share|improve this answer












            When it comes to apologies, I tend to call the offended parties instead of emailing. Two reasons - a call is more personal and it (usually) doesn't get recorded. Last thing you want is a reminder somewhere that you, one day, dropped the ball.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Sep 24 '14 at 15:15









            user1220

            4,80622644




            4,80622644







            • 1




              While I tend to agree, in this case calling internationally is probably not best, if they cost the company money.
              – thursdaysgeek
              Sep 24 '14 at 15:23










            • More personal I get but not wanting it recorded takes away from the "take accountability for your actions" aspect of an apology.
              – Myles
              Sep 24 '14 at 15:26










            • If it is the same company they may have IP phones that won't incur costs. But it is a good point.
              – user1220
              Sep 24 '14 at 15:26






            • 2




              @Myles - I disagree. The fact that you called and apologized in my view is taking enough accountability.
              – user1220
              Sep 24 '14 at 15:27












            • 1




              While I tend to agree, in this case calling internationally is probably not best, if they cost the company money.
              – thursdaysgeek
              Sep 24 '14 at 15:23










            • More personal I get but not wanting it recorded takes away from the "take accountability for your actions" aspect of an apology.
              – Myles
              Sep 24 '14 at 15:26










            • If it is the same company they may have IP phones that won't incur costs. But it is a good point.
              – user1220
              Sep 24 '14 at 15:26






            • 2




              @Myles - I disagree. The fact that you called and apologized in my view is taking enough accountability.
              – user1220
              Sep 24 '14 at 15:27







            1




            1




            While I tend to agree, in this case calling internationally is probably not best, if they cost the company money.
            – thursdaysgeek
            Sep 24 '14 at 15:23




            While I tend to agree, in this case calling internationally is probably not best, if they cost the company money.
            – thursdaysgeek
            Sep 24 '14 at 15:23












            More personal I get but not wanting it recorded takes away from the "take accountability for your actions" aspect of an apology.
            – Myles
            Sep 24 '14 at 15:26




            More personal I get but not wanting it recorded takes away from the "take accountability for your actions" aspect of an apology.
            – Myles
            Sep 24 '14 at 15:26












            If it is the same company they may have IP phones that won't incur costs. But it is a good point.
            – user1220
            Sep 24 '14 at 15:26




            If it is the same company they may have IP phones that won't incur costs. But it is a good point.
            – user1220
            Sep 24 '14 at 15:26




            2




            2




            @Myles - I disagree. The fact that you called and apologized in my view is taking enough accountability.
            – user1220
            Sep 24 '14 at 15:27




            @Myles - I disagree. The fact that you called and apologized in my view is taking enough accountability.
            – user1220
            Sep 24 '14 at 15:27










            up vote
            0
            down vote













            Your apologies are quick, to the point and leave no room for misunderstanding: just as it is blindingly obvious that you screwed up, it has to be blindingly obvious that you are apologizing. No parsing of the words, no excuses, no escape clauses, no vaseline, no shock absorbers. Go straight to the heart of the matter, and drive that stake into that vampire's heart :)



            There are exceptions: I have delivered apologies where I made it clear that the fault wasn't mine and apologies that were non-apologies because I sure as hell wasn't going to take the fall for what somebody outside my command chain did and was liable to do it again.






            share|improve this answer
























              up vote
              0
              down vote













              Your apologies are quick, to the point and leave no room for misunderstanding: just as it is blindingly obvious that you screwed up, it has to be blindingly obvious that you are apologizing. No parsing of the words, no excuses, no escape clauses, no vaseline, no shock absorbers. Go straight to the heart of the matter, and drive that stake into that vampire's heart :)



              There are exceptions: I have delivered apologies where I made it clear that the fault wasn't mine and apologies that were non-apologies because I sure as hell wasn't going to take the fall for what somebody outside my command chain did and was liable to do it again.






              share|improve this answer






















                up vote
                0
                down vote










                up vote
                0
                down vote









                Your apologies are quick, to the point and leave no room for misunderstanding: just as it is blindingly obvious that you screwed up, it has to be blindingly obvious that you are apologizing. No parsing of the words, no excuses, no escape clauses, no vaseline, no shock absorbers. Go straight to the heart of the matter, and drive that stake into that vampire's heart :)



                There are exceptions: I have delivered apologies where I made it clear that the fault wasn't mine and apologies that were non-apologies because I sure as hell wasn't going to take the fall for what somebody outside my command chain did and was liable to do it again.






                share|improve this answer












                Your apologies are quick, to the point and leave no room for misunderstanding: just as it is blindingly obvious that you screwed up, it has to be blindingly obvious that you are apologizing. No parsing of the words, no excuses, no escape clauses, no vaseline, no shock absorbers. Go straight to the heart of the matter, and drive that stake into that vampire's heart :)



                There are exceptions: I have delivered apologies where I made it clear that the fault wasn't mine and apologies that were non-apologies because I sure as hell wasn't going to take the fall for what somebody outside my command chain did and was liable to do it again.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Sep 24 '14 at 16:24









                Vietnhi Phuvan

                68.9k7118254




                68.9k7118254






















                     

                    draft saved


                    draft discarded


























                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f34142%2fhow-to-offer-a-good-apology%23new-answer', 'question_page');

                    );

                    Post as a guest

















































































                    Comments

                    Popular posts from this blog

                    What does second last employer means? [closed]

                    List of Gilmore Girls characters

                    Confectionery