Method
Run a disciplined weekly cycle

Run a disciplined weekly cycle

Build reliability through a consistent update-discuss-publish rhythm.

Establish a predictable weekly cadence that builds momentum through three phases:

  • Update: Teams capture progress and revise forecasts
  • Discuss: Teams address coordination issues and resolve constraints
  • Publish: Teams confirm commitments for the coming week

This cycle creates a natural rhythm where teams progressively improve both their planning accuracy and delivery performance. The weekly cadence provides structure without rigidity, allowing teams to adapt to changing conditions while maintaining alignment.

The power lies in consistency. When everyone knows the rhythm won't change, they arrive prepared to solve problems together rather than just give status reports. This predictability builds the trust essential for high-performing teams. It might be tempting to skip cycles when the project becomes pressed for time, but in fact this is when maintaining the cadence is most critical.

1.1

Together, not apart

1.2

Give the frontline bandwidth, not busywork

1.3

Measure flow, not just criticality

1.4

You can't plan what you don't know

1.5

Rhythm is everything

1.6

Match methods to project characteristics

1.7

Simplicity beats sophistication

2.1

Set clear targets

2.2

Start simple

2.3

Embrace progressive planning horizons

2.4

Run a disciplined weekly cycle

3.1

Establish a daily coordination rhythm

3.2

Find and clear blockers

3.3

Intensify the rhythm as complexity increases

4.1

Capture delays, don't hide them

4.2

Capture issues when they happen