From 901aa8bde270841b986a309e58e87b1161d24cad Mon Sep 17 00:00:00 2001 From: Brittany Istenes <50678820+BrittanyIstenes@users.noreply.github.com> Date: Tue, 22 Apr 2025 16:33:35 -0400 Subject: [PATCH 1/2] Create driving_innersource_culture.md Adding in new blog about driving InnerSource Culture. --- .../driving_innersource_culture.md | 101 ++++++++++++++++++ 1 file changed, 101 insertions(+) create mode 100644 docs/InnerSource/driving_innersource_culture.md diff --git a/docs/InnerSource/driving_innersource_culture.md b/docs/InnerSource/driving_innersource_culture.md new file mode 100644 index 00000000..b7f093e3 --- /dev/null +++ b/docs/InnerSource/driving_innersource_culture.md @@ -0,0 +1,101 @@ +# Driving InnerSource Culture within your Organizations – FINTECH Edition + + +## The Case for InnerSource - Brittany Istenes - FINOS Ambassador + + +In today’s risk adverse FINTECH environment, speed, security, and scalability are essential. Yet, many engineering teams still operate +in silos, guarding knowledge, and duplicating efforts. InnerSource – applying the open source principles within your organization, offers a proven path to breakdown these barriers. + + +InnerSource has been proven to foster a culture of transparency, shared ownership, and internal collaboration. It's not just a development +practice; it's a mindset shift. For any FINTECH firms navigating complex regulations, legacy infrastructure, and rising customer expectations, InnerSource needs to be a strategic enabler for both agility and compliance. + + +## Making the Business Case – ROI, Reputation, and Competitive Edge + +Leadership support is essential to embedding InnerSoure across your organization. To win Executive sponsorship, you need to translate +cultural change into business outcomes. + +- **Reduce Redundancy** – When teams reuse internal code, development time and risk drop significantly +- **Accelerate Delivery** – Shared modules and services across teams decrease release times and speeds time to market +- **Improve Code Quality** – More eyes on code means fewer defects and better maintainability +- **Support Compliance** – Standardized review processes aligned with regulatory needs to build audit-friendly software +- **Enhance Market Reputation** – Showing that your engineering org can scale innovation responsibly boosts confidence with partners, customers, and regulators + +InnerSource isnt just an internal win. It signals to the market that your organization is capable of modern, secure, collaborative +engineering – traits that are increasingly competitive in the landscape. + +## Bridging the Gap – Getting Middle Management on Board + +While executive buy-in is critical, real traction comes when middle management embraces the change. These leaders are closest to +the work, and often the most resistant to shifting priorities, sharing resources, or taking perceived risks. + +Here are some ways that you can get them to join the InnerSource movement: +- **Align with their goals** – Position InnerSource as way to meet delivery timelines faster, improve team velocity, and reduce work +- **Demonstrate Team Wins** – Show examples where teams solved complex problems faster through InnerSource contributions +- **Reduce Fear of Loss** – Emphasize that InnerSource doesnt remove control – it enable better quality through shared effort and standardized practices +- **Offer Enablement of Tools** – Provide templates, training, and support that reduces the lift for managers introducing InnerSource to their teams +- **Involve them Early** – Ask for their input in defining contribution models or pilot projects. Co-creation builds commitment + +Middle Managers are the engine room of change. If they see InnerSource as an accelerator, not a distraction, they will become some of the strongest advocates. + +## Redefining Ownership – Shared Doesn’t Mean Loss + +A common concern in enterprise environments is the fear that “shared” ownership means losing control. But InnerSource does change +that narrative. Shared ownership increases the quality, accountability, and resilience of our applications. + +When others contribute to your codebase, you will see: +- **Your team remains the core maintainers** – Your group reviews, approves, and shape contributions +- **You gain fresh perspectives** – Contributors may identify bugs, inefficiencies, or enhancements you missed +- **You are not alone** – Ownership becomes scalable, especially when key team members are unavailable + +Shared ownership means your teams work has broader impact and support. It turns “your” project into the company’s solution, trusted +and relied upon across teams. Shared ownership is not a threat to your teams work, it’s influence. + +## Breaking Silos – Creating a Culture of Contribution + + +One of the biggest challenges in any organization is the “not invented here” mindset. InnerSource helps chip away at this by turning +internal development into a shared ecosystem. + +To shift the culture you will need to: +**Establish contribution pathways** – Define how teams can contribute to and consume InnerSource projects +**Celebrate Contributions** – Publicly recognize teams and individuals who engage across silos +**Normalize Reuse** – Encourage teams to look inward before building from scratch +**Create Visibility** – Use dashboards or internal showcases to highlight active InnerSource projects and their impact + +It is not just about writing code. Participation can include reviewing pull requests, improving documentation, or raising issues. +Every interaction is a touchpoint for cultural change. + +## Empowering Developers – From Ownership to Recognition + +InnerSource, at it’s core, is a developer-led movement. In financial institutions, recognition can be hard to come by. InnerSource creates a merit-based avenue to showcase skill, leadership, and impact. + +- **Create growth opportunities** – let developers lead InnerSource projects or become maintainers +- **Create Gigs** – Create a “gig space” where external team members can join into a project as a part of a shared goal +- **Encourage Transparency** – Make work visible across the organization to foster trust and learning +- **Align Incentives** – Connect InnerSource involvement to performance reviews or career development + +When developers see their work making a broader impact, motivation and retention increases. It also creates a natural path to leadership, +especially for emerging talent. + +## Establishing a Baseline – Getting Started with InnerSource + +Before scaling, teams need a clear starting point. Here is a great starting point to lay the groundwork: +- **Audit what Exists** – Identify projects that could benefit from cross-team collaboration +- **Set Guidelines** – Publish contribution policies, review checklists, and onboarding steps +- **Designate Maintainers** – Appoint responsible owners who will review, merge, and guide contributions +- **Launch a Pilot** – Start small with a high-impact use case, with all your stakeholders onboard, that can showcase quick wins +- **Measure and Iterate** – Track engagement (as it grows and drops), contributions, and time saved – use this data to refine and expand + +Adoption will not happen overnight. Adoption will grow organically when developers see that InnerSource helps them work smarter, +not harder. + +## Final Thoughts – Build Culture, Build Advantage + +In a risk-averse, regulated industry like Financial Services, change often feels slow. But InnerSrouce, when implemented well, offers +a low-friction way to modernize, empower teams, and move toward a more transparent, resilient development model. + +When done right, InnerSource becomes more than just a way to share code IT becomes a differentiator fueling better projects, faster +delivery stronger talent retention, and a reputation for innovation in a climate where market leaders are defined by quickly and securely they build. From dd728b5b199c97c954db053c7fd3be4afa139646 Mon Sep 17 00:00:00 2001 From: Rob Moffat Date: Thu, 5 Mar 2026 13:26:11 +0000 Subject: [PATCH 2/2] Update driving_innersource_culture.md --- docs/InnerSource/driving_innersource_culture.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/InnerSource/driving_innersource_culture.md b/docs/InnerSource/driving_innersource_culture.md index b7f093e3..5a26694c 100644 --- a/docs/InnerSource/driving_innersource_culture.md +++ b/docs/InnerSource/driving_innersource_culture.md @@ -1,3 +1,6 @@ +--- +title: InnerSource Culture +--- # Driving InnerSource Culture within your Organizations – FINTECH Edition