Both of these approaches are great. In my experience, #4 rears its head over and over again. People tend to tie their identity and ego to their ideas and work

Both of these approaches are great. In my experience, #4 rears its head over and over again. People tend to tie their identity and ego to their ideas and work products and it can be very blinding and disabling in terms of figuring out a path forward that might exclude something that they perceive of as "theirs". "It's my code", or "That was my idea" becomes very problematic when its explicit. Doubly so when the person is unable to acknowledge it and it becomes and implicit, but unknown decision driver. I've worked at more than one company where a senior manager tied us to rapidly outdating tools and software simply because it was what they worked on when they were junior -- even when there were demonstrably better tools or approaches or software out there -- but this fact never came up in the reasoning for why we stuck with something (even if it was very obvious).