I have been running an experiment for the last year, and will also be interviewing professional developers, outside of my circles, as part of my research. Management and engineering cultures have been described as orthogonal, and the standard approach may be characterized as getting engineering to conform to management values.
Leadership has to be realist enough to understand that a) tech talent has other options b) managers have to commit to transparent dialogue and culture that is attractive to engineers, or pay talent higher than competitors.
With the fix-and-cheat in software fiascos such as Boeing 737 Max crashes and Volkswagen emission scandals,to name just two, this is a serious concern. With software eating the world, it will continue to grow in global magnitude.
Treating people with respect is not hard, it's just often not done in the corporate environment.
Right now I am consulting my university as to what would be appropriate to do the research anonymously, as close to truly as possible, to protect the sources, yet still have academic rigor.
My problem is that early on, I was interviewing engineers at a well-known San-Francisco company. That company had engaged in paranoid spy-craft, such as having developers followed, as well as the standard emails read, etc. My email was under continuous attacks and several trojans were sent to my personal phone (which I had not published online, nor had linked to my name in any records). So it looks like I have to protect my identity as well, to protect my sources. This is one of my current challenges.
I'll ping your comment once I set something up, thanks for your interest. The problem for me right now is making sure the people I interview are safe from corporate repercussion, due to their participation.
Voicing ethical concerns about management is a firing offense for many, it seems.So I have to make sure the blog / mailing list is set up so that the website, list, etc doesn't expose people.