LEARN. PRACTICE. GROW.Understand the concept
A stakeholder may influence the project or be affected by it. Identify needs, decision authority, and involvement. A responsibility matrix can clarify execution, approval, consultation, and information, but does not replace agreement among people. The record should evolve as objectives or stakeholders change.
Apply and decide
Choose channel and detail according to the decision. Technical teams need dependencies and evidence; sponsors need impact, options, and commitments. Confirm understanding and record actions with owners and dates. When disagreement arises, first understand interests and constraints before escalating.
Guided application
If operations rejects a migration window, ask which service, shift, or cutoff would be affected. Do not infer resistance merely from disagreement. A conversation may reveal that one person covers both batch and the change, making the proposal infeasible. Prepare options with impacts and take the decision to whoever can prioritize. Match communication to its recipient: a specialist needs dependencies; a sponsor needs effects and a decision. Finish by confirming the expected outcome, owner, and date. In English, a short summary with those elements is more useful than reproducing every technical detail. Revisit the stakeholder record when new teams or responsibilities emerge.
Operations rejects a window during month-end close. Facilitating alternatives and explaining impact is more useful than merely recording “resistant team.”
Common pitfalls
Labeling disagreement without investigation; confusing delivery with understanding.
Related topics: Decompose, sequence, and estimate · Control cost, risk, and change
Effective communication checks understanding and connects information to action.
Reference: What is project management? · CAPM ECO 2023; official outline consulted 2026-09-29