Give Credit Away
On this page
Credit multiplies when you give it and shrinks when you hoard it — attribution generosity is the cheapest compounding asset in an org.
Engineers guard credit instinctively, and not irrationally. Credit is the promo currency. The Cookie Licking: Claiming Work Without Doing It world genuinely contains credit thieves — people who reword your design in a bigger meeting, or absorb "we" into "I" when relaying results upward. So the reflex is to clutch: mention your name early, restate your ownership, make sure nobody walks off with your contribution. The reflex is understandable. For a secure contributor, it is also economically backwards.
The counterintuitive economics
Here is the asymmetry most engineers miss: the org rarely subtracts from you what you attribute to others. When you say "Priya's design made this possible" or "this was Wei's idea, I just implemented it," nobody in the room updates your contribution downward by the amount you handed to Priya or Wei. Credit is not conserved like mass. Attribution given publicly is close to free for the giver — and extremely valuable to the receiver, because it arrived from a third party, which is the only form of credit that fully counts.
So the trade is: you spend approximately nothing, the recipient gains a lot, and — this is the part that feels wrong until you watch it happen — your own standing goes up. Listeners run a simple inference: only people with surplus give away surplus. Someone confidently distributing credit must have done enough themselves to afford the generosity. The credit-giver is presumed senior. That is the paradox at the center of this note: giving credit RAISES your apparent contribution. Hoarding it signals scarcity — that you're scraping together every scrap, which reads as junior regardless of your actual level.
The caveat "for a secure contributor" matters. This works when your own work exists in the record (see the boundary section below). It is not a substitute for doing the work; it is a multiplier on work already done.
Mechanics
It's a zero-cost deposit in the favor bank. Public credit is one of the few favors you can do that costs nothing and can't be declined. Priya now owes you nothing formally — and remembers it anyway. This is The Favor Bank and Reciprocity — Go Positive, Go First in their purest form: you moved first, at zero cost, and the ledger opened in your favor.
People fight to work with credit-givers. Word travels fast about who shares wins and who absorbs them. Engineers maneuver to join the projects of known credit-givers and quietly avoid credit-takers. The downstream effects compound: your projects staff faster with better people, your peer feedback glows, your "would work with again" scores climb — the exact signals promo committees and skip-levels weight most. This is a load-bearing case of Easy to Work With Beats Brilliant.
Credit-hoarding is detected, and the detection is expensive. The people whose credit was taken KNOW. They talk — to each other, to their managers, along the The Shadow Org Chart, which carries reputation far faster than any formal channel. One detected theft costs more than years of attribution generosity earned, because it recategorizes you: you stop being "someone who did a thing" and become "someone who takes things." That label is nearly impossible to shed.
The manager's-eye view. A manager watching you accurately credit teammates concludes something specific: you see the team clearly. You know who did what, you track contribution honestly, and you're not distorted by self-interest. That is leadership evidence — it's most of what a lead's job is — and you're producing it for free, in public, every time you attribute accurately.
The boundary — not self-erasure
Generosity is not the same as disappearing. Your contributions still need to exist in the record, because The Work Doesn't Speak for Itself. The brag doc states YOUR part precisely: "I implemented the retry layer and cut p99 by 40%; the sharding design was Wei's." Giving credit for their part and claiming yours are compatible — and both required. A record that only credits others is not humility; it's a missing record, and at review time a missing record is indistinguishable from missing work.
And when YOUR credit is taken, correct it — promptly, lightly, in the room: "Glad the approach landed — that's the design I proposed in the March doc; here's what we added since." Notice the shape: factual, cheerful, anchored to a dated artifact, immediately forward-looking. Not bitter, not litigated afterward in DMs. This is the same idea-provenance defense from Cookie Licking: Claiming Work Without Doing It: dated docs, sent emails, and meeting notes make correction a citation instead of an accusation. Being a credit-giver does not obligate you to be a credit donor to thieves; in fact your generosity elsewhere makes your correction land harder, because everyone knows you don't grasp.
Practices
- Name names in demos, launch emails, and postmortems. "Shipped X" becomes "Shipped X — Priya's schema design, Wei's migration tooling, Sam's load testing." Specific beats general: name the contribution, not just the person.
- Credit upward accurately too. A senior engineer's unblocking or a manager's air cover was real help — say so. It isn't flattery if it's true and specific, and seniors notice who acknowledges help versus who pretends self-sufficiency.
- When relaying a team win to leadership, itemize contributors. The relayer controls attribution — whoever writes the summary email owns the credit map. That is author's framing power; use it honestly. It's also exactly where credit theft usually happens, so doing it right is conspicuous.
- Correct taken credit in the room, lightly, with artifacts. Same day, same channel, citation not accusation.
- Keep your brag doc precise in parallel. Every credit you give away should coexist with a clear dated record of your own part.
- Build the habit BEFORE seniority. It's cheapest early — as a junior you have little credit at stake and everything to gain from the abundance signal. Waiting until you're senior means paying full price for a habit you could have gotten at a discount.
Diagnostic test
In your last demo, launch email, or postmortem, count the names that weren't yours — if the answer is zero, you're hoarding a currency that only grows when spent.
Share this article