Every operating principle I hold reduces to three sentences: ship the loop, not the fragment. Measure what it changes, not what it demos. Keep what compounds — and kill what doesn't. This essay is the long version, because the short version gets nodded at and then ignored, and the gap between nodding and doing is where product organizations go to underperform.
Fragments versus loops
A fragment is any piece of work that requires imagination to connect to user value: the beautiful interface with mocked data, the model that performs in the notebook, the integration that works in staging, the strategy deck with no owner for slide twelve. Fragments are seductive because they demo well, and demos are the currency of internal status. An organization can stay busy for years shipping fragments — each one praised, none of them compounding — while carrying the warm feeling of momentum.
A loop is the smallest complete path from a real input to delivered value, instrumented well enough to tell you the truth. Emphasis on every word: smallest, because scope is the enemy of completion; complete, because a loop with one missing segment delivers exactly nothing — value is not proportional to percent-done; instrumented, because an unmeasured loop is just a fragment with better marketing.
The discipline sounds obvious. It is not practiced, because loops force you to eat the unglamorous parts first — the data plumbing, the edge cases, the handoff nobody wants to own — and fragments let you defer them indefinitely. Show me a team's last quarter and I can tell you which diet they are on: loops produce small, complete, slightly boring wins that stack; fragments produce impressive reviews and a strange absence of changed numbers.
What a loop means for AI products
AI raised the stakes on this discipline, because AI is the greatest fragment-generating technology ever built. The distance between a stunning demo and a dependable system has never been wider, and the demo has never been cheaper. For an AI feature, the complete loop includes four segments that fragment-thinking omits:
- The eval. A graded definition of good, runnable on every change. Without it you cannot tell whether the loop is improving or drifting — you can only tell whether people still clap.
- The fallback. Designed behavior at the edge of competence: how the system degrades, hands off, or declines. A loop that only works when the model is right is a fragment wearing a loop's clothing.
- The feedback capture. Corrections, rejections, and escapes harvested from inside the workflow, feeding the next quality target. This is the segment that makes the loop an asset instead of an artifact.
- The cost meter. Fully loaded cost per completed task, visible to the team that owns the loop. Unit economics is part of the loop's truth, not finance's problem.
A loop that runs is worth more than a platform that impresses. You can compound a running loop. You can only present a platform.
Measure what it changes
The second sentence exists because instrumentation is routinely aimed at the wrong target. Teams measure what the loop does — requests served, outputs generated, sessions engaged — because those numbers are easy and always go up. The question that matters is what the loop changes: a business number someone already reported before your feature existed, moving in the direction you predicted, by an amount you would defend in front of the CFO. Handle time. First-pass yield. Conversion. Days outstanding.
One primary metric per loop. Chosen before launch, not discovered after — a metric selected retrospectively is an alibi, not a measurement. And the corollary that keeps teams honest: if no business number could plausibly move, the loop should not be built. “Strategic” is not an exemption; it is the word fragments use to apply for permanent funding.
Keep what compounds — and kill what doesn't
The third sentence is portfolio discipline applied weekly. Compounding loops share a signature: each cycle of usage makes the next cycle better — more feedback, better evals, lower cost, higher trust — without proportional new investment. These deserve more than maintenance; they deserve doubling down, because compounding assets are rare and the instinct to move on to the next new thing systematically starves them.
Everything else is a candidate for the kill list, and the kill needs to be an act, not an absence: a dated decision, a written reason, instrumentation archived, the team redeployed with credit rather than stigma. Quiet abandonment — the fragment's natural death — teaches the organization nothing and leaves a residue of zombie surfaces that all cost trust to maintain. A clean kill teaches the organization what the bar is. In AI work especially, where the capability curve moves underneath you, a documented kill also leaves behind the one thing a dead project can bequeath: the precise conditions under which the bet becomes worth re-opening.
The weekly loop review
The ritual that operationalizes all three sentences fits in one recurring hour. Each loop owner brings four numbers: eval score against the bar, primary business metric against baseline, cost per completed task, and one week-over-week delta they are trying to move. Three questions per loop: is it improving, is it compounding, and what would make us stop? The review's output is allocation — which loops get more, which get maintenance, which get a kill date.
That hour replaces most of what product organizations currently do in status meetings, because status describes activity and the loop review prices assets. Run it for a quarter and the portfolio sorts itself: the fragments become embarrassing to present, the compounding loops become obvious to fund, and “learning rate” stops being a phrase from an essay and becomes a number your team knows it is managed on.
Ship the loop. Measure the work. Keep what compounds. Everything else in my practice is commentary on those three sentences.