session · cadence
Bi-weekly client sync
45 minutes every two weeks. Fixed agenda. Signal readings, roadmap, scope decisions, CS patterns. The client speaks last. Not a feature-request meeting — the backlog has its own process for that.
When
- Every other week, same day, same time. Held even if there's nothing dramatic to discuss.
- Within a week of any Signal reading — the result is read in sync, not delayed to the next quarter.
Who
- PO — drives.
- Tech Lead — present.
- Client stakeholder — typically one named decision-maker; sometimes two if the engagement is multi-team.
Time-box
45 minutes. Hard cap. Anything not fitting goes to the next sync or to a separate meeting with a separate agenda.
Inputs
- The current signal reading(s) since the last sync.
- The roadmap for the next two weeks (what's planned to ship).
- Any scope decisions pending the client's input.
- CS ticket patterns and helpdesk reading.
- The last sync's action items (so we close the loop).
Agenda
| Time | What |
|---|---|
| 0–10 min | Signal readings. Any check dates that landed since last sync. What was predicted, what was measured, what was learned. The most important conversation. |
| 10–20 min | Roadmap. Next two weeks: what's planned, what's at risk, what's deferred. Specific. "The grading shortcut ships Wednesday at noon; the Hebrew language pack is deferred to next cycle and here's why." |
| 20–30 min | Scope decisions. Any decisions the client needs to make to unblock the team. Decisions, not discussions. |
| 30–40 min | CS patterns. From the past two weeks' helpdesk readings. What themes are surfacing? What's a brief input for the next cycle? |
| 40–45 min | The client speaks last. What's on their mind that we haven't surfaced? Closing the room with the client's voice catches what the agenda missed. |
Outputs
- A short sync note — decisions made, action items, open questions. Sent same day.
- Updated Client Notes — anything the client said that affects scope or schedule.
- (If applicable) items added to the backlog or briefs adjusted.
What good looks like
The sync delivers two things to the client every time: honest news about what shipped or didn't, and a clear path for the next two weeks. The client leaves knowing what's happening; the team leaves with any decisions they needed.
The sync stays on agenda. Feature requests get acknowledged and routed: "That's a great idea — let me file it in the backlog process and we'll surface it at the next portfolio review." The sync is for state, not for feature design.
Anti-pattern
The sync becomes a feature-request meeting. The client lists desires; the PO captures them; nothing on the actual agenda gets covered. Fix: the agenda is fixed. Feature requests have their own intake. The bi-weekly is for state and decisions.
A second anti-pattern: the client is surprised by something they should have heard in the weekly update. "Wait, we missed the grading deadline?" — and they're hearing it for the first time at the sync. Fix: the Weekly client update is the no-surprises channel. The sync confirms what the client already read; it doesn't break news.
A third: the sync becomes a status report. The PO talks for 30 minutes; the client says "thanks." Nothing surfaces. Fix: signal readings, scope decisions, and CS patterns are interactive — the client's reaction to each is the value of the sync.
See also
- Canon — After We Build · Client cadence
- Area — Bi-Weekly Sync
- Adjacent session — Weekly client update writing · Quarterly portfolio review