They Were Playing a Different Game

The email lands at 4:47 p.m. on a Thursday. Your director has CC'd her boss, your skip-level, and two peers you've worked with for years. The subject line reads "Concerns re: Q3 Implementation Timeline," and the body is four paragraphs of careful language that does something very specific: it takes the project you built, the one you scoped, sold internally, and delivered on time, and repositions the entire narrative so that your contribution disappears. Not attacked or criticized; just absent. The framing is that "the team" achieved the early milestones, and that "going forward, leadership alignment" will be needed to keep things on track. Your name appears once, in the CC line, while her name appears in every paragraph that contains a verb.

On the first read, your chest tightens and you notice a small, cold sensation behind your sternum that you recognize from the last time something like this happened, eight months ago, when the same director used almost identical language about a different project. The second time, your face gets hot and your hands go still on the keyboard. Between the second and third paragraph, you stop reading the words and start reading the architecture. Who was included. Who was left off. What "leadership alignment" means when the person writing it has just placed herself between you and the people who approve budgets. The two peers she CC'd are not random; they are the two people most likely to be in the room when next year's project leads are selected. Their presence in this thread is positional.

Part of you wonders whether you're reading too much into it. Maybe it really is just a process email about timelines. That hesitation is worth noticing, because it is exactly the noise that makes these moves so effective: plausible enough to doubt yourself, specific enough to do damage while you're doubting. The skill you are learning, whether you wanted to learn it or not, is how to separate signal from noise while the noise is still loud enough to make you question whether there is a signal at all. What the email does, stripped of its polite framing, is establish a version of events in which your competence is no longer visible to the people who decide what happens next. The disagreement was never about timelines. You know it, she knows it, and the data in the shared tracker confirms it. The timeline language is set dressing for a repositioning move.

Your cursor hovers over Reply All. Your draft folder has three unsent versions of a response from the last time something like this happened. You didn't send any of them. You told yourself you were being strategic, picking your battles, not making it a thing. The real reason you didn't send them sits in a place you don't look at very often: you weren't sure you had the right to push back. Some part of you, the part that learned early to read rooms before speaking, was already running a calculation about what it would cost to be seen as difficult. That calculation finished before your conscious mind even started drafting. It always finishes before you start drafting, and that speed is the problem, because a decision that fast isn't really a decision; it's a reflex, and reflexes, unlike decisions, don't update when circumstances change.

Twelve minutes pass while the email sits there and your coffee gets cold. You open a different browser tab and do work that doesn't matter, and then you come back to the email and read it a third time and notice something you missed: the phrase "as we discussed" in the second paragraph, referencing a conversation that did not happen the way she's describing it. A selective edit. The kind of revision that, if you challenged it, would produce a response like, "Oh, I must have misremembered the specifics, but the general direction is right, isn't it?" And you would say yes, because saying no to a soft reframe in front of an audience feels disproportionate, like swatting a fly with a fire extinguisher.

Tomorrow, when your skip-level references "the concerns Diane raised," the new version of reality will have hardened by one more day. By the following Monday, when someone asks in a planning meeting whose project this originally was, the answer will feel uncertain to people who should know better. They were given a plausible alternative narrative at 4:47 on a Thursday, and nobody corrected it.

Most books would tell you to breathe, to practice mindfulness, to remember that you can't control other people. Or they'd tell you to "manage up," to schedule a meeting, to build a relationship. Fine ideas for a world where the other person is confused, where the problem is a communication gap. The person who wrote that email is precise. Her CC list was curated and the language calibrated. Her timing, late Thursday when you'd have the weekend to stew but not enough business hours to respond without looking reactive, was chosen.

Here is what the email actually did, underneath the polite language. It exploited the gap between what you know to be true and what the organizational record now reflects. The person who sent it gains three things at once: she becomes the point of coordination, which means future decisions flow through her; she creates enough ambiguity about your ownership to weaken your position in the next budget conversation without anyone saying so directly; and she tests your response threshold. That last one matters most. If you do nothing, she now knows the cost of taking from you is zero. She will use that information again.

Credit grabs disguised as "process emails" are among the most common power moves in professional environments because they carry almost no visible aggression. Nothing in that email would survive an HR conversation, and nothing in it would sound alarming if read aloud. If you printed it and showed it to a friend outside your organization, they might squint at it and say, "I mean, it's a little political, but is it really that bad?" You would feel that familiar deflation of trying to explain a wound that doesn't bleed visibly.

