Stakeholder Decision-Making: Diverge/Converge Pattern

PMBOK v8 Definition

Stakeholder decision-making in project management follows a diverge/converge pattern where stakeholders are first engaged individually to generate a broad set of solution alternatives or approaches, then the project team converges on a preferred solution. The goal is to make decisions quickly while engaging the diverse knowledge of a group in an inclusive and respectful manner, with the deciding authority making a final decision based on presented analysis and consideration for stakeholder expectations.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions about stakeholder engagement and team decision processes, particularly in situational questions where you must identify the correct approach to avoid groupthink or undue influence. Expect scenario-based questions testing when to use individual input versus group decision-making, and how to manage stakeholder influence during decision processes.

Key Points to Remember (for the exam)

• Core Pattern: Diverge (individual input generation) → Converge (team selects preferred solution)
• Primary Reason for Individual Work: Avoids the effect of senior or charismatic stakeholders unduly influencing other stakeholders
• Key Outcome: Inclusion increases commitment to the decision, even if the option selected was not everyone's first choice
• Downside of Group Decision-Making: Time required and interruption to the team's work when members are consulted
• Decision Authority: The deciding authority (individual or group) makes the final decision based on presented analysis
• Minimizing Groupthink: Approaches like Roman voting, wideband Delphi estimating, and fist of five voting use the diverge/converge pattern
• Escalation Rule: For decisions beyond project team authority, investigate alternatives, consider impacts, and escalate to proper authority

Typical PMI Exam Example

A project manager is facilitating a decision on which vendor to select. The team includes two senior stakeholders with strong opinions. To avoid their influence dominating the discussion, the project manager asks each stakeholder to individually submit their top three selection criteria and vendor evaluations before any group discussion begins. After collecting all individual inputs, the team converges on the preferred vendor through structured voting.

PMI Exam Traps

• Trap: Confusing "individual input" with "individual decision-making" Reality: Individual input is collected to avoid influence, but the final decision is made by the deciding authority (individual or group)

• Trap: Thinking group decision-making is always better Reality: Group decisions require more time and cause interruptions; careful selection of which decisions go to group discussion is essential

• Trap: Assuming consensus means everyone agrees Reality: Inclusion increases commitment even when the selected option was not everyone's first choice; everyone has an opportunity to explain their position

• Trap: Believing the project team decides everything Reality: For decisions beyond team authority, the team investigates alternatives and escalates to someone with proper authority

Important PMI Connections

Quick Review Questions

1. Why is individual input preferred during the diverge phase of stakeholder decision-making?

2. What is the primary downside of group decision-making according to PMBOK v8?

3. Name three voting approaches that use the diverge/converge pattern to minimize groupthink.

4. What should the project team do when a decision is beyond their authority?

5. How does inclusion affect stakeholder commitment to a decision outcome?

PMBOK v8 Reference

Section 2.4 - Stakeholder Performance Domain (Decision-Making Approaches and Diverge/Converge Pattern)