I missed one of my own four sprint goals — and the rule that caused it was mine

I run a product that holds developers to a 21-day sprint. Last month I ran it on myself, as a participant, on a separate product of my own.

Four goal criterIia, frozen before day one. I hit three. Here's the one I missed and why I think it's the useful part.

The setup: goals get written down at acceptance and can only be corrected downward afterwards, never upward. Every milestone is measured against that stored wording. The idea is that a goal you can edit mid-sprint isn't a commitment, it's a description of whatever happened.

The miss: criterion 3 required three completed reciprocal feedback exchanges between developers, 48 hours each. I got two.

The third contact went quiet after one follow-up. And I have a rule for myself: one follow-up per contact, then never again. A second nudge might have saved the criterion. It would have broken the rule.

So I kept the rule, missed the criterion, and filed it as a miss — not as "substantially met."

Why I'm posting this instead of the three I hit:

A frozen goal is worth precisely what it costs to miss it. If I'd rounded 2 of 3 up to a checkmark, I'd have proved that my own enforcement is decorative. The miss is the only evidence that it isn't.

The part I didn't expect: running my own product as a participant surfaced three defects that no test had found — including one data-protection bug that had been live for three and a half months, and a qualification filter that was only ever shown to people who had already disqualified themselves. A filter that only reaches the already-filtered isn't filtering. It just feels like one while you build it.

One more finding — and then the correction I had to make to it: both feedback exchanges that did happen came inbound, from a single public post, and both because I delivered first. Cold outreach to more than a dozen people stayed silent. I wrote that down as "going first converts existing interest, it doesn't create any," and filed it as a result.

Then I did the arithmetic. Sixteen contacts at a normal cold-reply rate is well under one expected reply. Silence was the single most likely outcome even in a world where cold outreach works fine. I had turned a null result into a law — which is the same move as rounding 2 of 3 up to a checkmark, just pointing the other way.

---

To be clear about what this is: a self-test, not a customer result. Nobody paid for it, there's no testimonial, and no paying customer has completed a full sprint yet. It proves the mechanism runs — nothing about whether it's worth paying for.

What I'm curious about: for those of you who set explicit goals for a build sprint or a launch window — do you log the misses anywhere, or do they quietly become "mostly done"? I've caught myself doing the second one for years, and the only thing that stopped it was writing the goal down somewhere I couldn't edit.