The damage never shows up in what anyone said. It shows up in who gets seen as essential and who gets seen as support, and the rearrangement happens so slowly that no single email would ever be enough to point at. I once worked with a director who had absorbed two colleagues' entire portfolios over eighteen months through exactly this kind of incremental reframing, and the mechanics of how she did it are worth pausing on because they illustrate something that abstract descriptions of credit grabs always miss. She never once claimed authorship of a deliverable, never said "I built this" or "my idea." What she did was position herself as the narrator of other people's work, the person who provided "context" when presenting it to leadership, the one who framed the why and the so-what while the people who actually built the thing were reduced to executors of her vision. By the time I described the pattern back to her she was visibly surprised. She experienced herself as someone who stepped up when others dropped the ball. I remember being struck by how genuine her surprise was, and I spent a week afterward thinking about something tangentially related: the way organizational cultures reward narration over creation. The person who explains the work often becomes more visible than the person who did the work, and I am not sure that any amount of individual counterplay can fix an environment where the incentive structure itself treats storytelling as leadership and execution as support. That question is still open for me. What I do know is that the people whose work she absorbed experienced something very different from what she experienced, and that gap between intention and effect is the only thing that matters here. Think of it like someone moving your desk two inches every day: no single move is noticeable, and after three months you're in the hallway. Your work is being absorbed into someone else's narrative while you watch.

Solvable, if you are willing to do three things in a specific order and resist the very strong impulse to do them all at once. Move One is Public Competence. Within 24 hours, while the thread is still active in people's inboxes and still part of their mental model of the conversation, you reply to the same thread, same audience, to add information that makes your role undeniable without ever claiming it directly. The reply looks like this:

"Thanks, Diane. Glad to see the Q3 implementation getting leadership visibility. For context, I've attached the project scope I developed in April and the milestone tracker I've been maintaining. Current status: we're six days ahead of the original timeline. Happy to walk through the details in our next check-in."

The architecture of this reply is doing the arguing for you, and every element is deliberate. No adjectives about your feelings, no language about ownership that could be read as territorial, no "as I'm sure you recall" or any other phrase designed to land a dig while pretending to be collegial. What it contains is documentary evidence placed into the same thread, in front of the same audience, that makes your authorship a matter of record rather than a matter of interpretation. The attachment does the heavy lifting. The phrase "I developed in April" is doing surgical work in that sentence; it establishes origin without making a claim that invites pushback. "I've been maintaining" establishes ongoing ownership. Neither phrase is aggressive, and both are load-bearing. Keep the tone collegial, because tone is what people remember and documents are what hold up over time. A year from now, nobody will recall the warmth of your phrasing, but the scope document with your name on it will still be in the thread. Anyone reading the exchange now has two versions of reality, and one of them has receipts.

Send this while the thread is still active, still part of the conversation's momentum. After 48 hours, you're reopening a closed topic, and the social read shifts from "providing context" to "relitigating." Same thread, Reply All, same audience: do not start a new thread and do not add people. Mirror the original structure exactly, because any change you make to the format becomes the story instead of the content.

Move Two is Private Boundary, and it is the move that determines whether the pattern repeats or stops. After your public reply has landed and been seen, which usually means waiting a day, you send a separate message directly to Diane. Just her. The message sounds like this:

"Hey Diane, wanted to flag something. The email Thursday framed the Q3 work as a team effort that needs leadership alignment going forward. I want to make sure we're on the same page that this project originated from my proposal and I've been the implementation lead throughout. I'm glad to collaborate on next steps, and I'd appreciate it if future communications reflect the project history accurately. Let me know if you want to sync on this."

Most people skip this move entirely, and the skipping is where the pattern gets its oxygen. What you are doing here is naming the behavior directly, in a private channel, without an audience for her to perform to, and without accusation that would give her a reason to escalate. You're not saying she stole credit. You're saying the communication didn't reflect reality, and you'd like it to going forward. The language is specific: "originated from my proposal," "implementation lead," "reflect the project history accurately." These are factual claims she would have to dispute factually, which is much harder than disputing an emotional accusation. People leave this message unsent because it feels aggressive, because the sensation of drawing a line registers in the body as provocation when you're not accustomed to drawing lines. That confusion between boundary-setting and confrontation is worth sitting with rather than letting it make your decisions for you. A boundary removes the ambiguity that both parties have been navigating around, which actually lowers the temperature instead of raising it. After you send this message, Diane knows that you see the pattern. She does not know that you are angry, because you have not given her that information. What she knows is that you are paying attention and that you have language for what is happening. That knowledge alone changes the calculus for her next move.

