Markdown was the inspiration: easy to scan, consistent, doesn't support fluff, etc. Trying to avoid many of the typical SaaS site tropes that get in the way.
I can confirm that it's not a paid promotion. Just my reflections on what I see as being exemplary community work.
Sorry to hear you found reading the article difficult. It's an aesthetic choice I've received only positive comments about before this, but I'll look into providing some option to disable it - perhaps I could hook into the
prefers-reduced-motion option or similar.
If you read article it outlines why I think so. Profitability is a larger issue than their community programs. Although, the process of converting community into customers is still slow for them, which I think is a contributing factor for sure.
Not astroturfing, just my take - I have no connection to the company. There's a section that goes into the licensing change a little more, but in my view, there's a lot of great stuff that can be learned from HashiCorp's approach to community from before the licensing change that is worth knowing about. If anything it highlights just what they've put at stake by making that move.
No, it's new, although was completed a couple of days before their announcement and updated to reference it. My audience is primarily community managers, DevRel, and community-minded rev teams and HashiCorp have done an exemplary job at community-led until the licensing change. There's a lot such folks can learn from before the licensing change, I didn't want to wipe that away. Also, I didn't see it as my place to provide too much commentary on it specifically, since the impact isn't yet fully understood.
I couldn't find a non-paywalled version, but do you know if they measured length of use in those studies? I can imagine it might be better short-term, but after a few hours...
There is more to it though. Like PLG encourages a freemium approach, to maximize the number of folks who can experience the product quality. As well as things like aligning user outcomes to business outcomes through usage-based pricing.
This isn't just PLG though, it's taking things a step further by layering on community that changes the go-to-market motion and not just business model. Corinne Marie Riley has an interesting article on this, too: https://corinneriley.medium.com/community-led-growth-the-pro...
I agree in part, at least the quote often applied to Henry Ford “If I had asked people what they wanted, they would have said faster horses” rings true. But I think that only really applies to the core innovation, actually turning that into a viable business requires a lot of customer understanding and getting user feedback is key to that. Rob Fitzpatrick's book "The Mom Test" explains how to get actually useful feedback from users.
Sure but how were they no-Sales? I used to work for an Atlassian consultancy and Atlassian put a ton of effort into their partner network. We would run Atlassian user groups, answer questions on their forums, etc. It was a community-based strategy, they were just earlier than most to it.
That's not the point being made in the article, though. It's not saying marketers should do community, but rather that companies should invest in community instead of marketing for mutual benefit (members and company). The follow-on Value Creation > Value Capture piece I think makes it clearer: https://orbit.love/blog/value-creation-beats-value-capture
We're producing a print version. We will have to tweak some of the colors for sure, but we've had a few test prints done and they match surprisingly well.
Asking around, some of the agents being worked on by folks I know include agents that:
- auto-update issue statuses based on GitHub activity.
- post daily summaries of Linear changes to Slack.
- discusses product requirements with you and creates Linear issues
- listens to Sentry error stream and auto creates linear issues for new crash signatures
- interprets GitHub events such as pull requests and deployment reviews, and propagates that context back to related Linear tickets