8605-412 Assignment Example

Meetings are among the most visible — and most frequently criticised — activities in any organisation. When managed well, they align teams, resolve problems, and drive decisions. When managed poorly, they consume time, frustrate participants, and produce no discernible outcome. Unit 8605-412 treats meetings not as an administrative task but as a management skill: understanding which meeting type serves which purpose, preparing effectively so time is not wasted, and developing your own ability to chair meetings that achieve their objectives.

This assignment example is written from the perspective of a project manager in a 150-person digital agency, responsible for managing cross-functional project teams of eight to twelve people across design, development, content, and client services. The agency environment — fast-paced, client-driven, and heavily reliant on collaboration — makes effective meeting management a daily operational necessity rather than an occasional leadership exercise.

Learning Outcome 1 — Understand Different Types of Meetings and Their Suitability for Different Purposes

AC 1.1 — Describe the Different Types of Meetings in the Organisation

The agency uses five distinct meeting types, each serving a different function within the project lifecycle and organisational governance.

Daily stand-ups. Fifteen-minute, time-boxed meetings held each morning within project teams. Conducted standing (or on camera with no chairs visible, for virtual attendees) to enforce brevity. Each team member answers three questions: what did I complete yesterday, what am I working on today, and what is blocking me? These meetings are not discussion forums — they are synchronisation mechanisms. Format: face-to-face or hybrid via Teams. Frequency: daily during active project phases.

Weekly project review meetings. Sixty-minute structured meetings between the project manager, team leads, and the account manager. These review project progress against milestones, assess risks and issues, review budget utilisation, and agree priorities for the coming week. A formal agenda is circulated 24 hours in advance, and minutes with actions are distributed within two hours of the meeting concluding. Format: typically hybrid (in-office and remote participants). Frequency: weekly.

Client status meetings. Thirty to sixty-minute meetings with the client’s project sponsor and key stakeholders. Purpose: communicate progress, present deliverables for sign-off, manage expectations, and escalate decisions that require client input. These are externally focused — the language, level of detail, and presentation standard differ significantly from internal meetings. Format: video call or client-site face-to-face. Frequency: fortnightly or as contractually agreed.

Retrospectives. Ninety-minute facilitated sessions held at the end of each project sprint or phase. Purpose: reflect on what went well, what did not, and what should change. Unlike review meetings (which focus on deliverables), retrospectives focus on process and team dynamics. They require a psychologically safe environment where team members can raise concerns without fear of blame. Format: in-person preferred (for facilitation quality). Frequency: end of each sprint (typically every two weeks).

All-hands company meetings. Monthly sixty-minute meetings attended by all 150 staff. Led by the managing director with contributions from department heads. Purpose: share company performance, celebrate achievements, announce strategic decisions, and provide a forum for questions. Format: in-person in the main office with livestream for remote staff. Frequency: monthly.

AC 1.2 — Explain Why It Is Necessary to Have Different Types of Meetings

Different meetings exist because different purposes require different structures, participants, durations, and communication dynamics.

Purpose alignment. A daily stand-up exists to synchronise — it requires all team members but only fifteen minutes. Using a weekly project review for daily synchronisation would waste four hours of collective time per week. Conversely, using a stand-up for strategic risk assessment would be inadequate — the time constraint prevents the depth of analysis that risk management demands. Each meeting type is designed around its purpose: the format serves the function (Barker, 2022).

Audience differentiation. Internal meetings and client meetings require fundamentally different communication approaches. Internally, the team uses technical language, discusses risks openly, and debates options candidly. Client meetings require curated communication — technical detail translated into business language, risks framed as managed rather than alarming, and options presented as recommendations rather than open debates. Attempting to serve both audiences in a single meeting would either overwhelm the client with technical detail or constrain the team’s ability to discuss issues openly.

Temporal rhythm. Organisations operate across multiple time horizons simultaneously. Daily stand-ups address the immediate — what is happening today. Weekly reviews address the short term — are we on track this week? Retrospectives address the medium term — how should we improve our process? All-hands meetings address the strategic — where is the company heading? Drucker (2022) argued that effective management requires different conversations at different cadences — the daily operational conversation and the monthly strategic conversation serve different purposes and therefore demand different meeting structures.