Move Three is the Professional Mirror, and it only activates if the pattern continues after Moves One and Two. If the credit displacement happens again, you send a follow-up that creates a formal record. This one goes to Diane, CC's your own manager, and sounds like this:

"Diane, I wanted to follow up on our earlier conversation about ensuring communications reflect project history accurately. I've noticed [specific example] in [specific email/meeting], and I want to make sure this is addressed before it creates confusion at the leadership level. I've copied [manager name] for visibility. Appreciate your partnership on keeping the record clear."

"Partnership" frames your escalation as collaborative, which makes it very difficult for her to characterize you as combative without sounding unreasonable herself. The CC to your own manager serves as a witness, and the entire sequence, the public reply followed by the private message followed by this formal escalation, tells a story in which you raised the issue directly and specifically and gave her a chance to correct it before you involved anyone else. If this ever becomes a formal conversation, that sequence is your evidence of good faith.

Those three moves, in that order, with that timing, constitute a counterplay: a specific, bounded response to a specific power move that restores your position without requiring you to become someone you are not. The escalation gradient matters. Move One is public and impersonal, Move Two is personal and private, Move Three is both, but only after the first two have been attempted and the behavior has continued. Each move gives the other person an opportunity to recalibrate, which is important because some credit grabs are entirely unconscious, the product of organizational habits, not individual strategy. You want a response that stops the pattern whether it is intentional or not, without burning a professional relationship that might still be functional. Worth noting: a person who deploys this sequence in every email, on every slight, in every thread where she feels even mildly underrepresented, becomes a tactician rather than a professional, and the difference matters more than the sequence itself.

In almost every workshop I run on this material, someone asks, "What if Diane retaliates?" She might. Move Two, the private boundary, is designed to minimize that risk because it gives her a face-saving exit that no one else witnesses. Some people double down when they feel seen. If that happens, Move Three already has you positioned correctly: you have a documented record of raising the issue directly, privately, and specifically before involving anyone else. Retaliation after that sequence creates a much bigger problem for the person retaliating than it does for you. You cannot eliminate the risk of another person behaving badly. You can make sure that if they do, the record is unambiguous about who tried to resolve it and who escalated it.

Few people get to Move One, and the reasons reveal more about the system than the counterplay itself does. Silence is the most common response, and the one that looks safest from the inside. A person reads the email, feels the sting, and tells herself she will address it later, or that it is not worth the political capital, or that her work speaks for itself. Silence carries the appeal of zero risk: no chance of being seen as petty or difficult. Silence in the face of a credit grab, though, is confirmatory, because organizational memory does not presume innocence or preserve unspoken truths; it remembers the last thing that was said, and when a person lets a reframing stand unchallenged, the reframing becomes the working narrative. She has absorbed a loss and called it maturity, which means the next credit grab will come with even less hesitation because the cost of taking from her has been established at zero.

After silence, emotional pushback is the next most common response: a Reply All that drips with barely contained frustration, that italicizes certain words for emphasis, that includes phrases like "just to be clear" and "as you know." The person sending it believes he is standing up for himself, and on the level of content he may be correct about every factual point. What he is actually doing is handing the other party a gift, because the moment the response carries emotional charge, the conversation shifts from "who did the work" to "why is he so upset about a process email," and he has turned a structural problem into a personality problem. Personality problems are always easier for organizations to dismiss, which means he is now the difficult one while the person who took his credit has become the reasonable one who "just wanted alignment."

Over-explanation and reciprocal CC escalation are the other two common failures, and they are worth naming briefly because they share a root with silence and emotional pushback even though they look different on the surface. The person who writes the long, detailed reply walking through every milestone is operating on the assumption that the problem is informational, that enough facts will make the truth self-evident. Meeting a strategic choice with information is like bringing a dictionary to a negotiation; the thoroughness reads as defensiveness. The person who adds more senior people to the thread, broadening the audience, turning a two-person dynamic into a spectator sport, occasionally wins in the short term but pays a corrosive long-term price: she trains herself to see every interaction through a threat lens, to treat colleagues as potential adversaries, and eventually she has organized her entire professional life around the threat she was trying to escape. She orbits it from a greater distance, which still means the threat is at the center.

Orbiting the threat from a greater distance still means the threat is at the center. Reactive pushback and hyper-tactical vigilance are different postures, but they share a common root: both are governed by the thing they oppose. One collapses inward while the other expands outward, and neither has chosen its own center. The person who goes silent lets the power move define her as someone who doesn't fight back; the person who becomes a permanent counter-strategist lets the power move define her as someone who is always fighting. Both are responses. Neither is self-authored.

