On responsibilities: In my previous company the product website system was over-engineered and urgently required 50 people on-call every second night, because always something was not working.
The company has lots of cash, so they kept adding layers of teams, spreading the responsibilities, so nobody was in charged of anything. (but it was SOX etc. compliant).
It was a big mess.
The site front-end was developed by somebody else and included some CSS script from some other CDN, which had a 8 seconds time-out. It could not be fixed because nobody was in charge and nobody took initiative.
I think nobody even recognized there was a 8 second delay in page loaded and nobody cared.
The company has lots of cash, so they kept adding layers of teams, spreading the responsibilities, so nobody was in charged of anything. (but it was SOX etc. compliant).
It was a big mess.
The site front-end was developed by somebody else and included some CSS script from some other CDN, which had a 8 seconds time-out. It could not be fixed because nobody was in charge and nobody took initiative.
I think nobody even recognized there was a 8 second delay in page loaded and nobody cared.