# A Release Lead's Output Is Mostly Subtraction ## Claim The release lead's principal contribution is deciding what does not ship, so the role's productivity is invisible in the release notes by construction. <!-- atomicity: 1 idea ✓ --> ## Evidence **Source**: [[3. Resources/Readwise/Articles/WordPress 7.1 Release Lead Decision Log|WordPress 7.1 Release Lead Decision Log]] — Anne McCarthy, passing the principle to the 7.1 squad after the "On this day" widget was cut > [!quote] > what we don't add is sometimes more valuable than what we do The log is the evidence for its own principle. Of roughly eighteen recorded decisions between the June 19 roadmap and August 19 release day, the large majority are punts, deferrals, reversions, or scope reductions: Dialog and Marquee, real-time collaboration, the Abilities API follow-ups, the Table of Contents block, Unicode email addresses, React 19, displaying inherited styles, the "On this day" widget, suggestion mode, and the toolbar focus/hover change. The reasons are consistently about **timing and unresolved disagreement rather than merit**. RTC went because "scope and transport decisions were unresolved with feature freeze approaching, so a clean deferral was safer" — and deliberately early, "to ensure we could focus on more realistic items to land." Inherited styles went because disagreement "persisted right up to Beta 4." The toolbar change was reverted once "the debate had run for several days without agreement." None of these are judgments that the work was bad. The second half of the role is unblocking, and it fails visibly less often than it succeeds: on inherited styles she records trying "to unblock things as the release lead by sharing various possible approaches to get consensus but, sadly, none of them ended up working out." A cut is the fallback when unblocking does not land, which is why the cuts dominate the log. ## Scope & conditions - **Holds** for time-boxed releases with a fixed date and negotiable scope. Where the date moves instead, the role's output shifts to schedule management and this inverts. - **Requires authority to cut.** Subtraction is only available to someone who can decline work others have already invested in — which is why the role reads as nebulous and is not. - **Early beats late.** RTC was punted deliberately early to redirect effort; the toolbar revert came days before release and salvaged less. The value of a cut decays across the cycle. - **Invisible by construction.** A shipped release lists what was added. Nothing in it records the ten things that were not, or that a squad spent July on realistic work because one call in early July freed them. - **Does not follow** that cutting is always right. The log includes exceptions made in the other direction — auto-approved self pingbacks landed late "due to the limited impact and small amount of code" — so the principle is a default, and the reasoning for departing from it is recorded too. ## Links - [[3. Resources/MOCs/Open Source Governance MOC]] — what release leadership actually consists of, against what a release announcement shows - [[3. Resources/MOCs/WordPress Platform Design MOC]] — scope discipline as the mechanism that keeps a platform's surface area from growing every cycle - [[3. Resources/Permanent Notes/Prevented Work Is Invisible to Velocity Metrics]] — because extends: this is the same invisibility one altitude up, where the unshipped feature leaves even less trace than the prevented defect. - [[3. Resources/Permanent Notes/A Decision Log Is How a Nebulous Role Becomes Inheritable]] — because this is what makes the subtraction legible at all; without the log the cuts are simply absences. - [[3. Resources/Permanent Notes/Primitive-First Design Absorbs Conflicting Feedback Without Scope Creep]] — because contrasts: that is the design-side way to avoid the cut, by shipping a primitive instead of adjudicating between requests. - [[3. Resources/Permanent Notes/Interface Surface Area Costs Selection Accuracy Not Just Tokens]] — applies-in: every feature not added is surface area not spent, which has a cost this note's subtraction is paying down. - [[3. Resources/Permanent Notes/Abstract Only After Two Real Implementations Exist]] — because extends: the same restraint expressed as a timing rule, where waiting is the decision and shipping is the failure mode. ## Tests / falsifiers - Count the decisions in the next release lead's log by type. If additions dominate, either the role differs by cycle or 7.1 was unusually contested. - Compare releases where a lead cut early against ones where cuts came at RC. If late-cut releases do not show more churn, the timing half of this is weaker than stated. ## Maintenance - Last tended: 2026-08-28 - Next review: 2026-11-28 ## Source [[3. Resources/Readwise/Articles/WordPress 7.1 Release Lead Decision Log|WordPress 7.1 Release Lead Decision Log]]