<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Rocco From Brooklyn</title>
        <link>https://paragraph.com/@rocco</link>
        <description>undefined</description>
        <lastBuildDate>Fri, 20 Nov 2026 21:25:10 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Rocco From Brooklyn</title>
            <url>https://storage.googleapis.com/papyrus_images/687027afbebd42aaf96634c08a5b52b9</url>
            <link>https://paragraph.com/@rocco</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[The Digital Watering Hole is Dead ]]></title>
            <link>https://paragraph.com/@rocco/the-digital-watering-hole-is-dead</link>
            <guid>HUkSlSmmZL8j7j6SLRv3</guid>
            <pubDate>Wed, 18 Mar 2026 00:44:46 GMT</pubDate>
            <description><![CDATA[This is a follow-up to a piece to something I wrote last year: The Internet is Dying, and It’s Going to be Okay. The optimism I had then was soft, but directional. I believed that in a world full of slop we'd retreat to smaller, curated digital spaces. A year later, the internet is pretty damn dead, but the retreat is playing out interestingly.]]></description>
            <content:encoded><![CDATA[<p>I haven't written anything in almost a year, but I felt like it was time to finally do so. This is a follow-up to a piece to something I wrote last year: </p><div data-type="paragraphEmbed" data="{&quot;post&quot;:{&quot;id&quot;:&quot;IUuQ9YNsyFTsDH18w7LE&quot;,&quot;slug&quot;:&quot;the-internet-is-dead&quot;,&quot;title&quot;:&quot;The Internet is Dying, and It’s Going to be Okay&quot;,&quot;cover_img&quot;:{&quot;img&quot;:{&quot;src&quot;:&quot;https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/328c02f6939363b65d15eaad653de5f4.jpg&quot;,&quot;width&quot;:2912,&quot;height&quot;:1456},&quot;isHero&quot;:true,&quot;base64&quot;:&quot;data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAQCAIAAAD4YuoOAAAACXBIWXMAAAsTAAALEwEAmpwYAAAGG0lEQVR4nAEQBu/5AKyyfLW5gJ+ldZ+oeZigczJCMxgxKC9HOSo6KiU4JhcoGSUzHTY9JGdrQ2NsQHyIXKGqeIeUaaGodZ+peH6RaF99XFRzVXGIY3GIX4mYZ56nb4CPYXiEWZOdaHaEV3GDVADBvoPDwoSqsH2tsoFsd1sIHRsZMysXMCkSIx4BFBAIGA4hLxw3QSNNUyZocT5qdkpSYj+Unm6wtoGGlmmElGp3jWhIalBLbE5BYEdWb0+qrnaytnuVoW2XoG2ElGKDlGIAsrV/ubmCnaR3Xm5SLkE3ABcXABERABUVAA4OABUVDh8YJzsqJDckMUEmX2w+UVcqaXBDra99laBxfpBmeo5oeItoPV1JJEY5JEc4R2dJhJRkn6hym6RxjJtqc4NZd4VbAJ2kd7C4g3B/XCI8MipBNgEWFgIXFgAWFQAJDAAJDggbGA4fGxYtJCtCMyM0JDtDJHF3Sc7NjrK5g4OYamyEZFRwWDNVRDtdRSxOPDpaQmV9V26EXoOUZm2DXGR2UXF6VACWo3eVoHOVoHNrgWRPalcoQjgKHRoEFhgACQ8AAAcAAAcAFRcUKygKHBsQIx1MYEFhckuTnW6stICDmW1wiWhlf2JSclc4WUUwUT46WENLZ01edlVdfFVJaUpsgluDlGUAsbeBqrB6k6F2aX9lJDs0EiklAA4SAAQMAAYOAAMMAA0SABUVFi8nIjcrMkk3Z39bfI5kpK17pa9+i59zaIZlY4FiUHFVKU09N1hCQWBISGVMXXlYbYpgYoRdgptukqd4ALK5hcXGj6a0iTRQRQAVFwMUFQAOEgAEDAAABQAHDgAGDgIVFhUlIzZINyA9MEZjSqSwf8fIi6y0f6GteoGacFp9X0xtVEBiS0NjS1h0VWZ+W36VaYifcpapeqK2haa5iADCyJPKypyyt5OFlHY5TEEJHx8AFRUACw4ADREACQ4JGBgmOzQSLSoGIiM9XU2UpH6To3ixuYOpsoCwt4GxuIF4kWtjgGBgeVtdeFmElmyZp3eYqHmdrX+Up3mYsIGmuIcA3N2n7+y7/vnQ4uG2hY9xmqWEdIFwXWxWUF9KAhQVFyYkLkQ7SWdVaIRsrbuR7uqsx8qRn657rLaBt72Eub2FtbuDkKF0d4xocYdloKx7tb2EprKAnq5+la19m7SFvcaNAO3tuPDwwfz4z+/txLq+lPX2wP//4/74y+ThrRUgHU5VRtzdprK9j83Vou/qrd3an87QlJ6seZCgcqeyfcDCh8TEir7BhZqoeKGtfrvAh7C7hYepgYyqgZSyhKm9is/PkQD09r7u8LT29sD//9Lx8b7u78jPzq/LyKTe2q0uMy8sNzH39Lf//L3h3q3v6rHj4KK4voanr36hrXmyuYDAwojGxorBwoattYG+wojEx4umuoiGrIOHrIS/x47Hx4va0pEAgYxfd4FSeINWgodaaXJJX2hLLTYtICYlUFJHY2lWCRwdm52B5Nuk9fG6+vG98uyz3tqf0NCSysqNzcqMysqMyMaKw8SKvcKJy82Uxc6Uv8uSv8qQyM+T2dKU19CT49uaAA4nEw8jEgASBgAEAAAMBwAMBwASDgASCwIZDyI4IzhGKWBjPHhzPsG3a+Tblf31t//6wf/4u+7mpebeouHbnNPQlM/LkdPNkrC9lrPGldLVltvVltfSkdPPkd/XmOnhnQAVLBsIHRYAFRQGGxsHHRkAEQ4MHhQPIxYPIhgXKhc2PBlNSxxJSxB9cQChjgSxoii/r03i0YD056H/+br/97n+87Pt5aPq4KBHXlOQmnTq4J3a0pTV0JLb1JXn3p3o4JwAAhkWABcWAA8OABUUABYUAA8JAA4FABQICxoMBBYHIicJODsNSEwFbWYAcWcAWVgAX10AiX4Aj38VpZQ8wa9e3M2D7eObureGFyImkZN29+yn5tya39eX592b7eOh7eSgAAAZEQAUEAADAwAMAwAGAQAPAgAUAggdChQoDQoYBhUcBzEyCzQzBSYsACgvADc8AD9CAE5MAFpWAFlSAGhfAGZdAHhvF3ZxK1ZdKXN9Tuzgm/HkoOndmt3WktfPi+DXlMb2oyaQj2/GAAAAAElFTkSuQmCC&quot;},&quot;publishedAt&quot;:1721050403699,&quot;post_preview&quot;:&quot;This is a bit of a shorter post, but it's just some observations on how the internet has felt lonelier and darker.&quot;},&quot;blog&quot;:{&quot;name&quot;:&quot;Rocco From Brooklyn&quot;,&quot;lowercase_url&quot;:&quot;@rocco&quot;,&quot;logo_url&quot;:&quot;https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/2434754896b5719eccef996a39f39383.png&quot;},&quot;hasCoins&quot;:false,&quot;supporters&quot;:[],&quot;supporterCount&quot;:0}"><link rel="preload" as="image" href="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/328c02f6939363b65d15eaad653de5f4.jpg"><link rel="preload" as="image" href="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/2434754896b5719eccef996a39f39383.png"><div style="margin:20px 0"><div style="border:1px solid #e5e7eb;border-radius:8px;overflow:hidden;max-width:600px;margin:0 auto;background-color:#ffffff"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/328c02f6939363b65d15eaad653de5f4.jpg" alt="The Internet is Dying, and It’s Going to be Okay" style="width:100%;height:auto;display:block;margin:0"><div style="padding:16px"><a href="https://paragraph.com/@rocco/the-internet-is-dead" target="_blank" rel="noreferrer" style="text-decoration:none;color:inherit"><h3 style="margin:0 0 8px 0;font-size:20px;font-weight:600;line-height:1.3;color:#111827">The Internet is Dying, and It’s Going to be Okay</h3></a><table cellpadding="0" cellspacing="0" border="0" style="width:100%;margin-bottom:12px;border:none;border-collapse:collapse"><tbody><tr><td style="vertical-align:middle;border:none;padding:0"><div style="display:flex;align-items:center"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/2434754896b5719eccef996a39f39383.png" alt="Rocco From Brooklyn" style="width:20px;height:20px;border-radius:4px;display:block;margin-right:8px"><span style="font-size:14px;color:#6b7280;font-weight:500;line-height:20px">Rocco From Brooklyn</span></div></td><td style="vertical-align:middle;text-align:right;border:none;padding:0"><span style="font-size:14px;color:#6b7280;line-height:20px">Jul 15, 2024</span></td></tr></tbody></table><p style="margin:0 0 16px 0;font-size:14px;line-height:1.6;color:#6b7280">This is a bit of a shorter post, but it's just some observations on how the internet has felt lonelier and darker.</p><table cellpadding="0" cellspacing="0" border="0" style="width:100%;border:none;border-collapse:collapse;border-spacing:0"><tbody><tr><td style="vertical-align:middle;border:none;padding:0"><div style="display:flex;align-items:center;gap:6px"><span style="font-size:14px;color:#6b7280;font-weight:500">0 collected</span></div></td><td style="vertical-align:middle;text-align:right;border:none;padding:0"><a href="/@rocco/nft/IUuQ9YNsyFTsDH18w7LE" target="_blank" rel="noreferrer" style="display:inline-block;padding:6px 16px;background-color:#f3f4f6;color:#374151;text-decoration:none;border-radius:9999px;font-size:14px;font-weight:500;line-height:20px;white-space:nowrap">Collect</a></td></tr></tbody></table></div></div></div></div><p>In short, the optimism I had then was soft but directional. I believed that in a world full of slop, we'd retreat to smaller, curated digital spaces. A year later, the internet is pretty damn dead, but the retreat is playing out in ways that are more interesting than I originally thought.</p><p>The dead internet theory is a doomer idea that I personally subscribed to quite early. It follows the line that the internet is filled with bots, there aren't any real people left, and it's all just botted interactions that lead you to believe there are signs of life. Honestly, we've hit that point. </p><p>A supermajority of accounts on major social platforms are estimated to be automated, multimedia content is increasingly synthetic, and it's getting harder to tell what's happening (war media being a great test of this). The theory isn't wrong and is really playing out as anticipated, but at least there's a bit of hope for some good to come of it. What I've been thinking about since is what happens <em>after</em>  the "public square" gets annihilated and looks like a wasteland of slop. Specifically, where people actually go, what they start to use, and what starts to matter as a result.</p><h3 id="h-back-to-a-readerly-web" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><strong>Back to a "readerly" web.</strong></h3><p>I touched on this briefly in the original post, but the internet has had a long, messy era of ownership (yes, I call it that even though we could argue semantics). Social media gave everyone a megaphone, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://dlsanthology.mla.hcommons.org/from-reading-to-social-computing/">but the writerly web</a> is collapsing under the weight of synthetic content and even worse algorithmic manipulation. AI slop, partisan bait, and aggressive advertising have now become dominant much more quickly than anticipated.</p><p>What's replacing it can be seen as a regression, but honestly should be welcomed with open arms, is a readerly web defined by passive consumption of curated content rather than active participation. Think Substack and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://davidzmorris.substack.com/">creators you have an actual connection to</a> over Twitter, and passively reading a feed again without the necessity to engage. There's a nostalgia angle to this that I think matters as well. The internet doesn't really yearn for "old Twitter" or "early Facebook," but knowing that the person on the other end was real and brought a bit of their genuine selves to the table. </p><p>Engaging with various subculture-driven forums (shoutout GameFAQs), Myspace pages, AIM away messages, and early blog comment sections felt great and worked because they were small enough that trust was ambient. You didn't need verification because the community itself or your personal web of trust was the filter. We're not going back to that specific version of the internet, but the instinct driving that nostalgia is pointing somewhere useful: toward spaces where you can actually trust who you're engaging with.</p><h3 id="h-verified-spaces-both-digital-and-physical-become-core" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0"><strong>Verified spaces (both digital and physical) become core.</strong></h3><p>This is the part I keep coming back to. The only digital social life that survives this shift is one built on verification. Not traditional IDV or some compliance nonsense, but the kind of assurance I wrote about in the original post. Knowing that the people in your group chat, your community, your forum are real humans who were invited or vouched for by someone you trust.</p><p>The digital spaces that will matter are gated, human-verified, and small enough to maintain signal. Discord servers with real moderation, subscriber-only communities built around specific subcultures, group chats where membership means something all will continue to grow. These aren't new ideas, but they're becoming the default rather than the niche. Platforms that figure out how to enable this at scale, through subscriptions or transaction volume rather than ad impressions, will be the ones that matter. People will pay a premium to know they're engaging with real people.</p><p>As digital spaces lose signal, physical presence also gains a premium. When you can't trust that the person replying to you online is real, showing up somewhere in person becomes the highest-signal thing you can do. That same nostalgia I mentioned earlier applies here, too. People are spending more on experiences to chase the feeling of being around other people in a way that the internet used to provide, and no longer does. Concerts, dinners, bars, and local meetups are returning as core gathering points, and they're growing because they offer something more meaningful than what's online at this point. </p><hr><p>A year ago, I said the internet was dying, but it would bring us closer together. I still believe that. </p><p>The digital watering hole as we knew it is gone, overrun by bots and stripped of the social contract that actually made it work. But people still want to connect, and the nostalgia everyone feels for an older internet isn't really about the internet at all. The spaces that win from here, digital or physical, are the ones that earn it back.</p><br>]]></content:encoded>
            <author>rocco@newsletter.paragraph.com (Rocco)</author>
            <category>deadinternettheory</category>
            <category>ai</category>
            <category>physical</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/7e4d43abcfa03f159f91f9fd2b4621ed4be12ce719fe672d018555fb0b9b3f57.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Entrepreneurial Nihilism ]]></title>
            <link>https://paragraph.com/@rocco/entrepreneurial-nihilism</link>
            <guid>nPeOKA2AwFpPUZJ2Fer9</guid>
            <pubDate>Tue, 15 Apr 2025 22:55:49 GMT</pubDate>
            <description><![CDATA[This might seem slightly self-help coded and controversial, but I feel it's necessary to talk about what helped me realize that there's more to life than work and that feeling fulfilled personally (first) leads to extraordinarily better outcomes. Too many founders are continually burning out from a self-destructive culture cultivated by venture capital, post dotcom startups, and the ugly side of hustle-and-grind culture - specifically in software. Oftentimes, I find LinkedIn-coded advice floa...]]></description>
            <content:encoded><![CDATA[<p>This might seem slightly self-help coded and controversial, but I feel it's necessary to talk about what helped me realize that there's more to life than work and that feeling fulfilled personally (first) leads to extraordinarily better outcomes. Too many founders are continually burning out from a self-destructive culture cultivated by venture capital, post dotcom startups, and the ugly side of hustle-and-grind culture - specifically in software. </p><hr><p>Oftentimes, I find LinkedIn-coded advice floating around startups that center on founders having to live and die for their startup. I believe it's important for founders to make their startup a significant part of their life and to be dedicated to solving the problem they set out to solve. However, I think it's important to recognize that the death of a startup is common and that the only way to succeed is to have your personal needs met before even being able to focus on a business. </p><p><em>That is to say - if your startup dies, everything will be okay, and that's the healthiest way to be an operator. </em>You should be afraid of your startup not succeeding because you care about your idea, not because of the death of the startup itself. Your life and personal needs should come first, and you should also have a healthy degree of disconnection from your work life. There are two 'zones of reality': your life, in which you need to first find your fulfillment and comfort, and your job, which is the cherry on top. </p><p><em>Fulfillment in work is a product of your personal needs being met. </em></p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.ebsco.com/research-starters/psychology/maslows-hierarchy-needs">Abraham Maslow's Hierarchy of Needs</a> illustrates the original part quite well, outlining what people truly require in their life, and in what order. It starts with basic needs such as physiological (food, water, rest) and safety, followed by psychological needs such as belongingness and love, and finally, self-fulfillment at the top (once all other needs are met). </p><figure float="none" width="484px" data-type="figure" class="img-center" style="max-width: 484px;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/3cc818d01f91cf3b457636b9ab53a1e1.jpg" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAASCAIAAAC1qksFAAAACXBIWXMAAA7EAAAOxAGVKw4bAAACcklEQVR4nGP4T2PAQKqGP3/+/P37l/oW/AUbeuvW7ZOnTv/69QsiggwotQACKurqSytqXr169efPn//EAaIs+At24NbtO0OjYkOj41euWffp06dHjx4/fPT46dNnDx48fvLkKfkW/AWb/vTps+T07Oj45Oj45NTMnLNnz505c/bOnbtfvnz59OnTly9fKbWgb9KU8Jj45PTM5PTMyNiErr5J7z98ICa2CVjw5w/IiAOHDielpOcUFGbl5Gbl5hcUFaekZWzZtu3Lly9wF5BjAUTn6zdvomITXD18vfxCQkKjQkKjvPxC3Dz8w6Piz52/ADcdlzX4LIAklbb2HmtbZzcvf2d3n6CQsKCQMGd3Hzcvfxs7l6aW9tdv3pw7f+HCxYt37967d/8BZurCaQFE6Y6duzV1jI3NrIzNrK1tHSHIxs7Z2Mza0NRKW99kxcrVDx48evnyFa7cgN0CiNL37z84u3uraepp65voG5rZOTjZ2DnaOTjZOzrrGphq65uoaOi6efjevnMXT7bAbgFEQ0lpFRe/uIy8qoSMMghJKykqaympaEpIK0JEZORVeQXF0zLzvnz5SkIcQEw/ePCwkJisqIQcBAmJyQqJySqrassrq0PYEHFhcRBjx87dDx48OnHi9M+fPwlYAHHIt2/fNHWNGRgYGBh5GBjYGRjYuAXEBcQkuQXEufjF+UUkeYXEweLsYAUMWvomV69eu3v33vfv3wlYAHF+fWMLyHAOAQZWXggSFJOSkJYXk5ITlZSVkJYXlZAFGQ2R5RBgYGCoqm2EFIJExcHTp8/Q0KNHjyGFz+MnTx7CSiE09PMn0RZQEQAAQsR/pP5NHXYAAAAASUVORK5CYII=" nextheight="692" nextwidth="1200" class="image-node embed"><figcaption htmlattributes="[object Object]" class=""><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.frezza.com/en/psychology-design-maslow-hierarchy-needs-theory/">Source</a></figcaption></figure><p>What has been distorted is the inclusion of one's startup fitting in the belonging, esteem, and self-actualization categories when it should sit atop self-actualization as a tiny part of it.  Self-actualization should come from one's personal creativity, spontaneity, hobbies, and more - not the development of software for capital reasons. The way I've found useful to balance this has been through entrepreneurial nihilism. </p><p><strong>Entrepreneurial Nihilism </strong>is the idea that a founder can first accept the upper bound of what they do as "important" in many contexts, but is oftentimes meaningless in the greater scheme of things. The next SaaS, productivity app, ad network, or game won't be the next great thing for the world, even if it achieves a critical mass of users or occupies someone's attention for a given period. It may be part of this small part of self-actualization for someone to build and ship something, but it shouldn't define your entire life and personality. </p><p>Through this awful blend of work with someone's needs, we've also created this idea of a performative "founder struggle" as something to be admired. The performative "founder struggle" is for social media; it's not healthy or productive. You getting no sleep, existing on a beanbag chair, and bragging about how hard you're working isn't cute or healthy when you could be taking care of yourself and getting more meaningful output in a shorter amount of time. </p><p><em>The artificial LinkedIn crowd might applaud this, but you're effectively handicapped in any productivity you think you're having.  </em></p><p>And that is the core of entrepreneurial nihilism. You will create your best work when you're not making work your entire personality and neglecting your personal needs. I'm not saying to not care about your business; I'm saying you shouldn't make your business your life so you can be a more fulfilled person and take that energy back to your business. </p><hr><p>One additional note in light of this as well - there are many people who could create great businesses but are unfortunately still managing the bottom of the pyramid. These people are often overlooked and should instead be highlighted wherever possible. Please don’t talk to me about the Stanford grad “roughing it” when they have a family and their basic needs met to fall back on.</p><p>Nobody genuinely struggling has the full opportunity to put themselves 100% into their business, and it's also why founders from these backgrounds are often unfortunately overlooked and are few and far between. When you're still at the bottom of the hierarchy of needs dealing with your personal life or taking care of your family and don't have the means to dedicate that time to a business, it should be obvious why this is the case. If you have the means to focus on yourself, do that first - don't put on a show for social media. </p><p>When I go to happy hours or meet people at events - even networking events about a particular subject- there's a time and place to talk about software. Let's talk about food, let's talk about hobbies, let's talk about sports. I don't care about "what you do" when I first meet you - we'll get to that later. Be an entrepreneurial nihilist. Take care of yourself, and don't form a personality around your work life. Enjoy your work, but don't let it consume you. </p><p>Go touch grass, don't worry - your startup will be here when you return. </p>]]></content:encoded>
            <author>rocco@newsletter.paragraph.com (Rocco)</author>
            <category>business</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/de87467d2817b4c42842f760a5907413.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[The Internet is Dying, and It’s Going to be Okay]]></title>
            <link>https://paragraph.com/@rocco/the-internet-is-dead</link>
            <guid>IUuQ9YNsyFTsDH18w7LE</guid>
            <pubDate>Mon, 15 Jul 2024 13:33:23 GMT</pubDate>
            <description><![CDATA[This is a bit of a shorter post, but it's just some observations on how the internet has felt lonelier and darker. ]]></description>
            <content:encoded><![CDATA[<p><em>This is a bit of a shorter post, but it's just some observations on how the internet has felt lonelier and darker - with a drop of optimism around what comes after this current phase.&nbsp;</em></p><p>As social platforms continue to be muddied with AI-generated content and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.urbandictionary.com/define.php?term=Hate%20Bait"><u>hate-bait engagement</u></a><u>,</u> we’re in for an interesting shift in how we interact online. I believe we’ll all find solace on more concentrated platforms, with a renaissance of internet forums and more sophisticated tooling for vetted group chats.&nbsp;</p><p>But for now, we have one last curtain call for large social media platforms.&nbsp;</p><p>It seems that The Dead Internet Theory is becoming increasingly correct in predicting the end of mass-scale human interaction on the internet – but really, it’s just the end of the <em>writerly purpose </em>of large social networks. The core idea behind the theory is that the internet has become dominated by bots and that there are few organic interactions between real people. It supposedly originated in the late 2010s but was amplified to more mainstream audiences after Kaitlyn Tiffany from The Atlantic <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.theatlantic.com/technology/archive/2021/08/dead-internet-theory-wrong-but-feels-true/619937/"><u>covered it</u></a>.&nbsp;</p><p>Although her article recognizes the difficulties in applying the theory to the fullest extent, every year has brought us a bit closer to bots winning. All content is increasingly becoming AI-generated and posted to serve some end, such as selling a product or generating hate with manipulated engagement.&nbsp;Very rarely do you find conversations between actual humans online, and when it’s "important", it’s two humans in an arena of bots.&nbsp;&nbsp;</p><p>The theory’s timing was quite impressive, as it seems the internet was on a collision course towards this end. Changes in OpenAI and social media platform incentive have truly accelerated it. Websites such as X now fully incentivize any form of engagement, leading toward countless Tweets and endless amounts of replies that aren’t even related but serve to generate views and harvest likes. Facebook has become a <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.npr.org/2024/05/14/1251072726/ai-spam-images-facebook-linkedin-threads-meta"><u>cesspool of AI-generated content</u></a> geared towards baby boomers, and we even now have <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://link.springer.com/article/10.1007/s00146-023-01857-0"><u>AI influencers</u></a> taking the place of actual people.&nbsp;</p><p>Given the sophistication of AI at the current time, replies on social platforms could just as easily be generated to sound as if you’re engaging with a real person. But people are slowly figuring out that some of the most incendiary responses are just being generated for the exact purpose of engagement:&nbsp;</p><figure float="none" width="443px" data-type="figure" class="img-center" style="max-width: 443px;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/62d494ad63823b04228029e5c9bf4a13.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAfCAIAAAAJNFjbAAAACXBIWXMAABYlAAAWJQFJUiTwAAAGLElEQVR4nJVWy47kthWVRIlNUu/qKqmqH5mqUulFcShpVA+pu6ftBjKTBDa8sRcG7B+IjRjIMlsv7GSTAHGQRRAgqyCA/yYLb4J8SLIIJiBZXV0zyXjGZyFQVxQv7+vcq2m6PgpCXrF4OmVlZmTXxqz0bYwIcRzX9wPHcRHGlmUhhIltAwC0twMAQNd1sXp+d/ubr79KVun7P/3Jo6ufzVh/fjZN0vTy0fzs/GKVZovFcjY7m88Xi+UyDMPJZDIejzHG36/Asqy9gvnl2c3Q2baTJMmPLmasKpOVQBRFQRAURZGsVmVZJklSFMVisWCMUUrDMNQ0bX/E98CQAKYJISSEIIQhhAihE4SILYAxgRBiLORv6ZxXFQAATNP0fZ9zThlnjNd1kxdFVVXyyaqqatsnZVVZlqVu/eaLv6LAsizTtGzbgRAdDAcmQAgfn6Xruu041sumQAht2yG2fZBgjLFwBjIMY+8i07SACTAhxz+bpmnbtlJwuDWxbVPacQDC2PU823GOJRhhW6WcrulojNyZa+iG4ziuhG3bQiUwlfdMUyxEpCzr7dP03nRD+/NfPvv7d39KqkfvvnP37PnzHz97ttlszi8uZ2fnkyiOp9NH8/nodOz5fhTHYTjSdV0mhoDULW4gvHF8uqadIKQr4a+++OCvf/xssbh4XDfL5TLL8yzPS0oZY0kiMraqKs7rLMuzPKs4bxqxrWmaruuathVJTOnZ2dlrg6xugzEOw1B6RsQcABFh13UhhDJIe3c5rut5/glCB9dBiAghliWCZxiGruuEEIyxaVq6bmgGMAAwZBaZjuOapnnQDUzT9TyMybFbsU2CICTkIWcIIUEYoqPCVpXkuq4ImDJAKjQt09ROXA0+nPiDYBjGYrnMiyLLc0KODunq+heff54X5YcfvOe9+6l+8UTXNN0wXldL+v9UGZB2f/zJJ//6z4vv/vHPf7948bdvv1V0JD5fbZ/88oufE2KPJ9F0Noum8ezsPIqnUTxVf74RSmWe57/9/TdffvXr333zhw8/+kjZpBkAOI6gHAMAJB0FIVRZDyG8D6OQ7OXikwDGWIUdSqj1cbLuDTUtq+K8H4ayLFdpyhgrq6pumqZtOedd17Xtk7ZtKaV93xdFudlsKom7u7u6aZLVqu8HznlRFpvN5vb2drfrl0nyoABCKOmMzefztm0ZY0VRbrfb1SpljJeUpmla17XgQUp3u10iy6Lv+yRJOOdVVe12fZpmiszbthV7kkRViQg1hDCXqKoqzTKVXq7rYow9z1O04fu+J+E4gtRc1/V9H2PBNmpt2zYhxJUbXNclohs6QRCINEUI1U2TZRmlVVGUvu+rb6pYFKSTEULY930igZAoLs/zVKtQCpQ+hJB63cfjBCFKaV3XVcWyLG/aVnhgGCilbddtt9u8yNM03Ww2eZ5vtlsuqWK73RZFwRjr1mvGeNO2fd/v+v5xXV9dXQ3D0DSN67p7BVmWpWnKJUpKr6+v0zTr1us8z9frddd1aZo2TUtpxTm/ur7e7XrKWFmW8/mCMV5xXpblerNpu26xWG6324uLi5eC/LiuJYW1o5FgSpmjgnxEmlqWJR0k2OmefATbSy5S2xRxKS5QtKYYaZ+tEMK6bjjnjLHlMplOp2EYxvF0NpuNx+MgCCaTSRRFYRiOx+M4jn3fV/Lz8/NJFF1eXo7H49Hp6SSKJpPJYrEIgmA2mz3MHKZlFUXZtm1eFJTSLMu4LIubm6eM8Twvbm/fubl5mue5ykJKq7ZtSyrY/Or6uuu6YRiUl5qmVf4chiGKon2QIYSNxGq1yvOcipGk2mx2ak6p67qVtVbeQzaDZLlMsizf7XayW7D1ep1lmXB1xbquS5JkGAbKmOQpCYQQhFC2KhEDAPaetW3b8zy1Vm1ZtTP1fGXCOGwQa+NeDoAZhqNJFE+i2PP80elpODoNgjCeznw/2O12T29vJ1EcxTFCbxjl/j8OTfygX1jx8u30o4sf1sd4nVCcawAgKMHzjCMn6Lqu5ov91nuVGBM/CFSPO6jHGPuh6HHHvwMAXM+TCgzDFZzjvdJGHNcNAjF9HgNjHISj434phISMRqeO/TAXqZkqHI00TfsvDgTVOXEHDB4AAAAASUVORK5CYII=" nextheight="1172" nextwidth="1202" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>We’ve arrived here by incentivizing the wrong kinds of behavior across social platforms, favoring raw engagement rather than meaningful engagement. Likes, comments, and views increasingly became measures of “successful” content, so naturally, controversial posts became kindling for such a fire. There was a misguided attempt to ‘return’ incentives to creators, but it ultimately led to bots <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.scientificamerican.com/article/how-twitter-bots-help-fuel-political-feuds/"><u>continuing to drive political discourse</u></a> and views to generate returns.&nbsp;</p><p>So, while a few of us are still trying to communicate online for reasons other than generating engagement, we’re all likely to retreat elsewhere for meaningful discussions.</p><p><strong><em>The question is, who's left, where are they currently, and where are they going?&nbsp;</em></strong></p><p>Besides being buried in tweet replies, the real people you want to speak to are in your group chats, emails, one-on-one text conversations, and niche internet forums. People who wish to have meaningful experiences on the internet and participate in a writerly web will slowly entrench themselves deeper in these mediums. Large social media platforms will widely become grounds for spectators of brands, news, and sports, rather than generating any meaningful discussion.</p><p>More <em>human</em> interactions require assurances about who you're talking to. I originally described the concept <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://blog.spruceid.com/decentralized-identity-and-web3/"><u>here</u></a>, but essentially, levels of assurance represent the trust cost based on the stakes of what you’re doing—in this case, the belief that you’re talking to a human being on the internet.&nbsp;There are two ways we typically have high assurance about who we’re interacting with on the internet: meeting them in person or using peers to validate that someone is who they claim to be. </p><p>There are very few venues in which we can have guarantees about talking to authentic people and having truly meaningful interactions on the internet, and that’s why we’re likely to retreat to curated group chats where members are selectively invited. The market opportunity here involves building <em>around</em> curated group chats and what you can do with them.&nbsp;Whether that's deeper forms of engagement within the context of a conversation (threading discussions, interactive activities within a chat, etc.), or just different ways of imagining group chats as something beyond just quick replies. </p><p>Internet forums function similarly as well, encouraging long-form, hypermedia-rich discussion, but run into the aforementioned issues unless they're gated. Although limited incentives exist for someone to post on a forum other than genuine interest in a subject, the cost of attacking a forum is quite low. It would be cheap to eclipse someone entirely in a forum where they think they’re speaking to real people to sell them something or try to influence their thinking.&nbsp;Again, in these scenarios where it's meaningful interactions, we'll likely have to curate groups and have some high assurances around group membership.&nbsp;</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/eec93ced5557d3dcb1f893759d778ce4.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAICAIAAAAX52r4AAAACXBIWXMAAAsTAAALEwEAmpwYAAACL0lEQVR4nI3SwWvTUBwH8HfpPPWUy/wHSnvJvULE9RKFXjrpQA1IUadCDgsU0h6Ga2XN5igMXrALK7yNZgTepDwK5mJOj01CB4GOUEbXQy4ryGgR7A7OwxMTKDgc+Dl94b3fD97v/cDPvw37/bNeLzg/909Oznq9bxcXURj2+1E47Xa94+PTbnfY719Np1EVC0Xh49ra64ePdtfXr6ZTxhiIzhhjv66vGWOWrteLxWatZlQq79+8/XJ4qK+uNmu1erGoPn1mVCrvXrxs1mrRhcnl5Y3yzwcHz4X7H1ZWnqTTxaWl75MJME0Thxo7OwghtL+vNxqmZTX39ja3tlqtVse2253Op3a73emYlvVqeVktl+vb26ZlOY5jhyilnuf5vv/16MjQdYRQA8JdXfd9H0iSxPM8AIDjuHg8fnd+PhaLcRwHALiXTpumiRAyDKNcKrmu+3hx8c7cHAglEgnHcUjItm1VVQuFgqqqDxYWZFlOJpP5fF5VVUAphRCKosjzvCRJ2WyW53lRFDOZzGAwGI1GlFLf9z3Pc12X5/lqtZrL5URRFAQBQsgYG4/HP0IQQoSQpmkIIUVRNjc2yqUSIIRE/3MDu0UQBAihfx5pmhYEAWOMEBIFhBBwHGe2AP/JdV3btkVRNAxDURRN0xRFIYRACA3DoJRijMfjMWMMY/znBUEQzIZAQ07Itu1oxNEWzES9UqlUoVCQJEkQhEwmU61WMcayLGuaRgiJ+mCMfwO1FgpMT3A0KwAAAABJRU5ErkJggg==" nextheight="380" nextwidth="1521" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">Broad social media will no longer be a home to human engagement</figcaption></figure><p>All of this is to say that we're in for an extreme shift in traditional social media towards a more readerly experience with limited human interaction. <strong>I'm not saying that this is novel in any way - </strong>people have been having deeper discussions and sharing ideas in these kinds of concentrated groups for years - but I think it'll accelerate a renaissance of features around those mediums.</p><p>It's fine to accept the fact that we're likely going to be using existing social media platforms to continue to scroll endlessly, but bots will likely drive human interactions and groundbreaking new ideas to smaller groups instead of 'the public square.' Eventually, these 'public square' platforms will be around to release information to the world, but further discussion and the advancement of ideas will go back to group chats and forums. </p><p><em>The internet is dying, but it'll bring us closer together. </em></p><p></p>]]></content:encoded>
            <author>rocco@newsletter.paragraph.com (Rocco)</author>
            <category>dead internet</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/328c02f6939363b65d15eaad653de5f4.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Everything I Wish I Knew About Hiring ]]></title>
            <link>https://paragraph.com/@rocco/everything-i-wish-i-knew-about-hiring</link>
            <guid>kYDyVVSpYHHbIMNJzibV</guid>
            <pubDate>Wed, 05 Jun 2024 15:02:08 GMT</pubDate>
            <description><![CDATA[This is a bit of a different post from me, but I thought it was important to share my thoughts on the hiring process with some of the startups I work...]]></description>
            <content:encoded><![CDATA[<p>This is a bit of a different post from me, but I thought it was important to share my thoughts on the hiring process with some of the startups I work with. When hiring people to grow my startup, I naturally made some mistakes, assuming it was easy. Most of the sections in this article could apply to any startup, but some are geared more toward early-stage companies that might be scaling from a handful of individuals to their first growth phase as a team (~10-20 individuals).&nbsp;</p><p>I’m going to break down each section, but effectively, the process for hiring is as follows:</p><figure float="none" width="460px" data-type="figure" class="img-center" style="max-width: 460px;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/55e7af574857e617983ba12717bd95f2.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABoAAAAgCAIAAACDyf9SAAAACXBIWXMAAAsTAAALEwEAmpwYAAAGSUlEQVR4nI1WfUwTZxx++WtzcWywTUCZbENFKHTyMbEBP1agOuTLDRhVDKMOBk4QNhCWNLOzLMxBYoxbMyWWeJ1tvC7XccPzA3vqpVbtHzU5x81VqbHZOr0/bsYbSPZC34W7rHYC0yeXN/fxu+f9/X7v8z53AM3CdCj0VUdH88ZNrSWljRpNbX5+/dvqXSUlXdXvt5WW2QcHEUIQwtkvIoTA7Fu/3b3bUV5Rr1AmAfAGAAVxizcuXroSgOUAfKouVMTHuy5fno9xDroH4+N7qqubclZXp6W/m5L6viJja7pyy/KULctTWvPXb1apqrXa27dvz8k4Bx1CaPT6ddJud1LUGZKsq6kZwnHSbh/56SfK4fhLFG/8+mtzc7Pf75/NODddJCiK+nFoaPjkSXJ4+Mehoc/37mUYxu/3t7S08Dz/VNlBCCcfPpx8+BAh9IXBUFdX92VPz7Zt21pbWgoLCsxmM0KIYRiDwfC0dPJoldDe3s4wDISQ53lBEKAEhBCGYQzDRJYMIIRT0uOpfw85KY7j9Ho9x3EIIUEQ9Ho9QRDhyWTwPG+1Wp+c3e/BoOvSJUEQwjMLgoDjuMweWYHVag0EAo/ogsHgVYa5cuGC69w517lzv1y7dnD//rycnGuXLwckNcgIBAKCIGg0Gr1eHwgEOI7z+XyCIJjN5sh6QU9r6/qYRWuiYzUJr1anpKkXJWxYlLA2Nm5TfGJzSSlCaEqKGxgYIAjCJMEsAcMwmqbdbjeO4xF0O3fWK5QZALy1YGF1SqoyKkoBQPazz+kyMj9Yuw6GQnIoSZIej8doNJIkeeDAAZqm+/r6uru7fT4fTdOP6A739+9QF7SWlNbm55dnZlVkZZdnZm1MTdNtUA/09iKE/p6cRAjZbDaHw2Gz2SwWi9VqJQiCJEmKonAcNxqNj3o3HQpNh0Lwvwf/55/fHDly8vRp2RHkcToUmpyaEicmghJ4nhdFESGkVqvPnj0rJwjk1oQhX44MDVWqVMkLF35WrzM0NuqKi3dXVXVv3972XuXBffvCYVAa3W53r1THDN1jEpHjOrTa5lzVqmcWvACAMipqBQBJACwFoCEzp7GwcHJKVuqjPAwGg8/nm0N3Mp3+w4ZUMIMMAFIByH/x5SQAEgFYBsAOdcHk1NRj6nO73RiGzSvjmzduUDjusFgcFot+9+59e/Yww8NOh8N16tStCCWHASHEMEwUxf9zlPDMh48coS9cYEdHqTNnrly9Ktf1WBjDMCzLzmsB4c1LURSGYYODg1VVVdnZ2ZWVlSzLznY6nudJkpw3Ozk6GAz29vaaTCa3281xnNfr9fl8c9o6hJAgiP8zKIqiTCYTz/MQQrPZLItrTk+H0p0Zuvm+SRzHYRgm+y2EUBRFo9FIUdST6EIzWn8wPv5gfFycmBDu34ehkLa2duDo0UgflU86Ozt1Op3cKVEUBUEQJYTNCnzb09Oo0dTk5VWqVCWrMt9bnVuTl5e9ZElLSekPx46FlcjzPEVRBEHo9Xqr1YpLoGna6/WSJOn1ekVRNJvNoL2srF6hVEZFrXspruy1ZGVU1DIA1kTHNuWs7qqtnQ6FZDqPx8OyLE3TOI7LPcVxvK+vjyAInudpmuZ5HsMw0FJW3pCZs/6V+NzomKKExFXPLMiNjtmwKEGXkbm3qSmcHcdxJEmyLCsbH47j52naZrOdoiiPx0PTNCWdgLGbN0+R5DBBME5nU0OD9dgxxulknM4Riop0YwjhrbExdnT0pjTaTpy4NTb2x717t+/cYUdH5aX3+/0zdGdI0m6xkHZ7RXFxf2+vi6Yv0bRLyj9y+ZwUZR8ctJnN5kOHNq5bZxsYoHB82GYbslp/ZlmTyTSzZ3eWllYtX7lp6evFS9/Ymq4sSUouiE+sWLZCuzLt685O4f59QRB4nv/++PGPC4vq0lcVJSRuTVdqFcqihMTc6JjajDd3qfJ0VdUXXa4ZusbCwoLYuDTJ0MteS1Y9H7MCgJUAFMTGtdfUnDx9+rzU/uycnM7izc25qlQANi9JUr8cnyz9EBXFLWlfv6G7oUFeNLC/q+vDt9UVWdnvpCk0KanvpCnKM7O256/9qLDo+HffhZdifGKiv7t7r0534JNP9+/a1d/W1t/WdmhPV39bW4dWe3FkRLbPfwBTCiuzEwytAQAAAABJRU5ErkJggg==" nextheight="910" nextwidth="742" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>We will be specifically reviewing the parts highlighted in red.&nbsp;</p><p>As an early founder, your first job is to do everything. This includes product, engineering, BD, marketing, selling, and negotiating.&nbsp;Now that we’ve established that, your next job is to identify scaling issues in your organization based on an actual need instead of a perceived problem. It’s very easy to say you need to hire for something, when in reality, it’s something you can solve yourself or not a legitimate problem the organization is facing:</p><figure float="none" width="382px" data-type="figure" class="img-center" style="max-width: 382px;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/2dcb2a910163346434836bf5cb50ad69.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAASCAIAAAC1qksFAAAACXBIWXMAAAsTAAALEwEAmpwYAAAClElEQVR4nJVULbOrMBDNP7gKgcFUUIPBxKAwMVUxUVFRmDgMChUVh4mLiqqKwqHqqlA4XBSuqo47l53X6fTj9r4jmHzs7mGzZxetn3DdAAvnHMY4TfdFUfR9fzv/xR19jL5u37ZtoyhK033btkqptm3jOE7T/TAMv3P8RgBu3vvdbkcIGcfxwcB7n2VZ0zT39n8iANNlWRhjRVGcz+fbW90DjNu2pZTO8/ySA73L7ng8YoyNMbC9XC43yxvBZcO6rsMwpOm+qiowu8frDIwxVVUty7L+GfM8I4Qopfd5/BB47xljnPPDBkoprKWUjDFCCGNMCEE3gJu1tq5rKaUQAm4551VVCSHAUUpZ13VVVX3fI4yx9/6B9kGd6waQ5jiOGONpmpZlmec5hADPcrlcQgjLsoQN1+tVa53nOZJSTtMkhIjjeLfbfX19SSkRQoyxJEmiKEIIJUkCSh2GQSklhKjrOooipVSa7jHGWZaVZck2CCEQQnmeO+cIIYhzPo7j6XSC1IQQwzBQSo0x0zQ1TSM2rOvaNM2NYBiGw+HQdZ2UsixLQgjnvOs6pZQxBuJYa38IgNla2/1D0zSwVUpZa51z3ntjTBzH0zSFEDDGzrm+7621x+Ox73vvvXNOaw3uSinnHFQOzfNsjLHWaq2VUnqDEAKi683HbjidTlAM4IPDruvatoVfruuaEEIpBXet9TiOj30A2yRJEELvZHp90zr1hkeZPrfouq4hBKUUxphzDq30stFAPHDOOWeMPdx+GBVQ2CRJlFL32n0IMU1TWZbQ8y9GxbvOvM+GEBJFkdb62R/Gat/3/zfsnmnO53NRFAghQkiz4aZ3KNW7wnwguNHAIoRQVVWe51mWFUUBurqfrM8E3zewJmvX5fEiAAAAAElFTkSuQmCC" nextheight="321" nextwidth="584" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>Problems should come from success, or being on the brink of success rather than being invented by some intellectual quest. You need an internal way to validate success to justify hiring someone. This could include KPIs that you set based on product adoption, or even closing contracts and not having the resources to handle an increase in business that you’re generating (with good margins, of course):</p><figure float="none" width="641px" data-type="figure" class="img-center" style="max-width: 641px;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/a392131a6a592ef708d29f4592c76d65.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAQCAIAAAD4YuoOAAAACXBIWXMAAAsTAAALEwEAmpwYAAACC0lEQVR4nKWUK5TrIBCGUdFXRkXFrYyKQ+JwSORIJBKJRNYiI7FYLBIbW4vFsqfMtqe74p7t9hM54TUvfob090gpxe+klMLAe7+uK3nH+vV6VUoZY/Cr7+Cw977vO2mtvWq3DXrvUkpKqVKKMbYsy77vWmtKKQAopVprnPObg9Za/Q6e/7F0HeBSznkaAADGjlFba51zAJBS6r0LIYhzzhjjvb9cLt774zi890qpUkpKCc9bawFAa422jDGMMa11790O8Lhz7uEmhNB7BwCitW6tLcsCAEKIbduO4wghUErnecZNYsA5Z4xhXPu+b9tGCJmmyRgjhKCUSimttYwxGHw5YIwZY6ZpWtf130AIgfEKIbTWnPN5nimlaPRyuXDOrbU555QS5xx9rwMMAm323o0xBPflnGOMOedzkFLCuscYSynneRJCrLWoy1KKlBJnYowoSvzB7I/jKKV8Ofi/WvqdnDOl1HuPw1prCIEQ8vHxYQYoUCyXUupxQy+8g1qrEAJzfyhVCLEMCCHzPGM9t21TStVatda/ddDuFo0xAPAYOudQSEopKSWqzjmHud4u+fcZ9HvRjuOQUp7n+aOMz5znOU3T7aG95KDfLZZSACDG+Jzc8waUU2vtL72oDRO1VjeotT4mn1sIbv57s0NbIQRr7XO58NE9hm91U+xU8zyjhCilhJBt257v5hP8GHmGUH3GCwAAAABJRU5ErkJggg==" nextheight="540" nextwidth="1051" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>After affirming, “Yes, we have an actual problem,” leaders typically draft a job description. This is a great way to waste time and potentially not find the candidate you’re looking for. Instead, return to the identified problem and draft a scorecard.&nbsp;</p><div class="relative header-and-anchor"><h3 id="h-why-and-when">Why and When</h3></div><p><em>Note: much of my process is inspired by </em><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://whothebook.com/"><em><u>The Who Method</u></em></a><em>.</em></p><p>A <em>scorecard</em> consists of outcomes and personality traits you’re optimizing for when considering opening up a role at your organization. There’s no ‘correct’ way to create a scorecard, and it doesn’t necessarily have to have a template. It can exist purely as a list you jot down in your notes or an email somewhere.</p><p>One way to start a scorecard is by listing and defining five immediate things you want this candidate to do. When thinking about these tasks, define them similarly to key results or key performance indicators with specificity and outcomes in mind:&nbsp;</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/ff192fcdb770837b45c1844025e921cf.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAMCAIAAACMdijuAAAACXBIWXMAAAsTAAALEwEAmpwYAAADOUlEQVR4nIVTTWjcRhgdX3vxZUkXuoeFDI2gSqgO62LhDlhtqsL0Z9qyKSp4IIimOsjQxaCGihBBY0wVgi97CNvDFpYS6xC1oEPYurgHQapDsxdflhSUHpyCbKykrWwvUrxTdoeIhUL7TsN88+a9+d43gE3Rn8LzPN/3Pc8LgoDN4LeHD7fv3TtMU8ZYnueMsU6no+u67/u9Xs80TYSQaZqcxQ/cuH79y7W1k9EIZFmWJInjOIQQCCHGGCHUaDQGg0Ecx4yx3x89enNh4QUAzE+vlHzLskRRVFVVURRZllVVrVQqiqJwQ91Ohywvv7W4eGWFgp2dHYxxvV4XBAFjbFmW4zimaUIIW60WY+zu1tY7S0tfXb36ar1+Oh7zKyilpmnWarVqtWrbNiEEAOC6Lq/euHbt7JkzSmPh8qVLgDEWBAEhxLbt+Smq1SqEcHNzkzFWFMXpeLzSbL7yUu2b27fLF0RRZBjG+vq6JEmUUlmWbdsuqweHh2urq45l/fH48UQgTdM4jpMkCYIgDMM4jsMwHA6HZQZ5np+MRqV9vlMiyzLGWDYFr3Jbp+NxURQTgf9FnudFUXB3swKzSv+mcIA4jtvtdr/fHzyH53lxHPPXsOeOjo+OZ/lZlmmahjHudDrdbtd1XUKI4zi8ejoeHx8d/f3nX4yxiYAoihBChBDGWJZlAACfDUIIv33j1s33Vz65+8P3ZZeDIBAEgVKqaZooioIgqKqKEPI8b5LB/sGq/cXbH38UhuGkRZ7naZo2NzdXqVSMKTRNMwwjnQ7+na2ts0sLL7/+Wl08Nzo+4Un0er1Go+E4jqZpAAAIIY/61wcPJlP09Yb47sXq+XMXP3gP7O7uJknS7XYxxpqmSZKEEKrVakmSRFGUZdlgMDj/BoLLix9eXnlWPOMCSZJQSkVRpJTqui5Jkuu6lmXxnH/8afvC8tKLjQufrX0OLMuan5/HGBuGoeu6YRj8Q0AIm80m7+n9X+5v3Lp5sL9fBtDv94MgoJSqqkopRQgJguD7fhRFe3t7jLHtn3e+vfPd0ydPQDlnaZry9X8MBl8Mh0Nd11utVrvdxhgTQmRZbjabhBBFUZIkmaX8A3uc+99wdz+SAAAAAElFTkSuQmCC" nextheight="265" nextwidth="688" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>If the requirements you write feel too loose to you, it’s because they are. In addition to those outcomes, write several traits you feel this candidate should possess when working on your team. This helps with eventually writing the job description and helps filter any inbound candidates based on your initial screener with them. These traits could include things like: “overly communicative,” or “individual contributor”.&nbsp;</p><p>By writing a scorecard, you might find the role begins to change based on the outcomes you’ve outlined. What originally started as a full-stack developer might be a developer relations specialist, or a backend engineer might be a product engineer, or even an operations lead might be a chief of staff. That’s why it’s important to draft a scorecard before a job description: you narrow in on what you want to hire for.&nbsp;</p><p>Now we can write the<em> </em>job description. Your job description should consist of five points:</p><p><strong><em>An Introduction</em></strong></p><p>This is where you’re not just describing the company and what it does, but <em>selling</em> the company. You’re a startup, not a worldwide phenomenon – and a candidate is taking equally if not more risk and opportunity cost by joining you than you are on them. Take four to five sentences to describe your company’s vision, what it produces, and why someone would want to work there. Talk about how you want to change the world and the type of individuals you want along for the journey. Don’t write a book, and get to the point.&nbsp;</p><p><strong><em>A Set of Responsibilities</em></strong></p><p>These should be heavily based on the outcomes you’ve defined in the scorecard earlier. Define at least five of these, but include no more than seven; these typically evolve after hiring a candidate. Be sure to scope these down as much as possible, similar to the scorecard. A candidate must read these and feel comfortable knowing exactly what they’re signing up for when they apply to work for your company.&nbsp;</p><p><strong><em>A Set of Qualifications</em></strong></p><p>These qualifications should be the necessary minimum to meet those responsibilities. Unless you want to spend an eternity hunting for a unicorn that would have an extremely narrow set of qualifications, make sure these are reasonable relative to those outcomes and responsibilities. Again, define at least five, but include no more than seven.&nbsp;</p><p><strong><em>Bonuses</em></strong></p><p>These are things added to the job description that aren’t necessary for candidates to have, but would increase their chances of being selected for the role. You can base these on abilities or some of the traits you’ve outlined earlier. For example, if you put “self-starter” as a trait in your scorecard, you might have “previous experience at a startup” as one of these bonuses, or “contributed to open-source software” if you’re an open-source software company.&nbsp;</p><p><strong><em>Outro</em></strong></p><p>Use this section for any odds and ends you wish to include in your job description. This could include notes about vacation policy, benefits, company culture, etc.&nbsp;</p><hr><p>Now that we have that out of the way, you might ask yourself “but what about title and compensation?” Let’s have an honest conversation about titles. You may or may not be at the point of defining strict leveling at your organization (if you’re early, this is a distraction), but you’re going to have to make a few decisions based on your philosophy, which will impact your candidate pool (and be hard to adjust later):</p><ul><li><p>What is your philosophy around titles against the amount of experience a candidate has?</p></li><li><p>Do you pay based on region if you’re a remote company, or do you have salary bands?</p></li><li><p>How do you weigh equity versus salary at your current stage and money raised?&nbsp;</p></li></ul><figure float="none" width="468px" data-type="figure" class="img-center" style="max-width: 468px;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/45b28ffc55877db56932a14b6ecc63ea.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAVCAIAAACor3u9AAAACXBIWXMAAAsTAAALEwEAmpwYAAAETklEQVR4nJWVMWjcVhjHdZs2Lxo03KBBwxtu0aDlDRoE6Q0i8DKIIgKCRCYVRpQK4tcUEVBMVIziWK6ryYZec6Il50GFyBREQRgciCFwpLkmHKG9djhwrsGOG0Qod+RUrJfKx0Gp80eIT0+f3u997/u+J6rb7bqu63meZVmGYWiaJssyhFAURaFUo5QkSQghy7Jc142iqDi3KIxxkiTj8TjP8/G/Iu8qoyht4pPneRAEBwcHcw7/CXBdl/iRexRFNE3ruo4xBgCYpgkA2NraqhhFUcRxnCTJeQGWZRHr+PjYtm3DMBBCLMtCCHVdBwBQFGUYhuM4g8GAeMZxnKbpeQEIIWKNRiOKohiGaTQaCKFarWZZVrMUhJCiqArQ6XRIBHmeV5HNqRqnZFmuIkAIqapK8kk2CiFEkkzTdAVIkuQDIoAQVg/kA57n6/U6AMBxHEVREEIkpZVDBfA8D2McRVEQBJZlmaZpGAbJn+/7hmG0Wi2q0WjMAobDoSAIuq5DCDmOYximXq9nWTaX5CzLxuMxyZ9lWYqihGGIENJ1PQxD27a73W6/31dVlQIAzK7O8zxJkhzHMQxDlmWaphuNhmEYs4AoitI0HQwGQRBkWaZpGkVRoihijBmGqdVqFEV1Op2iKGzbfg8gX6ZpKssywzAAgCAISI2yLCtJ0mzhE8BwOAzDEGPMcRwAQBAE27ZVVdU0DQDAMEySJJZlnUWQ57nruhDCer3O8zzpaq1c3cLCgizLpBNJFaVpOhqNHMcpikLTNJZlydSqqrIsy/M8xrgoCtM0z3IQBIGmaY7j8DwvCAKE0Pd9TdN0XV9YWOA4zvf9uTKVJClN05/StNVq7ezsRFEUx/HanTtfbWykadrpdDDGp3tXFEW326VKoVI8z7Msy3FcEASiKEqSRFqE7OzW1hYxer1eGIbftttfrq7iGzdM07xy9aq7shJsbn5z7147io6Pj0/7YDQaNZtN3/dpmhYEwXVdRVEAALBUq9VqNps8z9M0zfN8v9+P45gA3k2nvz9/vrq09HB392v8+fbKyvfr66tL1tqnn3nXrnX39t53cp7nrVZrOBySDhBLQQglSRJFUVEUvZTnebZtj0ajuBTJ+ZuTk/6TJyevX/85HP727Nmrw8NfHj/++dGjP168eHNycgowTbPqgyzL6vU6x3EURSmKIsuyYRg8z9dqNVVVqyr6sLOInKZVjYdhCCFUVdUuxXGcIAjNZpNMRw6fudN0MpnMTTo7cgro9XrVi8lkMruuSflYDZK77/v7+/vnjYD80VzX1XX9yuLiJVX9SFHkCxcuqapy8eLHly8vmuYnlvXFzZvLGK/cumXbdhAE/zvvGYAs5N10+tfR0fbt2+21tfthuPfgwfr16/fDkFzttbXvNjZeHR6+m05nf3nnBRD9/fbtj1H0w/Z2dPfur0+fZnH8cHc3i+ON5eW273c2N49evqw27fyAfwBJ+lq+GAANOAAAAABJRU5ErkJggg==" nextheight="423" nextwidth="650" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>For example, your philosophy about titles could be either lean or extreme, depending on how you want your organization to evolve.</p><p>These three questions will help you find the answers you need to think about the role’s title and compensation. Remember, compensation can always be discretionally adjusted - it’s good to have a set schedule for evaluations, but it’s ultimately up to you as a founder to set this. There are plenty of tools, such as <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://pave.com/"><u>Pave</u></a> or <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://carta.com/equity-management/compensation/"><u>Carta</u></a><u>,</u> that can help you benchmark compensation. </p><div class="relative header-and-anchor"><h3 id="h-where-and-how">Where and How</h3></div><p><em>Defining a role is fun; sourcing, interviewing, and hiring are difficult.&nbsp;</em></p><p>You are the master of your destiny when it comes to talent. The more work you put into sourcing, the greater your outcomes. You’re not just going to post a job description, especially as an early startup, and have quality candidates breaking down your door to work for you. Sourcing can come from various places, but I recommend starting in your backyard, depending on the industry you’re coming from.&nbsp;</p><p>For example, if you’re a blockchain startup, you can source from any of the following areas:</p><ul><li><p><em>Friends and allies -</em> start by sourcing locally. This includes your entire network and your friend’s networks if they know of anyone on the market that might be a good fit for the role you posted. These candidates typically come pre-vetted through your own experience, or a referring party.&nbsp;</p></li><li><p><em>Investors - </em>Typically, investors have a roster of talent that they keep and provide to portfolio companies as needs arise.&nbsp;</p></li><li><p><em>Conferences and hackathons - </em>these act as great gatherings both for information and for hiring as well. You might discover talent at a hackathon or meet someone at a conference who is competent and looking for their next role at a new home.&nbsp;</p></li><li><p><em>Various corners of the internet - </em>this includes both traditional and nontraditional means. For example, LinkedIn is always a simple place to look for candidates, but you can also try unique ways of vetting talent, such as looking at an engineer’s GitHub contributions, finding a marketer’s profile on Twitter, or even finding a business development lead active across multiple industry groups or forums.&nbsp;</p></li></ul><p>Don’t waste your time with aggregators like Indeed—you’ll spend more time sifting through bad resumes than interviewing quality talent. I also wouldn’t recommend working with a recruiter until you’re at least a Series A company with a consistent hiring process. </p><p>There are two types of recruiters you can work with: <em>contingency</em>, or <em>retained</em>. Contingency-based recruiters will source candidates for you, somewhat manage the introduction and first conversation, and charge you a percentage of the candidate’s yearly salary as a fee. The contingency model is typically success-based, so no matter how many candidates they may send your way, they only get paid when a candidate gets hired. </p><p>Retained recruiters typically charge a monthly fee, but spend a lot more time working with you to find the right candidate and spend additional time helping you directly manage the hiring process. Both models are expensive, but ultimately, the time they might save you is well worth it, depending on how specialized the roles are.&nbsp;</p><p>You should also use an Applicant Tracking System (ATS) to manage this process. An ATS typically helps you post job listings, manage candidates and the interview feedback process, and everything else until the offer letter. You can think of it as a CRM for people who go through your interview process, but instead of selling software, you’re selling them the idea of working for your company. </p><p>There are plenty of ATS providers out there, but I typically recommend <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.ashbyhq.com/"><u>Ashby</u></a>.&nbsp;</p><p>Once you’ve had a few resumes to review from all of your herculean sourcing efforts and inbound interest, it’s time to ensure you have your interview process squared away so you can invite candidates to go through it.</p><div class="relative header-and-anchor"><h3 id="h-who">Who</h3></div><p>Before inviting a candidate to interview, you should have several things defined:</p><figure float="none" width="381px" data-type="figure" class="img-center" style="max-width: 381px;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/931833a9a19097133a0134820b442740.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAVCAIAAACor3u9AAAACXBIWXMAAAsTAAALEwEAmpwYAAAESklEQVR4nJ1VUWhaZxT+H3zJmw++iAQCQYSACD6JIAQhIEggLCCECW5uKxJoZmpNui7JXawmJq6mu10ag4mZqcFOGEUncZ3U1e4Whw+SG6SX1CL44GYr+HCHYrw1Z8Sf3BnTpGPfw8/5z/3PPfc733/ORQDwnKLmnIt7kR9bxy0A4DiOX6FjYPDbi097TvIeAECZ7B/zG2t3H4c/nZ3ei0QAgKbpbDYLANVqtVwuA0Cz2azX63wYtvGKnel0mmEYfDKVSuFw/AgFHu19tXXf6VmZ+XZpdfN7AJDJZFarVS6Xy2QyqVQqFApVKpVYLCZJ0mw2I4QkEglCSKlUlkolmUw2NDSEEEomkzKZTKlUog5CoRDOgZJPn348++VN0m31OncjjwCAYRiWZb1eb7lcLhQKmUymUCj4fD6Komq1WiqVKhQK0WiUpmkAyGazNE3n83mWZQ0GQyqVYhgmGo1iQqcM2u/asf342rbv519/aTQa7y00nK91D3rk6QECgEKh8GB9/TB/2B3TPAPXKTdvd68YvN3t5JOhQ5o2zk7b/d99cutG6nkaAIrFIlbpIkqlUs8b8ddkMhmscD6f72Ww9XD39p7P+s3Xny3Yp5cWAcA+Y9doNEqlUq/Xq9XqXC6n0+mkUikWECupUqmKxaJCoVCpVAqFYmBgQKVS9fX1qdXqnlqhWDxmnJ2+TXqurRALbhe+hfF43GQyBYNBv99fKpVCoZDJZHI4HOFweGJiIhQKkSRZKpWSyWS0A4qivF6v0WjEDM4laDQam4Gt9Z/C5A9blT//ulrP/wF0AtBoNJJPnrw+OnqvyNDhxLIs3mLBedn5HuSd3eGnCf5m2RkHMbm6+Pmc/XEsBgDtk3b3IZZlcVas7dXfi8/XarV/GezuhewP7t7Z8V1fnJtZdXIt7iXzUq/Xp9NpuVw+PDwsFovdbjdBEAaDIZlMEgThcrkIgvB6vQRBODool8t+v9/tdut0ukAgYLFYHA6HzWbL5XLot2fPrrnmplzETXJ5ykUAQDAYNJvNiURCIBAoFAq3263VahFCk5OTFEWJRKKxsTGNRoMQ0mg0IpFofHy8Wq2OdKDVammatlgso6OjCCGfz3fayVsPdy1LhG3ZEd/fv9jAcMa9uxQ9bdVTKOypVqvNZhNxHNd+1+ZaXOv4mJ8QvG7cWRvzknR3dTe6O7/bPh0VR69era7f9wd3WsfH3deUV5W7ZOhfxuDcNX375q3lzvxKLGx1Ehs72wBwApDL5XBYpVIhSZLtgKbpSCSCp0itVisWix/qgU6C31+8+GLNccu5aFt2uAIbXIs7ODhACOVyuZGREYFAgBAaHBzEIms0GqFQKJfLJRJJf3//ZRP0XIJ8Pm+0XZ+6t/TR/I0FjxtPNIqiWJZNJBIURVUqFY/H43K56vV6tVplGIaiqGw2S1HUf2IAAJlMZtW/fm97802l8sGAi7+KqxP8A3LOTt7YxbNzAAAAAElFTkSuQmCC" nextheight="326" nextwidth="492" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p><strong><em>Define an Owner</em></strong></p><p>You’ll need four things, and the first is a primary owner and guide. This will either be the person managing the hiring process or the person managing the candidate if they are hired at the company. This person is responsible for staying in constant contact with the candidate and setting up all of the necessary interviews with team members.&nbsp;</p><p>Giving a candidate communication whiplash, where one person tells them one thing and another tells them a different thing, is a great way to lose them, and ghosting them is even worse. Don’t do that—their time is just as valuable as yours.</p><p><strong><em>Assemble Your Crew</em></strong></p><p>The second thing you’ll need to do is define which team members will be involved in the interview process. Interviewing is an art that involves proving to the candidate that you’re going to be a great team to work with by engaging in conversation with them, and receiving the right amount of information to evaluate whether or not they’ll be a good fit for the company. </p><p>If you’re uncertain about a team member’s ability to interview someone, don’t include them in the process. Each team member interviewing a candidate should be able to provide detailed notes about their conversation and evaluate them on a numerical scale that you set for your process to rate candidates.&nbsp;</p><p>One golden rule: if they’re not a <em>hell yes</em>, they won’t be a great fit.&nbsp;</p><p><strong><em>Have a Formula&nbsp;</em></strong></p><p>This process's third and most important part is defining your screener interview and loop. Your screener conversation should be a 15-30 minute conversation led by the primary owner with the candidate to gauge their interest, ask them about their resume and experience, and see if they pass some of the qualifications you’ve listed in the job description. It also allows the candidate to mention discrepancies between their resume and your job description. </p><p>One thing I liked doing during a screener was applying the airport test. If my flight was delayed for 6-8 hours, would I want to be stuck in an airport with this person? It’s a great way to see if the candidate would make a good culture fit for your startup.&nbsp;If they pass the screener, the primary owner then coordinates with the candidate and team of interviewers to set up a block of time to conduct a loop.&nbsp;</p><p>I try to discourage teams from having a million scattered conversations with the candidate. Instead, schedule a block of time to loop the candidate through several of your interviewers. Depending on seniority, we would typically use a 1.5-2.5 hour block to loop the candidate through 3-5 interviews. This way, instead of 30-minute blocks all over their schedule, the candidate can talk to each team member during the same session and doesn’t need to break up their schedule in a strange way.&nbsp;</p><p>These interviews typically cover the candidate’s job history in the first interview, followed by several focus interviews covering very specific subject areas to test their aptitude and see if they meet the requirements for the role.&nbsp;</p><p><strong><em>Follow the Script&nbsp;</em></strong></p><p>Returning to the previous point about your team, the fourth part of the process involves having a united front. You want to ensure that when the candidate asks about the company, the answers are consistent, and you also want to ensure that every team member knows what they are responsible for during the interview process.&nbsp;</p><p>Your job is to sell the company as much as it is to evaluate a candidate. They’re taking on risk to work for your startup, and there are plenty of other opportunities that would come their way coupled with better short-term compensation and security. Don’t just turn it into an interrogation - tell them about your vision and ambitions, and have your team talk about their experiences working for the company.&nbsp;</p><p>Finally, if a candidate makes it this far, one thing I encourage companies to do is have a <strong>paid</strong> assignment. If you ask someone to do work for you, regardless of the outcome, pay them. By doing so, you're showing them that you value their time. </p><p>Assignments should take the candidate no more than 2-4 hours for a standard role or 3-5 hours if it’s a leadership role. It should have a very well-defined objective while not guiding the candidate towards any means of getting there. You’re seeing how they approach a problem statement you give them, and evaluating their solution based on their route to get there. </p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/193f6ea64e5af15b330c88f8a40edf91.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAADCAIAAAB9IJo7AAAACXBIWXMAAAsTAAALEwEAmpwYAAABLklEQVR4nAEjAdz+AKSoplddWEZMSFphW1ZdVk9VUImNiubm5sLDwmpwbDM5Ni81MD9FQEtRTG1zb9vc3PX19X+FgUdMSEtRTHJ6c3Z8d252cKuuq+bm5oODgzMzMyMjIy8vLzs7O2BgYIyMjACGlIiar58ACAAADgAAAQCOoZKLm46JiIlMUk3L4tDD1sY3RzwdKyDS6NauwrGAg4FXV1eTo5QtPTECFgYhLyMAEgBkd2mSn5RIR0imp6dTU1McHBxPT09HR0dkZGSxsbEApKiml5+ajZWOdnx3cXhyjJONm5+b////z9HQjJONd394XGJeT1VQhIyFjZWOy83M5ubmjpSQkZeScXhyYGZhg4qFl5+aqKqo9/b3ubm5tra2p6enlZWVjIyMkZGRu7u7lx+LclbyxsMAAAAASUVORK5CYII=" nextheight="82" nextwidth="1032" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>We’ve now reached the references and offer stage. If candidates pass the assignment step, ask them for 2-3 references. It’s good to optimize for people they’ve worked with prior or collaborated with in the past. You should expect the references to want to guide the conversation towards the most flattering things they could say about the candidate.&nbsp;</p><p>However, your job is to ask them about the bad times. Ask them about when the candidate had to make a tough decision or struggled with something—you’ll learn more about the candidate's human side rather than their pure work side. Frame it as wanting to learn more about how to best work with them and adapt to their working style from a position of aid - not scorn. You’ll learn more by doing this instead of asking about their working relationship, which will be completely biased.&nbsp;</p><p>When speaking to a reference, you should tell them about the company, your vision, and how well the candidate did during the interview process. If they’ve reached the reference stage, they know they did well enough to do so, and it shouldn’t be a mystery. </p><p>If these all check out, it’s time to give a candidate a formal offer in writing.&nbsp;</p><p>I don’t have much to say about job offers other than the following: if you <em>really</em> want to hire a candidate, do what you can to close them. At this stage, this is a sale more than a recruitment process. Make them a competitive offer and give them room to counter if you expect they will. </p><p>Don’t get offended by a counter-offer (unless it’s completely unreasonable); you can even mention to a candidate that you use software to benchmark compensation so they don’t have unrealistic expectations.&nbsp;Also, don’t get offended if they tell you they have another offer they’re considering (to use as leverage), or if they gracefully turn down the offer. </p><p>You might do the same thing in their shoes - <em>I turned down an offer for a job at an amazing company to start SpruceID instead.</em></p><div class="relative header-and-anchor"><h3 id="h-1-what-some-closing-notes">1) What - Some Closing Notes&nbsp;</h3></div><p><em>Just wanted to include a few closing notes here:&nbsp;</em></p><p>Don’t be afraid to fire individuals having issues at your startup. There isn’t time for rehabilitation beyond 30-day reevaluation periods if a new hire struggles (bar outside emergency or medical issue). Additionally, they eventually become a drag on the rest of your team. You’ll know firing someone was the right decision if there’s zero or positive impact the next day on productivity.&nbsp;</p><p>Also, you don’t have time for interns at this stage. Your time is valuable, and you don’t have the time to train them. They typically require much more management unless they can accomplish an extremely well-scoped project during their internship that requires minimal oversight. Also, pay your interns - experience doesn’t pay their rent.&nbsp;</p><hr><p><em>Now, go off and hire for your next role. </em></p><p></p><p></p>]]></content:encoded>
            <author>rocco@newsletter.paragraph.com (Rocco)</author>
            <category>startups</category>
            <category>hiring</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/09257b77eeef23566f304b1447890100.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Joining Ethereal Ventures]]></title>
            <link>https://paragraph.com/@rocco/joining-ethereal-ventures</link>
            <guid>uGOrYPZZ0Ooty4OkoGPI</guid>
            <pubDate>Sat, 01 Jun 2024 00:00:00 GMT</pubDate>
            <description><![CDATA[I’m excited to announce that I’ve joined Ethereal Ventures as their Head of Portfolio and Platform. ]]></description>
            <content:encoded><![CDATA[<p>I’m excited to announce that I’ve joined <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://ethereal.xyz"><u>Ethereal Ventures</u></a> as Head of Portfolio. I will specifically be working with founders, and leading platform efforts. I strongly believe in Ethereal's vision and mission and am happy to support the firm as it invests in founders working on cutting-edge technology in blue ocean categories.&nbsp;</p><p>As a former founder, I’m excited to work with companies from a place of empathy whenever possible. At the stage Ethereal invests, founders sometimes require customized support and someone they can trust to get data points from to scale their protocol or business.  </p><p>At Ethereal, I’ll be working across the portfolio with founders, both early and new, and helping scale organizations from first principles. Whether it’s growing and scaling an organization, working on product and go-to-market strategy, or even dealing with deeper problems, having been in their shoes and being able to relate to their experiences in many cases makes it much more meaningful.&nbsp;</p><p>With all this being said, if you’re a founder working on an exciting problem, dealing with a particular conundrum, or even want to talk about the space at large:&nbsp;</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="mailto:rocco@ethereal.xyz"><strong><em>let’s chat.</em></strong></a></p>]]></content:encoded>
            <author>rocco@newsletter.paragraph.com (Rocco)</author>
            <category>web3</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/f2df3b60091daa85d65250b9ba74417c.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Protostructure, Superstructure, Hyperstructure ]]></title>
            <link>https://paragraph.com/@rocco/protostructure-superstructure-hyperstructure</link>
            <guid>29ojZUxNfKaydJgwYMdQ</guid>
            <pubDate>Sun, 19 May 2024 18:30:43 GMT</pubDate>
            <description><![CDATA[As protocols develop toward decentralization, governance typically evolves in three phases over time: a protostructure, a superstructure, and finally...]]></description>
            <content:encoded><![CDATA[<p>As protocols develop toward decentralization, governance typically evolves in three phases over time: a protostructure, a superstructure, and finally, a hyperstructure. Most protocols in this space start with the intention of becoming decentralized and gradually do so over time, moving from a concentrated group of stakeholders to an open community governance process.&nbsp;</p><p>At the start of any protocol, an individual or group creates an open rail for some purpose that will eventually be governed by a commons.&nbsp;This first stage is what I would call a <strong><em>protostructure</em></strong><em>.</em> </p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/33de36c5f2dc31d466c05013faf1abdc.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>A protostructure consists of a protocol in development with an implied direction and the eventual goal of having a group of decentralized stakeholders determine its future direction. The protocol’s intention and usage are strictly defined, and a roadmap of the elements required for launch is set.&nbsp;</p><p>To call a project in a protostructure phase "centralized" as an insult is ridiculous, as it isn’t even mature enough to be scrutinized against a set of criteria to consider it decentralized. In this stage, the team's actions are positive-sum, lifting all boats towards the same goal in a category. It is only competitive on narrative in this stage, but not on intention or outcomes.&nbsp;&nbsp;</p><hr><p>We've entered the <strong><em>superstructure</em></strong> phase once a protocol is launched and teams can use it as a common rail for their projects.&nbsp;</p><p>A superstructure can be defined in several different ways. One standard definition comes from large ships, where the superstructure sits upon the ship’s hull and exists as a lightweight extension above the main deck. The core foundation of the ship remains the hull, but the superstructure houses crew members, additional operations, and more. </p><p>One additional definition of it in a web3 context comes from <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://a16zcrypto.com/posts/article/crypto-glossary/"><u>a16z’s differentiation</u></a> of layer 1s (L1) and layer 2s (L2) that settle to layer 1s. In their view, the L1 is the foundation or hull, while the L2 is the superstructure where participants “live and work”; conducting business and settling down to a foundation.&nbsp;</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.marxists.org/history/erol/periodicals/theoretical-review/tr-12-1.pdf">The Marxist theoretical definition</a> of the superstructure encapsulates all things outside the means and relations of production. In this case, the <em>base</em> holds the means and relations of production (the protocol’s operational foundation), and the superstructure becomes anything related to or influential to production, such as ideology (incentive governance and protocol directional influence).&nbsp;</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/bc31623074612cf69f5339a62c4d78e2.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>This phase begins with a project's launch and tokenization, which becomes a means to govern the protocol.  </p><p>Projects can now build permissionlessly on top of the protocol and use it for critical processes. The protocol's usage introduces new efficiencies or value creation, and creates new modes of operation that weren’t originally possible with other centralized solutions.&nbsp;</p><p>We’ve reached a point where the core team can’t change the protocol on a whim, so it becomes safer to build upon or begin to be involved in steering any changes. Governance moves from centralized to semi-centralized during the superstructure phase. </p><p>In the superstructure phase, the core protocol acts as the base or foundation of the superstructure. On top of that, we now have data coming from the usage of the protocol that will influence its direction. We've also now introduced systems indirectly related to the protocol’s core function, such as creating community engagement programs or encouraging projects to build on the protocol, which are all steered by governance. These incentive programs directly impact the base protocol, as the incentive typically comes in the form of the governing asset.&nbsp;</p><p>Many projects in web3 are currently in this phase with backstops for centralized teams to prevent hostile takeovers and builders being involved in core protocol governance. During this phase, there are still typically checks on ‘total decentralization,’ as an originating team may still have veto power or slight majority control over decisions to prevent attacks.&nbsp;Additionally, issues can quickly be remedied if the protocol halts for any reason or bug. </p><p>Actions taken by actors in this phase are typically mixed, as some might now wish to steer protocol governance to their ends rather than for the common good. </p><hr><p>Finally, after the superstructure phase, we reach the<em> </em><strong><em>hyperstructure</em></strong><em> </em>phase once we've hit a point of total decentralization. </p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://jacob.energy/hyperstructures.html"><u>Originally coined by Zora founder Jacob Horne</u></a>, a hyperstructure is defined by a protocol finally being in a completely permissionless, unstoppable state. The protocol is completely neutral, free from all foundational influence, and creates positive incentives for anyone using it.&nbsp;We’ve reached fully open governance.</p><p>Making changes to the protocol is effectively beyond the control of the original team and is completely based on the whims of asset holders. There is no backstop that anyone can use to halt the protocol, nor is there a body of trusted individuals that can override any decisions. If there is a contentious change to the protocol, participants must fork it and rebuild consensus around their own version of it.&nbsp;</p><p>One example of preventing attacks in a fully decentralized system comes from a recent governance initiative in the ENS ecosystem. To thwart potential governance attacks, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://discuss.ens.domains/t/introducing-veto-ensdao-eth/19088">large delegates of ENS recently coordinated</a> to create a new delegate called <code>veto.ens.eth</code>. This new delegate enables a pool of existing delegates to easily veto proposals collectively (it can only vote <code>no</code>) if there is an attempted governance attack. </p><p>If the protocol breaks, it is up to the decentralized group of stakeholders to fix it. To reach this phase, a protocol needs to be completely battle-tested, as there aren’t any more training wheels preventing things from going awry.&nbsp;</p><p>The protocol must provide as much value as possible to stakeholders building on it, or it will completely fall apart. If it fails to do so, another protocol that may respond quicker to market demands will be able to subsume any meaningful activity completely. </p><p>Every action and decision pertaining to the protocol’s governance must be completely optimized both for the survival of the protocol and its victory against all other competition.&nbsp;In my opinion, this phase turns the protocol into a machine playing a zero-sum game.&nbsp;</p><p><em>If it’s a liquidity protocol, then it must amass all available liquidity.&nbsp;</em></p><p><em>If it's a decentralized name system, then it must be the dominating namespace.</em></p><p><em>If it’s a marketplace, then it must command all transactional activity.&nbsp;</em></p><p><em>If it seeks attention, it must command every last drop.&nbsp;</em></p><p>At this point, the protocol is self-serving and benefits everyone who builds on it.&nbsp;</p>]]></content:encoded>
            <author>rocco@newsletter.paragraph.com (Rocco)</author>
            <category>decentralization</category>
            <category>daos</category>
            <category>governance</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/8d6847d1fb6f7da95a97088ca2e06419.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Quickstarts Are Recipes - Developers Are Bakers ]]></title>
            <link>https://paragraph.com/@rocco/quickstarts-are-recipes-developers-are-bakers</link>
            <guid>Js1S5zpFlqn4QxtFQFTo</guid>
            <pubDate>Wed, 17 Apr 2024 15:19:09 GMT</pubDate>
            <description><![CDATA[Developers typically use quickstarts to familiarize other developers looking at their software for the first time. Quickstarts focus on demonstrating...]]></description>
            <content:encoded><![CDATA[<p>Developers typically use <strong>quickstarts</strong> to familiarize other developers looking at their software for the first time. Quickstarts focus on demonstrating what the software accomplishes and how a developer could use it. </p><p>However, more often than not, developers love to make quickstarts with limited information (leading new developers nowhere) or assume developers have everything set up in a particular way and set them up for failure while they follow along.&nbsp;Let’s break down what 'quickstart' <em>should</em> mean for those following along at home:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/9beaf2e565a54af5a49a7bdb5b36c6cd.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">Just make sure it ends somewhere</figcaption></figure><p>Sometimes, developers make too many assumptions about an audience, such as having an environment installed or deep prerequisite knowledge of a subject. In that case, you might be setting your audience up for failure. </p><p>Quickstarts are in place to get a developer from 0 -&gt; 1 while using your software and show them how it's used in practice. That even could mean scaffolding a few things around it to give a developer a delightful experience.&nbsp;</p><p>When thinking about quickstarts, I like to think about it as a recipe:</p><div class="relative header-and-anchor"><h3 id="h-start-with-a-goal">Start With a Goal</h3></div><p>When building a quickstart, <strong>start with a desired outcome</strong>, like how we search online for recipes. </p><p>When you look online for a chocolate chip cookie recipe and follow it, you want to have a chocolate chip cookie in your hand by the end of it. A good quickstart should have a user go from nothing to a desired, tangible outcome.&nbsp;&nbsp;While building your quickstart, work backwards. For example, if you want a developer to use your authentication library, show them how it can be used in practice with a mock application. Don’t just hand them a library with some vague instructions.&nbsp;</p><p>Set a ‘prep time’ and 'baking time' for your quickstart. If your quickstart is called a “quickstart” but takes two hours to follow, you might be in for some rough feedback. Keep it within a reasonable time for any new developer to have their 0 -&gt; 1 moment. </p><p><em>Make sure that this time is tested with a developer who isn’t familiar with your software.</em><strong> </strong>You might be biasing your results internally due to existing knowledge of your software; quickstarts are meant for fresh eyes.&nbsp;</p><div class="relative header-and-anchor"><h3 id="h-make-limited-assumptions">Make Limited Assumptions</h3></div><p>If someone's baking something, we can assume that they have at least some of the basics in their home: a fridge, an oven, and maybe a countertop—much like a developer might have an IDE and some knowledge about your domain. However, they might not have the specialized knowledge (‘specific brand’ of chocolate chips) you want them to use.&nbsp;</p><p>A good recipe lists <em>all</em> the ingredients and details needed at each step, detailing how each ingredient interacts with something in the kitchen. Good quickstarts list every prerequisite a developer would need and include steps that do not require too many logical jumps. This includes even noting the version of a particular piece of software you’re using in your quickstart (e.g. <em>"Node.js v20.12.2")</em>.&nbsp;</p><figure src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/20babc4b6c51a7d30015499ca128359d.png" float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/20babc4b6c51a7d30015499ca128359d.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>Make no assumptions about a developer's environment—you don’t want them to hit a snag at the beginning of following your guide. This also prevents them from hitting environment issues when breaking software versions come out, and you don’t have the time necessary to update your quickstart every time someone else updates their libraries.&nbsp;</p><p>Each step should help developers conceptualize where certain pieces of code should go, even if the quickstart allows them to copy and paste code directly. If the task is more involved, you should also show them how their directories should be set up. </p><p>Again, get them to where you want them to go, and assume it’s their first time using the software every single time. Your documentation can contain more advanced options and tutorials, but your quickstart is your first impression and hook to give a developer a delightful experience. </p><div class="relative header-and-anchor"><h3 id="h-buying-your-cookbook">Buying Your Cookbook&nbsp;</h3></div><p>Finally, the longer-term goal for any quickstart is to get a developer interested in using your software, much like a recipe is to buying a cookbook or following a specific baker. &nbsp;You want them to go beyond the quickstart and use your software in their applications. </p><p>Don't let your quickstart go stale, and routinely ensure that it is working and still providing the same experience—even as your software changes. </p><p style="text-align: justify"><em>Please don't leave them with a bad taste in their mouth. <br></em></p>]]></content:encoded>
            <author>rocco@newsletter.paragraph.com (Rocco)</author>
            <category>product</category>
            <category>developer</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/d15924e3f58cea444536eeb77866cb87.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Economies of Control]]></title>
            <link>https://paragraph.com/@rocco/economies-of-control</link>
            <guid>wgwFSfnIDIsgIL1JlkQY</guid>
            <pubDate>Wed, 03 Apr 2024 12:49:54 GMT</pubDate>
            <description><![CDATA[Building a great economy is more important than focusing on building an open economy.]]></description>
            <content:encoded><![CDATA[<p>Frequently, I hear stories about open marketplaces, worlds, and games that paint a picture of a consumer who feels ‘locked in’ and unable to break free of a particular economy. In these stories, you will hear about users wanting to trade items outside of in-game marketplaces, buying and selling their in-game currency, or even using their loyalty points in different contexts. I think this comes from a consumer’s frustration with a product instead of an actual grievance over something additive - <em>but that’s beside the point.&nbsp;</em></p><p>First, I’m a fan of the idea of in-game and in-app economies being a bit more flexible and offering more consumer choice. For example, could an app take another platform’s points and incentives and provide more in return for migrating? Or let’s say a user earns something in a game: why should they be limited in what they can do with that asset?&nbsp; I think it’s entirely possible in new and <em>emerging</em> markets to take a cross-platform approach in the name of taking on incumbents. </p><p>The operative word here is “emerging” because I don’t see it happening for established games, marketplaces, and loyalty programs.<em> </em>To paint it as a problem and as users' one true grievance seems disingenuous. It is more likely that a lousy platform is the primary concern rather than a marketplace not being ‘open’ enough.&nbsp;</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/e78f80f7a81ff6b16c7a39c7af08ba75.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">Perceived solutions are way more fun.</figcaption></figure><p><strong>Cross-platform incentives for users in established markets are tricky for various reasons, but mainly because organizations wish to be the gravity well that moves their economy.</strong> </p><p>If you establish an economy that benefits users somehow, you want to sit at the center of it and not have unexpected forces dethrone any defined exchange rates, encounter third parties that may threaten market safety, or have issues with congestion. It’s the same reason why airline loyalty programs introduce points partners in different verticals (that they define) or game developers keep tight controls over their marketplaces.</p><p>Healthy established markets are fully incentivized to avoid participants gaming the system <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.youtube.com/watch?v=xSHyDW6J_qY"><u>as it leads to their eventual unraveling</u></a>. In this case, both sides of a transaction are interacting on asymmetric information influenced by outside rates and dark markets. To keep market health going, established markets will want to control everything from how both sides enter the market to how they interact. This is all reinforced by the two most common responses to open market activity: active economic controls and reactive economic controls. </p><div class="relative header-and-anchor"><h2 id="h-active-controls">Active Controls</h2></div><p>Active controls fall under well-established economies that seek to maintain market health in the face of any adverse events. An example of this would be an airline loyalty program that determines everything from unit economics, to redemption partners, to curating earning activities. Airline loyalty programs shape travel decisions and act as a way to keep customers interested in brand – <em>but there are a few active controls in place to reinforce a few systems.</em>&nbsp;&nbsp;</p><p>Let’s start with the unit economics of airline loyalty programs. These are tightly controlled in terms of what they’re “worth” first and foremost to <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.oliverwyman.com/content/dam/oliver-wyman/global/en/files/archive/2006/MMJ22_New_Economics_Loyalty_Programs.pdf"><u>manage capacity across flights</u></a>. For example, if an airline is managing capacity across several routes and there are seats to fill, the ‘value’ of the points will be bent to encourage that particular flight as a redemption option. This impacts the vacation habits of users, but at the same time, it’s a constant way for airlines to ‘increase’ the value of the points by using them to discount the cost of capacity they may not sell.&nbsp;&nbsp;</p><p>Additionally, airline loyalty programs make a lot of money through partnership programs where partners effectively ‘buy’ points to reward their customers. This happens often with credit card providers that allow you to use your miles to offset your bills or redeem them for credit through their program. However, it’s the airline controlling the exchange rate here with an agreement with a partner, and they can also be highly selective about who they allow in these partner programs (<em>on purpose).</em></p><p></p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/8a43f35e95efae0d6258de43948227d8.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">Tight control without outside influence.</figcaption></figure><p>Airlines keep extremely active controls on their partners so as not to allow competition to poison their tightly controlled economies. Airlines will ensure they partner with organizations that are either complementary or not within the same industry (for example, food partners) but never another airline. That’s why there’s no option for consumers to directly exchange one airline’s points for another—it would intrinsically tie an exchange rate between the two and be an outside force that would sabotage already existing economic controls.&nbsp;</p><p>Finally, curated earning from the airline activities influence the float of points. Airlines will typically make all purchases eligible for earning points, but just enough so that it would take plenty of time and increased loyalty to hit a redemption moment. This enables plenty of airline points to float without being burned, and if airlines ever need to tip the scales, they can lower the price of redemption options on a whim.&nbsp;</p><p>Airlines will tip the scales as they sit fit for their ends, and continue to keep incentives in their court. They will continue to control their economy actively, as it impacts a massive chunk of their bottom line. These are all <em>active controls</em>, but sometimes organizations must be <em>reactive </em>when something unexpected impacts their marketplace economics.</p><div class="relative header-and-anchor"><h2 id="h-reactive-controls">Reactive Controls</h2></div><p>Reactive economic controls deal with tightening an existing market that has spilled over into the real world outside of the auspices of an original creator. A great example of this is illegal gold markets in Runescape, a popular MMORPG. In these cases, people would typically buy gold in these markets, which usually consisted of individuals in South American countries <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.polygon.com/features/2020/5/27/21265613/runescape-is-helping-venezuelans-survive"><u>such as Venezuela</u></a> making a living through the game.</p><p>Jagex found that 40-50% of their player base at a given time was buying gold and items in this way, and it was so influential at a certain point that when Venezuela went through power outages in 2019 it caused a small in-game economic crisis. All of the items being botted by these sellers were going through massive price increases due to a lack of activity on the supply side. To this day, Jagex hasn’t entirely curbed some of the botting problems to keep the in-game economy stable, but they have figured out a solution to users buying and selling gold.&nbsp;</p><p>Runescape has always dealt with real-world trading (RWT) with bans and has buffed its <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.pcgamer.com/the-wealthiest-player-in-old-school-runescape-with-more-than-1-trillion-yes-trillion-gold-has-been-banned/">anti-cheating capabilities</a> over the years to better track and trace it. With the sheer volume of bots and gold sellers, Jagex continued to try to be reactive toward this moving target, with one move consisting of a way to fix the price of gold in-game and be the largest legal dealer. </p><p>Before mentioning this, it’s important to note why an organization like Jagex would be employing these reactive controls. It’s primarily to avoid a pay-to-win problem in-game and to cut any price-gouging activity.&nbsp;<em>But really, Jagex wanted a piece of the action, as would any game creator.</em></p><p>Their approach to curb gold trading came from <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://oldschool.runescape.wiki/w/Old_school_bond"><u>membership bonds in 2015</u></a>. Membership bonds were an in-game item purchaseable by Jagex that allowed the holder to redeem the item for a fixed amount of days of member’s content (their paid version of the game). Bonds were attractive from a few different angles:&nbsp;</p><ul><li><p>Bonds acted as a deflationary mechanism, as gold was required to make a bond tradable, and that gold never was reintroduced into the game. </p></li><li><p>A fixed price point for gold was established through a legal channel, as whatever bonds were being traded for in-game could now be fixed to Jagex’s pricing. Instead of going through an unregulated and trust-based model, you could buy the assets directly through Jagex.&nbsp;</p></li><li><p>Jagex could now begin selling memberships almost as bearer instruments, directly to users to redeem them in the game as they wish at a significant markup. Their monthly membership price was cheaper than bonds. </p></li><li><p>It also now enabled players to ‘pay’ for membership through their work in the game, opening up membership for users in places that may not have had the opportunity to purchase it for real-world currency. </p></li></ul><p>But again, Jagex is now an authority on the exchange rate of gold to real-world currency because it introduced this. Although some markets may try to undercut them, there’s an inherent risk to using them instead of Jagex.&nbsp;<em>Jagex knew they couldn’t control outside markets - but were incentivized to do as much as possible to capitalize on the existing economic activity.&nbsp;</em></p><hr><p>All this to say - existing game and marketplace economies love their controls. </p><p>Your new marketplace or game would benefit from an open economy in the face of incumbents, <em>but focus first on creating something worth using</em>. You're going to face an uphill battle from existing large marketplaces and games that aren't looking for open economies, and that's a tough enough challenge in and of itself. </p>]]></content:encoded>
            <author>rocco@newsletter.paragraph.com (Rocco)</author>
            <category>economics</category>
            <category>startups</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/e81012fd031a9babb287c022d7e5b489.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Product-Led Blockchain Development]]></title>
            <link>https://paragraph.com/@rocco/product-led-blockchain-development</link>
            <guid>o9WSO3wGUukIwbPHd19o</guid>
            <pubDate>Thu, 21 Mar 2024 00:00:00 GMT</pubDate>
            <description><![CDATA[We’re in an age of infrastructural abundance, and an age of no excuses. Product-led growth has evolved into product-led protocol development, which has finally led to product-led blockchain development.]]></description>
            <content:encoded><![CDATA[<p>We still have a problem in the Web3 space around genuine consumer usage outside of speculation. Founders continue to build infrastructure and are losing sight of the most essential component of bootstrapping a successful protocol. We’re continuing the same pattern of building beautiful ghost cities, and the one thing most architects assume is that there’s some sufficient demand waiting at the gates (as they claim in their position papers and problem statements).&nbsp;</p><p>Quite often, founders attempt to justify building protocols instead of applications and clients by making excuses across several areas. You may hear tales about key management, costs, and scalability - when, in reality, these are mostly solved through embedded wallets, L2s, and progressively scaling trust assumptions.&nbsp;Related to this, the one philosophical tradeoff point founders will sometimes make is about <em>decentralization</em>, which is also the most flimsy argument available to them. </p><p>In most cases, decentralization is a moot point used in place of justifying systems that don’t need extreme trust guarantees about control. But if a new protocol drops and nobody wants to use it, does it make a sound?</p><blockquote><p><em>"Extraordinary; we can build the perfect system for decentralized food delivery that is protected from nation-state attacks." ~ Nobody</em></p></blockquote><h2 style="position: relative;" id="h-product-led-growth">Product-Led Growth</h2><p>When considering how to drive adoption, let's step back and start with core principles. Robust clients and products should be the core centerpiece—as they always have been when using a product-led growth framework. Product-led growth is a way of operating in which product usage dictates the direction of engineering, design, marketing, and more.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/aca324c0abba416dc468b43622faab5d.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>Every point of feedback that determines direction, resourcing, and messaging should come through a customer's experience using a product. There isn’t any philosophizing about what a user <em>might</em> like because all feedback exists as a directed beam to influence business direction. This evolved with web3, as there was more emphasis on building decentralized technologies and open protocols to usher in a new way of operating. </p><p>However, many teams lost sight of providing an experience for users and thought their technology alone could change the world. Sometimes, it isn’t about how great or complex a technology is, but how easily it can be harnessed and the downstream experience for a user. </p><p><em>Every ‘field of dreams’ looks great on paper, but here’s a shovel - start digging.</em></p><h2 style="position: relative;" id="h-product-led-protocol-development">Product-Led Protocol Development</h2><p><em>Your protocol is not a product.&nbsp;</em></p><p>In the web3 space, we inch closer to a new model with Dan Romero’s concept of <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://danromero.org/product-led-protocols.html"><u>Product-Led Protocol Development</u></a>. Too often, developers build protocols for the sake of building protocols, and think that users and other developers will flock to them and make them successful. It’s essential to think about driving the first usage of your protocol rather than just building the protocol itself.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/8120e814eecdd51e8be0582adc69dfb0.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">[Everyone disliked that.]</figcaption></figure><p>In this short post, he implores developers embarking on some unreasonably large protocol or network-building quest to make sure they’re aware of three things:</p><ul><li><p>A protocol is only as good as the number of clients and businesses using it.</p></li><li><p>Developers worth their salt care about their quality DAUs rather than a tech stack.</p></li><li><p>Users use apps, not protocols – so focus on building the cornerstone app.</p></li></ul><p>Before even thinking about a <em>new frontier,</em> we must ensure we’re building the first road there. You should be building both the protocol and the first client that leverages that protocol. What users want to see in a client should influence a protocol’s development, returning us to the original concept of product-led growth. In this case, the protocol properly becomes more abstracted away while enabling all its benefits to end-users through the client.&nbsp;Satisfied users start to increase your chances of success by influencing your client development, and any necessary changes to the protocol itself that other developers can benefit from.</p><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/e557f244f96d5c90efb0a46c5243fcc7.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAOCAIAAADBvonlAAAACXBIWXMAAAsTAAALEwEAmpwYAAAC1klEQVR4nIWUMUzbQBSGs2TMlCFSu2RxJRZYWdIhA168wMBkCYREJhYvuckVuIOpGlOpQSKuKlwpFlKNlJwQOaoSpOIBLFGODodUrssN5YaCu3i6Dr2KnBpVKKH/ZFnv3vfuf+9dTggxMTFh27ZpmpVKxXEcKaUQQj4oIQQAwPd9hJDnec1mc1xkznVdwzCKxaKmabqua5rW7/cfzi6l5Jzn8/lyuTw9PV0sFiuVylhAlmVSSsaYqiLLstnZ2S8XF5zzo6Oj79fXwwsxxjrdLiEkCIKVlRXOOcaYUpokCSFEpWOMnZyecs6Hp3Ijq0uSJAgCQi43NzfTNFXRYbjDGPt4eAghHFlsmqa+/wbji62Wr+oeDVCMMNwh5NJxnhNCOL8+Oz972Wjs9xDG+NPx8e3tTRiGURQFQQAhBABYlpWmP8Nwh9Jvq2trn8/PGWOc89EAIcTC4uLC4mK9DlzXzefzmqZVKk9t+9nc3BznPI5jwzAsy3Icx7IsXdeVw8u1Wr0OpqamyuVyqVSqVqujAYyx1bW1DwcHMzMz1WrVdV3TNDXtSRiGzWYToQMpJaUUY6z87Pf7WZYxxgAACKFHjx+XSiXLshBCowEQ7n29upJSRtEuIZfKtE63q9j7PRTHse/fGU0pTdOUMSbl7063O/iQnW5X9XlsD+I43u/1KKVbrdaPmxvVwHa7jTGOot0kSXzfn5yctG3bsizTNA3DeBcEJ6enCCF1ajhIowFSyobnbbX8jY1Xw4HDGC8tLTc8T0qpGBDCKIo8z3NdN4oiKeX6+ou329uvm5vDPGMBCB1AuBeGO0MAIaTdbkO4N24ulLdRtPt+ABPi1wiAigMAzM/Pq5Y2BwqCwPd99cfzPGcg27ZX/qpWqxUKBbVx/740Y/dAtUsMlGWZyg4AgBAidLcNEEJK6TBGCKFW8p7GWnTvWrqu5wYqFAqGYZimmcvdvWP/fRn/AOy+IvUT+1MTAAAAAElFTkSuQmCC" nextheight="404" nextwidth="896" class="image-node embed"><p>This model also sets an initial blueprint for how developers should leverage your protocol, because you’re making the most beneficial aspects of it abundantly clear through your product offering. </p><p>All the points you draft about how great your protocol is should be present in the client you build. You must demonstrate that value instead of expecting others to do it. However, that isn’t to say you shouldn’t <em>start</em> with a new protocol; ensure the first client or tool to leverage the protocol is the centerpiece of your offering to the world.&nbsp;</p><p>One last point to make in the case of web3 apps is that you must ensure you have your <em>table stakes</em> handled before trying to appeal to mass markets. Mimicking what exists on the market in the same category you're building in gets you to square one. Differentiation should come <em>after</em> meeting the market where it is. For example, a social networking application should at least allow users to create profiles, create content, and easily share content. If your app doesn’t even have that (in the name of ‘decentralization’ or some other excuse), it’s time to rethink your strategy.</p><h2 style="position: relative;" id="h-product-led-blockchain-development">Product-Led Blockchain Development</h2><p>Finally, I think we’ve moved beyond product-led protocol development and into what I’m calling product-led blockchain development. This is coming as more teams spin up new application-specific rollups and L2s. In this model, you’re not just building the first product or client to leverage your own protocol, but also your own blockspace and ‘product-defined blockspace’.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/0493457f798cdf759e605ea1e4c832c2.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">"Why can't I hold all this blockspace"</figcaption></figure><p>You need to show and demonstrate why you created an entirely new blockchain, and there’s no better way of doing that than demonstrating your wedge or unique advantage. Being ‘faster,’ ‘cheaper,’ or ‘more scalable’ doesn’t mean anything anymore when we’ve made creating new blockchains as easy as one-click deployment.&nbsp;</p><p>Your network effects don’t stop at someone leveraging a new open protocol. Now, developers influence the success of your new blockchain by leveraging the blockspace for the benefits it provides in the context that you’ve defined. You’re now on the hook for a hell of a lot more than just an open protocol and an application—you're on the hook for the engine that underpins it.</p><p>You’re now responsible for implementing nodes and clients, some of the first core fundamental protocols, and that novel application that justifies that new blockchain. If you’re willing to go on this mission, you better be ready to handle all of this.</p><hr><p>Be the blockspace you wish to be in the world - but remember to build something useful.</p>]]></content:encoded>
            <author>rocco@newsletter.paragraph.com (Rocco)</author>
            <category>blockchain</category>
            <category>product</category>
            <category>web3</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/70be0508d751879bda1ba194cae2db83.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Product Builders Are Screenwriters]]></title>
            <link>https://paragraph.com/@rocco/product-builders-are-screenwriters</link>
            <guid>hRqADjXkhVyTQf0azf1Y</guid>
            <pubDate>Mon, 11 Mar 2024 00:00:00 GMT</pubDate>
            <description><![CDATA[As you embark on your product journey, it’s also important to remember that you’re supposed to be creating an experience that both provides value and is compelling.]]></description>
            <content:encoded><![CDATA[<p>As you embark on your product journey, it’s important to remember that you’re supposed to create an experience that provides value and captivates an audience. Your product, in essence, is a show.</p><p>You’re building a product, but you’re also a screenwriter.<strong> </strong>You are directing the action from a user landing on a page to their first experiences taken on your product. You are scripting the entire process and designing it around a desired outcome. Every small iteration you make serves that outcome; if those outcomes aren't clear, you have a more significant problem. When a user leverages your product <em>differently</em> than expected, you learn from the critics, adjust your script, and ship the next part of the series.</p><p>One concept from screenwriting that should also be applied to building products is the “<strong>But and Therefore</strong>” rule.&nbsp;</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/04033825f599f7a93bb1c00dc678c6d4.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>Essentially, the rule revolves around replacing the words “and then” any time they're found in your script with “but” and “therefore” to build tension and eventually reach a logical conclusion. This tension refers to providing the reason why actions are being taken in the first place. Using “and then” creates a dull structure based solely on the writer’s desire to list actions they’re excited about. However, to a reader, it’s dreadful because it feels like you’re just being thrown around a story in which you have zero vested interest.&nbsp;</p><p>Let’s break it down a little bit and give a traditional example in the context of a quick script:</p><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/66fa04cce537bf58318201e4a79e960a.png" blurdataurl="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAALCAIAAACRcxhWAAAACXBIWXMAAAsTAAALEwEAmpwYAAAChklEQVR4nG2TMUzbQBSGT52rdGJiKGLJUGAgDKWuVCbkARxVNBtSEQV1oENihiQdcIIUywjZBCmRGWK5A1EYynk7BpRjczarQzk63QK50au3viq+tkIh/+Q7/fe+e+9+IwBw3bPzbtd1Xc45TBLG2HZOrOPjh+FQLnu9C9txGGNPzWEYNkyzYZqyGmKM2c7J/cN9saTbjgMAyT/JA0mSHBjGr7u775eX5UoVAD4UCkEQDAaDMb880jDNKPoxGAwODGMEiOO443n5fB4hROnNxA5c96xhmgihVrsNAMtvFISetdptQshEc7N5+jzzoljSRwAAKJZKGGOjVvN9Xwjx8/YWp6KUxnEMAJZ1ZNRq5Uq143lJkrTa7fNuV9f3KaUA0Evl+75c+r5fLJXeb2w0m6dxHCPO+au5OQAghLxbWQEAXdfn5+ezqSCdwMuZGQCglCrKW855Pp8HgAPD2NnZBQBFUTRNy2QylmUBwGIuF8cxY2xhYYExhoQQr5eXASCKoo7nyYqPW6aUrq6uAkAcx7bjCCFmZ2fTtiwJeOx/GA4Xczm5YztOkiQjQLX69brftx3nvNt9CoiiyLKOCLmSyZEjJeSq43muezYWCs65ru8nSSKEKFeqI0A6tW9r61qxpI+V/i/bcer1w729L0KItKebtXVtd/ezfKEx9XoX29ufPm5tyRCPAEEQNEyzXj+cWB0Arvv9VrstbySTbtRqaQp/PzXL+JYrlb//ASGEc84YE6kmAjjnQRAwxsIwZIxRSjHGE69PKY2iCGPc8bwwDIUQaHNzU9M0hNDS0pKqqhMBhBBVVaenpxFCqqpms1mEEMb48YPJD13XC4UCQkjTtKmpKUVR/gBhTxWzvXYTxgAAAABJRU5ErkJggg==" nextheight="300" nextwidth="850" class="image-node embed"><p>Here, we have a character, Jim, waking up, speaking to a character named Bob, and going home – all without any reason linking the events. It’s dull, and although it may seem like an obvious pitfall to avoid when writing, it’s pretty straightforward a trap to fall into. </p><p>This same style also applies to building products. It's very easy (actually quite fun) to list a set of user actions without anything stringing them together. You want your users to take actions on a product or platform—that's a given, but what <em>leads</em> them to those actions is the most crucial part. The difficulty comes from figuring out the user flow and actions that are compelling enough to lead them toward that desired outcome. </p><p>Let’s apply the “and then” framing to an MVP of a social product that optimizes for user interactions:&nbsp;</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/fbd43dc26b654f3e9d43a3d5aeb73151.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">One after another</figcaption></figure><p>As you can see, we have a set of desired actions but nothing as the catalyst to move the user across any of them. We want users to log in, update their profile, post, and check the news, but it’s disjointed and feels like a wishlist. Instead, it should feel like actions are continually supported and reinforced by other actions, and using the product becomes an engaging activity. </p><p>Now, let’s take it a step further and convert our "and then" scenarios to a “but and therefore” framing. Our original script with Jim looks a bit different because we now know the causes and events that took place which drive the story:</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/a763acbf394a7bade5fe6934cbac69d9.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>As you can see, the missing context drove the entire plot to begin with, much like contextual guidance is required to drive a user’s first interactions forward. If you start to design a product with an “and then” mentality, you won’t be <em>driving</em> users to where they need to be on your product, and you won’t understand what kind of interactions you need to enforce to make things sticky. </p><p>It would be best to optimize for outcomes <strong>and the hooks that lead to those outcomes.</strong> Let's take our original "and then" MVP app example and apply this new framework to it: </p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/162fe389399bcb41f89f08e3f24a6887.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>Now, we have drivers throughout the user journey that lead us to our following action. There is now a clearer reason for a user to edit a profile or engage with content. An “and then” mindset prioritizes scattered features over a cohesive experience. Start replacing every “and then” with “but” and “therefore" in your product journey. &nbsp;&nbsp;&nbsp;</p><hr><p><em>If a product is a show, your MVP is the pilot pitch.</em></p>]]></content:encoded>
            <author>rocco@newsletter.paragraph.com (Rocco)</author>
            <category>product</category>
            <category>startups</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/cc8f7bca4ee0d565b551fe35fc338a14.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Lessons From a Recovering Founder]]></title>
            <link>https://paragraph.com/@rocco/lessons-from-a-recovering-founder</link>
            <guid>B0NIXDe5Z81g7VDJBTh2</guid>
            <pubDate>Wed, 06 Mar 2024 00:00:00 GMT</pubDate>
            <description><![CDATA[Your battles inspired me - not the obvious material battles but those that were fought and won behind your forehead.” ~ James Joyce]]></description>
            <content:encoded><![CDATA[<blockquote><p><em>“Your battles inspired me - not the obvious material battles but those that were fought and won behind your forehead.” ~ James Joyce</em></p></blockquote><hr><p>I recently left my startup <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://medium.com/@Obstropolos/green-leaves-3c56a8f8f91"><u>in the capable hands of my cofounder</u></a>. Being a founder has been one of the most exhilarating rollercoasters I’ve been on, and I’m incredibly proud of everything that my startup, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://spruceid.com"><u>SpruceID</u></a>, has achieved to date. There are a few pieces of advice I think are pretty important to share with anyone else beginning the same journey.&nbsp;</p><h3>Your First Job Is Having an Idea and Conviction</h3><p>It’s an easy exercise to think about market opportunities across an infinite amount of verticals - even down to something extremely mundane but important like <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.rinsed.com/"><u>modernizing the carwashing industry</u></a>; or entirely ambitious like <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://thebrowser.company/"><u>reinventing the modern web browser</u></a> from the ground up.&nbsp;</p><p>Your job is to narrow that primordial soup of concepts and hypothetical scenarios into something that can make enough impact to build a sustainable business. Y Combinator has a great motto: “make something people want,” <em>because it can’t just be about what </em><strong><em>you</em></strong><em> want.&nbsp;&nbsp;</em></p><p>Quite often, building what you want as a founder creates a great trap. You may think you have a great idea for a product or business and are solving some great problem, but if you cannot validate that idea outside your personal bubble, you’re in for a rough time.</p><figure float="none" width="335px" data-type="figure" class="img-center" style="max-width: 335px;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/619b5a86e146a75b9a629957741cceef.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">Delusions of Grandeur </figcaption></figure><p>You can’t just have an idea - you need to validate it. Either you’re already an expert in the area you’re considering going into because you’ve personally faced this problem and know others do, or you’re preparing for a boatload of customer development. Remember: useful for <em>you</em> doesn’t necessarily mean it’s useful<em> for anyone else</em>.&nbsp;</p><p>Also, <strong>don’t bias the people you’re talking to</strong> – they rarely tell the truth when this happens. If you tell a friend or family member about your great vision, they’ll likely tell you “that’s great” to support you, or not hurt your feelings if they think it’s an awful idea. If you ask more about problems they encounter when doing something related to your idea (without specifically pushing a solution), you will likely get closer to the truth.&nbsp;</p><p>When you’re confident this problem is confirmed, your next goal is to tackle the most potent individual issue identified. This typically comes as an MVP that looks terrible but provides immediate value. After you do this, it’s just continual iteration.</p><p>It’s pretty fun to apply your solution to everything under the sun while neglecting an initial problem or market that needs it. As easy as it may be, don’t get caught up in this – you will burn yourself out quite quickly.&nbsp;</p><h3>Your Second Job Is to Articulate Your Mission and Inspire People</h3><p>Great – you’ve identified a problem, have a way of solving it, and have enough people interested in your MVP.&nbsp;</p><p><br>One of a founder's many jobs is articulating this vision and mission to a broader audience outside of your immediate circles. Specifically, I like to reference <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://www.youtube.com/watch?v=eRkgK4jfi6M"><u>Wired’s series</u></a> of explaining what may seem like a simple concept across five difficulty levels as an exercise to employ.</p><figure float="none" width="389px" data-type="figure" class="img-center" style="max-width: 389px;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/a0860d7059f0cdf67aee51a83704d1e7.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="">An example of what <strong>not</strong> to do</figcaption></figure><p>Externally, you must break it down in the simplest form possible, preferably within a phrase or sentence. One way of doing this could be using an existing company as a frame of reference in a comparison (e.g. a hypothetical service that offers transportation for your pet to daycare “It’s like Uber for Dogs”).&nbsp;</p><p>After breaking it down, you must convince an initial group of builders to believe in what you’re doing to bring your vision to life. This becomes your founding team who have to be ride-or-die throughout the process. The core adage to think about here is “hire missionaries, not mercenaries,” about the types of people you should work with.</p><p>You want people just as excited about what you’re doing in the early days, especially given the trials and tribulations you might go through to bring your wacky idea to life. However, the most critical next step is what you do <em>after </em>hiring, which is making sure to lead with not just clarity and direction, but <em>empathy</em> as well. You’ve brought some people onto this crazy ride, and you must be the ever-leading optimist at an organization.&nbsp;&nbsp;</p><p>This optimism can’t be blind – it has to be balanced with organizational transparency, integrity, and the ability to listen to the team you’re leading.</p><h3>Your Third Job Is to Take Action and Accountability</h3><p>There are two types of decisions that you’re trusted to make as a founder: measured actions or gut reactions.</p><figure float="none" width="679px" data-type="figure" class="img-center" style="max-width: 679px;"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/af6f8e2c5654cfc9d761705643dbb8bf.png" class="image-node embed"><figcaption htmlattributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>It’s easy to take your time for measured actions. These are your day to week to month decisions that impact the organization at large, and span everything from hiring, to product, to marketing. These actions typically fall under some internally defined process where you set up measurable objectives and milestones, and start to formulate and take action on how to achieve them.</p><p>The easiest way to gain internal trust on these types of decisions is through consistency. The more predictable these happen from a founder, the more comfortable a team is in supporting these actions and helping you see them to fruition. However, you don’t always have the time to take a measured action. The universe doesn’t often give you the luxury of taking your time, measuring every possible outcome, and taking action based on a plan you may have made.</p><p>Gut reactions are acceptable in a few scenarios based on a founder’s foresight. It’s important that a team trust that founder to align on scenarios where a gut reaction is warranted. Typically, gut reactions are necessary when it comes to decisions that have a very short window of response, such as security issues, crisis PR, and a time-sensitive market development. However, <em>by this point, you should have a history of consistency with measured actions </em>so your team trusts your intuition in these scenarios.&nbsp;</p><p>Just know that you are responsible for the outcomes stemming from these actions. It’s not a team effort unless your team is making decisions on behalf of the company. If it’s a delivery failure, that’s one thing and still involves founder accountability – but if it’s a vision or directional failure, that’s mostly on you, not your team.</p><h3><strong>Finally, Your Last Job Is to Survive</strong></h3><p>Everyone talks about the success of startups and less so about their survival when times <em>aren’t</em> great. The clock is ticking with every decision made, and with each moment that passes, there’s less capital to work with. You will be making some of the hardest decisions of your life while you operate a business, and it will include managing your burn rate.&nbsp;</p><p>There will be times when your product doesn’t take off, there aren’t favorable conditions in the market, or you have a year left of runway and need to turn that into two years. It will require making tough decisions, whether cutting certain parts of your product or your team.&nbsp;</p><p>Timing is one of the major killers of startups. If your idea is too early to take off in a significant way and see success in the market, you might need to withstand the storm until then. You might need to change your immediate product direction to serve the market while preparing your greater vision for when the time comes. Your goal is to make it until that time comes by cutting any corner you can and <em>keeping the same conviction mentioned earlier</em>.&nbsp;</p><hr><p>If there’s one thing to remember throughout all of this - <em>remember that you’re not alone.&nbsp;</em></p>]]></content:encoded>
            <author>rocco@newsletter.paragraph.com (Rocco)</author>
            <category>startups</category>
            <enclosure url="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/5c542eed4a2f61676edb1bf6a9163f8f.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>