Coordinate a project: actions, decisions and status after the meeting
Fictional practice case: minutes, e-mails and a status message become an action list, a decision overview and a compact status.
Situation
After the project meeting on a fictional travel company’s new website there are minutes, two e-mails and a status message. Tasks, decisions and proposals are mixed up, and some details contradict each other.
Source material
«Eva delivers the texts for the offer pages by 27 May. Publication on 3 June agreed. Translation budget: confirmation from finance still missing. Marco: an additional language version would make sense.»
Agency: «3 June only works if all texts are available by 20 May. IT approval for the domain switch is still pending.» Finance: «The translation budget is included in the annual budget. I will send the formal confirmation on Monday.»
«Status green. Texts in progress, publication on 3 June.»
Task for the AI
Create an action list, a decision overview, open questions and a compact status for the next meeting from the minutes, e-mails and status message. Distinguish information, proposal, confirmed decision and open decision. Name contradictions with their source instead of resolving them yourself.
Result: actions, decisions, questions and status (draft)
Action list
- Offer page texts · Eva · minutes: 27 May, agency needs them by 20 May · resolve contradiction (sources 1, 2).
- Formal confirmation of translation budget · finance · Monday · open (source 2).
- IT approval for domain switch · owner not named · date open (source 2).
Decision overview
- Confirmed decision: publication on 3 June (source 1); according to the agency, dependent on texts by 20 May.
- Information: according to finance the translation budget is in the annual budget; only the formal confirmation is missing. This is not a missing approval.
- Proposal, not a decision: additional language version (Marco, source 1).
- Open decision: will the additional language version be examined, and who decides?
Open questions
- To Eva: can the texts be ready by 20 May?
- To the project manager: who obtains the IT approval, and by when?
- To Marco: which language, for which audience?
Compact status for the next meeting
- Proposed status amber instead of green: 3 June depends on texts by 20 May and on the pending IT approval. Translation budget confirmed in substance, formal confirmation to follow.
Sources, assumptions and open information
- Sources
- Meeting minutes, e-mails from the agency and finance, status message from the project manager.
- Assumptions
- The minutes reflect the meeting correctly. The status message was written before the two e-mails.
- Still open
- Delivery date of the texts, owner of the IT approval, decision on the language version.
What people review and decide
The project manager confirms actions and status with those involved and decides whether the status changes to amber. Nothing becomes binding just because it was mentioned.
Benefit in this situation
Everyone sees the same picture: who delivers what by when, what has been decided and where the date is at risk, before it is too late.
