Flow over ceremony

Summary

Ritual is justified only when it improves movement of value or decision quality.

Description

Forge does not reject cadence, planning, review, or retrospection. It rejects ceremony as a proxy for progress. Meetings, boards, artifacts, and metrics must earn their place by improving flow, reducing waste, or increasing decision quality.

Article

Most frameworks eventually suffer from the same market failure: useful disciplines turn into inherited rituals. Teams become busy maintaining the process around delivery rather than improving delivery itself. In the AI era, that risk gets worse because output volume rises so quickly. It becomes easy to confuse more tickets, more generated code, more demos, or more updates with more value.

Forge responds by making flow the test. If a ceremony helps shape decisions, expose risk, unblock dependencies, or move value downstream, keep it. If it mainly narrates activity, duplicate status, or preserve habit, challenge it.

This does not make Forge anti-Scrum or anti-SAFe. It makes Forge intolerant of process theater. Cadence still matters. Review still matters. Retrospection still matters. But only when they serve movement rather than ceremony for its own sake.

Inspiration reference

Lean: value stream, flow, pull, and perfection. Agile: working software as the primary measure of progress. Scrum: empiricism, inspection, adaptation, and value through increments. SAFe: shortest sustainable lead time with best quality and value.

Part of the four core principles series.