3 ms·
> I suspect creating psychological safety boils down to things like the rewards and incentive system, org structure and transparency of decision making but I'd
by MattGaiser 6y ago
> I suspect creating psychological safety boils down to things like the rewards and incentive system, org structure and transparency of decision making but I'd love to hear if anyone has first-hand experience
I've never been in management but I am someone who modifies my interactions with people very easily and is very conscious of what harm could come to me based on my various actions. I am also good at spotting squirming people.
Consider what you would do if you personally owned the company, i.e. you can't be fired and everyone must get along with you. What issues would you report? What opinions would you challenge? What ideas would you propose? How uncertain would you be willing to be in a discussion? Would you cut corners on the code to make sure that everything in the sprint gets finished by the end of the two weeks?
Compare that list to what you actually do. For example, most people challenge very rarely but I can confirm from the Slack conversations which parallel the meeting that many want to do that (myself included). I've been in plenty of meetings where most agree that something is pointless or even harmful and we leave the meeting to go implement it. Why? The person speaking is the manager. Our concern is only expressed in chatting on the Slack in private during the meeting. That is why UnderCover Boss is so good at finding issues management knows nothing about.
The difference is the psychological safety deficit. Ask yourself what exactly causes that difference. Why specifically do you challenge far less than you would like to? That is what you must fix.
The problem is that the people who know this information are often lacking in the power to yield change and extracting feedback on this in an environment with low psychological safety faces the same problems as extracting any other feedback (which is why you wanted to solve the problem in the first place).
I would not believe that it could be done without replacing >50% of team members and having them trust from the start.
- iateanapple 6y ago> Why specifically do you challenge far less than you would like to? Because if you push in another direction then you have to own the new direction. That is a lot of responsibility to take on - and in many organizations it comes with no reward and serious potential downside.
- MattGaiser 6y ago> serious potential downside See? Found your problem. The downside must be eliminated.
- iateanapple 6y ago> See? Found your problem. The downside must be eliminated. How? I’ve been successfully able to push for devs to be rewarded better - but I’ve never been able to eliminate the downside of a poor idea/execution.
- ripvanwinkle 6y agoI suspect that an incentive system that is heavily biased towards collective success would make a big difference. The more we are vested in each other's success the more we are likely to want to bring out the best in each other and from there we might begin to get psychological safety and other goodness
- MattGaiser 6y ago> I posit that an incentive system that is heavily biased towards collective success would make a big difference. There needs to be enough individual benefit (or the team must be small enough) that individual efforts can move the needle. But yes I agree. One of the biggest challenges for companies is that the average employee has no reason to care whether their project succeeds.