CACM Reopens the MVP Debate With a 'Considered Harmful' Response

Communications of the ACM has published a response essay titled "'MVPs Considered Harmful' Considered Harmful," reopening a years-long argument about whether shipping a Minimum Viable Product helps or quietly damages software quality.

The CACM piece carries a recursive title that nods directly to Edsger Dijkstra's 1968 Communications essay "Go To Statement Considered Harmful." That essay became the template for every computer-science rebuttal using the "considered harmful" framing. Each new paper in the lineage inherits its weight. The MVP rebuttal sits squarely inside that tradition.

What's the MVP debate actually about?

The Minimum Viable Product entered mainstream product practice through Eric Ries's 2011 book The Lean Startup. The original idea: build the smallest version of a product that delivers real value, learn from real users, then expand. Critics say the label routinely masks thin releases that never grow up. Defenders say the discipline is in the loop, not the launch.

The "MVPs Considered Harmful" argument, circulated for years across product and engineering circles, holds that the MVP frame gives teams permission to skip research, accessibility audits, and performance work. It points to apps that shipped minimal, raised funding, and stayed minimal. The critique asks whether "viable" ever gets redefined upward, or whether it quietly freezes in place.

Why does the rebuttal land here?

The CACM piece lands at a moment when product teams ship AI features weekly and lean on the MVP frame to justify thinner releases. The rebuttal's central claim, as its title implies: the original critique confuses rushed shipping with disciplined iteration. MVP is a learning method, not a quality shortcut.

What does CACM's venue change?

Communications of the ACM is one of computer science's most cited publications, with a print run that reaches most CS departments worldwide. A debate that previously lived on LinkedIn threads, conference Q&As, and design-week panels now sits in a peer-reviewed venue. That shift gives the argument institutional weight. Design leads, engineering managers, and PMs reading the CACM table of contents will see the MVP frame treated as a serious engineering topic, not a startup slogan.

What should practitioners do with this?

The CACM response does not announce fresh user studies or new datasets. It reframes. The practical question for design and engineering leads stays the same: define what "viable" means before launch, set a date to revisit it, and decide what counts as enough. The MVP label works when teams circle back. It fails when they don't.

What's next?

Expect the debate to surface in conference talks and design-week panels before the next product cycle. Whether the CACM framing shifts team behavior is tougher to predict. The MVP argument now carries a citation a CS professor can point to. That alone will move the conversation.