Scaleflow’s weekly rhythm is carried by a handful of ceremonies. Every one of them shares the same shape: a clear purpose, a small attendee list, a tight agenda, and a hard time-box. Because the shape is constant, the pages that follow are constant too — once you can read one, you can read them all.

The standard template

Each ritual page is structured around the same six headings, in the same order:

• Purpose — the single thing this ritual exists to force.
• Cadence — how often it runs and how long it is allowed to take.
• Attendees — who is in the room, kept deliberately small.
• Format — the agenda and how the time is spent.
• Outputs — what concretely exists afterwards that did not exist before.
• Common pitfalls — the predictable ways teams break it.

The “at a glance” box at the top of each page carries the key facts so you can compare rituals side by side without reading every word.

A page may add the directives the method standardises on — a note, a tip, a warning, a best-practice, or a worked example tagged to a pillar — but the six headings carry the load. Read them top to bottom and you have the ritual.

Rituals are forcing functions, not ceremonies

This is the core stance, and it matters more than any agenda. A ritual is not something you perform because the method says so. It is a forcing function — a fixed point in the week that drags something into the open that would otherwise stay hidden.

Each ritual forces one or more of the three pillars:

• #REALITY — what is actually true on the ground, not what was planned.
• #LEARNING — what changed in the team’s expectations, captured as a lesson.
• #CONTEXT — a shared picture of the customer, the goal, and the constraints.

The cadences and time-boxes on the following pages are starting points, not commitments. Adapt them to your team. What you cannot adapt away is the demand that each ritual keep earning its place.