How to ask for credit without sounding petty

Ask for credit by attaching it to a decision that has not happened yet. "Could you add me to the author line before this goes out Thursday?" is a request somebody can act on without thinking about it. "I did most of that work" is a verdict you are asking them to agree with, and now they have to weigh your feelings instead of fixing a line of text.

Most people send neither version. They read the summary, notice their name is missing, and decide the whole thing is beneath them. Then they think about it for two weeks.

Credit lives in whatever summary got written last

Credit at work is tracked by whoever wrote the most recent summary. That person was busy, and they wrote the version they could remember.

That changes what the ask is. You are reporting a gap in a document someone wrote from memory at the end of a long day. Most of the time, that is exactly what happened, which is why the framing holds up.

The rarer case exists too. Some people do collect other people's work on purpose. You will not tell the two apart from the outside, and it does not matter for your first message, because the first message is identical either way. What changes is what you do if it happens twice.

The wounded sentence is the part that costs you

Cut every sentence that describes your effort. Effort is the part that reads as petty, and it is also the part nobody can verify.

Compare two versions. "I put three weeks into that migration and it would be nice if that showed up somewhere" makes the reader form an opinion about your three weeks. "The migration section came out of my work in March, could you list me there too?" asks for an edit. One is a claim about fairness. The other is a correction to a document.

The tells that sink these messages are consistent:

• Any mention of how hard or how long something was.
• The word "actually" turns a correction into a contradiction.
• A preamble apologizing for raising it tells the reader this matters more to you than it should.
• Naming who got credit instead of naming the work.

That last one matters most. The second you write that someone else got listed and you did not, the message becomes a comparison between two people, and the reader has to take a side in something you did not mean to start.

Ask the person who can change it, privately

Send it to whoever owns the document, in a direct message. Keep it short. Public asks for credit almost never work, because you are handing your colleague a choice between fixing a line and losing face in front of the team, and most people protect the face.

Ask once. One clear ask is a correction. The same ask a second time, phrased more carefully, is a campaign, and the campaign is what people remember. If the first ask is ignored, that tells you something about the person, and no amount of rewording changes it. If a second piece of work goes the same way, stop sending corrections. That is the point where you stop relying on somebody else's summary and start writing your own.

Timing helps more than tone here. Ask while the doc is still a draft, before the announcement has left the channel. The same words get a quiet edit while the file is open and a defensive paragraph once it has gone out. That clock also runs on raising a problem before it becomes your fault.

When the record is already public, correct forward

Ask to be right in the next one rather than asking someone to amend what people have already read.

Reissuing a sent announcement to add a name is a bigger favor than it sounds. It means admitting a mistake to an audience, and the correction gets less attention than the original did.

Forward is cheaper and works better:

• "For the follow-up post, can we list both of us on the data section?"
• "When this comes up at the review, I would like to walk through the part I built."
• "Can you add me to the owners field on the project page, so questions come to the right person?"

The owners-field version disguises nothing. It is a real operational reason, and it puts your name somewhere permanent instead of somewhere ceremonial.

Get close to whoever writes it down

By the time anybody decides who did what, they are reading a document rather than remembering a year. The durable fix for credit is to be near that document while it is being written.

I found this from the other side. I make Unvent, and the record of what happened each month is the changelog I keep. Reading old entries back, I could watch the wording shape what I believed about my own work. The weeks I described precisely still feel like weeks. The ones I filed under "various fixes" are gone from my memory of that year entirely.

If a summary can erase your work from your own memory, it will do the same job in somebody else's. The mechanics of writing a good one are in recaps that make decisions stick.

Three sentences, sent to one person

The message that works is three sentences long with no throat-clearing, sent to the one person who can make the edit.

"Quick one on the metrics deck. The retention chart and the notes under it came out of the analysis I ran for the last review, can you put me on the byline there? I can send you the source file if that saves time."

The offer at the end does specific work. It makes saying yes cheaper than saying no, because the fix becomes a copy and paste instead of a memory exercise. Give someone a reason to want the edit and it stops being a question about fairness.

One thing I would push back on is the advice to let credit go because the work is its own reward. Sometimes that is right. Often it is a way of avoiding a two-line message, and the cost lands later, when somebody is listing who did what and your name is not in the file. Being easy to work with is valuable. Being invisible is not the same thing, and the people who conflate the two tend to find out slowly.