It doesn't even require you to put your ego aside if you take pride in being someone who can "lose" an argument gracefully. I put "lose" in scare quotes because, if you do it right, you can count that argument as a mutual victory.
I had a girlfriend complain "you always have to be right!" to which I replied "no, I'm just willing to admit when I am wrong". She objected, saying that I win every arguement. I recalled many occurances where she won arguements and pointed out how breif those discussions were because I allowed her to be right. Then she got even more angry at me for being right again...
I actually dated her for quite a long time past this discussion. We parted ways quite amicably after growing apart because I kept switching back and forth between Philadelphia and the west coast for internships. You're reading too much into it, but I definitely understand where you are coming from and in the common case, you are right.
This is generally a good strategy even if it wasn't your mistake. Last week I wrote a short apology for something I'm sure I didn't do, which got my client in trouble with his business partner.
The business partner sent my client an angry email demanding to know how the mistake could have been made. It's very likely that it was the business partner's mistake, very unlikely that it was my clients mistake... but "oh, hey! our consultant was working near that issue, maybe he touched it?! We'll ask him right away, Mr. Angry Important Business Partner!"
Problem is: there's no possible way to know who did it. Shifting it back to the likely source (business partner's team) will only make him more angry, whether or not they are responsible. As a consultant, I can only loose.
So I write an email to him, CC my client, and apologize for the mistake, promising that it won't happen again. My client knows I didn't do it, and now knows that I willingly took the bullet for him.
Maybe SGaaS is a valid business model, where SG = scapegoat.
A very good policy and good advice. Still, one should be careful about apologizing in a way that could bring them financial liability for something they actually were not responsible for.
22 comments
[ 3.4 ms ] story [ 60.2 ms ] threadThat is, if you're humble enough to put your ego aside.
Seriously.
The business partner sent my client an angry email demanding to know how the mistake could have been made. It's very likely that it was the business partner's mistake, very unlikely that it was my clients mistake... but "oh, hey! our consultant was working near that issue, maybe he touched it?! We'll ask him right away, Mr. Angry Important Business Partner!"
Problem is: there's no possible way to know who did it. Shifting it back to the likely source (business partner's team) will only make him more angry, whether or not they are responsible. As a consultant, I can only loose.
So I write an email to him, CC my client, and apologize for the mistake, promising that it won't happen again. My client knows I didn't do it, and now knows that I willingly took the bullet for him.
Maybe SGaaS is a valid business model, where SG = scapegoat.
Another one of my favourites: Phrasing a request like you're asking a favour even though you're just telling someone to do their job.
One could argue that consultancy firms are already in this business, as you've just described.
When unpleasant decisions need to be made, hire a bunch of consultants who can 'rubber stamp' it so the management and board can pass the blame.
"That would reduce to the halting problem"
Or my favorite,
"If you can solve that problem, there are much more lucrative applications for the technology than [what you're working on]"
I don't have a link, although I think it was on HN awhile back.