Once you have a piece of content, you've baked a cake. Now you can take this cake and slice it up. Serve those slices to different channels to reach new audiences. Some get smaller pieces, some get bigger pieces. Serve a slice of webinar as a YouTube short. Serve a
Did you know that rotating helix thingy outside barber shops is called a barber's pole? It's something you see but you don't see it, right? It's enough to signal you're in the right place but that's as deep as it goes. The technology world is full of barber poles. Jargon,
They educate. Inspire. Help. Inform. Celebrate. Include. Question. Explain. Demo. Answer. Explore. In other words, they build trust. They don't sell... until the very, very end. IF at all. The content itself is the persuasive factor. Here's just one example of a Very Good Webinar.
You know the saying, "The first impression is the last impression." For someone using your product or open source project and learning it the very first time, is it any good? How do you know? Are you measuring it? How do you measure what "good" is? I would start with
Your first-time learning experience (FTLX) is an owned experience you create that teaches users how to use your product. This would be something like: * In-app onboarding * Course * Quickstart tutorial * Sample app * Readme There's another adjacent term, first-time user experience. That is used within the product context. I'm talking about a
It might be nice if people stopped by to chat with your advocates or team at the conference booth. But conferences are busy, noisy, and often create circumstances that uh... aren't great for interaction. I can think of tons of situations where I couldn't easily interact: * Your reps are busy
What's the heck's the difference?! Well, I don't think it's about one-way or two-way interaction – every platform can basically work both ways. Instead, I think each type of event evokes a vibe: * A live event's vibe is electric, there's a hum of excitement in the air * A live stream's vibe
If you give conference talks as part of your DevRel work, there are many ways to structure them. One of the first ones I remember being taught is what I'll call The Three Tees: Tell 'em what you're going to tell 'em Tell 'em Tell 'em what you told 'em
If an open source project is created first and then a community grows around it before a commercial offering is available, I'd call this community-led growth (e.g. Redis, Red Hat). If an open source project is created alongside a commercial product (aka "open source core" or "open source startups"
If you're the alpha, you probably have the resources to hire an army of developer advocates to maintain your dominance. If you're the underdog, it's going to be an uphill battle to take over the pack. Instead, you could leave and find a new pack. Sometimes finding an underserved niche