<?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 Éamon Cullen on Medium]]></title>
        <description><![CDATA[Stories by Éamon Cullen on Medium]]></description>
        <link>https://medium.com/@eamoncullen?source=rss-71cac2cfe29d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*08RgBzB8xI0XnMPqWqV-7g.jpeg</url>
            <title>Stories by Éamon Cullen on Medium</title>
            <link>https://medium.com/@eamoncullen?source=rss-71cac2cfe29d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:10:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eamoncullen/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[Why product managers should think more like entrepreneurs]]></title>
            <link>https://eamoncullen.medium.com/why-product-managers-should-think-more-like-entrepreneurs-aab16837e14?source=rss-71cac2cfe29d------2</link>
            <guid isPermaLink="false">https://medium.com/p/aab16837e14</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Éamon Cullen]]></dc:creator>
            <pubDate>Wed, 22 Sep 2021 14:27:58 GMT</pubDate>
            <atom:updated>2021-09-22T14:27:58.376Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s essential for entrepreneurs to be obsessed with perfecting the small details of their product while simultaneously understanding how it will fit into the wider economic, social, technological, legal, and political picture.</p><p>If entrepreneurs don’t possess this multi-dimensional view, it’s only a matter of time before the company hits an unforeseen roadblock and the company suffers.</p><p>Elon Musk is capable of discussing the finest details of a Tesla car battery while simultaneously plotting to shoot that same car into outer space. To make this happen, there are so many factors at play. It requires broad expertise, deep knowledge, and an ability to tie the two together.</p><p>So what can product managers learn from entrepreneurs? In a word — <em>Responsibility</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9bYj4ir7l4QBu-sRRPNliQ.jpeg" /></figure><p>Most product managers consider themselves entrepreneurial; they like thinking about ideas and seeing them play out. But to be a great product manager, it’s essential that they expand their role beyond what’s written in the job description.</p><p>Most product managers can come up with solutions to user problems, but can they account for the salary costs of their engineers when proposing the solution?</p><p>Most product managers can pitch an idea, but can they understand that their new feature could affect usage of the existing cash cow or overwhelm the customer service team?</p><p>Most product managers can improve the UI, but can they foresee how upcoming policy changes could render their efforts useless?</p><p>Product managers have garnered the nickname “mini-CEO” because a CEO — just like an entrepreneur — must be multivariant, prepared for everything and anything, and accountable. It’s the job of a product manager to be the eyes are ears of the company.</p><p>Product managers, like entrepreneurs, need to be scrappy to get things done. They need to push the envelope on what’s possible and be resourceful when everything is against them.</p><p>The best product managers, like entrepreneurs, put the company’s interest before their own. They are often confronted with potential quick wins to make themselves look good at the expense of the long-term company strategy.</p><p>The best product managers don’t take the bait. They openly share and communicate the challenges and opportunities they foresee down the road; challenges that may arise long after the product manager has left the company. They share concerns and initiate dialogues to bring awareness to the problems that lurk in the dark.</p><p>The best product managers have a willingness to take responsibility for grey areas where others proclaim “that’s not my job.”</p><p>The best product managers think like entrepreneurs and often become them.</p><p>—</p><p>Stack ranking helps hundreds of product managers to foresee their users’ biggest problems and pain points. In under 5 minutes, you can create a stack ranking survey on <a href="http://opinionx.co/">OpinionX</a> and learn exactly what problems you should prioritize solving next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aab16837e14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: How stack ranking saved us from building the wrong product]]></title>
            <link>https://medium.com/the-full-stack-researcher/case-study-how-stack-ranking-saved-us-from-building-the-wrong-product-47328ddb03db?source=rss-71cac2cfe29d------2</link>
            <guid isPermaLink="false">https://medium.com/p/47328ddb03db</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[surveys]]></category>
            <dc:creator><![CDATA[Éamon Cullen]]></dc:creator>
            <pubDate>Thu, 12 Aug 2021 11:13:07 GMT</pubDate>
            <atom:updated>2021-08-12T13:48:53.128Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0IkC7_kOYc-b_trSII0mnw.png" /></figure><p>80% of new features are rarely or never used. Back in May 2021, we <em>almost</em> fell victim to that statistic…</p><p>After a handful of identical requests from users in quick succession, we were on the verge of committing 3-months of development time to a huge new feature that we believed would fix a fatal flaw in our product funnel (spoiler, we were wrong).</p><p>This post explores the last minute experiment that saved us months of precious time and tens of thousands of Euro building the wrong thing.</p><h3>An obvious solution to our funnel woes</h3><p>In April 2021, after months of pivoting, we had finally landed on a proposition that was resonating with customers. Sign ups were surging and buzz was starting to build about our stack ranking tool that could help startups to validate their ideas and find product/market fit faster. But we had one major problem — people weren’t sending their stack rank surveys out to participants.</p><p>Within just a few weeks, we started to hear the same feature request over and over again; our users wanted the ability to buy participants for their stack rank surveys.</p><p>These requests instantly felt reassuring to us, like <em>‘Hey, this problem isn’t to do with OUR product, it’s just that these early-stage founders don’t have users yet to participate in their stack rank surveys!</em> 😅’</p><p>With this obvious solution handed right to us, we eagerly set off to get demos of the top tools for recruiting survey participants. Within a week, we had narrowed our list to the top 2 and were talking to their integration specialists about how we could build this feature into OpinionX.</p><h3>Cue the cold feet…</h3><p>The only thing that stopped us from moving ahead was the price tag — we needed to commit all our developer resources for at least 3-months to get this feature built. As an early stage startup, our vocabulary had always been in days or weeks. We had never committed to anything before that would require so much time.</p><p>We asked the integration specialists to give us a couple of days to confirm that we would definitely be continuing ahead with the project and we set about validating that this was the right project to work on. How would we validate that?</p><p>Well, we came to the conclusion that a feature demanding this much of our resources needed to solve the biggest problem our customers faced, otherwise we should be working on something else. It felt obvious to us that the right method to use was Customer Problem Stack Ranking — getting our users to vote on pairs of problem statements so that we could measure which ones were most important to them.</p><h3>Starting our stack ranking experiment</h3><p>Getting started was super easy; in under 30 minutes we wrote out the top 20 problems that users were experiencing — including a problem statement on the difficulty of finding participants — and added them to an OpinionX stack ranking survey. Then we grabbed the link and sent our stack ranking survey out to our most engaged users from the previous 6 weeks.</p><p>Over the following two days, users cast almost 800 votes and submitted 33 new problem statements to our stack ranking survey. It was immediately clear to us — not only was recruiting participants wasn’t the most important problem, it wasn’t even near the top of the stack rank.</p><h3>Understanding the results</h3><p>Digging into the data, we realized that we had blended together two completely different customer segments within our userbase: early-stage founders that were mostly pre-product and focused on idea validation, and product managers at scaling tech companies with existing userbases that were using OpinionX to prioritize their roadmaps and add quantitative data to their product discovery.</p><p>Once we split these two segments out, we realized that even if we did spend 3+ months building the panel recruitment integration, these early-stage founders didn’t have the money to pay for participants and wouldn’t end up using OpinionX often enough to become paying customers.</p><p>This stack ranking experiment didn’t just help us to avoid working on the wrong feature. It also showed us the most important problems to be working on and gave us the first clue that we needed to improve our understanding of our ideal target customer.</p><h3>What we learned:</h3><p><strong>1. Diagnose the problem that underpins each feature request.</strong></p><p>People like to be nice. When they have a problem with your product, the easiest way to raise the issue with you is to dress that problem up as a potential solution. Feature requests are a route to understanding the barriers in your product, not a pipeline of ideas to fill your roadmap with.</p><p><strong>2. Focus on the right customers.</strong></p><p>When you’ve got a giant userbase, a rich product analytics dataset, and a skilled data analyst, behavioral segmentation is a breeze. That’s not the case for most startups. We chased the wrong problem because we didn’t realize who had that problem (and more specifically, who didn’t).</p><p>Needs-based segmentation is vital — we’ve since added the ability to include multiple-choice questions in your stack rank survey so that you can segment your results to better focus on the customers that matter most.</p><p><strong>3. Make decisions with data, not anecdotes.</strong></p><p>Anecdotes and qualitative research are vital for understanding why people behave the way they do. But these methods also lead us astray so easily. Using a stack ranking tool like OpinionX gave us the best of both worlds — participants added new opinions to help us discover unknown problems and the stack ranking results gave us quantitative data for more informed decision making. Win win :)</p><h3>Stack Ranking</h3><p>Creating a similar stack ranking survey to the one we used in this project takes less than 5 minutes and is completely free. Before building that big new product or feature, check if it’s really solving the most important problem that you should be focused on. <a href="http://app.opinionx.co/sign-up"><strong>Start building your first stack ranking survey for free here</strong></a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47328ddb03db" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-full-stack-researcher/case-study-how-stack-ranking-saved-us-from-building-the-wrong-product-47328ddb03db">Case Study: How stack ranking saved us from building the wrong product</a> was originally published in <a href="https://medium.com/the-full-stack-researcher">The Full-Stack Researcher</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: How stack ranking made Animoto rethink the problem they were solving]]></title>
            <link>https://medium.com/the-full-stack-researcher/case-study-how-stack-ranking-made-animoto-rethink-the-problem-they-were-solving-73b77ebeeb7b?source=rss-71cac2cfe29d------2</link>
            <guid isPermaLink="false">https://medium.com/p/73b77ebeeb7b</guid>
            <category><![CDATA[surveys]]></category>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Éamon Cullen]]></dc:creator>
            <pubDate>Thu, 12 Aug 2021 11:06:33 GMT</pubDate>
            <atom:updated>2021-08-12T12:53:48.912Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*esxy0OgiKYTexm1ofGg2aA.png" /></figure><p>The discovery phase is the most impactful part of any new project; it sets the direction and locks in the insights that will shape the product that your teams builds. But what happens when, after months of user interviews, you realize that what people told you was their biggest problem isn’t actually their top priority at all? Well that’s exactly what happened to Micah Rembrandt during the summer of 2021…</p><p>Micah is a Senior Product Manager at Animoto, the easy-to-use video creator with over 130,000 paying customers around the world. Even though Animoto is a giant in the video marketing space, Micah has been leading a discovery research effort to understand more about the broader video production process and the pains that people feel throughout it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*2DGCI5aCkKKwmxNdCruGHg.jpeg" /><figcaption>Team Animoto on tour ⛵</figcaption></figure><p>Micah and his team started off by talking to marketing people about the video production process and quickly found a bunch of technical challenges they faced, many of which centred around video editing. Animoto is a data-driven company though, and as Micah explained…</p><blockquote>“Data is more telling than people’s opinions. Stack ranking as a methodology is more rigorous than straight-up asking.”<em> — Micah Rembrandt, Senior Product Manager at Animoto.</em></blockquote><p>When people hear about stack ranking, they picture a survey question with 5 or 6 options that they drag into order, or a workshop with a bunch of post-it notes ranked in order on a wall. Using these types of stack ranking come with a bunch of limitations though, which is what has prevented Micah from using them in the past.</p><blockquote>“In the past, stack ranking has been very hard to analyze — especially with bigger audiences. Giving people a list of 10+ things to rank is overwhelming and leads to unreliable data. Doing it all manually leaves me dealing with the complex math to summarize the results.”<em> — Micah Rembrandt, Senior Product Manager at Animoto.</em></blockquote><p>Instead of those traditional ranking methods, Micah decided to try OpinionX — which uses a different method of stack ranking where participants are shown two options at a time and they pick the one that is more important to them. For Micah, the OpinionX approach wasn’t just easier for his research participants, it also gave him much more robust comparative data.</p><p>As the final step of his initial discovery phase, Micah created a stack ranking survey on OpinionX to validate his findings with hard data. He added the top 12 problem statements to his survey and sent it out to 52 people that fit his target customer profile. Pretty quickly, Micah realized that the results were not coming out as expected…</p><blockquote>“All of our other data was pointing to stuff at other points in the journey. We had no data that getting approval was hard — yes people have to do it, but they just send an email or something. When we ran our OpinionX, it came back as the most frustrating part for people. The data really illuminated that it wasn’t a technical issue, it was a people issue. It reformatted how we thought about our whole approach; people don’t struggle with the tech for giving feedback, they struggle with giving others their feedback.”<em> — Micah Rembrandt, Senior Product Manager at Animoto.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-PJ4yJyLxVwdMQ8QR41nLg.png" /><figcaption>^ What stack ranking results look like on OpinionX (it’s super simple!)</figcaption></figure><p>Micah and his team decided to take this new insight back into user interviews to explore what it meant to people and to figure out why it hadn’t appeared more prominently in their previous research.</p><blockquote>“Through our follow up research, this problem kept coming up as something that’s really painful for people. It’s hard to ask people the straight-forward question of what they want, because people don’t always know how to necessarily articulate what they want. The underlying needs apart from what people were articulating were what stack ranking helped us to find.”<em> — Micah Rembrandt, Senior Product Manager at Animoto.</em></blockquote><p>The most surprising part about Micah’s story is that he never intended to include a stack ranking step in his research; in fact, he fully intended on skipping it.</p><blockquote>“I wouldn’t have done the stack ranking without OpinionX. I have quantitative skills but I’m not a data analyst and my team didn’t have access to one for this part of our process. Analyzing manual stack ranking is just too much to take in, in my experience, so we wouldn’t have done it given the scope and timing of this project. Who knows where this project would have ended up if we didn’t know about OpinionX…”<em> — Micah Rembrandt, Senior Product Manager at Animoto.</em></blockquote><p>Companies love to say that they’re data-driven; product analytics give them the numbers they need to optimize conversion, tweak onboarding, and improve retention. But when it comes to what they build next and how they manage their product roadmap, decisions are made using internal assumptions, back-of-napkin prioritization maths, and ‘product intuition.’</p><p>Join the hundreds of product teams like Micah’s that are using OpinionX to make product decisions using real data, by ranking users’ priorities during product discovery and roadmap prioritization (<a href="https://www.opinionx.co/blog/case-study-gnosis-uses-opinionx-to-ditch-internal-assumptions-in-favor-of-user-driven-roadmap-prioritization">like Kristina at Gnosis Safe</a>). Create your own stack ranking survey for free in under 5 minutes today with OpinionX. <a href="http://app.opinionx.co/sign-up"><strong>Get started here</strong></a><strong>.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73b77ebeeb7b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-full-stack-researcher/case-study-how-stack-ranking-made-animoto-rethink-the-problem-they-were-solving-73b77ebeeb7b">Case Study: How stack ranking made Animoto rethink the problem they were solving</a> was originally published in <a href="https://medium.com/the-full-stack-researcher">The Full-Stack Researcher</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Case Study: Gnosis uses OpinionX to ditch internal assumptions in favor of user-driven roadmap…]]></title>
            <link>https://medium.com/the-full-stack-researcher/case-study-gnosis-uses-opinionx-to-ditch-internal-assumptions-in-favor-of-user-driven-roadmap-c53a292b8f44?source=rss-71cac2cfe29d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c53a292b8f44</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[product-manager]]></category>
            <dc:creator><![CDATA[Éamon Cullen]]></dc:creator>
            <pubDate>Thu, 12 Aug 2021 10:59:11 GMT</pubDate>
            <atom:updated>2021-08-12T12:51:23.460Z</atom:updated>
            <content:encoded><![CDATA[<h3>Case Study: Gnosis uses OpinionX to ditch internal assumptions in favor of user-driven roadmap prioritization.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YvNKF_O-7lWoJO-kg-9dRw.png" /></figure><p>Prioritizing your product roadmap is a difficult task for product teams of all sizes, but when you’re paving the way in an emerging industry and dealing with customers ranging from individual consumers to millionaire traders and multinational companies, those prioritization challenges become a different beast altogether.</p><p>When we met UX Researcher Kristina Mayman in mid 2021, the product team at Gnosis Safe was starting to realize that their internal DIY methods for prioritization weren’t giving them the data they needed to confidently validate their roadmap decisions. As a data-driven team, Gnosis Safe was looking for better sources of data to inform their roadmap prioritization. That’s where OpinionX came in…</p><p>Gnosis is a crypto startup founded in 2015 that has a range of Ethereum infrastructure products. With $12M in funding raised in 2017 they are a defining voice in the cryptocurrency world. Their products include Gnosis Safe (the Web3 operating system, which stores $46 billion USD in ETH and ERC20s) and Gnosis Protocol v2 (which leverages batch auctions to provide MEV protection plus integration with liquidity sources across DEXs to offer traders the best prices).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tAiTTiunC-Yaq-4M7WoaHw.png" /><figcaption>Martin Köppelmann, CEO and Co-Founder of Gnosis.</figcaption></figure><p>Before they started using <a href="http://opinionx.co/">OpinionX</a>, Kristina told us that team at Gnosis Safe had a “pretty lengthy process” to decide on what they would prioritize each quarter:</p><blockquote>“We look through our internal user research database and say — ‘ok, I saw people mention X or Y more often, this seems like a big issue.’ We would discuss, triage and prioritize that list internally, but overall this was not a very solid approach to saying which things should be prioritized.”<em> — Kristina Mayman, UX Researcher at Gnosis Safe.</em></blockquote><p>Over the past few months, I’ve heard this same process play out at countless scaling startups. When it comes to optimization, startups have product analytics data down to the individual pixel to inform their decisions, but for new product development, those same data-driven companies revert to internal voting and workshops.</p><p>When Kristina and Product Manager colleague Lukas came across OpinionX, they initially saw it as a better method to understand internal priorities. The team worked together to build a list of 30 user-facing problems which they added to a stack ranking survey on OpinionX and sent throughout the company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gs-91OoxjBQicsatrYhpfw.jpeg" /></figure><p>Once the results started coming in, they realized that the same simple stack ranking process carried out with users rather than colleagues would yield even more valuable data. Kristina wasn’t alone — their internal test was the perfect way to get buy-in from the team for an external stack ranking pilot.</p><blockquote>“It really helped that the OpinionX survey is so short; you can go through it in a few minutes. Being able to add a column to our roadmap that sorts the whole thing by what users say is most important to them is so easy and clear for the team. It definitely gives us more confidence in our roadmap planning.”<em> — Kristina Mayman, UX Researcher at Gnosis Safe.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z-_g_vsL6t-TCmihCXfL3g.png" /><figcaption>Kristina and the product team at Gnosis Safe used a simple Intercom banner to source users for their stack ranking survey.</figcaption></figure><p>How did Kristina go about encouraging users to participate in the stack ranking? By adding a simple Intercom banner within the product, Gnosis Safe had 114 users jumping in to share their opinion on the list of problems the team had built. Not only that, but those same users submitted an extra 55 problem statements to help the Gnosis Safe team to discover new problems that they might have missed during their internal planning.</p><blockquote>“Our roadmap is a living document that’s always changing, but every three months we clear the backlog and start with a clean slate. Within two or three weeks of launching a new roadmap, we’re focused on the next one. The team are already thinking about how we’ll use OpinionX again and how we could use stack ranking for ongoing user-driven prioritization and engagement.” — Kristina Mayman, UX Researcher at Gnosis Safe.</blockquote><p>If your roadmap prioritization is driven by internal assumptions, politics, or DIY calculations, OpinionX is a simple but powerful way to put your users and measurable data back at the heart of your product decisions. <a href="http://app.opinionx.co/sign-up">Start building your first stack ranking survey for free today with OpinionX</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c53a292b8f44" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-full-stack-researcher/case-study-gnosis-uses-opinionx-to-ditch-internal-assumptions-in-favor-of-user-driven-roadmap-c53a292b8f44">Case Study: Gnosis uses OpinionX to ditch internal assumptions in favor of user-driven roadmap…</a> was originally published in <a href="https://medium.com/the-full-stack-researcher">The Full-Stack Researcher</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We can’t all be Jeff Bezos, but maybe we could be Matin Movassate?]]></title>
            <link>https://eamoncullen.medium.com/we-cant-all-be-jeff-bezos-but-maybe-we-could-be-matin-movassate-7b07709dbbae?source=rss-71cac2cfe29d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b07709dbbae</guid>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[jeff-bezos]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Éamon Cullen]]></dc:creator>
            <pubDate>Mon, 05 Jul 2021 17:39:29 GMT</pubDate>
            <atom:updated>2021-07-05T17:39:29.136Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xh3zImZ5BZ6gX6UQ-iVHNg.jpeg" /></figure><p>Jeff Bezos — like him or hate him — is a true visionary.</p><p>He identified the oncoming e-commerce tsunami and was able to surf it better than anyone. In doing so, Amazon changed the world.</p><p>Apple, Uber, SpaceX, Airbnb and Tesla are among others that changed the world.</p><p>They changed the world by betting big on radical ideas that offered high risk and high rewards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OsGVHnM84RBmAP5A27J0-Q.jpeg" /></figure><p>But stories of wildly successful entrepreneurs can give us a distorted view of entrepreneurship. I’ve noticed this among many aspiring founders. They focus exclusively on finding revolutionary new ideas. While this is admirable, it tends to lead to one of two situations.</p><ol><li>They become overwhelmed and burdened by their own expectations of themselves.</li><li>They try to execute on something big and fail to achieve their grand vision.</li></ol><p>This reality causes many would-be entrepreneurs to give up their ambitions for the security of a comfortable corporate lifestyle.</p><p>But it doesn’t have to be this way.</p><p>Instead, ambitious entrepreneurs can reduce their risk by following the well-trodden path rather than being the first to wade through the thickest part of the unexplored jungle. By no means does it guarantee success, but it increases the likelihood.</p><p>Replicate and differentiate is the name of this game. And the goal is to build a business that can survive the startup odds and allow you to live without a lifelong feeling of regret.</p><h3>Replicate</h3><p>It’s always easier to start a company by improving an existing product.</p><p>This can be a hard pill to swallow. There is a deep part of every person’s soul that rebels; <em>I am unique and special. What if I am capable of being a true change-maker, a maverick, a world-beater?</em></p><p>There are times when this rebellious voice should be listened to. When partnered with genuine insight, it is what propels truly great companies. Steve Jobs couldn’t have accomplished what he did without it.</p><p>There are also times where feelings of grandeur disrupt work ethic and distort what could be humble but excellent.</p><p>There are many companies that receive little media attention and put food on the table for hundreds of people. They have extremely happy customers and play their part in incrementally pushing the boundaries of what’s possible.</p><p>These companies weren’t founded because of a unique groundbreaking insight but instead by steadily improving existing technology.</p><p>There are also times when the copycat company surpasses its predecessor. <a href="http://kickstarter.com/">Kickstarter</a> was not the first crowdsourcing platform. Instead, they replicated the model of <a href="http://indiegogo.com/">Indiegogo</a> and put their own unique spin on it with tech-focused projects and better rewards for donors. Almost half a million products have launched on the platform since its founding in 2009.</p><p>Acquisition is also a very real possibility. In 1999, the Samwer Brothers developed Alando — a German copycat to American online auction site eBay. Within four months, eBay purchased Alando for $43 million.</p><p><em>Trying to find product/market fit? </em><a href="https://www.opinionx.co/newsletter"><em>Subscribe</em></a><em> to our fortnightly newsletter for top tips and tricks.</em></p><h3>Differentiation</h3><p>Once you’ve found the space you’re interested in, the second half of the formula is to differentiate. Your differentiation will become your core value proposition and the reason that customers should pay attention to what you’re doing.</p><p>Take Heap for example — a website and product analytics tool. From this description, you can probably name half a dozen other products just like it: Google Analytics, Mixpanel, Amplitude, etc.?</p><p>It can be hard to understand how this company has raised almost $100M and secured over 6,000 customers, many of which are global leaders in their field. Isn’t it just the same?</p><p>Heap replicated the basic value proposition of competing analytics platforms — <em>track your users’ behavior and identify areas where you can improve — </em>but Heap differentiated one very important step.</p><p>When <a href="https://twitter.com/matinm1?lang=en">Matin Movassate</a> was working for Facebook he experienced just how difficult it was to use analytics. He described his experience with analytics tools as “a big pain in the ass”.</p><blockquote>If you have very simple questions about your product, questions like: how many users use this feature? What are the common flows they take after using this feature? Those types of things require literally months of time. And if it takes months to go from question to answer, guess what? You’re not going to use data to answer questions as much anymore.</blockquote><blockquote>So, the realization that we had with that experience was, if it’s this difficult to make good use of data at a place like Facebook, then what hope does the rest of the world have to use data effectively and to achieve this glorious data-informed future that everybody heads up?</blockquote><blockquote>We decided to rethink analytics from the ground up.</blockquote><p>Matin was then able to take this insight to build the first tool of its kind. Instead of manually choosing which events to track and installing code to track each, Heap would automatically identify and track events and with just one simple block of code.</p><p>That’s not to say that it was easy:</p><blockquote>I remember early on, I was trying to get advice on how to approach this problem from somebody who had worked on the Google Analytics team. First, they told us, “You can’t do this. This is unsolvable. This won’t work. Give up now”.</blockquote><h3>How to replicate and differentiate</h3><p>Although you are following a proven business model, the process of <em>Replicate and Differentiate</em> is no walk in the park. It requires a lot of research.</p><h3>Replicate</h3><p>The first step of replication is to research a company you can model yourself off of. The company needs to be solving a real problem with paying customers. This is the proof you need that there is a market need for the solution, reducing part of the risk associated with new startups ideas.</p><p>You can use the following sites to search for companies:</p><ul><li><a href="http://crunchbase.com/">Crunchbase</a></li><li><a href="http://linkedin.com/">LinkedIn</a></li><li><a href="http://startupstash.com/">Startupstash</a></li><li><a href="http://index.co/">Index.co</a></li></ul><p>Another great way to find opportunities is to look abroad and see what businesses are successful but haven’t yet arrived in your country. This is what the Samwer Brothers did with Alando. When interning in Silicon Valley, they saw the opportunity to generate significant profit by providing a similar site to eBay but in Germany.</p><p>Questions you should be asking yourself when searching for companies include:</p><ul><li>Is there high-profit margin?</li><li>Are there many other competitors?</li><li>How difficult is it to build the technology?</li><li>Does my founding team have the skillset to run this business?</li><li>What does the future hold for this industry?</li></ul><h3>Differentiate</h3><p>The next step is to differentiate yourself through a unique value proposition.</p><p>The best way to differentiate yourself is to find a problem that your competing company is overlooking or underperforming on. In the case of Heap founder Matin Movassate, the problem was that the analytics tools he was using were painfully difficult to setup and took a long time until event tracking yielded results.</p><p>Melanie Perkins, the co-founder of the graphic design platform Canva, has a similar story. She discovered when teaching design to students that tools like InDesign and Photoshop weren’t very accessible. This led her to build tools to compete with the design tools she knew so well by offering an easier-to-use alternative.</p><p>So how do you find a unique problem or underserved niche?</p><p>Ideally, you experience a problem firsthand and are determined to fix it. But you can also discover problems within any area that you are interested in using simple research methods. You just need to find a bunch of similar people who use the product that you are replicating (or similar products) and then ask them to rank problems they experience in order of importance.</p><p>This way you can see exactly which problems are ranking highest for the largest segment of people. This is a major clue about which problems — if solved — will allow you to differentiate in a way that customers will appreciate.</p><p>The process of asking people to rank problems is called <a href="http://opinionx.co/blog/customer-problem-stack-ranking">Customer Problem Stack Ranking</a>. Luckily, you no longer have to do this manually as we built <a href="http://opinionx.co/">OpinionX</a> to do it without the hassle.</p><p>With OpinionX, you can see what each of your stack ranking participants voted on or submitted. Once you’ve picked a high ranking problem to focus on, you can follow up with individual participants for in-depth interviews to dig even further into the root of the issue.</p><p>By this point, it will be clear to you where your competitors are falling short and what problems they aren’t addressing well enough. Their inaction is your opportunity.</p><h3>Follow The Startup Bowtie</h3><p>Instead of jumping into building a product too soon, you should methodically follow a proven process to find Product-Market Fit. The <a href="https://www.opinionx.co/blog/startup-bowtie">Startup Bowtie</a> is a step-by-step checklist to help you focus on the most important decisions first. The left hand side of the bowtie leads founders to “the pull point” — the first important milestone in finding Product/Market Fit — which is when you get your first signal that you’ve got a product that an identified group of people really need.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5HubD8c0viqJd4krGP7O7g.png" /></figure><p>Let’s use Heap and Canva as examples to walk through the four steps leading to the pull point:</p><p><strong><em>Persona<br></em></strong>The more specific you can be when choosing your target persona, the better. Each different group of people experience the same problem in slightly different ways and need their own personalized solution. If you try to solve that problem for everyone, you’ll end up adding no value for anyone.</p><p>Heap initially targeted directors of analytics at scaling tech companies.</p><p>Canva focused on non-designer professionals like marketers at SMBs.</p><p>You can begin expanding your target persona once you have nailed your initial segment. Until then, you need to focus on just one.</p><p><strong><em>Problem<br></em></strong>You will either have identified the problem you are going to solve through personal experience or by using a stack ranking tool like <a href="http://opinionx.co/">OpinionX</a>.</p><p>Heap’s founder knew from personal experience that manually setting up analytics events was time-consuming and complex.</p><p>Melanie at Canva saw first hand how much time and effort it took to teach people how to use design tools.</p><p>Push yourself to articulate your problem statement in one quick sentence.</p><p><strong><em>Proposition<br></em></strong>For the Replicate &amp; Differentiate approach, your value proposition is where you communicate your differentiation. A good proposition is generally the inverse of the problem you are solving.</p><p>For Heap, “Manually tracking analytics events is time-consuming and difficult” becomes “Automatically track events without the need for code”</p><p>And “design tools are inaccessible” becomes “Use drag-and-drop features to create beautiful designs.”</p><p>Since your target audience has already told you that this is one of their big problems, you should stick this value prop right at the top of your website to grab their attention.</p><p><strong><em>Product<br></em></strong>It’s only at this final stage of the process that you consider building a minimal viable product (MVP).</p><p>Building an MVP is easier today than ever before. With no-code apps like <a href="http://bubble.io/">Bubble</a>, you often don’t even need to be able to code in order to build a functional product.</p><p>If no-code doesn’t cut it, then try and get some mock-ups in front of customers first using tools like <a href="https://www.figma.com/">Figma</a>, <a href="http://marvelapp.com/">MarvelApp</a> or <a href="http://invision.com/">InVision</a>.</p><p>Don’t spend too much time making it perfect. Instead, build something that is functional and get it in front of users as soon as possible. Then iterate over and over until you have a product they love.</p><p>Peace ✌️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b07709dbbae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You Built A Product Nobody Wants: 7 Steps To Save Your Startup]]></title>
            <link>https://eamoncullen.medium.com/you-built-a-product-nobody-wants-7-steps-to-save-your-startup-295544c48931?source=rss-71cac2cfe29d------2</link>
            <guid isPermaLink="false">https://medium.com/p/295544c48931</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Éamon Cullen]]></dc:creator>
            <pubDate>Thu, 01 Jul 2021 19:45:13 GMT</pubDate>
            <atom:updated>2021-07-01T19:45:13.116Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y_JekWADA2nA1KMEEB00Dw.png" /></figure><p>Find a big problem.</p><p>Build a great solution.</p><p>Onboard lots of customers.</p><p>It’s the perfect startup story. But it’s not your story…</p><p>Instead, you built a product that nobody wants.</p><p>So now what…?</p><p>Well, you have two options:</p><ol><li>Give up and try something else.</li><li>Bite, scratch and claw your way back until you find Product/Market Fit.</li></ol><p>Assuming you’re up for the challenge, you’ll need a strategy. That’s what you’re going to find in this guide.</p><h3>What is Product/Market Fit?</h3><p>The definition of Product/Market Fit is often debated but the description from Marc Andreesen (who first coined the term) provides everything we need to know:</p><blockquote><strong>You can always feel when product/market fit isn’t happening.</strong> The customers aren’t quite getting value out of the product, word of mouth isn’t spreading, usage isn’t growing that fast, press reviews are kind of “blah”, the sales cycle takes too long, and lots of deals never close.</blockquote><blockquote><strong>And you can always feel product/market fit when it is happening.</strong> The customers are buying the product just as fast as you can make it. Money from customers is piling up in your company checking account. You’re hiring sales and customer support staff as fast as you can. Reporters are calling because they’ve heard about your hot new thing and they want to talk to you about it.</blockquote><p>If you are reading this guide, you have built a product but haven’t yet found Product/Market Fit.</p><h3>The good news</h3><p>Lots of companies you know to be successful started with a product that nobody wanted. Then, through deep introspective work, attentive listening and strategic iteration, they made a successful pivot.</p><p>You see, your idea might be good — or at least a part of it might be good. It’s possible you just haven’t found the right customer segment or positioning that’s attractive to prospective customers. <em>You could be halfway there and you don’t even know it.</em></p><p>Finding Product/Market Fit can take anywhere from a few months to years. It’s only through patience, iteration and persistence that most companies find it.</p><p>In this post, I will show you a method that squeezes every drop of insight from your idea to extract what is valuable and eliminate what isn’t. This method will give your startup the best chance of success.</p><h3>The bad news</h3><p>It’s also possible you are waaaay off course and your perception of what people need is all wrong. As much as 80% of new companies build products that are never really used by anyone and the number one reason is that they solved problems that nobody cared about.</p><p>If nobody wants your product then finding Product/Market Fit is extremely painful. It turns into a tough period of soul searching and rejection. It’s especially painful if you have already invested a huge amount of time and effort into your idea.</p><p>Then, even if you do identify a segment that experiences the problem that your product solves, you will likely have to dump a huge portion of your code and reinvent your product.</p><p>All you need to do now is follow the step-by-step process laid out in this guide and it will either make it crystal clear that your idea isn’t needed or reveal a lucrative opportunity lurking right under your nose.</p><p>Following these steps will give you the best chance of a successful pivot.</p><h3>Case Study</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JHP621xgdOrBHG1iAcoz7A.png" /><figcaption><a href="https://twitter.com/friedberg">David Friedberg</a>, Former Startup Founder and Co-Host of the <a href="https://www.allinpodcast.co/">All-In Podcast</a></figcaption></figure><p>In 2006, David Friedberg had an idea for a startup.</p><p>Every morning on his way to work, David drove past a bike rental shop. One day as he drove past, he noticed that the shop hadn’t opened because it was raining. Tourists didn’t cycle around in the rain so he figured the shop wouldn’t make any money that day.</p><p>David did some research and found that 70% of businesses are affected negatively by weather events. Putting two and two together, he thought there could be an opportunity to sell weather insurance to these businesses.</p><p>The product he was dreaming up would analyze 30 years of weather charts to predict the probability of rain. Using this data, he could provide cover for businesses — like the bike rental shop — from the monetary losses they were experiencing. Best of all, he could do all this at a profit.</p><p>Enthusiastic about the opportunity, David built a team and began working day and night on his new company, Weatherbill. The technology they needed to build was a huge undertaking that involved analyzing decades of weather data and building predictive algorithms.</p><p>Finally, after months without sleep, David launched the Weatherbill website. His team eagerly waited for all the businesses affected by the rain to arrive on the website with their credit cards, ready to make their first payments.</p><p>Instead, there was silence. Nobody bought their insurance product…</p><p>This is such a typical startup story; the founders have a big idea, they build a product that works well, they launch the product expecting to attract buckets of customers and are left severely disappointed when nobody buys.</p><p>But Weatherbill isn’t a story of failure. 7 years after this launch, the company was acquired by Monsanto for $1.1 billion.</p><p>In this guide, we deconstruct the process that David’s team used to find product/market fit at Weatherbill.</p><p>At each step of the process, you’ll be given an action to carry out. These actions will help you to understand why your customers aren’t interested in buying from you today and provide you with the inspiration you need to pivot towards a product that customers love.</p><p><em>Searching for Product/Market Fit? Join our fortnightly </em><a href="https://www.opinionx.co/newsletter">newsletter</a><em> to discover what it takes to build products users love.</em></p><h3>A Step By Step Guide To Saving Your Startup</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y_JekWADA2nA1KMEEB00Dw.png" /></figure><p><em>Disclaimer: </em><strong><em>This is the wrong way to build a startup. </em></strong><em>That’s why there is so little content written about this topic. You’re supposed to validate the problem with your customers BEFORE building your product. That being said, this is the real way that many startups *actually* find Product/Market Fit.</em></p><h3>1. Identify the problem(s) your product can solve.</h3><p>First, you need to get really clear about what problems your product is capable of solving.</p><p>It’s important to remember that every startup needs to solve a problem. Many first-time founders fall into the trap of thinking that their product doesn’t need to solve a problem. But that is wrong. People buy solutions to problems.</p><p>These problems can be subtle, like giving someone more control or helping them to better navigate their professional relationships. But they are problems nonetheless. You need to abandon the idea that companies like Facebook never set out to solve a problem right here (spoiler: <a href="https://www.cnbc.com/2018/01/17/why-mark-zuckerberg-started-facebook.html">they did</a>).</p><p>In the case of Weatherbill, David knew what problem his team was trying to solve; businesses were losing money because they were dependent on the weather.</p><p>If you can’t quickly identify the problem that your startup is solving, you need to really consider if your idea is worth pursuing. The likelihood of success quickly diminishes when you aren’t solving a real problem.</p><p>If you don’t think you’re solving a problem and still manage to have a few customers using your product, then look closely at their behavior. See if they are hacking your product to do something you never intended. See what problem they are solving with your product. Some of the greatest opportunities are found through observation.</p><p>Take ‘Play-Doh’ — the popular children’s toy. It first started as a cleaning product called <em>Kutol</em> and was designed to clean coal soot from walls. Kutol experienced a decline in sales as gas heating grew in popularity, so the company went looking for a new revenue stream. They found a teacher that had been using Kutol for arts and crafts classes with their students.</p><p>The Play-Doh team could see that their product was solving a bigger problem for teachers than it was for cleaners. After some consideration, they renamed and repositioned their product as a toy. The company became immensely successful and was eventually acquired by Hasbro, one of the largest toy distributors in the world.</p><p><strong><em>Before moving to the next step in the process, write down the problem that your product solves. If your product solves multiple problems then write down each problem that it solves separately.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*tvGGidoICo6hGHWhJ4K99w.png" /></figure><h3>2. Map out the different segments that experience the problems your product solves.</h3><p>Once you have clearly defined the problems that your startup could solve, it’s time to list the segments that experience these problems. Segments are just groups of people that have shared characteristics.</p><p>One of the most common reasons that startups don’t find Product/Market Fit is that their offering is trying to target loads of segments at once. This leads to a proposition that is so vague that every segment assumes it’s not meant for them. The good news is that you’re likely aware of multiple segments that you could potentially serve.</p><p>Weatherbill recognized that lots of businesses experienced the problem of weather affecting their revenue: coffee shops, adventure centers, travel companies, farmers, and ski resorts, to name just a few. When they first launched, they tried to serve all of these segments at the same time.</p><p><strong><em>Action time — write down all of the potential segments that your product could serve.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*n9m0ogXWjVR_5hhD4skzxg.png" /></figure><p>If your product only serves one segment, break down the different personas that exist within that segment. For example, a CRM tool that targets the first marketing hire at early-stage startups would be very different from one that focuses on brand managers at large ecommerce companies.</p><h3>3. Pick one segment.</h3><p>First-time founders often look at big tech companies like Hubspot that have 8 different products and 10 target customer types assume that they too can serve multiple segments at once. This is a big mistake.</p><p>Successful startups <strong><em>all</em></strong> start out by serving just one segment. To build enough momentum to scale a product, you need to solve a problem extremely well. While different segments might have the same problem, they don’t experience that problem in the same way. Focusing on multiple segments at once leads to compromises that create a mediocre product for each of those segments.</p><p>Hubspot spent 6 years avoiding this segment decision and it was one of the main reasons it took them so long to reach Product/Market Fit. Nobody is immune to the paradox of segment specificity.</p><p><a href="https://thinkgrowth.org/hubspot-s-playbook-for-going-from-startup-to-scale-up-29ab85d3a3e1">Brian Halligan</a>, CEO of Hubspot, explains how they made this mistake:</p><blockquote>For years at HubSpot we debated our target market persona. We had one camp that wanted to build our offering for Owner Ollie, a small business owner with less than 10 employees and no full-time marketer. We had another camp that wanted to build our offering for Mary Marketer, a marketing manager who worked in a company between 10 and 1000 employees.</blockquote><blockquote>By not deciding on one of these personas, we paid a gigantic, invisible ‘optionality tax’.</blockquote><blockquote>It turns out the product requirements, support requirements, pricing, and everything were different for Ollie and Mary and by not deciding, we made one uninspired compromise after another and never nailed either one.</blockquote><p>It’s only when a company has found Product/Market Fit with one segment and one use case that it can consider expanding into others. The more specific you can be on your initial target segment, the better.</p><p>After the failed launch, the Weatherbill team was spread extremely thin. They were learning loads about all their different segments but hadn’t decided to go deep on any of them. Trying to serve all these segments at once resulted in mixed feedback and buried the company’s strategy in confusion. None of the customer segments at this stage felt like Weatherbill understood or served their needs.</p><p>David ultimately made the decision to focus on just one segment that Weatherbill could serve excellently. He began speaking with people in each of their potential target segments. The goal of these discussions was to establish which segment suffered the most from the negative impact of weather.</p><p>During their research, David and his team realized that farmers were impacted by adverse weather to a much greater degree than their other segments. Poor weather conditions risked the loss of all of their crops, destroying farmers’ revenue for an entire year. The Weatherbill team decided to pivot from a general-purpose weather insurance product to target farmers as their only customer segment.</p><p><strong><em>It’s time to choose which segment you’re going to focus on. This decision will inform all future strategies and will determine your eventual success or failure. Choosing a segment can’t be a guessing game. A deep understanding of how the problem manifests differently for each of your potential segments will enable you to make the best decision.</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*Ea_J685i7IAyK7Or2i7V4Q.png" /></figure><h3>→ How to identify the right segment.</h3><p>Traditionally, founders like David would conduct customer interviews to identify which segment to focus on. While customer interviews are a great way to understand customer needs, they come with a bunch of challenges.</p><p>Firstly, they take a huge amount of time. You need to find lots of people from each segment to interview. If you don’t interview enough people from each segment, you won’t know if their perspectives are representative of their whole segment.</p><p>Customer interviews are also filled with traps. One of the most dangerous of these traps is “The Focusing Illusion,” which is what often happens when you talk to customers about a <em>specific</em> problem. When the customer focuses on describing that problem, they overlook all the other problems they face and put a disproportionate emphasis on how important that problem is to them.</p><p>Later — when they don’t buy your solution — you realize that this problem you solved is not a high priority for them. They have more urgent burning problems to contend with. In reality, they only discussed the problem in such detail because you encouraged them to do so.</p><p>To save time and counteract the negative effects of The Focusing Illusion, you need to use a technique that identifies the <strong>relative importance</strong> of the problem you plan to solve. Customer Problem Stack Ranking (or CPSR for short) is a method that asks target customers to rank a set of problem statements in order of importance. It’s a simple data-driven approach to understanding whether your idea solves a burning pain point 🔥 or just a mild inconvenience 🙄</p><p>By using CPSR for each of the segments you listed earlier, you can see <strong>which segment considers the problem you’re solving most important.</strong> This is a structured framework that mirrors the exact same approach the Weatherbill team took. The output of these stack rankings will tell you which segment feels your problem the strongest.</p><p>It’s possible that you already know which segment you are serving. That’s all the better. In this case, you are going to create a survey for each of the personas you listed earlier.</p><h3>→ The CPSR Survey.</h3><p>Trying CPSR manually in a bunch of interviews will lead to many of the same problems as customer discovery. We recommend creating a stack ranking survey for each customer segment instead.</p><h4>Step 1: Write Your Question</h4><p>As with any survey, Customer Problem Stack Ranking needs a question. These CPSR surveys often follow a similar format, with questions like “What are the challenges you face when ____ ?” or “What do you find frustrating about ____?”. Your CPSR question should be broad enough that it allows your participants to explore all the problems associated with an activity rather than just the specific problem that you’re trying to solve.</p><p>For example:</p><ul><li><em>Survey 1: Farmers →</em> “What are the challenges you face as a farmer?”</li><li><em>Survey 2: Coffee Shops →</em> “What challenges do you face when running a coffee shop?”</li><li><em>Survey 3: Adventure Centers →</em> “What challenges do you face when running an adventure center?”</li></ul><h4>Step 2: Add Your Problem Statement To The Stack Rank</h4><p>Take the problem(s) that your product solves and tailor it to each segment. In the case of Weatherbill, it would be:</p><ul><li><em>Survey 1: Farmers →</em> “Bad weather reduces our crop yield and risks the loss of considerable revenue.”</li><li><em>Survey 2: Coffee Shops →</em> “Bad weather leads to lower footfall and lost revenue.”</li><li><em>Survey 3: Adventure Centers →</em> “Bad weather causes our customers to cancel their bookings.”</li></ul><h4>Step 3: Create Peripheral Problem Statements</h4><p>Brainstorm peripheral problem statements that fall under the same ‘activity of focus’ but aren’t related to your idea. These can be informed by a handful of interviews using open-ended questions or by reading some pain point blog posts/forums. Don’t worry if you feel like you’ve missed some peripheral problems; stack ranking tools like <a href="http://opinionx.co/">OpinionX</a> let participants add new problem statements to cover areas you missed when creating your survey.</p><p>Examples for Weatherbill could include:</p><p><em>Survey 1: Farmers</em></p><ul><li>The cost of fertilizer reduces our profit margins.</li><li>The price of crops is volatile so we struggle to predict our annual revenue.</li><li>The market for our crops is over-saturated.</li><li>Machinery is too expensive and doesn’t produce a return on investment.</li><li>There are too many people to split profit amongst.</li></ul><p><em>Survey 2: Coffee Shops</em></p><ul><li>There’s too much competition in our area so we have to lower prices.</li><li>Customers don’t appreciate higher-quality premium coffee.</li><li>Paying wages is a big expense.</li><li>Maintaining the appearance of the shop is a constant drain on cost.</li><li>People are only interested in buying coffee for a few hours in the morning.</li></ul><p><em>Survey 3: Adventure Centers</em></p><ul><li>Injury insurance is just so expensive.</li><li>Children like to play indoors more in recent years.</li><li>It costs a lot to maintain equipment.</li><li>We don’t have as many activities as competing adventure centers.</li><li>Training and retaining staff is a constant source of stress.</li><li>There isn’t enough interest in adventure centers among younger people.</li></ul><p>I recommend adding between 10–20 sample problem statements so that you can really see how important your problem is compared to all the other problems each segment experiences.</p><h4>Step 4: Send Your Stack Rank To Each Segment</h4><p>Now that your CPSR surveys are ready, it’s time to send one to each segment. If you’re struggling to find the right people for your survey, here’s are some techniques for <a href="https://www.opinionx.co/blog/how-to-find-free-participants-for-your-survey">finding free survey participants</a>.</p><h4>Step 5: Iterate!</h4><p>As participants vote on your stack ranking, they will add new problem statements to fill in gaps that you missed at the start (if you’re using a tool like <a href="http://opinionx.co/">OpinionX</a> that allows this). Over 80% of OpinionX surveys finish with problems added by participants in the top 3, so it’s important to be open to growing and changing your list of problems as you go.</p><h4>Step 6: Analyse The Results</h4><p>Analyzing stack ranking results couldn’t be easier; just hit “Importance” to organize all of the problems from highest to lowest importance. In one click, you’ll know how important your problem statement is compared to the other problems your target customers face. When you compare your stack rankings side by side, your data should look something like this:</p><p><em>Survey 1: Farmers</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e-gYW_uHL4-Pih1f6So-Vw.png" /></figure><p><em>Survey 2: Coffee Shops</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RSjUuNeQ2iIjxWFz38EpTg.png" /></figure><p><em>Survey 3: Adventure Centers</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H0CpOg_0JJN4YT6euNsLeg.png" /></figure><p>It’s easy to see from these results that Weatherbill’s product solves a much higher priority problem for farmers than the other two segments. A higher priority problem not only means that they will be more willing to pay — it also means that people are likely out searching for a solution already, making it much easier to acquire new customers.</p><p>If your problem is not ranking high for any segment, then it could be time to reconsider whether your idea is worth pursuing further. You may have even spotted a different problem in your CPSR data that you could solve instead!</p><p>Continue to split your target into increasingly specific personas where possible. The more specific your persona, the clearer their problem will become and the easier it will be to land your value proposition message.</p><h3>4. Focus on just one problem.</h3><p>Every product solves multiple problems, but they still have to choose one value proposition to lead with. Choosing your value proposition creates constraints that force you to focus on the highest priority problem you solve for your customers.</p><p>Thankfully, your CPSR results have shown you exactly which problem is most like to grab your customers’ attention.</p><p>Now that you know which segment you’re focusing on and which problem you’re solving, you need to understand more about the context of this overlap. Hidden in this overlap are your killer use case and the barriers you need to overcome to get target customers to give your product a try.</p><p>A few short interviews will enrich your understanding with all the details you need. Don’t fall into the trap of building or adapting your technology too early. The more conversations you can have at this stage, the more likely your Go-To-Market strategy will succeed. Stay as close to your validated highest priority problem throughout this process.</p><p><em>Searching for Product/Market Fit? Join the fortnightly </em><a href="https://www.opinionx.co/newsletter">newsletter</a><em> and discover what it takes to build products users love.</em></p><h3>5. Commit to the pivot.</h3><p>By this stage, you have found your single target customer segment and a burning problem that your product can solve. Armed with this knowledge, you must now put your pivot into action. This means shifting your entire company strategy to focus only on the specific needs of your newly defined segment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DsB6weQTBR6cFrxOrqEy4g.png" /><figcaption>It’s time to commit… 💍</figcaption></figure><p>During this pivot, you need to review every aspect of your strategy. Nothing can be off-limits at this stage. Whether it’s your product and pricing strategy or your distribution channel and brand, you must openly consider what can be salvaged and what gets chucked into the trash.</p><p>In the case of Weatherbill, with their decision to focus on farmers, they ruthlessly rebuilt their strategy. Their distribution channels had to be redesign from scratch. Farmers didn’t use credit cards to purchase so they had to move to written contracts and trusted personal connections. Weatherbill transformed its internal structures to move from a self-service digital platform to written contracts built on customer relationships.</p><p>The most painful parts of pivoting are killing your brand and throwing your product away.</p><h3>→ Cull technical debt early.</h3><p>Abandoning hard work as an underfunded startup is be a tough decision, but if you’ve reached the conclusion that any parts of your product don’t add value to your newly defined target customer segment then they’ve got to go. If not, you’ll fall victim to the <a href="https://en.wikipedia.org/wiki/Sunk_cost">sunk cost fallacy</a> and lose customers due to your confusing and complicated product.</p><p>Most of the front-end of Weatherbill was discarded during their pivot to farmers, however, the back-end weather prediction technology remained as useful as ever. It’s not always necessary to start completely fresh, just that you approach the decision with fresh eyes.</p><h3>→ Update your messaging based on your new priority problem.</h3><p>Whether your brand needs to be redesigned or not, you will definitely have to build a new value proposition. With one segment and problem in mind, your new proposition must articulate a clear solution that resonates with your new target customers.</p><p>This step is often where startups shed two of the most common positioning mistakes; they start talking about “why” their product adds value instead of “how it works”, and they stop using vague marketing terms like “one-stop shop” or “all-in-one.”</p><p>Weatherbill needed to move its focus away from “weather insurance” to communicate the benefit it offered farmers, which was its crop protection offering. This was a big change from its original generic messaging. Eventually, Weatherbill had moved so far from its original positioning that it renamed the company altogether, redefining its brand as <em>The Climate Corporation</em>.</p><h3>6. Re-launch</h3><p>Finally, it’s time to re-launch. This is where you’ll have an opportunity to observe changes in how customers receive your new value proposition.</p><p>After Weatherbill rebranded as The Climate Corporation and focused on crop protection, 50% of all farmers they pitched to said yes to buying the product. Yes, 50%! This incredible turnaround could only be achieved by investing their efforts in understanding the farmer’s unique view of the world, their priority problems and purchasing behaviors.</p><p>Regardless of your chosen distribution strategy, you can find simple ways to test the market with your new value proposition. Writing and sharing a blog post that describes your updated view of your market is a great cheap way to test your new positioning. Otherwise, here’s a great video about <a href="https://www.youtube.com/watch?v=3xU050kMbHM&amp;ab_channel=YCombinator">building a continuous launch mentality</a> that’s well worth a watch. Focus all your efforts on getting your first 100 customers and be open to <a href="http://paulgraham.com/ds.html">doing things that don’t scale.</a></p><h3>7. Iterate</h3><p>Product/Market Fit is a bit of a misnomer because finding that ‘fit’ doesn’t guarantee it forever (or even for a short period). To enable growth, startups must leverage their traction to expand to new segments, use cases or offer deeper value with their existing product. The same lessons explored throughout this post — prioritizing singular customer segment and problem focus — are what turn those new products, features and expansion experiments into compounding successes.</p><p>Whether you’re a struggling founder or a scaling product team, identifying the biggest problem to a defined group of people is one of the most important skillsets when it comes to finding Product/Market Fit. OpinionX is the <em>only</em> tool for Customer Problem Stack Ranking. It’s used by hundreds of teams at companies like Canva, Hotjar and Google to build products that customers love. Kickstart your pivot to Product/Market Fit right now by <a href="http://app.opinionx.co/sign-up">creating your own FREE stack ranking survey in under 60 seconds on OpinionX</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=295544c48931" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should you build a feature for just one customer?]]></title>
            <link>https://medium.com/the-full-stack-researcher/should-you-build-a-feature-for-just-one-customer-9a1e420130a?source=rss-71cac2cfe29d------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a1e420130a</guid>
            <category><![CDATA[features]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[founders]]></category>
            <category><![CDATA[user-research]]></category>
            <dc:creator><![CDATA[Éamon Cullen]]></dc:creator>
            <pubDate>Fri, 04 Jun 2021 12:35:34 GMT</pubDate>
            <atom:updated>2021-06-07T10:19:15.237Z</atom:updated>
            <content:encoded><![CDATA[<p>This post originally appeared on the <a href="https://www.opinionx.co/blog/custom-feature-request">OpinionX blog</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zyoWpi7x3c205Mb3BVxoUA.png" /></figure><p>In the early days of a startup, it is tempting to build a feature as soon as one person requests it. You’re hungry for new users and building the features they ask for seems like a logical approach to getting them signed up for your product. But this is <em>almost always</em> a big mistake.</p><p>As a general rule, building your product based on feature requests results in more pain than progress.</p><p>There are several reasons why you shouldn’t build a feature for just one customer:</p><h3>1) Products need to be built with a vision</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F0mlarAE8ty0U0Ewa-ke4Q.png" /></figure><p>As a product builder, you have a vision of what your product will become. Achieving this vision requires immense focus. If pleasing this one customer compromises your product vision — even just a little bit — then over time you’re product will creep further and further from your intended direction.</p><p>This mentality of accepting every customer request distorts your product vision. The tasks you focus on will increasingly be low priority for the rest of your target customers and your team will become progressively more frustrated with your constantly changing expectations.</p><p>You can’t solve every problem. Knowing when to say “no” is immensely important. Steve Jobs — arguably one of the greatest product visionaries of the last 100 years — is known for his dedication to product vision above all else. He famously said, <em>“People think focus means saying yes to the thing you’ve got to focus on. But that’s not what it means at all. It means saying no to the hundred other good ideas that there are.”</em></p><p>By default, the answer to feature requests must be <em>“no.”</em> That being said, you need to balance this tunnel vision with open-mindedness, a willingness to be wrong, and the ability to pivot iteratively. It’s a matter of using your initiative to navigate complex situations. This is what makes building a startup so difficult and product success so rare.</p><p>At <a href="https://www.kissmetrics.io/">Kissmetrics</a>, a startup that completely reinvented the analytics category with its funnel tracking product in 2010, the team used to call these feature request distractions ‘Hiten Bombs’ — named after their Founder and CEO <a href="https://producthabits.com/my-billion-dollar-mistake/">Hiten Shah</a>.</p><p><em>“Every week — actually it was usually daily — I would drop a bomb on someone in the company. It would be some new idea, some new direction, some new brilliant thing I came up with — something we absolutely had to do right now.</em>”</p><p>In hindsight, Hiten admits that allowing product vision to slip creates confusion within the team and impacts a startup’s most important asset; speed. <em>“We didn’t prioritize our product development with the right data. Our execution slowed. We were no longer innovating and staying ahead of the curve.</em></p><p><em>“The winning product is based on focus and planning. Continuous unbiased research and goal-focused development.”</em> Feature requests from just one customer are the most common (and easiest to blindly follow) ‘Hiten Bomb’ you’ll come across when building a product; avoid them at all costs.</p><h3>2) Resources at any startup are limited</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dA4k9FlAOIObPdrY4MSRbQ.png" /></figure><p>Every time you make a decision to build a new feature, you’re deciding not to spend time improving existing features, testing for bugs, or <a href="https://www.opinionx.co/blog/customer-problem-stack-ranking">solving more important customer problems</a>. Every action at a startup has an opportunity cost and prioritization is the key to success in this game.</p><p>Instead of saying yes right away, take a step back to think about whether you can solve this customer’s problem in a different way. Quite often you’ll realize that there is an alternative solution to the problem that doesn’t require an additional build, such as simplifying an existing feature, linking to a blog post, or improving your product support documentation.</p><p>As <a href="https://producthabits.com/my-billion-dollar-mistake/">Hiten from Kissmetrics explains</a>, following every new feature idea took a heavy toll on the Kissmetrics team, <em>“The team would rush to execute my new idea as priority. They’d huddle together to figure out the best and fastest way to accomplish it. They’d pull in more teammates and add it to our growing list of competing features to build, bugs to fix, and customer requests. I didn’t realize it at the time, but to my team the barrage of random ideas seemed like they were coming completely out of left field.”</em></p><p><a href="https://www.intercom.com/blog/the-right-way-to-respond-to-feature-requests/">Intercom</a>, on the other hand, is a great example of a team that doesn’t siphon away resources for features that aren’t an existing priority. Intercom regularly gets requests from customers to turn off their messenger widget outside of working hours. Instead of allowing the frequency of this feature request to alter their roadmap, the Intercom support team helps customers to set their office hours and expected response time. Intercom is the first to admit that this is not always what customers want to hear, but the workaround is usually enough to satisfy what customers originally asked for. Remember — customers buy solutions, not features.</p><h3>3) You should build for the many, not the few.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t-adTv2H_3_zLZkcvf8VqQ.png" /></figure><p>Impulsively building features is a consequence of short-term thinking. You need to build features that will add maximum value for the largest number of people long-term.</p><p>Product builders often fall into a mindset of <em>“but we will lose the customer if we don’t build this.”</em> The truth is that if one customer has that much influence over your company, you need to think about diversifying your revenue stream — <em>especially</em> if you’re dealing with a small overall amount of revenue.</p><p>When you don’t have many (or any) customers yet, it can be easy to think that one customer’s requirements are representative of all future customers. In reality, there’s no way to know for sure without having sufficient data. We almost made this mistake at OpinionX by adding a feature to our stack ranking product for buying survey participants. When we first heard the request from one customer, we thought it was an interesting idea. Within a week, we had 3 more identical requests. Understandably we were pretty confident that this was the correct move for us.</p><p>We set up introductory calls with panel recruitment providers and mocked up how the feature would work, the user flow, and the different recruitment segments our users would need. The deeper we got, the more we realized how big this project would be. It was going to take our entire development team almost three months of work before we could ship the first version to users.</p><p>We were shipping big features every single week around this time. Three months of not shipping stopped us in our tracks to properly consider this project. Two things snapped us out of this delusion:</p><ol><li><strong>We measured how important recruitment was to our users</strong></li></ol><p>In the early days, the product builder’s job is to repeatedly solve the biggest barrier for users to successfully adopt their product. We set about measuring how high on the list of barriers this was to our users. We turned all the feature requests we had received over the previous month into problem statements and asked users to vote for the biggest problems they were having with OpinionX. During the stack rank, they also added new problems for others to vote on which highlighted problems we never even knew about, but that’s a story for another time…</p><p>Within a few hours, we could see that participant recruitment was right in the middle of the stack rank — not a burning problem but more than a mild inconvenience. This validated that we shouldn’t jump into building this feature, but we wanted to understand where the request was coming from.</p><p><strong>2. We searched for overlap between this feature request and our paying customers</strong></p><p>We knew that participant recruitment was a ‘middle of the stack’ priority for the average user, so who was it a priority for? We had a small premium customer base at this stage and a quick glance showed that none of these users had any issues with finding survey participants. Digging into this further, we realized that we had two different user segments competing for different features — founders without users wanted recruitment so they could validate their ideas, product teams with users wanted us to add more analysis and moderation tools.</p><p>Our customer base at that stage consisted of more product teams than founders, so we prioritized that segment in our roadmap decisions. Instead of spending three months building the recruitment feature, we wrote a blog post on <a href="https://www.opinionx.co/blog/how-to-find-free-participants-for-your-survey">free techniques for finding survey participants</a> and continued to prioritize our product roadmap for our paying users.</p><h3>4) It adds complexity to the product</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XevM4vS0buLiPE2SSatdyQ.png" /></figure><p>Product builders think that by making a feature optional, they get the best of both worlds — satisfy the feature request without overburdening other customers. But that’s not how it works…</p><p>Each extra feature makes your product more intimidating for new users, increases the time users need to find the feature they’re looking for and adds even more information that users have to remember next time they use your product.</p><p>To make matters worse, the <a href="https://gostrengths.com/what-is-the-paradox-of-choice/">paradox of choice</a> says that adding more options actually causes more stress and delays decision-making. We’ve all experienced this; that overwhelming paralysis where you spend 20 minutes scrolling through Netflix and end up not watching anything at all.</p><p>Successful features depend on successful user adoption. Your features are all competing against one another for that sliver of time that users commit to spending on your product. The more features you build into your product, the harder it is for each feature to become part of a user’s product habit.</p><p>Instead of overburdening your users, you want to prioritize the features that solve your customers’ biggest problems and optimize from there for the smoothest product experience. Make it obvious to your users what is expected of them. In the words of <a href="https://sensible.com/dont-make-me-think/">Steve Krug</a>, “<em>don’t make me think</em>.”</p><h3>5) It might be harder to build than you think</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1KyPRmaSfzyT-YEcsv-LuA.png" /></figure><p><em>The Planning Fallacy</em> is a term psychologists use to describe our tendency to underestimate the amount of time it will take to complete a task. The funny thing about this fallacy is we never seem to learn from it. Even though your last 10 projects went 3+ weeks over schedule, you still don’t account for this when you decide to ‘quickly’ build that feature a customer just requested.</p><p>Roger Buehler, a social psychologist, <a href="https://medium.com/gravityblog/the-planning-fallacy-3af4bb20493c">conducted a study</a> in 1994 where a group of college students was asked to estimate how much time they would need to finish writing their theses. The students estimated 33.9 days. Then they were asked for an optimistic and pessimistic estimate, to which they answered 27.4 days and 48.6 days respectively. The number of days that it took to complete their theses was actually 55.5 days! Interestingly, this trend was observed in everything from fixing bicycles to writing letters and cleaning bedrooms.</p><p>Things are rarely smooth sailing when building something new and the time required for a new feature rarely stops once development is finished. There are bug fixes, user education, and ongoing customer support for this feature that will siphon away your time forever (especially if it falls outside your long-term product vision).</p><p>Think twice before you say yes to a feature request by telling yourself <em>‘it won’t take too long.’</em> Your time is precious at a startup; use it wisely.</p><h3>6) Will they even use it?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IRTNotPSf9skqhigWn5o3A.png" /></figure><p>This might be the most important of all. Most feature requests mask an underlying problem that users are trying to tell you. But there’s an even more dangerous type of feature request — when people say something for the sake of saying something or to sound smart. There is a good chance that after you build the feature and enthusiastically email that customer, they’ll never even respond. Trust me, you don’t ever want to experience that kind of pain…</p><h3>When should you consider building a feature for just one customer?</h3><p>Is there ever a time where you should build a feature for just one customer? The answer is a strong <em>maybe</em> 🥴 As discussed above, it’s always best to avoid building a feature based on a single or even just a few customer requests. That being said, there are a handful of very rare occasions when you should consider building a customer’s feature request:</p><h3>1) The feature aligns with the product vision</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z5Xia6mmQk6vyV4IBGrzog.png" /></figure><p>You’ll notice that some of your more visionary customers request features that are already on your product roadmap. This is a beautiful feeling and indicates that your ambitions are aligned with users’ needs.</p><p>If you receive a one-time feature request from a customer that happens to be already on your roadmap and aligns with your vision, it could be worth prioritizing over features that haven’t yet been mentioned by customers.</p><p>We had this experience at OpinionX. It was on our roadmap to add a feature that would allow stack rank creators to <em>approve</em> statements added by participants before they get sent to other participants to vote on. We knew this would be important but had other priorities on our plate first. After it was highlighted to us that this feature was super important by a couple of users, we pulled it to the front of our queue and built it straight away for those customers. (but this particular feature request was special… I’ll explain below).</p><h3>2) It requires minimum resources and is super simple</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_2EJE2occYirEB5K1NQdLQ.png" /></figure><p>We already discussed that most things take longer and are harder than you expect. But in some cases, you just know from experience that this feature will be of huge value to your customers and requires minimum investment from you (aka it has almost zero downsides).</p><p>In the case of this <em>approval </em>feature request, our product team was confident they could build the feature within two days. It wasn’t rocket science or time-consuming, so we decided it would provide more benefit than risk. During those two days, we started getting loads more requests for this same feature, validating our initial decision to start building it.</p><h3>3) You have already validated the problem with other users</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1q5GXqvhNeYxAHvq-O8iJA.png" /></figure><p>Sometimes, even though the feature hasn’t been requested before, the problem has already been validated. Through your user research, you know that the problem likely exists for most of your customers. In these cases, you can consider implementing the feature — although I would encourage you to investigate whether this specific feature is actually the best solution to the problem. There is always more than one way to solve a problem.</p><p>We ‘dogfood’ OpinionX (ie. use our own product on ourselves) all the time at our startup, so we knew first hand that not having this <em>approval</em> capability could lead to embarrassing moments where low-quality opinions were automatically sent to other users to vote on. By using our own product, we knew that other customers would benefit from this feature too. When the first feature request came in for approving opinions, we felt confident that it was the correct thing to do.</p><h3>4) You’re going to make a loooot of money</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5fYuJoNpJbYn4Yvg8-2jqw.png" /></figure><p>On rare occasions, a single customer is worth so much to you that building the feature will generate enough revenue to pay off the opportunity cost and make it all worthwhile. You can invest this money back into your original product vision.</p><p>In reality, this really only applies to startups with an enterprise sales focus (ie. they sell to a small number of really big companies). For <a href="https://www.opinionx.co/blog/what-is-product-led-growth">product-led</a> companies (which typically focus on building a much bigger user base with a smaller amount of revenue per customer), following a big cheque like this is usually little more than a giant distraction.</p><p>If you find yourself in this situation, I’d encourage you to investigate whether this is really a one-time big-ticket customer or if you’ve actually stumbled upon a really profitable customer segment (if you’ve already taken the money, I hope for your sake that it’s a really profitable segment 🙃).</p><p>At OpinionX, we were presented with this opportunity once. An enterprise-size customer wanted a heap of integrations that we didn’t have and had no intention of building for at least a year. We understood that building these features for this one user could be profitable in the short term and extend our runway, but ultimately we decided that we needed to stay focused on the vision of helping early-stage startups to find product/market fit faster.</p><h3>Make decisions based on problems, not features</h3><p>The underlying theme throughout this article is that it’s your job as a product builder to identify the problem underlying your customers’ feature requests and determine if they represent the most important problems faced by your broader customer base.</p><p>As mentioned, we almost made a huge mistake by jumping into a 3-month build for a feature requested by only a handful of people before discovering that the problem was not a high-priority pain point for most of our other users. We used <a href="http://opinionx.co/">OpinionX</a> to really quickly figure this out — it enabled our users to stack rank all the barriers they had with using our product so that we could identify the most urgent friction points to resolve.</p><p>Instead of spending 3 months working on that feature, we spent 3 hours writing a quick blog post to help that small subsegment of our users and dedicated our focus towards solving the most urgent problems that most of our users were struggling with.</p><p>Stack ranking is a really simple framework for prioritizing your time as an early-stage product builder. It gives you data that you could never find from user interviews so that you can be more confident in your decision-making. It’s free to create as many stack ranking surveys as you need on OpinionX — <a href="https://app.opinionx.co/sign-up">get started right now</a> and within a few hours, you’ll have the data you need to decide whether or not you should build that feature request :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a1e420130a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-full-stack-researcher/should-you-build-a-feature-for-just-one-customer-9a1e420130a">Should you build a feature for just one customer?</a> was originally published in <a href="https://medium.com/the-full-stack-researcher">The Full-Stack Researcher</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to find free participants for your survey]]></title>
            <link>https://medium.com/the-full-stack-researcher/how-to-find-free-participants-for-your-survey-c7d400750436?source=rss-71cac2cfe29d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7d400750436</guid>
            <category><![CDATA[user-research]]></category>
            <category><![CDATA[surveys]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Éamon Cullen]]></dc:creator>
            <pubDate>Tue, 18 May 2021 09:09:59 GMT</pubDate>
            <atom:updated>2021-05-18T09:09:59.179Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*X2esWiggx-JWheR7tYJNKw.png" /></figure><p>You’ve created a great survey and you’re already imagining the potential results. There’s just one crucial step standing in your way; you need to find participants. But not everyone has a big budget. Thankfully, there’s no need to worry. Here are 3 popular methods you can use to find people to complete your survey:</p><h4>1. Distribute to your community</h4><p>Distributing your survey to your existing community is the most common approach taken by people carrying out their research using <a href="https://opinionx.co/">OpinionX</a> .</p><p>This method is suuuuper easy; just copy a survey link and email it to your community. Things aren’t always this easy though — we don’t all have access to a perfect spreadsheet of emails. There are a few ways that you can get creative with survey links and the inbound traffic or followers you have.</p><p>SproutPlans founder Niamh de Búrca embedded her OpinionX survey on her startup’s landing page (using a simple ‘copy and paste’ block of code called an iFrame) which allowed her to survey people checking out her website before she had any users on her product (explained in <a href="https://www.opinionx.co/blog/sproutplans-customer-discovery-case-study">Niamh’s case study</a>). Another option is to integrate a chat popup like Intercom (free alternatives for those on a budget include <a href="https://www.drift.com/">Drift</a> and <a href="http://tawk.to/">tawk.to</a>) on your website and include your survey link in a conditional popup message that greets new visitors.</p><p>The key is to get creative! Use simple methods like these to turn website visitors into survey participants. To get website visitors in the first place, consider writing <a href="https://marketingexamples.com/content/sharing">and promoting</a> a few blog posts, look for a community shoutout slot on a relevant industry newsletter, or simply ask friends and family to help you out by sharing the survey link with their network.</p><h4>2. Promote your link publicly</h4><p>Social media and online forums are a great place for gathering survey responses. It’s cheap, convenient, and easy to reach large numbers of people. Forums in particular are a great resource for survey creators trying to find specific people with a niche interest, background or attribute all in one place. Depending on your approach, public promotion on the internet can enable you to gather a broad undefined sample or a well-defined segment if you seed your OpinionX survey link in these niche communities.</p><p>Publicly promoted surveys benefit hugely from having a good incentive. Once again, this is a great opportunity to get creative to stand out from the crowd. The most common reward is the raffled gift voucher, but you should think about other ways that you might be able to offer value in exchange for participation in your OpinionX survey; whether that’s a free ebook, access to an unlisted podcast, a 30-minute Zoom call with a well-known industry expert, or even a free account on a great premium product. There are plenty of ways you can catch people’s attention and gather rich insights with the right incentive.</p><p>For example, when <a href="https://offie.us/">Offie</a> founder Patrick Erichsen created his first OpinionX survey to validate his startup idea, he didn’t have any users or existing community to target. What he did have, however, was a very particular target participant in mind; a young professional working remotely while traveling. Patrick jumped over to the r/AirBnB community on Reddit as well as online community Remote Clan and <a href="https://remoteclan.com/s/tzhnwk/startup_feedback_need_feedback_on_rental">posted links</a> to his remote working survey along with a quick description of his research project. Within a few hours, <a href="https://remoteclan.com/s/xjmfaf/community_survey_results_long_term">he had a full sample of participants</a> and voting data ready to analyze.</p><h4>3. Direct message your target audience</h4><p>If you have no existing community to engage but you know what kind of people you need for your survey, a direct outreach approach can quickly source a robust sample size if you know the right techniques.</p><ul><li><strong><em>Slack Outreach</em></strong></li></ul><p>This is a method that we used at OpinionX to <a href="https://www.opinionx.co/blog/customer-problem-stack-ranking">find 149 product managers for our own survey</a>. With just a few hours of work, we found a Slack community where we knew that our target participants were hanging out. Instead of just posting the survey link publicly into one of the main channels, we sent friendly personalized messages to a filtered list and received a 25% response rate.</p><p>Here’s how to do it:</p><ol><li>Using a search phrase like “Top Slack Communities for _____”, find a large Slack community relevant to your target participant type.</li><li>Once you’ve joined, search the job title of the participant type that you’re targeting. In our case, it was product managers.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/1*kLjtSFVazLQYj_Xjy4EDhg.png" /></figure><p>3. Click the “People” tab to filter just to users and hit “Exclude deactivated accounts” to hide inactive users. In this case, one Slack community provided a list of 2,298 product managers available for direct message.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/1*lBoiZOA1Bi7dSlh0HqzpkA.png" /></figure><p>4. Finally, write a polite outreach message explaining what you are doing and why their help would be appreciated. If you don’t spend the time to write a good message, people will just feel like you are using them. Instead, give the person an opportunity to get something in return for their time; whether that’s just the satisfaction of helping someone or offer a favor as thanks.</p><p>Here is an example of a message that worked well for our cold Slack outreach:</p><p><em>Hi James, I’m working on a startup idea that helps product managers and I’m trying to understand the biggest challenges PMs face at work. Would you have 2 minutes to share your opinion? It would really help us out a lot to hear from a product manager like you! And please let me know if there’s anything I can do in return for your time? Thanks a million :)</em></p><p>We sent ~600 of these messages to product managers on Slack and received 149 responses — not bad for one evening of work! The best part about this outreach method is that it’s so warm and personal that’s really easy to find people willing to follow up the survey with a short call to learn more about their answers and experience.</p><ul><li><strong><em>Twitter Outreach</em></strong></li></ul><p>It may be surprising for some but Twitter is a great place to find survey participants. This is particularly true if there is lots of online conversation about your topic of interest. Use the search bar to find people who are talking about your topic of interest. I guarantee you that you’ll be surprised at how many Twitter users have their accounts set to allow direct messages from anyone.</p><p>Referencing an old tweet of theirs is a great way to show that you’re not doing a mass-spam outreach like a bot account. As with Slack, a friendly and personalized outreach will get a solid response rate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*WuSz-5I3r1RFhRx7zqTddQ.png" /></figure><p>For example, searching for “working remote” with search criteria of 10 likes or more will raise a solid list of recent tweets from real people.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*8d-4CxmfpdeR_KC-BD2NVQ.png" /></figure><p>Instantly, we’ve got a list of self-qualified leads for our survey. In the example above, all three accounts have their DMs set to open and have shown personal experience with remote working in the past week.</p><p>Don’t worry about learning off keywords like “min-faves:” — Twitter has a whole feature to help you to carry out <a href="https://twitter.com/search-advanced">advanced searches</a>.</p><ul><li><strong><em>Other Platforms</em></strong></li></ul><p>Like the “min-faves:” search term on Twitter, there are great terms you can use to custom filter searches on Google. Darko from ZeroToUsers posted this great guide to <a href="https://www.indiehackers.com/post/acquisition-channel-opportunities-content-marketing-google-sheets-fake-reviews-0371eb1356">finding public Google Sheets documents</a> in March 2020 and this guide to <a href="https://www.indiehackers.com/post/acquisition-channel-opportunities-67-app-stores-pinterest-quora-dbd59cd1de">finding ‘easy to win’ Quora posts</a> in January. Once you see the patterns in these search methods, they can easily be applied to other social media platforms better suited to direct outreach like Reddit and Twitter.</p><p>See, finding free survey participants is possible, it just requires a tenacious attitude and some good old-fashioned grafting. If you found this article useful, <a href="https://www.opinionx.co/newsletter">subscribe to our newsletter</a> to receive a digest of our latest ideas and posts every two weeks.</p><p><a href="https://www.linkedin.com/in/%C3%A9amoncullen/"><em>Éamon Cullen</em></a><em> is a Product Research Lead at OpinionX, where he takes a hands-on approach to help founders and PMs validate their ideas, find product-market fit faster and build products that customers love. </em><a href="https://calendly.com/ec-ox/30min"><em>Grab a free 30 minute slot</em></a><em> to talk to Éamon about validating your idea or aligning your messaging to your customers’ biggest problems.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7d400750436" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-full-stack-researcher/how-to-find-free-participants-for-your-survey-c7d400750436">How to find free participants for your survey</a> was originally published in <a href="https://medium.com/the-full-stack-researcher">The Full-Stack Researcher</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You don’t need to be creative to write landing pages that convert]]></title>
            <link>https://medium.com/design-bootcamp/you-dont-need-to-be-creative-to-write-landing-pages-that-convert-566ab9de769b?source=rss-71cac2cfe29d------2</link>
            <guid isPermaLink="false">https://medium.com/p/566ab9de769b</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[copywriting]]></category>
            <category><![CDATA[marketing-strategies]]></category>
            <category><![CDATA[landing-pages]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Éamon Cullen]]></dc:creator>
            <pubDate>Fri, 07 May 2021 04:57:33 GMT</pubDate>
            <atom:updated>2021-05-07T04:57:33.252Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A red slot machine in an arcade." src="https://cdn-images-1.medium.com/max/1024/1*4BAS_aRfJPcX2WFnSNNoSg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@carltraw">Carl Raw</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>For 6 months, our startup was stuck in a loop. We would admit that our landing page wasn’t good enough, re-write it, be happy for a few days and then the cycle would begin again. We understood the importance of getting our landing page right. We read every “how to write a landing page” guide and brainstormed headings for hours on end. Despite our efforts, we were never happy. Our poor conversion rate constantly reminded us that our messaging wasn’t landing properly with website visitors. It was painful, disheartening and time-consuming. We knew that we had to try something new.</p><p>We finally came across a <a href="https://twitter.com/shreyas/status/1376033615029538828">Twitter thread</a> from Shreyas Doshi, a product manager at Stripe. He outlined an idea validation method called Customer Problem Stack Ranking (CPSR) and we decided to give it a try to understand how much our target customers cared about the problem we said we were helping them solve. In the process, we discovered a whole new way to write landing pages. One week after implementing the results of our CPSR, we doubled our conversion rate, our onboarding success rate improved 2.5x, we tripled our website traffic and even saw organic referral between users.</p><p>I’m going to share exactly how we used CPSR so that you can get these same benefits too! But first…</p><h3>What is Customer Problem Stack Ranking?</h3><p>CPSR shows how important a problem is compared to all the problems that your target customer is trying to solve. It’s a unique survey method that helps founders and product teams to understand whether they’re solving a burning pain point or just a mild inconvenience. By getting customers to rank problems by importance, you can pick ideas with better potential for organic demand and identify the messaging that resonates best with your target segment. We built our own CPSR tool <a href="http://opinionx.co/">OpinionX</a> so that we could run our experiment at scale quickly and easily.</p><h3>5 steps to writing a better landing page using CPSR:</h3><h3>Step 1: Write The Question</h3><p>Customer Problem Stack Ranking requires just one open-ended question. Most CPSR questions follow the same format of “What is the most frustrating part about _____? or “What is the biggest challenge you face when______?”. For our own CPSR, we asked product managers, “What is the biggest challenge you face as a product manager?”</p><p><em>Top tip: Ensure your open-ended question is focused on problems, not solutions.</em></p><h3>Step 2: Draft Your Problem Statements</h3><p>Most early-stage startups solve multiple problems. This makes writing a landing page really difficult; which of the problems is <em>most important</em> to target customers? We were tired of guessing and after 100+ interviews with target customers, it still wasn’t clear to us! Even if we figured this out, we knew that we still had to understand the best wording to describe this problem to customers and our creative efforts were falling flat.</p><p>To test this, we turned our idea and landing page into multiple problem statements which we added to our CPSR. Some of these problem statements included:</p><ul><li>It’s hard to understand user needs.</li><li>I sometimes worry that we’re shipping the wrong things.</li><li>Stakeholders want to talk more about solutions than about problems.</li><li>Finding product-market fit for a new product/feature is an ongoing challenge as a PM.</li><li>It’s difficult to know if an idea has really been validated before we start building.</li></ul><p><em>Top tip: Add multiple problem statements related to your product offering to your CPSR. You should even consider experimenting with different wordings for the same problem. These differences can reveal a lot about how your customers perceive different terms or phrases.</em></p><h3>Step 3: Add Peripheral Problem Statements</h3><p>To understand how important your problems are to target customers, we need to compare them to other problems your target customers experience. To do this, we’ll add problems that are in the same ‘activity of focus’ but that your product doesn’t solve. The way to come up with peripheral problem statements is to just talk to some of your target customers and ask them. Otherwise, forums, blog posts and social media are all full of people talking about their problems :)</p><p>Some of the peripheral problem statements we used in our own CPSR included:</p><ul><li>Our organizational knowledge is too disjointed.</li><li>Getting the company to start tracking KPIs is painful.</li><li>Moving users from a free plan to a paid plan is a big challenge.</li></ul><p><em>Top Tip:</em> <em>Don’t worry if you feel like you’ve missed some peripheral problems. OpinionX lets your CPSR participants add new problem statements to your list as you go, cover areas that you miss.</em></p><h3>Step 4: Send To Target Customers</h3><p>Sending out a CPSR on OpinionX is as easy as copying and pasting a link. We spent an evening DMing our link to about 400–500 Product Managers in relevant Slack communities. We got 145 responses, giving us a solid sample size to trust our data. While sending out the survey, our list of problem statements grew from 19 to almost 60 statements in total. This was because participants could add new statements to fill any problems gaps that we had overlooked.</p><p>Below you can see the top 10 most important statements according to our participants:</p><figure><img alt="A list of the top 10 most important statements according to our participants." src="https://cdn-images-1.medium.com/max/1024/0*Eoy_1hZjsE31vEtv.png" /><figcaption>This is a snapshot of the top 10 problems out of almost 60 statements in total.</figcaption></figure><p><em>Top tip: Choose just one segment to participate in your stack rank. For example, if we sent our stack rank to product managers and user researchers at the same time, it would really mess up our data. Also, to ensure that you get a robust sample size, we recommend aiming for 40 participants minimum.</em></p><h3>Step 5: Map The Most Important Problems To Your Landing Page</h3><p>Once all the data was collected, we clicked one button to sort all the statements by what participants felt was most important. From this shortlist, we picked the 5 most relevant problems that we could solve and starred them on our list.</p><p>We took the highest-ranking problem — <em>“Finding product-market fit for a new product/feature is an ongoing challenge as a PM”</em> — and we just turned this straight into our headline value proposition, “<em>Find Product-Market Fit For Your New Product or Feature”.</em> This remains the heading of our landing page today.</p><figure><img alt="A screenshot of our website with the headline “Find product-market fit for your new product or feature.”" src="https://cdn-images-1.medium.com/max/1024/0*FBaSWAq0E7y4MxHG.png" /><figcaption>The heading of our landing page after using CPSR.</figcaption></figure><p><em>Top tip: Turn the highest-ranking problem that your product solves into your landing page header. You have validated that this is important so you can be sure it will catch the attention of your target audience.</em></p><p>Then we moved down the list and turned the next highest ranking problems into a benefits section on the landing page:</p><ul><li><em>Problem:</em> Stakeholders want to talk more about solutions than about problems.</li><li><em>Benefit:</em> Understand the problem before building the solution</li><li><em>Problem:</em> It’s difficult to know if an idea has really been validated before we start building.</li><li><em>Benefit:</em> Easily validate your ideas</li><li><em>Problem:</em> My attention is pulled in too many directions at once</li><li><em>Benefit:</em> Focus your attention on what really matters</li><li><em>Problem:</em> It takes too long to conduct robust user research so we end up cutting corners sometimes</li><li><em>Benefit:</em> Robust user research without cutting corners.</li></ul><p>We added a small paragraph under each benefit to explain it further and added some images that reflected what we were communicating.</p><figure><img alt="A screenshot of our website after adding images and text alongside the headlines." src="https://cdn-images-1.medium.com/max/800/0*Pgig_dfFYrolQ-gM.png" /><figcaption>The “Benefits” section of our website written with the help of CPSR</figcaption></figure><p><em>Top Tip: Try and stay as close as possible to the original wording participants voted on in the stack rank. Rewording the most important problem statements using different words is tempting but can result in you losing the meaning that resonated with your participants. We learned this the hard way during customer interviews. We presumed that “identifying user unmet needs” meant the same thing as “validating ideas”, but our CPSR showed that they were interpreted completely differently by our target customers.</em></p><h3>Summary</h3><p>Through Customer Problem Stack Ranking, product managers told us which problems were most painful for them. We identified which of the most painful problems our product could solve. We turned these problem statements into our value proposition on our landing page. Conversion doubled, successful onboarding improved, traffic ballooned and we even got an “I love you” message.</p><p>In hindsight, much of this seems obvious. All we really did was ask customers about their biggest problems and then communicated back to them how we can solve these problems. It’s not rocket science, but it’s also not the most obvious method for writing landing page copy. I just wish it was something we knew about before we spent 7 months doing 100+ interviews.</p><p>The best part is that once the stack rank was complete it didn’t even require creativity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=566ab9de769b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/you-dont-need-to-be-creative-to-write-landing-pages-that-convert-566ab9de769b">You don’t need to be creative to write landing pages that convert</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Innovation Fallacy: Understanding When Startups Shouldn’t Innovate.]]></title>
            <link>https://medium.com/the-full-stack-researcher/the-innovation-fallacy-understanding-when-startups-shouldnt-innovate-b8a294b98c92?source=rss-71cac2cfe29d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8a294b98c92</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Éamon Cullen]]></dc:creator>
            <pubDate>Thu, 06 May 2021 12:31:11 GMT</pubDate>
            <atom:updated>2021-05-06T12:31:11.496Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oEVu9wo62-PC3nR5d9OCMw.png" /></figure><p>There is a proven formula for successful startups: identify a niche, offer something better than existing providers, and communicate your differentiation to the people who care enough to pay you.</p><p>Within this formula, founders must choose where to be innovative and where it makes more sense to follow the well worn path. Choosing to unnecessarily innovate will waste precious time on features that add no value. Choosing the wrong things to innovate will leave you without any appealing differentiation. The key is to innovate only where it adds value for customers.</p><p>When we launched OpinionX in late 2020, we made a mistake. We convinced ourselves that we needed to design our own onboarding experience due to our unique survey format. After weeks spent building multiple pages and rewriting the text for each paragraph and button, drop-off was stubbornly high. We set up usability tests and watched as people got lost and confused along the way.</p><p>The key realisation for us was that — despite our unique survey format — our users still considered OpinionX a survey tool. People have been building survey tools for decades and there are established norms that users expect, especially in onboarding. After replacing our custom onboarding for a standard version used by industry leaders, onboarding success improved dramatically.</p><p>Understanding which part of your product mix will be your point of differentiation helps you to understand which areas to copy, like dashboards, acquisition channels and landing page structure. Like survey onboarding, these are user experience challenges that people have been working on for years. Therefore the problem you are trying to solve within these builds likely has a better quality solution that’s been refined through multiple cycles of iteration.</p><p>Choosing to innovate multiple parts of your product wastes precious time as a startup and risks implementing a confusing user experience that will take weeks to optimize. However, there is an even riskier alternative; picking the wrong innovation as your main point of differentiation.</p><p>For example, a new search engine with customisable background colours is unlikely to be something that many people care enough about to pay for. A faster search engine that puts less strain on your device’s memory, like that of startup <a href="https://www.mightyapp.com/">Mighty</a>, is something that many people care about and are willing to pay considerable money to have.</p><p>A good framework to identify which ingredient in a startup recipe should be the point of differentiation is to find the problem that customers care most about solving — otherwise known as <a href="https://www.opinionx.co/blog/customer-problem-stack-ranking">Customer Problem Stack Ranking</a>. Changing the colour scheme of Chrome is a mild inconvenience but your laptop freezing during an important presentation is a burning problem. Understanding the relative importance of these two problems is what determines successful product strategy of a company like Mighty.</p><p>With this point of differentiation solidified, companies like Mighty use the same landing page format, billing flow and Notion hiring board template as every other startup. Not because they want to copy others — they’re just too busy focusing the spotlight on the things they uniquely do best.</p><p>Now we want to help you understand your customer’s problems so that you can understand your unique point of differentiation. It only takes a few minutes to <a href="http://opinionx.co/">set up a free Customer Problem Stack Rank on OpinionX</a>. If you want some help, <a href="https://www.opinionx.co/#request">request a free call</a> so that we can make sure that you get set up properly and answer any questions you have.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8a294b98c92" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-full-stack-researcher/the-innovation-fallacy-understanding-when-startups-shouldnt-innovate-b8a294b98c92">The Innovation Fallacy: Understanding When Startups Shouldn’t Innovate.</a> was originally published in <a href="https://medium.com/the-full-stack-researcher">The Full-Stack Researcher</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>