Lab 07 — Cross-functional project meeting
| Level | Duration | Primary apps | Sample files |
|---|---|---|---|
| 200 | 30 minutes | Microsoft Teams, Microsoft 365 Copilot | 04_Project_Charter, 07_Standup_Notes, 12_Manufacturing_KPI |
Department and industry focus
Operations chairing a cross-functional steering meeting for the Unified Customer View programme, with manufacturing performance on the agenda.
Scenario
You run a recurring cross-functional steering meeting. In this lab you will use Copilot to prepare for the meeting, generate a decision-focused recap, and turn the discussion into a decision register with owners, conditions, and target dates. Drafting the messages that go out afterwards is covered in Lab 04, so keep this lab focused on preparation, recap, and the decision record.
Learning objectives
- Prepare for a cross-functional governance meeting with Copilot.
- Generate a decision-focused recap and action tracker.
- Separate agreed, deferred, and blocked items.
- Validate meeting outputs before sharing.
Exercise 1 — Prepare for the meeting
I am chairing a cross-functional steering meeting for the Unified Customer
View programme. Using /04_Mock_CrossFunction_Project_Charter.docx and
/07_Mock_Operations_Standup_Notes.docx, prepare me.
Include: objectives to confirm, risks and open decisions, operations issues
to raise, questions I should ask, and decisions likely required. Return as
a meeting preparation briefing.
🎙️ Live meeting path: Optionally schedule a short Teams meeting, enable transcription or Copilot meeting features per tenant config, and have one facilitator speak for at least 5 minutes using the sample speech. Works best with a single speaker in a quiet room.
Facilitator sample speech: Welcome to the cross-functional steering meeting for the Unified Customer View programme. We will confirm objectives, review risks and open decisions, and cover operations performance. The programme aims to give every business unit a consented, shared view of the customer, but privacy rules differ between HealthCare, Financial, and the other units, so we need to confirm the data owner and approve the consent framework before integration work starts. On operations, Penang OEE dipped after a line jam and Detroit defect rate is above threshold, so we need a quality recovery decision. Please capture all decisions with an owner and a target date, and record anything that needs escalation. Remember this is mock training data only.
Exercise 2 — Generate the recap
Use the charter and stand-up notes to generate a recap. Include: purpose,
key discussion points, decisions, risks/blockers, open questions, and
recommended next actions. Executive recap format.
Exercise 3 — Decision register
Create a decision register table: Item | Type | Risk | Decision (agreed/
deferred/blocked) | Owner | Conditions | Target date. Keep it grounded in
the sources.
⚠️ Validation: Before sharing any recap, register, or tracker, confirm that decisions, owners, and conditions accurately reflect the discussion. A participant must review Copilot output before distribution.