Skip to content
Snippets Groups Projects

added steps and made minor edits.

Closed Sylvia Kahn requested to merge internal-communications-edits into master

cc /@Ernst

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
131 131 <h4 id="internal-communication">Internal Communication</h4>
132 132 <ol>
133 133 <li>Use <b>asynchronous communication</b> when possible (issues and email instead of chat), issues are preferred over email, email is preferred over Slack.</li>
134 <li>If you notices something that is not documented, unclear or needs to be addressed, please open and issue.</li>
134 135 <li>If you have to use email please send one email per subject as multiple items in one email will cause delays (have to respond to everything) or misses (forgot one of the items).</li>
135 136 <li>Always reply to emails, even when no action is needed. This lets the other person know that you received it. A thread is done when there is a single word reply, such as OK, thanks, or done.</li>
137 <li>If you are not going to make the morning meeting, you can make a note of it on the agenda for that date, or not. Please do not reply "no" to the invite as that results in unnecssary email for the meeting organizer. We trust that if you are not at the meeting, you were needed elsehwher.</li>
  • 132 132 <ol>
    133 133 <li>Use <b>asynchronous communication</b> when possible (issues and email instead of chat), issues are preferred over email, email is preferred over Slack.</li>
    134 <li>If you notices something that is not documented, unclear or needs to be addressed, please open and issue.</li>
    134 135 <li>If you have to use email please send one email per subject as multiple items in one email will cause delays (have to respond to everything) or misses (forgot one of the items).</li>
    135 136 <li>Always reply to emails, even when no action is needed. This lets the other person know that you received it. A thread is done when there is a single word reply, such as OK, thanks, or done.</li>
    137 <li>If you are not going to make the morning meeting, you can make a note of it on the agenda for that date, or not. Please do not reply "no" to the invite as that results in unnecssary email for the meeting organizer. We trust that if you are not at the meeting, you were needed elsehwher.</li>
    136 138 <li>If you forward an email without other comments please add FYI (for your information) or FYA (for your action).</li>
    137 <li>Emails send to one person (no cc:) and likely not include other people later on don't need a subject line (make the first line descriptive since Gmail uses that).</li>
    139 <li>Emails sent to one person (no cc:) and not likely to include other people at later date don't need a subject line (make the first line descriptive since Gmail uses that).</li>
    138 140 <li>If you use Slack, please use a public channel whenever possible, mention the person you want to reach if it is urgent. This ensures it is easy for other people to chime in, and easy to involve other people, if needed.</li>
    139 141 <li>All company data should be <b>sharable</b> by default. Don't use a local text file but leave comments on an issue. Create Google docs with your company Google Apps account.</li>
    140 142 <li>All our procedures and templates are stored in (mostly public) git repositories instead of Google/Word documents. This makes them easier to find and suggest changes to with the organization and shows our commitment to open collaboration outside the organization.</li>
    141 143 <li>Use FYI and /cc if you want to inform people but it does not require an action, use FYA (for your action) if an action of the recipient is required.</li>
    142 144 <li>If there are materials relevant for a calandar meeting (for example a Google Doc) please add the url to the meeting invite description.</li>
    143 145 <li>If you want to schedule time with a teammember for an outside meeting, create a calendar appointment and invite the teammember only, after they respond yes then invite outside people.</li>
    146 <li>If you receive a calendar invite, accept, suggest another time or decline the appointment within 24 hours of the invite being sent. If you are on vacation, set your calendar to reply with your dates away. If someone card enough to set up a meeting, it is professional to reply.</li>
    • No deadline for dealing with this. Please remove deadline and say that calendar invites warrants a reply like regular emails. Replying yes in a calendar invite means the same as replying 'Yes, I'll be there.' in an email

  • Ernst van Nierop Status changed to closed

    Status changed to closed

  • Please register or sign in to reply
    Loading