The line between a thin, agile product iteration and a bad compromise

The line between a thin, agile product iteration and a bad compromise is hard to see and easy to screw up.

You want to avoid making compromises that set you off down the wrong path.

Equally important, avoid making compromises that actually and ultimately end up being just as hard/costly as doing it right. When measuring cost, be sure to factor in initial customer education, ongoing customer support, technical debt, and, perhaps most insidiously, future investments and cognitive drift going in the wrong direction to support the initial compromise.

Ship polished iterations that are along the correct vector towards your ideal - even if, at first, it feels like slightly more scope.