Skip to main content
Effective communication is central to our operation as a remote company. Since we are typically in different physical spaces, we must efficiently and effectively use our various communication tools. We strongly recommend that you read the Communication page in the Employee Handbook for essential insights. Beyond the practical and philosophical advice in the Staff Handbook, it’s essential for you, as a developer, to understand the impact of communication. Being part of a remote team at Trew Knowledge requires strong communication skills and the ability to self-direct. This involves consistently communicating your progress, being open about challenges, and voicing concerns over project-related decisions. We value and try to incorporate everyone’s feedback into our decision-making process. This principle is applied throughout the company; we seldom make decisions without considering team feedback, continuously refining our approaches based on what we learn. Regular communication through weekly updates and project retrospectives helps us collect this feedback passively. However, we encourage you to voice your thoughts whenever you actively spot areas for improvement. Offering feedback during meetings is a great way to discuss your insights and potential solutions directly with decision-makers. Your manager is always there to support you in navigating any concerns and deciding how best to express them. You should always feel comfortable sharing feedback openly. However, if you prefer a private discussion, you can approach the relevant individuals confidentially. For more significant concerns, contact the Director of Engineering or CTO. For interpersonal issues, our Human Resources team is always available for support.

​
Slack Communication Do’s and Don’t

​
Be direct and purposeful

  1. Start with Intent: Begin your direct messages on Slack with a clear purpose, avoiding casual greetings like “hey” or “hello” without immediately diving into the subject matter. This ensures that conversations are focused and efficient.
  2. Provide Context: Always include relevant context in your messages. This helps recipients understand the purpose of the communication upfront, reducing the need for clarification and back-and-forth exchanges.
  3. Respect Time and Focus: Developers often need uninterrupted focus to tackle complex problems. Avoid sending notifications followed by vague messages that can disrupt their flow. Respect their time and provide concise information to enable them to respond effectively.
  4. Include Necessary Details: When reaching out to a colleague for assistance or information, be mindful of their workload. Clearly state what you need from them and any relevant deadlines or constraints. This allows them to prioritize their tasks and respond appropriately.
For example, instead of saying: “Hey!” (1 second ago) “Are you available for a call?” (3 seconds ago) and then vanishing till they respond. You can say, “Hey, can you help me with a bug related to calculation of order total for WooCommerce? I have tried X and Y but no luck.”

​
Do use threads to maintain conversation flow

Slack threads enable users to reply directly to topics and messages that pertain to them. Replying within a thread declutters the channel and helps maintain control of the workspace. Threads ensure that responses are seen by the necessary eyes.

​
Don’t ignore availability statuses

If someone is marked as away, that’s for a reason. It’s no good spamming people to get their attention. This causes annoyance and discomfort when users have updated their availability. One of Slack’s best features is its potential for third-party integrations. Consider adding a calendar app synced with your work schedule, allowing coworkers to see when you are in a meeting. This helps to mitigate response expectations without having to ask you directly.