Communication

Goal of this document


Good communication is the key to happy kudus. Being on the same page on how to communicate is the first step to communicate well.

We value fluid and flexible over formal and stuffy, but we think it's important to agree on a few basic rules to achieve this.

TL;DR;

  • Hair on fire => cell phone or video call
  • Internal communications
  • Need this by end of day => Asana with due date + mention in Slack
  • Sometimes this week => Asana with due date
  • Real-time chats are like conveyor belts "perpetually moving away from you". It can be useful when there is an emergency, but we tend to use them too much.
  • Asynchronous communication should be the default mode. And "if everyone needs to see it, don’t chat about it".
  • Someday => Asana
  • OKR tracking / Weekly 1:1 ⇒ 15Five

Best practices

  • Phone call
  • Email
  • Slack
  • Asana
  • Google Doc / Quip / Slite
  • Github

Concepts and cool ideas

Download / Discuss / Decide
How to use communication channels effectively

Client Communication Guidelines



General principals

Do's
  • Even if a question is simple, follow the process
  • Always be helpful, polite and positive
  • Ensure you have an understanding of the context and have the details to reproduce the issue
  • Strive to be interested, not to be interesting
Don't do's
  • Be passive aggressive
  • Never commit to a request on the fly

Email

  • Subject line standards: MadKudu <> ClientName - Name of the task
  • Always cc  success@madkudu.com