Stakeholder &
Communication

GBS teams span both high-context and low-context cultures — misreading the style leads to misaligned expectations, missed signals, and fractured trust.

• High-context cultures (Japan, India, much of Latin America): meaning lives between the lines — tone, relationship, and what is not said matter as much as the words.
• Low-context cultures (US, Germany, Netherlands): communication is direct and explicit.

In a distributed GBS environment, your camera-on presence is your professional visibility.

• How you show up on video calls — framing, audio quality, background, engagement — directly affects how leadership perceives your readiness for higher responsibility.
• Remote does not mean invisible.
• The people who advance are the ones who are seen contributing, not just attending.

An executive summary is not a shorter version of your report — it is the decision-relevant extract.

• Lead with the recommendation, follow with the evidence, close with the ask.
• Executives read the first paragraph and decide whether to read the rest.
• If your summary requires scrolling before reaching the point, you have lost your audience.

GBS teams routinely span 8–12 time zones — async communication is not optional, it is the operating model.

• Synchronous meetings become impossible; the skill is structuring handoffs, documentation, and decision-making so work progresses across shifts without waiting for someone to wake up.
• The teams that master async operate 24 hours a day.
• The ones that do not create 24 hours of bottlenecks.

In a matrix, conflict is structural — it is built into the design.

• Functional leaders want standardization; regional leaders want flexibility.
• Your job is not to avoid conflict but to surface it early, frame it as a trade-off decision, and escalate with options rather than complaints.
• The GBS professionals who navigate conflict effectively are the ones who get trusted with bigger scope.

Managing up is not politics — it is making your manager effective.

• Understand their priorities, anticipate their questions, deliver information in their preferred format, and flag risks before they become surprises.
• The people who do this well get more autonomy, better assignments, and faster career progression.

Difficult stakeholders are rarely difficult people — they are people with unmet expectations, competing priorities, or legitimate concerns that nobody acknowledged. The skill is diagnosing the root cause of the resistance before responding to the behavior. Once you understand what someone is protecting, you can address the concern instead of fighting the symptom.

In GBS, every yes to an out-of-scope request is a no to something already committed. Saying no diplomatically means acknowledging the request, explaining the trade-off, and offering an alternative. "We cannot do that this week, but we can prioritize it for next sprint if you deprioritize X." The word no protects your team and your credibility.

Position-based negotiation ("I want X") creates winners and losers. Interest-based negotiation ("I need X because of Y") finds solutions that satisfy both parties.

• In GBS, you negotiate constantly — scope, timelines, resources, SLAs, vendor terms.
• The framework from Getting to Yes: separate people from problems, focus on interests, generate options — applies to every one of these conversations.

In GBS, you rarely have direct authority over the people whose cooperation you need.

• Influence maps identify who has decision power, who has veto power, who is a champion, and who is a blocker — then help you build a strategy for each.
• The skill is not persuasion; it is understanding what each stakeholder needs to say yes and systematically providing it.

The Minto Pyramid inverts how most people present:

• Start with the answer.
• Then the supporting arguments.
• Then the evidence.

Executives want the conclusion first and the analysis only if they challenge it. If you build up to your recommendation over 20 slides, you will lose the room by slide 5.