Split View: 일본어 비즈니스 이메일·Slack 커뮤니케이션 실전 가이드: 경어 사용법부터 실무 템플릿까지

Japanese Business Email & Slack Communication Guide: From Keigo Usage to Practical Templates

• Introduction
• Basic Structure of Japanese Business Emails
  • 7 Essential Email Components
  • Key Principles for Writing Subjects (件名)
  • Recipient Name (宛名) Notation Rules
  • Greeting Selection Table by Situation
• Keigo (敬語) 3 Categories and Practical Usage
  • Overview of the 3 Categories
  • IT Work Essential Verb Keigo Conversion Table
  • Keigo Level Comparison: Email vs Slack
• Situation-Specific Business Email Templates
  • Template 1: Meeting Request Email
  • Template 2: Bug Report Email
  • Template 3: Project Progress Report Email
• Slack Communication Etiquette and Guidelines
  • 5 Basic Principles of Slack Communication
  • Behaviors to Avoid on Slack
• Slack Message Patterns by Situation
  • Pattern 1: Code Review Request
  • Pattern 2: Urgent Incident Sharing
  • Pattern 3: Schedule Coordination
  • Pattern 4: Feature Release Announcement
  • Pattern 5: Work Request Message
• Tone Differences Between Email and Slack
  • Detailed Tone Comparison Table by Channel
  • Email vs Slack Comparison for the Same Situation
• Essential Japanese Expressions for IT Engineers
  • Development Process Related
  • Incident Response Related
  • Meeting/Reporting Related
• Common Mistakes and Corrections
  • Keigo-Related Mistakes
  • Email Structure Mistakes
  • Slack-Related Mistakes
• Operational Checklist
  • Pre-Send Email Checklist
  • Pre-Send Slack Message Checklist
• Failure Cases and Improvements
  • Case 1: Trust Damage from Keigo Misuse
  • Case 2: Excessive Formality on Slack Creating Awkward Team Atmosphere
  • Case 3: Omitting Cause and Response in Bug Report Email
  • Case 4: Relationship Deterioration from Misspelling Someone's Name
• Practical Tips: Channel Selection Criteria
• References
• Conclusion
• Quiz

Introduction

For foreign engineers working at Japanese IT companies, the biggest hurdle is not coding ability but Japanese business communication. Japanese is required in every process -- requesting code reviews, reporting incidents, or coordinating meetings -- and that Japanese comes with its own formal system called keigo (honorific language).

As of 2026, communication channels in the Japanese IT industry are broadly divided into two categories. Business email remains the standard for official correspondence and external communication, while Slack (or Teams, Chatwork) dominates internal real-time collaboration. The problem is that the tone, keigo level, and sentence structure required in these two channels are significantly different.

If you carry the formal style of email directly into Slack, you'll be perceived as stiff and distant. Conversely, if you use Slack's casual tone in email, you'll be seen as lacking professionalism. To build trust at a Japanese workplace, Korean engineers need to accurately distinguish and use the communication codes of these two channels.

This article is a comprehensive guide centered on daily work scenarios for IT engineers, covering writing methods for email and Slack respectively, keigo usage standards, situation-specific practical templates, common mistakes and corrections, and recovery procedures learned from failure cases.

Basic Structure of Japanese Business Emails

Japanese business emails have stricter formatting than Korean or American emails. There are components that are rude to omit, and conventions that feel odd if the order is changed.

7 Essential Email Components

Key Principles for Writing Subjects (件名)

The subject should convey the purpose and urgency at a glance. In Japanese business emails, it is common to indicate the category using brackets (墨付き括弧).

-- Good subject examples --
【ご相談】マイクロサービス移行スケジュールについて
【ご報告】本番環境デプロイ完了のご連絡
【ご依頼】コードレビューのお願い（PR #2847）
【緊急】本番DBレプリケーション障害について

-- Bad subject examples --
お疲れ様です          → Cannot tell the content
ご連絡                → No specificity at all
確認お願いします       → Unclear what needs to be confirmed

Recipient Name (宛名) Notation Rules

In external emails, never abbreviate the company name. Write 株式会社 instead of (株), and avoid double keigo where a title and 様 are used simultaneously.

