<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Michael Rome on Medium]]></title>
        <description><![CDATA[Stories by Michael Rome on Medium]]></description>
        <link>https://medium.com/@romemike?source=rss-5404fa7d32e1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IC-PTNgGNxQABsA-n6Ad5w.jpeg</url>
            <title>Stories by Michael Rome on Medium</title>
            <link>https://medium.com/@romemike?source=rss-5404fa7d32e1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:15:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@romemike/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[50 Principles for Startup CMOs]]></title>
            <link>https://medium.com/growthhackers/50-principles-for-startup-cmos-f546b8baf215?source=rss-5404fa7d32e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f546b8baf215</guid>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[growth-marketing]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Michael Rome]]></dc:creator>
            <pubDate>Mon, 22 Mar 2021 15:01:10 GMT</pubDate>
            <atom:updated>2021-03-23T13:42:46.396Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>50 Principles for Startup Marketers</strong></h3><h4>Principles to help modern marketers grow software products faster and accelerate their careers</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-TzkZuv98JBp4RQzFZXtrw.jpeg" /></figure><p>I wrote these Principles after 10 years of reading and applying many lessons on growing and marketing software from incredible practitioners. These Principles were revised and edited down 50+ times after years of growth experiments, failures, and successes.</p><p>Many of these ideas aren’t my own, but I can vouch for their effectiveness. Applying these Principles is how I:</p><ul><li>Became the CMO of a $50M+ annual revenue software company (joined at $8M)</li><li>Previously <a href="https://blog.growthhackers.com/literally-everything-ive-learned-acquiring-1-617-418-customers-17607bb8d48?source=friends_link&amp;sk=f2bb07c735474800ce5bddd02a09df05">acquired 1.6M paying customers</a> (*not users) for early stage software companies</li></ul><p>These Principles are for software entrepreneurs and marketers:</p><ul><li>Looking to focus on less things, but the right things for growth</li><li>Wanting a First Principles-based approach to growing and marketing software</li><li>Wanting a repeatable process for growth that isn’t reliant on single tactics</li><li>Aiming to move faster in their careers</li></ul><h3><strong>Macro Marketing</strong></h3><p>1. Successful marketing means mastering <strong>scale</strong> and <strong>unit economics</strong></p><p>2. <strong>Scale</strong> means a channel or tactic’s potential for customers</p><p>3. <strong>Unit economics</strong> means a channel or tactic’s cost vs. revenue and profit per customer</p><p>4. A common mistake with unit economics is only measuring <strong>cost to acquire</strong> and not <strong>cost to reactivate or retain</strong>; all matter for healthy growth</p><p>5. When it comes to finding successful marketing channels, start with <a href="https://www.amazon.com/Traction-Startup-Achieve-Explosive-Customer/dp/1591848369"><strong>Traction: How Any Startup Can Achieve Explosive Customer Growth</strong></a></p><h3><strong>Marketing Mix</strong></h3><p>6. A strong marketing mix includes <strong>Awareness</strong>, <strong>Consideration</strong>, and <strong>Conversion</strong></p><p>7. Maximizing your bets across all three with good unit economics and quick ratios is <strong>how to never get fired</strong></p><ul><li><strong>Awareness:</strong> prospective customers know who you are</li><li><strong>Consideration:</strong> prospective and active customers know your value and how you’re different</li><li><strong>Conversion:</strong> you have a playbook to convert prospective customers and retain active ones</li></ul><p>8. Direct ROI on <strong>awareness marketing</strong> is usually unrealistic if you’re trying to build for real scale (<a href="https://www.linkedin.com/in/nateturner1/">thanks for this one, Nate</a>)</p><ul><li>If you don’t spend on awareness, you risk an insufficient # of prospects (i.e. people aware and/or considering) to convert and continue considerable growth</li><li>This isn’t an excuse not to measure rigorously</li><li>Commit to tracking awareness spend separately with the key metric(s) being impressions/reach/CPI/CPC/CTR to your target audiences</li><li>Ruthlessly optimizing lower funnel marketing and product is the only way to keep scaling awareness marketing assuming you care about favorable cost to lifetime value ratios</li></ul><h3><strong>Customer Types and Real Growth</strong></h3><p>9. The most important formula for growth is <strong>Active = New + Reactivated + Retained</strong></p><p>10. <strong>Active</strong> customers is an output metric and often given too much focus</p><p>11. Only focusing on Actives can also lead to<strong> Fake Growth</strong></p><p>12. <strong>Fake Growth</strong> is a favorable CMGR where lots of customer acquisition masks unhealthy churn</p><p>13. <strong>New</strong>, <strong>reactivated</strong>, and <strong>retained</strong> customers are input metrics and often not given enough focus</p><p>14. <strong>New</strong>, <strong>reactivated</strong>, and <strong>retained</strong> are mutually exclusive, and thus, a wonderful way to understand strengths and weaknesses to growth</p><ul><li><strong>New</strong> customers use your product for the first time in [insert period]</li><li><strong>Reactivated</strong> customers use your product in [insert period], not in the preceding period, but in some period before that</li><li><strong>Retained</strong> customers use your product in [insert period] and in the preceding period</li></ul><p>15. Your marketing mix must balance each customer type if maximizing <strong>healthy growth</strong> is the goal</p><p>16. <a href="https://medium.com/swlh/diligence-at-social-capital-part-1-accounting-for-user-growth-4a8a449fddfc">Social Capital’s <strong>Quick Ratio</strong></a><strong> </strong>is the best most honest way to assess product-market fit (P/M fit) and real growth</p><p>17. Marketing’s purpose <strong>pre and post P/M fit</strong> are very different</p><p>18. <strong>Pre P/M fit</strong>, marketing is a tool to drive customers to learn how to achieve P/M fit; if you try to grow pre P/M fit, you’ll light money on fire</p><p>19. <strong>Post P/M fit</strong>, marketing is a tool to drive customer growth</p><p>20. The best engine for growth is a <strong>great Product, not Marketing </strong>(i.e. strong Quick Ratios)</p><p>21. If a company perceives Marketing as the only team responsible for growth, <strong>run</strong></p><p>22. A common marketing spend mistake is spending too much on <strong>New</strong>, not enough on <strong>Reactivated</strong>, and not knowing what you spend on <strong>Retained</strong> (i.e. Are you wasting money on already returning customers?)</p><h3><strong>Growth Stages, Frameworks, and Process</strong></h3><p>23. There’s <strong>four stages to growth</strong></p><ul><li>Making something enough people want and will pay for</li><li>Hypothesize models for growth (all below: use AARRR and/or Growth Loops, fold in ICE)</li><li>Test rapidly to validate your growth hypothesis</li><li>Confirm tests, double down, and repeat</li></ul><p>24. The best old school framework to measure what matters is Dave McClure’s <a href="https://producttribe.com/revenue-amp-growth/aarrr-framework-best-guide"><strong>Startup Metrics for Pirates</strong></a><strong> </strong>(AARRR)</p><ul><li><strong>Acquisition:</strong> prospective customers come to your product</li><li><strong>Activation:</strong> prospective customers become customers</li><li><strong>Retention:</strong> active customers continue being active customers</li><li><strong>Revenue:</strong> users get to revenue (i.e. customers), or active customers get to higher LTVs</li><li><strong>Referral:</strong> users or customers market the product for you</li></ul><p>25. Good marketers do acquisition; <strong>unicorn marketers</strong> do all five (AARRR)</p><p>26. The best new school framework to measure what matters is Brian Balfour, Casey Winters, Kevin Kwok, and Andrew Chen’s<strong> </strong><a href="https://www.reforge.com/blog/growth-loops"><strong>Growth Loops</strong></a></p><ul><li>Loops answer, “How does this product grow?” on more macro level than funnel frameworks</li><li>Loops provide compounding growth and may be more defensible than funnels</li></ul><p>27. The best framework to prioritize an individual or team’s time is<strong> </strong><a href="http://tech.trello.com/ice-scoring/"><strong>ICE</strong></a> (Impact, Confidence, and Effort)</p><ul><li><strong>Impact</strong>: if this works, how big can it be for profit, revenue, customers, etc.?</li><li><strong>Confidence:</strong> what’s the likelihood that it works?</li><li><strong>Effort:</strong> what’s the human, time, and financial cost to find out if it works?</li></ul><h3><strong>Growth Teams</strong></h3><p>28. <a href="https://medium.com/build-better-products/why-startups-shouldnt-have-growth-teams-57310ff06e18"><strong>Smaller startups shouldn’t have growth teams</strong></a></p><p>29. The <strong>most important attributes</strong> (*not skills) of Growth Teams are curiosity, humility, discipline for process, grit, and a belief in idea meritocracies</p><ul><li><strong>Curiosity:</strong> the best test ideas usually come from customers. The next best ones usually come from reading, reflection, and inspiration outside the office</li><li><strong>Humility:</strong> experiment results often surprise; even the best Growth Teams are wrong a lot</li><li><strong>Discipline for process:</strong> great Growth Teams can look boring. Same meeting cadence, agenda, and process to prioritize/test/measure/learn/repeat</li><li><strong>Grit:</strong> Growth Teams are paid to be wrong a lot. Being wrong leads to learning. The best keep going.</li><li><a href="https://www.linkedin.com/pulse/key-bridgewaters-success-real-idea-meritocracy-ray-dalio/"><strong>A belief in idea meritocracies</strong></a><strong>:</strong> the best idea should be tested. Doesn’t matter who or where it came from.</li></ul><p>30. Generally, a solid <strong>growth team makeup</strong> is a team lead, technical marketer, full stack developer, full stack designer, and a data analyst (that’s experienced and technical enough to moonlight as a QA engineer)</p><ul><li><strong>Team lead:</strong> keeps morale high (hard since most experiments fail) and maintains discipline for process</li><li><strong>Technical marketer:</strong> doubles as team product manager and measurer and communicates learnings</li><li><strong>Full stack developer:</strong> can set up majority of tests without much help</li><li><strong>Full stack designer:</strong> can polish experiments or take the lead if more front-end focused</li><li><strong>Data analyst-QA engineer:</strong> many of the best wins are just fixing bugs in core flows and experiences</li></ul><p>31. <strong>Growth teams need buy-in from the top. If it’s not there, don’t bother.</strong></p><p>32. <strong>Starting and finishing tests regularly is almost everything to start; forget about results</strong></p><p>33. <strong>The formula for growth</strong> = # tests run * average test impact” * test success rate</p><p>34. <strong># tests run</strong> is the only one fully in your control; hence why it’s almost everything to start</p><p>35. <a href="https://youtu.be/n_yHZ_vKjno"><strong>Growth is optional</strong></a></p><h3><strong>Easy Wins</strong></h3><p>36. Brian Balfour’s <a href="https://brianbalfour.com/essays/growth-process-first-tactics-second"><strong>Building a Growth Machine</strong></a> is how you build a constant engine for new, good ideas</p><p>37. <strong>Great tactics come from great process</strong>, but there’s a handful that usually work (below)</p><p>38. Apply <a href="https://thestartupfactory.tech/journal/apply-the-pareto-principle-to-your-startup"><strong>Pareto</strong></a> to all parts of the customer lifecycle (i.e. lead gen, sales, product roadmaps, support, etc.)</p><p>39. <strong>Conversions congruence</strong> (i.e. <a href="http://verygoodcopy.com/">Copy</a>, <a href="https://unbounce.com/conversion-glossary/definition/congruence/">Design</a>, etc. that matches on ads and landing pages) will drive more efficient spend (linked are my favorite one-stop sources)</p><p>40. <strong>Fixing bugs in core flows</strong> is usually the highest ICE-scoring opportunity for post-P/M fit products</p><p>41. <strong>Activate first</strong>, educate later</p><p>42. <strong>Personalize</strong> whenever possible</p><p>43. In other words, subscribe to Andrew Chen’s <strong>The Minimalist Funnel </strong>when it comes to product and activation</p><ul><li>Strip things down and ask for as little as possible</li><li>Just get the user into the product so they can experience the magic (ask for most info later)</li><li>The only exceptions are email/push/text permissions and key “personalization” steps</li></ul><p>44. Use <a href="https://en.wikipedia.org/wiki/Logistic_regression"><strong>logistical regressions</strong></a> to find your product’s AHA Moment</p><ul><li>Logistical regressions are how Facebook discovered <a href="https://mode.com/blog/facebook-aha-moment-simpler-than-you-think/"><strong>“7 friends in 10 days”</strong></a> was their growth engine</li><li>The <strong>AHA Moment</strong> is when someone realizes your product’s value and often tells others about; to find your AHA moment: (1) Organize your historical data so each row is a user (2) Have a column with your binary dependent variable such as retained users (3) Users that complete this goal get a 1, everyone else gets a 0 (4) Have additional columns with possible independent/explanatory variables (E.g. 7 friends in 10 days), noting a 1 or 0 depending on if the person did this (5) Use R or Excel to get coefficient and significance level for each independent variable</li></ul><p>45. Spend <strong>80% of time doubling down</strong> on channels and tactics with good scale and unit economics and <strong>20% of your time testing new ones</strong> (the others will become saturated and less effective in time)</p><h3><strong>Attribution</strong></h3><p>46. <a href="https://support.google.com/analytics/answer/9397590?hl=en#:~:text=Attribution%20in%20Google%20Analytics%20brings,duplicated%20across%20all%20digital%20channels&amp;text=Build%20understanding%20of%20your%20brand&#39;s%20customer%20journey."><strong>Google Analytics</strong></a> is usually sufficient for attribution for early stage companies</p><p>47. The best alternatives to last-touch attribution that tell a more accurate story of a channel’s value are <a href="https://mindyourdecisions.com/blog/2016/08/02/how-advertisers-are-using-game-theory-to-attribute-sales-more-accurately-game-theory-tuesdays/"><strong>Shapley Value</strong></a><strong> </strong>and <a href="https://www.analyzecore.com/2016/08/03/attribution-model-r-part-1/"><strong>Markov Chain</strong></a></p><p>48. <strong>Brand and offline marketing channels are measurable</strong>: you can do a lot with unique codes, landing pages, and post-order surveys and indices</p><h3><strong>People, Culture, and Management</strong></h3><p>49. <a href="https://firstround.com/review/radical-candor-the-surprising-secret-to-being-a-good-boss/"><strong>Radical candor</strong></a> is the best way to manage</p><p>50. Good managers do three things: listen, care, and follow through</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f546b8baf215" width="1" height="1" alt=""><hr><p><a href="https://medium.com/growthhackers/50-principles-for-startup-cmos-f546b8baf215">50 Principles for Startup CMOs</a> was originally published in <a href="https://medium.com/growthhackers">Growth Hackers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Literally Everything I’ve Learned Acquiring 1,617,418 Customers]]></title>
            <link>https://medium.com/growthhackers/literally-everything-ive-learned-acquiring-1-617-418-customers-17607bb8d48?source=rss-5404fa7d32e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/17607bb8d48</guid>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[growth-marketing]]></category>
            <dc:creator><![CDATA[Michael Rome]]></dc:creator>
            <pubDate>Mon, 19 Feb 2018 15:04:06 GMT</pubDate>
            <atom:updated>2018-03-05T23:46:20.329Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Advice for breaking into startups, building high-functioning growth teams, and the only customer acquisition playbook you’ll ever need.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gwbubhgKKcBFNNgfn7Z81A.jpeg" /></figure><p><em>I wrote the following “rough transcript” from my Guest Lecture at </em><a href="http://www.kellogg.northwestern.edu/innovation-entrepreneurship.aspx"><em>The Northwestern Kellogg Innovation &amp; Entrepreneurship Initiative</em></a><em>.</em></p><p><em>The customer count in the title is a conservative estimate based on my last 6-years working as a growth employee across three software businesses. 94% of the 1.6 million customers are not just “product users,” but actual paying customers. Big thanks to Professor </em><a href="http://sean-johnson.com/"><em>Sean Johnson</em></a><em> for inviting me in!</em></p><p><strong>How did you start working in growth for startups?</strong></p><p>I started out as a management consultant. I loved the challenging work and smart people, but I didn’t like the politics and hierarchies. I also didn’t like how consultants don’t control whether their work is put into the world. Often, you make recommendations that never get executed. But putting ideas into the world is how you learn, and I craved that.</p><p>I had a hypothesis that tech startups had what I liked about management consulting, but also satisfied its shortcomings.</p><p>In terms of how I landed a gig, I sent one thoughtful email to a founder, early employee, or investor every day for three months. I only reached out to people who genuinely excited me — that’s key. I also didn’t ask them for a job. I just asked for an opportunity to learn. In hindsight, that was a breath of fresh air for many since they’re always being asked for jobs, money, favors, etc. Dozens were happy to meet.</p><p>Along the way, the network I was building recommended following experts in the space. I started reading blogs like <a href="http://andrewchen.co/">Andrew Chen’s</a>, and I was blown away at the possibilities. The space was starting to evolve, and I was all-in on becoming a part of it.</p><p><strong>What are the skills or competencies that you think are most important in someone working on growth?</strong></p><p>1) <strong>Commitment to lifelong learning.</strong> A lot of the best test ideas come from customers. The next best ones usually come from observations and inspiration not at work. People on a quest to read, explore, and acquire knowledge outside of the office always benefit the team’s execution inside the office.</p><p>2) <strong>Humility.</strong> Right when we think we’ve got the world figured out, a test surprises us, and users do the complete opposite of what we think. You need to always balance the pride and confidence in all the progress that you’ve made with the reality that you’ve got so far to go.</p><p>3) <strong>An appreciation for process.</strong> On the outside, our team looks boring. We meet at the same time weekly. Our agenda never changes. We prioritize, test, measure and reflect on experiments. And repeat. The predictability isn’t for everyone.</p><p>4) <strong>Grit and perseverance.</strong> We’re like “weather-men” and “weather-women”–we’re paid to be wrong a lot. Even as we continue to practice our craft and commit to process. If you don’t have the stomach to appreciate the struggles and the journey, it’s not for you.</p><p>5) <strong>Someone who values an “</strong><a href="https://www.linkedin.com/pulse/key-bridgewaters-success-real-idea-meritocracy-ray-dalio/"><strong>idea meritocracy</strong></a><strong>.”</strong> Ray Dalio coined this term at Bridgewater, and it’s applicable to any team hell-bent on performing, not just growth teams. Best idea wins, period. We don’t care about whose experiment it was. We just care about putting the best one forward. The ship sinks or sails, and we’re all on it.</p><p><strong>What’s the ideal growth team constellation?</strong></p><p>Early on, the teams were just me (an analytical person with some DB skills to find product bugs) and a full-stack developer. Overtime, they got more sophisticated. Below is a strong team make-up and close to what I have today:</p><p>1) <strong>Growth team lead:</strong> ensures morale is strong, the team stays disciplined, and we stick to process.</p><p>2) <strong>Technical marketer:</strong> doubles as a growth product manager, measures experiments, and communicates outcomes and learnings to the team (to help us get smarter).</p><p>3) <strong>Full-stack developer:</strong> can generally set up 60–70% of tests without help.</p><p>4) <strong>Full-stack designer:</strong> can polish experiments or take the lead if more front-end focused.</p><p>5) <strong>QA engineer:</strong> we don’t have one, but I’ve seen what it can do. Many of the best wins are just fixing broken stuff, and people obsessed with QA can be a game changer.</p><p>This all said, our team is still resource-constrained. Even having raised tens of millions. We’re constantly having to give up developer time to other projects. But operating with constraints is way easier than operating without them.</p><p><strong>From a process perspective, how should growth teams organize?</strong></p><p>The first startup I worked at was small enough where we got away with sloppy organization. Early on, the process was just “hit the database, find something broken, show and convince a developer,” and hopefully it was enough to have them resolve the issue. Bringing a solution to the table also goes a long way in getting things done faster.</p><p>I also did more “product growth” vs. “marketing growth” because we were capital-constrained. We only raised a couple million. So that meant focusing on “product.” I later learned this product-first mentality was hugely important regardless of how much capital you had. At the time though, the constraint just forced our hand in a positive way.</p><p>Brian Balfour’s <a href="https://brianbalfour.com/essays/growth-process-first-tactics-second">Growth Machine article</a> is 80% of our current process. If you follow it rigorously, you’ll be ahead of 95% of growth teams.</p><p><strong>What are some top growth team lessons?</strong></p><p>1) <strong>If you can’t communicate and convince an engineer a task is worth their time, you’re not on a path to creating an ideal growth team culture.</strong> While you might get a few tests built and deployed quickly, you’ll move much slower long-term. Most developers are told what to do too often by people who aren’t as smart as they are. You’ve got to respect their criticalness to your craft and ensure they know they’re an equal partner vs. just a means to just ship the team’s idea.</p><p>2) <strong>It’s not just about finding people who have the skills. They have to appreciate the uniqueness of the work</strong>. Much of the best growth work revolves around a) setting up process to always be close to and communicate with the customer and b) fixing the biggest things that are broken. As a team, we rarely build features that are shiny and new–we just iterate on what already exists. Because our core product already exists. This iterative mindset vs. the “making something new” mindset isn’t for every developer, designer, marketer, etc. The work usually isn’t sexy. But some love it and get excited about moving key metrics. You’ve got to find those with a world view that aligns with the team mentality you’re striving to build.</p><p>3) <strong>Growth teams need buy-in from the top. If it’s not there, don’t bother.</strong> Much of your work won’t help grow the business. CEOs, founders, etc. need to be on board that a) it takes time to learn and b) while success rates will improve if you’re following process, you’ll still be wrong more than right. Outside of patience from the top, you also need committed resources because without it, you can’t succeed at the next lesson below.</p><p>4) <strong>Starting and finishing tests on a regular basis is almost everything, especially early on.</strong> The formula for growth equals “number of tests run” * “average test impact” * “test success rate.” In the early days, “number of tests run” is the only input in your control. If you start and finish tests on a regular basis, learnings compound, you get smarter about prioritization, and the other inputs improve.</p><p><strong>Any big wins you’re proud of?</strong></p><p>To the point of, “Some of the best wins are just fixing broken stuff,” 4-weeks into my first “growth job” I realized we weren’t telling users during sign-up that they had to activate and confirm their account via email. We found it out by getting outside the office and testing half-a-dozen coffee shop patrons with the flow. We fixed it and activation rates skyrocketed. It was a “million-dollar annual revenue” win that took less than a morning between spotting the problem and deploying a fix.</p><p>A more complex win my team’s (along with our Data Analytics team) making progress on today is “how we use churn scores and several other variables” to dictate “how we issue customer discounts and coupons.” We’ve already saved the business hundreds of thousands in annual coupon costs with no statistically significant negative impact on sales and revenue. We’re thinking the savings will climb to $1M+ as we continue to hone the model this year.</p><p><strong>How have things evolved from your early growth days and today from a growth perspective?</strong></p><p>I’ve come to have much more appreciation for well-rooted process. A lot of my time is now spent thinking and executing on how we master the process vs. hit the end goal. Because the best way to hit the goal is to double-down on the process (assuming it’s a good one).</p><p>I’ve become much more focused on the inputs (i.e. executing the process) because I know that’s the best way to move the outputs. Every growth team is trying to move an organization’s KPIs, but many are too focused on the end-KPI itself, instead of <a href="https://brianbalfour.com/essays/north-star-metric-growth">the inputs that’ll get you there</a>.</p><p><strong>What’s a typical day like for you and your team? Typical week?</strong></p><p>I wrote this article on <a href="https://medium.com/build-better-products/why-startups-shouldnt-have-growth-teams-57310ff06e18">why newly-founded, smaller startups shouldn’t have growth teams</a>. It gives a thorough description of a “day in the life.”</p><p><strong>How do you figure out if you have a product issue or a growth issue?</strong></p><p>Great question. While everyone is pursuing Product Market Fit, when you ask most what that means, they’re not sure. That’s because too many founders and investors toss around the phrase loosely but can’t translate it into an actual equation. <a href="https://medium.com/swlh/diligence-at-social-capital-part-1-accounting-for-user-growth-4a8a449fddfc">Social Capital’s Diligence Series</a> solved this problem, and their “growth accounting” and “Quick Ratio” measurements will tell you if the product’s ready for growth.</p><p><strong>If you were starting from scratch with a new company, didn’t have the benefit of a growth team, etc., how would you organize to get to your first 1,000 users?</strong></p><p>Before I went after even 1K users, I’d measure if a startup was ready for user acquisition with any kind of scale. Again, the Social Capital Diligence Series is my favorite method for measuring Product Market Fit. If it looks healthy, I’d then use the <a href="https://medium.com/@yegg/the-bullseye-framework-for-getting-traction-ef49d05bfd7e">Bullseye Framework</a> (Pro Tip: go read the full book <a href="https://www.amazon.com/Traction-Startup-Achieve-Explosive-Customer/dp/1591848369">Traction</a>) for starting and finishing tests across user acquisition channels to find the ones that lead to good scale and unit economics.</p><p>If P/M Fit doesn’t look promising, I’d start talking to users to figure out how to improve. Too many companies think “they just need a great growth marketer” when in reality their product isn’t ready for one.</p><p><strong>As the growth team, how do you influence making product improvements?</strong></p><p>Outside of the tests we run to hopefully improve the product, one of the best benefits to a growth team is “the world view it can instill” in the greater organization. That’s actually where much of the magic happens. If all of the sudden support teams or sales teams or non-growth product teams start making decisions based on quantifying things like <a href="http://tech.trello.com/ice-scoring/">impact, confidence, and level of effort</a> (i.e. ICE), the whole organization improves its productivity.</p><p><strong>What part of the funnel do you think is the most important?</strong></p><p>This just depends on if the product is pre- or post-P/M fit as well as what resources are available. Speaking generally though, I’d say many companies are too focused on marketing levers (i.e. acquisition) and not enough focused on product levers (i.e. activation, retention, and referral). Acquisition is usually the easiest of all levers, so I’d say it’s natural to gravitate towards it and spend a disproportionate level of time there.</p><p><strong>How do you prioritize acquisition work?</strong></p><p>The two frameworks mentioned above: 1) The Bullseye Framework for finding channels with good scale and unit economics and 3) ICE for figuring out which experiments to prioritize in what channels.</p><p><strong>How do you balance qualitative vs. quantitative user feedback?</strong></p><p>One great way is to “quantify qualitative feedback.” Sometimes what gets fixed first in a product is based on who received the worst support call from a customer. Or the bug the CEO finds. This is usually not a great method for prioritization.</p><p>Instead, I like Pareto Charts to quantify what customers are saying. Asking customers, “How can we make the product better for you,” theming responses, and segmenting the data by light/medium/heavy users is a great way to build confidence in the impact of fixing a specific bug or adding features. The goal of the chart is to understand “what small subset of themes comprise the majority of problems and opportunity?” We don’t focus on the things that extend beyond the horizontal 80% line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W9t68Ojw9ZKnv7RRc0zrdg.png" /></figure><p>Another great tactic to ensure a constant flow of data around “support requests and bugs” is to have members of growth team subscribe to support inboxes and regularly add data and themes to their Pareto.</p><p>There’s also new products like <a href="https://www.buglife.com/">Buglife</a> to help make capturing valuable feedback easier. While I haven’t used and can’t vouch for the product I’m definitely going to give it a shot. They’re hitting on a key problem.</p><p><strong>When do you think it makes sense to transition to a full-fledged growth team?</strong></p><p>Post-P/M fit. 20+ employees. My answer isn’t too scientific, but basically once the organization gets large enough where everyone’s job is no longer just to grow the company. In the early days, Alex Schultz says it best, <a href="http://startupclass.samaltman.com/courses/lec06/">everyone should be the growth team</a>.</p><p><strong>How do you decide what to focus on?</strong></p><p>ICE.</p><p><strong>How do you estimate impact?</strong></p><p>I haven’t found a bullet-proof answer yet. The important thing is a) that you try and b) apply a similar method to all potential tests. We tend to look in three places:</p><p>1) <strong>Primary Data:</strong> do we have any customer data in support of the idea?</p><p>2) <strong>Secondary “Close Proximity” Data:</strong> even if we don’t have customer data to support the trend, is there strong evidence specific to our space that we can have confidence in?</p><p>3) <strong>All Other Secondary Data:</strong> have we read something, that while not specific to our space, we have strong conviction is applicable?</p><p>Getting impact right improves in time (as you capture more primary data). Still, I’ve found that even if you have little-to-no customer data to start, going through the three tiers above is a great way to eliminate bad ideas. So, while you might not find the best idea at first, you’ll eliminate the worst ones. And if you eliminate the worst ones, your probability of success improves because your denominator in the “number of tests we could run” gets smaller.</p><p><strong>How do you track performance of your initiatives?</strong></p><p>Two ways:</p><p>1) <strong>The Input Metrics:</strong> are we starting and finishing tests on a regular basis (for us, weekly), are we having our weekly meeting every week (creating great habits and continued momentum is key), are we prioritizing using ICE and embracing an “idea meritocracy,” and are we capturing, socializing, and reflecting on every test’s learnings as we decide what to test next?</p><p>2) <strong>The Output Metrics:</strong> for us, we just make sure to only have a handful of metrics we care about to improve focus (i.e. 2–3), and we also ensure those metrics are tight with our company’s greater goals and strategic plan. i.e. Are we striving for profitability or topline growth? Are we doubling down on finding more new customers or better retaining our current ones? Of course, we’d like to move all these metrics, but we know that’s naïve. In order for a growth team to be successful, they need to get a firm answer from the top of the company in terms of priorities. Everything can’t be equally important.</p><p><strong>How do you keep the team enthusiastic in the face of adversity — failed tests, etc.?</strong></p><p>For starters, again, I’d find people that are okay with being wrong a lot. And people who value “process mastery” and appreciate the journey vs. the finish line. Some people are demoralized when they’re wrong and others are stimulated by it. Because it moves them closer to the truth.</p><p>Outside of personality fit, we set the expectation upfront that it’s going to be a struggle. But that’s okay because most great achievements are the result of struggle and perseverance. We take a lot of pride in just staying determined and steady against hard problems.</p><p>At the end of the day, we remember we’re all in this together, and we’re all here for each other to lean on and get better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17607bb8d48" width="1" height="1" alt=""><hr><p><a href="https://medium.com/growthhackers/literally-everything-ive-learned-acquiring-1-617-418-customers-17607bb8d48">Literally Everything I’ve Learned Acquiring 1,617,418 Customers</a> was originally published in <a href="https://medium.com/growthhackers">Growth Hackers</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t Boo, Make]]></title>
            <link>https://romemike.medium.com/dont-boo-make-bc76aaeaae69?source=rss-5404fa7d32e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc76aaeaae69</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Michael Rome]]></dc:creator>
            <pubDate>Thu, 10 Nov 2016 15:27:27 GMT</pubDate>
            <atom:updated>2016-11-10T18:10:14.955Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*19aQCnvJg9MJygeQhR2Mog.png" /></figure><p>Attention all founders, makers, movers, and shakers:</p><p>Six years ago I left management consulting for “greener pastures”. I felt empty professionally, and needed a change.</p><p>From the moment I landed my first “office hours” with a gracious Chicago investor, I knew how I wanted to spend the rest of my working days — tech.</p><p>From this one meeting, I started landing lots of meetings with other software &amp; hardware dreamers, optimists, and believers — people with a spectacular blend of hustle, humility, and intellect that I hadn’t known existed. It was the type of people I didn’t just want to surround myself with each day, but the type of person I wanted to become.</p><p><strong>But above all else, what’s most admirable about all of these extraordinary people is their burning desire to DO when most simply talk or complain.</strong></p><p>So today, I’m more excited to be part of tech than ever before. Because I know that regardless of political beliefs, the last couple of days have struck a deep nerve with many makers. The types of people hell-bent on <a href="https://medium.com/build-better-products/the-biggest-trap-for-founders-only-three-guys-are-talking-about-8f2b0b517682#.i18riao05">hacking on side projects</a>, solving morphine problems, and giving the middle-finger to big hairy audacious challenges and going heads-down on finding solutions.</p><p>It’s time to <a href="https://medium.com/@Romemike/the-golden-rule-of-growth-hacking-30390d535387#.w2tacm5a9">put in the work</a>.</p><p><strong>Don’t boo, make.</strong></p><p>-Mike</p><p><em>A special thanks to the amazing friends that helped inspire this post: Desiree Vargas Wrigley, Ethan Austin, John Haskell, Ariana Gibson, Ashley Groves, Dan Hirschberg, Chris McKeever, Nate St. Pierre, Stephanie Finken, and the greater GiveForward team. Sean Johnson, Jordan Katz, Colin Jones, Meredith Overmyer, Noah Manion, Becky Hogan, and all the other doers at Digital Intent. Elan Mosbacher, Nate Turner, Mike McGee, Emerson Spartz, Troy Henikoff, Kamil Chmielewski, Kaleigh Simmons, Brent Williams, Seth Kravitz, Julian Winternheimer, Andrew Cronk, Josh Evnin, Jeremiah Green, Jeff Judge and all of the other exceptional startup folks that have taught me along the way.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc76aaeaae69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Golden Rule of Growth Hacking]]></title>
            <link>https://romemike.medium.com/the-golden-rule-of-growth-hacking-30390d535387?source=rss-5404fa7d32e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/30390d535387</guid>
            <category><![CDATA[startup-marketing]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[life-learning]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <dc:creator><![CDATA[Michael Rome]]></dc:creator>
            <pubDate>Fri, 05 Aug 2016 15:08:10 GMT</pubDate>
            <atom:updated>2016-08-05T15:08:10.113Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oHrqf5V3uvq3VMYw1y6Mlw.jpeg" /></figure><p>“Growth is optional” (<a href="http://startupclass.samaltman.com/courses/lec06/">Thanks, Alex</a>).</p><p>Sounds crazy, right? That growth is simply left to one’s choice. Maybe crazy, but undeniably true.</p><p>Whether growth is learning how to test an onboarding flow, play an instrument, jump careers, or manage people for the first time, growth is optional.</p><p>These days there’s countless blog posts, webinars, and interviews touting the latest-and-greatest “microwave meal” strategy for growth — “Follow these three easy steps, and you’ll be swimming in cash”, or “have more customers than you’ll know what to do with”. But these one-size-fits-all, quick-fix headlines couldn’t be more of a disservice.</p><p>Thankfully though, there is one piece of timeless growth advice regardless of what industry you play in, your business model, how much money you’ve raised, etc.</p><p><strong>Real, sustainable growth comes down to one thing — you put in the work.</strong></p><p>People who grow personally or grow businesses share one thing — they put in the work. They commit to process. They finish things they start. They do the right thing when no one’s watching. They help a colleague when momentum is lost. They re-read the page when the learning isn’t realized— not because it’s expected, but because it’s who they are.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30390d535387" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Brexit & Andrew Mason Taught Me About Growing Startups]]></title>
            <link>https://medium.com/build-better-products/what-brexit-andrew-mason-taught-me-about-growing-startups-f15edaed0b13?source=rss-5404fa7d32e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f15edaed0b13</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Michael Rome]]></dc:creator>
            <pubDate>Wed, 06 Jul 2016 14:12:35 GMT</pubDate>
            <atom:updated>2016-07-06T14:12:35.038Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/898/1*ZpvPEwnl7Mxrh3LyRH3SIA.jpeg" /></figure><p>My brother called me last week, and he asked me what I thought of Brexit. I started to fumble a response — I guess I thought spending a couple of hours in a UK airport in 2010 qualified me to have an opinion.</p><p>But then I stepped back. I realized that all I knew about the “British withdrawal from the European Union” was that, well, the British withdrew from the European Union.</p><p>Shortly after, I caught this <a href="http://themacro.com/articles/2016/06/andrew-mason/">Andrew Mason-YC interview</a>. They asked him “what he believed that few people would agree with”. He said this, and it blew me away.</p><blockquote>It’s okay to not have an opinion about everything.</blockquote><p>While I’m still pretty reckless when it comes to giving opinions, I’ve started to be more conscious of the value in not having one at all — especially when it comes to growth and startups.</p><p>One of my favorite books is Traction — a book about frameworks for acquisition for Internet businesses. Two of the books <a href="https://medium.com/@yegg/78-takeaways-from-traction-book-1b44d2a03dda#.fhcb3wm4v">earliest and most important takeaways</a> are the following:</p><ol><li>Most founders consider using only traction channels with which they’re already familiar.</li><li>It’s hard to predict the traction channel that will work best.</li></ol><p>I’ve certainly been guilty of #1, only to then learn #2 too late. If you’re just sticking to what you know and executing tests based on what you already believe to be true, you’re probably leaving a lot on the table.</p><p>Growth is hard, but the pathway to growth is simple —</p><blockquote># tests run * test success rate * test impact</blockquote><p>In other words, <a href="https://growthhackers.com/growth-studies/high-tempo-testing-revives-growthhackers-com-growth">testing velocity is the lifeblood of growth</a>. More tests run means more thoughtful hypothesis, which leads to a) higher “success rates” and b) higher certainty around “impact”.</p><p><strong>If you’re not starting and finishing tests, nothing else matters. And few things get in the way more of putting things into the world than having too many opinions.</strong></p><p><a href="https://powered.by.rabbut.com/p/Nusp?c=1">Subscribe to my posts</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f15edaed0b13" width="1" height="1" alt=""><hr><p><a href="https://medium.com/build-better-products/what-brexit-andrew-mason-taught-me-about-growing-startups-f15edaed0b13">What Brexit &amp; Andrew Mason Taught Me About Growing Startups</a> was originally published in <a href="https://medium.com/build-better-products">manifold-group</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Startups SHOULDN’T Have Growth Teams]]></title>
            <link>https://medium.com/build-better-products/why-startups-shouldnt-have-growth-teams-57310ff06e18?source=rss-5404fa7d32e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/57310ff06e18</guid>
            <category><![CDATA[growth-strategy]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[growth-marketing]]></category>
            <dc:creator><![CDATA[Michael Rome]]></dc:creator>
            <pubDate>Tue, 24 May 2016 12:31:12 GMT</pubDate>
            <atom:updated>2018-02-18T14:44:05.608Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oUG3mQgNwCsHjXHvcRATBA.jpeg" /></figure><blockquote>Startups shouldn’t have growth teams. The whole company should be the growth team.</blockquote><p>While Alex Schultz isn’t the first person to infer <a href="http://www.paulgraham.com/growth.html">growth is everything</a> when it comes to new products, I like how he goes one step further and says <a href="http://startupclass.samaltman.com/courses/lec06/">growth is the whole company’s responsibility</a> (10 minutes into the video).</p><p>Currently, my team is working on growth for a new mobile app for a public company. We’re in the early days, so our North Star is retention. While we have $1M in the bank to spend, and while a lot of new companies would be envious of the cash position, the vast majority of that money will go untouched until we’re certain we’ve made something enough people want where users are happy.</p><p>While we’re making great progress, in the off chance we don’t get to <a href="https://medium.com/swlh/diligence-at-social-capital-part-1-accounting-for-user-growth-4a8a449fddfc#.upsxr1yd2">REAL product-market fit</a>, I’d much rather return the capital than spend it knowing acquisition without retention is no different than lighting money on fire.</p><p>From the outside, it probably looks like four different departments are building this product: engineering, design, marketing and customer service. But it’s exactly this line of thinking that smothers a product’s growth potential. Sure we all have different skill sets and experiences, but they’re all being applied to one thing — retention.</p><p>I could ramble on about how our whole team is responsible for growth vs. a select set of individuals who have outlandish LinkedIn titles like “growth master” or “marketing wizard”, but it’s easier to just tell you about what we all did yesterday.</p><figure><a href="http://digintent.com/growth-playbooks/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TgbTwsIHNhibFoAznCASzA.png" /></a></figure><h4><strong>Early Morning</strong></h4><p>Got into work and started the day catching up on customer support. Even though we’re still just a few thousand users, call-to-action requests around customer feedback are pervasive in-app. For this reason, it’s not uncommon to have hundreds of customers leaving us feedback daily.</p><p><em>As a team, we made the strategic decision of designing the user experience so it’s as simple as possible for customers to tell us what they think. Even though I’ve read plenty of stories about software companies hiding phone numbers or contact information to cut down on the amount of time spent reading, listening and responding to customers, I can’t think of a more dangerous way of cutting workload. Sure, not encouraging customers to contact you saves time on customer support. But then what’s this time spent doing? Likely speculating on what to build next in a conference room supported by little-to-no user feedback — another wonderful activity for lighting money on fire.</em></p><p>When some people think of customer support, they might think of a $10 an hour resource, or perhaps even an offshore solution. Nothing against affordable labor (we try to take advantage of it too), but I can’t think of someone I’d be more happy to pay handsomely in the early days than customer support. Here’s why —</p><h4><strong>Late Morning</strong></h4><p>In addition to reading and listening to customers and prompt response times, we take extra time “theming” all support responses. While the positive feedback is great for morale and momentum (and we quickly calculate “the share of customer feedback that’s positive” to have a rough pulse on how we’re doing), we spend very little time on what’s going well — mostly because it’s not actionable, unless “patting ourselves on the back” is considered actionable.</p><p>The theming comprises the foundation for our customer Pareto analysis — again, for actionable purposes, we leave out positive feedback. This analysis plots two things: (a) count of customer feedback by theme in descending order (primary vertical axis) and (b) the cumulative distribution function (CDF) of support requests (secondary vertical axis).</p><p>I’ve masked the themes, but you’ll get the idea. Despite twenty themes, the top three comprise 60% of all customer feedback and the top five, nearly 80%. If we can figure out ways to use our skills as designers, engineers, marketers, customer reps, etc., to resolve these top issues, there’s probably a pretty tight correlation to improving retention.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*XE_O5yiQ7JBif6hDJ3c5rw.png" /></figure><h4><strong>Early Afternoon</strong></h4><p>Now that we’ve quantified precisely what customers are telling us needs work, it’s time to call in the greater team, both other internal members as well as the client.</p><p><em>Another nice thing about the Pareto is it removes the bias of prioritizing work based on what customer is “screaming the loudest”. This way you’re not always calling “fire drills” having an engineer fix something solely because one customer dropped an f-bomb. While it might seem like an urgent issue if you’re the person having to deal with the feedback, the Pareto keeps us objective, especially given we’re still quite small with limited resources.</em></p><p>We present the findings and do a deeper dive into each specific theme. For example, let’s say one of the top themes had to do with “a poor onboarding experience”. What else can we conclude from the feedback? Using tactics such as <a href="http://www.writewords.org.uk/word_count.asp">word frequency</a> and <a href="http://werfamous.com/sentimentanalyzer/">sentiment</a> analysis, we can get a more granular view of the top issues specifically within onboarding.</p><p>Ultimately, the outcome of this exercise is a specific list of things to prioritize. Let’s say “improving onboarding” is one of those things. Intuitively, this might sound like an engineer or designer’s job. Sure it’s their job, but that’s shortsighted — if the goal is retention, and this is quantified as a top barrier to improving it, it’s everyone’s job. Every single person can do something to improve this.</p><p>If you’re customer support, perhaps you build a series of email onboarding templates to send the user immediately post-signup. Then you start testing the timing of this series (ideally using data to inform your hypothesis). If you can’t do this because you need someone technical to help with creating the templates, you just suck it up and do it manually.</p><p>If you’re a marketer, with a technical skill set, perhaps you figure out a way to help the person sending customer support emails to send them faster using automated tactics such as scripts to better sort through an inbox.</p><p>If you’re a designer, perhaps you go usability test around onboarding.</p><p>If you’re an engineer, perhaps you start mapping out the minimum viable way to test a design hypothesis while still getting a conclusive result.</p><p>If you’re none of these and think you’re off the hook, you better think again. You hop in customer support and you start lending a hand sending off onboarding emails manually.</p><h4><strong>Late Afternoon</strong></h4><p>With a list of priorities agreed upon and a list of tactics within these priorities outlined per team member, you create a shared document that notes precisely what time all of these things go live. Whenever anyone puts something into the world to help improve onboarding, they note the date, time and a brief description of the tactic — this way you have a much better shot at tying specific actions back to either increases or decreases in retention. Ideally, you already have a sprint cadence in place, and you establish consensus on all that’s to be done (and who’s responsible) in the next sprint in order to resolve this problem.</p><p>I mentioned that I’m happy to go on record saying whoever owns customer support in the early days should be one of the most well-paid people in your company. Sure, there’s the Steve Jobs rebuttal if you’re one of the few that’s able to offer products around a need people never realized they had, but for most of us, the customer has 95% of the answers. What the customer says should be the lifeblood of your roadmap and whoever is owning that holds the key to growth.</p><p>Mastering the stages of growth is hard (the first stage being product-market-fit), but the roadmap for getting there is simple. <a href="http://www.coelevate.com/essays/growth-is-optional">As with most things, it’s executing that’s the tough part.</a> Steady growth comes down to commitment and discipline around focusing everyone’s time on improving your North Star metric — and that’s too lofty a goal to leave on one person or a few individuals. The truth is, establishing a way to (a) capture, quantify and prioritize customer feedback (b) socialize these insights to the greater team and (c) create and commit to a roadmap that resolves your customers’ most pressing needs isn’t a “one person” or “one department” job — it’s all our jobs.</p><p>If you’re still reading this, thanks a lot, but you should probably be responding to customer emails.</p><p><a href="https://powered.by.rabbut.com/p/Nusp?c=0">Subscribe to my Medium posts</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57310ff06e18" width="1" height="1" alt=""><hr><p><a href="https://medium.com/build-better-products/why-startups-shouldnt-have-growth-teams-57310ff06e18">Why Startups SHOULDN’T Have Growth Teams</a> was originally published in <a href="https://medium.com/build-better-products">manifold-group</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Biggest Trap for Founders Only Three Guys are Talking About]]></title>
            <link>https://medium.com/build-better-products/the-biggest-trap-for-founders-only-three-guys-are-talking-about-8f2b0b517682?source=rss-5404fa7d32e1------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f2b0b517682</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Michael Rome]]></dc:creator>
            <pubDate>Fri, 08 Apr 2016 12:43:58 GMT</pubDate>
            <atom:updated>2016-04-12T13:13:21.897Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sgEnZuMi_4GVFQ65vUTg5g.jpeg" /></figure><p>Fred Wilson <a href="http://avc.com/2016/03/side-projects/">just quietly let the mic go</a>, and we should all listen up.</p><p>Before there were TV series about startups and tech offices well-equipped with Razor scooters + ping pong tables, there were side projects.</p><p>What side projects lacked in funding, they made up for in “problem passion” and grit.</p><p>There’s nothing glamorous about pulling 50 hour work weeks only to come home and “start your day”, begging strangers to user interview or writing code when friends are winding down and watching Netflix — but man is it exhilarating.</p><p>In addition to Fred, <a href="http://blog.samaltman.com/projects-and-companies">Sam Altman</a> and <a href="http://paulgraham.com/before.html">Paul Graham</a> have been talking about the magic of side projects for a long time. While I wish I had listened sooner, I’m thankful these guys have called bullshit on the biggest elephant in the cushy startup conference room:</p><blockquote>Because it’s so easy to get paid to be a founder on day one, we’re losing the stomach, will and authenticity to get through the inevitable roller coaster of building something great.</blockquote><p>Additionally, we’re starting companies around problems we don’t deeply care about — this in turn leads to lots of hollow startups. Hollowness when it comes to growth, but more importantly, hollowness when it comes to determination.</p><p>What if we ran a regression on the number of days a founder went without getting paid to understand its relationship to either being acquired or still being in business today? I’d be willing to bet we’d see an exceptionally tight correlation.</p><p>Every startup founder that’s been slogging it out long enough will tell you “It never gets easier.” If you manage to truly find product market fit, maybe you’re no longer worrying about making rent; instead though, you’re worrying about how to negotiate a larger office, or how to fire your first employee, or how to sustain growth off an ever-increasing base, or how to make it home in time for dinner with your family.</p><p>Starting a startup is fun. Sustaining a startup is grueling. Sure, there’s the off-chance you might sell, but that’s likely five to ten years out. In between, there’s countless sacrifices along the way. And if you’re among “the other 95%”, there’s all that same sacrifice only to ultimately wind down something you’ve put more into than potentially anything else in your life.</p><p>Why on earth should anyone commit to this? Simple — <a href="http://startupclass.samaltman.com/">because you can’t not do it</a>. Because if you don’t, then who will? This reasoning is similar to the makings of great side projects. It’s not done for the fame, or the fortune, it’s done for the love of making something that might not exist without you.</p><p><strong>Thanks</strong> to Ethan Austin and Sean Johnson for reading drafts of this.</p><p><a href="https://powered.by.rabbut.com/85c37c77-75ae-4e6c-a4d1-81b341bc7d42?c=0">Subscribe to my Medium posts</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f2b0b517682" width="1" height="1" alt=""><hr><p><a href="https://medium.com/build-better-products/the-biggest-trap-for-founders-only-three-guys-are-talking-about-8f2b0b517682">The Biggest Trap for Founders Only Three Guys are Talking About</a> was originally published in <a href="https://medium.com/build-better-products">manifold-group</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>