"The only way to apologize is to list a step you've actually taken to actually prevent it happening again." Sometimes you need to issue an apology before you h

"The only way to apologize is to list a step you've actually taken to actually prevent it happening again." Sometimes you need to issue an apology before you have time to take any concrete action. In fact, in crisis management, time till expected response is often more critical than noodling on precisely what must be done. You're in a triage situation, and the first thing you need to do is stop the bleeding. This is why "promises" get made, because they're the first step in figuring out a genuine series of restitutive actions. Often the first thing people want to hear -- and need to hear -- is a simple acceptance of responsibility. The acceptance should be followed by a legitimate demonstration of understanding: of the damages caused, of the seriousness of the issue, etc. This is followed by a pledge to investigate, or to take serious actions. Now here's the important part (to your point): 9 out of 10 apologies just leave it at that. There's no follow-through or followup. This is why people have been desensitized to the standard-issue apology as detailed in this article. They're used to seeing boilerplate and empty promises, but the devil is in the details. Listing a concrete action taken is a great way to go, but sometimes you don't have time to take such action (or fully consider the ramifications) before the apology needs to be issued. In summary: 1) take serious stock of the issue ASAP, 2) state sincere apology demonstrating accountability for the fuckup and responsibility for the fix, 3) maintain communication as fixes are implemented, and detail them.