-- Correct external notation --
株式会社ABCテクノロジー
インフラ部 マネージャー
田中 太郎 様

-- Incorrect notation --
(株)ABCテクノロジー      → Abbreviation not allowed
田中部長様              → Title + 様 is double keigo

-- Internal notation --
インフラ部 田中部長       → Title serves as honorific
開発チーム 佐藤さん       → さん is acceptable between colleagues

Greeting Selection Table by Situation

Keigo (敬語) 3 Categories and Practical Usage

Keigo is the core of Japanese business communication. The same action requires completely different expressions depending on who performs it. Here we organize the verbs most frequently used by IT engineers in email and Slack.

Overview of the 3 Categories

IT Work Essential Verb Keigo Conversion Table

Keigo Level Comparison: Email vs Slack

Even with the same content, the keigo level differs by channel. The table below compares which expressions are natural in email versus Slack when conveying the same intent.

Situation-Specific Business Email Templates

Template 1: Meeting Request Email

This is the most basic format for requesting a meeting with an external client or another department.

件名：【ご相談】API仕様変更に関するお打ち合わせのお願い

株式会社ABCクラウド
プラットフォーム部 マネージャー
山田 太郎 様

いつもお世話になっております。
株式会社XYZテック 開発部の金 英柱(キム・ヨンジュ)でございます。

現在進行中のマイクロサービス連携プロジェクトに関しまして、
API仕様の変更点について直接ご相談させていただきたく、
お打ち合わせのお時間をいただけないでしょうか。

■ ご相談内容
・認証エンドポイントのレスポンス形式変更
・レート制限ポリシーの見直し
・エラーコード体系の統一方針

■ 候補日時（いずれも60分程度）
・3月10日（火）10:00〜12:00
・3月11日（水）14:00〜16:00
・3月12日（木）10:00〜12:00

■ 開催形式
オンライン（Google Meet）を予定しております。

上記日程でご都合が合わない場合は、
別途ご希望の日時をお知らせいただけますと幸いです。

お忙しいところ恐れ入りますが、
何卒よろしくお願い申し上げます。

──────────────────────────
株式会社XYZテック 開発部
金 英柱（キム・ヨンジュ）
TEL: 03-XXXX-XXXX
Email: youngjukim@xyz-tech.co.jp
──────────────────────────

Key Point: It is good manners to suggest at least 3 candidate dates. いただけないでしょうか is a combination of kenjougo + teineigo, politely asking about availability.

Template 2: Bug Report Email

Used when reporting a bug found in the production environment to a client or relevant department. The key is structuring the discovery context, impact scope, and response plan.

件名：【緊急・ご報告】決済APIにおけるタイムアウトエラー発生について

株式会社ABCコマース
システム運用部 部長
鈴木 一郎 様

平素より大変お世話になっております。
株式会社XYZテック 開発部の金 英柱でございます。

本日14時頃より、決済APIにおいてタイムアウトエラーが
断続的に発生しておりますことをご報告申し上げます。

■ 障害概要
・発生日時：2026年3月6日（金）14:00頃〜
・対象システム：決済API v2（/api/v2/payments）
・事象：リクエストの約15%でタイムアウトエラー（HTTP 504）が発生
・影響範囲：エンドユーザーの決済処理遅延

■ 原因（暫定）
データベースコネクションプールの枯渇により、
クエリ実行待ちが発生しているものと推定しております。

■ 対応状況
・14:15 — 障害検知（アラート発報）
・14:20 — 一次調査開始
・14:35 — コネクションプール上限を一時的に引き上げ（暫定対応）
・14:45 — エラー率が正常値に回復

■ 恒久対応方針
・コネクションプール設定の最適化
・スロークエリの特定と改善
・DB接続のヘルスチェック機構の導入

詳細な原因分析レポートは、3月9日（月）までに
別途お送りいたします。

多大なご迷惑をおかけし、深くお詫び申し上げます。
再発防止に向けて万全の対策を講じてまいります。

何卒ご容赦くださいますようお願い申し上げます。

──────────────────────────
株式会社XYZテック 開発部
金 英柱（キム・ヨンジュ）
TEL: 03-XXXX-XXXX / 緊急: 090-XXXX-XXXX
Email: youngjukim@xyz-tech.co.jp
──────────────────────────

