I appreciate and agree with the core of your argument here, but it's not very useful for me.
I am that leader who is setting the example. We aren't endlessly changing tools, it's a new project. It's not another layer on top of the existing chatroom, nothing exists yet.
If there are product teams who are happy with their stack, I want to hear about it. It implies they have their communication sorted, their people have the right behaviours, and then they found tools which support them.
I can do the first parts of that, but I'm unaware of the current market of the tools that might follow. Or to put it another way: I'm looking for data so I can consider the problem, I'm not looking for an answer to some problem I haven't stated.
> If there are product teams who are happy with their stack, I want to hear about it. It implies they have their communication sorted, their people have the right behaviours, and then they found tools which support them.
For us, it’s Slack/Zoom/GitHub Issues. But you’re using Slack/Zoom and not having success. It’s not the stack.
Looking to the tools for the success is the definition of cargo culting.
I am that leader who is setting the example. We aren't endlessly changing tools, it's a new project. It's not another layer on top of the existing chatroom, nothing exists yet.
If there are product teams who are happy with their stack, I want to hear about it. It implies they have their communication sorted, their people have the right behaviours, and then they found tools which support them.
I can do the first parts of that, but I'm unaware of the current market of the tools that might follow. Or to put it another way: I'm looking for data so I can consider the problem, I'm not looking for an answer to some problem I haven't stated.