Many things aren't your fault but are still your problem. Integration failures, vendor mistakes, bad luck, the day of the week. If you're accountable for results, you're measured on outcomes regardless of cause. You have to fix it anyway.
There's a difference between what's your fault and what's your problem. The— what I find is that often there are things that don't go quite right. It could be the result of an integration, the result of a vendor, it could be the result of somebody who's working for you, it could be a result of just sort of context, bad luck, the day of the week, whatever. And it's reasonable to say that none of those conditions causing a downstream problem are your fault, right? They're just stuff that happens or stuff that's around you. That doesn't mean it's not your problem. When you have a responsibility for delivering a result or managing an area of a business or whatever, those things all matter, and you are still going to be measured based on the outcomes that your part of the business produces. And that means you sort of need to deal with those situations. That means, one, when bad circumstances happen, you know, doing something about it, i.e., when it rains, you gotta put out an umbrella. Or it means that you need to budget, right, for being able to handle those things in advance. Because managing those outcomes and managing the risk, that is your responsibility, even if it's not your fault.