Key Point: For incident reports, the timeline format (タイムライン) is the most preferred structure in Japanese companies. When the cause has not been confirmed, use 推定しております (we estimate) to avoid definitive statements.

Template 3: Project Progress Report Email

件名：【ご報告】Kubernetesクラスター移行 3月第1週 進捗報告

インフラ部 佐藤部長

お疲れ様です。開発部の金です。

Kubernetesクラスター移行プロジェクトの
3月第1週の進捗をご報告いたします。

■ 今週の実績
・Staging環境でのHelm Chart移行完了（12サービス中10サービス完了）
・CI/CDパイプラインのArgoCD連携テスト完了
・Istioサービスメッシュの設定検証完了

■ 残タスク
・認証サービスとログ集約サービスの移行（来週予定）
・本番環境への段階的切り替え計画の策定

■ 課題・リスク
・認証サービスのgRPC通信がIstio経由で
  レイテンシ増加（+20ms）を確認。
  チューニングで解決可能と判断しておりますが、
  解決しない場合はサイドカー構成の変更を検討します。

■ 来週の予定
・3/10：残り2サービスのHelm Chart移行
・3/12：負荷テスト実施
・3/14：本番切替計画レビュー会議

ご不明な点がございましたら、
お気軽にお申し付けください。

よろしくお願いいたします。

金 英柱

Key Point: Internal emails can be more concise than external ones. Start with お疲れ様です and the signature can be just a name. However, since this is a report to a superior, maintain the です・ます style.

Slack Communication Etiquette and Guidelines

Slack is more casual than email, but in Japanese companies, certain manners are still required. Foreign engineers especially need to be careful about both "being overly formal" and "being too casual."

5 Basic Principles of Slack Communication

1. Write the purpose on the first line -- The standard is to write the greeting and purpose on a single line, like お疲れ様です。〇〇の件でご相談です。. Long greetings like in email disrupt the flow.

2. Actively use threads -- To keep channels clean, discussions should always take place in threads. Continuing conversations in the channel without threads causes other members to lose track.

3. Minimize mention scope -- Use @channel or @here only for genuinely urgent situations. Unnecessary mass mentions are frowned upon in Japanese workplaces too.

4. Utilize emoji reactions -- Reactions indicating acknowledgment (eye emoji, check emoji, etc.) are very important in Slack culture. In Japanese teams too, reactions are understood as "I've read it."

5. When messages get long, use Notion or document links instead -- If a Slack message exceeds 10 lines, it is better for readability to create a separate document and share the link.

Behaviors to Avoid on Slack

Slack Message Patterns by Situation

Pattern 1: Code Review Request

お疲れ様です。
PR #2847 のレビューをお願いできますでしょうか。

変更概要：認証ミドルウェアのリファクタリング
変更ファイル数：5ファイル
影響範囲：/api/v2/auth 配下のエンドポイント

特に見ていただきたい点：
・JWTトークン検証ロジックの分離が適切か
・エラーハンドリングの網羅性

PRリンク：https://github.com/xyz-tech/api/pull/2847
お手すきの際にご確認いただけると助かります!

Pattern 2: Urgent Incident Sharing

@channel
【障害発生】本番環境 決済API

発生時刻：14:00頃
事象：タイムアウトエラー（504）が断続的に発生中
影響：エンドユーザーの決済処理に遅延発生
対応状況：調査中

担当：金
次回アップデート：14:30を目処にこのスレッドで共有します

詳細はスレッドにて更新します。

Pattern 3: Schedule Coordination

お疲れ様です。
来週のスプリントプランニングの日程調整です。

候補：
A) 3/10（火）10:00-11:00
B) 3/10（火）14:00-15:00
C) 3/11（水）10:00-11:00

リアクションで希望をお知らせください。
A → :one:  B → :two:  C → :three:

Pattern 4: Feature Release Announcement

@here
【リリース完了】ユーザーダッシュボード v2.3.0

本日15:00にリリースを完了しました。

主な変更点：
・ダッシュボードのレスポンス速度改善（平均40%向上）
・CSV一括エクスポート機能の追加
・グラフ表示のダークモード対応

リリースノート：[Notion リンク]
不具合を発見された場合は #bug-report チャンネルまで
お知らせください。