Your hands went still on the keyboard at 4:47 on a Thursday, and what stopped them was older than strategy or caution. A long time before this email, before this job, before you learned to read rooms and calibrate your responses to the comfort level of the people around you, you received a lesson. The lesson was not delivered in words, or maybe it was, but the words are less important than the feeling they left behind: when someone takes from you, the correct response is to wonder what you did to invite it.

Shame. Not guilt, which says "I did something wrong," but shame, which says "something is wrong with me." Guilt is about behavior; shame is about identity. The specific form of shame that makes professional counterplay feel impossible is the one that says: if you need to defend your position, your position must not have been solid in the first place. Good work should be self-evident. Having to point at your contributions is proof that they weren't good enough to be obvious. The boundary you need to set becomes evidence of the deficiency you're trying to hide.

This shame narrative didn't come from the workplace. It was installed much earlier, in families where asserting your needs was coded as selfishness, in classrooms where the kid who said "that was my idea" was told not to be a show-off, in cultural contexts where visibility was dangerous and smallness was survival. You brought it with you into your professional life like a piece of furniture you forgot you were carrying because you've been rearranging your house around it for so long. The furniture is invisible to you because every room you've ever lived in has been shaped around it. You don't see the couch; you see the way you walk around the couch.

Consider how specific the instruction was. The lesson was never "don't speak," which would be too blunt, too easy to identify and reject. The instruction was more like, "speak, but only when the cost of silence exceeds the cost of being noticed." That is a sophisticated algorithm, and you've been running it so long that it feels like personality instead of what it actually is: programming. When you describe yourself as someone who doesn't play politics, someone who lets the work speak for itself, you are narrating the output of this algorithm as though it were a choice. It was a survival adaptation that became a professional identity, and the distance between those two things is where the real work lives.

What comes next is less certain, and the uncertainty matters enough to name. I do not know whether the shame you carry is primarily developmental, from early relationships that taught you to minimize yourself, or cultural, from systems that punished visibility in people who look like you, or situational, from a specific event that collapsed your sense of professional safety, or some combination that doesn't fit neatly into any framework I've encountered. I have sat with this question across hundreds of people in dozens of organizations, and I still do not have a clean answer.

What I have observed is that the shame always predates the power move. The person deploying the credit grab did not create your silence; she identified it and sent a test signal into the environment, and your non-response told her exactly what she needed to know about what she could take next time. This is not your fault. Patterns, though, can be rewritten if you are willing to look at the source code, and looking at the source code means understanding that between knowing the counterplay and executing it, the gap is somatic, not informational, and that distinction changes everything about what the practice needs to be. Information lives in the prefrontal cortex; the freeze lives in the nervous system, and the nervous system is faster. By the time you've consciously decided to draft a response, your shoulders have already risen toward your ears, your breathing has already shallowed, and your fingers have already paused in the way that means "not safe." Trying to override that freeze with willpower is like trying to steer a car by yelling at the engine. The engine doesn't understand English; it understands fuel and spark and mechanical advantage. Thinking your way past the shame will not work because thinking is the wrong tool for this particular job, like trying to use a screwdriver to dig a hole: you can do it, technically, but you will be there for a very long time and the result will be shallow. The work is to excavate, which means to feel where the shame lives in your body, to name the specific narrative it runs, and to practice generating a different response under controlled conditions so that when the next 4:47 p.m. email arrives, you have something other than freeze loaded in the chamber. What follows does not require special equipment or training or a weekend retreat; it requires fifteen minutes, a pen, a piece of paper, and a willingness to feel uncomfortable in a way you have been avoiding, possibly for decades.

Do the Shame Excavation alone, in a quiet room, before bed for seven consecutive nights. Seven is not a magic number; shame narratives are stubborn and you will not believe the first three sessions are doing anything. They are.

Recall a specific professional moment when you should have spoken up and didn't, not the most painful one but something medium, a five out of ten. Write it down in two sentences covering the facts: who, what, when. Close your eyes and bring the scene back, not the narrative of it but the sensation. Where in your body did the freeze start: throat, chest, stomach, hands? Name the location out loud, even if it feels strange to say "my chest" to an empty room. That naming is enough.

