>>1069449 (OP)
web developers are known to say - 'I get the same problems in the middle of a coding process that they had in the beginning. We're supposed to just write code, and then make a decision about why we're doing it later.'
That is exactly how coding is supposed to work - you're expected to make the decision you want to make - not you, the person who is just putting the thing together.
The real problem with this approach is the lack of trust in the team. We don't trust someone who thinks she is better than me - or even you, your colleague - because of the things she is writing.
The result is an open channel between developers and the customers
A better approach is to create an internal chat room. These are things that your employees know intimately, they are not 'listening in on conversations'.
The company needs to be transparent in the way that it uses its chat rooms. It needs to be clear in order to engage with developers. It needs to create open channels in which developers can speak privately with each other to find out about issues raised.
Instead we are constantly asking, 'Is it ok for me to share my thoughts and opinions in public on my own chatroom? If the answer is no, then I should tell customers I'm sorry'.
But how do we go about this?