Scoping and Shipping
Cutting a first version that teaches you something, sequencing work so value lands early, feature flags as product tools rather than deploy tools, a definition of done that includes "someone used it", and a shipping cadence the team can sustain.
The quarter-size version that answers the same question as the full feature — found by naming the question first, and proposed by you before scope gets cut for you.
When the work does not fit, cut the parts that would not change the answer to the question the feature is asking — not the parts that are hardest to build.
Order the work so something useful reaches people in the first slice, and let the second slice — not a guess — justify the foundation.
A flag is how a launch becomes small and reversible: who sees it, how many, and how to stop it — owned like a product decision, and removed once the decision is made.
Merged is a midpoint. A feature is done when real people have used it and you know what happened — including when what happened was nothing.
A steady rhythm of small releases beats a heroic quarter: the team gets a pace it can hold, and stakeholders get a calendar they can plan around instead of a date they have to chase.