Executive - Securing Sponsorship for Cross-BU Initiatives

TL;DR

A cross-BU events initiative without explicit C-level executive sponsorship has - according to aggregate PCMA post-mortem statistics - a 60-70% probability of being scaled back or cancelled before go-live. The reason is structural: when two or more BUs have to allocate budget and resources to a shared event, there is inevitably a moment (typically around week 4-6 of the plan) when priorities diverge. Without an executive sponsor who can perform the political arbitration, the BU facing a local emergency pulls out, the other is left stranded, and the event shrinks. The sponsor is not a ceremonial title: it is a person who can literally call two VPs and say "this event is happening."

The 60-70% failure statistic for absent sponsorship is striking when compared to the average difficulty of securing explicit sponsorship in EU tech scale-ups: the same PCMA estimates that fewer than 25% of cross-BU initiatives in scale-ups with < 1000 employees have sponsorship formalized in writing at kickoff. The gap between "obvious need" and "actual practice" is enormous - and the L4-C2 domain exists precisely to close that gap with disciplined tooling.

This guide covers the L4-C2 domain of the Event Builder Track: how a Head of Events (or equivalent - Director Strategic Events, VP Brand Experience, Chief of Staff) secures, formalizes and maintains explicit C-level sponsorship for cross-BU initiatives. It is organized into five blocks: (1) the sponsor pre-qualification framework (who is the "right" sponsor for which type of event); (2) the sponsorship pitch deck in 7 slides; (3) the formalization tools (internal MOU, executive RACI, escalation path); (4) maintaining sponsorship throughout the cycle (the three monthly conversations that prevent "sponsor drift"); (5) the company politics you must navigate so you don't burn out your sponsor. Primary sources: HBR on executive sponsorship and cross-functional initiatives, the Atlassian Team Playbook (the Sponsor Buy-In play), the GitLab Handbook (cross-functional decision rights section), and PMI's Pulse of the Profession on the success drivers of cross-functional projects.

When you need it / Prerequisites

This guide is relevant in five recurring scenarios:

• You are planning a cross-BU event for the first time (e.g. a joint Marketing + Sales + Customer Success summit) and haven't yet identified the C-level sponsor.
• You have a formally assigned sponsor but they are "TBD" or passive: they appear on slides but not on the calendar; they don't respond to weekly updates; they don't step in when the two VPs involved negotiate laterally.
• Last year's event went badly because one BU scaled back, and the debrief identified "lack of sponsorship" as the primary cause. You need to rebuild organizational trust.
• You are negotiating the annual portfolio (see L4-C1 - Annual portfolio strategy) and for each cross-BU tentpole you must assign a sponsor before the portfolio is signed off.
• You are new in the role and need to understand how company politics work at your new employer before requesting sponsorship for your first initiative.

Prerequisites for the reader:

• Having access (or the ability to request it) to a C-level executive - CEO, CFO, CMO, CRO, CHRO. If the top of your reporting chain is a Senior Director with no direct line to the C-suite, you are in a context where L4-C2 doesn't apply yet - you are typically in a company with < 200 employees where the sponsor is implicitly the CEO by default.
• Having consolidated the foundational L3 mechanisms (cross-BU RACI, 1-pager brief, stakeholder map). Without these tools, the sponsorship pitch falls flat because you lack the baseline documentation the sponsor expects.
• Being familiar with company politics - knowing who the real decision-makers are behind the formal ones, understanding the organization's "turf war" history (who doesn't talk to whom, which BUs are in structural competition for budget). This knowledge is not cynicism: it is an operational prerequisite.

Conceptual framework

The framework I propose is called the 3-Layer Sponsor Map and rests on three converging sources:

