Knowledge Base

This page outlines how information should be shared and documented so that it can be referred back to easily by all team members.

Internal communication procedures apply to all employees and freelancers. 

One-on-one communications that are not relevant to the rest of the team.

Communications relevant to our group but not necessarily related to a project are sent via group chats.

When communication relates to a specific project, it should be included in Teamwork Projects. This can include:

Information that needs to be referred back to periodically should be posted in a Notebook rather than a task; as tasks get checked off, their comments disappear. To make information easy to find for our team members, please make sure it is put in the right place. 

When assistance is required to respond to a client's communication, a team member can post a note to get the information they need from another team member. 

Tasks that do not take much time (less than 2 hours) or require many steps can be passed to team members as tickets. Tasks with distinct deadlines that require ongoing communication between team members or have multiple streams should be included in Teamwork Projects.

We have a standard meeting to catch up as a team, pass information off about new projects, etc. However,  team members can propose a meeting whenever they need to. Meetings are best used to discuss complex issues that would take longer to hash out over text. If team members will likely need to ask many questions, meetings can also help provide an open forum for that.

Emails are generally used for external communications, although we should strive to communicate with clients exclusively through Teamwork Desk tickets. This ensures if another team member needs to pick up on this communication stream, they have the context required to step in and help.