>If I had to guess, I think it might be related to people’s experience in school/college. I am not so sure on that. But I have seen similar throughout my years

>If I had to guess, I think it might be related to people’s experience in school/college. I am not so sure on that. But I have seen similar throughout my years. More and more I am coming to the conclusion this is one of those "some people are wired a certain way, others are not". I have seen plenty of highly "educated" folks lacking terribly in skillsets. I have seen the same for those with no education. As an instructor as well, it skews similar with the students I have seen. Some just have a "fire" and work through issues, others will just give up at the first sign of issue (I am talking "I couldnt figure out key based auth, so i did nothing". I have tried to get folks to take personal ownership in products and deliverables, to varying degrees of success. In the past I was ardently against "silos" of responsibility but ultimately this led to some taking no ownership stake in any products. So we have had to transition to "assigning" primary, secondary, tertiary responsibility to services/products. This helped a little bit but also led to some then just bringing in personal excuses. Ultimately I have come to the conclusion that folks have varying capacity for load/projects and how much they are simultaneously work/support. As well as varying capacity to be able to work indepedantly vs need more guidance/check-ins on stuff. I try and cater to whats needed to get the most out of them and understand not everyone is a rockstar that can just take a challenge and come back with solutions. Even still, it can be tricky managing that withing intra-team dynamics.