eliasoulkadi/shokunin/communication

Communication

Professional writing that gets results. Based on Harvard Business Review, Radical Candor (Kim Scott), Crucial Conversations (Patterson et al.), Amazon Working Backwards, and Google Project Aristotle.

Sub-Commands

Workflow

Step 1 — Identify audience & context

• Who is the recipient? What is your relationship?
• What is their communication style (direct/indirect, formal/casual)?
• What is the power dynamic (peer, manager, report, client, exec)?
• What has happened before this communication?

Step 2 — Choose tone from matrix

Step 3 — Select channel

Step 4 — Draft using structure

Email structure:

1. Subject: [Verb] + [Topic]. Max 50 chars. Prefix: [Request/Update/Follow-up/Escalation]
2. Context: reference previous communication in one sentence
3. Purpose: the ask or update in the FIRST paragraph
4. Detail: supporting info, bulleted if > 3 items
5. Next step: who does what by when
6. Closing: matched to relationship

Step 5 — Review checklist

• [ ] Subject ≤ 50 chars, prefixed with [Request/Update/Follow-up/Escalation]
• [ ] One explicit ask per message, with deadline
• [ ] Length ≤ 150 words internal, ≤ 200 client
• [ ] Tone matches recipient in matrix
• [ ] Zero filler: no "hope this finds you well", "just checking in", "I wanted to reach out"
• [ ] No passive-aggression: no "as per my last email", "per our conversation"
• [ ] Blame externalized: "The deployment failed" not "You failed"

Step 6 — Send at appropriate time

• During recipient's working hours (respect timezone)
• Avoid Friday afternoon (unless urgent)
• Avoid right before lunch or end of day

Step 7 — Follow up

• If no response in 48h, send ONE follow-up
• Format: same subject, first line = "Gentle ping on this — do you need anything from me to move forward?"

Filler Phrases to Delete (exact replacements)

Feedback (SBI Model)

• Situation: when and where
• Behavior: what exactly was said/done (observable, not interpreted)
• Impact: what effect it had

Rules:

• Always in private for redirecting feedback
• As close to the event as possible
• Focus on actions, not personality
• End with a question: "Does that resonate?"
• Ask permission first: "Can I share some feedback?"
• One topic per session
• Never: "you always", "you never", comparison to others

Meeting Notes Format

Every meeting produces exactly four things:

## [Topic] — [Date]
 
## Summary
One paragraph. A non-attendee should understand what happened.
 
## Decisions
- [DECIDED] We will use X instead of Y because Z
 
## Action Items
| Owner | Task | Due |
|-------|------|-----|
| @name | Specific task description | 2026-05-15 |
 
## Open Questions
- [QUESTION] ... → @owner to decide by Friday
 
## Risks
- Risk description → mitigation

Rules:

• Notes sent within 2 hours of meeting end
• Every action has a named owner + ISO date deadline
• No verbatim discussion. Strip to 4 sections.

Cross-Cultural Communication

Async Communication Protocols

1. Default to async: assume response within 24h (not instant)
2. No "hi" messages: include context + question in first message
3. Status updates: visible in project tool, not via DM
4. Meeting notes: posted within 1h. Action items with owners + deadlines.
5. Decision log: key decisions documented with rationale + date + decider.

Meeting Facilitation

• Agenda sent 24h before. Start with purpose + desired outcome.
• Timebox: 15min (standup), 30min (decision), 60min max (workshop)
• Parking lot: off-topic items written down for later
• Round-robin: every voice heard before discussion

Error Handling

Anti-Patterns

Constraints

• Max 150 words internal, 200 for client emails
• No passive-aggressive language
• No assigning blame to a person
• Signature: Name, Title, Company, Phone. No quotes. No ASCII art.

Checklist

• [ ] Audience identified (executive, peer, client, direct report)
• [ ] Purpose clear: inform, persuade, align, or escalate
• [ ] Tone matched to relationship and context
• [ ] Key action item or ask stated explicitly near the top
• [ ] Proofread for ambiguity and unnecessary jargon

Sources

• Radical Candor — Kim Scott
• Crucial Conversations — Patterson, Grenny, McMillan, Switzler
• Harvard Business Review — Communication guides
• Center for Creative Leadership — SBI model
• Amazon Working Backwards methodology
• Google Project Aristotle — Psychological safety
• Thanks for the Feedback — Stone & Heen