Pattern 5: Work Request Message

@tanaka-san
お疲れ様です。

Terraform構成の件でご相談があります。
新しいEKSクラスターのモジュール定義について、
既存のVPCモジュールとの連携部分で
アドバイスをいただけないでしょうか。

具体的には：
・サブネット構成のベストプラクティス
・セキュリティグループの設計方針

お手すきの際で構いませんので、
15分ほどお時間いただけると助かります。

Tone Differences Between Email and Slack

Email and Slack, even in the same Japanese language, have distinctly different tones and formats. Without understanding this difference, you'll create a sense of incongruity -- "too stiff for Slack" or "too casual for email."

Detailed Tone Comparison Table by Channel

Email vs Slack Comparison for the Same Situation

Situation: Deployment Completion Report

Email version:

件名：【ご報告】v2.3.0 リリース完了のご連絡

お疲れ様です。開発部の金です。

本日15時に、ユーザーダッシュボード v2.3.0のリリースを
完了いたしましたのでご報告申し上げます。

主な変更内容は下記の通りです。

1. ダッシュボードのレスポンス速度改善（平均40%向上）
2. CSV一括エクスポート機能の追加
3. グラフ表示のダークモード対応

現時点で異常は確認されておりません。
引き続きモニタリングを実施してまいります。

ご不明な点がございましたら、お気軽にお申し付けください。
よろしくお願いいたします。

Slack version:

@here
【リリース完了】ダッシュボード v2.3.0

本日15:00にリリース完了しました!
・レスポンス改善（平均40%向上）
・CSVエクスポート追加
・ダークモード対応

モニタリング中。何かあればこのスレッドまで。

Essential Japanese Expressions for IT Engineers

Here we organize work-related Japanese expressions that IT engineers use daily, categorized by topic.

Development Process Related

Incident Response Related

Meeting/Reporting Related

Common Mistakes and Corrections

Here we organize and correct common mistakes that Korean IT engineers tend to make in Japanese business communication, categorized by type.

Keigo-Related Mistakes

Email Structure Mistakes

Slack-Related Mistakes

Operational Checklist

This is a checklist for maintaining the quality of Japanese business communication. Always check before sending emails or Slack messages.

Pre-Send Email Checklist

