A Practical Guide To Inner Sourcing Your IdP

Slides Sched Link

Homepage Dev Rel

A talk by Lian and i can always recommend her talks.

Background

  • 55% of orgs have adopted but only 27% have integrated best practives -> They built technically impressive ghost towns
  • We’re not good at explaining/thinking about platforms -> Viewing them as a whole house instead of the collection of bricks that make them up
  • The deployment process evolved from scripts to services (shared scripts) to platforms (shared scripts with extra steps)
  • Platform adoption is not a technical but an advocacy problem
  • Idea: Treat the platform to as a shared project -> We need devrel (Dicover evaluate learn build scale)

TODO: Steal lian’s evolution slide

Case studies

A

  • Base: Buerocratic and individual driven with general apahty due to frequent objective changes but with individual heroes
  • Ideas:
    • Internal user groups (low contribution ight amount of complaints)
    • CI Librarbies (that no one used)
    • A pilot program -> Actually works

B

  • Large manufacturer, mission driven but tool anarchy and a buch of sub-cultures
  • Collection:
  • Diagnosys:

The platform advocacy framework

  • Goal: Turn passive users into passionate advocates
  • Based on: CNCF platform maturity model
    • Levels: Provisional, Operational (Dedicated Team+Budget), Scalable (Grow without diusruptions), Optimizing (Anticipate needs/changes)
    • Aspects: Investment, Adoption, Interfaces, Operations, Measurement -> Aspect levels are indipendent from one another
  • Potential Trap: Creating actions just to graduate to the next level without actually keeping cultiure in mind
  • The orbit model:
    • Love: Activity in the community
    • Reach: Ability to pull others with you
    • Risk: Only focussing on high reach+love but the peopple with the most valuable feedback are usually hrll or lrll
  • Tribal Culture
    • Stages: Life Sucks -> My Life Sucks (Victim of the system mindset) -> I’m great - no you are not (lone warrior) -> We are great (mission driven) -> Life is great (team driven)
    • You have to move from one stage to another, no skipping

CNCF Platform maturity

TODO: Copy from slide

Orbit model

TODO: Make readable

Low Love High Love

Low Reach/Love: Detached observer Contractors, Juniors Low Reach/high love: Indipendent Fans Early adopters, individual contributor HR /ll: Sceptics (Managers, Architects, CTOs) HR/HL: Exoert multipliers (Senior ICs, Internal Advocates, Platform champoins)

Tribal Culture model

TODO: Beautify the text above

Using the framework

  • Culture first -> The culture sets your options and limits
  • Cycle:
    1. Collect data (Use the three discussed maturity models)
    2. Analyse bottlenecks/root causes (Keep with the DevRel journey)
    3. Invervene: Decide on actions and take them (sientific method style: hypothesis -> define action -> define success metric and threshhold -> take action -> compare desired outcome)
    4. Repeat
  • Important: Requires patience if it’s hard to show the value or missing value in numbers
  • Innersourcing moves the platform from the team into the whole org