Building got 10x cheaper. Shipping didn't!

Anyone can build a demo now. With Lovable or Cursor you go from idea to working prototype in a couple of days. That part genuinely got easier.

What didn't get easier is everything after.

The demo becomes ten features. The features become tickets. The tickets create dependencies. Requirements change. Priorities shift. Some work isn't ready to start. Some is blocked on a decision nobody made. And some keeps moving long after the assumption behind it stopped being true.

Then someone asks the question nobody has a clean answer to: are we shipping the right thing, or just producing more work?

I don't think that's a tracking problem. Jira, Linear and Asana do what they were built to do — they record what exists. They were designed for teams where a human moved every ticket by hand. That assumption is quietly breaking now that a real share of the work is machine-generated, and generated fast.

Curious what people here are actually doing about it:

— How do you tell the difference between a team that's shipping and a team that's just producing?

— Has the volume of work your team generates changed in the last six months? Did anything about how you plan change with it?

— If you're running coding agents, how do you decide a ticket is even ready to hand to one?

(Disclosure: I'm building in this space — Everview, not launched yet. But I'd rather hear how you're handling it than talk about what we're making.)