Week 6: Credit

Who reads what about a project, how a promotion packet is assembled from public associations, and what the research found when a mixed team's credit was left unassigned.

30 March 2027

Why it worksThe announcement is the one artefact senior people read, and when a team result's source is ambiguous, credit goes by expectation, not contribution.

A project has a dozen contributors and one announcement. The announcement is read by people who will never read the code, the design document or the incident log, and it is read by the people who chair calibration meetings. Whatever it says, the name at the top is the name the reader attaches to the work, and “we” in the body does nothing to change that.

Credit does not fall randomly when it is unassigned. Heilman and Haynes showed in 2005 what happens when a mixed team succeeds and nobody says who did what: readers hand the credit to whoever they already expected to have earned it, and in their studies that was the man, unless the woman’s part was made irrefutably clear. Ambiguity is not neutral. It is filled in with the reader’s prior, and the author line is the cheapest way to remove the ambiguity in your own favour. The person who pays is whoever the reader had already cast as the supporting act.

This is how promotion packets get written: not with lies, but with a consistent, public association between a name and a launch. The engineer who did the hardest part and never wrote a word about it exists in the codebase and nowhere else. The one who wrote the announcement exists in every inbox that matters. The last lecture before the break ends with the question the break is for: which one do you want to be, and what does it cost the other?

Outline

Sources

Teaching team