Case Study 2 — The Manager Who Thought Everything Was Fine

A composite case illustrating how honne, tatemae, and the after-hours channel shape a Japanese workplace. Names and details are illustrative.

The situation

Tom is a capable American product manager, newly posted to his company's Tokyo office to lead a team of nine on a tight, high-visibility software launch. He arrives determined to do it right: he's read about Japanese politeness, he bows, he's careful with business cards, he's warm and approachable. By his own account, things are going beautifully. In meetings, the team is attentive and agreeable. When he proposes a plan, heads nod. When he asks, "Any concerns? Does this timeline work for everyone?" he gets calm, affirmative answers — "Yes, we can do it," "It's fine," "Understood." Morale, he reports to his boss back home, is excellent.

He also has one running frustration. Twice a week, the team goes out together after work — to an izakaya, a casual pub — and they always invite him. Tom usually begs off. He's jet-lagged, he has calls with headquarters in the evening, and frankly, after a full day of careful cross-cultural effort, he wants to decompress alone. He figures the after-work outings are just socializing, and that the real work is what happens at the desk. He'd rather protect his energy for that.

Then the launch slips. Badly. A dependency that "was fine" turns out to have been a known risk for weeks. A junior engineer who'd said "we can do it" had, it emerges, serious doubts the whole time. When the post-mortem reveals that several people saw this coming and said nothing, Tom is genuinely baffled, and a little hurt. Why didn't anyone tell me? I asked — repeatedly — if there were concerns. They all said it was fine.

The 'before': how it felt through Tom's operating system

Through Tom's home-culture software, his read was airtight. He had done everything a good, open manager should. He explicitly, repeatedly invited concerns — "any pushback? does this work?" — and got clear yeses. In his world, that closes the loop: if you ask people directly whether there's a problem and they say no, then either there's no problem or they've chosen not to raise it, and either way you've done your part. An engaged team speaks up. Silence and agreement mean assent.

And the after-work drinking? That was optional socializing — pleasant, but not the job. The job was the work product, and a focused manager protects his time for that. Skipping the izakaya to take a headquarters call seemed not just acceptable but responsible.

Every piece of that reasoning is fluent — in the wrong language.

The 'after': what was actually happening

Tom's team had not been hiding the ball out of malice or disengagement. They had been behaving with complete cultural correctness, by rules Tom couldn't see:

• Their agreement was tatemae, not honne. "Yes, we can do it" and "it's fine," said in a group meeting to a senior person, were the harmonious public surface (tatemae). They preserved wa and avoided the discomfort of openly contradicting the boss or admitting a problem in front of peers. The honne — the real, worried opinion — existed, but the meeting was precisely the wrong place for it. (See the chapter's honne/tatemae section.)
• Open dissent in the group would disturb harmony and risk face. Voicing "actually, this timeline is unrealistic and the dependency is dangerous" in front of everyone could embarrass the colleague responsible for that dependency, contradict the boss publicly, and mark the speaker as the nail that sticks up. The culturally skilled move is not to blurt the concern in the meeting.
• "Any concerns?" into the group was the wrong instrument. A vague, open invitation to a whole room is almost designed to collect tatemae. The honne lives in private, one-on-one, and — critically — after hours.
• The after-work outings were the missing channel. The nomikai/izakaya evenings were not idle socializing; they were the sanctioned space where the daytime hierarchy and tatemae relax and honne is allowed to breathe. That is exactly where, a few drinks in, the worried junior engineer would have felt able to say, "Tom-san, between us, I'm not sure about this dependency…" By declining every invitation, Tom had unknowingly shut off the one channel through which the truth he was asking for could actually reach him.

So Tom spent weeks asking for honne in the one setting that produces only tatemae, while skipping the one setting that produces honne. He had been collecting the harmonious surface and mistaking it for the whole story — and then was blindsided when the surface and the depths turned out to differ.

The deeper point

Tom's failure was not ignorance of his team's competence or commitment — they were committed; they were trying to do right by him. It happened a level below that. He took the polite, agreeable surface (tatemae) as the complete truth, because his operating system holds an ideal in which a sincere "it's fine" means it's fine. He never learned that in Japan the harmonious public answer and the private real opinion are two different registers, both legitimate, living in two different places — and that the manager's job is to build the relationship and the private channels where honne can finally surface.

And notice the second, easily-missed error: Tom treated relationship-building as separate from the work — a nice-to-have he could skip when busy. In a culture where trust precedes candor and honne flows through informal, after-hours bonds, that "optional" socializing was the work. The thing he cut to protect his productivity was the very thing his productivity depended on.

The better approach

Tom doesn't need to become Japanese, drink heavily, or stop asking for input. He needs to change where and how he listens — and to recognize the after-hours channel as part of his job. Concretely:

• Stop trusting the group "yes." Treat agreement in a formal meeting as a provisional, harmonious surface, not a final answer. Build in private follow-ups.
• Gather honne one-on-one. Instead of "any concerns?" to the room, talk to people individually and specifically: "Sato-san, you know this dependency better than anyone — what worries you about it, even slightly?" A private, named, face-safe invitation is the instrument that surfaces real opinion.
• Show up after hours. Go to the izakaya — not every time, but regularly. Stay a while, relax, let the guard down a little. He needn't drink much; presence and informality are what open the channel. This is where the junior engineer's quiet doubt would have reached him in time.
• Do his nemawashi. Before locking a plan, walk the proposal around privately, person by person, so concerns surface before the timeline is set rather than in the post-mortem.
• Make it psychologically safe to deliver bad news. Visibly reward, never punish, the person who quietly flags a risk — so the calculation shifts from "raising this disturbs harmony" to "Tom-san genuinely wants to know early."

Scripts Tom could use: - (one-on-one, privately) "I'd really value your honest view — just between us. What's the part of this plan you're least comfortable with?" - (at the izakaya, relaxed) "Off the clock and off the record — what would you change about how we're running this launch?" - (building safety) "If anyone ever sees a risk, I want to hear it early, and I'll only ever thank you for it — never hold it against you."

Managers who learn this typically find their "agreeable, no-concerns" team was full of sharp, accurate, unspoken assessments all along — and that the fix was not to demand candor in the meeting but to build the private, after-hours trust where candor was always going to live.

Discussion questions

1. Tom "did everything right" by his own lights and still got blindsided. What belief about the meaning of "yes" did he mistake for a universal fact?
2. The case argues the after-work outings were the work. Make that argument as strongly as you can to a skeptical Western manager who "doesn't do forced socializing."
3. Honne and tatemae are framed as two legitimate registers, not honesty vs. lying. How does that reframing change how Tom should feel about his team — and about his own polite "it's fine" moments?
4. What's the difference between Tom's group "any concerns?" and a private, named "Sato-san, what worries you?" Why does one collect tatemae and the other unlock honne?
5. Where in your own work do you take a smooth, agreeable surface as the whole truth — and what private channel could surface the honne underneath it?

Portfolio link. In your Cultural Intelligence Portfolio, add a note under "Behaviors I might misread": a calm, agreeable group "yes" may be tatemae — the harmonious surface, not the real opinion; the honne lives one-on-one and after hours. Then write the one private, named question you'll use to draw out a real concern, and a commitment to treat informal relationship time as part of the job, not a distraction from it.