Add pattern: Sponsor Communication and Engagement - #932
Conversation
|
The Link Checker failure is unrelated to this PR, it's flagging a pre-existing oreilly.com link in the README's 'What are InnerSource Patterns?' section returning a 403, not anything in this change. |
spier
added
the
📖 Type - Content Work
|
Just a quick update @shrutibist, we are aiming to provide feedback on this PR by middle of next week. Thank you for your patience! |
amburi
left a comment
amburi
left a comment
There was a problem hiding this comment.
Thanks for contributing this, @shrutibist! 👏
I left a few comments.
| └─────────────────────────┘ └─────────────────────────┘ | ||
| ``` | ||
|
|
||
| ## Solutions |
There was a problem hiding this comment.
| ## Solutions | |
| ## Solution |
|
|
||
| Establish a recurring, structured, time-boxed communication cadence with a deliberately chosen sponsor group, built around a consistent, forward-looking readout format with protected space for two-way discussion, rather than relying on ad hoc updates, maximum-seniority sponsor selection, or one-way reporting. | ||
|
|
||
| **1. Choose sponsors for genuine engagement, not maximum seniority.** Name the specific individuals who will fund and organizationally protect the program, but resist the instinct to enroll the most senior possible names (such as business-unit heads) purely for organizational weight. The busiest, most senior leaders often cannot sustain hands-on engagement. Favor engineering leaders, even at a somewhat less senior level, who are known to genuinely believe in cross-team collaboration and are willing to invest real time. A smaller group of engaged sponsors is more valuable than a larger group of nominal ones. |
There was a problem hiding this comment.
Step 1 is the most valuable insight here and it's easy to miss buried in a list. In practice this is the decision that makes or breaks the whole thing — a sponsor who's too senior to show up consistently is worse than no sponsor. Worth calling this out more prominently.
|
|
||
| **1. Choose sponsors for genuine engagement, not maximum seniority.** Name the specific individuals who will fund and organizationally protect the program, but resist the instinct to enroll the most senior possible names (such as business-unit heads) purely for organizational weight. The busiest, most senior leaders often cannot sustain hands-on engagement. Favor engineering leaders, even at a somewhat less senior level, who are known to genuinely believe in cross-team collaboration and are willing to invest real time. A smaller group of engaged sponsors is more valuable than a larger group of nominal ones. | ||
|
|
||
| **2. Hold recurring readouts on a fixed cadence and a fixed, time-boxed format.** A quarterly rhythm balances sponsors' limited time against the need for real depth. Structure each session as a fixed block, for example 40 minutes total, split into a first segment for presentation and a second, equally long segment reserved purely for open sponsor discussion. Protecting real discussion time, not just leaving room for questions at the end, signals that sponsor input is expected and valued, not merely tolerated. |
There was a problem hiding this comment.
"Quarterly" is right for most programs but the pattern doesn't say why. Monthly burns sponsor goodwill; annual loses continuity. A sentence on the reasoning would help someone calibrate for their own context.
|
|
||
| **3. Weight the content toward forward-looking plans, not retrospective reporting.** Keep the look back at the prior quarter brief. The bulk of the presentation time should go to the next quarter's plan, current risks, and specific asks, the things sponsors can actually help shape or influence. A readout that spends most of its time reviewing the past leaves little room for sponsors to meaningfully engage with what happens next. | ||
|
|
||
| **4. Present risks honestly, with mitigation status.** For each identified operational, program, or engineering risk, cover its likely effect (short-term and long-term), the mitigation in progress, and its current status. Sponsors who see risks surfaced proactively, with a credible plan attached, trust the program more, not less, than sponsors who only hear good news. |
There was a problem hiding this comment.
Presenting risks and failures honestly is the right call, but the pattern makes it sound straightforward. In practice, building enough trust to surface bad news to the people who fund you takes time.
Worth acknowledging that step 4 works better once you've had a few cycles of steps 3 and 5 first.
|
|
||
| **7. Protect discussion time as time for sponsors to talk, not just listen.** Treat the second half of the readout as genuinely open, inviting feedback, questions, and pushback, rather than a token space for the meeting to end early. Sponsors who are asked to weigh in build more investment in the program's direction than sponsors who only ever receive a briefing. | ||
|
|
||
| **8. End with specific, concrete asks.** Rather than a general request for "support," ask for something the sponsor can actually do: mentioning the program in a specific upcoming leadership meeting, making an introduction to a team facing a relevant challenge, or resolving a specific organizational blocker. Specific asks are far more likely to be acted on than general ones, and they give sponsors a clear, low-effort way to feel invested in the program's success. |
There was a problem hiding this comment.
On specific asks is the most actionable step in the whole pattern — this is where most programs fail, defaulting to "please support us." A concrete example of what a good ask looks like versus a bad one would make this land.
| * **Advocacy vs. imposition:** sponsors are more willing to evangelize the program to their peers when asked for something specific and modest, but vague or frequent asks for help can feel like an imposition on their time and political capital. | ||
| * **Program-level metrics vs. sponsor-relevant framing:** raw adoption metrics (portal visits, number of projects) are necessary but not sufficient; sponsors respond more to what those numbers mean for risk, cost, and organizational goals they are personally accountable for. | ||
| * **Organizational seniority vs. genuine availability and buy-in:** the most senior possible sponsors (such as business-unit heads) carry the most organizational weight, but are often the busiest people in the company and may not have the bandwidth for sustained, hands-on engagement; moderately senior engineering leaders who genuinely believe in the program may offer less top-level prestige but far more consistent, active support. | ||
| * **Retrospective reporting vs. forward-looking planning:** reviewing the past builds accountability, but spending too much of a limited readout looking backward crowds out the conversation sponsors can actually influence, which is what happens next. |
There was a problem hiding this comment.
Two of the forces ("retrospective vs. forward-looking" and "consistency vs. relevance") are covering similar ground. Could be tightened.
|
|
||
| ## Known Instances | ||
|
|
||
| A large enterprise technology company ran this practice for its CTO-funded InnerSource program. The sponsor group consisted of a handful of senior leaders, the CTO plus several engineering leaders chosen for their genuine belief in cross-team collaboration rather than for holding the most senior title available. The InnerSource program manager held quarterly readouts on a fixed 40-minute format: a 20-minute forward-looking presentation (a brief look back, followed by the next quarter's plan, risks with mitigation status, portal and adoption metrics, and case studies), and a second 20-minute segment reserved for open sponsor discussion and feedback. Over time, sponsors moved from passively approving funding to actively evangelizing the program to their own leadership and peers, and proactively offered help beyond funding. |
There was a problem hiding this comment.
The patterns in #933 PR share the same known instance. They clearly work as a system — would be stronger to say that explicitly rather than having each pattern describe the same company in isolation.
3 participants
A new InnerSource pattern for keeping InnerSource program sponsors (executives and senior engineering leaders) genuinely engaged over time. Covers recurring, time-boxed quarterly readouts with a forward-looking presentation segment and a protected sponsor discussion segment, plus guidance on selecting sponsors for genuine engagement rather than maximum seniority. Includes an anonymized real-world instance.