GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Add pattern: Sponsor Communication and Engagement by shrutibist · Pull Request #932 · InnerSourceCommons/InnerSourcePatterns

Conversation

@shrutibist

@shrutibist shrutibist commented Aug 20, 2026

Copy link
Copy Markdown

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
shrutibist added 2 commits August 20, 2026 11:42
@shrutibist
Add files via upload
0515fd0
@shrutibist
Update README.md
99d7810
@shrutibist
shrutibist requested review from NewMexicoKid, cewilliams, lenucksi, robtuley, spier and yuhattor as code owners August 20, 2026 18:56
@shrutibist
Update sponsor-communication-and-engagement.md
570d1e5
@shrutibist

shrutibist commented Aug 20, 2026

Copy link
Copy Markdown
Author

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.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@spier spier added the 📖 Type - Content Work Working on contents is the main focus of this issue / PR label Aug 21, 2026
@github-actions github-actions Bot mentioned this pull request Sep 1, 2026
Monthly Metrics: New Issues + New Pull Requests 2026-08-01..2026-08-31 #934
Open
@spier

spier commented Sep 2, 2026

Copy link
Copy Markdown
Member

Just a quick update @shrutibist, we are aiming to provide feedback on this PR by middle of next week. Thank you for your patience!

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

amburi
amburi reviewed Sep 12, 2026
View reviewed changes

@amburi amburi left a comment

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for contributing this, @shrutibist! 👏

I left a few comments.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

spier reacted with heart emoji
All reactions
  • ❤️ 1 reaction
Comment thread patterns/2-structured/sponsor-communication-and-engagement.md Resolved

Uh oh!

There was an error while loading. Please reload this page.

Comment thread patterns/2-structured/sponsor-communication-and-engagement.md Outdated

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.

@amburi amburi Sep 12, 2026

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@shrutibist shrutibist Sep 13, 2026

Copy link
Copy Markdown
Author

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack. Updated to show this as a Critical foundation instead of a Step1.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread patterns/2-structured/sponsor-communication-and-engagement.md Outdated

**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.

@amburi amburi Sep 12, 2026

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@shrutibist shrutibist Sep 13, 2026

Copy link
Copy Markdown
Author

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack. i will add - A quarterly rhythm balances competing needs: monthly readouts burn sponsor goodwill and don't give enough time for meaningful InnerSource progress (contributions to accumulate, case studies to surface, new teams to enroll), while annual readouts lose momentum and let critical issues slip unaddressed for too long.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread patterns/2-structured/sponsor-communication-and-engagement.md Outdated

**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.

@amburi amburi Sep 12, 2026

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@shrutibist shrutibist Sep 13, 2026

Copy link
Copy Markdown
Author

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack. Added a sentence - That said, this works best once you have built enough trust through a few cycles of sharing accomplishments and getting sponsor input, surfacing bad news to the people who fund you takes credibility first.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread patterns/2-structured/sponsor-communication-and-engagement.md Outdated

**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.

@amburi amburi Sep 12, 2026

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@shrutibist shrutibist Sep 13, 2026

Copy link
Copy Markdown
Author

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack. For example: a vague ask is "Can you help evangelize the program?" A specific ask is "We have a new team in your BU considering an InnerSource project next quarter, could you make an introduction so we can talk through how it works?" The second ask is concrete, tied to a real timeline, and easy to act on.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread patterns/2-structured/sponsor-communication-and-engagement.md Outdated
* **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.

@amburi amburi Sep 12, 2026

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two of the forces ("retrospective vs. forward-looking" and "consistency vs. relevance") are covering similar ground. Could be tightened.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions

@shrutibist shrutibist Sep 13, 2026

Copy link
Copy Markdown
Author

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ack. I can update to a combined entry-
Cadence vs. Forward Momentum: A fixed recurring format builds a predictable rhythm sponsors can rely on, but must prioritize forward-looking conversation (what happens next, what you need help with) over backward-looking review, since sponsors can only influence decisions that haven't yet been made.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
Comment thread patterns/2-structured/sponsor-communication-and-engagement.md

## 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.

@amburi amburi Sep 12, 2026

Copy link
Copy Markdown
Contributor

There was a problem hiding this comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

All reactions
shrutibist and others added 2 commits September 13, 2026 12:45
@shrutibist @amburi
Update patterns/2-structured/sponsor-communication-and-engagement.md
f9061ff
Co-authored-by: Amburi Roy <[email protected]>
@shrutibist
Update sponsor-communication-and-engagement.md with review comments e…
76ed05b
…dits
@spier spier added the 1-initial Donuts, Early pattern ideas, ... (Please see our contribution handbook for details) label Sep 13, 2026
@amburi

amburi commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

@shrutibist Please let me know once you've addressed all the comments, and I'll be happy to take another look and approve the PR. 😊

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@shrutibist

shrutibist commented Nov 10, 2026

Copy link
Copy Markdown
Author

@amburi, all the review comments in this PR was addressed already. Please review and let me know if you see anything that was not addressed. Thanks

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

@amburi

amburi commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

@amburi, all the review comments in this PR was addressed already. Please review and let me know if you see anything that was not addressed. Thanks

Thanks for the confirmation 👍
I will re-review it by next week.

All reactions

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@lenucksi lenucksi Awaiting requested review from lenucksi lenucksi is a code owner
@NewMexicoKid NewMexicoKid Awaiting requested review from NewMexicoKid NewMexicoKid is a code owner
@cewilliams cewilliams Awaiting requested review from cewilliams cewilliams is a code owner
@spier spier Awaiting requested review from spier spier is a code owner
@robtuley robtuley Awaiting requested review from robtuley robtuley is a code owner
@yuhattor yuhattor Awaiting requested review from yuhattor yuhattor is a code owner
1 more reviewer
@amburi amburi amburi left review comments
Reviewers whose approvals may not affect merge requirements

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

Labels

1-initial Donuts, Early pattern ideas, ... (Please see our contribution handbook for details) 📖 Type - Content Work Working on contents is the main focus of this issue / PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Uh oh!

There was an error while loading. Please reload this page.

3 participants

@shrutibist @spier @amburi
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.