Multi-team coordination without adding more meetings

Coordinate through the record and meet only to decide

Multiple teams can coordinate without adding meetings when dependencies between them are written down with owners and dates, status is visible to every team that depends on it, and meetings are reserved for decisions the record cannot make. Most coordination meetings exist to share status, and status sharing is the one job a shared record does better than a room full of people.

Look at a typical operations calendar in a large company. There is a daily production call, a weekly logistics sync, a cross-site planning meeting, and a separate catch-up with procurement. Many attendees sit through most of each call waiting for the two minutes that concern them. The meetings grow because each new coordination problem gets solved by adding people or adding a slot.

Find out which meetings are really status meetings

Take the recurring coordination meetings and, for two weeks, note what happens in each one. Sort every agenda item into one of three kinds: someone reporting status, someone asking for help, or the group making a decision.

Meetings that are mostly status reporting are candidates to replace. Meetings where help is requested and given can often shrink to a short slot. Meetings that make real decisions, such as reallocating capacity between plants, should stay, and they usually improve once status no longer eats their time.

Count the attendees too. If a meeting has people who never speak and never receive an action, they are there to listen for news that affects them. A shared record can give them that news without an hour of their week. Ask them directly which items they come for, and make sure those items are visible in writing before anything is cancelled.

Write dependencies down where both teams can see them

Teams coordinate mostly around dependencies: the warehouse needs production to finish a batch, maintenance needs operations to release a line, procurement needs engineering to sign off a specification. When these live only in people's heads, the only way to check them is to ask, and asking at scale becomes a meeting.

Record each dependency as its own item, linked to the work on both sides. It needs a few facts to be useful:

• The team that needs something, and the team that must provide it
• What exactly is needed, described so both sides agree what done means
• The date it is needed by, and the date the provider has committed to
• A named person on each side who can answer questions
• Current status, updated by the providing team as they work
• What happens downstream if the date slips, in one line

Replace the round-the-table update with a written one

Ask each team lead to update their status in the shared record by a fixed time before any remaining coordination meeting. Attendees read it beforehand. The meeting opens by asking only about items marked at risk or blocked, and anything already understood is skipped.

Written updates need a little discipline to be useful. Each one should say what changed since the last update, what is blocked and by whom, and what the team needs from others. A paragraph saying all on track every day teaches readers to ignore it. A line saying waiting on QA sign-off for batch release, needed by Thursday, gives the dependent team something to act on.

Some leads will miss the meeting as a place to be seen. Recognise good written updates openly in leadership forums, so writing a clear status becomes the visible contribution instead of speaking in the call.

Keep the meetings that make decisions, and make them shorter

After a month of written updates, most status meetings can be cancelled or cut to a fraction of their length. Keep one regular forum where cross-team trade-offs get made, with the people who have authority to make them. Bring only the items the record shows are stuck, and leave with a decision and a named owner for each.

Set a rule that any new recurring meeting needs a written purpose and an end date. Coordination meetings tend to outlive the problem they were created for. Reviewing the calendar each quarter, and cancelling anything whose purpose the shared record now covers, stops the slow return to the old pattern.

Shared records for dependencies, status, and handoffs are central to how Fasttrade's BukuOP approaches operations work, along with the stand-ups and weekly reviews that run on them. Speak with Fasttrade to confirm whether it would cover your teams and sites.

Frequently asked questions