Senior Stakeholder Management: map cross-BU executives and manage priority conflicts with declared frameworks

An operational guide for anyone who is a senior coordinator (5-10 years) managing a stakeholder map extended to executive sponsors plus team leads across 2-4 BUs. This is the level at which priority conflicts become the key metric of success: those who can resolve them with declared frameworks grow; those who stay stuck in informal politics plateau at the mid level. No theory: OKR-based frameworks, internal MOUs, formalized escalation paths, real tier-1 cases (Spotify, Atlassian, GitLab Handbook, Harvard Business Review).

TL;DR

The difference between a senior coordinator and a mid one is not in the tools - both use stakeholder maps and RACI - but in the level at which the map is built and the way conflicts are resolved. The mid maps their own BU; the senior maps 2-4 BUs including executive sponsors. The mid resolves conflicts by escalating to a senior; the senior resolves them directly with declared, OKR-based frameworks. Harvard Business Review research shows that 65% of cross-functional initiative failures in companies with more than 500 employees are attributable to poorly managed priority conflicts, not to technical or execution problems. This guide proposes a framework with three components: (1) an extended 2x2 stakeholder map plus decision role, which adds a third dimension (DRI/Approver/Consulted) to the cornerstone's influence×interest matrix; (2) a conflict resolution framework in five structured steps that translate political conflicts into quantitative, OKR-based trade-offs; (3) an internal cross-BU MOU, a 2-3 page document that formalizes the allocation of shared resources, escalation paths, and exit strategy. Four tier-1 deep-dive case studies: Spotify Squads/Tribes/Chapters (the most relevant pattern for cross-tribe stakeholder management), Atlassian DACI applied to cross-team decisions, the radically transparent GitLab Handbook, and HBR research on cross-functional conflict. Three senior anti-patterns: informal politics (decisions made in the hallways), escalation reflex (every conflict goes to the VP), and false consensus (an apparent decision that crumbles during execution). If you are already a senior with an extended map, skip straight to the Operational steps section.

When you need it / Prerequisites

This guide is written for the senior coordinator who has already done three things: (1) independently run at least three BU events end-to-end; (2) participated as a decision-maker (not just as an observer) in at least one cross-BU escalation where divergent priorities were at stake between two or more sponsors; (3) worked with the OKR framework (Objectives and Key Results) or equivalents (NCT, KPI tree, NSM). Without these three prior experiences, the techniques in this guide are theory - useful to know, hard to apply.

The typical moment when this guide becomes critical is the second week of planning for a cross-BU event spanning 2-4 units. In the first week everyone says yes; in the second, the priority divergences that were hidden behind the initial courtesy come to the surface: BU A wants to position the event as a product summit, BU B as an employee experience event, BU C as a partner sales opportunity. Without a conflict resolution framework, the decision gets "pushed to the next meeting" and progressively drags on until three weeks before the event, when cancellation is almost inevitable.

A second scenario in which this guide is indispensable is the change of executive sponsor in the middle of an annual cross-BU program. Sponsor X of BU A resigns or changes role; the successor Y arrives with different priorities; the decisions made in previous months have to be renegotiated. Without a declared renegotiation framework, every historical decision becomes worthless and the program re-initializes from scratch, losing 3-6 months of work.

Cross-cutting prerequisite: you have the organizational legitimacy to write governance documents (internal MOU, cross-BU RACI, escalation matrix). It typically comes with the job title - "Senior Event Lead", "Program Manager Cross-Functional", "Head of Events" - but it can be informal if your VP has explicitly delegated it to you. Without legitimacy, writing an MOU is wishful thinking and produces defensive reactions from team leads.

Minimum reading time: 22 minutes if you are a senior reading to apply; 35 minutes if you are a mid in transition (taking notes on the extended stakeholder map). Actually compiling the first cross-BU MOU takes 4-6 hours spread across 2-3 sessions with executive sponsors; from the third iteration it drops to 60-90 minutes.

Conceptual framework: from the 2x2 map to the extended map

The conceptual framework for the L3 level is built starting from the 2x2 stakeholder map of the Atlassian Team Playbook (see the series cornerstone) and extends it along two dimensions: organizational depth (executives + team leads, not just team members) and relational complexity (2x2 matrix + decision role).

