<?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[Product Collective - Medium]]></title>
        <description><![CDATA[For people who build, launch and scale world-class products. - Medium]]></description>
        <link>https://medium.com/product-collective?source=rss----b25d500b002f---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Product Collective - Medium</title>
            <link>https://medium.com/product-collective?source=rss----b25d500b002f---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:05:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/product-collective" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How Customer Development Benefits Salespeople]]></title>
            <link>https://medium.com/product-collective/how-customer-development-benefits-salespeople-4041e635eaff?source=rss----b25d500b002f---4</link>
            <guid isPermaLink="false">https://medium.com/p/4041e635eaff</guid>
            <category><![CDATA[customer-development]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Mike Belsito]]></dc:creator>
            <pubDate>Mon, 23 Nov 2015 13:24:49 GMT</pubDate>
            <atom:updated>2015-11-23T13:24:30.901Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*hj5iaZXy1x4-dsxjqdFVNw.jpeg" /></figure><p>I know from experience that “Product” and “Sales” can sometimes be two groups within a company that are kept at arm’s length. On one hand, salespeople are constantly in front of customers and genuinely have a lot of valuable input from customers that could be quite useful to the Product team. On the other hand, a Product Manager can discount the feedback a salesperson receives, as a customer may just be telling the salesperson something to make their “no” less of a blow. For example, hearing “Gee, if you only had X feature, then we’d surely come on board,” can be interpreted much differently by the salesperson than by the Product Manager.</p><p>A salesperson hears: “If you only had X feature, I’ll give you all of my money.”</p><p>A product manager hears: “You don’t have X feature? Oh good, I’ll blame my lack of commitment on that rather than tell you I don’t think your product is anything special.”</p><p>Because of this, sometimes sales is held out of the product development process altogether. This isn’t necessarily the <em>right</em> approach, but it’s an approach that many companies take. They simply rely on the Product team to be in touch with customers directly and make product-related decisions based on their own interactions. The sales team is just supposed to sell.</p><p>When a company takes this approach, should a salesperson even <em>care</em> about the product development process? Should they just “stick to what they know” and treat every sales meeting as simply an opportunity to sell something?</p><p>My answer to that is unequivocally <em>no</em>!</p><p>In fact, implementing customer development practices can not only give a salesperson product-related insights, but it can actually help them be better at their job of <em>selling</em>. I’m learning this first-hand, myself. Just over a year ago, I was brought on to lead Product at Movable. In that role, I implemented customer development practices in order to inform our product decisions. As the year wore on, I was promoted to President and ultimately helped find an attractive strategic acquirer. Post-acquisition, my focus is now on Business Development for the combined company. One might think that day-to-day is much different — and that’s true. However, I’ve been sure to maintain some customer development practices even though it might not be in my job description. In fact, every first meeting I have with a potential customer is treated as a customer development meeting… not a sales meeting.</p><p>Here’s what I’ve learned thus far:</p><p><strong>First meetings are easier to get when the context is a customer development meeting.</strong></p><p>Let’s face it, unless a potential customer reached out to you first asking for more information, they’re probably not sitting there waiting for your call to schedule a sales meeting. Getting that first meeting can be tough. Of course, if you believe in what you’re selling, that first meeting is sometimes all you feel you need in order to have a shot. Well, when you lead with the notion of the meeting being purely educational and you’re simply looking for their insights as an expert — that changes things. People like being known as the expert. It’s no lock, but it certainly helps open up the door a bit more.</p><p><strong>Customer Development leads to learning.</strong></p><p>If you actually treat the meeting like a customer development meeting, you’ll learn <em>how</em> to sell when you’re ready to sell. Any salesperson who’s worth their weight already knows how to ask questions to learn more about their customer and their situation. But in a true customer development meeting, you’ll have better context about the problem the customer is experiencing, the workaround solution (if any) they’ve come up with, and what a real, legitimate solution must have. You’ll dig into these areas without talking about your product… yet.</p><p><strong>If your product genuinely solves their problem, a 2nd meeting is even easier to land.</strong></p><p>This might seem like it’s the case even if the first meeting was a sales meeting. However, customer development meetings tend to be much more disarming. In a customer development meeting, customers can speak more freely. I’ve found that it’s easier to build rapport in a first-meeting when the intent of the meeting isn’t to sell a thing. By the time the meeting ends, the customer’s situation should be very clear. Based on their situation, your product will either be an ideal solution — or not. If it is, it’s worth sharing a bit more about the product for context. With the rapport developed, the customer could be more open minded and — if they agree that the product could be the ideal solution, that next meeting is something they’ll want.</p><p>For salespeople that aren’t familiar with holding Customer Development meetings, the <a href="http://steveblank.com/2009/09/17/the-path-of-warriors-and-winners/">Customer Development Manifesto</a> by Steve Blank is a must-read. This will help you set the tone for your first meetings so that you can reap the benefits and, ultimately, land more sales as a result.</p><p><a href="http://indsum.com/how-customer-development-benefits-salespeople/">This post originally appeared at indsum.com.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4041e635eaff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-collective/how-customer-development-benefits-salespeople-4041e635eaff">How Customer Development Benefits Salespeople</a> was originally published in <a href="https://medium.com/product-collective">Product Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Absolute Must-Read Articles for Product Managers]]></title>
            <link>https://medium.com/product-collective/5-absolute-must-read-articles-for-product-managers-4e61082a033c?source=rss----b25d500b002f---4</link>
            <guid isPermaLink="false">https://medium.com/p/4e61082a033c</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Paul McAvinchey]]></dc:creator>
            <pubDate>Thu, 29 Oct 2015 17:53:23 GMT</pubDate>
            <atom:updated>2015-10-29T17:53:40.211Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*Gfr2R3vKbyIFKt-TkgNV5w.jpeg" /></figure><p>Product Managers are time-starved. There are always 100 things on their to-do lists when they know that about 20 of them will actually get done today. So let’s cut through the build-up and get right to it. This post curates the best, current must-reads for Product Managers. Enjoy, share, and then get on with your day! After all, you’ve got products to tend to…</p><p><a href="https://community.uservoice.com/blog/validate-product-idea-feature/"><strong>Validate or Bust: Testing new feature and product ideas before you build</strong> </a>via Heahter McCloskey at the UserVoice Blog</p><p>This post discusses the age-old conundrum that many product managers face: The worry of whether their new product will actually work out. But you don’t have to wait until you’re product is out in the wild to have an idea of whether it will be successful. There are many things that you can do well before the day of launch to understand if your solution even is solving the right problem in the first place.</p><p><a href="http://andrewchen.co/the-next-feature-fallacy-the-fallacy-that-the-next-new-feature-will-suddenly-make-people-use-your-product/"><strong>The Next Feature Fallacy: The fallacy that the next new feature will suddenly make people use your product.</strong> </a>via <a href="http://twitter.com/andrewchen">Andrew Chen</a> at AndrewChen.co</p><p>Stop me if you’ve heard this one, Product Managers. “We lost the sale because we don’t have Feature X. If you just added this feature, I <em>know</em> I’d be able to close more business.” Thanks sales guy. I can empathize, though. After all, this is what customers tell salespeople sometimes. But you know better, Product Manager, don’t you? This article reaffirms the notion that the next feature just may not translate into more sales or more users (complete with numbers to back it up).</p><p><a href="http://www.cindyalvarez.com/lean/3-questions-stop-asking"><strong>Three Questions We Should Stop Asking</strong> </a>via <a href="http://twitter.com/cindyalvarez">Cindy Alvarez</a> at CindyAlvarez.com</p><p>Whenever we are able to convince a potential customer that fits a certain persona with us, it’s easy to get all giddy and make a list of questions to ask. After all, we know in our heart-of-hearts that real, customer feedback is always a good thing. Except sometimes it’s not. Not when you’re asking the wrong questions, anyway.</p><p><a href="http://blog.brainstation.io/brainwaves/2015/5/13/6-tools-for-the-product-manager-in-you"><strong>Six Tools for the Product Manager in You</strong> </a>via <a href="http://twitter.com/daniellethe">Danielle Thé</a> on BrainStation</p><p>Let’s face it, we all would like to make our lives a little bit easier as Product Managers, right? Lucky for us, there are troves of companies creating products designed to do just that. But a lot of them just end up creating more headaches than help. Not these, though. These are 6 of the best tools for Product Managers that you can find. (Spoiler alert: Two of them are from sponsors of <a href="http://industry2016.wpengine.com/">Industry 2015</a>!)</p><p><a href="https://medium.com/@mikeatherton/ux-is-ui-105460807734"><strong>UX is UI</strong> </a>via <a href="https://twitter.com/mikeatherton">Mike Atherton</a> on Medium</p><p>We’ve all seen that meme. The paved road (caption: UI) and the organically created dirt path that students are actually using (caption: UX). It’s not as simple as that, though. In fact, the reality is that we might be thinking about UI and UX all wrong.</p><p>Did you come across an amazing article that every Product Manager should know about? Email me at mike [at] productcollective dot com and let me know!</p><p><em>Originally published at </em><a href="http://indsum.com/5-absolute-must-read-articles-for-product-managers/"><em>indsum.com</em></a><em> on June 5, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e61082a033c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-collective/5-absolute-must-read-articles-for-product-managers-4e61082a033c">5 Absolute Must-Read Articles for Product Managers</a> was originally published in <a href="https://medium.com/product-collective">Product Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop what you’re doing, your product needs to die]]></title>
            <link>https://medium.com/product-collective/stop-what-you-re-doing-your-product-needs-to-die-9a45d5994f39?source=rss----b25d500b002f---4</link>
            <guid isPermaLink="false">https://medium.com/p/9a45d5994f39</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Paul McAvinchey]]></dc:creator>
            <pubDate>Thu, 29 Oct 2015 17:53:10 GMT</pubDate>
            <atom:updated>2015-10-29T17:49:36.916Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/878/1*ShHkk4KkchJqxgX9XB92cg.png" /></figure><p>Before you think about building another feature or enhancing the look and feel of your interface to save your flagging product, stop and take a step back. Are you sure that you don’t need to take it around the back of the barn and shoot it? Hat tipped to Kevin O’Leary.</p><p>It’s easy to be distracted by incremental improvements. Particularly when you are seeing <em>some </em>usage of your app. But there are bigger questions to ask other than if something is working or not. Ultimately, it must be working phenomenally well to be seriously considered a business.</p><p>Let’s say you have a consumer-focused subscription service (like we did with <a href="http://diddlyi.com/">Diddlyi.com</a>) and you’ve seen hundreds sign up at $9.95/month over a period of a year. At first you think you’ve spotted <em>traction, </em>or what Paul Singh calls “the new intellectual property”. 100 people in 3 months and about $1,000 as your monthly recurring revenue (MRR). You know there are people canceling and you’ve even gone to the trouble of calculating the monthly churn rate which you find is about 6%. Not bad you say since that’s only 6 people lost for 30 people gained that month.</p><p>Meanwhile you’re following <a href="https://blog.intercom.io/prioritising-features-wholl-use-it-how-often/">Des Traynor’s rules for finding the optimal features</a> to develop for your service and are convinced that this is continuing to drive growth. In fact, you’re up to 40 new customers a month now.</p><p>Then when you get to 200 customers you start noticing something. Despite all the development and design enhancements that you’ve been staying up all night working on, the churn rate is barely budging. It sticks at 6% so you’re losing 12 customers a month now. Plus your onboarding improvements seemed to reach a peak with 40 customers a month following through to signing up for a subscription. OK, 200 customers/$2,000 MRR/6% churn/40 new customers/12 cancelations.</p><p>Then this happens:</p><p>300 customers/$3,000 MRR/6% churn/40 new customers/18 cancelations</p><p>400 customers/$4,000 MRR/6% churn/40 new customers/24 cancelations</p><p>This is where it gets really tricky. Remember, you’re pulling in $4,000 a month, you’ve been working on this for a year or two, 40 new people every month are seeing the benefit of your service and 400 customers are using your product regularly enough that they can justify the expense.</p><p>But … for all the work you are doing you are only gaining 16 customers a month. That’s an additional $160/month. Even if the expenses associated with your business are low just thinking about the profit after tax is taken away is depressing.</p><p><strong>So what do you do?</strong></p><p>I’d be interested to hear what you think in the comments, but here are some ideas that come to me:</p><ol><li>Consider it a small lifestyle business to complement a salary from elsewhere.</li><li>Admit that <a href="http://andrewchen.co/why-consumer-product-metrics-are-all-terrible/">consumer product metrics are all terrible</a> (thanks to Andrew Chen who also inspired this post with <a href="http://andrewchen.co/the-next-feature-fallacy-the-fallacy-that-the-next-new-feature-will-suddenly-make-people-use-your-product/">this</a>).</li><li>Completely rethink how your product is being delivered (which probably involves at least heavily maiming it first).</li><li>Take it out the back!</li></ol><p><em>Originally published at </em><a href="http://indsum.com/stop-what-youre-doing-your-product-needs-to-die/"><em>indsum.com</em></a><em> on June 2, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a45d5994f39" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-collective/stop-what-you-re-doing-your-product-needs-to-die-9a45d5994f39">Stop what you’re doing, your product needs to die</a> was originally published in <a href="https://medium.com/product-collective">Product Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do these 3 things before launching your product]]></title>
            <link>https://medium.com/product-collective/do-these-3-things-before-launching-your-product-d02bd0087a41?source=rss----b25d500b002f---4</link>
            <guid isPermaLink="false">https://medium.com/p/d02bd0087a41</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Paul McAvinchey]]></dc:creator>
            <pubDate>Thu, 29 Oct 2015 17:52:54 GMT</pubDate>
            <atom:updated>2015-10-29T17:51:14.253Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YTUNQSbzqBQSM8Ds8jD2vg.jpeg" /></figure><p>Whether you’re a startup that is working on a new game-changing innovation or an established company adding a product to your growing portfolio, you likely experience a very common and real issue: You’re not quite sure if the product you’ve been working on is ready to be launched.</p><p>On one hand, many people feel that getting their product out into the real world as early as possible is the best route, as it allows you to replace internal hypotheses with fact. After all, once people start using your product and giving you real feedback, any assumptions you’ve made can actually be tested. You can truly understand whether your product is solving the problem you set out to alleviate.</p><p>Of course, you can only launch a product once. Therefore, there are many that feel that every last detail should be ironed out before launching. Every potential issue or possible problem should be thought about and planned for. Then, and only then, should a product even be considered ready for prime time.</p><p>While these are two ends of the spectrum, neither is necessarily right or wrong. It’s true that you should have a well-thought out product plan and your launch should be green-lighted when you’ve accomplished your plan. However, you should also realize that not every detail can be resolved or even imagined before launch. As the quote by Mike Tyson goes, “Everybody has a plan until you get punched in the face.” You should realize and even assume that once your product is launched, there are going to be times where it feels like you’re getting punched in the face. No matter how many times you’ve thought through certain scenarios, know that certain issues will arise that will simply never have been thought of before.</p><p>Regardless of what end of the spectrum you feel like you fall on when considering a product launch, there are three things that you absolutely should do before considering launching any product — whether it’s physical or digital:</p><p><strong>1. Understand the real problem you’re trying to solve.</strong></p><p>This may sound very basic, and it is. But so many times products are launched without actually solving a problem that exists in the real world. Instead, they are solutions first — without a real problem to solve. If you’re unsure if the product you’re developing is actually solving a real problem, ask yourself this question: What was the genesis for the creation of this product in the first place? How did it actually <em>begin</em>? Was it an issue or roadblock that somebody kept running into? Or, was it a brainstorm of “Hey, what’s the next new cool thing we could launch?” If it’s the latter, you may want to take a giant step back and do some soul-searching. If your product isn’t alleviating a problem for somebody, it may be very difficult for people to see through to your value proposition. This doesn’t mean that you should scrap that product. But you may take some different approaches with design or consider different features once you’ve realized the true problem you’re solving.</p><p><strong>2. Get face to face with customers.</strong></p><p>The only way that you can understand if you’re solving a real problem is to talk to the very people <em>with</em> that problem. Identifying your target base of potential customers and literally talking to them is critical, and no launch should take place unless you’ve had several conversations with these potential customers. Also, by talking with customers — I mean just that. I’m not talking about holding a formal focus group or sending out surveys. Those things could be helpful, too. But regardless, you should have real-life conversations with actual, real-life customers. Understand where they’re coming from. Learn more about the problem that your product is trying to solve for. You’ll learn so much more about the context of their problem once you have a real conversation with them. Have the conversation in a setting that they’re comfortable with — ideally, with context to the problem you’re trying to solve. For instance, if you’re developing a new detergent — perhaps the conversation could be in their laundry room. If you’re developing a mobile app for travelers, perhaps you could have the conversation in a city’s visitor center. Regardless of where you have the conversation, be sure that you <em>have the conversation.</em></p><p><strong>3. Put a prototype in your customers’ hands.</strong></p><p>Now that the lines of communication are open between you and real-life customers, open it back up once you get to the prototype stage. After all, it’s not enough to know that your product is intending to solve a problem that actually affects your customers. You should get feedback on whether your solution is just that — a solution. Allow customers to give you this feedback well before you launch into the real world. When you put a prototype in your customers’ hands, you’ll quickly get a sense of where they’re gravitating towards. You’ll see first-hand what features and attributes actually resonate with them, and which are overlooked. These nuances are important, as you could quickly see if you need to go back to the drawing board, or if you’re on the right track.</p><p>Yes, it’s true that some things can only be learned once you launch your product into the real world. And getting to that point requires a lot of focus and dedication. But don’t do it in a vaccum. If you ensure that you’re doing these three things <em>before</em> you launch your product, you’ll be in a much better place once your solution is out in the real world.</p><p><em>Originally published at </em><a href="http://indsum.com/do-these-3-things-before-launching-your-product/"><em>indsum.com</em></a><em> on May 26, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d02bd0087a41" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-collective/do-these-3-things-before-launching-your-product-d02bd0087a41">Do these 3 things before launching your product</a> was originally published in <a href="https://medium.com/product-collective">Product Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How a Trip to the Mall Helped Me Launch a New Product]]></title>
            <link>https://medium.com/product-collective/how-a-trip-to-the-mall-helped-me-launch-a-new-product-ab5c92683b0a?source=rss----b25d500b002f---4</link>
            <guid isPermaLink="false">https://medium.com/p/ab5c92683b0a</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Paul McAvinchey]]></dc:creator>
            <pubDate>Thu, 29 Oct 2015 17:52:08 GMT</pubDate>
            <atom:updated>2015-10-29T17:47:03.544Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RCH4XhdHdmPQHSCzaHB1jA.png" /></figure><p>A product manager’s life is never easy.When you’re running product for a startup, life can be even more tricky.On one hand, there are likely dozens, if not hundreds, of new features and products that are already queued up which you’d love to launch.Yet, at the same time, you know in your heart that it’s critical to get real customer input throughout the process.The reality is that even if you were to get to the very end of your product/feature wish-list queue — the information that you were basing that specific product/feature off of is already outdated.</p><p>Currently, I serve as the President of Movable — a B2B platform that inspires groups to move more.We have our own line of fitness activity trackers (<a href="https://shop.movable.com/devices/movband2.html">Movband 2</a> and <a href="https://shop.movable.com/devices/movband3.html">Movband 3</a>) and our own Dashboard that is designed specifically for groups.Like many other startups, we run a fairly lean ship.Everybody is busy, and we all wear many hats.</p><p>Late last winter, we had just received a new batch of prototypes for our newest product, Movband 3.Yet, we had some critical decisions to make about the product.What color wristband should be included out of the box?Did it need to be thinner than the prototype wristband we received?Would users even want to wear the product on their wrist?Or would it be more comfortable on their hip?</p><p>We could spend tens of thousands of dollars and several months to work with aresearch firm to help us answer these questions.But we’re a startup company.We have sales forecasts to hit — and a budget to stay within.Yet, I didn’t feel comfortable just making these decisions at random.Even our talented Creative Director would be making a guess (albeit, probably a more educated guess than I could make).Something wasn’t sitting quite right with me.</p><p>So I went to the mall.Sort of.</p><p>Employees of large enterprise-organizations represented one of our larger customer segments for Movband 3.It just so happened that around noon each day, hundreds of these employees congregate in one of the handful of food courts that are spread out within Downtown Cleveland, Ohio — just a short drive from our suburban office.I had a crazy thought.What if we were to just “crash the food court” and put our prototypes in the hands of these employees — and simply ask them a few questions?</p><p>No doubt, my suggestion resulted in some eye-rolling and smirks around the office.More than a couple of my colleagues suggested that if I didn’t get kicked out, most people would surely give me the cold shoulder.Yet, nobody could find a good reason why we shouldn’t at least try.So, try we did.</p><p>The result?Two of us went to that mall during lunch armed with a handful of prototypes and a moleskin notebook.Within 90 minutes, we had come across over 20 people who fell right in our target customer demographic who were not only willing to talk to us, but seemed excited to provide feedback.That feedback that we received helped us make the call on a couple of urgent open questions.</p><p>Did we make the right call?Was the feedback we received quantitative enough to be statistically significant?</p><p>Who knows.But what I do know is that the decisions we made weren’t just pure guesses and “gut feels.”We took what we learned by talking to real people and combined it with some of our own internal instincts.It’s yet to be seen whether we made the right call, as we’re early into our launch, but as a product leader, I’m much more confident in the decisions we made as a result.</p><p>Do you have some questions that need answered about your product?Have you been struggling with which route to go?Depending on your product, perhaps a visit to the mall (or the park, or a café, etc) might help.</p><p>If you’re interested in meeting other like-minded product people and learning from product leaders like Nir Eyal, Trevor Owens, Mina Radhakrishnan and others, you should meet me at <a href="http://industry2016.wpengine.com/">Industry 2015</a>. We’ll be spending 2 days focused on “product” in my hometown and heart of the “Rust Belt Revival”, Cleveland, Ohio.</p><p><em>Originally published at </em><a href="http://indsum.com/how-a-trip-to-the-mall-helped-me-launch-a-new-product/"><em>indsum.com</em></a><em> on April 18, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab5c92683b0a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/product-collective/how-a-trip-to-the-mall-helped-me-launch-a-new-product-ab5c92683b0a">How a Trip to the Mall Helped Me Launch a New Product</a> was originally published in <a href="https://medium.com/product-collective">Product Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>