Look, if you want to do damage control, you gotta give us more than "there's more to it than that, but I can't say." Tell us: what was there to gain by delaying the story? Why did you tell him to hold off? And when people were publicly attacking him, why did you feel compelled to order him take the character assassination without being able to defend himself?
I'm willing to listen; I've worked in newsrooms. But you can't be vindicated by just saying, "That's how the business works." Tell us why the calls you made weren't terrible calls, and why his disregard of those decisions was egregious enough for a firing. Everyone makes employment mistakes sometimes, and most aren't fire-worthy. Tell us why the calls you made were not so terrible that disregarding them is the only thing a reasonable person would do, and why his disregard of those calls was fire-worthy.
If you can't tell us, we get that, but you can't expect us to change our minds. If you're worried about your site being boycotted, better ignore the lawyer advice and open up.
I wouldn't say "that's how business works" actually. But lets look at what a few days of polish can achieve (or why managing editors exist in the first place).
Just compare the story posted on Saturday on GamersWithoutBigotry to the raw material on Twitlonger (which was deleted) that I was so against posting on Tuesday.
Both contain the same information, but nobody's flipping cars at me over the latter. What was posted on Saturday had way more polish, it read better, an editor oversaw it before publishing it, it was balanced in that the fraud culprit is quoted, and is obviously free of liability. The Saturday piece was BASED on the Tuesday notes, and I love the other article.
Since the fraud stuff was reported four weeks before that there was no reason to rush into this. It would have still exposed all the facts and turned a lot of heads and made more of an impact and not rubbed anybody the wrong way. I'm oversimplifying what happened, but I think you'll get my drift.