Technical design docs are an efficient way to communicate about software architecture and technical solutions. These docs precede an architectural decision record. They benefit from detail, though brevity is an important consideration too.

Feature breakdown documents serve as a single resource to catalogue all information about a feature. As the team enhances the feature, this document becomes a single source of truth about it.

Idea papers allow you to nurture fresh ideas by articulating them clearly. People can use this as a reference to share feedback and enrich the idea. Decision making is also easier if everyone can understand the idea well.

A single line message that you send to 200 people isn’t a single line message anymore. It’s a 200-line message. Instead, “shrink the blast radius”.

Arguments on chat don’t help. Take a deep breath and slow things down.

One thread, one topic. And vice-versa.

Limit chat conversations only to those necessary to the discussion.

In the spirit of limiting messages, use emoji reactions where possible, instead of responding to a message.

It’s ok to write longer chat messages! Save everyone the extra notifications.

Imagine calling someone on the phone, going hello! then putting them on hold!

Most project management tools allow you to define a workflow for your team and visualise that workflow as a task board. Your task board should be the source of truth for all the work your team is up to.