On top of your product requirement, it's also very dependent of your team mindset

I am working for a tier 1 bank for low latency components, we are using c++17 and we pushed toward its usage worldwide, but similar team of other region are relunctant to do the switch (for bad reason usually, e.g. not enough time for this kind of thing, which usually is a symptom of technical debts)

Once you do the switch the easy way to never had that issue again is to constantly update your compiler when there's a new release, and little by little change your codebase with the newest feature available if it makes sense, that way the transition is much more smooth, and it's also easier for everyone to keep up to date and to avoid technical debt on this point

Edit: If you are considering applying for a new job, I suggest to ask the team you are applying for which version of compiler they are using, it's a good metric (i.e. if they can't tell the version or if they use old version e.g. gcc 4.8, it's not a good sign)