DevRel Scribbles
  • What are Scribbles?
  • Index
  • Developer Advocacy
  • Developer Advocates
  • Life as a developer advocate
  • Modernising Red Hat’s enterprise developer program
  • Engaging 9-year-old software developers
  • Making 22-year-olds love 26-year-old software
  • Dogfooding developer products: gathering insights from internal hackathons
  • How far does your ethical responsibility stretch for the tech your devs create?
  • Outside the lecture theatre
  • How do you design programs for diversity?
  • Build the Platform Your Developers Actually Want
  • Measuring dev rel programs far beyond marketing activities
  • Developer Evangelism
    • Developer Evangelists
    • How to rock a technical keynote
    • The Art of Slide Design
    • The Art of Talk Design
    • The Art of Story Design
    • Dev events beyond 2021
  • Developer Experience
    • The Power of Content
    • Building a Developer Community in an Enterprise World
    • How to lose a dev in three ways
    • Developer relations, why is it needed?
    • The hierarchy of developer needs
    • GitHub is your documentation landing page
    • Docs as engineering
    • Commit messages vs. release notes
    • A11y pal(ly)- crafting universally good docs
    • Inspiring and empowering users to become great writers, and why that’s important
    • Solving internal technical documentation at Spotify
  • Community Management
    • Building community flywheels
    • DevRel = Community Management?
    • Creating high-quality communities
    • How to grow a healthy Open-Source community?
    • Managing communities at scale
    • Using community to drive growth
    • Useful community success metrics
    • Communities aren't funnels
    • How to mobilise your community during a pandemic
  • Managing a DevRel Team
    • Developer Relations + Product
    • Distributed developer relations
    • Understanding company goals
    • DevRel Qualified Leads (DQL)
    • Path to success for DevRel
    • How to move up in your organization
    • Four pillars of DevRel
    • Building your DevRel dream team
    • Managing the burnout burn-down
    • I messed up and I’m going to get fired
    • How to report on community relationships without being creepy about it
    • How to scale a developer relations team
  • Misc
    • Is developer relations right for you?
    • Tooling your way to a great DevRel Team
    • Planning your DevRel career
    • Success metrics as narratives
    • Get executive buy-in or else
    • Introduction to the AAARRRP devrel strategy framework
    • Strategy for developer outreach
    • Connecting dev rel and product
    • Performance DevRel
    • Ultimate cheat codes for healthier travel
Powered by GitBook
On this page
  • Summary:
  • Scribbles:
  • Know who you’re actually serving
  • Defining core principles
  • Signal change
  • Make a place
  • Journeys
  • Publishing
  • Keywords Now!

Was this helpful?

Export as PDF

Modernising Red Hat’s enterprise developer program

Joe Schram talks us through the process of putting developers back in the spotlight. You’ll hear how Red Hat have brought together their developer materials out of silos and into a single experience.

PreviousLife as a developer advocateNextEngaging 9-year-old software developers

Last updated 3 years ago

Was this helpful?

Summary:

  • Evaluating your existing program.

  • Keywords

    • Shoe - People

    • Pyramid - Principals

    • Truck - Signals

    • Map - Placemaking

    • Hallway - Journey

    • Flywheel - Publishing

  • Know who you’re actually serving.

  • Defining core principles.

  • Signal change

  • Make a place

  • Journeys

  • Publishing

Scribbles:

Six things to remember when evaluating your existing program.

  • Keywords

    • Shoe

    • Pyramid

    • Truck

    • Map

    • Hallway

    • Flywheel

  • ⬆️ They’ll make some sense by the end of the scribble

Know who you’re actually serving

  • Maker is an interesting concept to discuss.

    • A maker is someone who puts their hands on the products to solve their personal and professional challenges.

  • An emphasis is required to keep telling the story of who the maker is. What we’re doing, why we’re doing it, is for the people who actually put their hands on the product.

  • Personal -- these folks want to advance their own skills and abilities.

  • Professionals, they have goals that they want to meet in their own career.

  • Maker is someone who builds.

  • The goal of doing DevRel is to try to join them on that building journey.

    • Because they’re going to build with lots of different tools and technologies.

    • Your hope, your aspiration is to be able to join them in that building process.

  • Enterprise developer -- security, scalability, and legacy. ‌

Defining core principles

  • Why does your program exist?

  • Why does it really exist?

  • Not just to drive sales, you have to go deeper than that.

  • Programs should exist to empower developers along their journey.

  • Tools to solve the problem

    • Providing solutions that are easy to find and simple to use.

  • Knowledge to grow expertise

    • Delivering insights in areas where we have something to say.

  • Community to share progress

    • Uniting developers to lead their work and careers forward.

‌

Signal change

  • You have to give outwards signals, especially when you’re in a turnaround or a reboot, that something has changed.

  • You have to back that up with visible outward signs.

  • The visible outward signs had to be backed up with real behind the scenes change.

Make a place

  • Show, don’t tell

    • Demonstrate ability to deliver value; serve first.

  • Every page is the homepage

    • Far more traffic enters through the rest of the website

    • Creating focused opportunities for discoverability is critical

  • Navigation is brand

    • Educate visitors about your opinionated worldview with opinionated navigation.

    • Lead with fresh, a topical structure that aligns with the user journey.

  • Best content first, presented in the best way

    • Videos, Blogs Learning paths

    • Every grouping of content is not the same, each group must be allowed to be different.

Journeys

  • Question/Challenge

  • Developer program content

  • Implementation

  • Solution Achieved

  • What stories across the top do they tell themselves about themselves, about their work, about their world?

  • What content are we going to create?

‌

Awareness journey.

  • There are moments of truth along this journey, where someone is moving from left to right, and they have a moment of proof that tells them, holy cow, I think I’m on the right track.

‌

Publishing

  • DevRel program at scale across many locations, the digital, online, grip is everything.

  • Your job is to fix the broken gears and teeth, even if you can’t see the immediate result.

  • Mobile layouts. ‌

  • Small compounding changes

    • Seo optimizing titles

    • Cross-linking to other assets(votes)

    • Mobile-first

    • Tone and voice (brand rep.)

    • Functional content/ tutorials

    • Videos

    • Working gates (SSO)

    • Talk to your audience (weekly newsletter + social media)

Keywords Now!

  • Shoe - People

  • Pyramid - Principals

  • Truck - Signals

  • Map - Placemaking

  • Hallway - Journey

  • Flywheel - Publishing

Video