I do this with internal teams at work. I've found approaching other teams with issues with their library/framework in a "this could be our mistake" manner really helps in keeping them from getting defensive and stonewalling.
Then be grateful for the help, because it truly isn't granted or a given that people have to drop everything and figure things out for you, even if you work together. And even if the mistake was actually theirs. Gratitude is huge.
It could go both ways. I can never change though; saying sorry is too simple for me
Me: Sorry, I forgot about some details about the stuff I was working on last month.
Him: Your memory is so bad. I can literally remember all the details of the last 6 months. Try to become more like me.
> It wasn’t her fault
Sir, I don't know you at all, but coming from personal experience, if you often get walked over, maybe it's time to stop taking shape of a door mat. Maybe it _was_ her fault, and you deserve better.
I'm sorry, I know this is a serious discussion, but this made me laugh. I need to use this in the future.
To give a really grotesque example, there is an country run by autocrats that carelessly unleashed a plague on the world because they prioritized their self image over taking descisive action to prevent an epidemic.
This is very wrong. Eastern/Asian culture with its obsession with saving face is the culture where saying sorry is anathema.
Years ago we started to get basic introduction into Chinese culture, so that we could better navigate situations with a Chinese customer. This helped to better understand requirements and defuse certain situations. I've NEVER experience Chinese or Indian companies go to the same length, instead they will frequently attempt to bullshit their way out of situations or be offended that you believe that their product/service might in some way be at fault and they sure as hell won't apologize for it, under any circumstances.
Ever been to Japan?
You don't have to be excessively self-effacing about it, just avoid presenting things as though the project you're reporting it to being at fault is the only possible conclusion.
Even if you get an error from the software, consider that you might not be using it as intended or setup properly.
Sure, be kind, but don’t bullshit people. My personal and professional tolerance for bullshit is very low these days because there’s so much of it.
Except if you're actually convinced it could be your mistake, getting that tone will feel like getting played like some small kid. Most people will help you anyway and be professional, of course.
That reminds me of detective Columbo. It's cute and all when it's supposed to be done to strangers. Imagine Columbo coming to you every week with that same convoluted spiel.
https://youtu.be/hVimVzgtD6w https://www.ted.com/playlists/474/the_best_hans_rosling_talk...
If you want, you can acknowledge how you tried to fix it and failed (if that's accurate). But don't say that the problem is your fault unless it is.
(There are situations in which taking blame for a situation not necessarily yours might be a convention, but mistakes of vendors when talking with the vendor aren't one of them, IMHO. For example, you might take a little heat for colleagues, when appropriate, and all the CEO you're talking with needs to hear right then is, "Sorry, I don't have that for you yet; let me get that to you later today." Not "I've been pestering Bob since Monday for the dependency." Then you can go tell Bob that you two really need to solve this in the next couple hours. And if there's a larger problem, like Bob has been overextended by a family problem, or tasking has been unclear since a tentative pivot, then work it with management in the appropriate vertices of the org chart.)
A few days ago I suddenly had my french press for coffee suddenly shatter and almost blast hot coffee over my upper body.
How am I supposed to start that call with "Hi, I'm jorvi and I made a mistake"..?
It's not like that is a unique situation either. And you can guarantee that if you tell customer service "I made a mistake", and it is clear they delivered a broken service / product (but often want to duck responsibilities), there is no way in hell they will not take the freebie you just gave them by admitting fault.
Practice those first, then work on inter personal soft skills.
Don’t bullshit people by lying to them about “whose fault it is”.
The kill switch was set to “off.”
Friends of mine hearing him would say, He never says what the mistake is precisely, but there’s always the option that it was booking a flight with that airline.
It basically helps move things forward, blame has been allocated, how do we move on from here, but this only works if you have a health work environment.
This wasn't a company policy or anything like that, it was just how we talked and supported each other.
ticks the 'potential liability' box
"How can I help you?"
If you don’t do it for the sake of the person you are asking for help, do it because it works better. That’s the most practical advice [0] ever given by Hans Rosling [1], the Fact master himself:
> In fact, I have the secret to how to get the best help immediately from any customer service, like the phone company or the bank or anything. I have the best line, it always works. You want to know what it is? When I call, I say, “Hello. I am Hans Rosling and I have made a mistake.” People immediately want to help you when you put it this way. You get much more when you don’t offend people.
[0]: Unless you are in charge of a developing country’s budget and have to decide between education and healthcare.
[1]: https://blog.ted.com/qa_with_hans_ro_1/