The first extension is organizational depth. For a single-BU event, the 2x2 map mainly covers the operational team plus the sponsor. For a cross-BU event spanning 2-4 units, the map must include three vertical levels for each BU involved: (a) the BU executive sponsor (VP/Director, the political decision-maker), (b) the BU team lead (operational manager, tactical decision-maker), (c) the BU contributors (team members, point decision-makers). For four BUs involved, the map therefore contains 12 "vertical" stakeholders plus 5-10 cross-cutting stakeholders (HR, legal, finance, IT, security). Total: 17-22 stakeholders. The number is much larger than in a single-BU event, but the complexity is manageable if the map's structure is clear.

The second extension is relational complexity: adding to the 2x2 matrix (influence × interest) a third dimension representing the decision role. The most applicable framework is Atlassian Team Playbook's DACI (see cornerstone): Driver, Approver, Consulted, Informed. For each identified stakeholder, beyond their cell in the 2x2 matrix you also assign their DACI role on the event's main decision. The deliverable is a spreadsheet with five columns: name, corporate role, BU, 2x2 quadrant, DACI role.

The third component of the framework, optional but useful for cross-BU events spanning 3-4 units, is the inter-BU influence matrix: a representation of who can influence whom among the BUs involved. Example: the VP of Engineering of BU A is a personal friend of the CFO who approves BU B's budget; the Marketing team lead of BU C worked for two years in BU D and is listened to by the VP of D. These informal connections are often decisive in moments of conflict, and they are invisible to anyone without corporate political experience. Mapping them explicitly - even just in a private Excel sheet - drastically reduces political surprises.

A taxonomy of cross-BU priority conflicts

To manage conflicts with declared frameworks, you first need to classify them. The HBR literature on cross-functional teams (see HBR 2022 - The Cross-Functional Team Problem) identifies four recurring categories of conflict, each of which requires a different resolution technique.

Conflict 1 - Scope. Two BUs want to include contradictory elements in the event (e.g. BU A wants 70% technical content, BU B wants 70% commercial content). The conflict is only apparent, because both positions are valid for their respective BU; the problem is that the event has a single format. Technique: scope split or scope sequencing. You split the event into parallel tracks (if the format allows it) or you decide which BU has priority in the next edition (sequential). Never a 50/50 compromise: it produces a generic event that satisfies neither of the two BUs.

Conflict 2 - Budget. Two BUs contribute to the budget but diverge on its allocation (e.g. BU A wants to invest more in a prestige venue, BU B wants to invest more in marketing). Technique: cross-BU budget allocation 60/30/10 (see cornerstone), with the shared 10% governed by the steering committee. L3 addition: the allocation is proportional to the share of budget contributed (e.g. if BU A puts up 70% of the budget, it has 70% of the decision weight over the allocation). Documented in writing in the MOU.

Conflict 3 - Timing. Two BUs want different dates for the event, based on different internal priorities (e.g. BU A wants the event before the Q3 sales push, BU B wants the event after the Q3 product release). Technique: backward planning from the corporate OKR. You start from the corporate OKR for the quarter/year, identify which date maximizes the contribution to the aggregate OKR, and formalize it in the MOU. If the BUs continue to diverge, escalate to the executive sponsor with the OKR-aligned document in hand.

Conflict 4 - Narrative. Two BUs want to tell the story of the event in divergent ways (see cornerstone, competing narratives section). Technique: signed narrative statement (see cornerstone) + co-branded communication (never one BU before the other in official press releases, alphabetical order). Documented in the MOU and rigorously enforced.

Operational steps: from the map to the signed MOU

The sequence that follows is the concrete deliverable of this guide. It is typically run between T-12 and T-6 weeks before a cross-BU event spanning 2-4 units, or at the start of an annual cross-BU program. Indicative total time: 8-12 full-equivalent days of the senior coordinator's work spread across 4-6 weeks of elapsed time (because many activities depend on executive calendar slots that don't free up immediately).

Step 1 - Extended stakeholder map (days 1-3)

