-
Notifications
You must be signed in to change notification settings - Fork 59
Marketing best practices
We’re trying to align the work executed in the bounty system with the goals of the RChain coop. One part of that, is making sure that people produce work that’s actually needed.
Below are 7 marketing ‘tenets’ is to help everyone suggest tasks that fit better with the broader RChain marketing strategy… and are thus more valuable to the RChain coop.
The goal of our marketing is to get Rholang apps running on the RChain platform. That means we should target I) people that will write Rholang code, and II) decision makers that decide on which platform to run Dapps for their organisation. It doesn’t hurt to get other people also enthusiastic about RChain… but it’s not a priority.
Publishing a blog post on the RChain blog (= controlled by RChain) is more valuable than publishing the same article on your own domain (= controlled by you). We prefer marketing assets that the Coop controls.
A piece of marketing content is more valuable when more people see it. A translation to Chinese is more valuable than a translation to Icelandic… simply because China is a much more important market. Better still: aim for marketing work that impacts everyone.
Follow the 3 tenets above, and you’ll create impactful marketing work. That impact also means there’s more at stake. For that reason, consider the process needed to get your work approved & released. Who signs off on your work? Where will this piece of content be visible? Who helps you get it on the RChain homepage?
Every bounty paid constitutes a cost to the coop. If the coop spends $1,000 on this work… what will the return on that investment be? Does the coop get a “good deal” spending that money in return for Rholang developers that you’ll help bring in? What’s the ROI?
If we’re talking about ROI anyway… can we measure the work? Can we measure how it performs? Can we measure the ROI? The more we measure our work, the easier it is to demonstrate ROI and get fair recognition for our efforts.
...
(for discussion about these best practices, see issue #693)