Making the business case for contributing to open source

A presentation at Open Infrastructure Summit in October 2020 in by Tobie Langel

Slide 1

Slide 1

Making the business case for contributing to open source Tobie Langel (@tobie) Principal, UnlockOpen tobie@unlockopen.com unlockopen.com

Slide 2

Slide 2

“In short, software is eating the world.” open source —Marc Andreessen, WSJ, August 20, 2011. 96% 57% OF APPS CONTAIN OPEN SOURCE COMPONENTS OF CODEBASE IS OPEN SOURCE Source: Black Duck 2018 OSSRA

Slide 3

Slide 3

And yet…

Slide 4

Slide 4

Why should companies contribute to open source? Common good The Right Thing To Do™ Paying it forward Etc.

Slide 5

Slide 5

The Right Thing To Do™ Paying it forward Common good

Slide 6

Slide 6

Lack know-how The Right Thing To Do™ Paying it forward Increased Risk Wasted resources Common good Lost IP Lost competitive advantage

Slide 7

Slide 7

The ROI of using open source is well understood. The ROI of contributing to open source: not so much.

Slide 8

Slide 8

The risk of contributing to open source is: • • not well understood, generally exaggerated.

Slide 9

Slide 9

Understanding the value of contributing to open source

Slide 10

Slide 10

Understanding the value of contributing to open source 1. Strategic benefits 2. Operational benefits 3. Second-order benefits

Slide 11

Slide 11

Commoditize Your Complement Company Focus Complement

Slide 12

Slide 12

On-ramp developers

Slide 13

Slide 13

Understanding the value of contributing to open source 1. Strategic benefits 2. Operational benefits 3. Second-order benefits

Slide 14

Slide 14

Photo: Pablo Andrés Rivero, 1997 (CC BY-NC-ND 2.0) Payback Technical Debt

Slide 15

Slide 15

Leverage external contributions React Router Redux React Ecosystem

Slide 16

Slide 16

Understanding the value of contributing to open source 1. Strategic benefits 2. Operational benefits 3. Second-order benefits

Slide 17

Slide 17

Problem Co!ee Engineer Sarcasm (by-product) Solution

Slide 18

Slide 18

Problem Co!ee Software Engineer Sarcasm (by-product) CODE

Slide 19

Slide 19

Problem Co!ee Software Engineer Sarcasm (by-product) Commons OPEN SOURCE CODE

Slide 20

Slide 20

Problem Co!ee Software Engineer Sarcasm (by-product) Commons OPEN SOURCE CODE Software Engineer Sarcasm (by-product) Problem Co!ee

Slide 21

Slide 21

Problem Co!ee Software Engineer Sarcasm (by-product) Commons OPEN SOURCE CODE Conversations Code reviews Mentoring Networking Etc. Software Engineer Sarcasm (by-product) Problem Co!ee

Slide 22

Slide 22

Problem Co!ee Commons Software Engineer OPEN SOURCE CODE Conversations Code reviews Mentoring Networking Etc. Sarcasm (by-product) Adopt best-prac tices Increase code qua lity BY-PRODUCTS Software Engineer Problem Co!ee Sarcasm (by-product) e l a r o m & e r u t l u c d e v o Impr s l l i k s t f o s e v o r p m I Lower technical debt Improve documentation y l d Reduced churn n e i r f e t o Rem Innovation Influence project directi I n crease e!cie l o o p on Access to talent r e ncies d a e l y r t s u d n i s a ed v i e c r e P Level-up engineers y t i p i d n e Access to expert n “Knowledge spillover” r Se Better career opportunities etwork

Slide 23

Slide 23

BY-PRODUCTS PROJECT INDIVIDUAL TEAM ORGANIZATION Improve documentation Level-up engineers Increase e!ciencies Improved culture & morale Increase code quality Adopt best-practices Serendipity Perceived as industry leader Lower technical debt Improve soft-skills Innovation Access to talent pool Influence project direction Access to expert network “Knowledge spillover” Remote friendly Better career opportunities Reduced churn

Slide 24

Slide 24

2× TWICE AS EFFICIENT Contributing firms capture up to 100% more productive value from usage of open source than their free-riding peers. Source: Franck Nagle, Learning by Contributing, 2017.

Slide 25

Slide 25

75% OF FACEBOOK’S NEW ENGINEERING RECRUITS MENTION FACEBOOK’S OPEN SOURCE PROGRAM AS A KEY REASON THEY ACCEPTED THEIR OFFER

Slide 26

Slide 26

“But we also noticed some e!ect that we didn’t expect. All the public visibility [sponsoring Webpack] have given us lead to a situation where we suddenly became one of the most interesting companies to work for as a JavaScript developer. […]” “We’ve hired a lot of really great engineers who mentioned during their job interview that our sponsoring for Webpack was one of their primary motivations for applying, […]” —Patrick Gotthardt, Lead JavaScript Architect, Trivago, 9 July 2018.

Slide 27

Slide 27

Lack know-how Increased Risk Lost IP Wasted resources Lost competitive advantage

Slide 28

Slide 28

Mitigate the risk of contributing to open source

Slide 29

Slide 29

Lost competitive advantage “I skate to where the puck is going to be, not to where it has been.” —Wayne Gretzky Photo: Rick Dikeman, 1997 (CC BY-SA 3.0)

Slide 30

Slide 30

Photo: O’Reilly AI Conference, 2016 (CC BY-NC 2.0) Lost IP “In today’s world of fast-paced internet services deployment, owning IP has become considerably less important than turning research results into innovative products as quickly as possible, and deploying them at scale.” —Yann LeCun, Business Insider, Aug. 3, 2018.

Slide 31

Slide 31

Increased Risk Wasted resources Lack know-how Etc.

Slide 32

Slide 32

Slide 33

Slide 33

Now it’s your turn! • Framework to think in terms of business tradeo!s. • A toolkit of benefits and mitigation strategies. • See how it applies to your organization.

Slide 34

Slide 34

Now it’s your turn! • Be reasonable. • Show empathy to other’s needs in the organization. • Aim for small wins. Start small. • Remember it’s a mindset shift.

Slide 35

Slide 35

Thank you! Tobie Langel (@tobie) Principal, UnlockOpen tobie@unlockopen.com unlockopen.com