目次
- 1 1) “Hai” covers everything from Yes to Maybe
- 2 2) Silence can mean dissent or deep thought
- 3 3) Meetings are “read-outs of decisions already made,” and still fill the entire slot
- 4 4) Hō-Ren-Sō (report–inform–consult) isn’t an amulet—it’s insurance
- 5 5) Titles determine where you sit—and the upper seat is far from the door
- 6 6) The business card is your first ID check
- 7 7) “The room’s air” can overwrite the agenda
- 8 8) Smells and sounds are landmines (“smell harassment,” etc.)
- 9 9) Time is managed by the slot (even if we don’t need all of it)
- 10 10) Office drinks are optional—but culturally not trivial
- 11 11) The right answer to bad news: buy it early
- 12 12) Keep a euphemism dictionary that preserves “wa” (harmony)
- 13 Japan-specific “institutional background” that props up these habits
- 14 Mini-scripts you can use tomorrow
- 15 Bottom line (sting + substance)
1) “Hai” covers everything from Yes to Maybe
How it shows up
- “We’ll consider it positively.” → usually pending.
- “I’ll share this internally.” → now begins the meeting → nemawashi (pre-alignment) → ringi (circulation for approval) journey.
Why (grounds)
- Japan is a high-context culture: meaning lives in subtext and atmosphere. In formal settings (tatemae), real positions (honne) are softened; conclusions are made outside the room and the meeting becomes a confirmation ritual.
- With very high uncertainty-avoidance, on-the-spot commitments feel risky. An ambiguous “yes” buys time to align offline (UAI scores Japan high).
How to handle
- In notes/minutes, lock the “yes” into next actions: who/what/by-when—so it becomes an actual commitment, not just “I heard you.”
2) Silence can mean dissent or deep thought
How it shows up
- After a new proposal, the room goes quiet. That may mean “not bad,” but it also often means no one is on board yet.
Why (grounds)
- Interrupting can be impolite; non-verbal cues and the “ma” (meaningful pause) carry intent. Silence itself is information.
How to handle
- Don’t say “silence means agreement.” Call on individuals (or use chat/docs) to surface positions explicitly.
3) Meetings are “read-outs of decisions already made,” and still fill the entire slot
How it shows up
- Purpose of the meeting: not to debate, but to announce decisions formed beforehand—yet the full scheduled time is still consumed.
Why (grounds)
- Nemawashi/ringi create consensus before the meeting; the meeting guarantees the form.
- Parkinson’s Law: work expands to fill the time available—meetings included.
How to handle
- Put “finish early if done” into the agenda: “If the three decisions are confirmed, we adjourn immediately.”
4) Hō-Ren-Sō (report–inform–consult) isn’t an amulet—it’s insurance
How it shows up
- The worse the status, the earlier and more granular the update. Paradoxically, your evaluation doesn’t drop—often rises.
Why (grounds)
- Hō-Ren-Sō is the operating system: early escalation turns an individual issue into an organizational response, minimizing damage.
How to handle
- Share facts first, then options (A/B). Keep recipients tight; blanket CC’ing everyone backfires.
5) Titles determine where you sit—and the upper seat is far from the door
How it shows up
- In a conference room, the seat farthest from the door is the upper seat. With clients, guests take the upper seat. In taxis, behind the driver is the upper seat.
Why (grounds)
- Visualizing hierarchy via seating reduces role clashes. It’s institutionalized across business-manner guides.
How to handle
- The host assigns seats up front. Even for internal meetings, a simple seating diagram on first contact kills confusion.
6) The business card is your first ID check
How it shows up
- Exchange with both hands, confirm name, title, firm. Don’t turn it into a scribble pad in front of them.
Why (grounds)
- The card represents not just the person but their group affiliation (uchi/soto) and status—which also drives polite language choice.
How to handle
- Right after exchange, repeat the affiliation, title, and reading; arrange cards on the table in the seating order to keep talk smooth.
7) “The room’s air” can overwrite the agenda
How it shows up
- A subtle mood at the top of the meeting silently sets the depth of debate and the “do-not-touch” lines.
Why (grounds)
- High-context + honne/tatemae: in formal space, the right not to say is strong; non-verbal cues steer the session.
How to handle
- Read the air before the meeting via 1-on-1 nemawashi. In the meeting, lock only issues and decision criteria; run a short, focused race.
8) Smells and sounds are landmines (“smell harassment,” etc.)
How it shows up
- Strong perfume, lingering lunch smells, unmuted typing or background noise—rarely told to your face, but it hurts your stock.
Why (grounds)
- Workplace harassment guidelines frame behavior that harms the work environment as addressable; strong scents/noise are commonly managed in that spirit—even if not defined by statute.
How to handle
- Stick to no/low scent. Online: hard-mute, manage mic/keyboard noise.
9) Time is managed by the slot (even if we don’t need all of it)
How it shows up
- A 45-minute topic still consumes the full 60-minute slot. Five minutes from the end, we read back decisions.
Why (grounds)
- Meetings guarantee form and shared context. With high uncertainty-avoidance, confirmation beats “leaving buffer”.
- And yes, Parkinson’s Law again—work swells to fill time.
How to handle
- For each time box, show deliverables (decision/owner/deadline). Declare “adjourn when done” at the start.
10) Office drinks are optional—but culturally not trivial
How it shows up
- “Nommunication” (communication over drinks) is weaker than before, but still useful for repairing relationships—never mandatory.
Why (grounds)
- Anti-power-harassment duties make coercion a clear no-go.
- Surveys show declining interest in mandatory year-end parties; opt-outs are normal.
How to handle
- Don’t rely on off-hours events. Build 1-on-1s and feedback rituals instead. If you do host one: truly optional, clarify costs covered.
11) The right answer to bad news: buy it early
How it shows up
- The moment something breaks, Hō-Ren-Sō it—attach impact and a temporary fix. Your reputation can improve, not decline.
Why (grounds)
- The system’s design is organizational response via early sharing. Meetings tend to be for announcing; firefighting runs offstage.
How to handle
- One mail/message: Facts → Impact → Options A/B → Recommendation → Next update time.
12) Keep a euphemism dictionary that preserves “wa” (harmony)
How it shows up (translations)
- “That’s difficult.” = nearly No.
- “Let me take it back.” = here begins nemawashi.
- “We’ll consider it positively.” = keep expectations modest.
Why (grounds)
- With honne/tatemae and high context, direct “No” has high relationship cost. Preserving face is often the priority, hence roundabout phrasing.
How to handle
- For important items, agree in advance on options and decision criteria, and make binary triggers for Yes/No explicit.
Japan-specific “institutional background” that props up these habits
- Nemawashi / ringi / hanko formalize the flow “pre-agree → announce in the meeting.” The ringi sheet, stamped along the way, leaves an audit trail of responsibility.
- Legal caps on overtime (baseline 45 hours/month, 360/year; special cases up to 720/year with multi-month averages, etc.) push organizations from “solve by more hours” to “standardize the process.” The formalization of meetings is a side effect.
Mini-scripts you can use tomorrow
Declare a short meeting (and mean it)
“Pre-alignment is done; we’re approving. If the three decisions hold, we’ll adjourn five minutes early.”
Translating an ambiguous Yes
Them: “We’ll consider it positively.”
You: “Thanks. Could you share the decision criteria and the decision date up front?”
Buying bad news early
“Fact: major defect in testing. Impact: up to 3-day slip. Options: A (spec change) / B (rollback). Recommend: A. I’ll report back in two hours.”
Bottom line (sting + substance)
- Sting: Decisions are often finished before the meeting; the meeting is an assurance ritual. “Yes” isn’t always Yes, and silence speaks.
- Substance: This isn’t laziness with ambiguity; it’s managing uncertainty. By formalizing the visible bits (seating, cards, time) and translating fuzzy bits into text, options, deadlines, and process, you protect relationships and outcomes.
最近のコメント