• HBR - "The Critical Role of Executive Sponsorship" (Prosci research + HBR Online, a recurring theme from 2010 to today): a consistent body of research shows that projects with active sponsorship have success rates 3.5× higher than those with sponsorship "in name only." The difference between "active sponsorship" and "in name only" is measured across three dimensions: time invested (≥1h/month in 1-on-1s), visible participation (kickoff + go-live + post-mortem), and political arbitration (documented intervention when two VPs diverge).
• Atlassian Team Playbook - the Sponsor Buy-In play: the Atlassian playbook includes a 90-minute play for "selling" an initiative to a potential sponsor. The structure is: 15 minutes of context + 30 minutes of problem framing + 30 minutes of proposal + 15 minutes of explicit ask (what you need from them in terms of time, political capital, decisions). The key Atlassian point: the explicit ask is not the generic "I'd like your support" - it is a numeric, calendared request.
• PMI Pulse of the Profession: PMI's annual report consistently identifies "lack of executive sponsorship" as one of the top 3 causes of project failure. The PMI framework breaks sponsorship into three roles: Initiating sponsor (who authorizes the start), Sustaining sponsor (who protects the project throughout the cycle), Closing sponsor (who validates the close). They can be the same person or three different people - but if the three roles aren't clearly allocated, the project suffers.

By overlaying these three sources, I arrive at the 3-Layer Sponsor Map:

1. Layer 1 - Identification: who is the "right" sponsor for this specific initiative? The criterion is not hierarchy (the highest available C-level) but strategic fit: the sponsor is whoever has decision authority over the primary company OKR the event serves. If the event serves a pipeline OKR → the sponsor is the CRO. If it serves an employer-branding OKR → the sponsor is the CHRO. If it serves a product-feedback OKR → the sponsor is the CPO. Getting the strategic fit wrong (e.g. the CEO as sponsor of an event that is actually CRO-centric) produces weak sponsorship even if it is hierarchically senior.
2. Layer 2 - Pre-qualification: before the official pitch, I verify that the sponsor has the capacity to intervene. The three pre-qualification questions: (a) does the sponsor have realistic time over the next 6 months (no ICO/IPO/M&A in progress that will absorb their entire agenda)? (b) does the sponsor have a pre-existing relationship with the VPs of the BUs that will need to collaborate? (c) does the sponsor have enough political capital to perform the arbitration (are they not recently in conflict with one of the VPs involved)? If even one answer is no, the sponsor is the "wrong fit" even if they are the "right hierarchical fit."
3. Layer 3 - Formalization: sponsorship is formalized through three artifacts: (a) a one-page internal MOU signed by the sponsor + me as Head of Events; (b) an executive RACI (the sponsor is A on strategic decisions, R on no tasks - they are not an operational executor); (c) a written escalation path (in case of a VP-VP conflict, the escalation order is: first an informal conversation between the two VPs within 5 days → if unresolved, Head of Events mediation within 3 days → if unresolved, sponsor intervention with a binding decision within 7 days). Without formalization, sponsorship stays verbal and gets forgotten.

