Case Study 2 — Who Takes the Blame: A Seat, a Mistake, and the Duties of Rank
A composite case illustrating the reciprocal half of hierarchy — what the senior owes the junior — across a Japanese and, briefly, an Indian setting. Names and details are illustrative.
The situation
Rachel is a capable British team lead, newly running a joint venture's operations out of Tokyo. She manages a small Japanese team, and she's determined to be fair, transparent, and modern: credit goes to whoever earned it, accountability lands on whoever made the mistake. "Own your work" is her motto — the good and the bad.
Two things happen in her first month.
First, a seating moment. At a formal dinner with a client, Rachel — running late, flustered — drops into the first open chair, which happens to be the seat facing the door, at the head of the table. Her most senior Japanese colleague, Mr. Tanaka, quietly takes a lesser seat near the entrance without a word. Rachel notices nothing.
Second, a mistake. A junior engineer, Sato, makes an error that causes a visible problem for the client — a missed spec that delays a delivery. In the review meeting, with the client present, Rachel does what she considers scrupulously fair and honest: she names the cause precisely. "The delay came from a spec that Sato missed. We've corrected it and put a check in place." She's careful not to blame the team unfairly — she pins it exactly where it factually belongs, on the individual responsible. By her values, this is integrity: no scapegoating the group, no hiding, just the clean truth.
Sato's face stays composed. Mr. Tanaka's face stays composed. The meeting ends. And something goes cold in the team that Rachel can feel but can't name. Over the following weeks, problems stop surfacing early; people go quiet in reviews; Sato, once eager, becomes careful and closed. Rachel is baffled — I was completely fair. I didn't even blame the team.
She had violated, twice, the single thing a senior is most obligated to do.
The 'before': how it felt through Rachel's operating system
Through Rachel's home-culture software, she behaved with real integrity. Taking the open chair was efficient — a seat's a seat, and fussing over placement is exactly the stuffy hierarchy she wants no part of. And naming Sato as the source of the error was fair and honest: you don't smear the whole team for one person's slip, and you don't bury mistakes. In her world, a leader who publicly pinned an individual's error precisely — while protecting the innocent majority — is being principled, even kind to the team as a whole. Accountability is individual; truth is truth; sunlight is the best disinfectant.
Every value she acted on is genuinely a value. And in this setting, two of them caused real damage.
The 'after': what was actually happening
Rachel had inverted the duties of her own rank — and didn't know rank had duties.
- The seat wasn't a convenience; it was a position she was obligated to manage. The seat facing the door, at the head, is the kamiza — the seat of honor, which in a client dinner belongs to the most senior guest or host, not to whoever sits down first. By grabbing it thoughtlessly, Rachel took a place of status she should have offered or been guided to, and forced senior Mr. Tanaka into a lower seat. He absorbed it silently (causing a scene would cost everyone face), but the room registered that the new boss either didn't know or didn't care where rank sits. (Chapter 6; more on Japan in Chapter 28.)
- Publicly naming Sato wasn't "fair" — it was a failure of the senior's core duty. This is the heart of it. In a Japanese hierarchy, a senior's most important obligation downward is to protect the junior's face, especially in public, and to absorb blame upward rather than pushing it down. The honorable senior, in that review, would have said something like "we missed a spec; I should have caught it in review; we've corrected it" — taking the hit onto the team and onto herself, shielding Sato entirely. By pinning the error on Sato by name, in front of the client, Rachel did the precise opposite of what a good senior does: she spent her subordinate's face to display her own honesty. (Chapters 3, 6.)
- The team's chill was rational. Once the team saw that the boss would name an individual's error in public, the lesson landed instantly: it is not safe to make a mistake here, and the senior will not cover for us. So mistakes went underground, early warnings dried up, and candor died. Rachel hadn't enforced accountability; she'd taught her team to hide — the same hidden cost we saw in Chapter 1's "radical candor" case, here flowing from a broken duty of rank rather than from blunt delivery.
What Rachel experienced as integrity, the team experienced as a senior who took the privileges of her position (the head seat, the authority) while refusing its obligations (protecting and covering her juniors). By the culture's own standards, that's not a fair leader. It's a bad senior.
The deeper point
Here is the reciprocal half of the chapter, dramatized. Westerners worry about hierarchy crushing the junior. But the more common Western mistake, when running a hierarchical team, is the opposite: enjoying the deference and authority that flow upward while never performing the protection, blame-absorption, and care that are supposed to flow downward. Rachel didn't fail by being too hierarchical. She failed by taking only the top half of the hierarchy — the status — and skipping the bottom half — the duty. In a Confucian-influenced system, that's the cardinal sin of a senior. The seat of honor is not a perk; it's a promise.
And — never flatten — the same principle wears different clothes elsewhere. Briefly: had Sato been Arjun on an Indian team, the dynamics would rhyme but not match. Indian professional culture is also steeply hierarchical and intensely attentive to a senior's duty to protect juniors — a respected Indian manager is often expected to be almost paternal, advocating for "their people," absorbing blame upward, looking after careers and even families. Publicly singling out Arjun's error before a client would similarly cost him dignity and signal a senior who doesn't shield her own. But the texture differs: the forms of deference, the role of the extended in-group, the way the correction would later be handled privately — all carry an Indian, not Japanese, accent (Chapter 30). The lesson ("the senior owes the junior protection") is shared; the performance of it is culture-specific. There is no generic "Asian" way to be a good senior — there is a Japanese way and an Indian way, related but distinct.
The better approach
Rachel doesn't need to abandon accountability or stop caring about truth — burying real problems would fail too, and her instinct against scapegoating the whole team was sound. What she needs is to learn that in a hierarchical culture, the senior's job is to take blame down and pass credit down, and to handle correction where it doesn't cost face:
- Manage the seat. Don't grab a chair; hover, let the host or protocol place people, and steer the seat of honor to the senior guest. If unsure, ask quietly or follow others' lead. (Cheap to do, costly to skip.)
- In public: absorb, don't assign. Take responsibility onto yourself and the team — "we missed this, I should have caught it, here's the fix." Protect the individual completely in front of clients and the group.
- In private: correct, with care. The actual conversation with Sato happens one-on-one, calmly, framed around learning and the future, not blame and the past — "let's make sure this doesn't recur; what would help you catch it next time?"
- Perform the duties of rank, not just the privileges. Advocate for your juniors, cover for them publicly, pass credit downward, take heat upward. That is what earns a hierarchical team's loyalty — and it converts your authority from positional to genuine.
Scripts: - (in the client review) "We had a process gap that let a spec slip — that's on us, and ultimately on me as lead. We've corrected it and added a check so it can't recur." - (privately, to Sato, afterward) "I covered it in the room because that's my job, not yours to carry in front of the client. Now just between us — walk me through what happened, and let's build something so it can't bite us again. No blame. I've got you."
Within a quarter, leaders who flip from "assign blame publicly" to "absorb blame publicly, correct privately, credit downward" typically watch the early warnings and candor come back — because the team has learned the thing that makes a hierarchical group function: our senior protects us.
Discussion questions
- Rachel thought naming Sato was the fair, honest thing to do. Explain precisely how the same act read as a failure of duty inside her team's operating system.
- The chapter says "the seat of honor is not a perk; it's a promise." What is the senior promising — and which half of that promise did Rachel keep, and which did she break?
- This case and the "radical candor" case in Chapter 1 both end with a team that learns to hide. Compare the two root causes — blunt delivery versus broken duty-of-rank. How are they different roads to the same cliff?
- Where is the line between a senior "protecting" a junior and a senior "covering up" a real problem that ought to be surfaced? How would you protect Sato's face and fix the actual process?
- Think of a time you were the senior/leader in a Western setting. Did you instinctively absorb blame downward and pass credit down — or the reverse? What would change if you treated that as a duty of your position rather than an optional nicety?
Portfolio link. Add a section to your Portfolio titled "The duties of my rank." Wherever you are senior to someone — at work, in a family, as a mentor — list three protections you owe downward in your chosen culture's terms (e.g., shield from public blame, pass credit down, advocate for their advancement, take heat upward). Beside each, note how you'd perform it concretely. Hierarchy only earns loyalty when the senior pays the bill; this page is where you commit to paying yours.