A lot of things go better if more people have more context on the state of a project. Just to name a few:

• Others can point out mistakes
• People can build common knowledge of how much everyone is working
• Others can build better models of your strengths and weaknesses, which means we can coordinate better around those
• If you need help, or become unavailable, others can jump in more easily

Slack is the central place for that kind of context sharing. There is practically no oversharing. Reading is cheap, and even if everyone on the team was continuously writing, I would still be able to at least skim what everyone on the team is saying.

Some specific guidelines we have for this kind of sharing:

• Avoid using DMs. It's OK to use them if you have something sensitive or private to discuss, but the vast majority of your written communication with individuals should be in public channels (either a generic X-Y-dm channel, a project-specific channel, or on their wall channel).
• If you are collecting any kind of analytics, post it regularly to a Slack channel for your project
• CC the team-transparency email on external email communication so [...]

---

First published:

Source:

---

Narrated by TYPE III AUDIO.