Newsletter
There are multiple ways to monetize an open-source product. Let's talk about a few of them here. One important thing to keep in mind is that these aren't mutually exclusive: any company can employ one or more of these options simultaneously. 1. Pure consulting services 2.
Newsletter
Matching the myriad things Developer Advocates do with your needs as a business is critical to determining the kind of Developer Advocacy organization you need. You may need someone to be stewards of your developer community, or perhaps you need someone who can show other developers how your product or
Newsletter
Product-led growth (PLG) enables you to focus your entire customer-facing SaaS business on a common goal: get people to sign up for your product. Once someone has signed up for your product, then a sales motion could kick in based on various qualifications you determine make the most sense for
Newsletter
Imagine you've seen chatter about a cool new product on social media or via word of mouth from your friends. You go to the website for this product, you see what it does (generally speaking), you see that it's backed by a real company, you check
Newsletter
The MRD is the principle product strategy document. It is primarily accompanied by the Product Requirements Document (PRD). Sometimes, companies skip the MRD and PRD and go straight to listing out features, writing user stories, and prioritizing them. But done properly, the MRD and PRD can both provide guiding first
Newsletter
The ringleaders of the circus
Newsletter
Product naming can be one of the most infuriating and most creative exercises one can go through in a company. As a Developer Product Marketing Manager, you are the ringleader of the circus, but you are not the main attraction. Your coterie will include product, engineering, your fellow marketing managers,
Newsletter
In our industry, we launch products constantly. When we're in the daily soup of running our business, we lose sight of the fact that 99% of our target developers don't give one iota of a damn about our launch. We think, "We worked on this
Newsletter
Measuring our work is important. Let’s face it: not every company gets the role of Developer Relations. I’m not going to belabor the point, but in lean times demonstrating your value to the organization has merit. At the same time, measuring what matters gives you room to experiment,
Newsletter
I organize Developer Advocacy around four specific areas. That’s not to say that any individual does or does not do all four. It’s more that our roles can be boiled down to these core areas. 1. Capture and represent product feedback 2. Build credible and authentic content that
Newsletter
I spoke with someone recently who didn't know where to start with their first hire in Developer Relations. As folks who know me appreciate, I think of the Developer Relations organization as the following distinct functional areas: * Developer Advocates: they're the spine of your Developer Relations