<?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[Elezea - Medium]]></title>
        <description><![CDATA[I write and share articles and resources about product management, software development, leadership, technology, and internet culture. - Medium]]></description>
        <link>https://medium.com/elezea?source=rss----eb8f6a9691fc---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Elezea - Medium</title>
            <link>https://medium.com/elezea?source=rss----eb8f6a9691fc---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 19:48:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/elezea" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Don’t get customers hooked, focus on healthy retention instead]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/elezea/dont-get-customers-hooked-focus-on-healthy-retention-instead-9d3dff6d1982?source=rss----eb8f6a9691fc---4"><img src="https://cdn-images-1.medium.com/max/2600/1*R9hDjtwauqsIZ3K5caC2sw.jpeg" width="3872"></a></p><p class="medium-feed-snippet">I&#x2019;m getting increasingly nervous about the ongoing emphasis on getting users &#x201C;hooked&#x201D;, which is taking the product world by storm.</p><p class="medium-feed-link"><a href="https://medium.com/elezea/dont-get-customers-hooked-focus-on-healthy-retention-instead-9d3dff6d1982?source=rss----eb8f6a9691fc---4">Continue reading on Elezea »</a></p></div>]]></description>
            <link>https://medium.com/elezea/dont-get-customers-hooked-focus-on-healthy-retention-instead-9d3dff6d1982?source=rss----eb8f6a9691fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/9d3dff6d1982</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Rian van der Merwe]]></dc:creator>
            <pubDate>Thu, 01 Aug 2019 17:59:03 GMT</pubDate>
            <atom:updated>2019-08-01T17:59:02.963Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Prioritization, product stewardship, and the hardest part about being a product manager]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/elezea/prioritization-product-stewardship-and-the-hardest-part-about-being-a-product-manager-e5af1c528a1e?source=rss----eb8f6a9691fc---4"><img src="https://cdn-images-1.medium.com/max/2600/1*zmfjlByiruLRDXOLyL2uFQ.jpeg" width="4000"></a></p><p class="medium-feed-snippet">I used to believe that the hardest part about being a product manager is effective prioritization. I don&#x2019;t think that&#x2019;s true any more. I&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/elezea/prioritization-product-stewardship-and-the-hardest-part-about-being-a-product-manager-e5af1c528a1e?source=rss----eb8f6a9691fc---4">Continue reading on Elezea »</a></p></div>]]></description>
            <link>https://medium.com/elezea/prioritization-product-stewardship-and-the-hardest-part-about-being-a-product-manager-e5af1c528a1e?source=rss----eb8f6a9691fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/e5af1c528a1e</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Rian van der Merwe]]></dc:creator>
            <pubDate>Tue, 16 Jul 2019 20:18:05 GMT</pubDate>
            <atom:updated>2019-07-16T20:18:05.610Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why it’s not a good idea to define a fixed project scope]]></title>
            <link>https://medium.com/elezea/why-its-not-a-good-idea-to-define-a-fixed-project-scope-da0ab0eb5e72?source=rss----eb8f6a9691fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/da0ab0eb5e72</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Rian van der Merwe]]></dc:creator>
            <pubDate>Tue, 30 Apr 2019 15:52:20 GMT</pubDate>
            <atom:updated>2019-04-30T15:52:20.864Z</atom:updated>
            <content:encoded><![CDATA[<h4>There are too many unknowns, too many variables, and too many things can change along the way.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nag1sxQYyUFXFlWdXBmfQQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/BY66BwIa9Bg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Lysander Yuen</a> on <a href="https://unsplash.com/search/photos/limit?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>There are some decent day-to-day work tips in Sierra Newell’s <a href="https://www.productplan.com/project-management-principles/">7 Project Management Principles Product Managers Can Learn From</a>. There’s one principle I wanted to expand on, and that’s “Define the scope and stick to it”. First, from the post:</p><blockquote>Product managers should set the scope of their products’ development as early in the process as possible. Learning how to say no to product requests is a valuable skill. But it is also a reactive method of keeping your product’s development on track. Instead, be proactive. Define your product’s scope from the beginning, and keep development within that scope.</blockquote><p>I know that “define the scope and stick to it” is fairly common practice, but I don’t think it’s a good way to build product at all. First, that principle tends only to define one side of the spectrum — how not to <em>add</em> scope. It doesn’t, however, talk about the need to sometimes <em>reduce</em> scope.</p><blockquote>If you define a “fixed scope” and say you won’t go over it, but then things take longer than anticipated (as they are prone to do in software) and you have no mechanism to deal with it, you’re going to get yourself in trouble.</blockquote><p>Because at that point, you “committed” to a scope that won’t change, presumably saying “no” to a bunch of things, and <em>still</em> you’re “late” in delivery.</p><p>This is why I’m a firm proponent of “fixed time, flexible scope” projects. Under that principle, you don’t lock down the scope for forever and ever. You commit to an initial body of work, and an expected timeframe. Then, if something happens along the way — a developer gets pulled into an emergency, or something takes longer than expected — you have a mechanism to deal with it. Since you didn’t lock down the scope, you don’t have to choose between being “late” or the team working themselves to death. You can <em>reduce</em> the scope of your work to fit into the time you gave yourselves to do it in.</p><p>There’s another scenario under which I would go even further and advocate for “flexible time, flexible scope” projects.</p><blockquote>There are instances where increasing scope (and time) is the Right Thing To Do for a project.</blockquote><p>For instance, if the choice is between a hacky way of implementing a feature, and extending functionality properly with future-proofing in mind, which would add two weeks to a project, I believe it’s pretty much a no-brainer that you need to add the two weeks.</p><p>This is why I think fixing scope is a dangerous practice. There are too many unknowns, too many variables, and too many things can change along the way. We shouldn’t let our process get in the way of good product decisions.</p><p><em>Originally published at </em><a href="https://elezea.com/2019/04/dont-fix-scope/"><em>https://elezea.com</em></a><em> on April 29, 2019. Sign up for </em><a href="https://elezea.com/newsletter/"><em>my weekly newsletter</em></a><em> with product management articles and resources.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da0ab0eb5e72" width="1" height="1" alt=""><hr><p><a href="https://medium.com/elezea/why-its-not-a-good-idea-to-define-a-fixed-project-scope-da0ab0eb5e72">Why it’s not a good idea to define a fixed project scope</a> was originally published in <a href="https://medium.com/elezea">Elezea</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product specifications: our template and process]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/elezea/product-specifications-our-template-and-process-e9589b42caba?source=rss----eb8f6a9691fc---4"><img src="https://cdn-images-1.medium.com/max/2600/1*cRREZsuKN5y5ajebVWQKpA.jpeg" width="5604"></a></p><p class="medium-feed-snippet">A follow-up post to share our product spec template and explain our process in more detail.</p><p class="medium-feed-link"><a href="https://medium.com/elezea/product-specifications-our-template-and-process-e9589b42caba?source=rss----eb8f6a9691fc---4">Continue reading on Elezea »</a></p></div>]]></description>
            <link>https://medium.com/elezea/product-specifications-our-template-and-process-e9589b42caba?source=rss----eb8f6a9691fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/e9589b42caba</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Rian van der Merwe]]></dc:creator>
            <pubDate>Mon, 22 Apr 2019 00:09:02 GMT</pubDate>
            <atom:updated>2019-04-22T00:09:02.446Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The dangerous rise of “crazy-busy” product managers]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/elezea/the-dangerous-rise-of-crazy-busy-product-managers-d510333d7dca?source=rss----eb8f6a9691fc---4"><img src="https://cdn-images-1.medium.com/max/2000/1*dnwA_QfQKF9Rz9PT60uDOA.jpeg" width="2000"></a></p><p class="medium-feed-snippet">It&#x2019;s time to talk about how &#x201C;crazy-busy PM&#x201D; thinking is harmful to individuals and our industry.</p><p class="medium-feed-link"><a href="https://medium.com/elezea/the-dangerous-rise-of-crazy-busy-product-managers-d510333d7dca?source=rss----eb8f6a9691fc---4">Continue reading on Elezea »</a></p></div>]]></description>
            <link>https://medium.com/elezea/the-dangerous-rise-of-crazy-busy-product-managers-d510333d7dca?source=rss----eb8f6a9691fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/d510333d7dca</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Rian van der Merwe]]></dc:creator>
            <pubDate>Sat, 13 Apr 2019 13:18:17 GMT</pubDate>
            <atom:updated>2019-04-22T00:10:12.279Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to make “product principles” more useful]]></title>
            <link>https://medium.com/elezea/how-to-make-product-principles-more-useful-a87f0b98ea96?source=rss----eb8f6a9691fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/a87f0b98ea96</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Rian van der Merwe]]></dc:creator>
            <pubDate>Thu, 14 Mar 2019 20:19:48 GMT</pubDate>
            <atom:updated>2019-03-14T20:20:48.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*6YkbQAcGUhQyOHbva32iJg.jpeg" /></figure><p>There’s an interesting discussion going on in the <a href="https://elezea.com/community/">Elezea Community</a> about “Product Principles”. What they are for, when you need them, how they can be made more useful, etc. A couple examples given are Intercom’s <a href="https://www.intercom.com/blog/how-we-build-software/">set of guidelines for making decisions</a>, <a href="https://medium.com/u/85f9656d8860">Dan(iel) Ritz(enthaler)</a>’s <a href="https://medium.com/intensive-code-unit/interface-design-values-3c32c0dc06bc">interface design values</a> and <a href="https://wildbit.com/blog/2017/05/09/revisiting-the-wildbit-values">my own company’s values</a>.</p><p>The biggest challenge I see with principles like these is figuring out how to make them specific enough to help us make decisions. The further I get into reading <a href="https://www.amazon.com/Good-Strategy-Bad-Difference-Matters-ebook/dp/B004J4WKEC/ref=sr_1_1?sr=8-1&amp;keywords=good%2Bstrategy%2Bbad%2Bstrategy&amp;s=gateway&amp;tag=leavethegreat-20&amp;qid=1552593721">Good Strategy, Bad Strategy</a> the more I realize how much we tend to hide behind nice words, when in most cases those nice words don’t actually change our behavior in any meaningful way. For example:</p><blockquote>Bad strategy is not the same thing as no strategy or strategy that fails rather than succeeds. Rather, it is an identifiable way of thinking and writing about strategy that has, unfortunately, been gaining ground. Bad strategy is long on goals and short on policy or action. It assumes that goals are all you need. It puts forward strategic objectives that are incoherent and, sometimes, totally impracticable. It uses high-sounding words and phrases to hide these failings.</blockquote><p>I fear that “product principles” are prone to be made up almost exclusively of “fluff”:</p><blockquote>Fluff is superficial restatement of the obvious combined with a generous sprinkling of buzzwords. Fluff masquerades as expertise, thought, and analysis. A hallmark of true expertise and insight is making a complex subject understandable. A hallmark of mediocrity and bad strategy is unnecessary complexity — a flurry of fluff masking an absence of substance.</blockquote><p>I think product principles, in particular, need to be detailed and specific enough so that they affect day-to-day decision making. This is similar to how we should use Personas (and why so many people hate Personas). If you just put a Persona’s face on a coffee mug, that’s not going to be very useful. But if you’re able to say, “this feature would be useful for a persona that’s not in our target market so we’re not going to build it”, that’s an entirely different story.</p><p>Which leads me to wonder if what we call “product principles” should rather just be the combination of a well-defined design system and content strategy. <a href="http://style.helpscout.com/">HelpScout’s Style Guide</a> immediately comes to mind as a good example of this. Because what are “Product Principles” for if they don’t help us make product decisions?</p><p><em>Do you have thoughts to add on this topic? </em><a href="https://elezea.com/community/"><em>Join the community</em></a><em>.</em></p><p><em>Originally published at </em><a href="https://elezea.com/2019/03/make-product-principles-useful/"><em>elezea.com</em></a><em> on March 14, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a87f0b98ea96" width="1" height="1" alt=""><hr><p><a href="https://medium.com/elezea/how-to-make-product-principles-more-useful-a87f0b98ea96">How to make “product principles” more useful</a> was originally published in <a href="https://medium.com/elezea">Elezea</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I look for in product management software]]></title>
            <link>https://medium.com/elezea/what-i-look-for-in-product-management-software-e792c8760fe8?source=rss----eb8f6a9691fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/e792c8760fe8</guid>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Rian van der Merwe]]></dc:creator>
            <pubDate>Tue, 26 Feb 2019 14:54:53 GMT</pubDate>
            <atom:updated>2019-02-26T18:46:34.206Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve had this vague sense for a while that I need to dig into the product management software space a lot more. So on Friday I just did it — I signed up for a bunch of accounts and started playing around. As I went through each product I realized two things:</p><ol><li>I didn’t know what I was looking for.</li><li>Most of the products I was looking at didn’t know why they wanted me to use it either. The landing pages are all great, but once I was <em>in</em> the product, it was like a different (and very confusing) world. Which is kind of ironic for a product that’s aimed at product managers.</li></ol><p>So I took a step back and asked myself <em>why</em> I’m actually doing this. What are the issues I’m hoping to address with software? What am I looking for?</p><blockquote><strong>In short, I am looking for a better way to plan.</strong> JIRA is a great execution tool — I don’t want to change that part. But JIRA is a <em>terrible</em> planning tool.</blockquote><p>And our current process of using Basecamp and Dropbox Paper for planning works <em>just ok</em> for me. The combination lacks a bunch of things to make it as effective as it can be.</p><p>I then identified what I would need to feel like our planning and scheduling process is effective and efficient:</p><ul><li>A visual, lightweight, flexible representation of our product ideas and overall strategy, to help us with prioritization.</li><li>Prioritization scoring (customer / business impact, effort, etc.). I’d like to try a version of <a href="https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/">RICE</a> at some point, but it should be flexible enough to use whatever system we want.</li><li>Incorporating, summarizing, and linking customer feedback from a variety of sources. We currently do this in JIRA, and it’s not a great workflow.</li><li>A way to go from general idea to product specifics in an orderly and predictable fashion. Right now we use JIRA, Confluence, Dropbox Paper, and Basecamp, and that can get a little confusing.</li></ul><p>This gave me the framework I needed to evaluate the different products I was looking at. I’m not done evaluating, but right now <a href="https://www.productboard.com/">productboard</a> is the one that seems to fit our particular culture and goals the best.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JOwVIAAntplu6uFZ.png" /><figcaption>productboard’s process</figcaption></figure><p>Here are the list of things <em>productboard</em> has going for it:</p><ul><li>The one thing that makes it stand out from all the others is that it’s a <em>flexible system</em> rather than a <em>process</em> (see the overview diagram above). Instead of forcing a particular software development process, it has no opinion on the specific methodology you use to prioritize and get work done. It’s focused on letting you use your own way to gather customer insights, define business goals, and prioritize work.</li><li>It will let us gather all user insights together, and prioritize features based on our goals and objectives (or “drivers” in the <em>productboard</em> language).</li><li>It will let us easily share, communicate, and <em>change</em> the plan without getting too formal about it.</li><li>If we wanted to, we could have a public-facing portal to get feedback on ideas, like <a href="https://portal.productboard.com/pb/tabs/7-under-consideration">this</a>.</li></ul><p>Oh, and their <a href="https://help.productboard.com/getting-started/1-why-productboard">Why productboard?</a> page is pretty solid, especially this phrase:</p><blockquote>a way that provides transparency, fosters collaboration, and encourages alignment with the broader product team.</blockquote><p>I’m not done evaluating yet, and who knows where we’ll end up. But I thought I’d share my initial thoughts and explorations of this interesting meta-industry.</p><p><em>Originally published at </em><a href="https://elezea.com/2019/02/what-i-look-for-in-product-management-software/"><em>elezea.com</em></a><em> on February 26, 2019. </em><a href="https://elezea.com/newsletter/"><em>Get a weekly email</em></a><em> with high quality articles and resources on software product management and desig</em>n</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e792c8760fe8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/elezea/what-i-look-for-in-product-management-software-e792c8760fe8">What I look for in product management software</a> was originally published in <a href="https://medium.com/elezea">Elezea</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product management doesn’t require in-person collaboration to be effective]]></title>
            <link>https://medium.com/elezea/product-management-doesnt-require-in-person-collaboration-to-be-effective-a170840b86ba?source=rss----eb8f6a9691fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/a170840b86ba</guid>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Rian van der Merwe]]></dc:creator>
            <pubDate>Tue, 05 Feb 2019 20:20:33 GMT</pubDate>
            <atom:updated>2019-02-05T20:21:40.459Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pmqiG7teL7vGKs-vK4RRhQ.jpeg" /></figure><p>Remote product management is <a href="https://medium.com/elezea/remote-product-management-challenges-and-opportunities-3fd5cefcf6bc">something I’ve written about before</a>, so I read Julie Caprio’s <a href="https://productcraft.com/perspectives/four-keys-to-successful-remote-pm/">Four Keys to Successful Remote Product Management</a> with interest. In general I agree with the advice she gives in the article, but there is one section that I wanted to respond to briefly:</p><blockquote>Product management, on the other hand, was more of a struggle. A PM needs to set strategy and come up with a vision for the product. Without the potential for spontaneous in-person conversation and even inspiration, this part of the job gets a bit harder. Creating a vision for a product is a collaborative effort involving several stakeholders; when the team is distributed, it’s more difficult to align on goals, tasks, and project ownership.</blockquote><p>It’s a common criticism of remote work that it’s more difficult to collaborate remotely. But I think this is the conventional wisdom only because we try to recreate the office experience for remote work. Since offices rely on <em>synchronous interactions</em>, we use the same lens to try to make remote work effective, and that’s just not going to work.</p><p>If we optimize for <em>asynchronous communication</em> instead — which is what remote work is so good at — collaboration can be extremely effective. Perhaps even <em>more</em> effective than office collaboration, because everyone can provide thoughtful responses on whatever topic they are discussing on their own time. As Brian de Haaff points out in <a href="https://www.inc.com/brian-de-haaff/3-ways-remote-workers-outperform-office-workers.html">Remote Workers Are Outperforming Office Workers — Here’s Why</a>:</p><blockquote>Without being able to lean on physical proximity, remote workers must reach out to one another frequently and with purpose. This leads to stronger collaboration and camaraderie.</blockquote><p>As counterintuitive as it sounds, this has been my experience as well. As long as we shift the way we think about collaboration away from the office mentality, and use the right tools, I don’t think remote collaboration is less effective than in-person work at all.</p><p><em>Originally published at </em><a href="https://elezea.com/2019/02/product-management-in-person-collaboration/"><em>elezea.com</em></a><em> on February 5, 2019.</em></p><p><a href="https://medium.com/elezea/remote-product-management-challenges-and-opportunities-3fd5cefcf6bc">Remote product management: challenges and opportunities</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a170840b86ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/elezea/product-management-doesnt-require-in-person-collaboration-to-be-effective-a170840b86ba">Product management doesn’t require in-person collaboration to be effective</a> was originally published in <a href="https://medium.com/elezea">Elezea</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The power of “why now?” as a prioritization technique]]></title>
            <link>https://medium.com/elezea/the-power-of-why-now-as-a-prioritization-technique-4cb9b24cb38f?source=rss----eb8f6a9691fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/4cb9b24cb38f</guid>
            <category><![CDATA[planning]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[prioritization]]></category>
            <dc:creator><![CDATA[Rian van der Merwe]]></dc:creator>
            <pubDate>Mon, 28 Jan 2019 20:18:37 GMT</pubDate>
            <atom:updated>2019-01-28T20:19:19.888Z</atom:updated>
            <content:encoded><![CDATA[<h4>The one question that can cut through all the complex reasoning and rightfully stop unneeded projects in their tracks.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZGvJiJU8fuGD8EMBzwVYsA.jpeg" /></figure><p>I imagine that if you made <a href="https://www.amazon.com/Story-String-Woody-Talking-Figure/dp/B000EDQGLK?tag=leavethegreat-20">one of those pull-string dolls</a> of a Product Manager, it would just say “Why?” over and over. We love figuring out the real reason behind an idea or a customer problem — as we should. But I think we often miss an important follow-up question: “Why <em>now</em>?”</p><p>We have so many methodologies for prioritizing problems and features, but I’ve found that this one question is able to cut through all the complex reasoning and (rightfully) stop unneeded projects in their tracks. Most things we could work on in a product are important. But going through the thought process of why it’s important to work on something <em>right away</em> is really helpful to separate the truly worthy projects from the ones that can wait.</p><p>The problem is that “Why <em>now</em>?” is not always an easy question to answer. It’s too vague, too broad. But if you flip it around and ask it a different way, things start to become clear very quickly. So here’s a question I recommend you ask yourself and the team the next time you debate a project:</p><blockquote>What is the danger of not doing this project right now?</blockquote><p>If we <em>don’t</em> solve this problem or add this feature right now, what do we lose? Are sign-ups going to drop? Are we going to lose customers? Are we going to miss a major shift in the market? If so, then, yes, <em>now</em> is a good time to work on it. But if the room suddenly falls silent and everyone comes up short on the downside of skipping over the idea — or if the downside is something like “this one customer will stop sending us angry emails” — that’s a pretty good indication that this thing can wait for later.</p><p>I say “wait for later”, and not “forget about for forever and ever”, because it’s quite possible that a few months from now you’ll answer that question differently, and suddenly <em>now</em> becomes the perfect time to work on it. The point is that we should never do something <em>now</em> if <em>later</em> is a better option.</p><p><em>Originally published at </em><a href="https://elezea.com/2019/01/the-power-of-why-now-as-a-prioritization-technique/"><em>elezea.com</em></a><em> on January 28, 2019.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cb9b24cb38f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/elezea/the-power-of-why-now-as-a-prioritization-technique-4cb9b24cb38f">The power of “why now?” as a prioritization technique</a> was originally published in <a href="https://medium.com/elezea">Elezea</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vinyl Me, Please and the power of product thinking]]></title>
            <link>https://medium.com/elezea/vinyl-me-please-and-the-power-of-product-thinking-ae053809d11c?source=rss----eb8f6a9691fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/ae053809d11c</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[vinyl]]></category>
            <dc:creator><![CDATA[Rian van der Merwe]]></dc:creator>
            <pubDate>Fri, 24 Aug 2018 14:20:56 GMT</pubDate>
            <atom:updated>2018-08-24T14:20:41.388Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been a <a href="https://www.vinylmeplease.com/"><em>Vinyl, Me Please</em></a> customer since January 2015. Back then things were pretty basic. For roughly $25/month they would send you a “Record of the Month”, along with a custom art print and cocktail recipe. It was cool, and helped to expand my musical palate quite a bit.</p><p>But sometime over the over the past year or so they kicked things into high gear. VMP now offers a “Classics” track (my favorite!) and a “Hip Hop” track in addition to their “Essentials” track (the original “Record of the Month”). But what’s even more apparent now is how <em>Vinyl Me, Please</em> has grown into a role model of how to provide value to music lovers in the digital era. The thought and care that went into <a href="https://www.vinylmeplease.com/magazine/mitski-liner-notes/">this month’s “Essentials” release</a> proves it once again.</p><p>I noticed yet another example yesterday. The <em>Vinyl Me, Please</em> store now shows the “nutrition content” of each record they sell:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8ju1REYCO0adGmrw.jpg" /></figure><p>Ask any vinyl collector and they will tell you how much this small detail improves the shopping experience. This is all the information we usually have to hunt for on product pages and do multiple Google searches about — but presented in a consistent, easy-to-read format. It’s such a relief and a breath of fresh air.</p><p>I’ve seen quite a few attempts to define “product thinking” lately. This example, to me, sums it up perfectly. So here’s my rough, working definition:</p><blockquote>“Product thinking” means gaining a deep understanding of what users need and what kind of friction they experience, and then providing a product solution that makes that friction go away in a delightful way.</blockquote><p><em>Originally published at </em><a href="https://elezea.com/2018/08/vinyl-me-please-and-the-power-of-product-thinking/"><em>elezea.com</em></a><em> on August 23, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae053809d11c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/elezea/vinyl-me-please-and-the-power-of-product-thinking-ae053809d11c">Vinyl Me, Please and the power of product thinking</a> was originally published in <a href="https://medium.com/elezea">Elezea</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>