7.2 Meeting Types, Roles & Follow-Through

Match the Meeting to Its Purpose

A meeting is justified when live interaction, collaboration, or a decision is worth the participants’ time. CompTIA groups common meetings by purpose.

Collaborative Meetings

• Workshops bring participants together to produce a defined artifact or solution.
• Focus groups gather reactions from a selected audience to explore needs or perceptions.
• Joint application development / joint application review (JAD/JAR) sessions unite users, business representatives, and technical staff to define or review requirements and solutions.
• Brainstorming generates possibilities before evaluation narrows them.

Informative Meetings

• Demonstrations or presentations show a result or convey structured information.
• Stand-ups provide brief synchronization around current work and blockers; in Scrum, the Daily Scrum specifically inspects progress toward the Sprint Goal and adapts the plan.
• Status meetings review integrated progress, risks, issues, dependencies, and decisions needed.

Decisive Meetings

• Refinement clarifies, splits, orders, or sizes future work so it is better understood.
• Task setting confirms near-term work, ownership, dependencies, and expected completion.
• Project steering-committee meetings make governance decisions about direction, funding, escalations, exceptions, or major change.

A kickoff aligns people at the transition into authorized work; a retrospective improves the way a team works; a phase gate evaluates exit evidence. Their purposes differ even when some attendees overlap.

Prepare the Agenda and Roles

Publish an agenda early enough for preparation. State purpose, desired outcome, pre-read materials, topics, presenters, timeboxes, and the decision owner. Invite the target audience that supplies required information, expertise, impact, or authority.

The facilitator keeps discussion aligned to purpose and time, makes space for relevant viewpoints, and parks unrelated topics. The scribe captures attendance when required, material decisions, rationale, action items, owners, dates, and unresolved questions. Attendees prepare, participate, and accept or challenge assigned actions during the meeting rather than after the record is published.

Timeboxing gives a topic a fixed window. When the time expires, the facilitator seeks a decision, assigns further analysis, schedules a focused follow-up, or escalates. Timeboxing prevents one topic from consuming the whole meeting; it does not justify cutting off required safety, legal, or governance review.

Minutes, Actions, and Follow-Up

Minutes are the durable record, not a transcript. Distribute them through the approved channel, protect sensitive material, and allow a defined correction period. Each action item needs one accountable owner, a concrete deliverable, and a due date. Record dependencies and escalation triggers.

Follow-up means checking completion, updating the relevant log or plan, and communicating the outcome to affected people. An action mentioned in minutes but never tracked is not controlled. Close the loop by linking meeting decisions to changes, issues, risks, requirements, or approvals where traceability matters.

Scenario Selection and Common Traps

A team needs to discover why users reject a prototype. A focus group can explore reactions; a workshop is better when participants must leave with a revised workflow; a JAD/JAR session fits collaborative application requirements; brainstorming fits idea generation before evaluation.

A developer wants to show completed behavior and gather reaction. Use a demonstration or Sprint Review, depending on the delivery framework. A sponsor needs an integrated health summary and escalation decisions, so use a status or steering meeting rather than a daily stand-up. A team wants to improve how it worked, so use a retrospective rather than a product demonstration.

Watch for these exam traps:

• An agenda is prepared before the meeting; minutes document what happened after it.
• The facilitator controls process and participation; the authorized decision-maker controls the decision.
• The scribe records the outcome but does not automatically own every action.
• “Consulted” attendees provide two-way input; “informed” recipients may only need the approved minutes.
• Timeboxing limits discussion but does not convert silence into approval.
• Sending minutes proves distribution, not completion of actions.

If a decision cannot be made, record exactly what evidence is missing, who will obtain it, by when, and where the decision will reconvene. If an action becomes overdue, follow the stated escalation path. Effective meeting management is visible in the resulting decisions, artifacts, and completed actions—not in the number or length of meetings.

Remote and Hybrid Meetings

For distributed participants, test the conferencing channel, provide accessible materials, state recording rules, and plan for time-zone and language barriers. Use a shared approved artifact so remote and in-room attendees see the same decision state. If technology fails, follow the alternate channel in the communication plan and record any decision that must be reconfirmed.