Ask the sensation a question, and this will feel ridiculous, which is fine: "What are you protecting me from?" Do not answer with your thinking mind. Wait. Let whatever comes up come up, even if it is a memory from when you were eleven, even if it is a sentence that doesn't seem connected to the professional situation at all. Write down what came up in one sentence without editing or analyzing it, and do not decide whether it is rational.

Now write the sentence you would have said in that professional moment if the shame were not present, the sentence your body would not let you say. Forget perfection and forget the ideal political move; write it in your own handwriting, not typed. Read that sentence out loud, once, and pay attention to what happens in your body when you hear your own voice saying the thing you could not say. That micro-shift between freeze and something else, between the familiar constriction and whatever opens up beside it, is the entire point of this practice. Put the paper away and go to sleep. Do it again tomorrow with a different moment, or the same one if it still has charge. After seven nights, try the sentence from Step 5 in a real, low-stakes professional interaction: a meeting where you agree with something but add a slight correction, an email where you name your contribution in a single factual clause. Start with the smallest possible version of the thing you've been withholding, not the big confrontation but the quiet correction that costs almost nothing and changes almost everything.

A caveat worth taking seriously. If you are carrying trauma that makes Step 3 feel destabilizing rather than uncomfortable, please work with a therapist who understands somatic processing. There is no valor in white-knuckling through a practice that activates something your nervous system is not ready to process alone. This practice is for the ordinary, accumulated weight of learning to be small, the kind that doesn't qualify as a diagnosis but absolutely qualifies as a constraint on your professional life. The weight is mundane, which is part of why it's so easy to ignore. It shows up wearing the clothes of professionalism, of temperament, of "I'm just not a confrontational person." Those labels are worth questioning. The inability to confront when confrontation is warranted is a restriction wearing the costume of a personality trait, and restrictions that you didn't choose deserve to be examined.

When you have done both things, when you know the three-move counterplay and you have started excavating the shame that makes Move Two feel like a declaration of war, something quiet happens. The tactical and the internal stop being separate categories, because they never were; you just didn't have the language to see them as one system with two expressions.

Setting a boundary in a direct message stops feeling like aggression because you have located the part of you that was interpreting self-advocacy as violence. That location matters more than any script. Intellectually understanding that boundaries are healthy will not carry you through the moment; your body needs a different experience of what happens when you set one, and the Shame Excavation gives your nervous system exactly that: a low-stakes rehearsal, a chance to say the unsayable sentence out loud in an empty room and notice that the ceiling does not collapse. Each repetition deposits a thin layer of new evidence against the old narrative. Seven nights is not enough to overwrite years of conditioning, but it is enough to create a hesitation in the reflex, a half-second gap between the trigger and the freeze where a different choice can live.

Replying to an email with documentary evidence stops feeling like a risk once you have unhooked the professional act of being visible from the childhood lesson that visibility equals danger. Those two things got fused together a long time ago, and the fusion was so complete that challenging one felt like challenging the other. The excavation practice separates them. Your body responds to visibility at work and visibility in the environment where you first learned to be small with the same constriction, and the practice teaches the nervous system that these are different rooms with different ceilings. A person who can name a credit grab and respond with precision but never examines why she froze the first four times will execute the tactics with a brittleness that breaks under real pressure; without the specific moves, meanwhile, beautiful self-awareness provides no professional ground to stand on.

Neither alone is sufficient, but together they become something different. A way of standing in a room where someone is playing a game you didn't choose, and knowing, in your body and your mind simultaneously, that you do not have to play it and you do not have to leave. That standing is quieter and more durable than dominance or the satisfaction of outmaneuvering someone who tried to diminish you. It is the experience of being ungoverned: free of the person who sent the email and the shame that predates it, free of the reflex that made your hands go still.

You know the email I'm talking about. You know the draft you didn't send, and the feeling in your chest when you decided, without deciding, to let it go. That feeling has information in it. Your hands are still on the keyboard, and the gap between the freeze and the choice is exactly as wide as you are willing to make it.

Here is a question to carry into your next workday: What did I not say today, and what was the feeling underneath the silence?

At the end of that day, place one mark on a line you draw in your head or on the back of a receipt or wherever you keep the things that matter but do not belong in a spreadsheet. On one end: "I spoke when it mattered." On the other: "I went quiet when it cost me." One mark. That is all.

This is not a worksheet, and there is nothing to score. It is a lens, one you carry into the rooms you already walk through, the meetings you already sit in, the emails you already read at 4:47 on a Thursday. Notice what you notice. The noticing is where the work begins, and for now, the noticing is enough.