The framework doesn't guarantee success - it guarantees visibility. If after three months the sponsor isn't investing the promised 1h/month, the framework makes that observable. Then you can decide whether to renegotiate (sponsor in burnout, reduce expectations) or replace (the sponsor wasn't the right strategic fit, identify an alternative).

An important consideration is the distinction between "initiative sponsor" and "portfolio sponsor." The 3-Layer Sponsor Map framework is optimized for the former - a specific cross-BU initiative lasting 6-9 months. The latter case (sponsor of the entire annual portfolio, see L4-C1) is structurally different: it is typically the CFO or the CMO, has a continuous relationship with the Head of Events, and the cadence is not 1h/month but 30 min/week. The two forms of sponsorship coexist: the portfolio sponsor provides macro cover, the initiative sponsors provide micro cover. Confusing them - asking the portfolio sponsor to arbitrate a single VP-VP conflict, or asking the initiative sponsor to approve the aggregate rationale - produces frustration on both sides.

A second framework concept worth spelling out is the notion of "political capital." The sponsor doesn't only invest time: they invest political capital - their own organizational credibility, which is consumed with every arbitration intervention. If a C-level sponsor steps in three times in a quarter to arbitrate VP-VP conflicts within the same initiative, they are implicitly saying "this initiative is my top priority." This is a precious asset that the sponsor distributes across a handful of initiatives per year - typically 2-3. If you ask a C-level to sponsor your initiative, you must be honest about the fact that you are asking for a slice of their total political capital for the year. This honesty changes the pitch: you aren't just asking for 8h of time, you are asking for a 20-30% slice of their annual "arbitration budget." Acknowledging this explicitly in the pitch (slide 5) increases the quality of the yes you get.

A third useful concept is the "sponsor stack": the idea that a cross-BU initiative can have a primary sponsor + a backup sponsor. The primary does the active arbitration work; the backup is an "insurance policy" if the primary becomes unavailable (e.g. internal promotion, M&A in progress, medical leave). The sponsor stack is particularly useful in long cycles (12+ months) or in companies with high C-level turnover. The operating rule: the backup must be briefed at the start of the cycle (a 30-minute coffee where they receive the executive summary) even if they aren't actively engaged - this dramatically reduces activation time if needed.

Operational steps

Eight operational steps, each with an estimated time and documentary output. Times are calibrated for a Head of Events at an EU tech scale-up with moderately formalized culture; they scale down for more informal startups and up for structured multinationals.

1. Step 1 (1-2 days) - Map OKRs → potential sponsors. For the cross-BU initiative you have in mind, identify the primary company OKR it serves. From there, map the 2-3 C-levels who have decision authority over that OKR. Example: a cross-BU "customer summit + product feedback day" event → primary OKR "expand product-market-fit in the mid-market segment" → sponsor candidates: CPO (primary, owns PMF), CRO (secondary, cares about the resulting pipeline), CMO (tertiary, cares about the brand). Output: sponsor-candidates-mapping.md with 2-3 prioritized names.
2. Step 2 (2-3 days) - Pre-qualification. For each of the 2-3 candidates you apply the Layer 2 filter. Typically you have 1-2 informal chats (15-minute coffee) with their chief of staff or EA to verify realistic availability, pre-existing conflicts, and a free agenda over the next 6 months. Output: sponsor-prequalification-notes.md with non-fit candidates eliminated.
3. Step 3 (3-4 days) - 7-slide pitch deck. Build the pitch for the final sponsor candidate. Canonical structure: Slide 1 - Problem (what cross-BU problem needs solving); Slide 2 - Proposed solution (what the event is); Slide 3 - Strategic value (mapping to the primary OKR); Slide 4 - Investment required (aggregate budget + team-weeks from which BU); Slide 5 - Sponsorship ask (what exactly I'm asking for: time, political capital, decisions); Slide 6 - Risks (top 3); Slide 7 - Timeline (kickoff + 3-4 milestones + go-live + post-mortem). Output: sponsor-pitch-deck.pdf.
4. Step 4 (1 hour) - Pitch meeting. 60 minutes on the calendar with the sponsor candidate. Atlassian structure: 15 min context, 30 min problem + proposal, 15 min explicit ask. The ask is not "I'd like your support" - it is: "I'm asking you for (a) 1h/month of 1-on-1 from May to December, (b) visible participation at kickoff and go-live, (c) the ability to intervene with the two VPs involved if they diverge." Output: sponsor-pitch-meeting-notes.md with the sponsor's answer (yes/conditional/no).
5. Step 5 (2-3 days) - Formalization: MOU + executive RACI + escalation path. Once you have the verbal "yes," I formalize the agreement in three written artifacts. A signed one-page internal MOU (digital or paper). An executive RACI with the sponsor as A on strategic decisions. A written escalation path shared with the VPs involved as the "rule of the game" before any conflict. Output: sponsor-MOU.pdf, executive-RACI.xlsx, escalation-path.md.
6. Step 6 (1 hour/month × 8 months) - Monthly 1-on-1 cadence. Calendar blocked for 1h/month for the next 8 months. Fixed agenda: (a) Status update 10 min - where we are on the timeline; (b) Risks 15 min - top 2-3 that surfaced this month; (c) Decisions needed 20 min - what to decide today that requires you; (d) Open Q&A 15 min - anything else. Monthly output: sponsor-1on1-YYYY-MM.md.
7. Step 7 (variable) - Escalation activation when needed. When the two VPs diverge (typically week 6-8 and week 14-16 of the cycle), you activate the escalation path. First VP-VP conversation 5 days; if unresolved, you step in as mediator for 3 days; if unresolved, you escalate to the sponsor with a binding decision within 7 days. Document everything in escalation-log.md: the log is the evidence that sponsorship was active, not just present on paper.
8. Step 8 (1 day) - Post-mortem sponsor inclusion. The event post-mortem includes a dedicated "Sponsor effectiveness review" section. Questions: did the sponsor invest the promised 8h? did they intervene when necessary? did their political capital grow or get consumed? would they be willing to take on the role again for edition N+1? Output: post-mortem-sponsor-section.md integrated into the overall post-mortem.

The operational total is roughly 10-15 person-days of active work spread over 8-9 months (from pre-pitch to post-mortem). Plus 8h of the sponsor's time (the monthly 1-on-1s). It's a significant cost but far lower than that of a cross-BU event that fails for lack of political arbitration.

A critical operational note for Step 7: the clean escalation rule. When you activate the sponsor for arbitration, you must present the decision in binary or ternary format (max 3 options), each with pros/cons/cost/timeline. Never present "we don't know what to do" - that's a way to consume the sponsor's political capital without making it count. The rule: the sponsor decides between pre-formulated alternatives, they don't receive problems for them to formulate.

A second detail on Step 5 (formalization): the internal MOU works best if it is genuinely one page and includes a calendar of "review checkpoints" - specific dates when sponsor and Head of Events re-meet to confirm that mutual expectations remain sustainable. Typically three checkpoints for an 8-month cycle: kickoff (month 0), mid-cycle (month 4), pre-launch (month 7). These checkpoints are different from the monthly 1-on-1s - they are points of explicit MOU renegotiation.

A third important detail concerns the preparation of sponsor onboarding material. Step 5 (formalization) implicitly includes an onboarding kit the sponsor receives when signing the MOU: (a) a 1-page executive summary of the project; (b) a visual timeline with the 4-5 key milestones highlighted; (c) a list of the 3 biggest risks with their mitigation plan; (d) a brief profile of the two VPs involved (background, quarter's OKR, decision style - useful for the sponsor who doesn't work day-to-day with both); (e) a link to the dedicated Slack channel where they will receive updates without having to ask. This onboarding kit, reduced to 5 documents, lets the sponsor "get into the project" in under 30 minutes - a minimal investment for the Head of Events but very high perceived value for the sponsor.

A fourth operational detail: the cadence of "kudos updates." Once a month, in addition to the 1-on-1, I send the sponsor a brief "kudos update" via email or Slack - a paragraph documenting a small recent win attributable (even if only partly) to their political cover. Example: "this week the VP Marketing unblocked the additional €15k budget for the summit's expo hall - I think the meeting you had with him on Tuesday helped. Thank you." This seemingly small gesture has disproportionate effects on sponsor engagement: it shows them that their time investment produces observable results, and it builds the relational "muscle memory" that makes the sponsor want to keep investing because they perceive a return. It's not manipulation - it's simply attributing credit correctly.

A detail on Step 4 (pitch meeting): personally I find it useful to do a dry-run of the pitch with my direct manager (or with a Head of Events colleague from another BU if available) 24-48h before the official pitch. The dry-run is an hour dedicated to stress-testing slide 5 (the sponsorship ask) - it's the slide on which the pitch can fail, because a vague or unrealistic ask makes the candidate look unserious. The dry-run surfaces ambiguities that should be ironed out before the real meeting.

Deep dive: navigating company politics without burning relationships

The most delicate point of the entire L4-C2 domain is company politics. The word has a negative connotation in many cultures (especially Italian, where "political" is often pejorative) but it is simply the neutral description of the dynamics of power, resource allocation and influence in any organization of >100 people. A mature L4-C2 doesn't avoid politics - they navigate it consciously.

Five political patterns I've seen recur in cross-BU sponsorship contexts:

Pattern 1 - "Dominant BU with reluctant sponsor." One BU is clearly dominant in the company (e.g. the CRO holds 60% of the budget and the CEO's attention). Your event primarily serves the CRO but for reasons of "organizational fairness" the CMO is named co-sponsor. The CMO knows they are politically "the younger sibling" and becomes a passive sponsor. The fix: renegotiate the sponsorship structure, making the CRO explicitly primary and the CMO informed (RACI-I), not co-A. Formal parity can be less useful than honest transparency.

Pattern 2 - "Sponsor in a vulnerable position." The sponsor you've identified recently joined (e.g. CRO in post for 4 months) or is in a precarious position (e.g. their department just missed a critical OKR). In both cases the sponsor needs quick "wins" to consolidate their position. This is both an opportunity and a risk: an opportunity because the sponsor is motivated to support initiatives that bring them visibility; a risk because they may demand changes that alter the scope to maximize their personal benefit rather than company value. The fix: be explicit about the success narrative - which "win" the event will bring the sponsor, and what internal narrative you want to build post-event.

Pattern 3 - "Historical conflict between the two BUs." The two BUs involved have a history of conflict (e.g. loss of decision territory, budget cuts in favor of the other, public episodes of tension between the two VPs). In these cases, any cross-BU initiative inherits the underlying conflict. The fix: before pitching the sponsor, run an informal round of "temperature checks" with the two VPs to understand whether they are willing to co-invest in this specific initiative. If the answer is ambiguous, postpone the initiative by a quarter and first repair the VP-VP relationship (perhaps via a smaller pilot micro-initiative).

Pattern 4 - "Sponsor with a hidden agenda." The sponsor accepts the role but with an undeclared parallel agenda (e.g. using the event as a stage to pre-announce an organizational restructuring, or using the budget as an "umbrella" for expenses that belong elsewhere). The pattern is rare but real. The defensive fix: the internal MOU must spell out scope and budget cap so that unilateral changes require formal renegotiation. If the sponsor starts modifying the agenda without renegotiation, you have a warning signal to take seriously.

Pattern 5 - "Sponsor who becomes the bottleneck." The sponsor starts with good intentions but discovers that the volume of decisions being escalated to them is excessive. They start responding slowly, decisions pile up, the initiative slows down. The fix is proactive: after the first two months, run an explicit review of the effective load - if more than 1 decision/month is being escalated, you have a design problem in the mediation layer (Head of Events) or in the VP-VP layer. Revisit the RACI to push more decisions downward before they become crises.

A personal note: company politics is not symmetric across roles. An external L4 (recently hired, < 12 months in the company) has very low initial political capital and must build it with micro-wins. An internal L4 (promoted, > 3 years in the company) has accumulated political capital but risks being perceived as "part of the system" if their cross-BU initiatives don't produce real value. Both can operate at L4-C2 successfully, but with different styles: the external must be more rigorous about frameworks (to compensate for the lack of relational capital), the internal can be more informal (because relational capital is part of the fix).

Real cases: Atlassian Team Playbook, GitLab Handbook, HBR research

Three case studies that cover three complementary dimensions of the sponsorship problem: the first is the operational framework (Atlassian), the second is decision transparency as a sponsorship asset (GitLab), the third is the documented failure of weak sponsorship at enterprise scale (HBR, research-based).

GitLab offers a different case: sponsorship as a function of decision transparency. At GitLab, all cross-functional projects have a publicly documented DRI in the Handbook, and sponsorship is a separate layer (usually attributed to a Director or VP).

The third case study is less celebratory but more instructive: a documented failure in HBR research on how weak sponsorship produces walking-dead projects.

The three case studies cover three complementary angles: Atlassian provides the replicable operational framework, GitLab shows decision transparency as a multiplier, and HBR quantitatively documents the differential value of active sponsorship. None of the three is transferable one-to-one into your company's reality - but each offers an extractable pattern of thinking. From Atlassian take the 90-minute play as a pitch template; from GitLab take the idea of making cross-functional decisions public (at least internally); from HBR take the quantitative business case for convincing a skeptical CFO.

Three additional sources to go deeper: the Prosci research repository (the most complete database in the world on sponsorship effectiveness, partially gated); the PMI Learning Library for the structured frameworks on Initiating/Sustaining/Closing sponsors; the full GitLab Handbook to see the transparent decision-rights pattern applied.

Anti-patterns and how to recognize them

Six anti-patterns observed repeatedly in EU scale-ups that try to scale their cross-functional model without maturing the sponsorship system.

Templates, checklist and next steps

The central template for the L4-C2 level is the cross-BU RACI extended to the executive layer, which explicitly includes the sponsor row with its specific RACI assignments (A on strategic decisions, R on no tasks, I on all milestones). The base template - the operational cross-BU RACI - is already part of the series' template pack.

Two other templates the L4-C2 level uses recurrently: the internal sponsor MOU (a 1-page template with Objective, Sponsor commitment, Escalation path, Review checkpoints, and Signatures sections) and the 7-slide pitch deck (an Atlassian-compatible version of the Sponsor Buy-In play). Both are on the roadmap as part of the premium template pack - their backend endpoint is gated 403 until the commercial go-live of Phase 19. Reference these templates in your plans knowing the unlock is coordinated with the series' pricing.

The personal growth path from L4-C2 has three directions. If your initiative requires aggregate budget and formal governance, the next is L4-C3 - Building an events governance framework. If you want to consolidate the strategic dimension of the annual portfolio, go to L4-C1 - Annual portfolio strategy. If you want to learn to position events as an internal-brand lever, go to L4-C4 - Events as a lever for internal brand and engagement.

For those who want to dig into the theoretical foundation and the practice, three external resources are particularly relevant for L4-C2: Atlassian's Sponsor Buy-In play (with a free downloadable worksheet); the HBR article "The Most Overlooked Leadership Skill" and related articles in the Managing People category; and the book Influence Without Authority by Allan Cohen and David Bradford (2005, Jossey-Bass) - focused on negotiating sponsorship in contexts without direct hierarchical authority. For those operating in the Italian market, the PMI Italian Chapter periodically runs workshops on executive sponsorship with Southern-EU market benchmarks.

A consideration on how this guide applies to different reader career stages: for a Head of Events entering the role (first 12 months), the priority is to apply Steps 1-5 rigorously even on small initiatives - building muscle memory before tackling critical ones. For an experienced Head of Events (3+ years in the role), the priority is to optimize Steps 6-8 (1-on-1 cadence, clean escalation, post-mortem) because the first 5 steps become automatic. For a veteran Head of Events (5+ years or multiple mandates), the priority is transmitting the framework to the team - training the Senior Coordinators (L3) on the Sponsor Map so they can support the cross-BU initiatives under their responsibility without having to escalate to the Head of Events every time.

A concluding observation: cross-BU sponsorship is probably the area where different corporate cultural systems diverge most radically. US-tech-coast companies (Atlassian, GitLab, Stripe) have a culture of explicit, documented sponsorship. Continental-EU companies (especially German- or French-rooted ones) have a more hierarchical culture where the sponsor is implicit in the reporting chain. Italian / Mediterranean companies have a more relational culture where sponsorship is informal and plays out on personal relationships. Three different cultures, three different L4-C2 styles. This guide is written in the US-tech-coast style (explicit, documented, framework-based) because that's what produces reproducible data - but if you operate in a different culture, apply the framework as direction and adapt the style to local reality.

What I learned writing this