Communication Cadence

Communication runs on a fixed rhythm so nothing depends on someone remembering to reach out. The daily beat keeps the team unblocked; the 2-week beat keeps the client aligned.

The rhythm

flowchart LR
  subgraph Daily["Every day"]
    SU["15-min standup<br/>team"]
  end
  subgraph Weekly["Every week"]
    WS["Written status<br/>to client"]
  end
  subgraph Cadence["Every 2 weeks"]
    D["Client demo"] --> R["Retro"] --> P["Plan next cadence"]
  end
  SU --> WS --> D

Who owns what

This table is the only list of standing meetings. If a meeting isn’t here, it isn’t standing.

Event	When	Owner	Format
Standup	Daily, 15 min	Team (PM facilitates)	Verbal — yesterday / today / blockers. Not a status report.
Written status	Weekly	PM (Firas Alhawasli)	Short written note to client: progress, next, risks, anything needed from them.
Client demo	Every 2 weeks	PM + team	Live demo of working increment against the cadence.
Retro	Every 2 weeks	PM facilitates	Team-only: what to keep, drop, try.
Cadence planning	Every 2 weeks	PM (Firas Alhawasli)	Pull the work for the next 2-week cadence.

Team leads call their own meetings as needed — occasionally, not on a fixed rhythm, so they aren’t on this table. If one becomes a recurring commitment, it belongs here.

Blocker escalation

Blockers do not wait for standup or the weekly status — they escalate the same day.

flowchart LR
  B["Blocker found"] --> TL["Team lead<br/>same day"]
  TL -->|needs client| PM["PM raises<br/>with client"]
  TL -->|internal| RES["Resolved / re-planned"]

Tip

Standup surfaces blockers; it doesn’t resolve them. Anything that stops work goes to the team lead the moment it’s found, not tomorrow morning.

The 2-week beat here is the same cadence as the Delivery Lifecycle. Client-facing escalation ties into Kickoff’s agreed comms plan.