>A good manager will avoid design by committee and will stay ahead of the spontaneous Slack firehose by arranging planning sessions and scheduled meetings where necessary
A great point. They will ideally also have enough context, experience and intuition to 'individualize' comms - providing detail from an earlier briefing to the ux person while omitting the unnecessary technical details that are more relevant to the other team mate who is working on a security feature.
As a team lead, I do subject myself to a bit of a firehose outside my immediate team in the hopes of stumbling across little nuggets of useful info and context, but if I orchestrate communications within my org well enough, that's the only time it occurs.
A great point. They will ideally also have enough context, experience and intuition to 'individualize' comms - providing detail from an earlier briefing to the ux person while omitting the unnecessary technical details that are more relevant to the other team mate who is working on a security feature.
As a team lead, I do subject myself to a bit of a firehose outside my immediate team in the hopes of stumbling across little nuggets of useful info and context, but if I orchestrate communications within my org well enough, that's the only time it occurs.