As posted in my marketing vision topic, I’m working on extending my landing page architecture’s elements/component/styles. While you’re listing out such design requirements, you drift towards architecting the requirements of an engaging/converting funnel.
So I took the network’s top priority: attracting developer talent, and began to brainstorm a funnel flow. And here’s the thing: I can sell any dream / vision / idea. But at some point the new developer will need to actually dive into the code, the community, the environments and decide whether it’s a place he wishes to contribute-to. It’s our job to prove that our decentralized organization will allow the developer to grow a career.
Here’s what I believe matters to developers. Please propose if you have ideas.
- Be educated on the Zenon mission and its USPs.
- Be educated on the Accelerator-Z project in question.
- Be educated on the other projects required to achieve the mission.
- Be educated on the opportunity for the developer.
- Be educated on the benefits of their contributions to Zenon.
- Be educated on how their contributions will be recognized, aside from payment.
- Be educated on the Pillar-led DAO.
- Be educated on the Accelerator-Z submission process (new one coming with a Zenon.Org dApp).
- Be educated about the APR’s for delegating/staking/pillar/sentinels.
- Be given Zenon swag if an Accelerator-Z proposal is paid.
- Be educated about the open and active spaces for developers (Discord, Forum).
– Actually get a reply from other developers / technical community in a timely fashion. - Be educated about the community-led developer online meetups.
- Be educated on the proposed Governance System (and the fact that it’s missing).
- Be educated on regularly updated technical documentation of the code.
- Be educated on regularly updated list of contributing developers and other project teams.
- Have access to a testnet.
Things we can work on:
-
Develop a method to recognize developers/teams for their contributions. This could include promotions in a variety of marketing channels, and should be included in the content calendar mix for Zenon.Org channels.
-
Improve the vote casting reaction time for Pillars. We can run a test AZ submission, and measure how long it took for Pillars to vote before the test passed. Then attempt to contact the Pillars who were slow, and push them into a method for better awareness (the bot / channel). The faster the reactions, the more I’d be willing to put dynamic stats on landing pages i.e. “The last 7 proposals were approved within 8 hours”.
-
Campaign to bring the rest of the develop community to Discord. You can use this post to promote the benefit for the transition.
-
A method to identify/tag brand new Discord and Forum members. If these people post in the relevant developer channels, the community would better-identify them.
-
I recall @georgezgeorgez would host dev meetups online. Would be awesome to continue such initiatives, and collaborate-with / tag #hypergrowth teams to include in their content calendar mix.
-
Campaign to find some technical community members willing to write technical documentation about the code in docs.zenon.org – we need to share current knowledge.
-
Maintain a list of contributing developers in docs.zenon.org.
-
Develop a privacy preserving method to ship physical items to developers (swag).
-
What’s going on with the Governance System implementation?
-
How do we get a testnet?
-
Can we get zenon-network Github to open some features of their account/organization to the community? Like the Github projects feature, or other stuff where the community can better self-organize in an official-looking space? Right now if I look at the GitHub account for zenon-network, my first gut feeling is: this project is dead. No community, no activity. That doesn’t look attractive to a new dev. So what do I do from a marketing perspective, hide the repo from him? We can do better.
With the above improvements, I can create a method which highlights to the developer all the strengths, and defines a clear path for learning and including himself (while of course pushing him down a path of web-based submission via a new dApp, tracked for conversion and all).
In my next phase I will showcase some funnel options, drawn as a flow chart with all scenarios laid out i.e. what if he doesn’t opt-in to the form and leaves? (we retarget him)… what happens after he opts-in with his email/discord/telegram/twitter handle? etc. Funnels will be tuned for each channel i.e. is the traffic aware and exposed to crypto? (depends where the traffic is coming from… like a crypto job board vs. a Go lang job board). You may not need to explain the same things to an experienced blockchain dev… get where I’m going?
Summary: It’s up to us the community to engage with all current participants, and make them understand the benefits of improving the architecture of the community. The more we streamline, the easier it’ll be to onboard new participants. Looking forward to the open discussion. I’m not asking for any specific feedback, these are just thoughts I figured I’d share as I progress.
Between the lines I’m basically saying “how can we be attractive to new talent, if we don’t have many basics organized?” (mainly on the technical side). I can use all the skills and tools available to market, find, build lists, retargeting audiences – if the environment doesn’t feel right to developers, they won’t dive in. Not everything is solved by marketing/sales. We need a good product in the first place, and the product isn’t only the code, it’s the decentralized organization that comes-with.
mehowz
… The first impression when I get to the Github /go-zenon repo is: this project is dead. It would be great if the technical community can understand where 