Engineering Sync

Purpose: Align engineering leadership on cross-cutting priorities, risks, and decisions

How to run this meeting

The engineering sync is a weekly leadership meeting, not a status report. It exists to handle what daily standups can't: cross-team dependencies, resource conflicts, architectural decisions, and anything that requires more than one team to solve. Keep individual team status off the agenda — if it doesn't affect anyone else in the room, it belongs in a team standup.

Rotate the facilitator role among tech leads and engineering managers. This distributes the sense of ownership and prevents the meeting from becoming one person's forum. The facilitator's job is to move the agenda, timebox each item, and ensure every decision is captured with a clear owner. A good rule of thumb: if an agenda item takes more than 10 minutes, it's either too big for this meeting or it wasn't prepared well enough.

Send the agenda at least 24 hours in advance and ask each team to submit their items by end of day Tuesday (for a Wednesday sync). This gives the facilitator time to sequence items by urgency and cut anything that can be handled async. The meeting should feel like triage, not open-ended discussion.

Before the meeting

• Submit agenda items to the facilitator by the stated deadline
• Review last week's action items and update their status before the meeting
• Prepare any relevant data, metrics, or context for your agenda items
• If you're presenting a decision, bring a clear recommendation — not just options
• Identify any cross-team dependencies that have emerged since last week

Meeting Details

• Date:
• Facilitator:
• Attendees:
• Duration: 45–60 minutes

---

Agenda

Items submitted ahead of time, sequenced by urgency. Each item should have an owner and a time budget.

---

Current Priorities

What is each team focused on this week? Flag any shifts from what was planned last week.

• Platform: API v2 scaffolding, deprecating legacy endpoints by end of sprint
• Payments: Migrating to new auth token format, blocked on Auth team's timeline
• Data: Finishing pipeline reliability work from last quarter; no new feature work this week
• Mobile: iOS release 2.4.1 hotfix in progress, Play Store submission by Thursday

---

Status Updates

Brief cross-team-relevant updates only. Detailed team status belongs in team standups.

• Auth token migration is on track for Wednesday deploy; Payments team needs at least 48h to test
• Platform's legacy endpoint deprecation has one external customer still on the old format — @platform-lead is coordinating
• Q1 infra bill came in 23% over forecast; details in agenda item #1

---

Cross-Team Dependencies

Explicit call-out of work that requires coordination across two or more teams.

---

Risks

Issues that could derail current priorities if not addressed. Flag severity and proposed mitigation.

• Auth/Payments dependency: If Auth ships Wednesday, Payments has only 48h to test before sprint end. Risk of hotfix needed post-sprint. Mitigation: Auth team delays to Friday or Payments extends testing window.
• Infra cost overrun: At current trajectory, Q1 closes 25% over budget. No mitigation in place yet.

---

Decisions

Record decisions made during this meeting — what was decided, who decided it, and the rationale.

• API v2 strategy: Team agreed to maintain v1 alongside v2 for 6 months, then hard deprecate. @platform-lead owns the deprecation timeline doc.
• Auth token timing: Auth team will delay Wednesday deploy to Friday to give Payments adequate testing time. @auth-lead to update sprint accordingly.

---

Action Items

Follow-up

The facilitator posts the meeting notes to the engineering Slack channel within an hour of the meeting. Action items are tracked in the shared project tracker — not just in this doc. Next week's facilitator should be confirmed before the meeting ends. If a decision made this week affects the broader roadmap, the PM team should be looped in separately.