Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 09:28:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 45

Handbook: Slack communications best practices (#7434)

Browse source
This commit is contained in:
Charlie Chance 2022-08-29 14:17:40 -06:00 committed by GitHub
parent 5f088148e5
commit 3f201f799c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
handbook/people/README.md
View file

@ -200,6 +200,11 @@ We use these prefixes to organize the Fleet Slack:
* ***help-***: for asking for help on specific topics.
* ***at*** or ***fleet-at***: for customer channels.
### Slack communications and best practices
In consideration of our team, Fleet avoids using global tags in channels (i.e. @here, @channel, etc).
1. What about polls? Good question, Fleeties are asked to post their poll in the channel and @mention the teammates they would like to hear from.
2. Why does this matter? Great question! The Fleet [culture](https://fleetdm.com/handbook/company#culture) is pretty simple: think of others, and remember the company [Values](https://fleetdm.com/handbook/company#values).
## Performance feedback
At Fleet, performance feedback is a continuous process. We give feedback (particularly negative) as soon as possible. Most feedback will happen during 1:1 meetings, if not sooner.
@ -547,4 +552,4 @@ Please see [Digital Experience > Slack channels](https://fleetdm.com/handbook/di
<meta name="maintainedBy" value="charlottechance">
<meta name="title" value="🧑‍🚀 People">
<meta name="title" value="🧑‍🚀 People">