InnerSource Program Guide for
ISPO/OSPO Leaders
Last Updated: 05/08/2025
Why do firms struggle to adopt Open Source practices internally?
2
Systemic Friction
High friction ecosystems hinder collaboration, drive inefficiency, reduce transparency and create environmental barriers to innovation and reuse.
3
*Source: 2021 Analysis of data, issues and pull requests from Watson NLP GHE repos
Healthy Friction
Optimize infrastructure to reduce friction and create a high collaboration ecosystem that drives innovation and reuse at scale.
4
Remove systemic friction > optimize collaboration
5
*Source: 2021 Analysis of data, issues and pull requests from Watson NLP GHE repos
Long-term commitment
Low-friction Ecosystem
High friction ecosystems force teams to reinvent all the wheels which create redundancy & knowledge silos and reduce knowledge sharing, contribution, reuse & collaboration.
Community Advocacy
Short-term commitment and underinvestment in community enablement increases frustration and hinders knowledge sharing, contribution, reuse & collaboration.
Common Infrastructure
Suboptimized infrastructure lacks consistency, repeatability and standards, which drives friction and impedes knowledge sharing, contribution, reuse & collaboration.
6
↓
Invest in enablement infrastructure supported via program office to scale InnerSource
How can an enablement infrastructure drive reuse and collaboration at scale?
7
Don’t reinvent all the wheels, start with a reuse first mindset, then solve a problem once that solves for many
8
The Mindset
The Approach
InnerSource as an Experience (IaaE) is a programmatic approach to scale InnerSource adoption via a Program Office (ISPO) and enablement platform that maximizes impact by allowing InnerSource Practitioners to solve a problem once that solves many through reuse.
9
The Foundation
Our Practices
Consistency
Work smarter, not harder by optimizing consistency through IaaE program infrastructure, automation, and standardized processes that enable scalability
Repeatability
Remove systemic friction to deliver impact through IaaE program infrastructure by providing standardized processes, patterns and templates that enable scalability
Reuse
Invest in creating and optimizing a low friction, open collaboration environment through IaaE program infrastructure designed for enabling reuse at scale
Community
Build an open collaboration culture using IaaE program ecosystem of InnerSource Practitioners to drive co-creation and reuse at scale
10
Infrastructure
Standardized and optimized for a low-friction experience drives collaboration through IaaE.
Pay-it-forward
High collaboration, low-friction environment drives ROI through IaaE by solving once to solve for many.
Business essential
Low-redundancy environment drives productivity and reduces cost through IaaE.
Bleeding edge
Accelerate research>product integration for an innovation fast-track through IaaE.
The Catalysts
The Benefits
12
Improve productivity
Eliminate ‘reinventing all the wheels’. Optimize to deliver differentiation.
Drive innovation
Access community of global thought leaders, experts and innovators.
Open collaboration
Experiment on new ideas. Solve big problems and pay-it-forward with reuse.
Deliver value
Break knowledge silos to improve quality and accelerate time to value.
How does IaaE enablement infrastructure maximize business impact and deliver value for clients?
13
Enablement Pillars
Program
Consistency
Repeatability
Reuse
Community
Platform
Consistency
Repeatability
Reuse
Community
Practitioners
Consistency
Repeatability
Reuse
Community
↓
IaaE is an open collaboration infrastructure built on three keystone pillars
Metrics that matter
Approach
Adopt, adapt and apply CHAOSS model to IaaE
Guiding Principles
Adopt or reuse existing reporting tools, community data, data sources and types to define, collect and organize metrics for IaaE program levels and project level dashboard
Success Criteria
ROI measured through IaaE enablement infrastructure architected to drive high collaboration and reuse behaviors.
15
*Source: CHAOSS community metrics and models k-base articles https://chaoss.community/kb-metrics-and-metrics-models/
Categories | Goal | Metrics |
Contribution Activity | Drive open collaboration through contributor or contribution growth by measuring Git pull request activity | Platform
Projects
|
Community Engagement | Drive growth and diversity of adoption through increasing awareness and participation and measuring portal activity, site cliqrate, and contributor diversity |
|
Reuse and Collaboration | Drive adoption and reuse via consumption (run once) or continuous adoption (repeat use) by measuring new onboarding, asset/artifact usage, project asset consumption/download and product integration | Platform
Projects
|
Time to Value | Drive value through scaling of workflows for contributors and adopters, and acceleration of innovations into products by measuring velocity, turn-around time and code quality |
|
Metrics that matter
↓
Program and project level metrics guide and chart samples
Contribution Activity
↓
Drive open collaboration through contributor or contribution growth by measuring pull request activity
Platform
Projects
Program Foundation
Metrics that matter
Community Engagement
↓
Drive growth and diversity of adoption through increasing awareness and participation and measuring portal activity, site cliqrate, and contributor diversity
Program Foundation
Metrics that matter
Reuse and Collaboration
↓
Drive adoption and reuse via consumption (run once) or continuous adoption (repeat use) by measuring new onboarding, usage, asset consumption or download and product integration
Platform
Projects
Program Foundation
Metrics that matter
Time to Value
↓
Drive value through scaling of workflows for contributors and adopters, and acceleration of innovations into products by measuring velocity, turn-around time and code quality
Program Foundation
Metrics that matter
How does someone get involved and who is allowed to participate?
21
Enablement Pillars
Program
Consistency
Repeatability
Reuse
Community
Platform
Consistency
Repeatability
Reuse
Community
Practitioners
Consistency
Repeatability
Reuse
Community
↓
IaaE is an open collaboration infrastructure built on three keystone pillars
Practitioner Community > Force Multiplier
Explorers
New to InnerSource practices, first-time contributor, looking for a community to join
Contributors
Active InnerSource Practitioner, frequent contributor, joined at least one community
Trusted Committers
Experienced InnerSource Practitioner, feature contributor, tech expert, community advocate
Starters
Advanced InnerSource Practitioner, advocate, project kick-starter, community builder
23
Open Collaboration
Trusted Committer
Contributor
Contributor
Explorer
Open Community
Starter
Reduce systemic friction > optimize collaboration
24
*Source: 2021 Analysis of data, issues and pull requests from Watson NLP GHE repos
Practitioner Community > Use the Force
25
Trusted Committer
Contributor
Contributor
Explorer
Open Community
Starter
Solve Once to Solve for Many
26
Starters
Explorers
Trusted Committers
Contributors
Practitioner Community
InnerSource Contributor Funnel
Participation > Open
Agile Cadence
Participation > Active
Agile Cadence
Participation > Ongoing
Agile Cadence
Participation > Dedicated
Agile Cadence
An InnerSource Practitioner’s Journey
27
Explorer
Contributor
Trusted Committer
Starter
Practitioner Community
Learning
New Skills
Incentives
Learning
New Skills
Incentives
Learning
New Skills
Incentives
Learning
New Skills
Incentives
Benefits for becoming an InnerSource Practitioner
28
Explorer
Contributor
Trusted Committer
Starter
Practitioner Community
Our Rules�
Open everything
We practice an Open Source > InnerSource approach to begin development so we can break down silos by adopting a reuse first mindset.
Failure is necessary
We continuously experiment, embrace failure, try things, fail, and try again because failure is fundamental for innovation.
Focus, focus, focus
We limit work in progress to focus on one thing at-a-time by investing in the most valuable, non-renewable resource we have…time.
Pay-it-forward
We pay-it-forward by documenting processes, decisions and taking time to write clear guidelines for the next person to understand.
Respect & patience
We must have an environment where failure and innovation go hand in hand via empathy and respect for people and ideas.
Plan as a team
We use Agile practices to plan work, manage communication and we welcome community participation, so show-up to be heard
29
We agree to follow these rules of engagement. We further agree that these may evolve to meet new needs as the community grows.