Most building advice sounds obvious when it is written as a heading. It becomes valuable only when it helps reduce a real idea, choose the next piece of work or decide what evidence would change the plan.
The question behind small releases keep projects moving is what changes in practice. The useful answer is usually found between reduce the distance to feedback and do not confuse shipping with rushing: the point where a broad idea becomes a choice that can be made, observed and revised.
Small releases expose assumptions while the context is still fresh. They show whether the change works in the real environment and whether the next planned step still makes sense.
Small does not mean random. A good release has one understandable purpose, complete validation and a rollback path. Several unrelated half-changes create more risk than one larger coherent change.
Make progress visible
A sequence of finished improvements preserves momentum and makes the project easier to resume after interruption. It also creates an honest history of what changed and why.
The work still needs tests, review and operational care. The useful constraint is scope: reduce what the release promises, not the quality of the promise it keeps.
The aim is not to remove ambition. It is to turn ambition into a finished piece of work that can be used, judged and changed. Smaller honest steps create better information than a large plan that never reaches reality.
That is the standard I would use when returning to small releases keep projects moving: keep the reason visible, make the next decision small enough to understand, and leave enough evidence to know whether the approach is still helping.