Communication and Stakeholder Management: Getting Decisions Adopted
What you must know
This domain tests whether you can move a technically correct answer through people. Know stakeholder mapping (influence versus interest), the difference between informing, consulting, and deciding, and how to build a RACI-style clarity on who owns what. Understand that logistics sits between sales, operations, finance, and suppliers, each with different objectives and vocabularies - cost language for finance, service and availability for sales. Know how to frame a recommendation as options with criteria, impacts, and a clear ask. Expect questions on escalation, managing disagreement, and communicating bad news early.
Traps
Beware answers that are technically right but ignore the decision rights - recommending an action owned by another function without consultation. Watch for "communicate more" as a substitute for defining who decides. Another trap is presenting a single option as a fait accompli; stakeholders resist what they were not consulted on. Also watch for confusing a stakeholder with high interest but low influence (keep informed) with one who can block the decision (engage early).
Worked example
A carrier change saves $200k but raises transit by one day. Sales objects. Rather than escalate immediately, map stakeholders: finance (high influence, supportive), sales (high influence, opposed), customer service (low influence, high interest). Build a one-page options table - status quo, carrier change, hybrid with premium service on top accounts - and pre-brief sales before the meeting. Rule of thumb: pre-brief the blockers, table the options, and name the decision owner before the formal meeting.