n o ren
Systems & Organizations

Who Actually Holds the “Done” Flag?

When the product lead signs the release checklist, the engineering lead still controls the final merge, and the ship never leaves the dock.

2026-09-141 min read

The “done” flag lives in a tiny spreadsheet column that only the product manager updates, while the codebase lives under the engineering lead’s branch protection rules. That split creates a silent tug‑of‑war: product claims delivery, engineering withholds the merge until every test passes, and the organization stalls in a loop of “we’re ready” versus “we’re not yet”. The root cause is a mis‑aligned ownership contract: the person who declares completion is not the one who can actually unblock it. Because the two roles answer to different incentive structures—product is rewarded on launch cadence, engineering on defect‑free releases—they each push the flag in opposite directions. The result is a hidden queue where work piles up behind an invisible gate, and senior leadership sees a healthy roadmap while the team’s velocity silently erodes.

At a mid‑size fintech startup, the product manager announced a new payment feature as live on the internal dashboard. Meanwhile, the lead engineer kept the pull request in draft, citing a flaky integration test that only ran in the nightly pipeline. The feature sat in “released” status for weeks, confusing sales, upsetting customers, and inflating the churn metric. Only when the CTO forced a joint “done” ceremony—where the product manager and engineer sign off together—did the bottleneck dissolve, and the next release hit the calendar on time.

The lesson is that “done” is not a state but a contract. When the contract is split, each side defaults to protecting its own KPI, and the organization pays the price in delayed value and mis‑aligned metrics. Aligning the flag with the actual gatekeeper—by giving the product manager merge rights or by moving the final sign‑off to a neutral role—removes the invisible queue and restores a single source of truth for delivery.

Key insights
A “done” flag that isn’t tied to the actual gatekeeper creates a hidden hand‑off queue.
Aligning the flag with the true blocker eliminates the silent stall and clarifies real delivery speed.
Why it matters

Ignoring the split ownership lets invisible bottlenecks grow, turning every release into a guessing game for the business.

The mis‑aligned flag also skews performance data, making leadership think teams are faster than they truly are.

Use this tomorrow
1
Open the current release spreadsheet, find the “Done” column, and count how many rows are marked done but whose corresponding pull request is still unmerged.
2
In the next sprint planning meeting, add a single line item that requires the product manager and engineering lead to co‑sign the release checklist before a feature is marked done.
Go deeper

The idea traces back to “ownership contracts” in organizational design, where the party who declares a state must also have the authority to make it happen; otherwise the contract is merely a promise. In software firms, branch protection rules act as the real gate, so any declaration of completion that bypasses that gate is structurally unsound.

Over‑centralizing the flag on a neutral role can backfire if that role becomes a new bottleneck; the key is to match authority with accountability, not simply to add another sign‑off.