Routines & Cadence

The Pulse of Flow: Routines & Cadence

In FlowOS, we do not let meetings dictate the work. We let the flow dictate the meetings. We abandon the rigid ceremonies of Scrum (like the 15-minute daily interrogation) in favor of a rhythm that respects deep work.

1. The Timebox: The 4-Week Cycle

We operate on a 4-week cadence.

• Why 4 Weeks? True Discovery takes time. A 2-week sprint is often too short to empathize with users, ideate, and prototype a meaningful solution before building it.

• The Logic: While the board flows continuously (Kanban), we use the 4-week mark as our "Heartbeat" to synchronize with stakeholders and reflect on the system.

2. The Weekly Sync (Replacing the Daily Standup)

• The Problem with Dailies: Daily standups often devolve into status reporting, interrupting the "Maker's Schedule."

• The FlowOS Routine: The Weekly Sync (30 Minutes).

  • Focus: We look at the board together. We discuss blocked items, dependencies, and the "Design Thinking" validation results.

  • Goal: Unblock the flow for the week ahead. No status updates (the board is the status).

3. The Value Review (Every 4 Weeks)

• Not a Report: This is not a meeting to explain "what we did."

• A Showcase: This is a collaborative session with Stakeholders and Customers.

  • The Agenda: We demonstrate the Prototypes (from Column 4) or the Shipped Software (from Column 6).

  • The Discussion: "Does this solve the problem?" We gather real feedback to feed the next cycle of the Strategy Stream.

4. The Flow Retrospective (Every 4 Weeks)

• No Burndown Charts: We do not track "Velocity" or "Story Points completed." Those are vanity metrics.

• Focus on Flow: We look at the system.

  • Where did the flow stop?

  • Did we hold items in the 'Discovery' column too long?

  • Are the Management Objectives clear?

  • How is the team's energy?

Outcome: One specific action to remove friction from the system.