HKSM

Key Points

• Meetings are purposeful, time-boxed, and outcome-focused; they need a clear agenda and decision criteria.
• Tailor the format (workshop, stand-up, review, decision meeting) and use synchronous time only when it adds value.
• Invite the right participants and define roles such as facilitator, scribe, and decision-maker.
• Use structured analysis techniques (brainstorming, root cause, prioritization matrices) to guide discussion.
• Capture tangible outputs: decisions, actions with owners and dates, assumptions, and parking-lot items.
• Virtual or hybrid meetings require explicit norms, inclusive tools, and strong facilitation to maintain engagement.

Purpose of Analysis

• Turn scattered data and viewpoints into a shared understanding.
• Evaluate options against explicit criteria to support sound decisions.
• Validate assumptions and clarify constraints before committing.
• Identify, assess, and prioritize risks, issues, and dependencies.
• Agree on next steps that advance scope, schedule, cost, and value goals.

Method Steps

• Define the objective and success criteria for the meeting and confirm the needed decision or outcome.
• Select participants and roles; ensure the decision-maker and key SMEs are available.
• Prepare an agenda, timeboxes, pre-reads, and any data visualizations or templates.
• Open by setting context and ground rules; review the agenda and decision criteria.
• Analyze using structured techniques (e.g., cause analysis, option comparison, risk ranking) while managing time and participation.
• Summarize and confirm outputs: decisions, action items with owners and due dates, and items parked for later.
• Close with clear next steps and communication plan; distribute minutes and track follow-ups.

Inputs Needed

• Meeting objective, agenda, and decision criteria.
• Relevant data and reports (scope, schedule, cost, quality metrics, performance trends).
• Logs and registers (risk, issue, assumptions, dependencies, change requests).
• Backlog items, requirements, or user stories with acceptance criteria.
• Constraints, policies, and prior decisions or approvals.
• Stakeholder list and roles, including decision authority.
• Pre-read materials and collaboration tools or templates.

Outputs Produced

• Documented decisions and the rationale behind them.
• Action items with owners, due dates, and success measures.
• Updated logs and registers (risks, issues, assumptions, dependencies).
• Change requests or recommendations for governance review.
• Updates to plans, backlog, or baselines as applicable.
• Meeting minutes and distribution list for transparency.
• Parking-lot list for topics requiring separate analysis.

Interpretation Tips

• Test decisions against the stated criteria and project objectives to ensure alignment.
• Differentiate consensus from quality of decision; revisit if evidence is weak or biased.
• Confirm shared understanding by restating conclusions and asking for explicit agreement.
• Check for cognitive and group biases; invite dissenting views and data.
• Verify that owners, due dates, and success measures are clear and realistic.
• Trace decisions to requirements, risks, and constraints for auditability and future reference.

Example

A project team holds a 60-minute decision meeting to select a supplier. Pre-reads include performance data and a weighted criteria matrix. In the meeting, they review the scoring, discuss risks and assumptions, and confirm the decision-maker's criteria. They agree on Supplier B, capture two follow-up actions to validate contract terms, update the risk register for onboarding risks, and publish minutes summarizing the rationale.

Pitfalls

• Lack of a clear purpose or decision criteria leading to aimless discussion.
• Missing decision-maker or critical SMEs, causing delays or rework.
• Poor preparation or no pre-reads, resulting in low-quality analysis.
• Allowing off-topic debates and scope creep without a parking-lot.
• Dominance by a few voices, silencing diverse perspectives and data.
• No written outputs or unclear ownership of actions and decisions.
• Overlong or too-frequent meetings that could be handled asynchronously.
• Combining brainstorming and final decision in the same session without adequate evaluation time.

PMP Example Question

During a vendor selection meeting, the discussion goes off-track and time is nearly up. What should the project manager do to keep the meeting effective?

1. Extend the meeting until the team reaches a decision.
2. Call for a quick vote and choose the most popular option.
3. Refocus on the agenda and decision criteria, time-box remaining items, and assign actions for unresolved points.
4. Cancel the meeting and move the discussion to email.

Correct Answer: C — Refocus on the agenda and criteria, time-box remaining items, and assign follow-up actions.

Explanation: Effective meetings are guided by clear objectives and time limits; the project manager should steer the group back to the plan and capture follow-ups rather than forcing a rushed decision or overrunning.