• Does the subject include a bracket category and specific purpose
• Is the 宛名 (recipient name) accurate (no company name abbreviations, no double keigo)
• Have you used the appropriate greeting (external/internal/first contact distinction)
• Have you stated your self-introduction (affiliation + name)
• Is the conclusion placed at the beginning of the body (結論ファースト)
• Have you not confused kenjougo and sonkeigo
• Are specific dates, numbers, and deadlines stated
• Is a closing greeting included
• Is the signature block complete (company, department, name, contact info)
• Does the CC include necessary people while excluding unnecessary ones
• If there are attachments, have you mentioned them in the body
• Are there no typos or name misspellings (getting the other person's name wrong is critical)

Pre-Send Slack Message Checklist

• Are you posting in the appropriate channel (public channel instead of DM)
• Are you mentioning only the necessary people (not abusing @channel)
• Is the purpose clearly stated on the first line
• Have you separated long content into threads
• Have you adjusted the tone with emoji/reactions
• If there is code or logs, have you used code blocks
• Have you used expressions appropriate for the urgency level

Failure Cases and Improvements

Case 1: Trust Damage from Keigo Misuse

Situation: Korean engineer A sent an incident report email to a client using ご確認してください (incorrect kenjougo application) and 了解しました (expression for equals). The client's contact person told A's supervisor that "there seems to be a problem with their Japanese manners."

Root Cause Analysis: ご~する is a kenjougo pattern that should only be used for one's own actions, but it was used when requesting confirmation from the other party. Also, 了解しました is perceived as inappropriate for superiors or clients in Japanese business conventions.

Improvement Methods:

• Correct ご確認してください to ご確認いただけますでしょうか
• Correct 了解しました to 承知いたしました
• Establish a habit of always checking the keigo checklist before sending emails
• For the first 3 months, request review of important emails from supervisors or Japanese colleagues before sending

Case 2: Excessive Formality on Slack Creating Awkward Team Atmosphere

Situation: Engineer B, early in their employment, started every Slack message with いつもお世話になっております。〇〇株式会社の金でございます。 in a long email-style format. Team members felt distance, wondering "Why is the tone like an external email when we're on the same team?"

Root Cause Analysis: The fundamental cause was not recognizing the tone difference between email and Slack. Since they learned mainly formal styles during Japanese language study, they applied the same level of formality across all channels.

Improvement Methods:

• On Slack, start with お疲れ様です。 or jump directly into the topic
• Observe and match the Slack message tone of other Japanese team members
• Actively use emoji reactions to maintain a light communication feel
• When unsure about formality level, directly ask the team lead "Slackのトーンはどのくらいがいいですか"

Case 3: Omitting Cause and Response in Bug Report Email

Situation: When a production incident occurred, engineer C sent only a one-line report saying "障害が発生しました." The client immediately fired back questions: "影響範囲は? 原因は? いつ復旧しますか?" The additional back-and-forth took time and increased the client's distrust.

Root Cause Analysis: The essential 5W1H (what, when, where, why, how, impact scope) for incident reports was missing. In Japanese business especially, the 4-step structure of "problem occurrence, cause, response status, recovery timeline" is fundamental.

Improvement Methods:

• Prepare incident report templates in advance for immediate use
• Include at minimum: "time of occurrence, event, impact scope, current response status, next update time"
• Even if the cause is unknown, promise the next contact time with 原因調査中です。〇時を目処に続報をお送りします
• Maintain an incident report runbook within the team so that anyone can send a report of consistent quality

Case 4: Relationship Deterioration from Misspelling Someone's Name

Situation: Engineer D entered the wrong kanji for a client's name, sending 斉藤 instead of 斎藤. Once was forgiven as a mistake, but making the same error twice in a row caused the client to express displeasure.

Root Cause Analysis: Japanese names can have various kanji representations even with the same pronunciation (渡辺/渡邉/渡部, 斉藤/斎藤/齋藤/齊藤, etc.). The cause was not accurately verifying the kanji written on the other person's signature or business card.

Improvement Methods:

• Copy-paste the kanji from the other person's email signature
• Register accurate kanji in your contact management system
• If unsure, add a line in the first email: お名前の表記に誤りがございましたら、ご指摘いただけますと幸いです
• If you get the name wrong, immediately send a correction email: 先ほどのメールにて、お名前の表記を誤っておりました。大変失礼いたしました。

Practical Tips: Channel Selection Criteria

Here is a reference for when you're unsure whether to send something via email or Slack.

References

For those who want to learn more deeply about Japanese business communication, please refer to the resources below.

1. Slack Official Blog - ビジネスチャットのエチケット -- Official guide on business chat etiquette on Slack
2. ゴンドラ - ビジネスメールマガジン -- Explanation of basic business email structure and expressions
3. サイボウズ メールワイズ - ビジネスメールのコラム -- Common mistakes and corrections when writing emails
4. アナグラム - Slackガイドライン -- Example of corporate Slack operation guidelines
5. CHINTAI JOURNAL - ビジネスメールまとめ -- Collection of business email templates by situation
6. 文化庁 - 敬語の指針 -- Agency for Cultural Affairs official keigo guidelines (basis for keigo 3-category classification)
7. 日本ビジネスメール協会 -- Survey reports and educational materials from the Japan Business Email Association

Conclusion

Japanese business communication is not complete with just "correct keigo." You must simultaneously judge three axes: tone adjustment based on channel (email vs Slack), structure selection based on situation (reporting/requesting/apologizing/sharing), and keigo level adjustment based on the other party (external/supervisor/colleague).

At first, all of this may feel overwhelming, but through repeated practice it becomes second nature. If you customize the templates presented in this article to your own work situations and develop the habit of verifying with the checklist before every send, you should be able to communicate at a level on par with Japanese colleagues within 6 months.

The most important principle is one: It's okay to make mistakes, just maintain a polite attitude. Even if you cannot command keigo perfectly, if your consideration for the other person comes through, you can earn sufficient trust in the Japanese business environment. Conversely, even perfect keigo is useless if the attitude is arrogant. The heart comes before the form, and the expressions and structures covered in this article are the means to accurately convey that heart.

Quiz