<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[The Community Code]]></title><description><![CDATA[Exploring how community intersects with product, marketing, sales, and customer success, and what changes when community is integrated with GTM.]]></description><link>https://www.thecommunitycode.com</link><image><url>https://substackcdn.com/image/fetch/$s_!WfpE!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde0a1e70-e4e0-4342-ad75-4b6972a28c40_256x256.png</url><title>The Community Code</title><link>https://www.thecommunitycode.com</link></image><generator>Substack</generator><lastBuildDate>Sun, 22 Nov 2026 20:09:51 GMT</lastBuildDate><atom:link href="https://www.thecommunitycode.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Joshua Zerkel]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[thecommunitycode@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[thecommunitycode@substack.com]]></itunes:email><itunes:name><![CDATA[Joshua Zerkel]]></itunes:name></itunes:owner><itunes:author><![CDATA[Joshua Zerkel]]></itunes:author><googleplay:owner><![CDATA[thecommunitycode@substack.com]]></googleplay:owner><googleplay:email><![CDATA[thecommunitycode@substack.com]]></googleplay:email><googleplay:author><![CDATA[Joshua Zerkel]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Community Program Portfolio Audit: What to Keep or Stop]]></title><description><![CDATA[A scored audit across six dimensions for deciding which community programs to keep, improve, scale, consolidate, pause or stop.]]></description><link>https://www.thecommunitycode.com/p/community-program-portfolio-audit</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/community-program-portfolio-audit</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 17 Nov 2026 16:30:45 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!VTOn!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!VTOn!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!VTOn!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!VTOn!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!VTOn!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!VTOn!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!VTOn!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png" width="350" height="350" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/d2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:350,&quot;bytes&quot;:75580,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/223050401?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!VTOn!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!VTOn!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!VTOn!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!VTOn!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fd2abf4ed-12bc-497f-9021-1f4de89bc86b_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Ask a community team to list every program they run, and the list is usually longer than anyone expected, including the team (I&#8217;ve watched people get to the end of theirs and look a little surprised). An event series, an ambassador program, office hours, local groups, a webinar series, an advisory board and a forum can all be running at once, each one started for a good reason and few of them ever looked at together.</p><p>I wrote about why those programs pile up, and why stopping one is so hard, in <a href="https://www.thecommunitycode.com/p/why-community-programs-are-so-hard-to-stop">Why Community Programs Are So Hard to Stop</a>, so I won&#8217;t make that case again here. This is the working version: an audit for looking at your programs as one portfolio and deciding what to do with each of them.</p><h3>What this is for</h3><p>The audit helps you check whether your current set of programs is coherent, useful, sustainable and still connected to what members and the business need. It works at two levels. You score the portfolio as a whole across six dimensions, and then you use the same evidence to make a call on each individual program.</p><p>It&#8217;s built for teams that already have programs running. If you&#8217;re still deciding whether to build a community at all, the <a href="https://www.thecommunitycode.com/p/community-readiness-assessment">Community Readiness Assessment</a> is the better place to start.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3>How to use it</h3><p>Score each dimension from 1 to 4 based on what&#8217;s true today.</p><ol><li><p>Fragmented or inherited.</p></li><li><p>Partially intentional.</p></li><li><p>Coherent and actively managed.</p></li><li><p>Portfolio decisions are evidence-backed and resource-aware.</p></li></ol><p>Bring real evidence to the conversation: program plans, member research, participation data, business outcomes, the staffing each program actually takes, and any recent examples of a program being changed or stopped. If a dimension is hard to score because the evidence doesn&#8217;t exist, that&#8217;s useful to know too.</p><h3>The audit</h3><h4>Strategic fit</h4><p>Do programs map to clear member needs and business priorities?</p><ol><li><p>Many programs exist because they&#8217;ve always existed or because someone requested them.</p></li><li><p>Most programs have goals, but portfolio-level priorities are unclear.</p></li><li><p>Major programs map to defined needs, use cases and outcomes.</p></li><li><p>Strategic fit is reviewed regularly, and weak-fit programs lose priority or stop.</p></li></ol><h4>Portfolio coverage</h4><p>Does the set of programs cover the important needs without unnecessary duplication?</p><ol><li><p>Programs cluster around similar activities while important needs go unsupported.</p></li><li><p>Gaps and overlaps are visible but not actively managed.</p></li><li><p>Programs have distinct jobs, and important member needs are reasonably covered.</p></li><li><p>The portfolio is intentionally balanced across lifecycle stages, segments and use cases where those distinctions matter.</p></li></ol><h4>Member value</h4><p>Do programs create enough value that members would reasonably choose to participate?</p><ol><li><p>Participation relies heavily on promotion, incentives or company asks.</p></li><li><p>Member value exists but is inconsistent or generic.</p></li><li><p>Major programs solve specific member needs or create valued relationships and access.</p></li><li><p>Member value is validated through repeat behavior, research or contribution without a lot of prompting.</p></li></ol><h4>Business value</h4><p>Can the team explain what each major program contributes to the business?</p><ol><li><p>Business value is mostly inferred from participation volume.</p></li><li><p>Programs have intended outcomes but weak logic connecting behavior to outcomes.</p></li><li><p>Major programs have plausible, measurable ways of influencing outcomes.</p></li><li><p>Program impact informs portfolio and investment decisions.</p></li></ol><h4>Operational load</h4><p>Is the portfolio realistic for the team&#8217;s capacity?</p><ol><li><p>The team is maintaining too many programs, reactively.</p></li><li><p>Capacity problems are known, but prioritization is weak.</p></li><li><p>Resources broadly match program commitments.</p></li><li><p>Operating effort, complexity and what else the team could be doing are explicit inputs to portfolio decisions.</p></li></ol><h4>Program evolution</h4><p>Can programs change or end?</p><ol><li><p>Once launched, programs are effectively permanent.</p></li><li><p>Programs change when something visibly fails.</p></li><li><p>Programs are reviewed against current needs and performance.</p></li><li><p>The team has an accepted practice for scaling, redesigning, consolidating, pausing or stopping programs.</p></li></ol><h3>Read your results</h3><p>Look at the pattern as well as the scores.</p><ul><li><p><strong>Low strategic fit</strong> means the portfolio needs a strategy conversation before any optimizing.</p></li><li><p><strong>Low portfolio coverage with high member value</strong> usually means the individual programs are good but the set is accidental. Look for duplication and for lifecycle stages no program serves.</p></li><li><p><strong>Low operational load</strong> is usually a prioritization problem before it&#8217;s a staffing problem. More headcount can preserve a portfolio that should have been simplified.</p></li><li><p><strong>Low program evolution</strong> is a warning sign even when everything else looks good. A portfolio that can&#8217;t stop anything will eventually become a museum of old priorities.</p></li></ul><h3>An example</h3><p>This one&#8217;s a composite rather than any one company, but it&#8217;s a pattern I&#8217;ve seen plenty of times. A two-person community team runs a monthly customer webinar, a quarterly virtual meetup, weekly office hours, an ambassador program and a forum. The webinar and the meetup both started as ways to share product tips, and they now cover a lot of the same ground for a lot of the same people. Meanwhile, newer customers keep asking basic questions in the forum, and the team doesn&#8217;t have time to build anything for them.</p><p>Running the audit, I&#8217;d expect that team to score reasonably on member value, since people do show up and say nice things. Strategic fit and coverage would land around a 2, because two programs share a job while new customers go unsupported. Operational load would be a 1 (the team is running five programs on two people&#8217;s time, ideally while also sleeping occasionally), and program evolution would be a 1 too, since nothing has ever been stopped.</p><p>Program by program, the call might look like this: consolidate the webinar and the meetup into one series, keep the forum and the ambassador program, pause office hours for a quarter to see who misses them, and use the time that frees up to build something for newer customers. That&#8217;s two portfolio changes, which is about as many as a small team can take on at once.</p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/community-program-portfolio-audit?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/community-program-portfolio-audit?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.thecommunitycode.com/p/community-program-portfolio-audit?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h3>What to watch for</h3><p>Low participation alone isn&#8217;t enough reason to stop a program. A small program serving a strategically important audience can be worth more than a big one full of people who aren&#8217;t very invested.</p><p>A stakeholder liking a program isn&#8217;t enough reason to keep it, either. Keep it because the member and business case still holds, and be ready to explain that case.</p><p>Consolidating doesn&#8217;t have to mean one giant program. Different experiences can serve different needs and still share the same infrastructure, the same calendar or the same team.</p><p>And the audit has limits. It&#8217;ll show you where the portfolio is drifting and which programs to look at, but it won&#8217;t design the replacement for you or tell you how members will feel about a change. That part takes talking to them.</p><h3>Apply the code</h3><ul><li><p>List every recurring community program. Include the small ones and the ones only one person remembers starting.</p></li><li><p>For each program, name its primary member need, business outcome and operating effort. Hours a month is a fine way to describe the effort.</p></li><li><p>Identify programs doing the same job.</p></li><li><p>Identify important member needs with no program supporting them.</p></li><li><p>Mark each program Keep, Improve, Scale, Consolidate, Pause or Stop.</p></li><li><p>Choose the two portfolio changes that would create the most value or free up the most capacity.</p></li><li><p>Set a date to review the portfolio again.</p></li></ul><h4>Checklist</h4><ul><li><p>Every major program has a defined job.</p></li><li><p>Member value is specific.</p></li><li><p>Business value has a plausible mechanism.</p></li><li><p>Programs don&#8217;t duplicate each other without a reason.</p></li><li><p>Important member needs aren&#8217;t being ignored because legacy programs take up the team&#8217;s capacity.</p></li><li><p>Operating effort is visible.</p></li><li><p>The team can stop things.</p></li><li><p>Portfolio decisions reflect current priorities more than history.</p></li></ul><h3>The audit at a glance</h3><ul><li><p><strong>Strategic fit.</strong> Programs map to clear member needs and business priorities.</p></li><li><p><strong>Portfolio coverage.</strong> Each program has a distinct job, and the important needs are covered.</p></li><li><p><strong>Member value.</strong> People would choose to participate without much prompting.</p></li><li><p><strong>Business value.</strong> Each major program has a plausible way of contributing to the business.</p></li><li><p><strong>Operational load.</strong> The portfolio fits the team&#8217;s real capacity.</p></li><li><p><strong>Program evolution.</strong> Programs can change, and they can end.</p></li></ul><p>Score the portfolio, then make a call on each program, and pick the two changes that matter most.</p><h3>Try this</h3><p>Do only steps 1 and 2 this week: list every recurring program and, next to each one, write its member need, its business outcome and the hours a month it takes. You&#8217;ll probably find at least one row that&#8217;s hard to fill in. If any of those programs is newer and you&#8217;re still not sure it should exist, run it through the <a href="https://www.thecommunitycode.com/p/community-readiness-assessment">Community Readiness Assessment</a> as if you were deciding whether to launch it today.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3>Related Posts</h3><ul><li><p><a href="https://www.thecommunitycode.com/p/community-readiness-assessment">Community Readiness Assessment: Should You Build a Community Yet?</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/why-one-community-format-will-never">Why One Community Format Will Never Reach Everyone</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/the-community-integrated-gtm-framework">The Community-Integrated GTM Framework</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[Community Codebreakers: Kimberlea Hunt on Building the House for Friends of Figma]]></title><description><![CDATA[Surveys, structure, tool creep and why you can't create a community out of thin air.]]></description><link>https://www.thecommunitycode.com/p/community-codebreakers-kimberlea-hunt</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/community-codebreakers-kimberlea-hunt</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 10 Nov 2026 16:31:04 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/161145649/8b9000fa8d45bb25dea288ce0027c532.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Kimberlea Hunt, who goes by KB, describes herself as &#8220;a community wizard,&#8221; and having worked with her, I&#8217;d say that&#8217;s pretty accurate. She started her career in public policy and advocacy at Sunrun, then moved into tech and community at Asana, and today she leads the Friends of Figma user group program at Figma.</p><p>KB inherited a program that already existed and rebuilt it, which is a spot a lot of community leaders end up in. We talked about how she gathers input at scale, why she loves a structured process, how she measures a program that&#8217;s kept small on purpose, and why she&#8217;s so wary of new tools.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3>Every community is &#8220;2C&#8221;</h3><p>KB defines community as people coming together around something that brings them joy or excitement, which is what separates it from a support system. She also made a point about B2B I really liked: &#8220;Whether you&#8217;re talking to a B2B or a B2C community, you are still talking to an individual.&#8221; In her view, the real difference is internal, in the strategy and in how you keep the business motivated to invest.</p><h3>Surveys for members, conversations for stakeholders</h3><p>With over 200 leaders around the world, KB relies on surveys (a little to her own amusement) so everyone can weigh in &#8220;no matter what their time zone is.&#8221; Her annual survey goes out every December, built mostly on short-answer questions so people feel comfortable sharing what they love and what they don&#8217;t. Internally, she starts with the stakeholders who actually want to work with her, then brings in the skeptics once there&#8217;s something real for them to lock into.</p><h3>Structure is what makes choice possible</h3><p>&#8220;I love a structured process,&#8221; KB told me. She&#8217;s a big fan of choose-your-own-adventure communities, since some members want a lot of support and some would rather do their own thing without talking to her much at all. (I told her I couldn&#8217;t believe that was possible, and I stand by it.) I described it as a buffet: you don&#8217;t have to eat everything, but if you want to heap your plate mile high, you can.</p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/community-codebreakers-kimberlea-hunt?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/community-codebreakers-kimberlea-hunt?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.thecommunitycode.com/p/community-codebreakers-kimberlea-hunt?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h3>Bringing a siloed program closer</h3><p>When KB joined, Friends of Figma was run by contractors region by region, with each region running its own version and very little visibility into who was doing what. What leaders needed most was to be closer to Figma, so the team globalized the program with KB as the single point person. &#8220;Ironically, the community was missing from this community of leaders,&#8221; she said, and connecting leaders with each other became a big part of the work.</p><p>Because new groups join in small quarterly cohorts, KB sets goals around activity rather than headcount:</p><ul><li><p>How many events leaders host around the world.</p></li><li><p>Who attends, which accounts they&#8217;re from, and whether anything happens afterward, like upgrades or expansion.</p></li><li><p>Participation in Config watch parties, where groups host local viewings of Figma&#8217;s annual conference. There were 80 of them the year before we talked, from Hong Kong to Luxembourg.</p></li></ul><h3>Beware tool creep</h3><p>One thing that drives KB crazy is &#8220;adding vendors for the sake of adding vendors.&#8221; An external tool can shape how the community itself is structured, so she only adds one when leaders are clearly asking for what it does. I&#8217;m the same way, since every new tool comes with integration, legal, security, IT and a learning curve. As KB put it, &#8220;If you need it, they&#8217;ll tell you.&#8221;</p><p>She&#8217;s just as careful about taking things away. She tries never to remove something without saying what takes its place, and she checks whether pushback comes from most members or from a few loud voices.</p><h3>You can&#8217;t create a community</h3><p>When I asked about her least favorite engagement initiative, I was sure the answer would start with a G and end with &#8220;amification.&#8221; It was anything recurring the team can&#8217;t sustain, like a weekly town hall the team doesn&#8217;t have the bandwidth to keep up.</p><p>Her advice for anyone starting out was my favorite part of the conversation. You can&#8217;t create a community, she said. It creates itself, and your job is to build the house it lives in, floor by floor, as it grows.</p><h3>Key takeaways</h3><ul><li><p>Even in B2B, you&#8217;re talking to an individual.</p></li><li><p>Surveys let a global program hear from everyone. Internally, start with the stakeholders who want to work with you.</p></li><li><p>Strong structure lets members choose their own path.</p></li><li><p>A program that&#8217;s small by design should measure activity rather than headcount.</p></li><li><p>Add tools only when members clearly need them, and never take something away without saying what replaces it.</p></li></ul><h3>Decoded insight</h3><p>KB&#8217;s approach comes back to building structure around people who are already excited, then getting out of their way.</p><p>You can connect with KB on LinkedIn at <a href="http://linkedin.com/in/kimberlea">linkedin.com/in/kimberlea</a>. And if this conversation sparked a thought, leave a comment or share it with someone who&#8217;s inheriting a community program and wondering where to start.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3>Timestamps</h3><ul><li><p>00:00 &#8211; Meet KB </p></li><li><p>01:14 &#8211; Defining community </p></li><li><p>01:55 &#8211; A memorable experience as a member </p></li><li><p>03:24 &#8211; B2B, B2C and why every community is &#8220;2C&#8221; </p></li><li><p>04:53 &#8211; Community goals at Sunrun and Figma </p></li><li><p>06:19 &#8211; Gathering input from members and stakeholders </p></li><li><p>08:17 &#8211; Designing program structure </p></li><li><p>10:23 &#8211; Promoting a new program </p></li><li><p>12:00 &#8211; Friends of Figma success metrics </p></li><li><p>14:10 &#8211; Choosing vendors and avoiding tool creep </p></li><li><p>19:45 &#8211; Rebuilding Friends of Figma </p></li><li><p>22:14 &#8211; Engaging leaders through Config and Slack </p></li><li><p>23:48 &#8211; The annual survey </p></li><li><p>24:37 &#8211; Reporting results </p></li><li><p>26:34 &#8211; Changes, rollbacks and loud voices </p></li><li><p>31:30 &#8211; Sustainable swag and the swag store </p></li><li><p>37:33 &#8211; Bumps in the road with independent groups </p></li><li><p>41:59 &#8211; Favorite and least favorite engagement initiatives </p></li><li><p>46:51 &#8211; Advice for building a community program </p></li><li><p>49:33 &#8211; Why KB does this work </p></li><li><p>51:07 &#8211; Where to find KB</p></li></ul><h3>Related Posts</h3><ul><li><p><a href="https://www.thecommunitycode.com/p/unlocking-volunteer-passion-lessons">Unlocking Volunteer Passion: Lessons from Slack Chapter Leader, Kevin Cox</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/community-codebreakers-jane-nadaraja">Community Codebreakers: Jane Nadaraja on Patreon&#8217;s Community</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/community-codebreakers-max-pete-on">Community Codebreakers: Max Pete on Rebuilding B2B Community at Scale</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[Why Community Programs Are So Hard to Stop]]></title><description><![CDATA[Launching a program comes with a kickoff and an announcement, and ending one usually waits until someone has no other choice.]]></description><link>https://www.thecommunitycode.com/p/why-community-programs-are-so-hard-to-stop</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/why-community-programs-are-so-hard-to-stop</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 03 Nov 2026 16:31:39 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!nc_H!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!nc_H!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!nc_H!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!nc_H!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!nc_H!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!nc_H!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!nc_H!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png" width="350" height="350" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/cbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:350,&quot;bytes&quot;:165280,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/223048981?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!nc_H!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!nc_H!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!nc_H!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!nc_H!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcbc53736-571e-4b47-918b-3b243a9829e7_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>At Asana, alongside our Ambassadors program, we ran a program called Certified Pros. It was built for people who consulted on Asana as part of their own businesses, and we put a lot of time and effort into building it out. There wasn&#8217;t really another team to run it, and I&#8217;d been a consultant myself and had run programs like it before, so in lieu of a true partnerships team at the time, community took it on.</p><p>It was a great program, and the members in it really loved it. It also wasn&#8217;t really community in nature. As the company grew, a few of my teammates and I decided it would be better served by the partnerships team, so we wound it down on the community side and transferred it over. It was a difficult decision, and the logistics were difficult too (moving a program people love is a bit like moving apartments while everyone&#8217;s still sitting on the couch). It was also the right thing to do.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3>How programs pile up</h3><p>That&#8217;s a pretty common way for a program to land on a community team. When something needs doing and no one else is around to do it, community often ends up with the pieces other teams can&#8217;t or won&#8217;t take on. Add the programs a team starts on its own, and the list grows quickly:</p><ul><li><p>An event goes well, so it becomes a monthly event.</p></li><li><p>A stakeholder asks for a webinar series, an advisory board or a local chapter program.</p></li><li><p>A program gets inherited because it had nowhere else to go.</p></li></ul><p>Each one makes sense when it starts, and eventually the team is running a portfolio that was never designed as one (a bit like the kitchen drawer where everything in it was useful once).</p><p>Starting something is visible, with a launch, an announcement and someone&#8217;s name on it. Ending something has none of that, and I&#8217;ve yet to see anyone put &#8220;wound down the Thursday webinar series&#8221; in a quarterly review with a confetti emoji. So in my experience, the decision to keep a program is rarely made out loud. It gets made by default, every quarter the program doesn&#8217;t come up.</p><h3>Where the team&#8217;s time goes</h3><p>Most community teams are one or two people, so every recurring program is a real slice of somebody&#8217;s week. That&#8217;s fine while the program is doing its job, and a problem when it&#8217;s keeping the team from something members need more. Maybe newer members are struggling to find their footing while the team spends a week every month on an event that mostly draws the same thirty regulars. More headcount sometimes helps, but sometimes it just means you get to keep running everything, including the parts that should have ended.</p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/why-community-programs-are-so-hard-to-stop?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/why-community-programs-are-so-hard-to-stop?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.thecommunitycode.com/p/why-community-programs-are-so-hard-to-stop?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h3>Good reasons, and reasons that only feel good</h3><p>When I&#8217;m deciding whether a program should keep going, these are the questions I ask:</p><ul><li><p>Does it still have a clear job, for members and for the business?</p></li><li><p>Is something else already doing that job?</p></li><li><p>Can the team actually run it well with the time it has?</p></li><li><p>Has the need moved on, or would it be better served somewhere else in the company?</p></li></ul><p>That last one is what happened with Certified Pros. The program still mattered to the people in it, and it made more sense with a team built for partners.</p><p>The reasons that keep programs alive anyway are a different list: someone senior likes it, it&#8217;s always been there, or ending it would mean an awkward conversation. I get all three (I&#8217;m not a big fan of awkward conversations either), but none of them says anything about whether members are getting something out of it. I&#8217;d add one caution going the other way, too. Small isn&#8217;t the same as failing, and a program for a handful of people can matter a lot if they&#8217;re the right handful.</p><h3>How to end one well</h3><p>Rolling things back is risky, because you never really know how a change is going to land, and the people who loved the thing you&#8217;re ending are usually the ones who care most. If you don&#8217;t share the reason for a decision, members will come up with one of their own, which in my experience is rarely the flattering version. A good wind-down note covers a few things:</p><ul><li><p>What&#8217;s ending, and when.</p></li><li><p>Why, in plain language.</p></li><li><p>What takes its place, or where the program is going.</p></li><li><p>Thanks to the hosts, speakers, volunteers and members who made it work.</p></li></ul><p>A heads-up before anything changes goes a long way, too. And ending a program on purpose can be a sign things went well. The version I&#8217;d worry about is the one that slowly fades because the call never got made, which leaves members wondering what happened and the team wondering whether it ever worked.</p><h3>Making stopping normal</h3><p>The teams I&#8217;ve seen handle this best treat stopping as one of several regular options, alongside keeping, improving, scaling, consolidating and pausing. Two habits help a lot: give every new program a review date at launch, and ask &#8220;would we launch this today?&#8221; about each program, out loud, with the team.</p><p>I&#8217;m putting together a tool for doing this across a whole set of programs. In the meantime, I&#8217;m curious which program on your list would be the hardest to stop, and what makes it so hard!</p><h3>Try this</h3><p>Pick the one program you&#8217;d be least likely to launch if you were starting from scratch today. Write down, in a sentence each, what it&#8217;s for, who it serves and how many hours a month it takes your team. If the first two are hard to write, it&#8217;s worth putting on the agenda for your next planning conversation. And if you&#8217;re worried about cutting the only option some members use, I wrote about that in <a href="https://www.thecommunitycode.com/p/why-one-community-format-will-never">Why One Community Format Will Never Reach Everyone</a>.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3>Decoded Takeaways</h3><p>Community programs pile up. Some start because an event went well, some because a stakeholder asked, and some land on the community team because no other team was there to take them. Over time the team runs a set of programs that was never designed as a set, and keeping each one becomes a default rather than a decision.</p><p>Because most community teams are tiny, every recurring program uses real capacity. The useful questions are whether a program still has a clear job, whether something else already does that job, whether the team can run it well, and whether it would be better served elsewhere in the company. A stakeholder&#8217;s fondness, tradition and the discomfort of an awkward conversation aren&#8217;t reasons to keep something, and small programs deserve care, since a small audience can be the right one.</p><p>How a program ends matters. Explaining why, giving notice, saying what replaces it or where it&#8217;s going, and thanking the people who made it work protect trust. A review date at launch and a regular &#8220;would we launch this today?&#8221; make stopping a normal option.</p><h3>Related Posts</h3><ul><li><p><a href="https://www.thecommunitycode.com/p/why-one-community-format-will-never">Why One Community Format Will Never Reach Everyone</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/who-runs-your-community-after-youve">Who Runs Your Community After You&#8217;ve Designed It?</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/why-nobody-cares-about-your-community">Why Nobody Cares About Your Community Engagement Metrics (and What to Do Instead)</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[Community Readiness Assessment: Should You Build a Community Yet?]]></title><description><![CDATA[A scored check across four conditions, member need, business need, value exchange and ownership, for deciding whether to build, pilot, wait or not build at all.]]></description><link>https://www.thecommunitycode.com/p/community-readiness-assessment</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/community-readiness-assessment</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 20 Oct 2026 15:30:44 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!UppL!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!UppL!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!UppL!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!UppL!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!UppL!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!UppL!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!UppL!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png" width="350" height="350" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:350,&quot;bytes&quot;:105169,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/219812360?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!UppL!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!UppL!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!UppL!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!UppL!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fb0de287f-0085-45aa-b8f4-d1b58c2b45ce_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Deciding whether to build a community usually happens in a meeting where the exciting parts get most of the airtime. Customers are already asking each other for help, leadership wants retention (or product feedback, or advocacy), and somebody usually has a platform in mind. What gets skipped, pretty often in my experience, is whether the conditions are actually there for a community to work, and what to do if one of them isn&#8217;t.</p><p>I wrote about why the weakest condition decides what happens in <a href="https://www.thecommunitycode.com/p/is-your-company-ready-to-build-a-community">Is Your Company Ready to Build a Community?</a>, so I won&#8217;t make that whole case again here. This is the working version: a scored assessment you can run with your team before anyone commits to a platform, a headcount plan or a launch date.</p><h3>What this is for</h3><p>The point of the assessment is to turn &#8220;are we ready?&#8221; into an actual decision: build, pilot, wait, or don&#8217;t build at all.</p><p>It tests four conditions:</p><ol><li><p>Member need</p></li><li><p>Business need</p></li><li><p>Value exchange</p></li><li><p>Organizational capacity, which mostly comes down to ownership</p></li></ol><p>A high score means the basic conditions are strong enough to justify trying something. It doesn&#8217;t tell you how big to go, though. That&#8217;s a separate decision.</p><h3>How to use it</h3><p>Score each statement from 1 to 5 based on what&#8217;s true today, not what&#8217;s planned.</p><ol><li><p>No evidence.</p></li><li><p>Weak or anecdotal evidence.</p></li><li><p>Some evidence, with important gaps.</p></li><li><p>Strong evidence.</p></li><li><p>Clear, repeated evidence.</p></li></ol><p>Use real evidence wherever you can: how customers already behave, what the business is actually prioritizing right now, and who would really do the work. Real talk: if you score from enthusiasm inside the company, everything comes out inflated.</p><h3>The assessment</h3><h4>Member need</h4><ul><li><p>People already seek peer advice, context, connection or examples around this problem.</p></li><li><p>The need recurs, rather than appearing only at launch, onboarding or a single event.</p></li><li><p>Peer interaction adds something the company can&#8217;t provide as effectively on its own.</p></li><li><p>We can identify a specific audience with this need.</p></li><li><p>We have direct evidence from customer or member behavior, beyond internal belief.</p></li></ul><h4>Business need</h4><ul><li><p>Community would support a current business priority.</p></li><li><p>The priority is big enough that leaders will keep paying attention after launch.</p></li><li><p>We can describe the behavior or signal community could plausibly influence.</p></li><li><p>Relevant leaders understand why community may help.</p></li><li><p>We can identify what the company would learn or improve if the program works.</p></li></ul><h4>Value exchange</h4><ul><li><p>Members get real value from participating.</p></li><li><p>The company gets real value without depending on extraction.</p></li><li><p>The contribution asked of members is proportionate to what they receive.</p></li><li><p>There is a credible reason for people to return.</p></li><li><p>The value exchange still makes sense if the company stops offering novelty or swag.</p></li></ul><h4>Organizational capacity</h4><ul><li><p>There is a clear program owner.</p></li><li><p>The owner has enough time and resources to steward the experience.</p></li><li><p>The owner has access to the internal teams that need community signal.</p></li><li><p>The organization is willing to respond when members surface problems.</p></li><li><p>The product and customer experience are stable enough that community isn&#8217;t being asked to compensate for basic failures.</p></li></ul><h3>Read your results</h3><p>Score each section out of 25.</p><ul><li><p><strong>5&#8211;10: Not ready.</strong> The basic condition is missing. Solve that problem before building.</p></li><li><p><strong>11&#8211;17: Test carefully.</strong> There&#8217;s enough signal for research or a small pilot, but not enough for a large commitment.</p></li><li><p><strong>18&#8211;22: Ready to pilot.</strong> The underlying conditions are strong enough to test a focused community experience.</p></li><li><p><strong>23&#8211;25: Strong foundation.</strong> The condition is well supported. Keep validating it as the program grows.</p></li></ul><p>Then look at your lowest section, because that&#8217;s your constraint. Three strong sections don&#8217;t cancel out a weak value exchange or a missing owner, and adding the four scores together hides the one thing you most need to see.</p><h3>An example</h3><p>This one&#8217;s a composite rather than any one company&#8217;s numbers, but it&#8217;s a pattern I&#8217;ve seen many times. A founder decides the company should have a community and sets up a Discord server. Customers join, and a lot of them are really interested in talking to each other about the product. Leadership likes the idea because it could help with retention. The catch is that nobody&#8217;s job includes running it, so whoever&#8217;s keeping an eye on it is doing that in their spare time.</p><p>If that company ran the assessment, I&#8217;d expect it to score well on member need and reasonably well on business need. Value exchange would probably land somewhere in the middle, since members are getting something out of it but nobody has really thought through what the company is asking of them. Organizational capacity would land squarely in &#8220;Not ready&#8221;: no clear owner, no protected time, and no line into the teams who&#8217;d need to hear what&#8217;s coming up.</p><p>Averaged together, that looks like a company that&#8217;s more or less ready. Read by the lowest score, it&#8217;s a company that needs a real owner before it does anything else, ideally before the server gets popular enough to spiral.</p><h3>What to watch for</h3><p>The big one is averaging away a fatal weakness. A community with no member need won&#8217;t be rescued by executive sponsorship, however enthusiastic the sponsor is. And a community with strong member demand but no owner can turn into a group of frustrated customers the company can&#8217;t support.</p><p>The assessment has limits, too. It&#8217;ll tell you where the risk is, but it won&#8217;t pick your platform or your programming for you.</p><h3>Apply the code</h3><ol><li><p><strong>Score all four conditions.</strong> Do it with the people who&#8217;d actually be involved, including whoever would own it.</p></li><li><p><strong>Identify the lowest score.</strong> That section is your constraint, whatever the other three look like.</p></li><li><p><strong>Decide whether a small pilot can test that gap.</strong> If it can, design the pilot around it. If it can&#8217;t, fix the gap first.</p></li><li><p><strong>Design the smallest useful pilot.</strong> One audience, one focus, and a real owner.</p></li><li><p><strong>Define what evidence would justify expansion.</strong> Write it down before the pilot starts.</p></li><li><p><strong>Set a date to decide.</strong> When it arrives, choose whether to scale, redesign, wait or stop.</p></li></ol><h4>Checklist</h4><ul><li><p>The member need is based on real behavior.</p></li><li><p>The business need is current and specific.</p></li><li><p>The value exchange works for both sides.</p></li><li><p>There is a real owner, with protected time.</p></li><li><p>We can run a small test before a large platform or headcount commitment.</p></li><li><p>We know what evidence would change our decision.</p></li></ul><h3>The assessment at a glance</h3><ul><li><p><strong>Member need.</strong> People already want to learn from and connect with each other around this problem, and you can see it in their behavior.</p></li><li><p><strong>Business need.</strong> Community supports a current priority that leaders understand and will stay focused on.</p></li><li><p><strong>Value exchange.</strong> Members get enough to keep coming back, and the company benefits without extracting from them.</p></li><li><p><strong>Organizational capacity.</strong> A real owner with time, resources and access to the teams who need what the community surfaces.</p></li></ul><p>The lowest of the four is your constraint.</p><h3>Try this</h3><p>Score only the organizational capacity section for your community (or the one you&#8217;re planning), and be strict about &#8220;clear program owner&#8221; and &#8220;enough time.&#8221; If that section comes in below 18, I&#8217;d work on ownership before anything else, however strong the rest looks. And if you&#8217;re not sure community is the answer at all, I wrote about that in <a href="https://www.thecommunitycode.com/p/when-community-is-the-wrong-fix">When Community Is the Wrong Fix</a>.</p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/community-readiness-assessment?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/community-readiness-assessment?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.thecommunitycode.com/p/community-readiness-assessment?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h3>Related Posts</h3><ul><li><p><a href="https://www.thecommunitycode.com/p/when-community-is-the-wrong-fix">When Community Is the Wrong Fix</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/who-runs-your-community-after-youve">Who Runs Your Community After You&#8217;ve Designed It?</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/the-community-integrated-gtm-framework">The Community-Integrated GTM Framework</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[Is Your Company Ready to Build a Community?]]></title><description><![CDATA[Four things need to be in place before a community launch, and the one you're weakest on decides how it goes.]]></description><link>https://www.thecommunitycode.com/p/is-your-company-ready-to-build-a-community</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/is-your-company-ready-to-build-a-community</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 06 Oct 2026 15:31:14 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!hTdD!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!hTdD!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!hTdD!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!hTdD!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!hTdD!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!hTdD!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!hTdD!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png" width="350" height="350" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/de330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:350,&quot;bytes&quot;:109018,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/218848866?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!hTdD!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!hTdD!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!hTdD!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!hTdD!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fde330b72-bf01-4ab4-855c-e3a5a5a62494_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>When I advise companies about building community programs, there&#8217;s a conversation that comes up again and again. They tell me they started a community about a year ago, so I ask to talk to whoever&#8217;s running it. More often than I&#8217;d like, the answer is some version of &#8220;well, no one&#8217;s running it, we just started a Discord.&#8221;</p><p>I understand how it happens. A founder or someone in marketing says let&#8217;s just start a community, and a Discord server or a Slack group is the fastest way to have one. It feels like progress, and for the first few weeks it can even look like it&#8217;s working. The gap is that nobody&#8217;s job includes running it, and that doesn&#8217;t show up until later.</p><p>When a company asks me whether it&#8217;s ready to build a community, the conversation usually starts with the parts that look good. Customers are already asking each other for help somewhere. Leadership has a reason to care, maybe retention, maybe product feedback. There&#8217;s even a rough idea of what members would get out of showing up.</p><p>Then I ask who&#8217;s going to run it.</p><h3>Four things need to be in place</h3><p>The way I think about readiness comes down to four conditions. All of them need to be true, at least well enough to start:</p><ul><li><p><strong>Member need.</strong> People already want to learn from each other or connect around this problem, and you can see it in how they behave, beyond what the company hopes.</p></li><li><p><strong>Business need.</strong> Community would support something the company cares about right now, and the leaders involved understand why.</p></li><li><p><strong>Value exchange.</strong> Members get something real from participating, and the company gets something back without extracting it from them.</p></li><li><p><strong>Ownership.</strong> A specific person is responsible for it, with enough protected time to do the work and a line into the teams who need to hear what the community is saying.</p></li></ul><p>The teams I talk to usually have a decent story for the first three. Ownership is the one that gets waved through, because it feels like a staffing detail you can sort out after launch.</p><h3>Why you can&#8217;t average them</h3><p>It&#8217;s tempting to treat readiness like a score, where strength in three places makes up for a gap in the fourth. Plenty of member demand, a clear business case, a sensible value exchange and a plan to figure out the owner later sounds like three out of four, and three out of four sounds pretty good.</p><p>I don&#8217;t think it works that way. The weakest condition decides what happens, because the others depend on it. Strong member demand with no owner can turn into a frustrated group of customers the company can&#8217;t support. A great business case with no real member need gives you a space people stop coming back to, however good the programming is.</p><p>Seen that way, the question worth asking before launch shifts. It stops being whether there&#8217;s enough excitement and becomes which of the four is weakest, and whether that one can be fixed first.</p><h3>What a missing owner looks like a few months in</h3><p>Back to the Discord. If it&#8217;s at all popular, posts start coming in faster than anyone can read them. The person keeping an eye on it in their spare time has neither the experience nor the bandwidth to keep it under control, let alone make it a useful, valuable place for the people in it and for the business.</p><p>From there, I&#8217;ve usually seen one of these happen:</p><ul><li><p>The company shuts it down, which is terrible for the people who showed up and cared.</p></li><li><p>It gets left to drift, which is also bad, just slower.</p></li><li><p>Someone gets brought in to clean it up, which usually means a lot of time dealing with some significantly bad content before anything of quality can be rebuilt, often from scratch.</p></li></ul><p>That last one is extremely time consuming, and it&#8217;s work that a real owner from the start would mostly have avoided. My advice here is about as plain as I get: don&#8217;t start a place where you&#8217;re encouraging customers to have conversations without someone on your team whose job it is to manage it.</p><h3>When the owner is a junior hire expected to do everything</h3><p>Sometimes the company does hire someone. The version I see most often goes something like: we need a community, who&#8217;s the cheapest person we can get to do this? I don&#8217;t know of any other part of the business where you&#8217;d hire the least experienced, least knowledgeable, but maybe very eager person you can find and put them in front of your customers all the time.</p><p>The job postings tell the same story. I&#8217;ve seen them ask for two or three years of experience to single-handedly lead, strategize, execute and report on a community program that doesn&#8217;t exist yet. That&#8217;s the whole job, handed to someone with very little experience to lean on and nobody more senior to learn from, often for very little pay. The people in those roles are often talented and eager, and I don&#8217;t hold it against them. What it tells me is that the company doesn&#8217;t yet value community, and hasn&#8217;t understood what goes into making it work.</p><p>The owner doesn&#8217;t always have to be a dedicated hire. Typically it&#8217;s one full-time person, and sometimes it&#8217;s half of another person&#8217;s time. Either way, the time needs to be carved out and protected, and there needs to be a person.</p><h3>Value exchange, and who fixes it</h3><p>At HeyGen, I inherited a community that was essentially a bunch of activities that had been happening before I arrived. It needed to be righted before it could really work.</p><p>Recentering it started with talking to community members about what they actually wanted or needed, especially the ones in the audience we were trying to build for. From there we restructured the program and rethought the strategy around it, so that it met what the business was trying to achieve along with what members wanted to have happen.</p><p>I bring it up because of the order things happened in. The value exchange got repaired because someone owned the community and had the job of going and asking. Without an owner, the other three conditions don&#8217;t have anyone looking after them either.</p><h3>What I&#8217;d do with the weakest one</h3><p>A few questions I&#8217;d put to any team before a launch:</p><ul><li><p>Who owns this, by name, and how many hours a week do they actually have for it?</p></li><li><p>What will community do for this business that isn&#8217;t already served by something else in your go-to-market?</p></li><li><p>Are customers already helping each other somewhere, even informally?</p></li><li><p>What would make participating worth it for members, given everything else competing for their time?</p></li></ul><p>Sometimes the answers point to waiting, and that&#8217;s a legitimate outcome. If ownership is the weak spot and the rest looks strong, if it were me, I&#8217;d run a pilot, with a real owner and a set date to look at what happened and decide whether to keep going, before anyone commits to a platform or a headcount plan.</p><p>I&#8217;d be patient with that date, too. In my experience community typically takes several months or more before it shows results for the business, so the first decision point should look at whether the pilot is doing what you set it up to test.</p><h3>What a readiness check won&#8217;t tell you</h3><p>Working through the four conditions tells you where the risk sits. It won&#8217;t tell you how big to go, which platform to pick, or what the programming should be, and a team can look strong on all four and still have a hard first year. What it does tell you is which condition to work on before you launch, and in the companies I&#8217;ve advised, that&#8217;s most often the owner.</p><h3>Try this</h3><p>Before your next planning conversation about community, write down who would own it, by name, and how many hours a week they&#8217;d have for it. If either answer is fuzzy, that&#8217;s the condition to work on before anything launches. For more on what ownership involves once a community is up and running, read <a href="https://www.thecommunitycode.com/p/who-runs-your-community-after-youve">Who Runs Your Community After You&#8217;ve Designed It?</a></p><h3>Decoded Takeaways</h3><p>Readiness for a community comes down to four conditions: whether members need it, whether the business needs it, whether the value exchange works for both sides, and whether someone owns it. They don&#8217;t add up like a score. The weakest one decides what happens, because the others depend on it.</p><p>Ownership is the condition teams most often wave through, treating it as a detail for after launch. The results are familiar: a Discord or Slack group that grows faster than anyone can manage and ends up shut down, left to drift, or cleaned up at great effort. Hiring the cheapest, least experienced person available and expecting them to do everything leads to the same place more slowly.</p><p>A real owner is also what makes the other conditions repairable, because someone has the job of asking members what they need and reshaping the program around it. Before launching, it&#8217;s worth naming the weakest condition and deciding whether to fix it first, run a pilot with a real owner and a set decision date, or wait.</p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/is-your-company-ready-to-build-a-community?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/is-your-company-ready-to-build-a-community?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.thecommunitycode.com/p/is-your-company-ready-to-build-a-community?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h3>Related Posts</h3><ul><li><p><a href="https://www.thecommunitycode.com/p/when-community-is-the-wrong-fix">When Community Is the Wrong Fix</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/who-runs-your-community-after-youve">Who Runs Your Community After You&#8217;ve Designed It?</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/why-community-teams-lack-decision">Why Community Teams Lack Decision-Making Power</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[Somebody Has to Decide What Members See Next]]></title><description><![CDATA[What a member encounters after they join is a design decision, even when nobody treats it as one.]]></description><link>https://www.thecommunitycode.com/p/what-members-see-after-they-join</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/what-members-see-after-they-join</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 29 Sep 2026 15:31:17 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!ZmyO!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!ZmyO!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!ZmyO!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg 424w, https://substackcdn.com/image/fetch/$s_!ZmyO!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg 848w, https://substackcdn.com/image/fetch/$s_!ZmyO!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!ZmyO!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!ZmyO!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg" width="1456" height="1092" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/a72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1092,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:563530,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/214376741?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!ZmyO!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg 424w, https://substackcdn.com/image/fetch/$s_!ZmyO!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg 848w, https://substackcdn.com/image/fetch/$s_!ZmyO!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!ZmyO!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fa72afe1c-9bc1-4c87-852e-fe9cf596b479_2216x1662.jpeg 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><span>For a few years now I&#8217;ve been going to one of my favorite community events, KCON in Los Angeles. The thing that struck me at the most recent one had nothing to do with the music.</span></p><p><span>In previous years the whole thing felt centered on K-pop, which makes sense, because that&#8217;s what most people are buying a ticket for. K-pop was still clearly the draw, and the convention around it had been deliberately widened. There was programming and floor space given over to K-dramas and broader Korean content, to K-beauty, to Korean food, and to Korean culture more generally. I wasn&#8217;t reading that into the layout, either. During some of the MC segments they said it directly, that they wanted people to leave more interested in Korean culture than they arrived.</span></p><p><span>So somebody sat down and decided what a person who came for one artist was going to walk past on their way through the building.</span></p><p><span>The obvious lesson would be that KCON cross-sells well, which is both true and boring. The more useful observation is that the ecosystem created the conditions for someone&#8217;s interest to widen, by putting adjacent things in front of people who already had a reason to trust the setting they were standing in. Nobody had to be persuaded that Korean culture was worth their attention. They had already bought a ticket. All that remained was whether the next thing was visible or not.</span></p><p><span>There&#8217;s a version of this in B2B that I don&#8217;t think gets designed on purpose very often.</span></p><p><span>A customer enters through one team, one use case, one problem they needed solved this quarter. Then they show up in the community, and what happens next depends almost entirely on what&#8217;s in front of them there. If the only thing visible is more material about the use case they already have, they&#8217;ll get better at that one thing, which is fine. If they come across people using the product in ways they hadn&#8217;t considered, some of that will stick, and a portion of it will turn into a conversation with a colleague on a different team.</span></p><p><span>None of that is mysterious. It&#8217;s a set of fairly ordinary decisions that somebody either made or didn&#8217;t: what the welcome sequence actually says, which conversations get surfaced rather than buried under whatever was posted most recently, what the event calendar covers across a quarter, which groups a new member is shown on the way in, what goes into the digest, and who gets introduced to whom. Each one is a small choice about what a person encounters. Together they determine whether somebody who arrived for one thing ever finds out the other things exist.</span></p><p><span>It&#8217;s worth saying that adjacency isn&#8217;t automatically a gift. Someone who discovers three things their team can&#8217;t fund, or that would need buy-in from a sibling team they don&#8217;t have, may come away more frustrated than when they arrived. Showing people what other customers are doing is also showing them what they aren&#8217;t getting, which is worth weighing when you decide what to put in front of whom.</span></p><p><span>The question I&#8217;d want to ask about my own program, and the one I&#8217;d ask a client, is this: if somebody arrives through one entry point, what do they come across next, and did anyone decide that or did it just happen?</span></p><p><span>Korean culture isn&#8217;t a company, obviously. It&#8217;s a great many creators, brands, and institutions with different and sometimes competing interests, and whatever got decided inside that convention center doesn&#8217;t extend to any of them. The deliberateness I saw was KCON&#8217;s, and that&#8217;s the part I&#8217;m borrowing.</span></p><h3><span>Try this</span></h3><p><span>Take one customer who joined your community in the last six months through a single use case, and trace what they&#8217;ve actually encountered since, meaning what they&#8217;ve plausibly seen rather than everything that was technically available to them. Then ask whether that path was designed by anyone, or whether it&#8217;s just the shape your program happened to take. If the answer is that nobody chose it, </span><a href="https://www.thecommunitycode.com/p/why-one-community-format-will-never"><span>Why One Community Format Will Never Reach Everyone</span></a><span> is where I&#8217;d start, because what somebody encounters next is mostly a function of which formats and layers exist for them to encounter at all.</span></p>]]></content:encoded></item><item><title><![CDATA[The Community-Integrated GTM Framework]]></title><description><![CDATA[Community cuts across every go-to-market function and sits inside one of them. This is the model I use to make that work.]]></description><link>https://www.thecommunitycode.com/p/the-community-integrated-gtm-framework</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/the-community-integrated-gtm-framework</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 22 Sep 2026 15:31:30 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!ohu4!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!ohu4!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!ohu4!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!ohu4!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!ohu4!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!ohu4!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!ohu4!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png" width="350" height="350" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/ec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:350,&quot;bytes&quot;:100552,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/214376477?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!ohu4!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!ohu4!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!ohu4!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!ohu4!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fec7ddae3-6033-4bd9-9eba-ac32fdadb84d_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><span>Most companies organize go-to-market vertically. Product owns roadmap and prioritization. Marketing owns demand and narrative. Sales owns revenue. Customer success owns retention and expansion. Community gets put somewhere on that org chart, but customers don&#8217;t experience a company in those same departmental slices.</span></p><p><span>Community tends to cut across them.</span></p><p><span>At Asana, for example, the forum, ambassador program, events, and other community surfaces gave us visibility into how people were learning the product, where teams were getting stuck, which use cases were spreading inside organizations, and who was becoming an advocate. Those signals could matter to product, marketing, sales, customer success, and other teams for different reasons.</span></p><p><span>The useful question was rarely &#8220;which outcome does community own?&#8221; It was usually &#8220;how do we make sure what community is seeing actually changes how the rest of the company works?&#8221; That&#8217;s what this framework is designed to help with.</span></p><p><span>I&#8217;ve written separately about what community is doing once somebody has already become a customer, which tends to be the least worked-out part of this. What follows is the operating version of that argument, so I won&#8217;t re-make the case here.</span></p><h3><span>The model</span></h3><p><span>Community-integrated GTM treats community as a horizontal source of customer participation, signal, and connection across the customer lifecycle. The model has a sequence:</span></p><ol><li><p><span>Alignment</span></p></li><li><p><span>Integration</span></p></li><li><p><span>Amplification</span></p></li></ol><p><span>I use the sequence intentionally. I&#8217;ve seen companies try to jump directly to amplification by asking community to generate more advocacy, more pipeline, more referrals, more content, or more product feedback. Sometimes that produces activity. It rarely fixes the underlying operating problem if teams are still working from different assumptions about the customer.</span></p><h4><span>Alignment</span></h4><p><span>Alignment starts with shared inputs.</span></p><p><span>Different GTM teams naturally see different parts of the customer. Sales hears objections during evaluation. Customer success sees adoption friction after the contract is signed. Product sees feature usage and requests. Marketing sees which stories and messages get attention. Community can see pieces of all of those things, often in the same conversation.</span></p><p><span>The problem starts when each team builds its own version of customer reality from its own slice of the evidence.</span></p><p><span>Alignment means creating a shared enough view of the customer that teams can make related decisions from related information. They don&#8217;t need to agree about everything. They do need access to the signals that could materially change their decisions.</span></p><p><span>Questions I&#8217;d ask:</span></p><ul><li><p><span>What customer signals are showing up in community today?</span></p></li><li><p><span>Which teams would make different decisions if they had those signals?</span></p></li><li><p><span>Where are teams currently working from different assumptions about customer needs, language, behavior, or friction?</span></p></li><li><p><span>Which business priorities matter enough right now that community should be paying particular attention to them?</span></p></li></ul><p><span>A company is reasonably aligned when community has a clear connection to current business priorities and the relevant teams have a shared understanding of what community can see that they cannot see as easily on their own.</span></p><h4><span>Integration</span></h4><p><span>Shared information doesn&#8217;t do much sitting in a recap deck.</span></p><p><span>Integration is the operational part of the framework. Customer signal has to enter the places where decisions actually get made: roadmap discussions, positioning reviews, sales enablement, onboarding design, expansion planning, content planning, support processes, and whatever other operating loops matter in that company.</span></p><p><span>This is where I&#8217;ve seen a lot of well-intentioned community work stall. A community team may produce an excellent monthly report full of member feedback and emerging patterns. People read it, say it&#8217;s interesting, and then go back to their existing workflows.</span></p><p><span>Integration asks a more practical question: where does this information need to show up so somebody can actually use it?</span></p><p><span>Questions I&#8217;d ask:</span></p><ul><li><p><span>Where are the recurring decisions that community insight should inform?</span></p></li><li><p><span>Who owns those decisions?</span></p></li><li><p><span>What format makes the signal usable for that person or team, and how often does it need to arrive?</span></p></li><li><p><span>What happens after the signal is shared, and can community see whether anything changed as a result?</span></p></li></ul><p><span>A company is integrated when community signal has an expected route into relevant operating processes, with enough context that another team can evaluate and act on it.</span></p><h4><span>Amplification</span></h4><p><span>Once alignment and integration are working, community can strengthen things the company is already trying to do.</span></p><p><span>Before somebody buys, that tends to be easier to describe. Afterward, the description tends to collapse into engagement, which doesn&#8217;t give anyone a decision to make. It&#8217;s more useful to organize this part around what&#8217;s actually happening to the customer.</span></p><p><strong><span>Adoption.</span></strong><span> A new customer sees how a comparable team made something work, tries a version of it, and reaches whatever behavior counts as adopted for your product. Customer success and education usually own the outcome, with community supplying the peer examples. Before anything shows up in an adoption metric, the thing to watch is whether the customers who saw those examples get there sooner than the ones who didn&#8217;t.</span></p><p><strong><span>Expansion.</span></strong><span> This takes two shapes. A team goes further with what it already has, picking up capabilities it had ignored or moving from one workflow into several. Or somebody encounters a use case belonging to a different team, carries it back, and that other team starts using the product for its own reasons. The account team owns the follow-up either way, and community owns making the possibility visible in the first place. For the deepening version, the early indicator is which capabilities members are asking each other about before those requests reach sales. For the cross-team version, it&#8217;s how many distinct job functions from a single account are participating at all, which is countable long before anything reaches ARR. Both are participation counts, so report them as leading signs rather than as the outcome itself. Count them without making a show of it, as well. People share differently once they know a thing is being scored, which is its own reason to keep this a background measure rather than a program goal.</span></p><p><strong><span>Retention.</span></strong><span> Accumulated participation raises what a switch would actually cost. Customer success owns the outcome, with community creating the conditions. The early indicator worth watching is whether that depth is developing in accounts outside your current top tier.</span></p><p><strong><span>Advocacy.</span></strong><span> Value received becomes value produced. Community and customer marketing share this one. Unprompted member-to-member help moves well ahead of case studies or reference calls, which makes it the more useful thing to watch.</span></p><p><span>Community programs can also create their own direct outcomes. At Asana, our community programs influenced substantial pipeline, and community members were more likely to be on paid plans. Both of those are correlations, and I&#8217;d describe them the same careful way I&#8217;d describe anything else here. The larger lesson for me was how much more useful those programs became when they were connected to the rest of the business.</span></p><p><span>Questions I&#8217;d ask:</span></p><ul><li><p><span>Which existing GTM outcome is community helping improve?</span></p></li><li><p><span>What behavior or signal connects community participation to that outcome?</span></p></li><li><p><span>Can we see an intermediate effect before the final business metric moves?</span></p></li><li><p><span>Are we strengthening a working system, or asking community to compensate for a broken one?</span></p></li></ul><p><span>That last question matters. Community can help customers learn from each other. It cannot repair a product nobody wants, a pricing model customers don&#8217;t understand, or an onboarding experience that fundamentally doesn&#8217;t work. I&#8217;ve seen community asked to absorb problems that belong somewhere else. That drains the team and frustrates the members.</span></p><h3><span>In practice</span></h3><p><span>I wouldn&#8217;t start by reorganizing the community team or buying another platform. Start with one business priority where community already has useful signal or participation.</span></p><p><span>For example, suppose the business is focused on improving activation. Community conversations show that new customers repeatedly struggle with the same handoff between individual setup and team adoption. Rather than setting a goal to increase community posts, you might route that pattern into onboarding and education, recruit experienced members to share team setup examples, and track whether the relevant activation behavior improves among customers exposed to those resources.</span></p><p><span>The point is to connect community activity to a business problem through an observable mechanism. Otherwise you&#8217;re left with two charts that moved at roughly the same time and a lot of optimism about causation.</span></p><h3><span>What to watch for</span></h3><p><span>Community-integrated GTM doesn&#8217;t require community to report to a particular executive. I&#8217;ve had opinions about organizational design over the years, and context matters too much for one reporting line to be universally right.</span></p><p><span>It also doesn&#8217;t require every customer signal to become a cross-functional initiative. That would create its own bureaucracy. Some feedback is anecdotal. Some requests are specific to a small segment. Some patterns matter deeply to members and very little to the current business strategy.</span></p><p><span>The work is deciding which signals deserve broader attention, where they should go, and whether the organization has a way to use them.</span></p><p><span>Where the framework stops helping is attribution. Each of the four amplification paths is plausible and none of them is proven, because the data that would separate cause from correlation usually sits in systems nobody has connected. Say so in the reporting. In my experience executives trust the rest of the number more when you do.</span></p><h3><span>Questions to work through</span></h3><p><span>If you want to see how integrated community is today, pick one meaningful customer pattern that surfaced in the last month and trace it.</span></p><p><span>Where did it appear? Who saw it? Who else needed to know? Did it enter a decision process? Did anything happen? Did the community team or the members who raised it ever learn what happened next?</span></p><p><span>You can learn a surprising amount about the operating model from that one example.</span></p><h3><span>The model at a glance</span></h3><p><strong><span>Alignment.</span></strong><span> Shared customer signal and shared connection to current business priorities.</span></p><p><strong><span>Integration.</span></strong><span> Community signal and participation enter the workflows where GTM decisions get made.</span></p><p><strong><span>Amplification.</span></strong><span> Community strengthens adoption, expansion, retention, and advocacy through those integrated loops, each with an owner and an early indicator that moves before the business metric does.</span></p><p><span>The sequence matters because amplification is easier to sustain when the organization is aligned enough to recognize useful signal and integrated enough to act on it.</span></p><h3><span>Apply the code</span></h3><p><span>If you only do one thing with this framework, pick one business priority and run it through these five steps:</span></p><ol><li><p><strong><span>Name the business priority.</span></strong><span> Choose one outcome the company already cares about: adoption, retention, expansion, pipeline, or something equally concrete.</span></p></li><li><p><strong><span>Identify what community can see.</span></strong><span> Write down the customer behaviors, questions, language, friction, or participation patterns that community is surfacing around that priority.</span></p></li><li><p><strong><span>Find the people and decisions that need that signal.</span></strong><span> List the GTM teams involved and the actual decision or workflow where the information could change what happens next.</span></p></li><li><p><strong><span>Build one operating loop.</span></strong><span> Decide who shares the signal, where it goes, who owns the response, and how community learns what happened. Keep it small enough that people will actually use it.</span></p></li><li><p><strong><span>Look for amplification.</span></strong><span> Track whether the loop improves an observable behavior or intermediate outcome before claiming a final business result. If nothing changes, fix the loop before adding more programs.</span></p></li></ol><h4><span>Checklist</span></h4><ul><li><p><span>We can name the current business priority community is supporting.</span></p></li><li><p><span>We know what relevant customer signal community can see.</span></p></li><li><p><span>The teams that need that signal receive it in a usable way.</span></p></li><li><p><span>The signal enters a real decision or workflow, rather than ending in a report.</span></p></li><li><p><span>Someone owns what happens next, and community can see whether action was taken.</span></p></li><li><p><span>We can point to an observable behavior or outcome that should change if the integration is working.</span></p></li><li><p><span>For any post-sale claim, we&#8217;ve named the path, the owner, and the early indicator, and we&#8217;ve said out loud what we can&#8217;t yet separate.</span></p></li></ul><p><span>If you can&#8217;t check several of these boxes, I&#8217;d work there before trying to increase community activity. More activity flowing through a disconnected system usually gives you more disconnected information.</span></p><h3><span>Try this</span></h3><p><span>Mark which of the four amplification paths your community is actually being measured on right now: adoption, expansion, retention, or advocacy. In the teams I&#8217;ve worked with, the answer is usually none of them, and participation volume is standing in for all four at once. Pick the one your business cares most about this quarter, write a single sentence naming the behavior that matters and the early indicator you&#8217;d watch first, and take it to whoever owns that outcome inside your company. If you want the longer argument for community as infrastructure rather than a program, that&#8217;s most of what </span><a href="https://www.amazon.com/dp/B0GNJBXCPR"><span>The Community Code</span></a><span> is about.</span></p><h3><span>Related Posts</span></h3><ul><li><p><a href="https://www.thecommunitycode.com/p/from-community-led-to-community-integrated"><span>Why I No Longer Say &#8220;Community-Led Growth&#8221;</span></a></p></li><li><p><a href="https://www.thecommunitycode.com/p/community-signal-has-to-reach-the-business"><span>Community Signal Has to Reach the Business</span></a></p></li><li><p><a href="https://www.thecommunitycode.com/p/the-gtm-problem-behind-the-community"><span>Where Community Breaks Down Inside GTM</span></a></p></li></ul><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/the-community-integrated-gtm-framework?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/the-community-integrated-gtm-framework?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.thecommunitycode.com/p/the-community-integrated-gtm-framework?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div>]]></content:encoded></item><item><title><![CDATA[What Does Community Actually Do After the Sale?]]></title><description><![CDATA[Most of us agree community helps with adoption, expansion, retention, and advocacy. Far fewer of us can say how.]]></description><link>https://www.thecommunitycode.com/p/what-does-community-do-after-the-sale</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/what-does-community-do-after-the-sale</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 08 Sep 2026 15:30:48 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!HhV4!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!HhV4!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!HhV4!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!HhV4!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!HhV4!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!HhV4!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!HhV4!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png" width="350" height="350" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/c65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:350,&quot;bytes&quot;:48994,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/214375779?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!HhV4!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!HhV4!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!HhV4!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!HhV4!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fc65af529-8fb7-4d4b-8a6c-1b38a797f894_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><span>A community lead I worked with a while back had a slide she brought to every quarterly review. Member growth, posts, event attendance, satisfaction scores, all of it moving in the right direction, and she was rightly proud of it because the numbers were real and she had worked hard for them. Then somebody from finance asked what any of it had to do with renewals, and there was one of those pauses that lasts about four seconds and feels considerably longer, and then the meeting moved along to the next thing. She told me later that she hadn&#8217;t had a good answer, and that she&#8217;d been dreading that question for about a year.</span></p><p><span>I&#8217;ve been on both sides of that exchange. I&#8217;ve built that slide, more than once, and I&#8217;ve also sat in the room wishing the person presenting it would tell me something I could actually use.</span></p><p><span>The claim underneath the slide is one most of us in community work believe, which is that community helps with adoption, expansion, retention, and advocacy. I believe it too, and I&#8217;ve watched it happen at Asana, at Evernote, and across a lot of advisory work since. The problem is that &#8220;community improves retention,&#8221; said on its own, isn&#8217;t yet a claim about anything. It doesn&#8217;t say which customers, doing what, leading to what, over how long. It doesn&#8217;t hand anyone something to go and do differently next week. In a room where everyone else has a number attached to their name, it lands like a feeling rather than an argument, and people are polite about it and then move on.</span></p><p><span>So the question worth sitting with is the how. If community contributes to those outcomes once somebody has already become a customer, what is actually happening, to whom, and how would anyone know?</span></p><h3><span>The question that helped at Asana</span></h3><p><span>The community work at Asana was anchored in adoption, expansion, and retention for a long time before we could show any of it clearly. That&#8217;s what the ambassador program was built around, and the forum, and the events. By the end there were roughly 25,000 ambassadors, most of them team leads running Asana inside their own organizations, alongside a forum with hundreds of thousands of people in it and a global events program running into the hundreds of events a year. We knew what we were trying to influence, and we designed the programs with that in mind.</span></p><p><span>What we couldn&#8217;t do, for a long stretch, was see it. The question that eventually got us somewhere was a fairly plain one, and it came from the shape of the product. Asana is a team-based tool, so: are accounts with an ambassador in them adopting, expanding, and renewing differently from accounts without one?</span></p><p><span>Getting to an answer meant having community participation data sit next to account data, and that data was scattered across an array of disparate systems. Mostly what it took was going to our data analytics team, more than once, and asking them to help me connect those dots, with the particular mix of gratitude and persistence you develop when you need something from a team that doesn&#8217;t report to you. There wasn&#8217;t anything clever about the question itself. Answering it was the part that took time.</span></p><p><span>Once we could see it, the conversations with the rest of the business changed. We could compare accounts that had an ambassador in them against accounts that didn&#8217;t, look at how each group was behaving, and then talk about what to do with that. Usually it meant working with customer success to get ambassadors into the accounts where their presence would matter most, which is something a CS leader can plan around.</span></p><p><span>None of that is causation, and I&#8217;ve never claimed otherwise. It&#8217;s correlation. It was still worth having, because it told us where to put our effort, and I&#8217;d rather say that plainly than dress it up. Executives have heard the dressed-up version before, and once someone catches you overstating what you can prove, everything else you tell them gets discounted along with it.</span></p><h3><span>Four different things wearing the same word</span></h3><p><span>Part of what makes this hard is that &#8220;engagement&#8221; gets used as a single word for several processes that work quite differently from each other. Underneath it, the things community is actually doing after somebody becomes a customer tend to fall into four groups:</span></p><ul><li><p><strong><span>Adoption</span></strong><span>, where a customer actually starts using what they bought, helped along by seeing how a peer did the thing they&#8217;re trying to do.</span></p></li><li><p><strong><span>Expansion</span></strong><span>, where a customer uses or buys more, either because a team went further with what it already had or because somebody carried a use case back to a different team.</span></p></li><li><p><strong><span>Retention</span></strong><span>, where a customer stays, and part of the reason is that leaving would now mean giving up relationships, knowledge, and a bit of standing built alongside the product.</span></p></li><li><p><strong><span>Advocacy</span></strong><span>, where a customer vouches for you, publicly or privately, because they&#8217;ve had enough value from being there to be willing to.</span></p></li></ul><p><span>In practice they overlap constantly, and a community team, which is usually small, gets asked to influence all four at once. What differs is the mechanism underneath each one and the evidence that would show it working, which is why a single participation number can&#8217;t stand in for all of them.</span></p><p><span>The adoption one is the most familiar to anyone who has run a forum. A lot of the questions we got at Asana arrived looking tactical, about permissions or templates or how to structure a project, and underneath they were usually about how a group of people worked together. Somebody would set something up successfully on their own and then find that their team carried on doing it the old way, and no amount of documentation fixed that, because documentation explains how a feature behaves and not what happens when a dozen people have opinions about it. What tended to help was showing them how a team of a similar size and shape had actually made it stick.</span></p><p><span>Expansion covers a fair bit of ground. Sometimes it&#8217;s a team going further with what they already bought, picking up capabilities they&#8217;d ignored or moving from one workflow to several, which community helps with in much the same way it helps adoption. The version I find most interesting is the one that crosses into another team, partly because it doesn&#8217;t look like expansion while it&#8217;s happening. When I was at Gradual, one of our customers, an AI company, started their community program inside a single team with a deliberately narrow focus. Customers showed up and participated, and other teams inside that company could see it happening. Those teams wanted in, and over time they picked the platform up for their own purposes, first for customer education, then champion engagement, then customer marketing, and eventually demand gen events and webinars. Each team that came on board made the next one a bit easier, because there was more of it visible internally for somebody to point at. There were discovery calls and sales conversations along the way, the way there always are. What&#8217;s worth noticing is where the interest started, which was somebody inside that company seeing a colleague doing something adjacent and wanting a version of it for themselves. The commercial conversation followed that interest rather than manufacturing it, and that&#8217;s a meaningfully different thing from a rep working an account cold.</span></p><h3><span>Where I&#8217;d stop short</span></h3><p><span>Retention is where I&#8217;d be most careful, because it&#8217;s where the claims tend to get loosest.</span></p><p><span>The version I find plausible is about accumulation. A customer who has used the product for two years and done nothing else has one thing to lose if they leave. A customer who also knows a handful of people through the community, who has answered questions and been thanked for it, and who has picked up a way of working rather than a set of clicks, has rather more to rebuild somewhere else, at their own expense, on their own time. The software is replaceable in a way the rest of it isn&#8217;t, and the difference is closer to changing neighborhoods than changing banks.</span></p><p><span>That&#8217;s a reasonable story and it may well be true. It&#8217;s also very hard to separate from a much less flattering explanation, which is that the customers who accumulate all of that were the committed ones to begin with, and the community is where their commitment became visible rather than where it came from. I&#8217;ve never been able to fully pull those apart, and there&#8217;s one thing I&#8217;d want to know before believing the stronger version: is that depth showing up in accounts that didn&#8217;t already look like your best ones?</span></p><p><span>If it is, that&#8217;s the more interesting result, because something is happening in accounts where nothing was guaranteed, and it&#8217;s where I&#8217;d point the program next. If depth only ever appears in customers who were always going to stay, the program is still worth running for the people in it, and I&#8217;d stop describing it as a retention driver, because what you&#8217;re holding is a picture of your strongest accounts rather than an explanation of why they&#8217;re strong.</span></p><p><span>Advocacy is mostly a question of sequence. Think of it as a piggy bank: companies want to make a withdrawal before they&#8217;ve made any deposits. They want the referrals, the case studies, and the reference calls before they&#8217;ve put much into the relationship at all. Members can tell, which is why the ask so often lands with a thud and then somebody wonders why the advocacy program isn&#8217;t converting.</span></p><p><span>What happens when it works is less spontaneous than that might sound. Plenty of advocacy gets asked for, and there&#8217;s nothing wrong with that, because making asks is how advocacy programs actually run. What&#8217;s different is that by then somebody has gotten real value out of being there, some of it from the company and some of it from other members, and they&#8217;re willing to be asked.</span></p><p><span>The craft is in the asks themselves. They need to be the right size, made at a moment that makes sense for that person, and spaced out enough that being an advocate doesn&#8217;t turn into a second job. And whatever the ask is, an advocate can never be put in a position where they feel like they&#8217;re selling, because that&#8217;s the point at which they stop being credible to the people they&#8217;re talking to.</span></p><p><span>There&#8217;s a measurement trap here as well, and it&#8217;s easier to fall into than the retention one. Advocacy counts go up when you ask more often, so a program can look like it&#8217;s improving when what&#8217;s really happening is that the same willing people are being asked again. The number rises and the willingness drops, and nothing in the reporting shows you the second part until somebody stops replying.</span></p><p><span>So the version of the earlier question that applies here is this: how much of this year&#8217;s advocacy came from people you hadn&#8217;t already asked more than once? If most of it did, something is working. If it&#8217;s a small group being asked repeatedly, you&#8217;re spending down a handful of relationships, and the count won&#8217;t tell you when they run out.</span></p><h3><span>Try this</span></h3><p><span>Pick one of the four: adoption, expansion, retention, or advocacy. Write a single sentence naming the behavior you think matters for the one you picked, where you&#8217;d see that behavior happening, which outcome it plausibly influences, and who owns the next step. Then go and find out whether your systems can show you that behavior at all, because in a lot of companies that&#8217;s the actual blocker, and it&#8217;s better to discover it this week than in the middle of planning. If the measurement side is where you tend to get stuck, </span><a href="https://www.thecommunitycode.com/p/why-nobody-cares-about-your-community"><span>Why Nobody Cares About Your Community Engagement Metrics (and What to Do Instead)</span></a><span> goes further into putting this in terms an executive will engage with.</span></p><h3><span>Decoded Takeaways</span></h3><p><span>Most people who work in or around community accept that it contributes to adoption, expansion, retention, and advocacy. That belief is reasonable and it&#8217;s also where the conversation usually stops, which is why the claim tends to fall apart the moment somebody outside community asks a second question about it. &#8220;Community improves retention&#8221; doesn&#8217;t say which customers, doing what, or leading to what, and it doesn&#8217;t give another team anything to act on.</span></p><p><span>The more useful version separates out the different things happening underneath the word engagement. Adoption runs on peer examples that do something documentation can&#8217;t. Expansion happens both when a team goes further with what it already has and when somebody carries a use case back to a different team. Retention plausibly comes from accumulated relationships and knowledge that raise what leaving actually costs. Advocacy works when an ask lands on somebody who has already received enough value to be willing to be asked. They overlap constantly, and most community teams are asked to influence all four at once, but each works through a different mechanism and shows up in different evidence.</span></p><p><span>The discipline that keeps all of it credible is being straight about what the numbers can&#8217;t show. At Asana, comparing accounts with an ambassador in them against accounts without gave us something real to work with, and it was never proof of cause. The same caution applies to advocacy, where the count goes up whenever you ask more often, so a program can look healthier at the same time as the willingness behind it is being spent down. Saying that out loud tends to make the rest of the argument easier for a skeptical executive to accept.</span></p><h3><span>Related Posts</span></h3><ul><li><p><a href="https://www.thecommunitycode.com/p/community-integrated-gtm"><span>Community Has Impact. It Doesn&#8217;t Carry Across GTM.</span></a></p></li><li><p><a href="https://www.thecommunitycode.com/p/why-nobody-cares-about-your-community"><span>Why Nobody Cares About Your Community Engagement Metrics (and What to Do Instead)</span></a></p></li><li><p><a href="https://www.thecommunitycode.com/p/why-community-and-customer-education"><span>Why Community and Customer Education Need Each Other</span></a></p></li></ul><h3><span>From our Partner</span></h3><p><span>If you&#8217;ve been meaning to get hands-on with the AI side of GTM, GTM Engineer School&#8217;s fifth cohort starts 28 September.</span></p><p><span>It runs eight weeks, live. The first four are spent working in Clay, Octave, Sumble and Swan alongside the teams who built them. The back half is a capstone on whatever stack you actually run, finishing with demo days in front of hiring managers.</span></p><p><span>It&#8217;s $1,850, and every seat comes with $3,500 in platform credits for the tools. Enrollment closes 14 September.</span></p><p><span>Learn more at </span><a href="http://gtm-engineer-school.com"><span>gtm-engineer-school.com</span></a><span>.</span></p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/what-does-community-do-after-the-sale?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/what-does-community-do-after-the-sale?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.thecommunitycode.com/p/what-does-community-do-after-the-sale?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div>]]></content:encoded></item><item><title><![CDATA[Who Runs Your Community After You've Designed It?]]></title><description><![CDATA[Designing the right community formats and structural layers is only half the job. Someone still has to run them.]]></description><link>https://www.thecommunitycode.com/p/who-runs-your-community-after-youve</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/who-runs-your-community-after-youve</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 18 Aug 2026 15:30:20 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!t-Mn!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!t-Mn!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!t-Mn!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!t-Mn!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!t-Mn!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!t-Mn!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!t-Mn!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png" width="349" height="349" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/e799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:349,&quot;bytes&quot;:123699,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/209702702?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!t-Mn!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!t-Mn!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!t-Mn!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!t-Mn!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe799bb75-d1b0-40ec-b39f-9f5252c7694f_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><span>A community manager I worked with years ago used to keep her phone on the nightstand, not because anyone required it, but because a new post could show up at eleven at night and she genuinely believed she was the one who had to answer it. She wasn&#8217;t wrong that someone needed to respond eventually. She was wrong about who that someone had to be. It took a bad month, not a bad year, before that assumption caught up with her.</span></p><p><span>That assumption is more common than it should be, and it usually isn&#8217;t stated out loud. A team designs a thoughtful set of formats and layers, gets the structure right on paper, and then assumes, without ever really deciding to, that the same one or two people who built it will also be the ones running every part of it forever.</span></p><p><span>The architecture scales. The staffing plan under it doesn&#8217;t, and that gap is where good programs start to buckle.</span></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h4><span>Deputize, don&#8217;t just delegate</span></h4><p><span>The cheapest way to scale the operating side rarely means more headcount. Most of the time, it means handing pieces of real ownership to the members who are already doing the work informally: answering questions before staff gets to them, welcoming newcomers unprompted, keeping a channel useful on their own time without anyone asking them to.</span></p><p><span>Most of those people don&#8217;t especially want a title. What they want is a trade that feels fair: some combination of earlier access, a direct line to the team, recognition that&#8217;s visible to their peers, or a genuine say in how their layer of the community runs. Offer that trade explicitly, and you turn a volunteer instinct into a role with real accountability attached, instead of hoping the goodwill holds up indefinitely on its own.</span></p><p><span>This only works if the ownership is real.</span></p><p><span>A community advisory badge that comes with no actual authority is a participation trophy, and members notice the difference immediately. Give a deputized member something to actually decide, whether that&#8217;s who gets welcomed into their specific layer, what the recurring format for their group looks like, or which questions get escalated, and the trade holds. Skip that part and dress it up as a title instead, and you&#8217;ve just created an unpaid role with extra steps.</span></p><h4><span>Not every container needs the same rules</span></h4><p><span>The second piece of the operating model is deciding what each format is actually for before you decide how to moderate it. A blog-style post and a forum thread look similar on a screen and behave completely differently once people start responding.</span></p><p><span>A broadcast piece, something meant to be read, is a different kind of container than a discussion piece, something meant to be argued with. Treat them the same, and an announcement about a hard product decision turns into an unmoderated debate in the comments, while a genuine discussion thread gets flattened into something that reads like an official statement because nobody feels safe disagreeing there.</span></p><p><span>Splitting content by purpose rather than by topic fixes more of this than people expect. Read-this content gets a container built for clarity and a lighter moderation touch, because the goal is comprehension, not debate. Discuss-this content gets a container built for disagreement, with moderation calibrated for tone rather than dissent, because the goal is genuinely working through something together. That split is really a decision about which conversations you&#8217;re actually inviting. Get it wrong, and the container shapes the conversation more than the topic does.</span></p><h4><span>The restraint nobody teaches</span></h4><p><span>The last piece is the hardest one to sell to a team that prides itself on responsiveness. Sometimes the right call is to wait.</span></p><p><span>The instinct to answer every new post within minutes feels like good service, and in the first weeks of a community it often is. Past that point, it starts working against you. If staff always gets there first, members stop bothering to answer each other, because why would they, when the &#8220;real&#8221; answer is coming from the team anyway. Peer-to-peer discussion never gets the chance to become a habit, and the community turns into a support queue with a nicer name, without anyone ever deciding that&#8217;s what it should be.</span></p><p><span>Holding back for a day, sometimes two, on a post that isn&#8217;t urgent gives other members room to try answering first. Some of those answers will be wrong or incomplete, and that&#8217;s fine. A staff member can still step in afterward to correct or add context. What matters is that the first attempt came from a peer, because that&#8217;s the moment a community starts teaching itself to function without staff in the room. It&#8217;s uncomfortable to practice. From the outside it can look like inaction. From the inside, it&#8217;s one of the more deliberate calls a community operator makes.</span></p><p><span>Deputizing members, splitting containers by purpose, and building in restraint don&#8217;t take a bigger team or a new platform to pull off. They take a decision, though: that the architecture built last month isn&#8217;t finished just because the formats and layers exist. Somebody still has to decide who runs each part, and whether that person is going to be you, forever, or someone you&#8217;ve actually trusted with a piece of it.</span></p><h4><span>Decoded Takeaways</span></h4><p><span>A well-designed set of community formats and layers still fails if one person is expected to personally staff all of it. Fixing that rarely takes more headcount. It takes a real operating model, built on three decisions: hand actual ownership, not just recognition, to the members already doing the work informally; split content into broadcast and discussion containers, with moderation calibrated to each one&#8217;s real purpose; and build in deliberate restraint so members get the chance to answer each other before staff steps in.</span></p><p><span>Deputizing only works if the ownership is genuine. A badge with no real authority is a participation trophy, and members can tell the difference. The blog-versus-forum split is really a decision about which conversations a container is actually inviting, and mismatching that decision is what turns announcements into arguments and discussions into statements. Restraint is the least intuitive of the three. Holding back can look like inaction from the outside. From the inside, it&#8217;s one of the more deliberate calls that teaches a community to function without staff in the room.</span></p><p><span>Design gets a program most of the way there. Who runs it, and how much room they&#8217;re given to run it, is what determines whether the design survives contact with an actual community.</span></p><h3><span>Related Posts</span></h3><ul><li><p><a href="https://www.thecommunitycode.com/p/why-community-teams-lack-decision"><span>Why Community Teams Lack Decision-Making Power</span></a></p></li><li><p><a href="https://www.thecommunitycode.com/p/community-signal-has-to-reach-the-business"><span>Community Signal Has to Reach the Business</span></a></p></li><li><p><a href="https://www.thecommunitycode.com/p/vera-devera-on-building-community"><span>Community Codebreakers: Vera DeVera on Building Community as an External Team</span></a></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div></li></ul>]]></content:encoded></item><item><title><![CDATA[Why One Community Format Will Never Reach Everyone]]></title><description><![CDATA[Most programs default to one format and one audience, then wonder why participation stays shallow.]]></description><link>https://www.thecommunitycode.com/p/why-one-community-format-will-never</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/why-one-community-format-will-never</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 04 Aug 2026 15:30:48 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!fZWZ!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!fZWZ!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!fZWZ!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!fZWZ!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!fZWZ!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!fZWZ!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!fZWZ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png" width="348" height="348" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:348,&quot;bytes&quot;:192748,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/209701861?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!fZWZ!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!fZWZ!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!fZWZ!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!fZWZ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6e37fd6e-5f0b-45b8-936e-f2f5843d52d6_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><span>A few months into a new community launch, I&#8217;ve watched the same meeting play out more than once. The team pulls up the dashboard, and the numbers are underwhelming. A few hundred members joined in the first weeks, but only a small slice ever posted anything. Most people signed up, looked around, and never came back to write a word. Someone on the team eventually says the quiet part out loud: maybe community just isn&#8217;t for us.</span></p><p><span>That&#8217;s usually the wrong conclusion, and it comes from a design mistake that&#8217;s easy to miss because it happens by default. Somebody needed to stand up a community fast, so they spun up a forum or a Discord server, invited everyone who might plausibly care, and called it done. The container got built before anyone asked what different kinds of people in that audience actually wanted to do there.</span></p><p><span>A forum is not a community. It&#8217;s one format inside a community, and it happens to reward a specific kind of person: someone comfortable writing in public, replying to strangers, and putting their name next to an opinion. That&#8217;s a real slice of any audience. It is almost never the majority.</span></p><p><span>Everyone else is still there. They&#8217;re reading threads without replying, forwarding a good post to a coworker, showing up to a live session without saying a word in the chat, or skimming a recap email on their phone between meetings. None of that shows up in a post count. On a dashboard built around one format, it looks like absence. It&#8217;s actually just a different, unaccounted-for kind of participation.</span></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3><span>The buffet, not the entr&#233;e</span></h3><p><span>The fix isn&#8217;t a better forum. It&#8217;s treating the community like a buffet with a few different stations, not a single dish everyone is supposed to eat the same way. In practice, that means offering more than one format on purpose, and treating each one as a legitimate way to belong rather than a lesser substitute for &#8220;real&#8221; participation:</span></p><ul><li><p><span>An async, written space for people who think out loud by typing.</span></p></li><li><p><span>A live format, whether that&#8217;s an event, an office hour, or a working session, for people who need conversation to process an idea.</span></p></li><li><p><span>A structured cohort or program for people who want a defined start and end, not an open-ended stream to keep up with.</span></p></li><li><p><span>A curated digest that surfaces the best of the other three for people who will never post but will absolutely read.</span></p></li></ul><p><span>None of these are optional add-ons layered onto &#8220;the real community.&#8221; They&#8217;re parallel front doors. A member who only ever opens the digest is participating just as much as the person posting three times a week. Treating them differently is how programs end up serving ten percent of their audience while quietly assuming the other ninety percent weren&#8217;t that interested to begin with.</span></p><h3><span>Format solves one problem. Layers solve the other.</span></h3><p><span>Format variety answers how people want to engage. It doesn&#8217;t answer who each format is actually for, and that&#8217;s the second design decision most programs skip.</span></p><p><span>A broad, welcoming layer works well for onboarding, general announcements, and cross-cutting conversation. It&#8217;s the front door, and it should stay easy to enter. The mistake is stopping there and assuming one flat layer can also serve a specialist who&#8217;s been doing this work for a decade, a first-time member who doesn&#8217;t know the vocabulary yet, and a customer whose use case looks nothing like the median member&#8217;s, all at the same time and in the same thread.</span></p><p><span>Those people need narrower layers underneath the broad one, where the conversation gets specific enough to actually be useful. A group built around revenue operations leaders and a group built around customer success managers can both live under the same broad umbrella and still need almost none of the same content, because the problems those two groups solve day to day barely overlap.</span></p><p><span>Skip the narrower layer, and the broad community either stays generic enough to be safe for everyone, which makes it useful to no one in particular, or it drifts toward whichever segment shows up loudest, which quietly tells everyone else the community wasn&#8217;t built for them. I&#8217;ve seen both versions, and they fail for the same underlying reason. Nobody decided on purpose who each part of the community was for.</span></p><h3><span>Where this goes wrong in the other direction</span></h3><p><span>The overcorrection is just as common. A team reads something like this, gets excited, and tries to stand up five formats and eight persona groups in the same quarter. Six weeks later, nothing has an owner, three of the channels have gone quiet, and the program looks worse than the single flat forum it replaced, because now members can&#8217;t even tell which of the five places is supposed to be active.</span></p><p><span>The move that actually works is smaller and slower. Pick the one format your loudest members are already improvising around anyway, whether that&#8217;s a live call people keep asking for or a side channel that&#8217;s already forming, and make it official. Pick the one segment whose needs are furthest from the median member, and give them a narrower layer before anyone else. Everything else can wait.</span></p><h3><span>What this actually costs to build</span></h3><p><span>None of this requires standing up five separate platforms on day one. It requires a decision, made early and revisited occasionally, about which formats and which layers you&#8217;re going to support and why, instead of defaulting to whatever tool was easiest to set up on a Tuesday afternoon.</span></p><p><span>A useful starting question: for the three or four segments who matter most to the business, what does each one actually need that a single flat forum can&#8217;t give them? Sometimes the honest answer is a monthly call. Sometimes it&#8217;s a smaller private channel. Sometimes it&#8217;s just a different subject line on the same digest, written for their specific role. The point isn&#8217;t more infrastructure. It&#8217;s fewer wrong assumptions about who the one format you already built was ever supposed to serve.</span></p><p><span>The teams that get this right don&#8217;t necessarily have bigger community budgets. They&#8217;ve just stopped measuring the whole audience by the behavior of the loudest ten percent, and started asking what the other ninety percent actually came for.</span></p><h3><span>Decoded Takeaways</span></h3><p><span>Community participation looks lower than it is when a program only has one format for members to show up in. Most audiences split between people who process out loud in writing, people who need live conversation, people who want a structured program with a clear start and end, and people who will only ever read a good recap. All four are real participation. Treating the loudest, most public format as the only legitimate one is what makes the other three-quarters of an audience look disengaged when they&#8217;re actually just engaging differently.</span></p><p><span>Format variety solves how people want to show up. It doesn&#8217;t solve who each format is for, which is a separate design decision. A broad layer keeps the front door open and easy to enter. Narrower, persona-based layers underneath it are what make the community specific enough to be genuinely useful to the segments that matter most, rather than generic enough to be safely irrelevant to all of them.</span></p><p><span>Neither move requires a bigger platform budget or building everything at once. It requires deciding, deliberately and gradually, which formats and which layers the community is built to support, instead of defaulting to whatever was fastest to set up. The programs that hold up over time aren&#8217;t the ones with the most features. They&#8217;re the ones where somebody actually made that decision on purpose.</span></p><h3><span>Related Posts</span></h3><ul><li><p><a href="https://www.thecommunitycode.com/p/flattening-your-community-is-a-gtm"><span>Flattening Your Community Is a GTM Mistake. K-Pop Shows Why.</span></a></p></li><li><p><a href="https://www.thecommunitycode.com/p/person-vs-persona-resetting-gtm-strategy"><span>Person vs Persona: Resetting GTM Strategy by Focusing on Real People</span></a></p></li><li><p><a href="https://www.thecommunitycode.com/p/the-gtm-problem-behind-the-community"><span>Where Community Breaks Down Inside GTM</span></a></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div></li></ul>]]></content:encoded></item><item><title><![CDATA[Community Signal Has to Reach the Business]]></title><description><![CDATA[Community teams often see valuable customer signal before the rest of the business does. But signal only becomes business value when the company has a way to route, interpret, and act on it.]]></description><link>https://www.thecommunitycode.com/p/community-signal-has-to-reach-the-business</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/community-signal-has-to-reach-the-business</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 21 Jul 2026 15:31:28 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!hD4n!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!hD4n!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!hD4n!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!hD4n!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!hD4n!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!hD4n!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!hD4n!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png" width="350" height="350" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/e35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:350,&quot;bytes&quot;:80188,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/207683964?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!hD4n!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!hD4n!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!hD4n!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!hD4n!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fe35474a9-c1e3-450f-bb4f-d1bb6568f3f0_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><span>A community team sees the same customer issue show up a few times in a short period. The first time, it feels anecdotal. The second time, it starts to look like a pattern. By the third time, someone on the team knows it&#8217;s probably worth sharing, so they pull a few examples, write up the context, and include it in the next recap.</span></p><p><span>From the community team&#8217;s side, the value seems obvious. Customers are saying something important, and they&#8217;re often saying it in their own language, with more detail than they&#8217;d provide in a survey response or a support ticket. They&#8217;re explaining what they&#8217;re trying to do, where they&#8217;re getting stuck, what they&#8217;ve tried already, and what advice from other customers actually helped.</span></p><p><span>And then, very often, the signal goes nowhere useful.</span></p><p><span>That&#8217;s one of the more frustrating parts of community work. Community teams are often close enough to hear what customers are actually saying and far enough from the decision-making system that they can&#8217;t reliably influence what happens next. They can surface the pattern. They can explain the context. They can send the recap. After that, the signal enters the company and starts getting translated by whichever function picks it up first.</span></p><p><span>Marketing may hear a positioning issue. Sales may hear an objection. Customer Success may hear adoption risk. Product may hear a feature request, or feature noise, depending on the week and who&#8217;s reading the recap. Leadership may hear something strategic, or may hear another request from a team that already seems to have a lot of opinions.</span></p><p><span>Everyone can be acting in good faith and still turn the same customer signal into different work.</span></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3><span>The recap is not the operating model</span></h3><p><span>A lot of community teams have been trained to believe that if they can tell a better story about their impact, the business will understand the value of community. There&#8217;s some truth to that. Community leaders do need to explain the work in business terms, not just participation terms, and a thoughtful recap is usually better than a spreadsheet full of posts, likes, and event attendance.</span></p><p><span>But better recaps only get you so far. At some point, the issue isn&#8217;t that the community team failed to explain the insight clearly enough. The issue is that the company doesn&#8217;t have a reliable way to route, interpret, and act on what the community is seeing.</span></p><p><span>That&#8217;s where a lot of community insight quietly dies. It doesn&#8217;t usually die because someone hates customers or because the business is trying to ignore reality. It dies because the insight has nowhere specific to go, so it ends up in a recap, a deck, a Slack thread, or a meeting where everyone nods and says some version of &#8220;that&#8217;s really interesting.&#8221;</span></p><p><span>&#8220;Interesting&#8221; is often where signal goes to retire.</span></p><p><span>A useful operating model has to answer more annoying questions. Who needs to see this? What decision could it change? Is this a Sales issue, a Product issue, a CS issue, a Marketing issue, or some miserable little blend of all of them? Who owns the next step? How will we know whether anything improved?</span></p><p><span>Those questions are less satisfying than a beautiful dashboard, but they&#8217;re usually the difference between community signal being admired and community signal being used.</span></p><h3><span>The same signal becomes different work inside each function</span></h3><p><span>One of the reasons community signal is hard to use is that it doesn&#8217;t belong neatly to one team. That&#8217;s part of what makes it valuable, and also part of what makes it annoying. A single customer conversation can contain messaging feedback, product confusion, implementation friction, expansion potential, and a support issue, all tangled together like a lovely little GTM knot.</span></p><p><span>I saw this kind of thing constantly at Asana. A customer might come into the community asking how to structure a workflow, use a template, or set up permissions. On the surface, that might look like a product education question. In reality, the person was often trying to solve something bigger: how do I get my team to collaborate differently, how do I make this process stick, how do I convince people to stop working out of fifteen different places, and how do I translate what Asana can do into the way my organization actually works?</span></p><p><span>If that signal only goes to Product, it may become feedback about a feature. If it only goes to Education, it may become a help article or webinar. If it only goes to Customer Success, it may become an adoption risk. None of those responses are necessarily wrong, but each one captures only part of what the customer was showing the company.</span></p><p><span>At Evernote, the signal often had a different texture. People had built deeply personal systems around the product, and when something changed or didn&#8217;t work the way they expected, the reaction wasn&#8217;t only about functionality. It was about trust, habit, memory, and the workflows people had built around the product over years. If you summarized that as &#8220;users are frustrated with change,&#8221; you&#8217;d technically capture something. You&#8217;d also lose most of what mattered.</span></p><p><span>That&#8217;s why community signal needs somewhere better to go than a general recap. The value is rarely just in the topic. The value is in the context around the topic, the pattern behind it, the type of customer saying it, the stage of their journey, the intensity of the reaction, and what other customers say in response.</span></p><h2><span>Community insight needs plumbing</span></h2><p><span>This is where the unglamorous work starts. Community signal becomes business value when there&#8217;s plumbing behind it: data connections, recurring rituals, clear ownership, shared definitions, and decision paths that make it easier for the right teams to act on what customers are saying.</span></p><p><span>None of that sounds especially exciting, which is probably why it gets underbuilt. It&#8217;s much more fun to talk about community as a source of belonging, advocacy, engagement, or customer love. All of that matters. But if the business can&#8217;t connect what happens in community to the systems where decisions get made, the insight stays trapped in the place where it was created.</span></p><p><span>At Gradual, this is one of the things I&#8217;ve come to appreciate more directly because the platform problem and the operating problem sit right next to each other. Community teams often have useful signal, but if that signal lives in one system while Sales works in the CRM, CS works in its own customer platform, Product works from roadmap inputs, and Marketing works from campaign data, everyone ends up with partial context.</span></p><p><span>That&#8217;s how companies get into the &#8220;chicken wire and gum&#8221; version of community operations. Someone manually exports data. Someone else builds a recap. Someone tags a few people in Slack. A few screenshots get dropped into a meeting. Everyone agrees the signal is useful, and then the actual business process continues as if nothing happened.</span></p><p><span>I don&#8217;t say that to be dismissive. A lot of teams are doing the best they can with the systems they have, and in many companies the community team is already under-resourced, under-leveled, and expected to produce strategic outcomes with operational scraps. But that&#8217;s exactly why the plumbing matters. If the company wants community to inform GTM, it has to create the paths that allow community signal to move.</span></p><h3><span>What good signal movement looks like</span></h3><p><span>The goal is not to turn every community discussion into an executive memo. Please do not do that to your members, or to yourself. Members aren&#8217;t there to become raw material for your next quarterly business review, and treating them that way is one of the fastest ways to make a community feel extractive.</span></p><p><span>The goal is to create enough structure that meaningful patterns don&#8217;t disappear. That usually starts with a few specific signal paths, not a giant cross-functional transformation program with a name, a kickoff deck, and twelve stakeholders who all want to &#8220;circle back.&#8221;</span></p><p><span>For example, if customers are repeatedly asking how to adopt a feature in real workflows, the signal path might connect Community, Education, Product Marketing, and Customer Success. The question isn&#8217;t only whether the feature needs better documentation. It may need customer examples, peer-led sessions, clearer lifecycle messaging, or an implementation playbook that helps CS teams reinforce the behavior after launch.</span></p><p><span>If customers are repeatedly describing the product differently than the company does, the signal path may connect Community, Marketing, Sales, and Product Marketing. The issue may not be that the campaign language is bad. It may be that customers understand the value through a different problem than the one the company thinks it&#8217;s solving.</span></p><p><span>If customers are repeatedly helping each other through the same implementation challenge, the signal path may connect Community, Support, Education, and Product. The company may be seeing ticket deflection, but the more useful insight may be that customers need a better onboarding path, a different product affordance, or more examples from people who have already made the change successfully.</span></p><p><span>The pattern in all of these examples is that community is not treated as the owner of the entire problem. That would be absurd, although sadly not unprecedented. Community is treated as one of the systems that helps the business understand what customers are trying to do, where they&#8217;re getting stuck, and what kind of support would actually help.</span></p><h3><span>Start with one signal path</span></h3><p><span>If you&#8217;re trying to make community signal more useful inside the business, I wouldn&#8217;t start by building a massive reporting model. That may come later, especially if you need stronger attribution or executive reporting, but starting there can turn the work into a data architecture project before anyone has agreed what decisions the data should improve.</span></p><p><span>I&#8217;d start with one recurring signal and one decision path.</span></p><p><span>Pick a pattern the community team is already seeing. Maybe it&#8217;s a recurring product launch question. Maybe it&#8217;s onboarding confusion. Maybe it&#8217;s customers describing a use case that doesn&#8217;t match your messaging. Maybe it&#8217;s power users creating workarounds that Product should understand. Then ask a few basic questions:</span></p><ul><li><p><span>Who else in the business needs to understand this signal?</span></p></li><li><p><span>What decision could this signal influence?</span></p></li><li><p><span>What context needs to travel with the signal so it doesn&#8217;t get flattened?</span></p></li><li><p><span>Where should this show up: a recurring meeting, CRM field, roadmap review, lifecycle planning process, enablement doc, QBR, or something else?</span></p></li><li><p><span>Who owns the follow-up, and how will the community team know what happened?</span></p></li></ul><p><span>That last part matters more than people think. Community teams spend a lot of time sending signal into the company without knowing whether anything changed because of it. Over time, that becomes demoralizing, and it also weakens the operating loop. If the team never learns what happened after the signal moved, they can&#8217;t improve how they identify, package, or route it next time.</span></p><p><span>The simplest version of this can be very lightweight. A monthly customer signal review. A shared doc with structured fields. A recurring section in Product or GTM planning. A CRM note type for community-sourced account context. A closed loop where Product or CS reports back on what happened after a pattern was surfaced.</span></p><p><span>This does not have to start as a giant system. In fact, it probably shouldn&#8217;t. Giant systems have a way of becoming impressive and unusable at the same time, which is quite a trick.</span></p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/community-signal-has-to-reach-the-business?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/community-signal-has-to-reach-the-business?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.thecommunitycode.com/p/community-signal-has-to-reach-the-business?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h3><span>Community has to be part of how the business learns</span></h3><p><span>This is the bigger shift I think companies need to make. Community can&#8217;t just be the place where engagement happens, or where customers help each other, or where the company occasionally looks for quotes, advocates, or launch energy. Those things can all matter, but they don&#8217;t capture the full value of the system.</span></p><p><span>Community is one of the places where customers reveal how they actually understand the company&#8217;s products, promises, and decisions. They show what makes sense, what doesn&#8217;t, what they trust, what they ignore, what they repeat to each other, and what they quietly work around.</span></p><p><span>That kind of signal should affect how the business operates. It should influence product decisions, messaging, customer education, onboarding, sales enablement, lifecycle programs, and executive understanding of the customer. If it doesn&#8217;t, then community may still be valuable to members, but the business is leaving a lot of learning on the table.</span></p><p><span>The frustrating part is that many companies say they want customer insight until the insight becomes inconvenient. Everyone likes customer feedback when it confirms the plan. The harder test is what happens when the community shows something messier: the positioning isn&#8217;t landing, the launch created confusion, the onboarding path assumes too much, or customers are using the product in ways the roadmap doesn&#8217;t fully support.</span></p><p><span>That&#8217;s where community signal needs more than appreciation. It needs a route into decisions.</span></p><h3><span>Decoded Takeaways</span></h3><p><span>Community teams often see valuable customer signal before the rest of the business does, but seeing the signal is not the same thing as using it. If the insight only lives in a recap, a Slack thread, or a meeting where people agree it&#8217;s interesting, it probably won&#8217;t change much.</span></p><p><span>The same customer signal can mean different things to different teams. Marketing may hear language, Sales may hear objections, Product may hear requests, and Customer Success may hear risk. Those interpretations can all be valid, but the business needs a way to preserve the context around the signal so it doesn&#8217;t get narrowed too early.</span></p><p><span>The most useful starting point is usually one recurring signal path. Pick one pattern the community team is already seeing, identify which decision it could influence, route it to the right teams, and close the loop on what happened. Community becomes more valuable to the business when it becomes part of how the company learns, not just a place where customers gather.</span></p><h3><span>Related Posts</span></h3><ul><li><p><a href="https://www.thecommunitycode.com/p/how-signal-gets-distorted"><span>How Signal Gets Distorted</span></a></p></li><li><p><a href="https://www.thecommunitycode.com/p/how-the-same-customer-signal-turns"><span>How the Same Customer Signal Turns Into Different Decisions</span></a></p></li><li><p><a href="https://www.thecommunitycode.com/p/community-integrated-gtm?utm_source=publication-search"><span>Community Has Impact. It Doesn&#8217;t Carry Across GTM.</span></a></p></li></ul><h3><span>Related resources</span></h3><p><span>I recently joined Yukta Kandhari from Packt to discuss AI and community (spoiler alert: it&#8217;s not AI OR community), and how important building customer trust is when information is available everywhere. </span><a href="https://www.linkedin.com/posts/yukta-kandhari-a5386a185_join-us-tomorrow-for-a-conversation-that-activity-7482931721315708928-Be-V?utm_source=share&amp;utm_medium=member_desktop&amp;rcm=ACoAAAAK4RcBxCMeBNqXz8lAPucNicLNZhgNRZc"><span>Check out the full recording of our discussion</span></a><span>.</span></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[When AI Gives Everyone the Same Answer]]></title><description><![CDATA[AI can help GTM teams turn messy customer signal into summaries, briefs, and recommendations. But useful answers still need context, interpretation, and trust - which comes from community.]]></description><link>https://www.thecommunitycode.com/p/when-ai-gives-everyone-the-same-answer</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/when-ai-gives-everyone-the-same-answer</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 07 Jul 2026 16:02:49 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!MwoT!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!MwoT!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!MwoT!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!MwoT!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!MwoT!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!MwoT!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!MwoT!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png" width="350" height="350" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:350,&quot;bytes&quot;:53393,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/205419026?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!MwoT!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!MwoT!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!MwoT!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!MwoT!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F99ea1b72-a7d8-49b4-88d8-ed619bc50d55_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><span>One thing I&#8217;ve been noticing in conversations about AI is how quickly people move from &#8220;can it produce the thing?&#8221; to &#8220;great, now we have the thing.&#8221; I understand why that happens. If you&#8217;ve ever had to turn a pile of call notes, support tickets, survey responses, Slack threads, and half-remembered customer comments into something usable, the appeal is pretty obvious. AI can take a messy input and turn it into a tidy summary. It can find themes. It can draft the recap. It can make the blank page less blank, which isn&#8217;t nothing.</span></p><p><span>I don&#8217;t think this is bad. I use AI, and I&#8217;m interested in what it makes possible. I&#8217;m also not especially nostalgic for the days when every customer insight had to be manually assembled by someone squinting at a spreadsheet at 11:00 p.m. while wondering whether &#8220;miscellaneous feedback&#8221; was a category or a cry for help. There are real gains here, especially for teams that have been doing too much of this work manually for too long.</span></p><p><span>The problem is that a polished output can make the work feel more finished than it actually is. A summary can tell you what themes showed up, but it doesn&#8217;t necessarily tell you what those themes mean. A recommendation can sound reasonable without being especially useful for your specific company, customer base, product maturity, team structure, or timing. And when the original signal has already passed through several layers of interpretation before AI ever touches it, the final output can look useful while still missing the thing that mattered most.</span></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3><span>The answer is usually the beginning of the work</span></h3><p><span>That&#8217;s where I think a lot of GTM teams are going to get themselves into trouble. The issue isn&#8217;t that AI will always be wrong. That would be easier, honestly. If the output were obviously terrible, people would know to ignore it. The harder problem is that a lot of AI-generated output will be basically reasonable. It&#8217;ll sound organized. It&#8217;ll use the right words. It&#8217;ll include the expected steps. It&#8217;ll probably be good enough to drop into a doc, share in a meeting, or turn into the next slide in the deck.</span></p><p><span>And because it looks useful, teams may stop too early.</span></p><p><span>Take a simple example. A company asks an AI tool how to build a community initiative around a product launch. The answer will probably include some version of the usual steps: define the audience, set goals, recruit early advocates, create programming, gather feedback, measure engagement, and connect the work back to business outcomes. That&#8217;s all fine. It&#8217;s also the kind of answer that could apply to almost any company, which means it doesn&#8217;t yet apply to this company.</span></p><p><span>The harder questions are more specific. Is this product launch aimed at existing customers who already trust the company, or a new audience that has no reason to care yet? Is the product asking people to adopt a genuinely new behavior, or is it a better version of something they already understand? Does the community team have enough influence to shape the launch before decisions are made, or are they being asked to create excitement after the strategy has already been locked? Are customers confused, skeptical, excited, tired, or politely saying &#8220;interesting&#8221; while meaning something else entirely?</span></p><p><span>Those are the details that determine whether the answer is useful. They&#8217;re also the details most likely to get flattened when teams optimize too heavily for speed, summarization, and outputs that look more complete than they really are.</span></p><h3><span>Where the plausible answer breaks down</span></h3><p><span>This isn&#8217;t only a community problem. It shows up across GTM because every function has its own way of interpreting customer signal. Marketing hears language. Sales hears objections. Customer Success hears risk. Product hears requests, friction, and sometimes noise, depending on the week and who&#8217;s reading the recap.</span></p><p><span>That&#8217;s normal. Each team has different responsibilities, so of course they listen differently. The problem is that AI can make those translations happen faster without making them better. It can take the same messy signal and turn it into a smoother version of whatever the organization already knows how to process.</span></p><p><span>You can see this in a few common places:</span></p><ul><li><p><span>In customer feedback, AI can summarize hundreds of comments into a few themes. &#8220;Customers want better onboarding&#8221; might be accurate, but it could mean the product is confusing, the docs are weak, implementation is underdeveloped, peer examples are missing, or customers don&#8217;t understand the value they&#8217;re supposed to get. Those are different problems, even if they collapse into the same summary.</span></p></li><li><p><span>In sales, AI can turn community conversations, webinar questions, support tickets, and product usage signals into an account brief. That&#8217;s useful, especially when the alternative is asking someone to spelunk through five systems and somehow emerge with insight. But the brief still needs judgment. Is the customer showing buying intent, trying to solve a peer problem, or giving the company useful context for a longer relationship?</span></p></li><li><p><span>In product, AI can cluster feature requests and complaints. That can help teams see patterns faster, but it doesn&#8217;t answer whether the request is the real need or the workaround customers invented because they didn&#8217;t know what else to ask for. Anyone who&#8217;s been around product feedback for more than twelve minutes has seen this.</span></p></li></ul><p><span>I&#8217;ve seen versions of this throughout my own work. At Asana, community conversations often revealed where customers were trying to understand not just a feature, but a way of working. Someone might ask a tactical question about a workflow, a template, or a permission setting, but the real issue underneath was often broader: how do I get my team to collaborate differently, how do I make this process stick, or how do I translate what Asana can do into the way my organization actually works?</span></p><p><span>A tidy summary might call that &#8220;product education&#8221; or &#8220;workflow guidance.&#8221; That&#8217;s not wrong, exactly. But it misses the more useful point. The customer wasn&#8217;t only asking how to use the tool. They were trying to figure out how to change behavior inside their company. That&#8217;s a different kind of problem, and it requires a different kind of response.</span></p><p><span>At Evernote, the pattern showed up differently. Customers often had deeply personal systems for managing their work and lives, and when something changed, the reaction wasn&#8217;t only about a feature. It was about trust, habit, memory, and a workflow they had built around the product over years. If you flattened that into &#8220;customers dislike change,&#8221; you technically captured something. You also lost most of what mattered.</span></p><p><span>And now at Gradual, I see the operating version of this problem all the time. Community teams are sitting on useful signal, but that signal only becomes business value if it moves somewhere. If it stays trapped in the platform, or gets summarized into a vague monthly recap, it&#8217;s not going to help Sales, Product, Marketing, or Customer Success make better decisions. It has to connect to the systems and conversations where decisions actually happen.</span></p><p><span>This is why I keep coming back to customer signal as an operating problem, not only an information problem. Most companies already have more signal than they can use. They have support tickets, call transcripts, CRM notes, community discussions, survey data, product analytics, win-loss notes, social comments, event questions, advisory board feedback, and the occasional Slack thread where one person says the thing everyone should probably be paying attention to.</span></p><p><span>The issue is how that signal moves through the company.</span></p><p><span>It gets summarized too early. It gets stripped of context. It gets translated into whatever each function already cares about. None of those translations are inherently wrong, but each one narrows the signal in a different way. AI can make that narrowing faster, more polished, and harder to notice.</span></p><p><span>Very exciting. Everyone gets a prettier version of the same problem.</span></p><h3><span>Community preserves some of what summaries lose</span></h3><p><span>That&#8217;s where community becomes important in a way that&#8217;s easy to underestimate. Community isn&#8217;t useful here because it gives the company one more place to distribute AI-generated content. Please, no. We have enough channels distributing vaguely useful answers already.</span></p><p><span>Community matters because it gives people a place to make sense of the answer together. Members can test it against lived experience, challenge what sounds too generic, add the caveats that actually matter, and surface the context that would otherwise stay hidden.</span></p><p><span>When someone asks a question in a community, the answer they receive is often only part of the value. The surrounding conversation is usually just as useful. One person gives the official answer. Another describes the workaround. Someone else explains why the answer worked for them, but only after they changed the process internally. Another person asks the question underneath the question. Occasionally someone says, gently or not, &#8220;I wouldn&#8217;t start there.&#8221;</span></p><p><span>That&#8217;s hard to capture in a neat executive summary. It&#8217;s also exactly what makes the exchange useful.</span></p><p><span>A healthy community shows when customers are asking the same question in five different ways. It reveals when the official positioning doesn&#8217;t match how people actually describe the problem. It helps teams understand whether a feature request is really about product capability, confidence, workflow change, peer validation, or something else entirely. None of that means every community thread should become an executive memo. Members aren&#8217;t there to become raw material for your next GTM strategy doc, which should not need saying, but here we are.</span></p><p><span>The value comes from stewarding the system well enough that customers are willing to be honest with each other. If the company is paying attention, that honesty becomes a source of context the rest of the business usually struggles to preserve.</span></p><h3><span>The interpretation work has to go somewhere</span></h3><p><span>This matters more as AI becomes embedded in GTM work. The more teams use AI to produce summaries, recommendations, briefs, enablement content, and playbooks, the more they need ways to test whether those outputs are actually useful.</span></p><p><span>I&#8217;d be less interested in asking how AI can help a company create more community content. That question might matter sometimes, but it&#8217;s not the most useful starting point. I&#8217;d rather ask whether customers are better able to understand, trust, and apply what the company is putting into the world.</span></p><p><span>A few questions make this more concrete:</span></p><ul><li><p><span>Where do customers go when the official answer is technically correct, but still not specific enough to help them act?</span></p></li><li><p><span>What do customers understand after talking with peers that they didn&#8217;t understand from our documentation, onboarding, campaigns, or sales materials?</span></p></li><li><p><span>Which customer conversations are helping the business make better decisions, and where does that learning actually go?</span></p></li><li><p><span>Where are we preserving nuance from community interactions, and where are we flattening everything into themes that are easier to present than act on?</span></p></li><li><p><span>What decisions have changed because of what customers helped each other understand?</span></p></li></ul><p><span>That last question is often where the useful work starts. It moves community away from being a place where engagement happens and toward being part of how the business learns.</span></p><p><span>This is also where the conversation gets uncomfortable. If community is part of interpretation, then the community team can&#8217;t be treated as a peripheral engagement function. The work has to connect to customer education, product learning, lifecycle programs, sales enablement, support, and executive decision-making. Otherwise the signal stays in the community, people admire it, and nothing changes.</span></p><p><span>AI won&#8217;t fix that. It may even make it easier to ignore, because the summary will look productive.</span></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3><span>What I&#8217;d watch for next</span></h3><p><span>The companies that use community well in this next phase won&#8217;t be the ones that simply add AI to the community calendar and declare themselves modern. They&#8217;ll use AI where it actually helps: synthesis, routing, drafting, pattern recognition, and reducing some of the manual work that makes community and GTM operations more ridiculous than they need to be.</span></p><p><span>But they&#8217;ll also be careful about what AI can&#8217;t do by itself. It can produce an answer, but it doesn&#8217;t know whether customers trust the answer. It can cluster feedback, but it doesn&#8217;t automatically understand the emotional stakes underneath it. It can draft a playbook, but it doesn&#8217;t know which parts will break inside a specific organization with specific people, incentives, history, and politics.</span></p><p><span>Community is one of the few systems that can help with that, assuming the business treats it like a system and not a content bin. It gives customers a place to interpret information together, and it gives the company a way to see how that interpretation actually happens.</span></p><p><span>That&#8217;s the part I&#8217;d pay attention to. As AI gives everyone more answers, the advantage may come from understanding which answers mean something, which ones don&#8217;t, and what customers need from each other before they&#8217;re ready to act.</span></p><p><span>I&#8217;d love to hear where you&#8217;re seeing this show up. Where does AI-generated synthesis help your team move faster, and where do you still need human context, customer interpretation, or peer discussion before the output becomes useful?</span></p><h3><span>Decoded Takeaways</span></h3><p><span>AI can help GTM teams produce more organized summaries, faster briefs, better first drafts, and more neatly packaged recommendations. That&#8217;s useful, especially for teams that have been manually stitching customer signal together across too many disconnected systems. The risk is that polished outputs can make teams feel like the work is done before they&#8217;ve actually understood what the output means.</span></p><p><span>Community becomes more important in that environment because it preserves context that summaries often lose. The useful signal frequently shows up around the answer: the caveats, workarounds, questions, disagreements, examples, and peer interpretation that make advice usable in the real world.</span></p><p><span>For GTM teams, the practical question isn&#8217;t whether AI helps produce more. It probably does. The better question is whether customers are making better decisions because of what the company puts into the world. Community can help answer that, but only when the business treats it as part of how it learns, not just another channel for distributing content.</span></p><h3><span>Related Posts</span></h3><ul><li><p><a href="https://www.thecommunitycode.com/p/ai-without-community-doesnt-work"><span>AI Without Community Doesn&#8217;t Work in GTM</span></a></p></li><li><p><a href="https://www.thecommunitycode.com/p/even-ai-agents-end-up-building-communities"><span>Even AI Agents End Up Building Communities</span></a></p></li><li><p><a href="https://www.thecommunitycode.com/p/the-efficiency-trap-in-ai-powered"><span>The Efficiency Trap in AI-Powered Customer Experience</span></a></p></li></ul><h3><span>Resources and upcoming events</span></h3><p><span>I recently joined Todd Nilson from </span><a href="https://www.clocktoweradvisors.com"><span>Clocktower Advisors</span></a><span> on the &#8220;</span><a href="https://www.youtube.com/watch?v=KH7fXiW54m8"><span>Talk About Your Community</span></a><span>&#8221; livestream to talk about community, GTM, and how organizations can think more clearly about the role community plays in growth and customer trust. </span><a href="https://www.youtube.com/watch?v=KH7fXiW54m8"><span>Check it out here</span></a><span>.</span></p><p><a href="https://www.packtpub.com"><span>Packt&#8217;s</span></a><span> Yukta Kandhari is hosting me on July 15th for a webinar about community, AI, and customer trust. If you&#8217;re thinking through how AI changes the way customers learn, evaluate information, and engage with companies, this will be a useful conversation. </span><a href="https://luma.com/ee09d01v"><span>RSVP here</span></a><span>.</span></p><p><span>And a small book note: </span><em><span>The Community Code</span></em><span> was just featured in the </span><a href="https://magazine.sfsu.edu"><span>SFSU Alumni Magazine</span></a><span>, which was a very nice full-circle moment as an SFSU alum.</span></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div>]]></content:encoded></item><item><title><![CDATA[Community Codebreakers: Vera DeVera on Building Community as an External Team]]></title><description><![CDATA[Some of the people doing the most consequential work inside large companies still don&#8217;t have a real team around them.]]></description><link>https://www.thecommunitycode.com/p/vera-devera-on-building-community</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/vera-devera-on-building-community</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Mon, 29 Jun 2026 16:01:07 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/160611653/66441eb7119f3589bde64069337b535c.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Some people work inside very large companies and still have almost nobody around them who understands their job.</p><p>That came up early in my conversation with <a href="https://www.linkedin.com/in/vdevera/">Vera DeVera</a>, who led community at Watershed. Many of the sustainability professionals she worked with sit inside enterprise companies with tens of thousands of employees, yet the actual sustainability team may consist of one to five people.</p><p>They&#8217;re expected to influence complex decisions across finance, operations, legal, procurement, and leadership. In many cases, the role itself is still new. There may not be an established playbook, a large internal team, or a long line of experienced peers sitting nearby.</p><p>The company is large. The work can still feel very solitary.</p><p>Vera has spent much of her career building communities for people in that kind of position. Before Watershed, she built programs at early-stage companies where emerging professional roles were trying to establish themselves at the same time as the companies serving them.</p><p>What she&#8217;s building now gives sustainability leaders something they often can&#8217;t get inside their own organizations: a team of peers who understand the work.</p><h2>People arrive through different doors</h2><p>Vera&#8217;s own path into sustainability wasn&#8217;t traditional.</p><p>She came from community, not environmental science. What drew her to Watershed was the chance to bring her professional experience into a company whose mission aligned with her personal values.</p><p>The people in the community have similarly varied backgrounds.</p><p>Some studied environmental science and built their careers around the field. Others volunteered to lead a workplace recycling or sustainability effort, became more involved over time, and eventually helped create a formal role inside the company.</p><p>That range matters because emerging functions rarely develop in a straight line.</p><p>People are learning the technical work while also figuring out how to explain it internally, secure resources, and influence leaders who may not understand why it matters yet. They&#8217;re often developing the role at the same time they&#8217;re performing it.</p><p>Community becomes useful because it gives them access to people at different points along the same path.</p><p>Someone who has just inherited sustainability responsibilities can learn from someone who built a program two years earlier. A more experienced leader can compare notes with peers facing the same regulatory or organizational pressure. The expertise doesn&#8217;t flow in only one direction.</p><h2>The four C&#8217;s</h2><p>Vera describes community through four C&#8217;s:</p><ul><li><p>Connection</p></li><li><p>Collaboration</p></li><li><p>Commiseration</p></li><li><p>Celebration</p></li></ul><p>The inclusion of commiseration is important.</p><p>Professional communities often emphasize expertise, best practices, and success stories. Those things are useful, but people also need somewhere to say that the work isn&#8217;t going well.</p><p>That can be difficult inside a company.</p><p>A sustainability leader may be trying to build support for a new initiative, complete a complicated reporting process, or secure headcount. Admitting uncertainty internally can carry political or professional risk, especially when the function is already fighting for credibility.</p><p>A trusted peer community gives people somewhere to be more honest.</p><p>They can say, &#8220;I&#8217;m stuck,&#8221; or &#8220;I tried this and it failed,&#8221; and hear from someone who has dealt with something similar. The conversation can remain private enough to be useful and specific enough to lead to action.</p><p>That kind of safety has practical value. People surface problems earlier, learn from one another&#8217;s mistakes, and gain confidence before returning to the internal conversations where they still have to make the case.</p><h2>Community as an external team</h2><p>Vera described the community as something close to an extended team.</p><p>That&#8217;s more than a nice metaphor.</p><p>She has watched people meet through dinners and events, become accountability partners, and continue helping each other across companies and cities. Some members now have someone they can call when they&#8217;re facing a problem their internal colleagues don&#8217;t fully understand.</p><p>That relationship changes the experience of the role.</p><p>The member still has to do the work inside their own company. Community doesn&#8217;t remove the organizational constraints, and it doesn&#8217;t give them formal authority. What it can provide is a place to test ideas, compare experience, and avoid starting from scratch every time.</p><p>For emerging functions, that&#8217;s a substantial advantage.</p><p>The community also helps members become more influential inside their organizations. They can bring back examples, language, approaches, and evidence from peers who have faced similar resistance. The community gives them a broader base of practical knowledge than their internal team alone could provide.</p><h2>Listening before building</h2><p>When Vera joined Watershed, the company had already created the community role. She still didn&#8217;t start with a predetermined program.</p><p>She began with a listening tour.</p><p>Internally, she talked with customer success, product, and other GTM teams that were already close to customers. Externally, she spoke with dozens of customers and asked questions about how they learned, what problems they were facing, how they wanted to connect with peers, and what they could teach others.</p><p>That last question is especially useful.</p><p>Community discovery often focuses on what people need. Vera also looked for what they could contribute.</p><p>She wanted to identify the people who had experience worth sharing, then create the conditions where that experience could help someone else. That approach treats members as participants in the value creation, rather than an audience waiting for the company to deliver everything.</p><p>It also reflects something I wrote about in <em>The Community Code</em>: the company can design and steward the system, but much of the value comes from what members create together.</p><h2>Trust is built through curation</h2><p>Vera&#8217;s work includes a lot of deliberate matchmaking.</p><p>She pays attention to who is struggling with a particular problem, who has recently solved something similar, and who might benefit from being in the same room. Sometimes the most useful outcome from an event isn&#8217;t the content on stage. It&#8217;s the person someone meets over dinner.</p><p>That kind of curation can look informal from the outside. It still requires judgment.</p><p>A good community builder notices patterns, remembers context, and understands enough about the members to make useful connections. The goal isn&#8217;t to force relationships. It&#8217;s to create enough proximity and relevance for the right conversations to happen.</p><p>This is one area where scale can become misleading.</p><p>A community may have thousands of members, but the value often appears through much smaller interactions. One introduction, one peer conversation, or one honest admission can change how someone approaches the work.</p><p>The numbers matter. They don&#8217;t explain the whole experience.</p><h2>The business value follows the member value</h2><p>Watershed didn&#8217;t create community only because sustainability leaders needed friends.</p><p>The company also sees community as a growth and retention driver. Customers who are more connected, more confident, and more successful are more likely to stay, advocate, and help others understand the value of the work.</p><p>Those business outcomes are real.</p><p>They depend on the member value coming first.</p><p>A community built primarily to extract advocacy will eventually feel extractive. A community that helps members become better at their jobs creates the conditions for advocacy to develop more naturally.</p><p>Vera&#8217;s approach starts with the work people are trying to do.</p><p>How can they become more capable? How can they feel less isolated? How can they gain more influence in rooms where they may not currently have much power?</p><p>When the community helps answer those questions, the relationship with the company becomes stronger for understandable reasons.</p><h2>What this adds to the broader conversation</h2><p>We spend a lot of time talking about how community creates engagement.</p><p>Vera&#8217;s example is more specific.</p><p>The community is filling an organizational gap.</p><p>It gives people access to peers their employer may not be able to provide. It creates a place for practical honesty that may not exist inside the company. It helps members develop influence in a function that is still establishing its role.</p><p>That&#8217;s a more consequential form of value than keeping people active in a platform.</p><p>It also shows why community can matter most in emerging or under-resourced roles. The need isn&#8217;t simply information. People need examples, language, reassurance, and relationships with others who understand the stakes.</p><p>A content library can help with part of that. A trusted peer usually helps with more.</p><h2>Watch the conversation</h2><p>In the full interview, Vera and I talk about:</p><ul><li><p>How her personal values led her into sustainability community work</p></li><li><p>Why emerging professional roles often need community the most</p></li><li><p>How she conducted internal and customer listening tours</p></li><li><p>The role of peer safety and commiseration</p></li><li><p>How curated relationships turn into accountability and support</p></li><li><p>Why community can drive retention, advocacy, and growth</p></li><li><p>What she has learned building communities from zero to one</p></li></ul><p>The conversation is practical and warm, which is very much Vera&#8217;s style. She has a clear point of view about the business value of community without losing sight of the people doing the work.</p><h2>Decoded Takeaways</h2><p>Community can become an external team for people who don&#8217;t have enough peers, support, or institutional knowledge inside their own companies. That&#8217;s especially valuable in emerging functions where people are still defining the role while trying to perform it.</p><p>Vera&#8217;s approach begins with listening. She looks at what members need, what they can teach, and where trusted relationships could make the work easier or more effective. The company creates the conditions, but members help one another produce much of the actual value.</p><p>The strongest communities also give people somewhere to be honest about what isn&#8217;t working. That kind of safety has practical consequences. Problems surface earlier, members learn from one another&#8217;s experience, and people return to their companies with more confidence and better language for influencing decisions.</p><p>For the business, the value shows up through stronger customer relationships, retention, advocacy, and growth. Those outcomes are more credible when they follow from helping members succeed, rather than treating community as a source of activity or promotion.</p><h2>Timestamps</h2><p>00:00 Introduction and Vera&#8217;s path into community<br>01:40 Vera&#8217;s four C&#8217;s of community<br>03:06 How people arrive in sustainability careers<br>04:50 Why Watershed invested in community<br>06:21 Similarities between emerging legal and sustainability roles<br>07:57 Community as an external team<br>10:43 Vera&#8217;s listening-tour process<br>11:57 Helping members become more influential<br>12:25 Why community needs to feel safe</p><h2>Related posts</h2><ul><li><p><a href="https://open.substack.com/pub/thecommunitycode/p/why-community-teams-lack-decision">Community Without Power</a></p></li><li><p><a href="https://open.substack.com/pub/thecommunitycode/p/the-efficiency-trap-in-ai-powered">The Efficiency Trap</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/community-codebreakers-demario-bell">Community Codebreakers: DeMario Bell on Sequencing B2B Community for Scale</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[Why Community Teams Lack Decision-Making Power]]></title><description><![CDATA[Community teams are often held accountable for results they have very little authority to influence.]]></description><link>https://www.thecommunitycode.com/p/why-community-teams-lack-decision</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/why-community-teams-lack-decision</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 23 Jun 2026 16:00:56 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!aKO5!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!aKO5!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!aKO5!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!aKO5!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!aKO5!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!aKO5!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!aKO5!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png" width="350" height="350" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/cf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:350,&quot;bytes&quot;:148480,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/200992249?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!aKO5!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!aKO5!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!aKO5!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!aKO5!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fcf68d0ac-df46-4504-80f5-0f8cd3f8bb26_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>A community leader gets invited into quarterly planning.</p><p>The company wants community to improve adoption, help with retention, create more advocacy, generate better customer feedback, and support education. By the time the community leader joins the meeting, the plans behind most of those outcomes are already finished.</p><p>Marketing has its campaign calendar. Customer success has set its adoption priorities. Product has committed the roadmap. Education has chosen its content plan. The community leader is asked how the community can help.</p><p>I&#8217;ve seen this pattern in companies at very different stages. People are usually well intentioned. They like the community team, believe the work is valuable, and genuinely want to collaborate.</p><p>The operating model still leaves community responsible for outcomes shaped somewhere else.</p><h2>How the mismatch develops</h2><p>Community usually starts inside one function for a sensible reason.</p><p>Support creates a forum because customers are already helping each other. Marketing builds an advocacy or events program. Customer success launches a peer network to improve adoption. Product creates a place for feedback and expert users.</p><p>The program needs a home, a budget, and an owner. That part makes sense.</p><p>As the program grows, the work starts to spread.</p><p>Members create educational content, answer product questions, refer new customers, explain use cases, identify bugs, test features, lead events, and help other customers navigate organizational problems. Community begins contributing to the work of several teams even though it still reports into one of them.</p><p>That&#8217;s where the mismatch appears.</p><p>The community team is asked to influence horizontal outcomes with vertical authority. It can recommend, persuade, share evidence, and offer access to customers. It often can&#8217;t decide what happens next.</p><p>That distinction matters when the desired result depends on choices the community team doesn&#8217;t control.</p><h2>Adoption is a useful example</h2><p>A company may ask community to improve product adoption.</p><p>That&#8217;s reasonable. Experienced customers can show newer customers what good use looks like. Community events and discussions can help people discover workflows, learn from peers, and see how others solved similar problems.</p><p>Adoption is also shaped by a lot of things outside community:</p><ul><li><p>Whether the product solves the customer&#8217;s actual problem</p></li><li><p>Whether onboarding prepares them to use it</p></li><li><p>Whether their internal champion has enough influence</p></li><li><p>Whether education arrives at the right time</p></li><li><p>Whether customer success understands the real barrier</p></li><li><p>Whether the product experience reinforces the intended behavior</p></li></ul><p>Community can contribute to all of those areas. It doesn&#8217;t own most of them.</p><p>When adoption rises, several teams may point to their influence. When it stalls, community can still be asked why engagement didn&#8217;t translate into more usage.</p><p>Retention creates a similar problem. A strong peer network can deepen a customer&#8217;s relationship with the company and help them succeed. It can&#8217;t fix a product that no longer meets the need, a pricing change that undermines value, or an implementation problem that began before the customer ever joined.</p><p>Community affects the result without controlling the conditions.</p><h2>What I was trying to resolve in the book</h2><p>One of the tensions I kept returning to while writing <em><a href="https://www.amazon.com/dp/B0GQ4NYQ5N/">The Community Code</a></em> was that community creates value across the business while remaining structurally attached to a single team.</p><p>I argued that companies should treat community as part of the GTM system. I still believe that. The harder question is what that requires from the organization.</p><p>It&#8217;s easy to say community should partner with marketing, product, customer success, sales, support, and education. Most experienced community teams already do that. Partnership doesn&#8217;t resolve the power imbalance by itself.</p><p>A community leader can attend cross-functional meetings and still be invited after the important decisions. They can share strong customer evidence and still lose to the metric another team is measured against. They can be accountable for an outcome without having any authority over the workflows creating it.</p><p>This is where the language of collaboration can become misleading. Everyone may be responsive and friendly while the structure leaves community with very little leverage.</p><h2>When community becomes an internal service desk</h2><p>Community teams spend a lot of time translating their value for internal audiences.</p><p>Product wants usable feedback. Marketing wants stories and advocacy. Customer success wants adoption and retention. Support wants deflection. Sales wants references. Executives want measurable business impact.</p><p>None of those requests is unreasonable. The accumulation of them can push community into a service model for the rest of the organization.</p><p>The team finds speakers for events, recruits beta testers, sources customers for case studies, fills reference requests, creates peer groups, and produces recurring reports. Much of that work is useful, and some of it is central to a strong program.</p><p>The risk appears when internal demand starts determining too much of the member experience.</p><p>Customers don&#8217;t join because marketing needs a case study or sales needs a reference. They participate because they expect to learn, contribute, connect, or get something they couldn&#8217;t access as easily on their own.</p><p>Once members begin to feel like a company resource, the program gets weaker. The community team is usually close enough to see that shift. It may not have enough authority to stop it.</p><h2>Authority can be practical</h2><p>Giving community more power doesn&#8217;t require creating a giant centralized organization or handing every customer decision to the community leader.</p><p>Authority can be much narrower.</p><p>It may mean bringing community into lifecycle planning before the campaign is finalized. It may mean requiring product teams to respond to recurring member patterns. It may mean giving community a role in customer education planning or allowing the team to decline requests that would damage member trust.</p><p>Some decisions may belong clearly to the community team:</p><ul><li><p>Which member segments receive access to particular programs</p></li><li><p>What participation standards protect the quality of the space</p></li><li><p>How member contributions are recognized and used</p></li><li><p>Which internal requests fit the purpose of the community</p></li><li><p>When repeated customer patterns require executive attention</p></li></ul><p>These decisions shape whether the community remains credible. Without authority over them, the team can spend an extraordinary amount of energy negotiating for permission to do work it is already expected to own.</p><h2>Measurement helps, but it doesn&#8217;t settle the argument</h2><p>Community leaders are often told that stronger measurement will earn them more influence.</p><p>Better measurement helps. I&#8217;ve used account data, product behavior, business outcomes, qualitative evidence, and program activity to show what community contributes. The assumption that proof automatically changes the operating model is less reliable.</p><p>Data enters an organization that already has priorities, incentives, and power structures. A strong result may earn more budget while leaving decision rights unchanged. Another team may accept the evidence and still prioritize the metric it owns.</p><p>This doesn&#8217;t make measurement pointless. It means the report has to do more than prove value. It has to connect the result to a decision.</p><p>A company may learn that community members adopt more features or renew at a higher rate. Everyone congratulates the team, and onboarding continues to be designed without community input. The evidence showed impact. It didn&#8217;t alter the workflow.</p><h2>Being invited isn&#8217;t the same as being involved</h2><p>I&#8217;ve been in enough planning processes to know that timing tells you a lot.</p><p>A team may ask for community input once the core plan is fixed. At that point, the remaining choices are usually promotional. Can members attend the webinar? Can an ambassador share the launch? Can the community amplify the announcement? Can the team recruit advocates?</p><p>The more consequential questions were answered earlier.</p><p>Did the product reflect the behaviors the community had been observing? Does the education plan match how customers actually learn? Will the launch create confusion inside an existing program? Are the company&#8217;s most credible customers prepared to explain the change?</p><p>Late involvement limits community to distribution. Early involvement gives community a chance to affect design.</p><p>That difference is one of the clearest signals of whether the company sees community as infrastructure or as an audience.</p><h2>The part nobody likes to say out loud</h2><p>Meaningful cross-functional influence usually requires someone else to give up some control.</p><p>A product leader may have to change a roadmap based on patterns that didn&#8217;t come through the formal research process. Marketing may have to adjust a campaign because the language doesn&#8217;t match how customers describe the problem. Customer success may have to change a standardized journey for people participating differently through community.</p><p>Cross-functional work sounds great until it changes someone&#8217;s plan.</p><p>That&#8217;s why many community teams remain advisory. The company benefits from their proximity to customers without allowing that proximity to disrupt established ownership.</p><p>I don&#8217;t think most leaders do this cynically. The existing structure feels easier to manage. Clear functional ownership makes planning, budgeting, and accountability simpler.</p><p>The customer&#8217;s experience is less interested in the org chart.</p><h2>A better operating model starts with decisions</h2><p>The most useful place to begin is with the outcomes community is expected to influence, then trace the decisions behind them.</p><ul><li><p>If community is accountable for adoption, where is it involved in onboarding, education, product discovery, and customer success planning?</p></li><li><p>If it&#8217;s accountable for advocacy, can the team influence the customer experiences that create genuine advocates?</p></li><li><p>If it&#8217;s expected to improve retention, does it participate in conversations about risk, value realization, and product friction?</p></li></ul><p>The gaps become visible quickly. From there, leaders can decide which decisions require community input, which decisions community co-owns, and which decisions belong to the community team.</p><p>That level of clarity is more useful than another promise to collaborate.</p><p>It also makes accountability more honest. A team should be measured against outcomes it has enough influence to shape.</p><h2>The argument I&#8217;m still working through</h2><p>I still believe community should be integrated across GTM. And I&#8217;m increasingly convinced that integration without authority has a ceiling.</p><p>A community team can build strong relationships, gather useful insight, and create value across the customer lifecycle. It can do all of that while remaining peripheral to the company&#8217;s most important decisions.</p><p>At some point, better partnership stops being enough. The organization has to decide whether community is mainly a source of labor and distribution or whether it participates in how customer-facing work is designed.</p><p>You can usually see that choice long before it appears in a strategy deck. It shows up in who is in the room before the plan is finished.</p><h2>Decoded Takeaways</h2><p>Community teams often influence adoption, retention, advocacy, education, support, feedback, and growth while controlling very few of the decisions behind those outcomes. That creates an accountability gap that good collaboration alone doesn&#8217;t resolve.</p><p>The program&#8217;s reporting line may still make sense, but its value often spreads well beyond that function. As community becomes more useful across GTM, the company needs clearer rules about where community provides input, where it shares ownership, and what the team can decide directly.</p><p>Measurement supports that conversation, but evidence doesn&#8217;t automatically change decision rights. Community leaders have to connect results to the workflows that should operate differently. Executives have to decide whether the team&#8217;s proximity to customers will influence planning or remain useful mainly for distribution and execution.</p><p>The practical test is timing. When community enters after the plan is complete, it&#8217;s usually being treated as an audience. When it participates before priorities, experiences, and workflows are fixed, it has a chance to function as infrastructure.</p><h2>Related posts</h2><ul><li><p><a href="https://www.thecommunitycode.com/p/why-community-should-report-to-the?utm_source=publication-search">Why Community Should Report to the COO</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/community-integrated-gtm">Community Has Impact. It Doesn&#8217;t Carry Across GTM.</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/the-3-biggest-lies-about-community">The 3 Biggest Lies About Community and GTM&#8212;And The Truth</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[The Efficiency Trap in AI-Powered Customer Experience]]></title><description><![CDATA[Companies can make every customer interaction faster and still leave customers feeling less understood.]]></description><link>https://www.thecommunitycode.com/p/the-efficiency-trap-in-ai-powered</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/the-efficiency-trap-in-ai-powered</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 16 Jun 2026 16:01:14 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!ktGF!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!ktGF!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!ktGF!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!ktGF!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!ktGF!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!ktGF!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!ktGF!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png" width="349" height="349" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:349,&quot;bytes&quot;:94384,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/200904339?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!ktGF!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!ktGF!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!ktGF!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!ktGF!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F1f5b2073-551a-47a8-bc9f-b35d709cab60_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>A founder recently asked me recently whether AI could help them scale customer support, onboarding, and education without adding a lot of headcount.</p><p>The honest answer was yes. It probably could, and in some areas it probably should.</p><p>Most companies have a long list of repetitive work that doesn&#8217;t require a person every time. Customers shouldn&#8217;t have to wait for someone to reset a password, locate a basic answer, or walk them through the same setup step that hundreds of people have already completed. Teams also shouldn&#8217;t spend their days copying information from one system into another because nobody has connected the systems properly.</p><p>I&#8217;ve worked inside enough companies, and advised enough others, to know how much energy gets wasted that way. There&#8217;s a lot of customer-facing work that can become faster, more consistent, and more useful with the right automation.</p><p>What I&#8217;m less convinced of is that making each interaction more efficient will automatically create a better customer relationship.</p><p>That&#8217;s where the conversation usually gets fuzzy.</p><p>A customer doesn&#8217;t experience support, onboarding, success, product, marketing, and community as separate functions. They experience one company. They don&#8217;t care which team owns the answer or which system generated it. They care whether the answer helps, whether it fits their situation, and whether they trust the people and product behind it.</p><p>When teams optimize those interactions one at a time, it&#8217;s very easy to lose sight of what they add up to.</p><h2>A series of reasonable decisions</h2><p>Most of the choices that create this problem make sense on their own.</p><p>Support introduces an AI assistant because response times are too slow. Product adds more self-service because customers want to move without waiting for someone. Customer success standardizes outreach because the team has too many accounts. Marketing produces more educational content because buyers want to do their own research before talking to anyone.</p><p>None of that is particularly controversial.</p><p>The risk appears when each function gets better at the part it owns and nobody looks closely at the relationship forming across all of it.</p><p>I&#8217;ve seen customer accounts that looked healthy from every internal view. Support volume was low. Product usage was stable. The customer success team had completed its check-ins. Nobody had raised an escalation, and there wasn&#8217;t an obvious warning sign.</p><p>The customer was still considering leaving.</p><p>Nothing dramatic had happened. They&#8217;d simply reached a point where they no longer believed the company understood what they were trying to accomplish.</p><p>That kind of confidence loss doesn&#8217;t usually arrive as a clean data point. It tends to show up through a collection of smaller changes:</p><ul><li><p>The customer asks fewer questions because they don&#8217;t expect a useful answer.</p></li><li><p>They stop joining events or participating in programs they used to value.</p></li><li><p>They use the product in a narrower way and stop exploring what else it could do.</p></li><li><p>They become less willing to advocate internally or publicly.</p></li><li><p>They remain technically active while becoming less invested.</p></li></ul><p>Sometimes silence means the experience is working. Sometimes it means the customer has stopped expecting much. Those look surprisingly similar for a while.</p><h2>The customer journey has more owners than the customer</h2><p>Inside most companies, the work has to be divided somehow. Marketing owns acquisition. Sales owns evaluation. Customer success owns adoption and renewal. Support owns troubleshooting. Product owns the experience inside the product. Community may touch all of those areas while (usually) officially sitting inside one of them.</p><p>That structure is practical, but it creates a blind spot.</p><p>Teams naturally optimize the moments they can see and measure. Support looks at resolution time and deflection. Marketing looks at content performance and conversion. Customer success looks at health scores, adoption milestones, and renewal risk. Product looks at activation and feature usage.</p><p>Those measures tell you whether a workflow is operating efficiently. They say less about whether the customer trusts the overall experience.</p><p>Trust develops gradually. A customer gets a useful answer, sees another customer describe a similar situation, notices that customer success understands the context, and sees the company acknowledge a limitation rather than pretend one doesn&#8217;t exist. None of those moments has to be dramatic, but together they create confidence.</p><p>The reverse happens the same way.</p><p>An automated response misses the nuance. A success check-in arrives with no awareness of the support issue from the previous week. The educational content sounds polished but doesn&#8217;t match the customer&#8217;s actual problem. Nobody has done anything terrible, yet the relationship starts to feel less useful and less personal.</p><p>The company may still be hitting every internal target. That&#8217;s what makes this difficult to catch.</p><h2>Community works differently</h2><p>I often describe community as relationships at scale.</p><p>That doesn&#8217;t mean community replaces sales, support, or customer success. I&#8217;ve never found that argument particularly credible. If you have a complicated product, you still need people who can answer technical questions, guide implementation, and help customers work through issues that require judgment.</p><p>Community works alongside those teams.</p><p>A support person can explain how a feature works. A customer success manager can help an account build an adoption plan. A community gives customers access to people who have dealt with something similar and can explain what happened in practice.</p><p>That distinction matters because customers often need more than information.</p><p>They may need to know:</p><ul><li><p>Whether someone else has tried the same approach</p></li><li><p>What went wrong the first time</p></li><li><p>Which tradeoffs mattered more than expected</p></li><li><p>How another team got internal buy-in</p></li><li><p>What the official process left out</p></li></ul><p>A technically correct answer may still leave the customer unsure what to do. A peer can help them interpret the answer in the context of a real situation.</p><p>The same thing happens in education. A company can build a comprehensive course that explains every feature. Another customer can say, &#8220;These were the three things we needed first, and we ignored the rest until month two.&#8221;</p><p>That&#8217;s often the more useful answer.</p><p>In <em><a href="https://www.amazon.com/dp/B0GQ4NYQ5N/">The Community Code</a></em>, I wrote about community as part of the operating system around the customer. AI makes that idea more relevant because companies can now scale information and interaction much faster than they can scale judgment, context, and trust.</p><p>Community can help preserve those things, but only when it&#8217;s connected to the rest of the customer journey. A forum sitting off to the side with no relationship to support, product, success, or education won&#8217;t solve much. It may just create one more place for customers to repeat themselves.</p><h2>People are messier than personas</h2><p>One of the recurring problems in scaled GTM is that the customer gradually becomes a persona.</p><p>Personas are useful. Marketing teams need a shorthand for planning campaigns. Product teams need patterns. Customer success teams need segmentation. Nobody can design every workflow around the full complexity of every individual customer.</p><p>The risk is forgetting that the person on the other side doesn&#8217;t fit the bullets as neatly as the slide suggests.</p><p>They may understand the product and still lack the internal influence to get anyone else to use it. Their company may have unusual politics. Their implementation may be blocked by someone who wasn&#8217;t part of the buying process. They may look like a healthy account while feeling increasingly unsure about whether the product is worth the effort.</p><p>Those details are often where the actual outcome is decided.</p><p>AI can make personalization better. It can tailor messages based on role, industry, product behavior, and past interaction. That will probably be more useful than the broad lifecycle campaigns many companies have been sending for years.</p><p>It still isn&#8217;t a relationship by itself.</p><p>A relationship requires some degree of recognition. The customer knows there&#8217;s someone on the other side who understands enough of the context to be useful. The company has enough continuity to notice when something changes. The person is more than a set of attributes used to generate the next message.</p><p>Community is one of the few GTM motions where people regularly show up as people to one another. They have names, histories, expertise, preferences, and frustrations. They don&#8217;t always behave the way the segment says they should, which is partly why the experience can surface things the rest of the system misses.</p><h2>Automation solves real problems</h2><p>There&#8217;s a version of this argument that romanticizes human interaction and treats automation as something inherently cold. I don&#8217;t find that very useful.</p><p>People give bad advice. Communities can repeat outdated information. Employees send canned responses. A customer may get a much better answer from an AI assistant at midnight than from a person two days later.</p><p>Automation can improve the experience in several practical ways:</p><ul><li><p>It makes basic information available when people need it.</p></li><li><p>It reduces repetitive work for teams that are already stretched.</p></li><li><p>It can identify patterns across far more interactions than a person could review manually.</p></li><li><p>It gives experienced employees more time for situations that require judgment.</p></li><li><p>It can make messages and guidance more relevant than the generic campaigns customers are used to receiving.</p></li></ul><p>Those are real benefits. The decision isn&#8217;t whether to automate. It&#8217;s where automation belongs and what still needs human context around it.</p><p>A company that automates repetitive retrieval while preserving access to judgment is making a very different choice from one that treats every interaction as a candidate for removal. Both may describe what they&#8217;re doing as efficiency, but the customer will feel the difference.</p><h2>What conventional metrics miss</h2><p>The efficiency gain usually becomes visible before the relationship cost does.</p><p>A team can see support deflection quickly. It can measure how many customers completed an automated onboarding flow. It can compare the cost of a live webinar with an on-demand course. Those results are useful and easy to explain internally.</p><p>Trust takes longer to show up.</p><p>It may appear when a customer asks a question earlier because they feel comfortable admitting confusion. It may show up when one member helps another avoid an implementation mistake. It may become visible when a customer advocates for the company internally because they trust the people around the product.</p><p>Sometimes the clearest evidence arrives when something goes wrong.</p><p>A customer who trusts the company gives it a chance to repair the situation. A customer who has received efficient but disconnected service may simply leave. By the time that happens, the original operating decisions are hard to trace.</p><p>This creates an incentive problem. Teams are rewarded for visible improvements inside their own reporting periods. The cost of removing useful human context may be distributed across retention, advocacy, product learning, and brand over a much longer period.</p><p>Nobody has to make a reckless decision for the overall system to get weaker.</p><h2>Start with what the customer is trying to decide</h2><p>When I&#8217;ve helped companies think through community, education, support, and customer engagement, I&#8217;ve found it more useful to start with the customer&#8217;s uncertainty than with the available channel.</p><p>What are they actually trying to decide?</p><p>Do they need information, judgment, reassurance, proof, or access to someone with similar experience?</p><p>Those needs lead to different answers.</p><p>A searchable help center may be ideal when the customer needs a factual answer. An AI assistant may be faster when they&#8217;re trying to locate the right documentation. A customer success manager may be necessary when the issue involves organizational risk. A peer conversation may be more credible when the customer wants to know how another team handled the same tradeoff.</p><p>Those are all legitimate parts of the customer journey. They just don&#8217;t produce the same kind of value.</p><p>This also changes how I&#8217;d think about community. It shouldn&#8217;t become the human fallback for everything automation can&#8217;t handle. That would turn it into an underfunded service layer with an impossible remit.</p><p>Its more distinctive role is creating the conditions where customers can learn from one another, see their experience reflected, and build confidence through participation. To do that well, community has to be connected to the teams designing the rest of the journey.</p><h2>The operating choice underneath the technology</h2><p>Two companies can adopt the same tools and create very different customer experiences.</p><p>The difference comes from what they decide to preserve.</p><p>Do customers still have access to people who understand their context? Can they learn from peers without every interaction becoming a sales opportunity? Does the company notice when repeated questions point to a deeper product or education issue? Are community insights allowed to change how onboarding, support, and customer success are designed?</p><p>Those are operating choices. The technology makes some options easier and others cheaper, but it doesn&#8217;t decide which relationships matter.</p><p>I&#8217;m optimistic about what AI can do inside customer-facing work. I&#8217;ve watched teams struggle for years with repetitive tasks, fragmented knowledge, and limited capacity. There&#8217;s a lot here that can genuinely improve the experience for customers and employees.</p><p>I&#8217;m less confident that the pursuit of efficiency will naturally preserve the parts of the relationship customers value most.</p><p>In my experience, those parts survive because someone identified them, argued for them, and designed them into the system.</p><h2>Decoded Takeaways</h2><p>Companies can improve support, onboarding, customer success, education, and product guidance while still creating a weaker overall relationship. That happens because each function measures the interaction it owns, while the customer experiences all of those interactions together.</p><p>AI makes local improvements easier to achieve. Faster answers and more self-service are useful, but they don&#8217;t always provide the judgment, continuity, or peer context customers need when the situation is unfamiliar or consequential.</p><p>Community can help by giving customers access to comparable experience and a place to interpret company guidance with other people. That role has to be connected to the broader customer journey. It won&#8217;t work particularly well as a forum or event program sitting off to the side.</p><p>The practical next step is to look at what customers are trying to decide at each stage. Information, judgment, reassurance, and peer proof aren&#8217;t interchangeable. Once you can see the difference, it becomes much easier to decide where automation improves the experience and where human context still needs to be designed in.</p><h2>Related posts:</h2><ul><li><p><a href="https://www.thecommunitycode.com/p/community-integrated-gtm">Community Has Impact. It Doesn&#8217;t Carry Across GTM.</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/how-the-same-customer-signal-turns">How the Same Customer Signal Turns Into Different Decisions</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/how-signal-gets-distorted">How Signal Gets Distorted</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[Community Codebreakers: Jane Nadaraja]]></title><description><![CDATA[What Yelp, Patreon, and Grammarly can teach us about building community programs around the behavior already happening]]></description><link>https://www.thecommunitycode.com/p/community-codebreakers-jane-nadaraja</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/community-codebreakers-jane-nadaraja</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 26 May 2026 16:01:24 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/161136047/579c1230ce796ea0615bae9b6e5a50cb.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><a href="https://www.linkedin.com/in/janenadaraja/">Jane Nadaraja</a> has spent nearly two decades working across community, marketing, events, and advocacy programs. She started her career at Yelp, spent six years at Patreon working closely with creators and their communities, and most recently worked with Grammarly&#8217;s large-scale community. She&#8217;s also advised companies on how to build programs that can grow without turning into a pile of disconnected activities with a nice program name slapped on top.</p><p>Her range is part of what makes this conversation useful. Jane has seen community across local consumer communities, creator ecosystems, product-led communities, ambassador programs, events, and large-scale advocacy work. Each of those environments has its own goals and constraints, but the common thread is pretty consistent: strong community programs tend to build around real member behavior, rather than internal assumptions about what the company wishes people would do.</p><p>One of the first things Jane said stuck with me because it gets at a point companies often skip past. In many cases, you&#8217;re not creating a community from nothing. The community already exists in some form. People are already helping each other, sharing feedback, writing reviews, creating examples, teaching peers, or explaining the product better than the company does. The program comes later, and the job is to understand what&#8217;s already happening before trying to formalize it.</p><h3>The community exists before the program does</h3><p>When Jane talked about Patreon, she described a company with an existing creator community that needed a more intentional way to listen, support, and build with those creators. The program didn&#8217;t begin as a blank-page exercise. It began with a real ecosystem of creators, fans, podcasters, musicians, and artists already using the platform in different ways.</p><p>A company can create a program, a forum, an ambassador structure, a newsletter, an event series, or a Slack channel. It can&#8217;t manufacture the emotional bond that makes people care. The more useful work is understanding what people are already doing, why they&#8217;re doing it, and what kind of structure would make that behavior easier, more useful, and more aligned with the company&#8217;s goals.</p><p>Jane described community as more than a role, identifier, or product relationship. It&#8217;s a sense of connectedness around a shared interest, experience, passion, or problem. That doesn&#8217;t mean everyone in the community is the same. In fact, stronger communities often bring together people from different backgrounds who care about the same thing from different angles.</p><p>For GTM and community teams, this is an important distinction. If you treat community as something the company invents, you&#8217;ll probably overbuild the container and underinvest in the behavior. If you treat community as something you&#8217;re trying to understand, support, and structure, the program has a much better chance of earning participation.</p><h3>Start with input, then build the program</h3><p>Jane kept coming back to the importance of gathering input before designing the program. That sounds obvious until you remember how many companies still launch community initiatives from a planning doc written mostly by internal stakeholders. The intentions may be good, but the result can end up reflecting the company&#8217;s operating needs more than the community&#8217;s actual motivations.</p><p>At Grammarly, Jane ran a pulse survey to understand how active community members were using the product, what they valued, and who might be interested in deeper advocacy. At Patreon, she used Discord polls, surveys, focus groups, and one-on-one interviews with creators to understand what was working, what wasn&#8217;t, and where the company needed to listen more closely.</p><p>Her approach was practical: use the full funnel of input. Broad data can show patterns. Surveys can surface themes. Focus groups can pressure-test hypotheses. One-on-one interviews can uncover the nuance that never shows up cleanly in a dashboard.</p><p>No single input is enough on its own. The point is to triangulate. If survey data tells you one thing, focus groups add context, and individual interviews reveal the emotional or practical reasons behind the behavior, you&#8217;re in a much better position to build something people will actually use.</p><p>Jane put it simply: &#8220;Your community is always the wisest resource you have.&#8221;</p><p>Easy to say. Frequently ignored. Usually expensive to rediscover later.</p><h3>Find the behavior you want more of</h3><p>One of the most useful parts of the conversation was Jane&#8217;s explanation of how to identify the right first members for a program. A lot of teams start with a vague idea of &#8220;power users,&#8221; &#8220;superfans,&#8221; or &#8220;advocates,&#8221; then try to reverse-engineer a selection process from there. Jane&#8217;s approach was more grounded: look for the people already modeling the behavior you want the broader community to adopt.</p><p>At Yelp, the goal was reviews. So the team looked for people already writing thoughtful, useful, high-quality reviews. They weren&#8217;t just looking for enthusiasm or brand affinity. They were looking for people whose behavior matched the value Yelp needed more of.</p><p>At Patreon, the goal was different. The team wanted creators who could help build awareness and bring other creators into the ecosystem. That meant looking for influence inside specific creative niches, creators who were already supporting others, and people with recruiting potential inside their own communities.</p><p>The useful part of this example is that the principle stays the same, even when the business goal changes. The right early members are usually already doing something worth scaling. They&#8217;re helping, teaching, creating, organizing, advocating, or connecting others before the company gives them a badge or invites them into a formal program.</p><p>The mistake is treating member selection like a popularity contest or a pure reach exercise. Reach can matter, of course. Influence can matter. But if the person&#8217;s behavior doesn&#8217;t map to what the program needs to create more of, you&#8217;re mostly recruiting visibility without much operating value.</p><p>A better question is: who is already acting like the community we want to build?</p><h3>Pilot before you scale</h3><p>Jane was very clear on this point: pilot the program.</p><p>At Patreon, the ambassador program started with 50 people, then expanded to 50 in different international metros before rolling out more broadly. The first year was invitation-only before applications opened up.</p><p>This kind of sequencing can feel slow, especially inside companies that want the optics of scale as quickly as possible. It&#8217;s also how you avoid making a big promise to the community before you know whether the experience works.</p><p>A pilot gives you room to kick the tires. You can see what people respond to, what confuses them, what internal teams actually need, and where the operational load starts to break. It also gives the company time to understand what kind of support, communication, tooling, and internal coordination the program will require.</p><p>Community programs involve people, trust, status, access, and identity. Rolling them out broadly without testing can create problems that are hard to unwind later. Expectations harden quickly once people feel like they&#8217;ve been invited into something meaningful.</p><p>So yes, starting smaller can feel less exciting. It&#8217;s also a lot less chaotic than launching a dinner party by opening the doors to the entire city and hoping the vibes sort themselves out.</p><p>Bold. Usually unwise.</p><h3>Scaling requires structure</h3><p>Jane likes what she called the &#8220;slow burn&#8221; approach. That doesn&#8217;t mean staying small forever. At Patreon, the program grew from 50 to 500 creators in a year. The difference is that growth followed learning, rather than replacing it.</p><p>She mentioned several tactics that helped: referrals, targeted invites, events, segmented outreach, and using data to identify members whose behavior aligned with the program&#8217;s goals. She also talked about the emotional challenge of scale. In the early days, community managers often know everyone. They know people&#8217;s names, interests, projects, and sometimes their pets. At a certain point, that one-to-one intimacy can&#8217;t work the same way.</p><p>The work then becomes less about personally knowing everyone and more about designing systems that still make people feel seen, supported, and connected.</p><p>At Patreon, that included clearer support pathways for ambassadors, including a dedicated email address and service-level agreement with the customer support team. Ambassadors had a more direct experience, and the community manager didn&#8217;t have to become the human router for every product or support question.</p><p>This is where community scale tends to get very real. More members means more edge cases, more internal asks, more communication needs, and more chances for the experience to become uneven. Without structure, the program starts depending too much on individual heroics. And individual heroics are a terrible operating model, even if community teams have historically been very good at disguising them as &#8220;being scrappy.&#8221;</p><h3>Consistency is underrated</h3><p>Jane also made a strong case for consistency: monthly events, reliable communication, a regular newsletter or update, and a predictable rhythm people can depend on.</p><p>This may sound basic, which is probably why it gets neglected. A lot of programs over-index on big moments and underinvest in the operating cadence that keeps people engaged between those moments. Jane&#8217;s view was simple: don&#8217;t bombard people, but do show up reliably.</p><p>At Patreon, she sent a monthly newsletter by a consistent date. If internal teams wanted product updates, testing opportunities, or announcements included, they had to meet that deadline. Over time, the newsletter became valuable because members knew what to expect and internal teams knew how to participate.</p><p>For community teams, this is one of those unglamorous operating practices that makes the visible work possible. A reliable cadence creates trust with members and discipline internally. It also gives other teams a clear way to work with community without turning every request into a last-minute favor.</p><h3>Reporting needs both business impact and program health</h3><p>Jane&#8217;s reporting framework lined up closely with how I think about community measurement: you need to understand both the business value and the health of the community itself.</p><p>The business side answers how the work is helping the company. Depending on the program, that might mean more high-quality reviews, creator acquisition, product adoption, advocacy, customer stories, early product feedback, or support for launches.</p><p>The community side answers whether the program is healthy enough to keep creating that value over time. That might include member growth, engagement quality, event participation, satisfaction, programming value, retention, and whether members feel like the program is worth their time.</p><p>The mistake is choosing only one side. If you only report program health, leadership eventually asks why the work matters. If you only report business impact, the community starts to feel extracted from. You need both lenses if the program is going to keep earning investment without burning through the trust that makes it work.</p><p>A mature community program should be able to say, &#8220;Here&#8217;s what this is doing for the business, and here&#8217;s how we know the community is still healthy enough to keep creating that value.&#8221; That&#8217;s a much stronger story than reporting activity and hoping people connect the dots themselves.</p><h3>Key takeaways</h3><ul><li><p>The community often exists before the program does. The work starts by understanding what people are already doing, then building structure around the behavior that matters.</p></li><li><p>Member selection should begin with behavior. At Yelp, that meant finding people already writing useful reviews. At Patreon, it meant finding creators with influence inside their own communities.</p></li><li><p>Pilots protect the relationship. Starting small gives you room to learn, fix weak spots, and avoid overpromising before the program is ready.</p></li><li><p>Scale requires systems. As a program grows, the work shifts from personally knowing everyone to designing pathways, rhythms, and support structures that still make people feel connected.</p></li><li><p>Consistency builds trust. Regular communication and predictable programming may not sound exciting, but they&#8217;re often what keep the program usable for members and internal teams.</p></li><li><p>Reporting needs two lenses: business impact and community health. One helps earn continued investment. The other protects the engine that creates the value.</p></li></ul><h3>Decoded insight</h3><p>The best community programs don&#8217;t start by asking how big they can get. They start by asking what behavior is already worth building around.</p><p>Jane kept returning to that idea in different ways. Whether she was talking about Yelp reviewers, Patreon creators, Grammarly advocates, or ambassador programs, the pattern was consistent: find the signal, build around it, and scale without flattening the thing that made it valuable in the first place.</p><p>You can connect with Jane Nadaraja on LinkedIn to follow more of her work across community, advocacy, and customer engagement.</p><p>And if this conversation sparked a thought, leave a comment or share it with someone building a community program that needs more structure and less wishful thinking.</p><h3>Timestamps</h3><p>00:00 &#8211; Meet Jane Nadaraja<br>00:59 &#8211; Defining community<br>02:00 &#8211; A memorable Patreon moment<br>05:20 &#8211; Why Patreon invested in community<br>07:22 &#8211; Where community sits inside the org<br>09:08 &#8211; Gathering input<br>12:21 &#8211; Designing around business needs<br>14:52 &#8211; Piloting before scaling<br>15:49 &#8211; Finding the right first members<br>20:23 &#8211; Scaling without losing quality<br>27:24 &#8211; Engagement rhythms<br>30:35 &#8211; Reporting on impact<br>34:28 &#8211; Sharing community work internally</p>]]></content:encoded></item><item><title><![CDATA[How Signal Gets Distorted]]></title><description><![CDATA[If you follow customer signal through a GTM workflow, there are a few specific places where it tends to lose its shape.]]></description><link>https://www.thecommunitycode.com/p/how-signal-gets-distorted</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/how-signal-gets-distorted</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 19 May 2026 16:02:09 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!r3gD!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!r3gD!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!r3gD!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!r3gD!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!r3gD!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!r3gD!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!r3gD!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png" width="348" height="348" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/dd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:348,&quot;bytes&quot;:175201,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/197115449?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!r3gD!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!r3gD!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!r3gD!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!r3gD!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Fdd0c43d3-6621-4a54-9834-ad83db590816_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>If you take the idea <a href="https://www.thecommunitycode.com/p/how-the-same-customer-signal-turns">from the last post</a> and follow it a bit further, the more useful question isn&#8217;t whether signal gets reshaped as it moves across teams, because that part is almost inevitable. What matters more is understanding where that reshaping actually happens in practice, and why it tends to show up in the same places over and over again.</p><p>It&#8217;s easy to talk about this in abstract terms, but when you look at how work actually moves through a GTM organization, the breakdown points are surprisingly consistent. You can usually trace them back to a small number of transitions where information has to change form in order to be useful to the next team, and those transitions are where most of the signal loss happens.</p><h3>Where translation tends to happen</h3><p>In most GTM workflows, customer signal moves through a few predictable steps before it influences a decision. It usually starts in a raw form, whether that&#8217;s community activity, support tickets, sales conversations, or product usage, and from there it has to be turned into something that can travel across teams.</p><p>That typically involves a sequence of changes that look something like this:</p><ul><li><p>Summarizing what&#8217;s happening into a smaller set of patterns</p></li><li><p>Grouping those patterns into categories or themes</p></li><li><p>Framing them in a way that fits the next team&#8217;s priorities</p></li></ul><p>Each of those steps is necessary, because without them the signal is too noisy to act on. At the same time, each step introduces a small shift in meaning, where something specific tied to a particular situation becomes more general and easier to process, but also easier to deprioritize once it&#8217;s competing with other inputs that have already been structured in a similar way.</p><h3>Why this doesn&#8217;t get caught earlier</h3><p>One of the reasons this is difficult to address is that the process makes sense from inside each function. Product needs to see patterns across many customers rather than individual anecdotes, marketing needs language that can scale, and sales and customer teams need signals that map to pipeline and retention.</p><p>From within each of those contexts, the translation step feels like the right thing to do. The issue is what happens when those translations aren&#8217;t connected to each other, because over time you end up with multiple versions of the same signal that all make sense locally but don&#8217;t line up in a way that drives a clear decision globally.</p><h3>Where it breaks inside workflows</h3><p>If you map this to how work actually gets done, there are a few points where the signal tends to break down, and they&#8217;re usually tied to moments where ownership shifts or where inputs get combined.</p><p>One is the initial handoff from a raw source into a structured system, which is where context is most likely to get compressed. Another is when that structured input gets combined with other inputs, because at that point it&#8217;s no longer evaluated on its own terms but as one item in a broader set of priorities. You also see it when outputs get pushed back out into the market, because messaging, enablement, and product updates are all shaped by whatever signal made it through those earlier steps.</p><p>Across those moments, the same pattern tends to show up:</p><ul><li><p>The signal becomes easier to compare</p></li><li><p>It becomes easier to prioritize at a high level</p></li><li><p>It becomes harder to connect back to the original context</p></li></ul><p>That tradeoff is part of what allows teams to operate at scale, but it&#8217;s also where the gap starts to widen in ways that are hard to see from inside any single function.</p><h3>Why adding more signal doesn&#8217;t fix it</h3><p>A common response to this problem is to try to improve visibility by adding more dashboards, more reporting, and more ways to surface customer feedback. Those can help at the edges, but they don&#8217;t address what&#8217;s happening inside the workflow itself.</p><p>If the underlying process requires signal to be translated multiple times, then adding more signal just increases the volume moving through the same system. You end up with more data, but the same points of breakdown, which is part of why community can feel like it&#8217;s working and not working at the same time. It generates a lot of useful signal, but that signal is still subject to the same translation steps once it leaves that environment.</p><h3>What this looks like in practice</h3><p>If you look at how this plays out across functions, it tends to follow a familiar pattern. Product sees a set of categorized inputs that are easy to compare but harder to tie back to specific customer situations, marketing works with language that has been generalized enough to scale but doesn&#8217;t always reflect how customers actually describe their experience, and sales and customer teams operate on signals that map cleanly to their metrics but don&#8217;t always capture what&#8217;s changing underneath.</p><p>None of those views are wrong. They&#8217;re all shaped by how the work needs to happen. The issue is that they don&#8217;t reconnect, which makes it harder to act on the underlying situation in a coordinated way.</p><h3>Where this leaves you</h3><p>If you&#8217;re trying to improve how customer signal influences your GTM, the goal isn&#8217;t to eliminate translation, because that&#8217;s not realistic and it&#8217;s not even desirable. The goal is to understand where it&#8217;s happening and what&#8217;s being lost at each step, which usually starts with a simple question: at what point in your workflow does the signal stop looking like the thing you originally observed?</p><p>Once you can identify those points, you can start to decide where you want to preserve more context, where you need better alignment between teams, and where the system itself needs to change. That&#8217;s a harder problem than just improving visibility, but it&#8217;s also where most of the leverage tends to be.</p><h2>Decoded Takeaways</h2><p>Customer signal doesn&#8217;t disappear inside GTM workflows. It gets translated into forms that are easier to process and prioritize, and that translation happens at predictable points.</p><p>Those points include the initial shift from raw input to structured data, the combination of that data with other inputs, and the way decisions get pushed back out into the market. Each step makes the signal more usable within a specific system and less connected to its original context, which over time creates gaps between how different teams understand the same underlying situation.</p><p>Improving visibility can help, but it doesn&#8217;t address where the signal is actually breaking down. The more useful approach is to identify where translation is happening and decide where you need to preserve more of the original meaning.</p><h2>Related Posts</h2><ul><li><p><a href="https://www.thecommunitycode.com/p/community-integrated-gtm">Community Has Impact. It Doesn&#8217;t Carry Across GTM</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/the-gtm-problem-behind-the-community">Where Community Breaks Down Inside GTM</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/make-it-daebak-what-k-pop-fandoms">What K-Pop Can Teach Go-to-Market Teams</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[How the Same Customer Signal Turns Into Different Decisions]]></title><description><![CDATA[You can look at the same customer behavior in three different systems and walk away with three different conclusions.]]></description><link>https://www.thecommunitycode.com/p/how-the-same-customer-signal-turns</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/how-the-same-customer-signal-turns</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 12 May 2026 16:01:32 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!kBXW!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!kBXW!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!kBXW!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!kBXW!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!kBXW!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!kBXW!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!kBXW!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png" width="350" height="350" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:350,&quot;bytes&quot;:274146,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://www.thecommunitycode.com/i/197114885?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!kBXW!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png 424w, https://substackcdn.com/image/fetch/$s_!kBXW!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png 848w, https://substackcdn.com/image/fetch/$s_!kBXW!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png 1272w, https://substackcdn.com/image/fetch/$s_!kBXW!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F3d9a094c-c285-4256-af62-342c6076b934_1200x1200.png 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>When I was at Asana, I got into the habit of spending time in the forum before big cross-functional meetings. It wasn&#8217;t part of any formal process. I just wanted a quick read on what customers were actually dealing with at that moment and how that was evolving over time.</p><p>If you spend even a little time in a space like that, patterns start to show up quickly. You begin to recognize the same accounts, how their questions change, and where they&#8217;re running into friction. A lot of what you see tends to fall into a few categories:</p><ul><li><p>Where people are getting blocked</p></li><li><p>How they&#8217;re working around limitations</p></li><li><p>What they&#8217;re trying to do that isn&#8217;t fully supported</p></li><li><p>How their usage is changing over time</p></li></ul><p>Then I&#8217;d go into a planning conversation, and that context wasn&#8217;t already in the room.</p><p>It wasn&#8217;t that people didn&#8217;t care about it. It just wasn&#8217;t part of the system they were using to make decisions, so the same customers and the same product showed up as a different set of priorities depending on where you were looking.</p><h3>Where this gets expensive</h3><p>One place this becomes very clear is in expansion.</p><p>You&#8217;re reviewing accounts and deciding where to spend time, and from the perspective of the systems most teams rely on, things look fine. Usage is steady, nothing is at risk, and nothing is moving in a way that demands attention. So the account ends up somewhere in the middle. It&#8217;s not something you ignore, but it&#8217;s not something you prioritize either.</p><p>At the same time, if you look at what&#8217;s happening in the community, you can see a different trajectory. The signals don&#8217;t look urgent in isolation, but taken together they tell a different story:</p><ul><li><p>Questions are shifting from basic to more advanced</p></li><li><p>The same people are showing up repeatedly in events</p></li><li><p>Customers are starting to answer other customers&#8217; questions</p></li></ul><p>Those are usually signs that an account is going deeper into the product and starting to figure out how to apply it in more complex ways.</p><p>From one angle, the account looks flat. From another, it looks like it&#8217;s moving. Both views are grounded in real data, but they don&#8217;t connect in a way that changes what happens next. As a result, the account stays where it is.</p><p>From the outside, that can look like a missed opportunity. From the inside, it&#8217;s a reasonable decision based on the information that&#8217;s available, which is part of what makes this hard to catch early.</p><h3>How that pattern repeats</h3><p>You see a similar dynamic in product conversations.</p><p>Community surfaces a steady stream of signal, and it&#8217;s not just feature requests. It&#8217;s confusion, workarounds, and patterns in how people are actually using the product. That signal usually makes its way into product discussions, but it has to be translated into something that fits how roadmap decisions are made.</p><p>That typically means it gets summarized, categorized, and compared against other inputs that are already structured in a similar way. This step is necessary, because product teams need a way to evaluate tradeoffs across many competing priorities.</p><p>At the same time, something changes in that translation.</p><p>What felt immediate and clear when you saw it in its original context becomes easier to deprioritize once it&#8217;s been reshaped. The context that made it feel urgent doesn&#8217;t fully carry through, and over time that creates a gap between what&#8217;s being surfaced and what actually influences decisions.</p><p>From one side, it can feel like the same issues keep coming up without anything changing. From the other, the signal doesn&#8217;t quite map cleanly to how decisions are made, so it gets acknowledged without materially shifting the roadmap.</p><h3>Messaging drifts in a similar way</h3><p>Marketing runs into a version of this that&#8217;s a bit less obvious, but follows the same pattern.</p><p>Community is one of the few places where you hear how customers actually talk about the product when they&#8217;re not trying to fit into your positioning. You get a clear sense of the language they naturally use, where they hesitate, and how they describe what they&#8217;re trying to do.</p><p>That&#8217;s useful input if you&#8217;re trying to refine how you show up in the market, but unless there&#8217;s a tight loop that brings that language into how messaging is developed and updated, it tends to stay local.</p><p>Over time, that shows up in ways that are easy to rationalize:</p><ul><li><p>Messaging feels slightly off, but not enough to trigger a full rethink</p></li><li><p>Different teams describe the product in slightly different ways</p></li><li><p>Customer language shows up inconsistently across channels</p></li></ul><p>Nothing in that process looks broken when you&#8217;re inside it. It just takes longer to get to something that feels coherent.</p><h3>Why this is hard to catch</h3><p>One of the reasons this persists is that the system keeps working well enough that it doesn&#8217;t force a correction.</p><p>Expansion still happens, product still ships, and marketing still drives pipeline. From the inside, it feels like normal complexity, where each team is doing good work and decisions make sense within the context they&#8217;re operating in.</p><p>The cost shows up more in timing than anything else. You see it in opportunities that take longer to surface, decisions that take longer to line up, and messaging that takes longer to correct when it starts to drift. None of those issues trigger an immediate response, but they accumulate over time.</p><h3>What&#8217;s actually going on underneath it</h3><p>Each GTM function is doing what it&#8217;s designed to do. It takes in information and translates it into its own system.</p><p>Marketing is looking at pipeline and conversion, product is looking at usage and roadmap, sales is focused on deals and expansion, and customer teams are looking at retention and support. Each of those perspectives is grounded in something real.</p><p>The challenge is that the same underlying signal gets reshaped as it moves through those systems. Each step makes it easier to interpret within that context and harder to connect across contexts, which is where the drift starts to show up.</p><p>This is something I kept coming back to while writing <em><a href="https://www.amazon.com/dp/B0GQ4NYQ5N/">The Community Code</a></em>, because community is one of the few places where you can see the full arc of how customers actually think and behave over time. The visibility is there. What happens after the signal leaves that environment is where things start to break down.</p><h3>Where I&#8217;d look first</h3><p>If you&#8217;re trying to make sense of this in your own organization, I wouldn&#8217;t start by asking whether you have enough customer insight, because most teams do.</p><p>I&#8217;d start by looking at where that insight changes form, where it gets summarized, reframed, or filtered to fit a different system, and where it stops influencing decisions even though it&#8217;s still being surfaced. Those are usually the places where the underlying issue becomes visible.</p><h2>Decoded Takeaways</h2><p>The same customer behavior can show up across multiple systems and lead to different decisions depending on how it&#8217;s interpreted.</p><p>Each team is working with real signal, but they&#8217;re working with it in a way that fits how their system operates, which makes it harder to act on collectively.</p><p>Over time, that shows up less as obvious failure and more as delay, where opportunities, decisions, and messaging all take longer to line up than they should.</p><p>If you&#8217;re trying to improve outcomes, it&#8217;s worth paying attention to where the same signal leads to different conclusions, because that&#8217;s usually where the system is introducing friction.</p><h2>Related Posts</h2><ul><li><p><a href="https://www.thecommunitycode.com/p/community-integrated-gtm">Community Has Impact. It Doesn&#8217;t Carry Across GTM</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/the-gtm-problem-behind-the-community">Where Community Breaks Down Inside GTM</a></p></li><li><p><a href="https://www.thecommunitycode.com/p/make-it-daebak-what-k-pop-fandoms">What K-Pop Can Teach Go-to-Market Teams</a></p></li></ul>]]></content:encoded></item><item><title><![CDATA[How Your Org Structure Distorts Customer Signal]]></title><description><![CDATA[Why do so many GTM problems show up when customer-facing work moves between teams?]]></description><link>https://www.thecommunitycode.com/p/in-gtm-and-community-the-work-doesnt</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/in-gtm-and-community-the-work-doesnt</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Tue, 21 Apr 2026 16:03:01 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!AOeC!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!AOeC!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!AOeC!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic 424w, https://substackcdn.com/image/fetch/$s_!AOeC!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic 848w, https://substackcdn.com/image/fetch/$s_!AOeC!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic 1272w, https://substackcdn.com/image/fetch/$s_!AOeC!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!AOeC!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic" width="350" height="350" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:350,&quot;bytes&quot;:207183,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/heic&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://thecommunitycode.substack.com/i/193428440?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!AOeC!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic 424w, https://substackcdn.com/image/fetch/$s_!AOeC!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic 848w, https://substackcdn.com/image/fetch/$s_!AOeC!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic 1272w, https://substackcdn.com/image/fetch/$s_!AOeC!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F0932f648-5404-4e4b-87d0-9e0fb3d37137_1200x1200.heic 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>If you spend time inside most go-to-market teams, the work generally looks fine. Marketing is generating demand, product is shipping features, sales is closing deals, and customer teams are running onboarding, driving adoption, and trying to protect retention. You can sit with any one of those teams and they can usually explain what they&#8217;re doing, why they&#8217;re doing it, and how they measure success.</p><p>That part is rarely the issue. When I was at Asana, and in most of the companies I&#8217;ve worked with since, the internal story at the team level was usually coherent. People were thoughtful about their tradeoffs. The work was intentional. There was a clear sense of progress.</p><p>But customers don&#8217;t experience teams. They experience the system those teams create together. And when you look at it from that angle, things start to feel less connected. The message they hear early doesn&#8217;t always carry into onboarding. The context they build up during onboarding doesn&#8217;t always show up in product decisions. The signals they&#8217;re sending in one place don&#8217;t seem to exist in another.</p><p>No single team owns that gap, which is why it persists. The work inside each function holds up, but the system between them doesn&#8217;t.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3>Where things actually start to drift</h3><p>The way I&#8217;d think about this is that GTM systems don&#8217;t usually break inside workflows. They drift at the seams, where work moves from one team to another and has to be reinterpreted.</p><p>Onboarding is one of the clearest places to see it. Marketing spends a lot of time getting the story right. Who this is for, what problem it solves, and what success looks like. That&#8217;s usually the result of a lot of iteration and pressure to improve conversion.</p><p>Then the customer lands in the product or in an onboarding program that&#8217;s optimized for something slightly different. Product might be focused on feature exposure. Customer success might be focused on time-to-first-value. Support might be trying to reduce ticket volume. All of those are reasonable goals, but they don&#8217;t always line up with the promise that brought the customer in.</p><p>So the customer ends up doing the translation work themselves. They&#8217;re trying to reconcile what they were told with what they&#8217;re now being asked to do. That gap isn&#8217;t the result of a bad decision by any one team. It&#8217;s the result of how the work is structured across teams.</p><p>You see the same pattern with product feedback. Community surfaces a constant stream of signal, not just feature requests, but confusion, workarounds, and the language customers actually use to describe what they&#8217;re trying to accomplish. Product teams want that signal and will often set up processes to capture it.</p><p>But once that signal moves into product, it has to fit how product makes decisions. It gets summarized, categorized, and prioritized alongside roadmap commitments, sales input, and internal hypotheses. In that process, a lot of the context gets stripped out, and what started as a clear signal turns into something more abstract and easier to deprioritize.</p><p>Nothing is broken inside the function. The hand-off changes the meaning.</p><h3>Every team defines success differently</h3><p>This is where the issue becomes more structural. Each GTM function is operating against a different definition of success, and those definitions shape how customer behavior gets interpreted.</p><p>Marketing is looking at conversion and pipeline. Product is focused on adoption and usage. Sales is looking at deal velocity and size. Customer teams are tracking retention, expansion, and support load. All of those are valid, but they create different lenses on the same underlying reality.</p><p>A spike in community questions might signal strong engagement from one perspective and product friction from another. A highly active customer in the community might be seen as an advocate by one team, but not show up as expansion-ready in another team&#8217;s systems. So each team takes the signal and reshapes it to fit its own model.</p><p>Over time, that creates drift. Not because anyone is doing something wrong. It&#8217;s just that there&#8217;s no shared mechanism to carry meaning across those interpretations.</p><h3>Community sees more than it can carry</h3><p>Community sits in an unusual position in all of this. It often has visibility across the entire customer journey, from early interest through onboarding, product usage, and expansion. It hears the same customer talk about different parts of their experience over time, which gives it a more continuous view than most other functions.</p><p>In theory, that makes it a useful connective layer. In practice, it&#8217;s usually embedded inside a single team, most often marketing or customer success, and that placement shapes how its work is interpreted.</p><p>If it sits in marketing, its insights tend to get pulled toward demand and engagement. If it sits in customer success, they get framed around retention and support. Either way, it struggles to carry signal cleanly across the rest of the system. It can surface insight and advocate for it, but it rarely has the structural authority to ensure that insight changes how other teams operate.</p><p>So it becomes a source of signal without a reliable path for that signal to travel.</p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/in-gtm-and-community-the-work-doesnt?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/in-gtm-and-community-the-work-doesnt?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.thecommunitycode.com/p/in-gtm-and-community-the-work-doesnt?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h3>What this looks like in real workflows</h3><p>You can see this most clearly in a few recurring workflows, but one that stands out from my time at Asana is expansion.</p><p>We had accounts where, from a traditional lens, things looked stable but unremarkable. Usage was steady, no major support issues, nothing that would trigger immediate attention from sales or customer success. If you were looking purely at product analytics or account health scores, these accounts would sit somewhere in the middle of the pack.</p><p>At the same time, if you looked at community behavior, a different picture emerged. You&#8217;d see people from those same accounts showing up consistently in events, asking increasingly sophisticated questions in the forum, and in some cases, answering other customers&#8217; questions. They were moving from basic usage into deeper workflows.</p><p>That&#8217;s not a vanity signal. That&#8217;s a leading indicator of maturity.</p><p>The problem was that this context didn&#8217;t consistently show up in the systems that sales or customer teams were using to prioritize expansion. So decisions were being made based on a partial view of the account.</p><p>If you map that out, it tends to look something like this:</p><ul><li><p>Product sees stable usage and no obvious risk, so the account is &#8220;healthy but not urgent&#8221;</p></li><li><p>Customer success sees limited expansion activity, so it doesn&#8217;t rise to the top of the queue</p></li><li><p>Sales focuses on accounts with clearer, more immediate signals tied to pipeline</p></li></ul><p>Meanwhile, community is seeing depth, curiosity, and increasing sophistication, but that signal isn&#8217;t structured in a way that carries into those decisions.</p><p>No one is making a bad call. They&#8217;re making a rational call based on the data available to them. The issue is that the system isn&#8217;t designed to bring those signals together in a way that changes how the account is handled.</p><p>So expansion opportunities get missed, or at least delayed, not because the signal isn&#8217;t there, but because it doesn&#8217;t travel.</p><p>You see a similar pattern in messaging. Community hears how customers actually talk about the product, what language resonates, what confuses them, what they struggle to explain internally. That&#8217;s valuable input for marketing.</p><p>But unless there&#8217;s a tight loop, that language tends to stay local. It might influence a few pieces of content or a specific campaign, but it doesn&#8217;t consistently shape how the company talks about itself across channels.</p><p>Each team continues refining its own version of the story, and over time those versions start to diverge.</p><h3>Why this stays hidden for so long</h3><p>One of the more frustrating aspects of this is that the system can operate this way for a long time without forcing a correction. Nothing fully breaks. There&#8217;s enough overlap and redundancy to keep things moving. Teams compensate, build their own processes, and fill in gaps manually.</p><p>From the inside, it feels like normal complexity. From the outside, it shows up as inconsistency.</p><p>Customers don&#8217;t see the internal structure. They experience the system as a whole. When signal doesn&#8217;t carry across hand-offs, that shows up as repeated context, mismatched expectations, and small moments of friction that accumulate over time. None of those moments are catastrophic on their own, but they compound.</p><h3>Where things go sideways</h3><p>If you step back, the issue isn&#8217;t that teams aren&#8217;t doing good work. It&#8217;s that the system they&#8217;re part of isn&#8217;t designed to preserve intent as work moves across boundaries.</p><p>Each team takes in customer signal, interprets it through its own lens, and optimizes accordingly. That&#8217;s rational behavior, and it&#8217;s also what causes the drift. Community makes this more visible because it sits across those boundaries and hears when customers notice the gaps, but without structural support, it ends up compensating rather than resolving.</p><p>Teams respond by trying to improve the work inside each function. Better onboarding, clearer messaging, stronger feedback loops. Those are all worthwhile, but they don&#8217;t address the underlying issue.</p><p>The breakdown isn&#8217;t inside the work. It&#8217;s in how the work connects.</p><h3>So where does it break for you?</h3><p>If you&#8217;ve tried to make this work across teams, you&#8217;ve probably felt some version of this already. The more useful question isn&#8217;t whether your teams are doing good work. It&#8217;s where that work starts to lose meaning as it moves between them.</p><p>Where does the original intent get diluted or reshaped? Is it onboarding, where the promise doesn&#8217;t quite carry into the experience? Is it product feedback, where signal gets filtered to the point of being unrecognizable? Is it expansion, where you know more about the account than your systems reflect?</p><p>Or is it somewhere else entirely? I&#8217;m curious where this shows up most clearly for you.</p><div><hr></div><h3>Decoded Takeaways</h3><ul><li><p>Most GTM teams don&#8217;t struggle because individual functions are underperforming. They struggle because the system connecting those functions isn&#8217;t designed to preserve meaning as work moves across it.</p></li><li><p>Each team is operating with a different definition of success, and that shapes how it interprets customer behavior. Over time, that creates consistent distortion. The same signal gets translated differently depending on where it lands, which makes it harder to act on collectively.</p></li><li><p>What makes this difficult to address is that the system continues to function. There&#8217;s enough overlap to keep things moving, which hides the underlying issue. Teams compensate instead of fixing the structure.</p></li><li><p>Community sits in the middle of this. It often has the clearest view of the full customer journey, but it doesn&#8217;t have the authority to ensure that signal carries across teams in a consistent way. It surfaces insight, but it can&#8217;t guarantee that insight changes how the system operates.</p></li><li><p>If you&#8217;re trying to improve outcomes, the instinct is to optimize within a function. That helps, but it doesn&#8217;t solve the problem.</p></li><li><p>The more important question is where intent gets lost between functions. That&#8217;s where the system actually needs to change.</p></li></ul><div><hr></div><h3>Related Posts</h3><ul><li><p><a href="https://thecommunitycode.substack.com/p/community-integrated-gtm">Community Has Impact. It Doesn&#8217;t Carry Across GTM</a></p></li><li><p><a href="https://thecommunitycode.substack.com/p/the-gtm-problem-behind-the-community">Where Community Breaks Down Inside GTM</a></p></li><li><p><a href="https://thecommunitycode.substack.com/p/community-x-gtm-playbook-what-every-15c">Community x GTM Playbook: What Every Chief Product Officer &amp; Head of Product Needs to Know</a></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div></li></ul>]]></content:encoded></item><item><title><![CDATA[Community Has Impact. It Doesn’t Carry Across GTM.]]></title><description><![CDATA[Why community-led growth falls short and how community-integrated GTM changes decision-making and outcomes across teams.]]></description><link>https://www.thecommunitycode.com/p/community-integrated-gtm</link><guid isPermaLink="false">https://www.thecommunitycode.com/p/community-integrated-gtm</guid><dc:creator><![CDATA[Joshua Zerkel]]></dc:creator><pubDate>Wed, 01 Apr 2026 14:30:48 GMT</pubDate><enclosure url="https://substackcdn.com/image/fetch/$s_!3Vbw!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic" length="0" type="image/jpeg"/><content:encoded><![CDATA[<div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!3Vbw!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!3Vbw!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic 424w, https://substackcdn.com/image/fetch/$s_!3Vbw!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic 848w, https://substackcdn.com/image/fetch/$s_!3Vbw!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic 1272w, https://substackcdn.com/image/fetch/$s_!3Vbw!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!3Vbw!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic" width="1200" height="1200" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:1200,&quot;width&quot;:1200,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:97886,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/heic&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://thecommunitycode.substack.com/i/192806447?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!3Vbw!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic 424w, https://substackcdn.com/image/fetch/$s_!3Vbw!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic 848w, https://substackcdn.com/image/fetch/$s_!3Vbw!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic 1272w, https://substackcdn.com/image/fetch/$s_!3Vbw!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F4c612ba8-01d5-4263-9723-e31c59bd2e04_1200x1200.heic 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Today, my new book, <em>The Community Code,</em> is officially out.</p><p><a href="https://www.amazon.com/dp/B0GQ4NYQ5N/">It&#8217;s available now on Amazon</a><strong>.</strong></p><p>This book comes out of a pattern I kept running into across companies, roles, and stages. Community was clearly doing something valuable. Customers were helping each other learn the product, sharing use cases, influencing adoption, and in some cases shaping pipeline and expansion.</p><p>But that impact rarely translated across the rest of the organization.</p><p>Individually, the signals were easy to point to. Collectively, they were harder to make sense of. That&#8217;s where things tend to break down.</p><div class="captioned-button-wrap" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/community-integrated-gtm?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="CaptionedButtonToDOM"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! This post is public so feel free to share it.</p></div><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/p/community-integrated-gtm?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://www.thecommunitycode.com/p/community-integrated-gtm?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p></div><h3><strong>Why this book exists</strong></h3><p>Inside the company, each team interprets what it sees through its own lens. Marketing frames it as advocacy. Product treats it as feedback. Customer success sees adoption patterns. Sales looks for proof points to support deals in motion.</p><p>All of those interpretations are valid. The problem is that they don&#8217;t connect in a way the business can actually operate on.</p><p>What looks like a cohesive system from the outside gets broken into pieces on the inside. As a result, community ends up feeling simultaneously important and hard to justify. There&#8217;s visible impact, but no shared understanding of how that impact moves through the business.</p><p>This book makes that system visible and usable.</p><h3><strong>Where community-led growth falls short</strong></h3><p>&#8220;Community-led growth&#8221; helped move the conversation forward. It gave the work more weight and tied it to outcomes leadership already cared about.</p><p>That shift mattered. But in practice, it also introduced a mismatch.</p><p>Most organizations aren&#8217;t designed for any single function to lead growth on its own. Product, marketing, sales, and customer success each control different parts of the lifecycle, and growth shows up when those parts reinforce each other over time.</p><p>Community doesn&#8217;t sit neatly inside that structure. It cuts across it. So expectations expand, but decision rights and operating models don&#8217;t change alongside them.</p><p>As companies scale, the result becomes obvious. Multiple versions of &#8220;community&#8221; start to appear across the org. Marketing builds advocacy programs. Customer success builds onboarding and support spaces. Product runs betas or feedback groups. Developer relations builds ecosystems.</p><p>Each effort makes sense in isolation. Each is tied to a clear goal. But they&#8217;re owned by different teams, measured differently, and rarely connected in a way that reflects how customers actually experience the product.</p><p>From the company&#8217;s perspective, the structure is rational. From the customer&#8217;s perspective, it&#8217;s fragmented.</p><h3><strong>The problem isn&#8217;t belief, it&#8217;s translation</strong></h3><p>At this point, most GTM leaders don&#8217;t need to be convinced that community has value. The harder problem is making that value usable.</p><p>Signal is generated in one place and consumed in another. Context gets lost along the way. Teams fall back on their own proxies because the underlying system isn&#8217;t visible enough to work from directly.</p><p>That&#8217;s why the same patterns keep repeating. Product teams see spikes in requests without full context. Marketing highlights stories that resonate externally but don&#8217;t fully reflect usage. Sales leans on isolated proof points. Customer success sees early signs of friction but struggles to connect them back to upstream decisions.</p><p>These aren&#8217;t failures of execution. They&#8217;re artifacts of how the system is structured.</p><p>Without a shared way of carrying signal across functions, each team optimizes locally. The result is a set of decisions that make sense individually but don&#8217;t consistently reinforce each other.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><h3><strong>From fragmented signal to community-integrated GTM</strong></h3><p>A more durable approach starts by changing how community shows up in the system.</p><p>Not as a standalone program, and not as a function that owns outcomes, but as a way of feeding shared customer signal into how product, marketing, sales, and customer success actually operate.</p><p>When that signal is visible and consistently used, things change in a way that&#8217;s hard to fake. Product decisions reflect how customers are using the product in context, not just isolated requests. Marketing messaging aligns more closely with how customers describe value in their own words. Sales conversations carry examples that generalize. Customer success leans more on peer momentum instead of purely reactive support.</p><p>What changes isn&#8217;t any single output. It&#8217;s how those outputs start to reinforce each other.</p><p>That reinforcement is where leverage shows up. It&#8217;s also where most community efforts stall, not because the work isn&#8217;t valuable, but because the system around it isn&#8217;t designed to absorb and use that value consistently.</p><h3><strong>How this looks in practice</strong></h3><p>You can see this in companies that have invested in connecting customer signal across functions.</p><p>At Asana, the community forum, ambassador program, and events surfaced patterns around how teams were adopting the product, where they were getting stuck, and how use cases were evolving over time. That signal showed up in product conversations, influenced how customer stories were told, and informed how teams approached onboarding and expansion.</p><p>At Atlassian, community conversations often surface emerging needs and workarounds long before they appear in formal feedback channels. That signal feeds into product teams, partner ecosystems, and support content, creating a more connected view of how customers are actually using the platform.</p><p>In both cases, the value of community isn&#8217;t just in the interactions themselves. It&#8217;s in how those interactions inform decisions across the rest of the organization.</p><p>That doesn&#8217;t happen automatically. It requires intentional design around how signal is captured, translated, and shared.</p><h3><strong>What the book does</strong></h3><p><em>The Community Code</em> breaks this down directly.</p><p>It maps how customer signal actually moves across go-to-market, where it gets lost, and how to integrate it into the way teams operate day to day.</p><p>This isn&#8217;t about elevating community as an idea. It&#8217;s about changing how work happens across product, marketing, sales, and customer success so they operate from the same underlying inputs.</p><p>If you want to go deeper, you can <a href="https://www.amazon.com/dp/B0GQ4NYQ5N/">learn more about </a><em><a href="https://www.amazon.com/dp/B0GQ4NYQ5N/">The Community Code</a></em><a href="https://www.amazon.com/dp/B0GQ4NYQ5N/"> here</a>.</p><h3><strong>Decoded Takeaways</strong></h3><ul><li><p>Community generates some of the earliest and most nuanced customer signal, but that signal often fragments as it moves across teams</p></li><li><p>&#8220;Community-led growth&#8221; elevates the importance of the work, but doesn&#8217;t resolve how it fits into vertically structured organizations</p></li><li><p>The core issue isn&#8217;t belief in community&#8217;s value, it&#8217;s the lack of a shared system to translate that value into decisions</p></li><li><p>A community-integrated approach creates a common layer of signal that product, marketing, sales, and customer success can operate from</p></li><li><p>Durable advantage shows up when those functions start reinforcing each other based on the same underlying inputs</p></li></ul><h3><strong>Related Posts</strong></h3><ul><li><p><a href="https://thecommunitycode.substack.com/p/from-community-led-to-community-integrated">Why I No Longer Say &#8220;Community-Led Growth&#8221;<br></a>Where the language starts to fall apart in practice, and how it creates expectations most organizations can&#8217;t actually support.</p></li><li><p><a href="https://thecommunitycode.substack.com/p/the-gtm-problem-behind-the-community">Where Community Breaks Down Inside GTM<br></a>How community gets fragmented across marketing, product, sales, and customer success, and what that fragmentation costs the business.</p></li><li><p><a href="https://thecommunitycode.substack.com/p/make-it-daebak-what-k-pop-fandoms">What K-Pop Can Teach Go-to-Market Teams<br></a>A different lens on the same idea, showing how coordinated community behavior can shape distribution, adoption, and narrative without owning growth directly.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://www.thecommunitycode.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Thanks for reading The Community Code! Subscribe for free to receive new posts and support my work.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div></li></ul>]]></content:encoded></item></channel></rss>