GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — Add pattern: Sponsor Communication and Engagement by shrutibist · Pull Request #932 · InnerSourceCommons/InnerSourcePatterns ConversationA 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
requested review from
NewMexicoKid,
cewilliams,
lenucksi,
robtuley,
spier and
yuhattor
as code owners
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Member
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
amburi
reviewed
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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. All reactions
Uh oh!
There was an error while loading. Please reload this page.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ack. I can update to a combined entry-
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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
Contributor
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Author
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
Contributor
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
Reviewers1 more reviewerUh oh!
There was an error while loading. Please reload this page. AssigneesNo one assignedLabels
1-initial
ProjectsMilestoneNo milestoneDevelopmentSuccessfully merging this pull request may close these issues. Uh oh!
There was an error while loading. Please reload this page. 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. |