The extended map is built in three successive steps. First: for each BU involved, identify the three vertical levels (executive sponsor, team lead, contributors) using the corporate org chart (Workday, BambooHR, intranet). Second: for each stakeholder thus identified, assign the quadrant of the 2x2 matrix (influence × interest) through direct questions to the BU's team lead (e.g. who blocks your decisions? who unblocks them? who is in a position of formal veto?). Third: assign the DACI role on the event's main decision.

The deliverable is a shared spreadsheet (Google Sheets, Excel via SharePoint, or a Notion table) with six columns: name, corporate role, BU of belonging, 2x2 quadrant, DACI role, notes (a free field for relevant details). Typically 17-22 rows for a cross-BU event spanning 2-4 units.

A decisive sub-step is verification with a third party for each BU: bringing the map to each BU's team lead and asking who is missing?. Almost always 1-2 names per BU emerge that the senior coordinator did not know about - typically middle managers with informal power or relevant external consultants. Ignoring them produces political surprises; mapping them drastically reduces the risk.

An optional sub-step for 3-4 BU events is the inter-BU influence matrix (see framework). It is filled in privately (not shared) and is the most politically sensitive document: recognizing informal connections is a leverage tool, but if it leaks it can produce defensive reactions.

A practice often skipped is verifying the DACI role with the stakeholder themselves. Assigning a DACI role without confirming it directly with the person produces misaligned expectations: the senior thinks X is an Approver, X doesn't know they are one, and the decision that requires X's approval gets stuck. The practice that works is a 4-5 line email to each stakeholder with an assigned DACI role that says For this decision, I have identified you as [role] with [specific responsibility]. Confirm or suggest corrections within 48h. The responses should be archived.

