It's obviously going to strongly depend on the context, but I've found that there is a shared amount of risk in organisations where IT and Finance both have the

It's obviously going to strongly depend on the context, but I've found that there is a shared amount of risk in organisations where IT and Finance both have their choices to make together. Say you have some on-prem datacenter stuff for a manufacturing plant, you might have the request from factory operations to be as available and consistent as possible. The cost for such a thing might be astronomical, but even a single day of downtime would cover it. On the other hand, the finance department might already have made a risk assessment and set aside some money or had it insured in some way and now suddenly the impact of that risky thing that might happen is a whole lot lower in terms of money. For a lot of people that can be news, or unexpected. If you silo yourself you might end up engineering something that is completely unnecessary. At the same time, someone might be buying some expensive insurance, but forgets that unrecoverable data doesn't magically yeet itself into existence just because the insurance contract says so. So while on paper it's "covered and we just need to recover our systems and get on with it", in reality that might not be possible. Starting a company from scratch (IT-wise) leaves you with empty systems. Those are about as useful as a brick. A functional brick, but perhaps not the spreadsheet, email or CRM database you had in mind. This is a lot of words just to say: in most companies (as long as they don't get too big), most people are there for a reason, and most departments are there for a reason. Go up the chain of reasoning and you'll find your common reason ("because the company wants to make money" for example), and now you have all you need to 'justify' to yourself that 'those other people' are there for the same reason and with the same goal as you.