Talk to the Character, Not the Actor

Transfers

In theatrical directing, a fundamental technique for giving notes is to address the character rather than the actor. Instead of “You were stiff in that scene,” the director says “Hamlet is holding back here — what is he afraid of?” The redirection is not merely diplomatic; it changes the cognitive frame. The actor stops defending their choices and starts problem-solving on behalf of the character. The note becomes a puzzle to solve rather than a wound to absorb.

Key structural parallels:

• The role is separable from the person — theater operates on the premise that an actor is not the character. This creates a natural buffer: feedback about Hamlet’s behavior is not feedback about the actor’s worth. In code review, the equivalent is “this function is doing too much” rather than “you wrote a bad function.” In management, it is “the project plan has gaps” rather than “you didn’t plan well.” The indirection is structurally identical to the director’s technique.
• Notes are collaborative, not evaluative — a director giving notes is not grading the actor; they are co-creating the performance. The relationship is between two professionals working toward the same outcome. When feedback is framed this way in non-theatrical contexts, it shifts the power dynamic from assessor/assessed to collaborator/ collaborator. The receiver becomes a partner in solving the problem rather than a defendant answering charges.
• The character can fail without the actor failing — if Hamlet’s soliloquy doesn’t land, that is a problem to fix, not a personal failing. This separation allows iteration without accumulating shame. The actor can try a different approach to the same scene without feeling that each failed attempt is a mark against them. Applied to work feedback, this means “the first draft needs rework” is a normal part of the process, not evidence of inadequacy.
• Specificity is built into the form — “talk to the character” forces the director to be specific about what the character is doing wrong in the scene, not to make general pronouncements about the actor’s talent. This structural constraint transfers directly: feedback that addresses the work artifact must name specific problems, while feedback that addresses the person can hide behind vague judgments (“you need to try harder”).

Limits

• Some roles are identity — an actor playing Hamlet can step out of the role at the end of the evening. A surgeon receiving feedback on their bedside manner, a teacher being critiqued on their classroom presence, or a leader being told their management style is damaging cannot easily separate the role from the self. When the “character” is a person’s professional identity practiced over decades, the theatrical separation is a polite fiction that the receiver sees through instantly.
• It requires a recognized director — the technique works because the director has legitimate authority to give notes. In peer contexts — code review among equals, feedback in a flat organization, unsolicited advice from a colleague — there is no asymmetry to support the frame. Without the director role, “talking to the character” can feel patronizing rather than protective.
• It can become avoidance — the indirection that makes this technique humane can also make it evasive. If the actual problem is that someone consistently delivers sloppy work, talking about “the code” or “the deliverable” instead of addressing the pattern directly lets everyone pretend the issue is situational when it is structural. The theatrical frame can become a way of never saying the hard thing.
• Cultural assumptions about directness vary — the technique assumes that indirect feedback is preferable. In cultures or organizations that value blunt honesty (Dutch directness, radical candor frameworks, many engineering cultures), the indirection can read as passive-aggressive or dishonest. The theatrical frame is not universally more humane.

Expressions

• “Critique the code, not the coder” — the software engineering instantiation, standard in code review culture
• “Attack the idea, not the person” — debate and argumentation form
• “I have a note on this scene” — the director’s idiom, which names the work rather than the worker
• “The design isn’t solving the user’s problem yet” — UX feedback that addresses the artifact
• “Let’s look at what the data is telling us” — redirecting from “you were wrong” to “the situation shows us something”

Origin Story

The technique is foundational in Western acting pedagogy, traceable to Stanislavski’s system and refined through decades of American method training. Directors like Elia Kazan and Mike Nichols were famous for giving notes that engaged the actor’s imagination rather than their ego. The principle crossed into management through theater-trained consultants and organizational development practitioners in the 1980s and 1990s, and found independent expression in software engineering’s code review norms, where the separation of code from coder became an explicit cultural value in open-source communities. Kim Scott’s “Radical Candor” (2017) and similar frameworks formalize the same structural move without citing theatrical origins.

References

• Stanislavski, K. An Actor Prepares (1936) — foundational text on the actor/character separation
• Hauser, F. and Reich, R. Notes on Directing (2003) — directing aphorisms that encode this principle
• Scott, K. Radical Candor (2017) — management framework paralleling the theatrical technique