The post you read twice
It's a few minutes past eight. You open the team channel and there it is, a thank-you to everyone for getting behind his new plan. The plan is yours. You built it at your kitchen table over three evenings. Fourteen thumbs-up are stacked under his name, and one of them is your boss's.
You have probably already had the conversation. In the car, in the shower, over dinner while your partner nodded. You were sharp and calm and he had no answer. The problem is that none of it happened out loud. The argument in your head costs you sleep. The one in person costs about four minutes.
Here is the idea that makes it easier. Marcus Aurelius, in his private notebook, the Meditations (book 5), describes the best kind of person who does good work. He writes that "he is like a vine which has produced grapes, and seeks for nothing more after it has once produced its proper fruit." The work is the fruit. Nobody can take it from you, and neither can the skill that made it.
That changes what you're walking into. You are not going to get your worth back, because you still have it. You are going to correct the record. That is a smaller job, and it's one you can do.
Marcus lived in a world of emperors and slaves, and he never saw a team channel. But the order he implies still holds. Settle where your worth lives first, then act. A man who acts from a grudge sounds bitter. A man who acts from a settled place sounds calm, and he's harder to argue with.
Epictetus, who was born a slave and later taught in Greece, adds a second piece. Your duties come from your role. If you supervise a team, part of your job is making sure the people above you understand that team's work. So speaking up may not be vanity. It may be part of the job.
A third voice helps with tone. Benjamin Franklin wrote in his Autobiography that he trained himself to stop stating opinions as flat certainties. He used softer openers, along the lines of it appears to me. You are not softening the facts here. You are skipping the accusation about what's in his head. Stick to what you saw.
How to choose a line
You do not need all 22. Pick one from each group, and start with the first line in each if you're unsure. Say them out loud once before you go, in the car or the shower. Have the talk in private, standing up, and keep it under five minutes. Don't do it by chat, and don't do it with an audience.
Add their name in the box and it's filled into the lines that use it.
To open it
Pick a quiet moment and a private spot. You're asking for a few minutes, not staging a confrontation.
Hey, got five minutes? It's nothing huge. I'd just rather talk than type.
It's low-key and honest about the size of the thing. It also moves the talk off the channel, where everyone can see it, and onto two voices. Most tension eases once that happens.
Can we grab the corner by the coffee machine? It's about the post you put up Monday.
It tells him the topic up front, so he isn't ambushed. Epictetus would call this keeping to your role: you came to deal with the work, not to win.
I'd rather say this to you than around you.
This is the quiet part of fairness. You came to him first, before anyone above him, and that matters later if the problem comes back.
I'll keep it short.
It signals that you're not about to give a speech. A short talk is easier to stay calm through, for both of you.
To say the hard thing
Facts first. Leave out his motives.
The update you posted called it your plan. I built that plan, with my team. You were in the meeting where I walked through it.
Everything in it can be checked. There's no adjective and no accusation, just what happened. That's the kind of plain account that is hard to argue with.
I'm not guessing at why. I'm telling you how it looked from where I sit.
It follows Franklin's habit of not stating your read of someone's mind as a fact. You can't prove his intent, and you don't need to.
My name wasn't on it, and neither were the two guys who ran it on the floor.
Naming your team shows you're speaking for the work, not only for yourself. A supervisor is responsible for his team being understood correctly, and Epictetus would call that a duty of the role.
I figure it might have been a slip.
This gives him an easy way out, and it costs you nothing. If it was a slip, he fixes it. If it wasn't, he now knows you noticed.
To ask for what you want
Don't stop at the complaint. Say exactly what you want to happen next.
I'd like it corrected in the channel today. One line is enough.
It's specific, small and doable. A request that has a clear yes-or-no answer gets a better result than a general gripe.
From here on, can we agree before either of us presents the other's work?
You are fixing the process, not just the one incident. It sets the edge of the playground without making him your enemy.
If you want to present it, great. Just say it's mine, and I'll do the same for you.
It offers fairness both ways. You're not hoarding the work. You're asking that the credit follow the work.
If he brushes it off or gets defensive
Stay level. You don't need to win the argument. You need the correction.
I hear that you meant it as a team thing. The team includes the people who did the work, and they weren't named.
You accept his stated intent without giving up your point. It's hard to argue with, because it uses his own words.
We don't have to agree on what you meant. I'm asking for the correction.
Arguing about intent never ends. Marcus's gymnasium advice is to watch for the next knock and step aside without hatred. You do that by going back to the request.
I'm not accusing you of anything. I'm telling you what I saw and what I need.
It lowers the heat without dropping the point. When he stops feeling attacked, he usually stops defending.
I can show you the original file and the date, if that helps.
Offering proof calmly shows you have it, and you aren't making threats. People tend to back off when the record is simple and clear.
To leave it on decent terms
You'll still work next to him tomorrow. End the talk so that tomorrow is easier.
Thanks for hearing me out. I appreciate it.
Say it even if the talk was stiff. You're not rewarding him. You're keeping the door open, and Cleanthes in the theater story is a reminder that people can change when you let them.
Saw the fix in the channel. Thanks for turning that around.
A short thank-you shows him that doing the right thing gets noticed and then dropped, not held against him.
Next time, send me a heads-up and I'll get you the numbers so your slide's right.
It makes the better habit easy. You're offering help that protects your credit and his accuracy at once.
If it goes badly, or happens again
This is where you stop talking to him and start talking to the person who can act.
Okay. We see this differently. I'm going to make sure my team's work is documented properly.
You close the talk without a fight. It's a statement about what you'll do, not a threat about what you might do to him.
I'd rather stop here than say something I'll regret. Let's pick it up tomorrow.
It takes a pause before you lose your temper. Seneca's advice on anger, roughly, was to give it time before you act. You keep the high ground by leaving first.
I came to you first. If it happens again, I'll take it to upstairs.
Use it only if you mean it, and put your manager's name in. It's a plain statement of the next step, not a threat. It also shows you're fair, because you went to him before going above him.
Here's the timeline. I raised it with him once already. I'd like your advice on making sure my team's work is credited.
This one is for your manager. It asks for advice instead of a verdict, and it lets the dates speak. Hugh in the book answered, leave it with me. That wasn't satisfying, but it was the right answer.
What not to say
You always do this.
It turns one incident into an argument about his character, and he'll defend his character instead of fixing the post. It's also hard to prove.
Everybody knows it was mine anyway.
It sounds like a bluff, and it draws attention to the audience you wish you had. Stick to what happened and what you want done.
I know exactly what you were doing.
You don't know his intent, and claiming you do invites a fight you can't win. Describe what you saw.
Fine, keep it. See if I care.
This is giving up dressed as calm. It teaches him he can repeat it, and it quietly trains you to stop contributing ideas.
After the conversation
Write it down the same day. Date, what you said, what he said, what he agreed to. Two or three plain sentences, no adjectives, no guesses about what he was thinking. This isn't a grievance file. It's a work file, and you'll be glad you have it if you never need it.
Then give it a day or two. If he said he'd fix the post, watch whether he does. Many people do, a little stiffly. Some get friendlier afterward, because now they know where the edges are. Don't expect an apology, and don't read his coolness as a verdict. You asked for a correction, not for him to like you.
Also make your work visible in the ordinary way. Give a short update in the next meeting. Name the people who helped you. Don't mention him at all. That does more than any correction in a chat thread.
If it goes badly
If he waves you off, or it happens again, you haven't failed. You went to him first, directly and calmly, and that is exactly what makes the next step fair. Take your dated notes to your manager. Lay out the timeline, say you raised it with him once already, and ask for advice on making sure your team's work is credited. Don't call him a liar. Let the facts do that job.
One more thing. If what you're dealing with goes beyond credit, like bullying, harassment, discrimination or threats, this page is the wrong tool. Take it to HR, a union rep if you have one, or an employment lawyer. And if it's affecting your sleep or your health for weeks, talk to a doctor or a counselor. You don't have to carry that alone.
The full method for this situation, including how to settle where your worth lives before you speak, how to keep the record, and when to escalate, is in Stoicism for Difficult Coworkers. It follows one supervisor through a credit-taker, a chronic complainer and a sharp-tongued email writer. It's about forty minutes, and it ends with a plan for your next seven days.
The ideas, decoded
- The Vine
- The idea that good work is its own reward, like fruit on a vine that wants nothing more once it has borne. It comes from Marcus Aurelius, Meditations, book 5. It lets you settle your own worth before you speak.
- The Role Card
- A habit of asking what your job title requires of you in a hard moment, not what you feel like doing. It builds on Epictetus, Handbook 30 and Discourses 2.10, where duties come from the roles we hold.
- Dichotomy of control
- Epictetus's opening point in the Handbook: some things are up to you, such as your judgments and actions, and some aren't, such as other people's behavior. You can't control whether he takes credit. You can control what you say about it.
- The Training Ground
- The book's name for a view from Marcus Aurelius, Meditations, book 6: treat difficult coworkers like sparring partners who sometimes scratch. Watch them, step aside calmly, and don't make them enemies.
- The Fair Witness
- The book's own term for writing down what happened the way a camera and microphone would record it: dates, words, actions, no adjectives, no guessing at motive. It rests on the Stoic emphasis on justice and on judging events without adding to them.
- Stating your read softly
- A habit Benjamin Franklin describes in his Autobiography: giving his view with phrases like it appears to me instead of flat certainty. It's useful when you can see what happened but can't see what he meant.
Questions people ask
Should I say something in the moment, or wait?
If it happens live in a meeting, a short, warm correction works: thanks, that builds on what I said earlier. For the real conversation, wait until you're calm, usually a day or less. Waiting weeks lets resentment pile up, and it tends to come out too big.
What if he's my boss, not a peer?
The same facts apply, but add more care. Ask for a private minute, state what you built, and ask how you can make sure the work is represented correctly in the future. Keep the dated notes either way, and consider HR if it becomes a pattern.
What if I've misread it, and he really did mean it as a team thing?
Then the conversation costs you almost nothing, and you've learned that. The lines here don't accuse him of anything. They ask for a correction, and a decent person will give it.
Should I put this in an email instead?
Start in person if you can, because tone gets lost on a screen and a first email tends to look like a formal complaint. Send a short, friendly follow-up afterward if you want a written record of what you agreed. Keep it to two or three plain sentences.
What if nothing changes?
Then you have a pattern, and you went to him first. That is when you take a short, factual timeline to your manager. If it's more than credit, like harassment, threats or discrimination, go to HR or get outside advice, and don't carry it alone.