A Frictionless Inner Source Journey
summary
Company audits the inner source pipeline, surveys engineers and logs emotional, cognitive and interactive friction, then maps those to measurable initiatives. Findings show a popular internal time-tracking app used by 2,500 users attracts 50+ contributions from 12–15 different people, but most projects stall for lack of recognition, scattered docs, too many steps and middle‑manager inertia. Responses include metrics for adoption, action mapping, pilots like new-joiner awareness sessions, internal advocates, newsletters and a continuous feedback loop to cut red tape.
AI-written summary · about
chapters (11)
- 0:00Introduction to Inner Source
- 1:15Mercedes-Benz Inner Source Setup
- 3:00Time Tracking System Success Story
- 5:13Why Inner Source Succeeds
- 6:18Challenges in Inner Source Adoption
- 8:26Developer Pain Points Identified
- 10:11Analyzing Developer Feedback
- 13:06Three Types of Friction
- 14:31Strategic Initiatives to Reduce Friction
- 15:36Current Initiatives and Progress
- 17:24Summary and Next Steps
related talks
28mA Frictionless Inner Source Journey
19mWhen there is no alternative to InnerSource
28mA Journey to Inner Source
18m(Y)Our Journey to Inner Source
15mEmpathetic Engineering and InnerSource
30mInnersource: open source collaboration patterns beyond public FOSS projects
23mAccelerate Innovation by Initiating InnerSourcing
16mAnalysis of development velocity in an InnerSource context