<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nihal Salah on Medium]]></title>
        <description><![CDATA[Stories by Nihal Salah on Medium]]></description>
        <link>https://medium.com/@nihal_salah?source=rss-44eab5ab53f1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*KBlzfAp20so_1rgD</url>
            <title>Stories by Nihal Salah on Medium</title>
            <link>https://medium.com/@nihal_salah?source=rss-44eab5ab53f1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 05:52:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nihal_salah/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Speak and be heard: two key elements of effective web3 communication]]></title>
            <link>https://medium.com/b9lab/speak-and-be-heard-two-key-elements-of-effective-web3-communication-b49f56dac8d3?source=rss-44eab5ab53f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b49f56dac8d3</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[blockchain-marketing]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[devrel]]></category>
            <category><![CDATA[web-developer]]></category>
            <dc:creator><![CDATA[Nihal Salah]]></dc:creator>
            <pubDate>Tue, 28 Feb 2023 17:19:20 GMT</pubDate>
            <atom:updated>2023-03-13T13:02:09.947Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Effective messaging strategies for web3 developer marketing" src="https://cdn-images-1.medium.com/max/1024/0*tLuqGLvnCMbfv-rF" /></figure><p>This is the third in our series about how to promote your project or ecosystem and attract the right developers. In the <a href="https://blog.b9lab.com/four-steps-to-get-web3-devs-using-your-tech-f63593875e0a">first post we looked at four steps to get web3 devs using your tech</a>, and in the <a href="https://blog.b9lab.com/how-to-promote-your-web3-developer-products-and-tools-b6bc93c57693">second we focused on how a few marketing basics</a> can have a massive effect on engaging devs and driving them your way. Now it’s time to turn our attention to <strong><em>messaging</em></strong>.</p><p>Even if you’ve built some great products and tools to benefit web3 developers, you still need to make sure you’re very clearly communicating your value proposition. So let’s explore how you can make sure you’re using the right messaging to say something that will resonate with your target audience.</p><h3>The essence of good messaging</h3><p>If you’re struggling with your messaging, it’s likely that you haven’t nailed your value proposition or positioning, two complementary ways to differentiate yourself from the competition:</p><ul><li>A <strong>value proposition</strong> is a promise of value to your <a href="https://blog.b9lab.com/how-to-target-the-right-type-of-developers-to-grow-and-scale-your-web3-project-5ef828e03247">target developers</a>. It’s the reason why they should use your product, tool, or service. It’s a statement that clearly communicates why they should choose you over your competitors or alternatives.</li><li><strong>Positioning</strong> on the other hand is the process of creating an image of your product or service in your target audience’s mind. It is how they perceive your brand in comparison with your competitors.</li></ul><p>These two concepts are very closely related, and both are important for effective messaging. Your value proposition helps target devs understand what’s in it for them, why they should choose your product or service. Simultaneously, your positioning helps target devs assess you against the competition, and helps them remember your brand.</p><p>Having a clear and concise value proposition and positioning strategy enables you to create messaging that makes you stand out from the crowd and attract more of your target devs, by clearly communicating who you are, why they should care, and how you’re different.</p><h3>The ultimate test</h3><p>It’s human nature to focus more on what benefits us! Therefore, whether it’s on your website, social media, or in your content, your messaging should be precise and devoid of fluff. It should be specific to your target audience, about how your products or tools will help them.</p><p>However, when I first started working in web3 I was surprised to find that this kind of thinking is scarce. For a young, disruptive, vibrant space, there are far too many projects using what I call “wallpaper words”. Everywhere I look I see claims like <em>We’re building the next generation of whatever</em>… but in web3, everyone is building the next generation of something!</p><p>So how do you know if your messaging is precise and specific enough? Try picturing your marketing blurb on the website of your competitor, or anyone with a similar project to yours. Would this messaging work for their product the way you think it works for yours?</p><p><strong>If the answer is “Yes”, then your messaging is too vague</strong>. It isn’t personalised to your project, and it isn’t personalised to the devs you want to target. If what you say about yourself makes you sound like anyone else, why would an audience come running to you?</p><h3>Placing your audience at the centre</h3><p>Previously we’ve discussed <a href="https://blog.b9lab.com/how-to-target-the-right-type-of-developers-to-grow-and-scale-your-web3-project-5ef828e03247">the different key audiences to target in web3</a> — four distinct types of dev needed in the space, plus enterprises hungry to adopt this technology as a solution. We’ve also talked about the <a href="https://blog.b9lab.com/four-steps-to-get-web3-devs-using-your-tech-f63593875e0a">developer adoption journey</a> and why your marketing needs to be tailored to each stage to increase conversion. Ensuring your messaging speaks to the specific needs, pains, and potential gains of your target developers is absolutely essential.</p><p>There may be nothing more important than understanding who your audience is. Even if you didn’t have any product at all, you could always identify people in need and work to give them a solution. By contrast, if you don’t know who to target and how to speak to them, you could be sitting on the greatest toolkit in all of web3 and never see it get traction.</p><p>Many web3 projects make the mistake of talking about what they do, rather than <em>how what they do will benefit their audience</em>. But to create audience-centric messaging, you need to understand your audience really well. You should use language that resonates with your targeted audience, covering motivators they find relevant and addressing potential barriers to adopting your technology.</p><p>Achieving this doesn’t have to be a struggle. If you want to understand someone, the best way is usually to just ask what matters to them! <strong>A simple survey</strong> can work really well: focus on asking about which factors motivate their adoption and which ones can become barriers. An excellent strategy is to <strong>ask open-ended questions</strong>, because when your audience is free to answer in their own words you really get inside their heads — plus you can use what they say in your copy later, so you get to learn <em>and</em> leverage that data on a practical level.</p><h3>Let me tell you a story…</h3><p>Humans are storytelling animals. We are wired to respond to stories; when we hear a good one, our neural activity increases fivefold. Neurons which fire together, wire together, helping us to remember more of the information we hear when told as a story.</p><p>This screams opportunity for any project that takes this approach when all around do not!</p><p>Storytelling is one of the most powerful yet most underutilised tools of good messaging. Very few developer-enabled projects in web3 use this tactic to get their message across. You can use stories in various ways, such as to illustrate potential use cases or examples of how your tech can be used and the benefits.</p><p>It’s very easy to just state the possible use cases of your tech and list a bunch of relevant benefits. Alternatively, you could create a character who embodies the same characteristics, pains, and gains as your target devs, and craft a story about the problem she was trying to solve, how she came across your tech, how she used it, and the results she achieved. The key is to create ways for your audience to “see” themselves in your messaging, to feel that they can relate to your project even if they are not yet part of it.</p><p>If you have devs using your products, ask if they’d like to be featured in your content — most will say yes! People are always flattered to be invited to talk about themselves, and you get to present real-world experiences as stories in your messaging. On the other hand, if you’re still in the early stages of your project and trying to attract devs, or are launching a new product that’s yet to gain a user base, simply create a character to represent the goals and needs you’re aiming to satisfy. Just remember to be clear it is a fictional character!</p><p>Writers of fiction are often advised to “show not tell”, and marketers can spin this advice as well. Simply <em>telling </em>your audience why your product is exciting won’t necessarily inspire excitement in them. <em>Showing</em> someone’s excitement about your product (even an imaginary someone!) paves the way for the audience to feel it for themselves. Now, when you start detailing why the product is exciting, you’re suddenly reinforcing an existing urge to adopt.</p><h3>Speak to the heart, not just to the head</h3><p>Web3 as a whole tends to position itself in relation to the technological. It’s a fact that devs are eagerly getting involved already, and in many cases they’re fired up by being part of a movement — but web3 messaging generally doesn’t try to appeal to them on an emotional level, even though in almost every single web3 project “community” is central to their profile.</p><p>Contrast this with many marketing efforts to come out of web2 organisations — in the nearly forty years since <a href="https://www.youtube.com/watch?v=2zfqw8nhUwA">Apple’s famous 1984-inspired ad</a>, traditional tech companies have had no hesitation to attempt to personalise products and the organisations behind them, to make them seem relatable to their present and potential users in one way or another.</p><p>Good marketing is underpinned by an understanding of human psychology. Despite the fact that we like to believe we’re rational beings and make rational decisions… <em>we’re not</em>. We’re emotional beings, and up to 95% of our decision-making is actually subconscious and driven by emotional reactions. This is why understanding your audience and what drives them is so important. It enables you to use language that elicits positive emotions such as excitement and belonging.</p><p>Take the title of this post: everyone wants the freedom to “speak and be heard”, to feel like others are paying attention when they want to communicate; this choice of phrase is aimed at provoking a moment of recognition and engagement for the reader. Then we build on that positive reaction with the offer of sharing a valuable benefit from reading on. If you’ve come this far through the article, it seems like our messaging is working the way we want it to.</p><h3>Clarity trumps cleverness</h3><p>We’ve proposed some powerful messaging strategies here — <em>thinking smart and evoking emotions, being creative and audience-centric</em> — and that’s all good. But there’s a fundamental rule that you should always keep in mind:</p><p><strong>Never sacrifice clarity for cleverness or creativity.</strong></p><p>I’ve seen this mistake time and time again. When teams try too hard to play with words and visuals to make their message stand out, they often just end up confusing their audience. However, today this may be more of a danger than ever before.</p><p>Unlike previous technological revolutions, where people around the world had very different access to the big new thing, web3 exists in the context of global connectivity and availability. Blockchain technology is being eagerly adopted by people from wildly different cultures, and although the use of English remains the typical professional default you should always take into account that your tech adopters may be second-language English-speakers with varying degrees of skill level, or whose linguistic idiosyncrasies are very different from your own.</p><p>Clarity in your messaging strengthens all its other aspects — and strong messaging is the core of an effective adoption strategy.</p><p><strong>Nihal </strong>is the head of marketing at <a href="http://www.b9lab.com/">B9Lab</a> and has over 17 years of experience in marketing and tech.</p><p>If you want to know more about maximising the effectiveness of your communication, download our white paper, <a href="https://bit.ly/3ysr7u4"><strong>The Definitive Guide to Web3 Developer Adoption</strong></a>, and learn how to design a developer adoption strategy that fits your project whether you’re at 50 or 5000 devs.</p><p>If you’re interested in discussing how you can improve your communication and messaging, you can also reach out to us <a href="https://www.b9lab.com/contact">here</a>.</p><p>At <strong>B9Lab</strong>, we’ve been designing and building developer adoption strategies for leading web3 organisations since 2015. Through our onboarding and learning journeys, we’ve minted thousands of developers. Our team covers the whole spectrum of developer adoption strategy and management. We’re developers, business strategists, marketers, and blockchain educators.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b49f56dac8d3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/b9lab/speak-and-be-heard-two-key-elements-of-effective-web3-communication-b49f56dac8d3">Speak and be heard: two key elements of effective web3 communication</a> was originally published in <a href="https://medium.com/b9lab">B9lab blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The benefits, the action, and the metrics: how to make web3 developer promotion actually work]]></title>
            <link>https://medium.com/b9lab/how-to-promote-your-web3-developer-products-and-tools-b6bc93c57693?source=rss-44eab5ab53f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b6bc93c57693</guid>
            <category><![CDATA[blockchain-startup]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[web3-marketing]]></category>
            <dc:creator><![CDATA[Nihal Salah]]></dc:creator>
            <pubDate>Wed, 22 Feb 2023 16:53:00 GMT</pubDate>
            <atom:updated>2023-03-13T13:05:10.180Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S-3qSsudLF1P12uONdJtuA.png" /></figure><p><strong>This is the second in a series to help you promote your project or ecosystem and attract the right developers. Read the first </strong><a href="https://blog.b9lab.com/four-steps-to-get-web3-devs-using-your-tech-f63593875e0a"><strong>one here</strong></a><strong>.</strong></p><p>In the<a href="https://blog.b9lab.com/four-steps-to-get-web3-devs-using-your-tech-f63593875e0a"> first blog</a> of this series, we talked about the importance of designing a developer journey to drive adoption of your web3 products and tools. But how do you encourage devs to move through your funnel? There are three key aspects: <strong>promotion</strong>, <strong>events</strong>, and <strong>incentives</strong>.</p><p>In this blog, we’ll talk about promotion. We’ll cover events and incentives in later blogs, so make sure you follow us on Medium for updates when those are published!</p><h3>What exactly is promotion?</h3><p>In essence, promotion is simply making your target developers aware of your tech in ways they’ll find engaging. There are countless ways to promote your product, but your approach should be tailored to fit the stages of the <a href="https://blog.b9lab.com/four-steps-to-get-web3-devs-using-your-tech-f63593875e0a">developer adoption funnel</a>. The tactics you deploy at the first stage of a dev’s journey, to ensure they ‘discover’ your tech, are not the same ones you’ll need later to convince them to commit to your product instead of an alternative.</p><figure><img alt="Web3 developer funnel" src="https://cdn-images-1.medium.com/max/1024/0*KtYLJHxsshpGSWRY" /><figcaption>Developer funnel</figcaption></figure><p>Promotion should be a collective consideration for all your developer-facing teams. They need to work together to create a seamless promotional experience. Promotion in developer adoption encompasses everything from marketing driven by educational content to PR messaging and content across all social media platforms, your email, and your website. It’s also a vital part of developers’ experience with your community and DevRel teams.</p><p>You may feel very confident about your current promotional activities, but it’s very easy to fall into the trap of assuming you’re promoting your tech when all you’re really doing is talking about it. It’s time to distil things right to the core. What is promotion? This is promotion:</p><blockquote><strong><em>Communication expressing benefits that leads to action you can measure</em></strong></blockquote><p>Communication is the broad sweep here, so let’s postpone that for a minute and focus our attention on concrete benefits, calls to action, and the vital importance of metrics.</p><h3>The benefits of looking beyond the details</h3><p>Your messaging could range from the entirely non-technical — say a blog post announcing an event — to the polar opposite — like a breakdown of the intricacies of your next big upgrade. But neither of these things are “promotion”. All you’re doing here is <em>dispensing information</em>.</p><p>Promotion has to be more than just informative: it needs to convey the <strong><em>benefit</em></strong> of its subject to a curious audience, not just the facts about it. <em>Our event is going to expose skilled devs to teams hungry for new talent</em> — that’s promotion. <em>The v2.6 update will revolutionise how your project interacts with other dApps across the ecosystem</em> — that’s promotion. Exactly <em>how</em> those benefits are expressed may be vital to get across, but sharing data alone isn’t enough.</p><p>Many web3 projects confuse sharing information with doing promotion; even experienced marketing teams make this mistake. That’s not to say that raw information has no value — of course it does — but its appeal may be limited to stack insiders who you’ve already brought onboard. For your outreach to flourish, it needs to extend far beyond that core group.</p><h3>Always use a call-to-action</h3><p>The acid test for the <em>information versus promotion</em> trap is identifying a <strong>call-to-action</strong> (CTA). Is there a clear decision you’d like your audience to take? CTAs indicate to your audience the next step in their journey, and they are absolutely essential to your developer adoption funnel. <strong>If there is no CTA, you’re not doing promotion</strong>, because the aim of promotion in developer adoption is to capture <em>and direct</em> target devs to where you and they want to be.</p><p>Here are some best practices regarding CTAs:</p><ul><li>CTAs should create urgency, offer incentives, encourage participation, or do all three.</li><li>CTAs should be targeted to your developer types and personalised if possible.</li><li>You should adapt your CTAs to their context; for example, the CTA at the end of a blog post is going to be very different from a “sign up” button on a landing page.</li><li>Each CTA should be concise and only reference one action. You can use different CTAs to allow your targets to funnel themselves, but if they’re next to each other they should be about the same thing. <em>“Start now”, “Start later”,</em> etc.</li><li>CTAs should always lead to the next step in the funnel, and align with the overall goal of developer adoption. A CTA that takes a dev into a side loop is not a useful CTA.</li><li>Always experiment with your CTAs, both for different placements and strategies such as A/B testing, in order to determine where calls-to-action prove most effective.</li></ul><p>A great CTA is what enables your target devs to progress in their journey towards their (and your) goals.</p><h3>Metrics, metrics, metrics</h3><p>The old DIY adage <em>measure twice, cut once</em> doesn’t cut it when it comes to promotion. Better to say <em>measure ceaselessly, and never stop crafting</em>.</p><p>Web3 suffers from a critical lack of metrics analysis and iteration. Teams are very focused on moving fast, shipping, and moving on to the next thing, and this attitude often bleeds into promotion. It forces your promotions team to focus on output rather than outcomes with no space to iterate. <strong><em>Promotion isn’t development</em></strong>. Treating it as such only harms your project.</p><p>Developer adoption is an evergreen process that takes developers from <em>somewhere near point A</em> to <em>somewhere near point B</em> over and over again, fine-tuning content and feeling out new tactics with each round of activity. Even though each dev will only experience a given interaction once, this is a continuous process for your promotions team. Making sure to track and analyse the metrics of your journeys improves the experience for the next dev.</p><p>Every planned (and unplanned) interaction with your target devs should be deeply understood. At it’s most basic you should be assessing the effectiveness of every email in a nurture campaign so you can make improvements. Sources for sign-ups to an event should be tracked so your promotion can be optimised, as should the success of any devs attracted into starting a journey through your various channels; only then can you know what works.</p><p>Setting up and consistently analysing the metrics of your developer adoption journey is the most effective way to improve it over time. Treating your promotion as a collection of one time “ship it and move on” activities is a serious mistake.</p><h3>Who to communicate with, and how</h3><p>Curating the right content for a given target audience requires that you have their needs top of mind when you’re evaluating your output. This allows you to create comfortable and easy journeys to adoption. You and your devs can share the goal of adopting your tech; your job is to make it as easy as possible to get them to the destination.</p><p>In developer adoption, education-focused content marketing is the core of your strategy, especially at the early stages. B9Lab strategies target <a href="https://blog.b9lab.com/how-to-target-the-right-type-of-developers-to-grow-and-scale-your-web3-project-5ef828e03247">five types of developers</a>: <strong>pioneer devs</strong>, <strong>entrepreneur devs</strong>, <strong>career devs</strong>, <strong>sysadmins</strong>, and the developer-adjacent <strong>enterprise adopters</strong>. We also think about them in terms of how familiar they are with blockchain technology as a whole, and with specific tech stacks in particular.</p><p>The requirements of different devs with different levels of web3 experience vary widely. Sysadmins and pioneer devs are pursuing divergent goals, while what your stack insiders want to know and curious outsiders <em>need</em> to know are poles apart. However, that is not to say that you have to create entirely new content solely for promotion — there can still be ways to take material designed for one purpose and use it to support another.</p><h3>Repurposing content</h3><p>Look at your last 15 blogposts. There’s a high likelihood that 90% are informational posts for your stack insiders. Clearly, these aren’t going to sync with the needs of an outsider dev who is still only considering whether your tech is the right choice for them — but there could still be plenty of useful content that <em>can</em> speak compellingly to a new audience, <em>if you work with it</em>.</p><p>Any information is fair game when it comes to repurposing, but there are many different ways to go about it. Take two examples:</p><ul><li>Using snippets from an in-depth AMA to drip feed info to a less knowledgeable audience. You push these clips out via your socials, along with a CTA to sign up for an entry-level event in the near future — <em>content originally targeting one group now targets two</em>.</li><li>Turning the opening paragraphs of an entry-level explainer into an email campaign. Your target devs click through to the full content to know more, which might lead to a recording of a relevant twitter space, and from there to a sign-up for an introductory AMA — <em>all of a sudden a brand new dev has joined your Discord</em>.</li></ul><p><strong><em>Communication expressing benefits that leads to action you can measure</em></strong> — this is real promotion, and the beginning of a fruitful process that you can iterate on in countless ways.</p><p>When you target the right devs, and create messaging and positioning to make them aware and interested, <em>they come to you</em>. Once you’ve captured their attention, promotion moves them down the funnel. It demonstrates the benefits of the project <em>for them</em>, the social proof to encourage them to engage; it tells them how to take the next step, and makes them want to. Promotion also nurtures devs already in your funnel if you are not ready for them to move to the next stage; without it, you risk them dropping out and moving on to something else.</p><p>So here’s our call to action for you: take some of your stack insider blog posts and see if you can turn just three of them into educational content marketing that targets outsiders to your tech instead. Think about which of the five developer types you want to reach out to, when in their journey, and what you want <em>their</em> next step to be after they finish reading.</p><p>And when you’re ready to take the next step, you can <a href="https://b9lab.com/contact">give us a call</a> and really get working.</p><p><strong>Nihal </strong>is the head of marketing at <a href="http://www.b9lab.com/">B9Lab</a> and has over 17 years of experience in marketing and tech.</p><p>If you want to know more about crafting effective developer promotion, download our white paper, <a href="https://bit.ly/3ysr7u4"><strong>The Definitive Guide to Web3 Developer Adoption</strong></a>, and learn how to design a developer adoption strategy that fits your project whether you’re at 50 or 5000 devs.</p><p>At <strong>B9Lab</strong>, we’ve been designing and building developer adoption strategies for leading web3 organisations since 2015. Through our onboarding and learning journeys, we’ve minted thousands of developers. Our team covers the whole spectrum of developer adoption strategy and management. We’re developers, business strategists, marketers, and blockchain educators.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b6bc93c57693" width="1" height="1" alt=""><hr><p><a href="https://medium.com/b9lab/how-to-promote-your-web3-developer-products-and-tools-b6bc93c57693">The benefits, the action, and the metrics: how to make web3 developer promotion actually work</a> was originally published in <a href="https://medium.com/b9lab">B9lab blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Four steps to get web3 devs using your tech]]></title>
            <link>https://medium.com/b9lab/four-steps-to-get-web3-devs-using-your-tech-f63593875e0a?source=rss-44eab5ab53f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f63593875e0a</guid>
            <category><![CDATA[blockchain-development]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[blockchain-marketing]]></category>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[devrel]]></category>
            <dc:creator><![CDATA[Nihal Salah]]></dc:creator>
            <pubDate>Fri, 17 Feb 2023 12:30:06 GMT</pubDate>
            <atom:updated>2023-03-13T13:15:20.159Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Q4AUZTglMJCYmBWr" /></figure><p>Imagine trying to get to a destination you don’t know with no map to guide you. It’s unlikely you’d ever arrive. You might never find out what wonderful things that awaited you there! For developers entering web3, this is a worryingly common experience — but it doesn’t have to be. Creating an adoption journey helps your target devs understand where they want to go and how to get there.</p><h3>What is an adoption journey?</h3><p>“Adoption journey” is shorthand for creating a path for developers that leads to the destination you want them to reach. This isn’t manipulation, quite the opposite. Trying to discern the destination is difficult for new developers in web3; having it clearly spelt out is a very refreshing change. As the authority in the tech, you are plotting the journey to make it easy for you both to achieve a shared goal: satisfying and productive work using your tech.</p><p>Each adoption journey represents an individual developer’s path. The full map of adoption can encompass many journeys, with many destinations — this is the <strong>developer funnel</strong>. These interacting journeys allow for multiple decisions along the way and result in various outcomes — each of which may even be part of <em>multiple</em> funnels! — but every developer’s journey will include a few common core elements:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7veRUSlQUG7L4Z9U" /></figure><p>For now, let’s focus on the <strong>adoption</strong> portion of the developer funnel — we’ll look at engagement and retention in a later post. Adoption is about discovering, exploring, comparing and deciding, and technical learning. This diagram crudely represents the volume of individuals active in each stage — you’ll never convert everybody discovering web3, and probably wouldn’t want to. Some will self-select out, freeing you to help those who want in.</p><p>Let’s take a look at each phase in more detail.</p><h3>Discovering</h3><p>In this phase you’re reaching out to your target developers where they are. This is the purview of your promotions, marketing, events, and PR teams, with back-up from your technical content teams and DevRels.</p><p>Many projects only target experienced web3 “pioneer” developers, <strong>blockchain experts</strong> who in some cases may also know something about your stack — what we call <strong>emerging insiders</strong>. Superficially, this makes sense: emerging insiders probably use your Discord or follow you on Twitter, they’re a receptive audience who already know the basics of your tech. And blockchain experts are easy to find, right? Just do a bit of sponsorship, some YouTube interviews, pay a PR firm for some nice profiles on Cointelegraph… 🙄</p><p>However, this kind of targeting is easy, and everyone does it. The cacophony of projects calling out to experts and insiders is overwhelming, and it’s hard to differentiate your message over the noise.</p><p>A much richer vein of future talent are <strong>curious outsiders</strong>: people interested in web3 but who have yet to start their learning journey. They are actively looking to discover blockchain technology, they just need to be guided towards your part of it. Curious outsiders could be anywhere, so reaching out to them may seem difficult — but don’t forget: <em>they are curious!</em> The challenge is to identify the type of developer your project needs, and devise messaging that targets that subset of the larger group. Suddenly, it’s not so difficult.</p><p>At the top of the funnel (TOFU), devs are curious about web3, about the applications of your tech and its various use cases. During the Discovering phase they want basic technical <em>and non-technical</em> information, to assess if it’s worth continuing a web3 journey or if they should explore other options. Remember: even if your stack is the perfect choice for them, the wrong messaging at this point can easily drive them away and into the arms of your competition.</p><h3>Exploring</h3><p>Targets begin Exploring after you capture their interest by clearly explaining the basics and the benefits of your project; now you start answering more complex questions. They will start interacting with people in your space, so expect them to join forums or community groups on Discord or Telegram, maybe ask questions through your website chat, or even email you directly or start going to meetups. You may also find them posting questions on Reddit.</p><p>When devs (and non-devs) go to Discords asking discovery questions, around 65% of interactions result in no further interaction over the following months — or worse, <em>questions are asked that get no answer at all</em>. This down to a combination of community teams, project websites, and generally available materials failing to address target groups correctly, or funnelling them in the wrong direction. This is a strategy for pushing devs away.</p><p>Correctly funnelled, the exploring phase is when your community team can shine. Answering basic technical queries and directing tougher questions up the chain is their meat and drink. Even better is preparing your community team, promotion teams, and DevRels to identify a developer’s type based on the questions they ask, and direct them towards a journey that will work for them (if you want to learn more about these developer types, read <a href="https://blog.b9lab.com/how-to-target-the-right-type-of-developers-to-grow-and-scale-your-web3-project-5ef828e03247">take a look here</a>).</p><p>Managing your target devs through the exploring phase doesn’t mean resorting to the dark arts! It is simply a case of anticipating their pain points and helping to resolve them.</p><h3>Comparing &amp; Deciding</h3><p>Your tech doesn’t exist in a vacuum. Devs aren’t just assessing your tech, they’re comparing it with tech from other sources. There is a very important point here: it doesn’t matter whether <em>you</em> consider something as comparable, it only matters what <em>they</em> see as comparable. At this phase of their journey, they are not as informed as you — but if you dismiss their notions of what is comparable you’re not helping them choose your solution, you’re alienating them.</p><p>This is a problem we’ve seen hundreds of times. Projects get annoyed with being compared to what they see as “inferior” tech. Frankly, this is <em>their </em>mistake, not the dev’s. They haven’t delineated the functionality of their tech in a way that speaks effectively to their targets.</p><p>Developers will happily adopt tech that isn’t a perfect fit, <em>if</em> their non-technical questions are well answered — that clarity is simply more valuable to them at this stage. Yes, they will need to solve tech problems, but that’s their passion and it’s rewarding. Their passion is not sifting through outdated tutorials, or repeating the same questions on a dead Discord. Imagining such roadblocks on their path to success will be more than enough to drive them elsewhere.</p><p>When it gets to this phase, for better or worse you have little sway over a potential dev’s actions: now it’s entirely down to them. If you have built effective adoption journeys, target devs will be able to properly compare and make informed decisions on which tech to use.</p><h3>Technical Learning</h3><p>At last we reach the middle of the funnel (MOFU) in the adoption journey!</p><p>For an adopter to get to the Technical Learning phase, they have decided your tech is the one for them. And that’s great! However, they still have a way to go — if they feel friction here they will still abandon you, because it is only now that they really start to spend their most valuable asset: <em>time</em>.</p><p>Technical Learning is the culmination of your outreach efforts to your target devs, and their stepping-stone towards becoming Stack Insiders. It is also a deep and complex topic in its own right, and not one we’ll try to reveal here! However, this is a subject we’ve got lots to say about, so watch out for a later post.</p><h3>Conclusion</h3><p>Design your adoption journeys right, give your target developers information, guidance, and learning material at each stage of their journey, and you’re likely to convert more of the right type of developers. This means higher ROI for your marketing, developer adoption, and DevRel efforts, as well as increased adoption of your tech and reduced churn. That’s a destination everyone can enjoy reaching.</p><p><strong>Nihal</strong> is the head of marketing at <a href="http://www.b9lab.com/">B9Lab</a> and has over 17 years of experience in marketing and tech.</p><p>If you want to know more about the adoption funnel and its features in real detail, download our white paper, <a href="https://bit.ly/3ysr7u4"><strong>The Definitive Guide to Web3 Developer Adoption</strong></a>, and learn how to design a developer adoption strategy that fits your project whether you’re at 50 or 5000 devs.</p><p>At <strong>B9Lab</strong>, we’ve been designing and building developer adoption strategies for leading web3 organisations since 2015. Through our onboarding and learning journeys, we’ve minted thousands of developers. Our team covers the whole spectrum of developer adoption strategy and management. We’re developers, business strategists, marketers, and blockchain educators.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f63593875e0a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/b9lab/four-steps-to-get-web3-devs-using-your-tech-f63593875e0a">Four steps to get web3 devs using your tech</a> was originally published in <a href="https://medium.com/b9lab">B9lab blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why your web3 project isn’t getting traction (and what to do about it)]]></title>
            <link>https://medium.com/b9lab/why-your-web3-project-isnt-getting-traction-and-what-to-do-about-it-2d6eccc73f4?source=rss-44eab5ab53f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d6eccc73f4</guid>
            <category><![CDATA[developer-adoption]]></category>
            <category><![CDATA[blockchain-marketing]]></category>
            <category><![CDATA[devrel]]></category>
            <category><![CDATA[web3-marketing]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Nihal Salah]]></dc:creator>
            <pubDate>Fri, 03 Feb 2023 11:47:03 GMT</pubDate>
            <atom:updated>2023-03-13T13:30:07.241Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eqY-SKxtDAaBnJaEQZGuRQ.png" /></figure><p>Nearly all blockchain projects fail within the first four years. Only about 8% of blockchain projects are successful three years in, so maybe this shouldn’t be surprising. What it <em>should</em> be is the indicator of a serious problem.</p><p>Failure usually isn’t a sudden event. It happens progressively; factors accumulate; the situation snowballs. Identifying a specific cause may be difficult (especially if there is no single issue), but one of the main reasons projects ultimately fail is due to <strong>lack of adoption.</strong> Don’t mistake the point here: a bad product is always unlikely to spark a spending frenzy. But why do otherwise sound web3 projects languish alone and fade into obscurity?</p><p>I’ve asked numerous founders why they built their products and, unfortunately, many of their responses boil down to a very costly assumption about their users:</p><p><em>“If I build it, they will come.”</em></p><p>The problem is, <em>they don’t</em>. Here’s why.</p><h3>What are you building, and who is it for?</h3><p>Adoption of any tech requires that you have built something with enough value or utility for a defined target market, that you’ve communicated its value to the target audience, and that you’ve made it as easy as possible for them to onboard and use your tech. Achieving this first means carrying out research to understand the market gaps, various audiences and use cases, what product updates you might need to make, etc. This research is essential to ensure you don’t invest time and money on promoting your product to the wrong audiences.</p><p>Maybe you feel you’ve done all that, yet you’re still not getting the adoption you expected. If so, it’s probably down to one or more of the following:</p><ol><li><strong>You didn’t define your ideal target audience</strong> — you’re trying to attract too broad of an audience, so you’re unable to clearly articulate your product’s value for them.</li><li><strong>Your ideal target audience isn’t aware your product exists or how it can help them</strong> <strong>— </strong>you haven’t invested in your messaging and communications strategy.</li><li><strong>Your product’s onboarding journey has too many gaps</strong> — documentation and key information is too hard to find.</li></ol><p>Let’s look at the problems, and the solutions, in detail.</p><h3>Defining your ideal audience</h3><p>If you’re like many organisations in the web3 space, you’re developer-enabled and your target audience are devs who will build their own applications using your technology.</p><p>However: <strong><em>You </em>are not your target audience</strong>. Targeting the right type of developers at the right stage of your project is key to success. Knowing exactly who your audience is enables you to create highly focused product and marketing strategies. If you are clear on who your audience is, the problems they’re looking to solve, the alternatives they explore and the goals they want to achieve, you’ll be in a much stronger position to promote your product to them and ensure they receive value from it, thereby reinforcing brand loyalty.</p><p>Your target audience can be defined based on a number of criteria, such as:</p><ul><li><strong>Technical expertise: </strong>Programming languages, development frameworks, and technologies used.</li><li><strong>Experience level:</strong> Beginner, intermediate, advanced.</li><li><strong>Use cases:</strong> Making payments, identification services, digital assets, etc.</li><li><strong>Specialty:</strong> Smart contracts, validator management, blockchain applications…</li><li><strong>Platforms and protocols used</strong>: Ethereum, Hyperledger, Corda…</li><li><strong>Industries: </strong>Gaming, finance, circular economy, ID management…</li><li><strong>Hardware: </strong>Desktop, web, mobile…</li><li><strong>Operating system:</strong> iOS, Linux, Windows, Android…</li><li><strong>Company size and maturity:</strong> small up to enterprise; startup or established…</li><li><strong>Developer role: </strong>entrepreneur devs, career devs, sysadmin devs…</li><li><strong>Geographical location: </strong>Target specific regional markets; acknowledge cultural expectations and norms…</li></ul><p>It’s important to segment your target developers based on relevant criteria in order to guide your marketing and outreach efforts more effectively. By doing so, you will be able to tailor your message and materials to the specific needs of your intended audience. This will result in higher conversion rates, better developer retention, and increased ROI.</p><p>I always advise clients to invest in carrying out research with their newly defined target audience, to dig deeper into the problems they’re looking to solve and what they’re trying to achieve. This is incredibly important in terms of informing both your product and marketing strategy, and can be done as simply as via a survey coupled with some online interviews.</p><h3>Make target developers aware of your product</h3><p>Once you’ve defined your target audience, it’s much easier to develop a highly focused communication strategy to raise awareness of your product and encourage adoption. This includes the key messages, channels, and activities to focus on.</p><p>If you’ve carried out the right market research, you’ll have a good understanding of your audience’s needs and alternatives in the market. This will help you craft messages that are highly relevant and communicate the benefits and points of differentiation of your product.</p><h3>TOFU, MOFU, BOFU</h3><p>A comprehensive strategy will implement messaging in a multi-channel marketing plan which includes top of funnel, middle of funnel, and bottom of funnel activity. This approach works to capture the attention of your audience at different stages of their own awareness and needs, rather than perceiving them as static and uniform in how <em>they</em> perceive you and your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/0*7-e4U-95477M5fQy" /><figcaption>Stages of the marketing funnel</figcaption></figure><p><strong>Top of Funnel</strong> (TOFU) marketing focuses on creating <strong>awareness</strong> of your product by introducing it to targeted devs and familiarising them with the problems it solves. This involves activities such as creating educational content, social media campaigns, events and meetups, newsletters, and using organic or paid searches to link on relevant keywords.</p><p><strong>Middle of Funnel</strong> (MOFU) marketing is about generating <strong>interest</strong> and engaging with potential developers, showing them how your product or service can solve their problems. This involves activities such as creating content around use cases or case studies, white papers, videos, and webinars.</p><p><strong>Bottom of Funnel</strong> (BOFU) marketing is where target devs <strong>decide </strong>to use your product, being convinced by access to hands-on experience such as a sandbox or free trial. Ensure you’re encouraging them to take action by providing ever more in-depth information about how your product can benefit them.</p><p>A good strategy will include activity across all three stages of the funnel. Keep in mind that tracking the right metrics at each stage is essential, so you can focus your resources where you’re most likely to get the highest return. Understanding how devs are responding to the different stages of the funnel provides critical insight into the effectiveness of your messaging and helps identify if any aspect of your plan is negatively impacting the onboarding journey, causing devs to drop out. This enables you to act efficiently and accurately to plug any leaks.</p><h3>Optimise your product’s onboarding journey to reduce time to value</h3><p>While onboarding is the last stage of adoption, it is one of the most important. Unfortunately it often gets the least attention.</p><p>As a general rule, your onboarding process should be plain and simple, so developers join you with minimal friction. Lower the barriers to adoption as much as possible, and ensure important information such as pricing, integrations, and technical requirements are easily accessible. Your documentation should be up to date and right at your devs’ fingertips, designed to take them on a coherent journey from the minute they arrive.</p><p>This is the bare minimum for good onboarding. <em>Great</em> onboarding takes it to another level.</p><p>You ensure new devs are getting education, support, and experience working with your tools in a structured manner. This can include instructor-led learning pathways such as Academies, or self-paced learning via open access developer portals — services which double as life-time information resources that your devs know they can go to throughout their career as your products evolve, carrying the value of an investment now into the future.</p><p>As discussed above, tracking metrics across each stage of the onboarding journey is critical so that you can identify and address any issues and avoid losing devs to the competition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*51tkYi33oJbgK5fp95_R7g.png" /><figcaption>New dev funnel</figcaption></figure><h3>Invest wisely, or pay the price</h3><p>Don’t make the costly mistake of assuming <em>if </em>you build it they <em>will </em>come. Define your target developers, create a focused marketing strategy to make them aware of your product, and optimise your onboarding journey to eliminate barriers to adoption. Investing your time and resources in these areas will help ensure your project is successful in the long run.</p><p>At the moment, “success” means you’re part of that slender 8% of projects that make it past three years. With the right onboarding strategy, both the percentages and lifespans of blockchain technologies might start moving in the right direction.</p><p><strong>Nihal</strong> is the head of marketing at <a href="http://www.b9lab.com/">B9Lab</a> and has over 17 years of experience in marketing and tech.</p><p>If you want to know more about the developer funnel, targeting the right devs, and driving them to you, download our white paper, <a href="https://bit.ly/3ysr7u4"><strong>The Definitive Guide to Web3 Developer Adoption</strong></a>, and learn how to design a developer adoption strategy that fits your project whether you’re at 50 or 5000 devs.</p><p>At <strong>B9Lab</strong>, we’ve been designing and building developer adoption strategies for leading web3 organisations since 2015. Through our onboarding and learning journeys, we’ve minted thousands of developers. Our team covers the whole spectrum of developer adoption strategy and management. We’re developers, business strategists, marketers, and blockchain educators.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d6eccc73f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/b9lab/why-your-web3-project-isnt-getting-traction-and-what-to-do-about-it-2d6eccc73f4">Why your web3 project isn’t getting traction (and what to do about it)</a> was originally published in <a href="https://medium.com/b9lab">B9lab blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Accelerating Web3 Tech Adoption Through Mapping Your Developer Journey]]></title>
            <link>https://medium.com/b9lab/why-understanding-the-developer-journey-is-the-key-to-unlocking-growth-in-adoption-of-your-web3-532965f55511?source=rss-44eab5ab53f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/532965f55511</guid>
            <category><![CDATA[developer-adoption]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[web3-marketing]]></category>
            <category><![CDATA[blockchain-marketing]]></category>
            <category><![CDATA[devrel]]></category>
            <dc:creator><![CDATA[Nihal Salah]]></dc:creator>
            <pubDate>Fri, 20 Jan 2023 16:53:33 GMT</pubDate>
            <atom:updated>2023-03-13T14:29:41.165Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IgrmthVKf8d2ua_gyTliDQ.png" /></figure><p>If you’re like most web3 founders or leaders, you want more devs adopting your tech. You’re probably also making a fundamental mistake: focusing too much of your education and support on devs who are part of a group I like to call ‘Insiders’. These are devs who are aware of and likely already using your tech. They’re probably early adopters, play an active role in your community on Discord, and are likely to be major ambassadors for your stack, which is great.</p><p>You absolutely should be supporting and nurturing your Insiders, but you can’t scale if you focus a disproportionate amount of time and resources on this one group. You need to make sure you’re also paying attention to groups of devs outside that circle who could potentially become valuable Insiders too, with the right encouragement.</p><p>I’ve seen this mistake over and over in web3. DevRel and marketing teams spend most of their time on Twitter spaces, Discord, and arranging Hackathons. I’m not saying these aren’t important channels — they can be. But they don’t provide devs new to your tech with a well thought out, progressive journey that takes them from zero understanding of your tech to being able to use it effectively.</p><p>Before we go into how you can design that journey, we need to understand more about who exactly those new devs are.</p><h3>Why you need to segment your dev audience</h3><p>The diagram below gives a holistic view of what your dev landscape probably looks like. The x-axis shows the extent of a dev’s blockchain experience, the y-axis shows their awareness of and understanding of your tech, and the size of each group is roughly representative:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EtcyoomViSZbNGIiPMAitQ.png" /><figcaption>Segmenting web2 and web3 developer audiences</figcaption></figure><p>In the chart I’ve segmented all the world’s devs into five distinct groups:</p><ol><li>Your <strong>Insiders</strong> are in the top right quadrant. They probably have experience building with blockchain technology and they have high awareness of your ecosystem or tech. They’ve already bought into what you do.</li><li>In the bottom right quadrant are devs who have extensive blockchain experience but no or little awareness of your tech specifically. I call these the <strong>Blockchain Insiders</strong>.</li><li>Next is the group I like to call <strong>Emerging Insiders</strong>. These are devs who have slightly less experience building with blockchain technology, and are not as familiar with your tech and ecosystem as the Insiders. They want to learn more and are keen to contribute to the ecosystem.</li><li>The bottom left quadrant is where it gets interesting. We have a group of web2 devs with little or no blockchain experience but who want to explore blockchain further. I call these the <strong>Curious Outsiders</strong>. They may have no idea you exist, but they’re a highly motivated group.</li><li>Lastly, we have the <strong>Oblivious Outsiders</strong>: web2 devs who don’t even realise a career in blockchain is a viable possibility for them, and likely have never heard of you at all. As you can see, they are the biggest segment by far — so much bigger that there’s no way to visualise them completely!</li><li>In addition to nurturing your Insiders, your marketing and developer adoption efforts should focus on moving developers from the left and bottom left quadrants to the top right quadrant. You want as many active, loyal, and qualified devs using your tech as possible. That is how you scale.</li></ol><p>So what does this mean in practice, especially if your DevRel and marketing teams are already spread too thin?</p><h3>How to design and execute a new developer funnel</h3><p>Think about the devs in your Insider group. How did they first come across blockchain technology? What piqued their interest? How did they hear about your tech? How did they <em>learn</em> your tech? What obstacles did they run into along the way? How did they end up building their project on your tech? Where do they find support?</p><p>By mapping out a journey from the point at which devs first become aware of and interested in a technology all the way through to when they are actively using it, we can come up with a strategy to ensure they see relevant messaging that reinforces their decisions at every stage of the journey, and that they get the support they need exactly when they need it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fIO3OvqqyYnr6KF4gt6aVw.png" /><figcaption>New dev funnel</figcaption></figure><h3>Stage 1: Developing interest</h3><p>At the very top of your funnel you need to capture the attention of your target devs. You do that with entry level information that answers the questions they’re asking at that early stage. If they’re new to the blockchain space, they’re curious to know how they can learn more about blockchain, about applications of your tech and the various use cases. They want basic information to validate if it’s worth continuing on the journey, or if they should be exploring other options — and even if your stack is the perfect choice for them, the wrong messaging at this point can easily drive them away and into the arms of your competition.</p><p>Your job at this stage is to convince them to further explore your tech and not the competition’s.</p><p>Your marketers are largely responsible for this stage of the funnel. They should have an education-focused content marketing strategy which includes up to three core content pillars under which sit a number of topics. For technical content, they should be relying on subject matter experts to ensure accuracy. They should be sure to have a solid distribution plan so the devs can find the content.</p><h3>Stage 2: Learning the stack</h3><p>If you’ve done a good job at Stage 1, new devs will at least have shortlisted your tech amongst one or two others and be ready to learn how to use it. Remember, new entrants don’t know what they need to know, and don’t even know what they don’t know! This means you need to give them a clear path to knowledge acquisition. Learning material provided at this stage is invaluable when a developer is assessing which protocol to invest their time and energy in. This is especially the case when the knowledge itself is not easy to assimilate.</p><p>There are two ways to design the learning:</p><ol><li><strong>Instructor-led</strong> — Devs are exposed to learning materials over several weeks as part of an academy program with expert support, skill assessments, and certification.</li><li><strong>Self-paced</strong> — Devs are exposed to learning materials via an open-access portal at their own pace, but without dedicated active support, assessments, or certification.</li></ol><p>At <a href="http://www.b9lab.com/">B9Lab</a>, we’ve worked with many foundations and projects to deliver both open-access portals and academy programs. They can each have an important role to play in a developer adoption strategy, which we will be covering in more detail in upcoming posts — so make sure to follow us on Medium to get notified!</p><h3>Stage 3: Getting involved</h3><p>Now that they’ve learnt about your tech, it’s time for the new devs to start implementing that learning, by applying for roles with a project in your ecosystem or building their own projects. At this stage, you need to show them that there are valuable opportunities to pursue and re-validate their decision to invest their time and energy in learning and using your stack.</p><p>Providing job information and having spaces where they can find other devs (and non-devs) to collaborate with on projects is an excellent way to support them, and to foster a sense of community within your ecosystem. For example, we’ve built our own <a href="https://jobs.b9lab.com/">jobs portal</a> to support devs who complete any of the programs we run for our clients.</p><h3>Where do you start?</h3><p>The important thing is to recognise where you currently stand. Invest some time in auditing your current marketing and DevRel activities and do research with your community to understand their journeys and needs. Next, consider what your developer adoption targets are for your next planning cycle, and tailor your plans accordingly. If you want to attract 500 devs that’s a very different plan than if you’re looking for 5,000! The numbers will depend on where you are in your organisational and technology lifecycle.</p><p>Once you’re comfortable with your strategy, make sure your marketing and DevRel teams understand and are working hand-in-hand towards the defined target. You also want to make sure that you’re tracking key metrics so you know what needs optimising at every stage.</p><p>Exciting? Yes! Impossible? No! But if this all sounds overwhelming right now and you feel that <em>you</em> could use some support, feel free to <a href="https://b9lab.com/contact">reach out to me for a chat</a>.</p><p><strong>Nihal</strong> is the head of marketing at <a href="http://www.b9lab.com/">B9Lab</a> and has over 17 years of experience in marketing and tech.</p><p>If you want to know more about identifying and supporting different devs with different needs, download our white paper, <a href="https://bit.ly/3ysr7u4"><strong>The Definitive Guide to Web3 Developer Adoption</strong></a>, and learn how to design a developer adoption strategy that fits your project whether you’re at 50 or 5000 devs.</p><p>At <strong>B9Lab</strong>, we’ve been designing and building developer adoption strategies for leading web3 organisations since 2015. Through our onboarding and learning journeys, we’ve minted thousands of developers. Our team covers the whole spectrum of developer adoption strategy and management. We’re developers, business strategists, marketers, and blockchain educators.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=532965f55511" width="1" height="1" alt=""><hr><p><a href="https://medium.com/b9lab/why-understanding-the-developer-journey-is-the-key-to-unlocking-growth-in-adoption-of-your-web3-532965f55511">Accelerating Web3 Tech Adoption Through Mapping Your Developer Journey</a> was originally published in <a href="https://medium.com/b9lab">B9lab blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The costly mistake web3 leaders need to avoid in developer adoption]]></title>
            <link>https://medium.com/b9lab/the-costly-mistake-web3-leaders-need-to-avoid-in-developer-adoption-7fc9868d6624?source=rss-44eab5ab53f1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fc9868d6624</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[web3-marketing]]></category>
            <category><![CDATA[developer-relations]]></category>
            <category><![CDATA[developer-marketing]]></category>
            <category><![CDATA[blockchain-marketing]]></category>
            <dc:creator><![CDATA[Nihal Salah]]></dc:creator>
            <pubDate>Thu, 19 Jan 2023 15:06:35 GMT</pubDate>
            <atom:updated>2023-03-13T14:33:11.777Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iorjBeO8tGSIYvVOlrlrRQ.png" /></figure><p><em>Energy and fuel crises, cost-of-living crises, job crises</em> — the economic downturn hit hard in 2022, and the prospect of a global recession gives us all a sense of dread. It’s no secret that, with a steady cascade of high-profile bankruptcies or scandals throughout the year, 2022 was also very tough on all of us in the blockchain space. Losses have been high, confidence has fallen, and the media has (again) been quick to conduct a gleefully preemptive post-mortem on web3.</p><p>But this isn’t our first crypto winter. <a href="http://www.b9lab.com/">B9Lab</a> has been around since 2015 and our founding team has come through at least seven such periods of instability and decline during the last five years. Whenever this happens, we see the industry freeze as so-called “non-essential” activities are put on hold until after the cold snap passes. Unfortunately, this includes developer adoption activities aimed at both web3 and web2 devs.</p><p>Even though it might seem logical to slow down or “pause” activities during a winter, doing so is consistently one of the most costly mistakes we see leaders of web3 companies make. We think that if there was ever a time to double down on developer adoption activities (and their associated marketing), it’s during a winter. Here’s why.</p><h3>There’s a cost of hibernating during a winter</h3><p>When things take a turn for the worse, it’s a natural instinct to duck and cover while you wait for the crisis to subside. Bears hibernate to survive, but at a painful cost: they reenter the world reduced to skin and bones, on the verge of starvation, and even then their survival isn’t guaranteed. They’re at risk during their long uncomfortable sleep and in the period of urgent, fierce competition over desperately needed food once the hibernation is over.</p><p>It’s a grim analogy, but think about what happens when you significantly reduce or pause developer adoption and developer marketing activity during a winter. When the market finally recovers, you can’t simply pick up where you left off as if nothing had happened. When you slow down, you lose momentum — that’s just basic physics.</p><p>For web3 organisations and ecosystems trying to build a community of devs who are actively using their technology, losing momentum is a very expensive mistake. You’ve got the sunken cost of all the effort that went into attracting and onboarding them to your stack (a cost that is often grossly underestimated), but there’s also the less tangible reputational cost to consider. When maintaining educational resources or providing training and support to new devs grinds to a halt, word spreads. And if your plans to scale involve large enterprises using your technology, you’re at an even bigger risk of jeopardising your reputation. It’s infinitely better to project the image of an organisation and technology robust enough to be around for decades to come.</p><p>Developer adoption shouldn’t be seen as a “nice to have” that can be put on hold: it should be at the core of your business.</p><h3>The benefits of investing in developer adoption during a winter</h3><p>There’s another important reason to keep or even increase supportive activities when times seem tough. Retention is the most under-recognised benefit of investing in developer adoption during a winter.</p><p>Devs who enter an ecosystem during a downturn are stickier and more engaged in the long-run than those who join during a market peak — 33% vs 25% according to research by Electric Capital. This means investing in supporting them with educational resources and training increases the likelihood they’ll stick around.</p><p>There’s another benefit to this investment: you send positive signals to the market about your organisation or ecosystem, and of web3 in general, which naturally attracts even more devs as they view you as a place to establish themselves and build a reliable career.</p><p>Long story short: if you make proactive moves to deal with the hard times, you get the drop on those hoping to wait out the winter. Not only does this approach benefit you, because you’re building a community of devs who know your stack and encouraging their loyalty, it also positively impacts our overall environment by deepening a web3 dev pool that right now is just a microscopic fraction of what’s available in web2 space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tBJrsi5o8hL4yrsy" /><figcaption>Web3 devs as a percentage of the total global dev population</figcaption></figure><h3>Adapt, but don’t stop</h3><p>We believe that, within reason, we should be bullish in a bear market. To be clear, this doesn’t mean you should never make changes or even reduce some of your activity. The point is that you need to carefully assess what should be changed, reduced, or stopped, and do so with full awareness of what the long-term costs might prove to be.</p><p>At B9Lab we’re doubling down on marketing and educational content because we believe that this is what will give us the highest return on our investment. We’re actually spending more on these activities now than we were before the market crash. We’re also working closely with our clients to ensure their developer adoption strategies are optimised and continue to deliver a return, for example by exploring ways they can sustain the same activities through different sources of financing.</p><p>Crypto winter isn’t the time to retreat inward, curl up protectively, and desperately hope you survive while sleeping through periods of difficulty. It’s a time to invest in anticipation of the thaw, to take the steps necessary to bring devs in from the cold when they need support the most.</p><p>If you want to explore alternatives to the problems we’re discussing here, make sure you follow us on Medium and get notified when we release our Developer Adoption whitepaper.</p><p><em>Statistical interpretations in this article are partially derived from Electric Capital’s Developer Report (2021).</em></p><p><strong>Nihal</strong> is the head of marketing at <a href="http://www.b9lab.com/">B9Lab</a> and has over 17 years of experience in marketing and tech.</p><p>If you want to know more about how to defy the crypto winter and instead build momentum for the future, download our white paper, <a href="https://bit.ly/3ysr7u4"><strong>The Definitive Guide to Web3 Developer Adoption</strong></a>, and learn how to design a developer adoption strategy that fits your project whether you’re at 50 or 5000 devs.</p><p>At <strong>B9Lab</strong>, we’ve been designing and building developer adoption strategies for leading web3 organisations since 2015. Through our onboarding and learning journeys, we’ve minted thousands of developers. Our team covers the whole spectrum of developer adoption strategy and management. We’re developers, business strategists, marketers, and blockchain educators.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fc9868d6624" width="1" height="1" alt=""><hr><p><a href="https://medium.com/b9lab/the-costly-mistake-web3-leaders-need-to-avoid-in-developer-adoption-7fc9868d6624">The costly mistake web3 leaders need to avoid in developer adoption</a> was originally published in <a href="https://medium.com/b9lab">B9lab blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>