Context for Korean remote teams
Korean remote teams deal with (1) work messengers clashing with KakaoTalk culture, (2) local data residency/security requirements, (3) sustaining productivity without overtime.
Stack
Messenger **JANDI** or **Dooray Messenger** — separated from KakaoTalk. Keep work as work.
Docs / wiki **Dooray Wiki** or **Notion** (when security allows).
Project **Dooray Project** or **Jira/Linear** (engineering).
Video **Zoom** or **Google Meet**. Zoom still wins for large meetings.
Files **Google Drive** or **Dooray Drive**.
Async docs **Loom** + **Notion** — recordings instead of meetings.
Recommended combos
- **Early (5–15)**: Swit or Dooray all-in-one
- **Mid (15–50)**: Slack + Notion + Google Drive + Zoom
- **Engineering-heavy**: GitHub + Linear + Notion + Slack
- **Public / finance**: Dooray on-prem + Microsoft 365
Korean remote ops tips
- Do not spin up a KakaoTalk work channel — keep work messaging in one place
- Async status doc on Friday afternoons
- Standardize new-hire onboarding docs in Dooray/Notion
Pitfalls
- Running everything through a KakaoTalk group: no search, no history
- Meeting overload: check if async tools can replace first
- Making decisions in meetings with no doc trail: fatal for remote
The core is documentation habit + async communication. Tools accelerate it.