Portfolio · Event · Sync · Weekly

VMO Sync

A weekly look at portfolio flow, exceptions and blockers.

01What it's for

The VMO Sync keeps the portfolio flowing between QBRs. It looks at where Epics wait, which blockers the ARTs cannot solve themselves, and which deviations need a decision now instead of in three months.

It is exception management: surface risks early and decide on escalation or corrective action.

02What it turns into on the old system

The VMO becomes the PMO with a new name. The weekly sync collects status, chases reports and timesheets, and sends actions down.

Teams spend time preparing for it. The meeting tracks milestones, not outcomes.

03How you notice

ARTs prepare slides for the VMO.
The same blockers are reported week after week.
Escalations wait for the next sync instead of being handled when they occur.
The VMO owns the plan instead of serving the flow.

04How to make it work

Thirty minutes, exceptions only, with data from the tools rather than from slides.

Decide only the blockers the ARTs cannot solve at their level. Send everything else back down, with the authority to decide it.

Measure the portfolio's own flow: time from idea to decision, Epic WIP, time to stop.