Constant emails, requests for updates via management tools, group chats can also be a sign of not…
Christian Toivola

A successful manager’s job is to create an environment that enables people to do great work. This is done through leadership, feedback, coaching and training (this is not an exhaustive list). There’s a fair amount of communication involved, but I don’t believe it’s any more than is necessary for normal interaction with people.

To be successful, a developer needs to communicate A LOT. Should that communication be primarily progress oriented? I don’t think so. Successfully, completing a feature requires meeting with subject matter experts, asking questions, giving demos, listening to feedback, writing documentation, creating bug reports, discussing reported defects, etc. These are all forms of communication, as they all involve direct interaction with others.

The idea that we should avoid a tool as disruptive as chat as the primary form of organizational communication sounds like a good one to me. But it’s just as big of a problem for management as it is for staff, in my opinion.

A single golf clap? Or a long standing ovation?

By clapping more or less, you can signal to us which stories really stand out.