Most case studies are illustrations. They show the tool working. They don't show how it works — the depth at which the practitioner is operating, the altitude the subject is at, the moment the bilateral matches and what made the matching possible, the container moves that held the conversation open, the somatic precursors that arrived before the cortex could name what was happening.
Five Scenes does both. Each scene is rendered first as canon-voice narrative — the somatic detail, the half-second catches, the recursive questions, the recognition moments. Then it is taken apart architecturally: the Psychology of each step (what happened, what the research says about why, what the FTS lens reads), and the Diamond Walk (the hinge, the climb, the drill, the catch, the cascade, the container moves) — culminating in a Bilateral Lens table that tracks subject altitude and practitioner depth at every moment of the conversation.
The five configurations cover the rank-axis. A practitioner reading a subordinate. A practitioner reading a peer. A practitioner reading a senior. And the inversion — a junior associate reading a senior partner, holding the practitioner role across two years of climate-reading before bringing one question. The instrument is rank-portable. If the climate is held.
Then the negative case. Same setup as the inverted bilateral. Same junior, same senior, same question. But the leader seals the frame instead of holding it. The page shows what that does — to the question, to the room, to every conversation that follows.
An ERP six months behind. A practitioner who has the data, the velocity charts, the architecture memo. He walks in prepared. The CFO walks him from M1 (status delivery) up the ladder until the question lands that the prepared answers can't reach: What did you commit to when you took this on? The fluency breaks. The body knows before the cortex does. The recursive why arrives.
Twelve percent adoption against a sixty percent target. Three hypotheses — onboarding friction, navigation, value proposition. Every hypothesis locates the problem in the customer. None locates it in the feature. What's the version of this story where the feature is the problem? The question is structurally different. The wall becomes visible.
A senior leader walked through the same architectural drill that produced the catches in the first two scenes — but at the altitude where the protected M5 has organizational consequences across multiple teams. The practitioner operates at depth; the subject moves from M1/R1 up the ladder under recursive questioning. The catch lands where competence and identity fuse at the leadership tier.
The bilateral instrument applied where the protected M5 is built around client relationships — the version of self organized by the long arc of an account. The drill exposes the architecture by which the relationship's preservation organized the framing of the work delivered. The catch lands at the place where account stewardship and identity become indistinguishable.
Maya, four years in, has watched the senior partner David across two years and four prior feedback moments. The pattern is reliable enough that she is willing to test it. She brings one question — about an engagement that quietly collapsed three months after delivery — and David walks the diamond on himself, in front of her, in front of the room. This is the keystone configuration. The instrument operating in both directions.
The debrief is in its second hour. Three months after delivery, the CEO of a mid-cap healthcare client has quietly walked away from the strategic pivot the engagement was structured to support. The deck is in a drawer. The relationship is intact, technically. The next renewal is in six months and no one has called.
David is naming what he sees. Change-fatigue at the client. A CFO transition mid-project. Organizational politics he saw too late. Each is real. Together they form a coherent story. The story is missing one position.
Maya has been listening. The pattern she sees is that every explanation David has offered for the adoption gap is located in the client. She has noticed this kind of completeness-shaped-by-omission before; she's watched David catch it in others.
She has watched him for two years. She has seen four moments where someone brought him a hard observation — Chen on the operating model, Theresa on the org-design work, Marcus when he pushed back on the framework, a junior partner who told him his strategy memo had a hole. Each time he stayed. Each time he asked the second question. Each time the person who brought it was not punished — not in the moment, not in the months after. The pattern is reliable enough that she is willing to test it.
The room is quiet. David doesn't move. His face doesn't change. His shoulders don't shift. There is no quick shake of the head. He doesn't fill the silence.
He asks, "When did you first notice it?"
"Week four. The kickoff workshop where we wrote the question of the engagement on the whiteboard. The CEO led that session. The question they wrote was framed around the pivot. We took the framing."
"Why didn't you say it then?"
"I wasn't sure. And I didn't know if I had standing to question the framing the CEO had set."
"Why didn't you say it in week eight?"
"I think I'd taken on the same framing by then."
David sits with this. Then, slowly:
David: "What was I protecting?" The question isn't to Maya. Maya doesn't answer.
David: "I was protecting the relationship. We've worked with their CFO for nine years. The pivot was the new CEO's. If I'd surfaced that the pivot was wrong, we'd have ended the engagement in week six and not had a next engagement. I told myself we were doing the responsible thing — giving them what they asked for, well. I was preserving the account."
He looks at Maya. "And what I was preserving the account for was the next renewal cycle. The firm's incentive structure. The partner-track conversation that includes 'maintained the relationship.' I didn't run that out loud either."
Then: "How long have you been holding that observation?"
"Since week four."
"Eight months."
David nods. Not in the way that says that's appropriate. In the way that says I see what you did, and I see what I made you wait through.
| Moment | Subject (David) | Practitioner (Maya) | Bilateral |
|---|---|---|---|
| Climate read across 2 years | M5 unaware, R4 unexamined | R4 reading David's behavior history | Practitioner deeper |
| Setup walk-through | M1–M3, R1–R2 | M5, R4 | Practitioner deeper |
| Maya's question | M3 transitioning, somatic onset | M5, R4–R5 | Closing |
| "What was I protecting?" | M5 emerging, R4 visible | M5, R5 | Matched |
| Naming the firm's incentive structure | M6 named, R4–R5 visible | M5, R5 | Subject momentarily deeper |
| Meta-recognition of the eight-month wait | R5 in the relationship | R5 (her own wait visible to her) | Matched at depth |
What the table shows: Maya enters at M5/R4 and holds there. David moves from M1/R1 to M6/R5 across the conversation. There is one moment where the subject is briefly deeper than the practitioner — when David names the firm's incentive structure. Maya brought him to the room. He walked further into it than she pointed. This is what bilateral excavation looks like when it lands: the practitioner opens the door, the subject walks through it further than the door's location suggested they would. The climate makes the further walk possible.
Same conference room. Same Maya. Same David. Same question, almost word for word. But the climate Maya was reading wasn't there — or it was bounded in a way she couldn't see from the four prior moments she had observed. The negative variant is rendered with the same somatic depth as the climate version, beat by beat, so the difference becomes structurally legible.
Doesn't move. Face doesn't change. Shoulders don't shift. Doesn't fill the silence. Asks for the data (when did you first notice it?) rather than for justification. Runs the recursive why through himself, out loud. Names Maya's eight-month wait as information about him. Pauses the debrief rather than performing recovery.
The container is visible because the absent gestures — the bristle, the deflection, the rank deployment, the category rename — are conspicuous by their absence to anyone who has been watching for them.
The sure arrives a beat too quick. Shoulders rise a quarter inch. Hands retract from the table. Eyes shift past Maya to the principal, then back. "That's not what we were hired to do." When Maya tries to clarify, her voice comes out lower than she meant it. The hedge — "I'm not saying we should have undermined their commitment" — is the body recognizing that the floor of safety just got revoked.
"Maya." The use of her name is positioning. Then: "That's not a judgment call you get to make at your level." Then the category rename — "Let's keep this kind of analysis for projects where we have the latitude." Then the closing-move-disguised-as-thank-you: "I appreciate the thought." Said in the register one uses to end a conversation, not to begin a different one.
What the negative case shows. The same bilateral asymmetry that made the climate version succeed is the asymmetry that, in the negative version, makes the disclosure impossible to land. Maya is the practitioner — she has done the climate work, she holds the depth, she brings the precise question. But the subject is sealing the frame faster than she can hold it open. Depth asymmetry doesn't help because the subject is preventing the bilateral contact.
The decisive structural feature: the work the climate version did was Maya's reading, not Maya's construction. The climate that allowed the climate version to happen was something Maya identified. The climate that prevents the negative version is something David enacts. The leader is the gatekeeper of climate. The practitioner can do everything right and the conversation can still fail if the climate isn't held by the person with the formal authority to seal the frame.
And it shows what the climate is, by showing what its absence does. Climate is not the leader's feeling about receiving feedback. Climate is the leader's consistent prior behavior, reliably enough that a junior person can do the R4 inference and bet their career on the inference being accurate. The four moments Maya watched were not moments David remembered as climate-building. They were moments Maya remembered as climate-building. The leader builds the climate without knowing what they're building. The room knows.
When the leader takes it as attack, the room finds out what the climate actually was. Not what the leader thought it was. What it was.
Five Scenes sits adjacent to the Field Manual on the corpus spectrum. The Field Manual teaches the discipline as it operates in project rooms. Five Scenes shows the discipline working, with the architecture made visible at every beat. Each scene is a Field Manual chapter rendered at full somatic depth and then taken apart with the rigor of the Dissertation's psychological mechanisms layer.
For sophisticated buyers and procurement leaders: this is the artifact that answers "show me what it actually looks like." For academic readers in adult development, organizational behavior, or psychological safety: this is the artifact where the framework's mechanisms are demonstrated in operation across rank-axes. For working practitioners: this is where the instrument's operation becomes legible, where the gap between reading about bilateral practice and recognizing it in a room is closed.
The five-scene structure produces an insight that no single scene can produce alone: that the rank-axis is portable, that climate is the precondition for portability, and that the cost shape of failure changes when the subject is the leader rather than the subordinate. See the Library for the other volumes in the corpus.