For the L3 senior level, the extended map is not a static deliverable but a continuous working tool: it is updated every 4-6 weeks throughout the life of the event or cross-BU program. Typical changes: new stakeholders emerge (an external consultant who gets involved at T-8 weeks), existing stakeholders change quadrant (a team lead who was initially Manage Closely and after 4 weeks becomes Keep Informed because the critical phase of their BU has passed), stakeholders exit (an internal promotion moves a person outside the event's perimeter).

Step 2 - Identification of potential conflicts (days 4-5)

After completing the map, you apply the conflict taxonomy (scope, budget, timing, narrative) to proactively identify the points of divergence. For each pair of BUs involved, you explicitly write down: the points of alignment (what both want), the points of possible divergence (what one BU wants and the other might contest), and the points of certain conflict (what has already emerged in informal conversations).

The deliverable is a 1-2 page document for each BU-BU pair: a 2-BU event produces 1 document (A-B); a 3-BU event produces 3 documents (A-B, A-C, B-C); a 4-BU event produces 6 documents. This combinatorial growth is one of the reasons why 4+ BU events are almost always sub-optimal: the senior coordinator does not have the capacity to manage 6+ cross-BU relationships. The rule of thumb: a maximum of 3 BUs per cross-BU event; if there are 4+, split into two separate events or promote one BU to "primary BU" and the others to "participating BUs" (with lower decision weight).

A useful sub-step: identifying the latent conflicts that have not yet surfaced. Typically these are narrative conflicts (who takes credit for the event) and scope conflicts in adjacent areas (e.g. the event is formally cross-BU but one BU will use it to advertise its own technical leadership). Recognizing a latent conflict 6-8 weeks in advance allows you to prevent escalation into a visible crisis.

Step 3 - Conflict resolution framework (per conflict: 60-90 minutes)

For each conflict identified in step 2, the senior coordinator applies a framework structured in five steps that translates the political conflict into a quantitative, OKR-based trade-off. The framework is a synthesis of Atlassian's DACI and of the principled negotiation model of Fisher & Ury (Getting to Yes, 1981, still the international reference).

Step 3.1 - Reframe in OKR. You translate the conflict from subjective positions ("BU A wants X, BU B wants Y") into measurable contributions to the corporate OKR ("X contributes to OKR Z with value Vx; Y contributes to OKR Z with value Vy"). This reframing transforms the negotiation from "who has more political power" into "which option maximizes aggregate value".

Step 3.2 - List alternatives. You produce at least three alternatives beyond the original two: in addition to X and Y, you propose Z (structured compromise), W (temporal sequencing), V (scope split). Having 5 alternatives instead of 2 destroys the binary dynamic of the negotiation and opens up the decision space.

Step 3.3 - Quantitative scoring. For each alternative, you evaluate it on 3-5 quantitative criteria (OKR contribution, cost, risk, time feasibility, political acceptability) on a 1-5 scale. You obtain an aggregate score per alternative.

Step 3.4 - DACI decision. The Driver (typically the senior coordinator) prepares the proposal document; the Approver (typically the executive sponsor or the steering committee) approves or defers with structured feedback; the Consulted (the BU team leads) have the power of explicit objection (a 24-48h review window); the Informed receive the final communication after the decision.

Step 3.5 - Documentation. The decision is archived in the MOU as a decision log: date, conflict, alternatives considered, scoring, decision, owner. The history of decisions is essential for consistency in subsequent decisions and for the post-mortem.

A variant of the framework for urgent conflicts (deadline within 72h) is fast-track conflict resolution: you compress the five steps into a single 60-minute call, with all the relevant DACI stakeholders present, and you force the decision by the end of the call with a structured vote (the Approver decides, the Consulted have 15 minutes to object before the vote). The fast-track is effective only if the stakeholders have already internalized the standard framework: applying the fast-track to a team that has never seen the framework produces rushed decisions and low commitment.

A practice complementary to the framework is the post-execution decision review: 2-3 weeks after a contentious decision has been implemented, you hold a 30-minute review with the DACI stakeholders to assess whether the decision turned out to be correct (based on post-implementation data). These reviews produce bidirectional learning: the senior coordinator understands which scoring criteria are predictive, and the stakeholders see that decisions are evaluated after the fact and feel more committed to subsequent decisions.

Step 4 - Internal cross-BU MOU (days 6-10)

The internal MOU (Memorandum of Understanding) is the final deliverable of the L3 framework. A 2-3 page document, signed by all the executive sponsors of the BUs involved, that formalizes: (a) the mission of the cross-BU program (narrative statement, see cornerstone); (b) the allocation of shared resources (budget split, team contribution, vendor sharing); (c) the governance rules (steering committee cadence, alternating co-chairs, anti-fatigue rules); (d) the escalation paths (who decides what in case of divergence, with timing within 48h); (e) the exit strategy (conditions for terminating the program); (f) the initial decision log with the decisions already made.

The MOU is not a legal contract (it does not go through legal), it is a documented political agreement. Its value is declarative: writing and signing the MOU forces the sponsors to make explicit rules that would otherwise remain implicit, and it creates a concrete reference tool when the rules are violated (you can always say in the MOU we wrote that...).

Compiling it typically takes 4-6 hours spread across 2-3 sessions with executive sponsors. A practice that works is the MOU drafting workshop: a 90-minute session in which the senior coordinator brings a pre-filled skeleton and the sponsors discuss it section by section. The most debated sections are typically budget allocation and escalation paths; the least debated sections are mission and exit strategy (because they are abstract). The rule of thumb: the escalation path must specify a name (not just a role) and a time window within 48h.

A section of the MOU often underrated is the communication protocol: who talks to whom, on which channels, with what frequency. Examples: Steering committee decisions are communicated to the teams via email within 24h of the meeting; Conflicts that require escalation use the dedicated Slack channel #event-cross-bu-escalation, never personal DMs; Informal meetings between team leads do not produce binding decisions unless archived in the decision log within 48h. Formalizing the communication protocol prevents one of the most frequent causes of misunderstanding: decisions made in one channel and re-interpreted in another.

A practice for validating the MOU before signing is the tabletop exercise: the senior coordinator proposes 3-4 plausible conflict scenarios to the sponsors (e.g. BU A proposes postponing the event by 4 weeks to align with the launch of its own product; BU B objects because it would lose the Q3 sales push window) and applies the MOU to resolve them on paper. If the MOU does not resolve one or more scenarios, it must be amended before signing. 60-90 minutes of tabletop exercise save weeks of later renegotiation.

Step 5 - Quarterly MOU review (ongoing)

The MOU is not static: it is reviewed quarterly in the steering committee to update the decision log and redefine any obsolete rules. The quarterly review lasts 45-60 minutes and has three outputs: (a) the quarter's decisions added to the decision log, (b) any MOU rules modified (with explicit justification), (c) verification that the escalation paths worked (if they were activated, how long they took, whether they produced a timely decision).

The quarterly review is also the moment to verify the health of the cross-BU program: NPS between the BUs, satisfaction of the events team, attendance of the steering committee. Health metrics below threshold (e.g. NPS below 60, steering committee attendance below 80%) trigger corrective actions - the most frequent being a review of the MOU to identify rules that aren't working.

A useful extension of the quarterly review is the open MOU revision window: one week a year (typically the first of January) in which any stakeholder can propose changes to the MOU. The proposals are collected in a shared document, discussed in a 90-minute workshop, and a revised MOU is signed at the end of January. This scheme prevents the pattern of a rigid MOU that becomes obsolete: the formalized annual opening keeps the document alive and maintains the sponsors' commitment to its applicability.

A final advanced practice for recurring annual cross-BU programs (3+ consecutive years) is MOU lineage: archiving the successive versions of the MOU so that it is possible to read the program's evolutionary history. The lineage is precious at the moment of the senior coordinator's succession planning: whoever takes the role after you has visibility into how the rules came about, why they changed, and which experiments failed. Without lineage, every new senior re-initializes the program from scratch.

Real-world cases: Spotify, Atlassian DACI, GitLab Handbook, Harvard Business Review

Four tier-1 case studies, chosen because they cover different modes of cross-functional stakeholder management: Spotify (squads/tribes/chapters as a structural model), Atlassian (DACI as a decision framework), GitLab (radically transparent), HBR (academic research).

Spotify is the structural reference (how to organize the company to reduce conflicts). For the framework for individual decisions, the reference is Atlassian.

Atlassian DACI is the framework for individual decisions. For the radically transparent version of the concept, the reference is GitLab.

The fourth case study is a piece of academic research that provides the conceptual framework for the three previous ones.

Three additional sources for those who want to go deeper: Getting to Yes by Roger Fisher, William Ury, Bruce Patton (Penguin, 2011 ed.) - the international reference on principled negotiation, directly applicable to cross-BU conflict resolution; McKinsey Insights in the Organization category has annual reports on cross-functional teaming with international benchmarks; Atlassian Team Playbook - Working Agreements for the group-agreements pattern applicable to a cross-BU events team.

Anti-patterns and how to recognize them

The senior anti-patterns in cross-BU stakeholder management are different from the mid ones (see cluster L2-C2): they are not about the difficulty of mapping stakeholders, but about the difficulty of resolving conflicts with declared frameworks. They are the patterns that block the senior's growth toward the executive level.

Templates, checklist, and next steps

The template that makes the difference at the L3 stakeholder management level is the cross-BU RACI, downloadable from the templates portal. It is the extended version of the canonical RACI (see cornerstone) with additional columns for: the stakeholder's BU of belonging, the DACI role on the main decision, the review window (for the Consulted) or the information window (for the Informed).

The personal growth path from the L3 senior stakeholder level toward L4 executive includes three conceptual transitions. First: from the internal cross-BU MOU to the corporate governance framework (a policy that applies to all events, not to one specific event). Second: from 1:1 negotiation with executive sponsors to board-level negotiation with the C-suite (CEO, CFO, COO). Third: from reactive conflict resolution to structural conflict prevention (changing the org design to reduce latent conflicts).

For those who want to deepen their formal training on the topic, two readings and one certification. Getting to Yes by Fisher, Ury, Patton (Penguin 2011) - the international reference on principled negotiation; required reading for anyone negotiating cross-BU beyond 12 months. Crucial Conversations by Patterson, Grenny, McMillan, Switzler (McGraw-Hill, 2021 ed.) - on difficult conversations applied to the corporate context; a book that changed the way I structured my steering committee sessions. The certification with the most value at the L3 level is, paradoxically, the Certified ScrumMaster from the Scrum Alliance: not because Scrum applies to an events portfolio, but because Scrum training is the single most effective training on the facilitation of multi-stakeholder groups.

The most effective practical experience for consolidating the L3 stakeholder level: facilitating 3-4 cross-BU steering committees of an annual program, taking detailed notes on how latent conflicts manifest. 12 months of continuous facilitation produce more growth than three formal training courses.

What I learned writing this