Weekly Ops Standup Prep
1-page or slide deck distributed 1 hour pre-standup. Outcomes captured during the meeting. Action items logged within 1 hour post-meeting.
Before you start
- Ops dashboard with key metrics
- Issue tracker for open items
- Standup format documented
- Current state of ops metrics (incidents, vendor SLAs, financial flags)
- Open issues from prior weeks
- Upcoming events or risks
The steps
- Pull weekly metrics snapshot — Compile: vendor SLA status, financial health flags (cash position, burn rate), open incidents, compliance items due this month, key vendor contract renewals. Match to standard standup template.
- Review open issues and update statuses — For each open issue from prior weeks: pull current status, last update, owner, blockers. Stale issues (no update >7 days) get flagged for the standup discussion.
- Identify the 3 things worth discussing — Don't list 30 items. Pick 3: a positive (something completed), a problem (something blocked or surfacing), a watch (something trending toward concern). Focused discussion beats comprehensive listing.
- Highlight cross-team dependencies — Flag any item that depends on another team's action: legal, finance, IT, HR. List the ask, the owner, the deadline. Cross-team items often slip without explicit surfacing.
- Compile the standup deck or doc — Format: 1-page or short slide deck. Top: 3 highlights. Middle: open issues with status. Bottom: cross-team asks and decisions needed. Distribute 1 hour before the standup.
- Capture standup outcomes and follow up — During the standup, capture decisions and action items live. Within 1 hour of standup ending, update the tracker with new owners and dates. Close the loop on every decision.
If it goes wrong
Standup runs long because of status-update theater
Status updates are async (in the deck). Standup is for discussion. If something doesn't need discussion, don't bring it up.
Action items don't get followed up
Tracker integration with the standup notes. Every action item is automatically a tracker entry with owner and date. Check progress at next standup.
Same issues recur week after week
Recurring issues need root-cause sessions, not weekly status. Schedule a 30-minute deep-dive to resolve, not just track.
All OpenLabor playbooks