Skip to content

Commit

Permalink
Remove kickoff reference
Browse files Browse the repository at this point in the history
  • Loading branch information
therebbie committed Aug 28, 2022
1 parent af7b6e7 commit 8d9e940
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/_company/communication.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ While asynchronous communication is strongly preferred, there are scenarios in w
## In practice

1. Aim to respond to mentions other than FYIs within 3 business days. If you are unable to fulfill a specific request during that time, respond to the mention and indicate when you'll have an answer.
1. If you're behind on responding to notifications and expect to miss a deadline for any new mentions (until you're caught up), please inform the team in the Kickoff, and ask that urgent requests be sent to you via Slack DM and include the issue/MR link.
1. If you're behind on responding to notifications and expect to miss a deadline for any new mentions (until you're caught up), please inform the team via Slack in `#internal-chatter` or the relevant department channel, and ask that urgent requests be sent to you via Slack DM including the relevant issue/PR link.
1. Use direct language when communicating. If you want someone to take action, directly tell them what's required, and when you need an answer, and whether there is urgency. Also indicate whether something is a "must have" or "nice to have" when asking for collaboration.
1. Over-communication can be appropriate. You can mention someone in an issue, but we all know that sometimes we can miss something, so if a request has stagnated, you can send someone a direct message as a gentle reminder. If you need something urgently, you can also send a Slack message to request that something is prioritized.

Expand Down

0 comments on commit 8d9e940

Please sign in to comment.