Value delivering things over doing work - ship three items all the way out the door and nothing elsewhere, rather than move nineteen forward

Situation

Closing the Aug 18 Engineering Weekly Sync, Peter gave the whole engineering leadership group a standing priority instruction: I really want everybody here to value delivering things over doing work. He put it concretely - I would much rather see you do fewer things all the way to completion and get stuff shipped to customers than be reporting status of, look, I am moving the ball forward on 19 different items. And not across the finish line on any of them, but forward on 19 items. I would way rather see us ship three items and do nothing anywhere else. He grounded it in the prior half: we delivered just enough in a bunch of areas to squeak across the finish line. And we built up a bunch of tech debt. He then closed the obvious loophole - I do not want to do less just to do less - and converted the instruction into standing permission to re-allocate: if pulling people off one project and putting them on another is going to allow us to get that second one out the door, let us have a conversation and advocate for that, make that change. The engineering order of operations is the named venue for making that argument.

Reasoning

Peter named three payoffs and none of them is efficiency: customer value actually shipped, learning that only comes from product in customers hands, and his own ability to advocate for headcount. The headcount clause carries the real mechanism - a half spent squeaking across finish lines produces no evidence he can take upward, whereas three finished things do. He judged the prior half by its result rather than its effort, and treated the accumulated tech debt as the price of breadth, which makes narrowing the debt remedy as well as the delivery remedy. The instruction is a re-allocation instruction, not a reduction in ambition, which is why he pre-empted the do-less reading out loud.

Additional Context

Delivered to the full engineering leadership group rather than to individuals, at the point where every direct report has now completed one round of five-week presentations - so Peter has a full picture of breadth across the org for the first time. H2 load is visibly heavier than H1.

Observed Evidence

Direct extended quote from the Peter-recorded Engineering Weekly Sync transcript, delivered as one of two explicitly flagged closing points. Confirmed by Peter in reflection review with no correction.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis