Business Chat Etiquette: Your Own Rules for Replies, Mentions, and Channels

チーム運営・人事

Business Chat Etiquette: Your Own Rules for Replies, Mentions, and Channels

New hires who freeze before hitting send in Slack or Teams use the business chat etiquette template to set their own rules for reply times, mentions, and when to call instead of chat. The whiteboard holds the team chat rules, a matrix that picks the channel by urgency and audience size, opening lines for requests, questions, updates, and nudges, a pre-send check, and a KPT retrospective. The task board has four columns - stuck moments, drafting a rule, trying it out, and locked in - and starts with 5 parent tasks and 13 subtasks, from the audit through the two-week review, all not started. Turning one hesitation into one rule at a time means that after two weeks you decide chat or call in three seconds and stop losing minutes in front of the send button.

0 いいね 0 コピー 作者: WeProcess
business chat team communication response times remote work new to the workplace
無料登録してこのテンプレートを使う

無料登録すると、マーケットプレイスからこのテンプレートをコピーして使えます

ホワイトボード プレビュー

プレビュー表示中 Business Chat Etiquette: Your Own Rules for Replies, Mentions, and Channels

ホワイトボード プレビュー

1. Your Team Rules (who, when, and wh... 2. Choosing the Channel (urgency vs. ... Call first, then post Post once to everyone DM it and wait Put it in the channel 3. Opening Lines by Situation (use th... 4. Before You Hit Send (recipients an... 5. Mistakes in How You Split and Group 6. Reading the Room on Emoji Business Chat Eti... How to use: 1. As... Where you are hea... Rules you set Where you got stuck What you learned Where you want to be in two weeksNo more freezing before you send. Pick the channel in three seconds and fill in a template. Confirmed with a senior teammate1. All-hands mentions are for outages and same-day schedule changes only2. Work hours are 9 to 5, and anything later counts as the next business day3. An emoji reaction is a fine substitute for… Still undecided- Does a note to the director go by chat, or does it need email?- Do requests to another team go by DM, channel, or email? What the team actually doesChannel posts come back in about two hours, DMs in twenty minutesRequests with the ask and the deadline on line one come back faster 縦軸: Urgency (top ... A one-to-one item that needs a decision within thirty minutes. Call first, then leave what you agreed in a three-line DM. An item that meets the all-hands rule from section 1. Post it a single time, and keep every update in the same thread. You only need one person to confirm. Assume it will not come back right away, say when you need it by, and switch to other work while you wait. Notes and status updates that people only need to read. Leave it in the channel and skip the individual mentions. Making a request Asking for input Sharing an update Following up Opening line Quick ask - could you review the quote?Anything back by 5 p.m. on the 25th would help. I could use a second opinion. I am torn between option A and option B.Do you have ten minutes today? Sharing for visibility, no reply needed.Here are the decisions from today's call with Acme. Following up on the quote I asked about on the 18th.Even a rough sense of when you can look at it would help. Always include The deadline (date and time)What done looks like (who gets what)A past example to work from The options and the one you favor, with your reasoningWhen you need the decision byHow far you want them to weigh in Whether a reply is needed (say so if it is not)Who actually needs to read itThe date, if there is a deadline The date you first askedYour deadline, and what breaks if it slipsA fallback (tomorrow morning still works) Common mistakes Sending ASAP and nothing else.Nobody knows the deadline, so you end up waiting. Opening with Got a minute? and stopping there.They brace for bad news while they wait. Dropping a link to the notes with no message.Nobody knows what was decided, so nobody opens it. Sending Any update? and nothing else.It reads as blame, and the next ask gets harder. Reread the recipient before you send. When in doubt, go direct If you finish writing after hours, schedule it for the next morning Never put judgments about people in writing. Say it face to face Firing off five one-line messages and five notifications Packing five requests into one long message and getting an answer to the first Continuing a new topic in an old thread so nobody can find it later Pasting a screenshot without saying what to look at Skip them on a first message to a client or a director Matching how many the other person uses is the safest bet A thumbs-up or a check reads more clearly than a face Never add them to an apology or a no 7. Retrospective ... Keep (what to continue) When I cannot answer yet, I reply first with I will come back to you by five Putting the ask and the deadline on line one cut the follow-up questions Problem (what did not work) I talked myself into urgent three times and sent after hours instead of scheduling The pre-send check is the first thing I skip when I am rushed Try (what to test next) Stop DMing other teams and post in their channel instead Cut the check from three items down to one, the recipient
100%

ドラッグで移動・ホイールで拡大縮小

タスクボードの内容

Stuck moments 18件

Audit how you chat
Choose your channel
Set your reply times
Draft your openers
Review in two weeks
List your channels
Log 5 stuck moments
Ask about team norms
Plot your 5 cases
Set the call trigger
Limit @channel use
Post your reply time
Set after-hours rule
Draft a holding line
Template your asks
Add two more openers
Count what stuck
Fix rules that fail

Drafting a rule 0件

Trying it out 0件

Locked in 0件