
8 Engineers, Zero Ships, Six Months
Thirteen people, two roadmap reviews, nothing shipped to a customer in two quarters. How teams go busy and idle at once.
Angle
10 posts

Thirteen people, two roadmap reviews, nothing shipped to a customer in two quarters. How teams go busy and idle at once.

Reported in February, deprioritized in April, still open in November. The bug had outlasted three roadmap cycles.

One product line, scoped at twelve weeks, quietly stalled the rest of the roadmap for a quarter. Why a big launch costs two to three times its headline.

The board asked why those four items. He gave four different answers. None was the real one. A roadmap of compromises dressed as strategy.

Eighty-seven items filed under one word: roadmap. Twelve were shipping. The rest were every customer ask since 2023, waiting for a commitment that never came.

Every product meeting opened with what the leader shipped. Two years later you were a cheaper version of them, and buyers said so out loud.

Six months of engineering. Three demos to leadership. Logged into twice in production. The tool was a project nobody had asked for.

The signal shows up in spring. The pivot happens the next winter, after months of burn and the best people leaving. Most of the delay is identity, not data.

Signups up forty percent, conversion down sixty: the trial worked perfectly for people who would never pay. A trial is a selector, not a funnel widget.

Customers don't churn loudly. They ask for one more thing, watch you not ship it, and quietly leave. Most late feature requests are exit interviews in disguise.