<?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 Yoav Yechiam | The Product Alliance on Medium]]></title>
        <description><![CDATA[Stories by Yoav Yechiam | The Product Alliance on Medium]]></description>
        <link>https://medium.com/@yoavyechiam?source=rss-66350b557286------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MXtPB1t1A3exXntvWwOc-w.jpeg</url>
            <title>Stories by Yoav Yechiam | The Product Alliance on Medium</title>
            <link>https://medium.com/@yoavyechiam?source=rss-66350b557286------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:53:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yoavyechiam/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[How hard can defining an Analytics event be? Really?]]></title>
            <link>https://medium.com/agileinsider/how-hard-can-defining-an-analytics-event-be-really-1c1d9a4b8fab?source=rss-66350b557286------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c1d9a4b8fab</guid>
            <category><![CDATA[data-driven]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[spotify]]></category>
            <category><![CDATA[strategy-analytics]]></category>
            <category><![CDATA[analytics-platforms]]></category>
            <dc:creator><![CDATA[Yoav Yechiam | The Product Alliance]]></dc:creator>
            <pubDate>Sun, 28 Aug 2022 13:52:15 GMT</pubDate>
            <atom:updated>2022-08-28T13:52:15.210Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/749/0*kUVjMIjiiOksCpX1.jpeg" /><figcaption>Shoutout to <a href="https://unsplash.com/@mbaumi">Mika Baumeister</a> for the image</figcaption></figure><p>All of my Analytics courses and lectures begin with me explaining why having many (over 100) Analytics events is bad — very bad. There are many reasons. Thus, I spend a full lecture explaining them. But this time I wanted to actually show, on a real product, how hard defining an event really can be. Or rather how easy it is to not define an event well at all.</p><h3>Volunteers? Yes, you in the back? Couldn’t catch your name — Spotify, is it?</h3><p>So, let’s take the most basic event we’d want to track if we’re a PM at Spotify — Play a song:<br>Let’s define the event:<br><em>Name:</em> “Song played”.<br><em>Trigger</em>: user clicks on the play (triangle) button.</p><p>Yay! Now we’ll know exactly how many songs were played.<br>Mission accomplished — Yessss! Moving on to define the next 500 events.</p><p>But wait a minute…</p><h3>Maybe we should add a few properties to better enrich the data set</h3><p>Properties:<br><em>Song name</em> — that’s easy.<br><em>Band, album, genre, release year, song duration, explicit content, top chart ranking</em> and much more…</p><p>Now that’s rich! Moving on to define the next 500 events (although now I realize this might take me a few days…).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nWDXlVPDjQ4ZXTm5.jpeg" /></figure><h3>Well… I actually might need some context to go with that…</h3><p>Many times the event is meaningless without proper context. There’s a reason why it’s called ‘Behavioral Analytics’ — we want to analyze behavior, not just show a pretty graph.</p><p>Maybe it’s important to understand <em>if this is the 1st/10th/50th song played today</em> — as they might represent very different behaviors?</p><p>Maybe it’s also important to understand if this specific song was played by my specific choosing, as part of a playlist I built, a playlist I found or if it was chosen for me by Spotify’s engine. Just because I might be interested in understanding how many Spotify suggestions are played.</p><p>And what about the context of whether this song was played by a free or premium user? I can’t accurately tell if the user played a few songs for free and then turned premium. I only know the current user status…</p><h3>But, hold on a sec — What if the user hated the song and skipped it after 5 seconds?</h3><p>That’s a totally different experience. That can’t account as a good ‘song played’. Practically, to truly understand how each song was experienced by the user I must wait (at least) until the end of the song.</p><p><em>How long did the song play, out of its full duration? Was it skipped? Was it favorited? Was it shared? Did the user interact with it (FF/RW, viewed lyrics, watched video, lowered volume)?</em></p><p>This different perspective on context could allow me to understand much more about the user’s experience, behavior and intent.</p><h3>Come to think of it, most songs are played without even pressing ‘play’…</h3><p>So it looks as though we’ve defined the wrong trigger or even the wrong event (‘Song played’ needs to fire only when the song has STOPPED playing). Or maybe we need 2 different events…</p><p>Now let’s consider doing that for all 500 events :-(</p><blockquote><em>“The essence of strategy is choosing what NOT to do” — Michael Porter</em></blockquote><p>Having this article as a good answer for the above quote, let’s move on to — what should we do?</p><p>Unfortunately, that’s always more complicated (remember I mentioned the full lecture on the subject…). But if I was to leave you with just one point of advice, it would be to focus on the question “what is truly important for us to understand about our users’ behavior?”, which must far precede “what do we need to measure?”</p><p>We will continue exploring this subject, even trying to give a generic answer to the “what to do?” question, with the disclaimer that it’s not going to be easy to put in writing. But that will have to be in my next article..</p><p>Now excuse me while I assist solving that exact dilemma for a dear client :-)</p><p><a href="https://www.linkedin.com/in/yoavyechiam/">Yoav Yechiam</a> is a partner at the <a href="http://www.product-alliance.com/">Product Alliance</a>, a boutique consulting firm specializing in Strategy, Product and Analytics. He is a globally recognized Analytics and Optimization expert, with over 13 years’ experience working with all Analytics tools imaginable. Yoav will be leading the next <a href="https://www.product-alliance.com/mixpanelcourse">Mixpanel Analytics Mastery Course</a> that begins in September. <a href="https://www.product-alliance.com/mixpanelcourse">Click here for more details</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c1d9a4b8fab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/how-hard-can-defining-an-analytics-event-be-really-1c1d9a4b8fab">How hard can defining an Analytics event be? Really?</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Optimizer — ep.1 — series intro]]></title>
            <link>https://medium.com/the-optimizer-series/the-optimizer-ep-1-series-intro-94817e09432b?source=rss-66350b557286------2</link>
            <guid isPermaLink="false">https://medium.com/p/94817e09432b</guid>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[optimization]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Yoav Yechiam | The Product Alliance]]></dc:creator>
            <pubDate>Mon, 24 Feb 2020 15:16:06 GMT</pubDate>
            <atom:updated>2020-02-24T15:16:06.896Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Optimizer — ep.1 — series intro</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3f6MK0R7J345ELs6Qcx8EQ.png" /><figcaption>Photo by <a href="https://unsplash.com/@scienceinhd?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Science in HD</a> on <a href="https://unsplash.com/s/photos/testing?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Here’s what The Optimizer series is intended to be: a series of short case studies showcasing real optimization dilemmas and solutions from real life cases. Having done quite a few of these in the past 15 years, and being asked to talk about them on various platforms, I chose to share my experience here. I’m hoping that PMs and entrepreneurs will find something to relate to and implement on their own ‘turf’.</p><p>For obvious reasons I won’t be sharing the clients names and the data might be altered a bit to not reveal sensitive information. But everything is real. Nothing made up.</p><blockquote><strong>When it comes to optimization, mistakes are pretty consistent. Actually, the solutions are as well.</strong></blockquote><p>Having gone through quite a few optimization processes with various organizations from various fields, I find that many dilemmas repeat themselves very similarly across markets. Some solutions (actually most of them) are relevant in many different domains. Thus, there’s a good chance the optimization I did with my clients might be a great case to learn from for you.</p><h4>As always — strategy first</h4><p>A few words about strategy and my philosophy on optimization and testing. I believe that each product can only be one of two stages of life’: discovery or optimization</p><ul><li><strong>Discovery </strong>— Product Discovery, is all about finding product market fit. I’ll be very blunt — If you’re still in this process there’s no point in optimizing the product features and elements. You are wasting your time and efforts. At this stage you must think in multipliers (changes that would make your product X time better — YY% improvements simply aren’t enough). Optimizing onboarding/registration even by an amazing 50%, pre-PMF, is still not the impact you need.<br><em>There’s no point in *optimizing pre-PMF!</em></li><li><strong>Optimization</strong> — Once you’ve past PMF and you’re absolutely positive there’s a market demand for whatever value you’re providing, it’s time to be more efficient by maximizing the user’s value and the product’s key metric. Whether it’s engagement, retention or monetization, double digit percentage changes can be worth a lot in revenus and/or valuations.</li></ul><p><em>* You can and should optimize testing, to validate or discard your assumptions much quicker and more efficiently (which is very important on its own). But that differs from optimizing A product.</em></p><p>I believe that although optimization is built around tactical ‘plays’, the guiding strategy is crucial. When it comes to optimization, experience (and many failures) have shown me that intuition is too often more misleading than helpful.</p><blockquote><strong>We think we know what our user thinks/wants, but in reality we don’t — at least </strong>not enough</blockquote><p>The moment we accept that and don’t try to force or prove our intuition, we find that a strategic ‘cold’ approach to testing works better 9 times of 10. This means that many times (not all) we don’t need to make assumptions, but rather choose the range of our test scenarios.</p><p>For example: I can assume that a low price subscription would work best for my product, but that should not hold me back from testing a $50 annual plan as part of a range of 10 different pricing models.</p><p>Strategy also plays a crucial role in choosing what to test next, and more importantly, what not. We need to view our product, at its optimization phase, as a testing lab. When we do so, our testing strategy and priorities should rely not on the expected results, but rather on the expected impact the actions we will take, based on those test results.</p><p>Instead of a roadmap I suggest writing a test-plan, which basically lays down the tests we want to make prioritized by their impact value. The test-plan (like a roadmap BTW) should not be strict and allow adjustments and changes. If a certain test raises a new question that might have more potential impact than the next test in line, then it should take precedent.</p><p>Bottom line, optimizations work. It will consistently improve engagement, retention and most impactfully monetization, by tens of percentage points. It works not because we’re smart, but rather because we acknowledge the fact that we’re lousy at predicting human user behaviour. But through methodological and strategic testing we will constantly keep on improving.</p><blockquote>It’s almost impossible not optimize if we follow the right strategy</blockquote><p>So what am I going to write about in the upcoming episodes? Monetization (especially pricing models), retention, driving rating, and whatever else comes up. If you’d like me to share my experience on something more specific, ask for it.</p><h4><strong>About me:</strong></h4><p>My name is Yoav Yechiam. I come from an entrepreneurial background, with a few startups in my belt, some more successful, so less, one sold. Throughout the years I’ve found myself focusing on Product Management. Not because that’s something I aspired to be, but mainly because it seemed to be the most important role I felt I needed to take wherever I’ve been.</p><p>3 years ago I ventured out to become a consultant. Focusing mainly on product strategy and analytics. This led me to take on many projects that were aimed at improving a certain ‘stubborn’ metric. The strategies and tactics I’ve used, along with the lessons learned from these experiences are what we’ll discuss in this series.</p><p>Six months ago, I joined forces with a few other (very) experienced Product consultants to form <a href="http://product-alliance.com/"><strong><em>the</em></strong><em> </em><strong><em>Product Alliance</em></strong></a>. A boutique consulting firm that is unique by having a multi perspective approach to the client’s solution. This is due to every project having more than one Product consultant analysing it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94817e09432b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-optimizer-series/the-optimizer-ep-1-series-intro-94817e09432b">The Optimizer — ep.1 — series intro</a> was originally published in <a href="https://medium.com/the-optimizer-series">The Optimizer series</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why ‘Never give up’ Does Not Work as a Startup Strategy]]></title>
            <link>https://medium.com/agileinsider/why-never-give-up-is-an-awful-startup-strategy-c8934a40b897?source=rss-66350b557286------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8934a40b897</guid>
            <category><![CDATA[ceo]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Yoav Yechiam | The Product Alliance]]></dc:creator>
            <pubDate>Wed, 18 Sep 2019 13:04:51 GMT</pubDate>
            <atom:updated>2019-10-03T19:25:16.198Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why ‘Never Give Up’ Does Not Work as a Startup Strategy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kBpbvlQ3Ag7qFkcotV1Q2g.jpeg" /></figure><p>Actually, it’s exactly the other way around. A startup, any startup, has many opportunities and paths it can take. Business opportunities, technology opportunities, marketing, and of course product. So obviously, a startup must constantly give up on opportunities and possible paths.</p><p>Most times, most startups end up eventually pivoting their company in a different direction. So why do we expect every entrepreneur to look us in the eyes with the most determined face and say that they’ll never give up?</p><p>We expect them to be smarter than that. To have a firm grasp on their company, market, technology and situation. We expect them to have an eagle eye view on their path and direction. And when the path is blocked too quickly, realize it, and then change course to a better suited path. That is a good thing. But if that’s not ‘giving up’ then what is?</p><p>As optimistic and motivated as entrepreneurs are, fortunately for us, in most cases we do eventually realize that giving up on a path isn’t defeat. Rather, it’s a late chance get out of a dead-spin. Yet, for the exact same reasons above, in most cases they’ll do it too late.</p><h3>What is your startup’s strategy?</h3><p>Funny, but we don’t hear entrepreneurs being asked that too often. When they do, too often they mistake strategy for their list of goals and objectives. “To grow 200% based on our superior product” is NOT a strategy. “To always provide the best possible service” is also NOT a strategy. Those are nothing but vague words, that might be hard to disagree with, and on some level, might be motivating. Yet, that’s not a path.</p><blockquote><em>“A good strategy does more than urge us forward toward a goal or vision. A good strategy honestly acknowledges the challenges being faced and provides an approach to overcoming them.”</em></blockquote><p><em>― Richard P. Rumelt, Good Strategy/Bad Strategy</em></p><p>For a startup, a strategy is as important in deciding not to do something as it is in deciding what to do. Too many opportunities being approached all at once often marks the coming downfall …</p><h3>Great, you got funded! Now there’s only an 81% chance you’ll fail.</h3><p>Those are the chances of a seed funded startup to not being able to raise an additional funding within three years. Yet, both founders and investors tend to celebrate the investment milestone as a great sign of achievement. Founders get their initial external validation for their idea. Investors celebrate choosing the best opportunity they had based on team, market and concept or tech.</p><p>From here, all that stands in the way of success is execution. That’s exactly where strategy needs to be your plan and map. Yet in practice that often translates to “let’s get as much sh*t done as possible in the quickest amount of time.” Focusing on speed and not velocity, output as opposed to outcomes. And that is terribly wrong! Without a clear strategy your up-hill chase is a big waste of energy.</p><h3>Strategy is not the solution, it’s the path to maximizing our chances</h3><p>Strategy is exactly the opposite of playing fair. It is by definition the shortcuts and trickery used to give ourselves an advantage and improve our position. It dictates where and how we can leverage our advantages to bypass the most challenging barriers. With the purpose of placing our products in a much better position to succeed (PMF anyone?). But for that to happen effectively, we must identify not only our strengths and weaknesses, but more importantly, which of them and where they should be leveraged to gain that needed edge.</p><p>Strategy is our ‘witty’ plan to most effectively utilize our weapons. “Go out there and give it your all” is just a bad strategy, as there is no leverage or synergy involved.</p><h3>It’s time to update S.W.O.T.</h3><p>S.W.O.T. (Strengths, Weaknesses, Opportunities, Threats) analysis, as some of us have been taught in business school, is not relevant for the majority of startups. Reason being, it was mainly used to assess a ‘competitive strategy’. Today, we’ve come to realize that rarely are startups beat by competition. We’re now well aware that the main goal for most startups is reaching Product-Market-Fit before time or money runs out. Thus, a correct strategic plan, when it comes to product-oriented startups, should prioritize W.LS.LO:</p><p><strong>W</strong> - Identify our weaknesses facing the obstacles ahead.</p><p><strong>LS</strong> - Leverageable Strengths, focus on utilizing strengths we can significantly leverage.</p><p><strong>LS</strong> - Leverageable Opportunities, only opportunities that can truly be leveraged.</p><blockquote><em>“A talented leader identifies the one or two critical issues in the situation — the pivot points that can multiply the effectiveness of effort — and then focuses and concentrates action and resources on them.”</em></blockquote><p><em>― Richard P. Rumelt</em></p><h3>The forbidden low hanging fruit</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2qjYv8vNtm1sGXXjSiprEQ.jpeg" /><figcaption>Image by <a href="https://pixabay.com/users/JillWellington-334088/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=553464">Jill Wellington</a> from <a href="https://pixabay.com/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=553464">Pixabay</a></figcaption></figure><p>Bad strategy or not having one at all can be equally damaging. A common example are ‘low hanging fruit.’ Startup CEOs are often times mesmerized by ‘low hanging fruit,’ short term gains that can be seen as achievements, acquired for minimal effort or cost. It’s very easy to see how this happens, and how hard it would be for a young CEO to pass on an opportunity that looks to be so easily obtained and is in front of their eyes. But that happens when we forget that our time or money is much more limited than it seems. Focus is the most critical name of the game. Not being focused on the right path and sidetracking to reap short-term gains might seem like a harmless sin. But too often we miss judge and forget where things can go wrong and how much maintenance will be required.</p><p>One of the most crucial parts of good strategy is choosing what not to do. That in turn means that deciding on a strategy will likely present losers. You need not try to avoid it. If your strategy pleases everyone, it’s probably a bad one. Strategy must state what needs to be sacrificed, and that would often mean frustration by some of your people who will feel their work is no longer the organizational focus of attention.</p><h3>Product strategy is beyond just a plan</h3><p>It is an ongoing process of evaluation and assessment of processes and situations. Our strategy needs to be intertwined in our organizational culture. Constant debriefing to learn from our mistakes, changing perspectives to catch the ‘obvious’ that everyone sees but us, and the courage to step outside of our comfort zone and test our riskiest assumptions first (although it might result in a ‘premature disaster of a result’), all need to be part of our strategy. This is one of the most effective ways to leverage or strengths.</p><h3>How should we take it from here?</h3><p>We have a blindspot for our own bad actions and wrong way paths. It’s simply too hard for us humans to identify them in time. That’s why it takes us so long to admit we’re lost. Our optimism and eagerness, especially as entrepreneurs, is to not give up, which often hurts us. Yet when it comes to observing others, we are much quicker at spotting mistakes.</p><p>So based on that, here’s my assignment for you: choose a startup you’re familiar with. Now analyze through your eyes their product strategy. Can you describe it? Is it focused? Is it exclusive (of low hanging fruits) and is it being over-seeded by an external observer? Now with each conclusion you draw, consider if you, on your startup, are not making these exact same mistakes.</p><p><strong><em>About the author:</em></strong></p><p><a href="http://yoav-yechiam.mystrikingly.com/"><em>Yoav Yechiam</em></a><em> is a serial entrepreneur. Four time CEO, coach, lecturer, writer and mentor. He’s the Chief Product Strategy Consultant at</em><a href="http://www.y-perspective.com/"><em> Y-Perspective</em></a><em> and is a partner at the </em><strong><em>Product Alliance</em></strong><em>. Yoav also holds a specialty in Analytics strategy and runs courses, workshops and webinars on Analytics. Loves to write about his two professional passions: Startups and Product, with </em><a href="http://yoav-yechiam.mystrikingly.com/#publications"><em>articles published</em></a><em> on VentureBeat, Mind the Product, Product Coalition and more.</em></p><p><em>Yoav is also the founder and head instructor of the</em><a href="http://www.startupceocourse.com/"><em> Startup CEO Course</em></a><em> and the recently added </em><a href="http://www.productmba.org/"><em>productMBA</em></a><em> (Product Leadership course).</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8934a40b897" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/why-never-give-up-is-an-awful-startup-strategy-c8934a40b897">Why ‘Never give up’ Does Not Work as a Startup Strategy</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Product Leadership — really?]]></title>
            <link>https://medium.productcoalition.com/what-is-product-leadership-really-fa3e90db4ab6?source=rss-66350b557286------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa3e90db4ab6</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-leadership]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Yoav Yechiam | The Product Alliance]]></dc:creator>
            <pubDate>Sat, 20 Apr 2019 23:52:03 GMT</pubDate>
            <atom:updated>2019-04-20T23:52:03.264Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is Product Leadership — really?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LKHsvG0ssO4CSkgOejzmvQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/4lfrwRyHRYk?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">rob walsh</a> on <a href="https://unsplash.com/search/photos/leader?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>With so many Product Management articles out there, let’s talk ‘Product Leadership’ for a change.</p><p>As so often, it’s better to start with what it is not.</p><p>It’s <strong>NOT </strong>about UI, UX or even engagement or retention — What good are those if you haven’t truly defined what your overall goals are?</p><p>It’s <strong>NOT </strong>about running a perfectly synchronized Agile process — Yes, Agile is a way of being more effective. Yet, if you yourself cannot focus on what truly matters, your perfectly synced Agile team might be very busy, but probably not effective.</p><p>It’s <strong>NOT</strong> even about how not to fail — Failing is a learning process. Knowing where and when to quit is often the most important decision.</p><p>Most importantly — and perhaps most surprising — Product Leadership is <strong>NOT </strong>necessarily about having the best Product Manager skills.</p><p>Why is this? Because being a Product Manager is similar to being a conductor: you can’t make much sound without your band. Hence, if you cannot be a master influencer and do not know how to drive change within your organization, you will remain a cog in the wheel. A very important cog, no doubt, but one that can and will be replaced as it wears out…</p><p>You see, in order to be a great Product Leader you do not need to master Product Management — you need to master professional and self leadership. Having said that, it is important this be not confused with charisma or authority, which you either have or you don’t.</p><p>Leadership skills can be learned and a leadership mindset can be built. It begins by understanding that you have a choice. You can decide to be your own boss (regardless if you already have one), constantly guiding and pushing yourself. Leadership is identifying your own barriers — it means pushing yourself outside of these (self-defined) barriers. It means showing up when you least feel like it, simply because you know that is what you need to do. Becoming a leader means identifying the feeling of being outside your comfort zone and turning this into a trigger to keep moving forward and not turning away.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xuUJQgIpW84pJLZi" /></figure><p>We, as Product Managers, are too often too busy to look ourselves in the mirror. True, we may have the most stressful job in the organization. Deep inside, though, we know that being busy is the easy excuse. From here it’s on you. To advance to the next level, you need to become an impactful Product Leader.</p><p>The good news is that it can be taught.</p><p>The bad news (could be) that it requires making a decision with yourself.</p><p>If you can solve the dilemma, you might very well be the Product Leader type.</p><p><strong><em>Yoav Yechiam is a serial entrepreneur and Product specialist. He is the owner and chief strategy consultant at Y-Perspective, a Product Consulting, and Analytics firm.</em></strong></p><p><strong><em>Founder of the </em></strong><a href="http://www.productmba.org/?art"><strong><em>productMBA</em></strong></a><strong><em> and </em></strong><a href="http://www.startupceocourse.com/"><strong><em>Startup CEO Course</em></strong></a><strong><em>.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa3e90db4ab6" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/what-is-product-leadership-really-fa3e90db4ab6">What is Product Leadership — really?</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Product Leadership?]]></title>
            <link>https://medium.com/agileinsider/what-the-f-ck-is-product-leadership-137bcc2cbd01?source=rss-66350b557286------2</link>
            <guid isPermaLink="false">https://medium.com/p/137bcc2cbd01</guid>
            <category><![CDATA[yoav-yechiam]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[product-leadership]]></category>
            <dc:creator><![CDATA[Yoav Yechiam | The Product Alliance]]></dc:creator>
            <pubDate>Tue, 16 Apr 2019 16:06:59 GMT</pubDate>
            <atom:updated>2019-06-10T17:08:07.667Z</atom:updated>
            <content:encoded><![CDATA[<h3>What Exactly is Product Leadership?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*0EJgKoYybaBMW4eoEIRDoA.jpeg" /></figure><p>Let us start off with what Product Leadership is <strong>NOT</strong>.</p><p>It’s <strong>NOT </strong>about UI, UX or even engagement or retention — What good are those if you haven’t truly defined what your overall goals are?</p><p>It’s <strong>NOT </strong>about running a perfectly synchronized Agile process — Yes, Agile is a way of being more effective. Yet, if you yourself cannot focus on what truly matters, your perfectly synced Agile team might be very busy, but probably not effective.</p><p>It’s <strong>NOT</strong> even about how not to fail — Failing is a learning process. Knowing where and when to quit is often the most important decision.</p><p>Most importantly — and perhaps most surprising — Product Leadership is <strong>NOT </strong>necessarily about having the best product manager skills.</p><h4>Why is this?</h4><p>Being a product manager is similar to being a conductor: you can’t make much sound without your band. Hence, if you cannot be a master influencer and do not know how to drive change within your organization, you will remain a cog in the wheel. A very important cog, no doubt, but one that can and will be replaced as it wears out…</p><p>In order to be a great Product Leader you do not need to master product management— you need to master professional and self leadership. Having said that, it is important this be not confused with charisma or authority, which you either have or you don’t.</p><blockquote>“As a leader, the first person I need to lead is me. The first person that I should try to change is me.”</blockquote><blockquote>— John C. Maxwell</blockquote><p>Leadership skills can be learned and a leadership mindset can be built. It begins by understanding that you have a choice. You can decide to be your own boss (regardless if you already have one), constantly guiding and pushing yourself. Leadership is identifying your own barriers — it means pushing yourself outside of these (self-defined) barriers. It means showing up when you least feel like it, simply because you know that is what you need to do. Becoming a leader means identifying the feeling of being outside your comfort zone and turning this into a trigger to keep moving forward and not turning away.</p><p>We, as product managers, are too often too busy to look ourselves in the mirror. True, we may have the most stressful job in the organization. Deep inside, though, we know that being busy is the easy excuse. From here it’s on you. To advance to the next level, you need to become an impactful Product Leader.</p><p>The good news is that it can be taught.</p><p>The bad news (could be) that it requires making a decision with yourself.</p><p>If you can solve the dilemma, you might very well be the Product Leader type.</p><p><strong><em>Yoav Yechiam is a serial entrepreneur and Product specialist. He is the owner and chief strategy consultant at Y-Perspective, a Product Consulting, and Analytics firm. He is the Founder of the </em></strong><a href="http://www.productmba.org/?art"><strong><em>productMBA</em></strong></a><strong><em> and </em></strong><a href="http://www.startupceocourse.com/"><strong><em>Startup CEO Course</em></strong></a><strong><em>.</em></strong></p><figure><a href="https://productmanagementinsider.com/?utm_source=pmi&amp;utm_medium=article"><img alt="" src="https://cdn-images-1.medium.com/max/531/1*yPRWnRlzXXe8hWuwg2xETA.png" /></a></figure><figure><a href="https://alphahq.com/?utm_source=pmi&amp;utm_medium=article"><img alt="" src="https://cdn-images-1.medium.com/max/530/1*d6feM7YM9xI2c0CPC8XhSA.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=137bcc2cbd01" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/what-the-f-ck-is-product-leadership-137bcc2cbd01">What is Product Leadership?</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[K.I.S.S? — my ass!]]></title>
            <link>https://medium.productcoalition.com/k-i-s-s-my-ass-147c4dcf20b5?source=rss-66350b557286------2</link>
            <guid isPermaLink="false">https://medium.com/p/147c4dcf20b5</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[keep-it-simple-stupid]]></category>
            <category><![CDATA[product-strategy]]></category>
            <dc:creator><![CDATA[Yoav Yechiam | The Product Alliance]]></dc:creator>
            <pubDate>Sun, 17 Mar 2019 21:58:23 GMT</pubDate>
            <atom:updated>2019-03-17T21:58:23.300Z</atom:updated>
            <content:encoded><![CDATA[<h3>K.I.S.S? — my ass!</h3><p>We’ve been using Keep It Simple Stupid (KISS) as a guiding mantra for the products we are developing for a long time now. It might be time to challenge that notion. Oh, there’s nothing like striking down a consensus in its prime!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*D6ht5EmiZfkzbacQjWWW8A.jpeg" /></figure><h3>Time to bust the myth once and for all</h3><p>It actually makes a lot of sense to make a ‘simple’ product. One that ‘even your mother can understand’. No doubt that’s the logical thing to do. But does that really stick?</p><p>When we come to think of it, <a href="https://www.seguetech.com/waterfall-vs-agile-methodology/">‘waterfall’</a> planning can also be considered the logical thing to do,right? Who wouldn’t want to design a product all the way through. To make sure everything fits exactly in the right place. All processes and details are thoroughly thought through. And that nothing will be changed until the project is shipped…</p><p>That’s a silly comparison, many will say, and pull out the obvious examples: Google, Facebook, Instagram and even the the iPhone. Any snot-nosed kid who’s downloaded 5 apps onto his phone, will tell you that millennials and generation-Zs have an attentions span <a href="https://www.csoonline.com/article/2922807/microsoft-goldfish-have-higher-attention-spans-than-we-do-thanks-to-digital-lifestyles.html">shorter than a goldfish</a>. And that if loading an app takes more than 5 seconds no one will be there to see its first screen… Right?</p><p>Let me bust that myth once and for all. Or actually give credit to the BBC that have tracked down the source of the famous Microsoft study + goldfish, only to find out that it’s completely bogus (<a href="https://www.bbc.com/news/health-38896790">BBC article by Simon Maybin</a>). So goldfish don’t have short attention spans or memories. There is no evidence human attentions spans are shrinking.</p><blockquote>“Keep it simple, my A.S.S.” — Urz Trooli</blockquote><p>You see, as much as things might sound reasonable and logical, that’s not how our minds work. I‘d like to challenge the ‘keep it simple’ notion and show that in many cases complexity, a challenge and even a bit of frustration, actually cause us to better and more deeply connect to a product and the value it provides.</p><p>This form of connection will almost always out last the ‘simple’ connection and more importantly will cause the product to be ‘activated’ by more and stronger internal triggers and not as reliant on external ones (as disappointing as it might be to all our affection to push notifications).</p><p>Examples? Shouldn’t a MS study be enough? ;-)</p><p>Let’s explore the most popular apps out there to see if the theory sticks:</p><p>Remember Facebook? Not the monstrous product you are connected to on all of your devices. TheFacebook.com of 2004/5 that didn’t yet include the ‘like’ button or even the <strong>feed! </strong>That Facebook was NOT a simple nor easy product to understand — try to explain that to your mom… 8–12 seconds attention span? Try 15 minutes to register, answer the bio questions and upload your picture… That’s all it was back then, and yet 90% of every college campus they’ve launched were in within a few weeks.</p><p>But Facebook is ancient some will say. 2005 almost prehistoric… So let’s talk something a bit more recent targeting a younger population — Fortnite.</p><p>Fortnite is one of the more complex games out there. The short tutorial videos are 5 minutes long, not to mention downloading and installing it that would take you at least 20 minutes. So much for a quick and simple onboarding…</p><p>Even when you get past that and actually begin to play, the only quick thing that will happen is that you’ll get blown away. One can consider that an ‘achievement’ right? If you want to enjoy this game you have to study, practice, learn — those are not simple stupid tasks. They take time and a whole lot of frustration. Yet it works…</p><p>So maybe complexity is a good thing? Maybe it filters out all those user we’ve worked so hard to ‘covert’ through our onboarding funnel, just to lose for good 2 minutes later… Maybe complexity or overcoming and conquering it feels to us users as an achievement worth working for. And the investment / learning process that we’ve painfully gone through is what differentiates us from those who have yet to ‘join the elite club’. Psychologically, we might hate not being ‘in the know’ and being forced to learn. Yet we’re hooked on the sense of <a href="https://nickwignall.com/psychological-mastery-competitive-advantage/">achieving mastery</a> of a certain ability. It apparently makes us feel superior to those who have yet to achieve it.</p><h3>Fantasy sports as a ‘simple’ example</h3><p>Think of the most boring game you can imagine. Now add to that that it lasts over 6 months. 99% of the time nothing happens. It makes you follow scores of teams you care nothing about. You might not know your opponents, see their faces or speak a word to them the entire time. And worse of all, if you want to be really good at it you have to keep excel sheets and do math calculations of statistics and trades…</p><p>That’s how one might describe fantasy sports if they have never played it. And yet it’s a game being played for over 60 years now, by tens of millions of players around the world.</p><h3>Conclusions</h3><p>We, as product developers, shouldn’t automatically fear and reject complexity. Simplicity as a tactic does hold obvious benefit. Yet complexity can turn out to be even more valuable when utilized strategically. Taking our users through a more complex flow will most likely increase churn. Yet if done smartly, the ‘surviving’ users have a much higher chance of being retained and converted to our desired action.</p><h3>The questions left open</h3><p>It might be time to stop being afraid of complexity, long processes and even frustrating your users. Ask yourself where is your product’s value hidden. And how much of that value is obtained by the user’s ambition and will to achieve mastery.</p><p>Does that make your work as a product designer easier? Probably not.</p><p>Does that open new paths? Hopefully it does.</p><p>Where you take it from here? Well, that depends on how eager YOU are to achieve mastery. Have a thought about that…</p><p><strong><em>Keep it real — not simple, stupid ;-)</em></strong></p><p><strong>About the author:</strong></p><p>Yoav Yechiam is a serial entrepreneur. 4 time CEO, numerous product lead positions, lecturer, writer and mentor. He’s currently Chief Product Strategy Consultant at<a href="http://www.y-perspective.com/"> Y-Perspective</a> and holds Analytics courses and workshops.</p><p>Yoav is also the founder and head-master of the<a href="http://www.startupceocourse.com/"> Startup CEO Course</a> and the <a href="http://productmba.strikingly.com/">Product Leadership Course</a> — productMBA</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=147c4dcf20b5" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/k-i-s-s-my-ass-147c4dcf20b5">K.I.S.S? — my ass!</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Truth needs to be told — startups fail because CEOs have lousy bosses]]></title>
            <link>https://medium.productcoalition.com/truth-needs-to-be-told-startups-fail-because-ceos-have-lousy-bosses-d2c113475422?source=rss-66350b557286------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2c113475422</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[fail]]></category>
            <category><![CDATA[ceo-skills]]></category>
            <category><![CDATA[ceo]]></category>
            <dc:creator><![CDATA[Yoav Yechiam | The Product Alliance]]></dc:creator>
            <pubDate>Tue, 27 Nov 2018 22:04:53 GMT</pubDate>
            <atom:updated>2018-11-27T22:56:06.157Z</atom:updated>
            <content:encoded><![CDATA[<h3>Truth needs to be told — startups fail because CEOs have lousy bosses</h3><p>Why do startup fail? Google it — you’ll find hundreds of articles, most pointing to the same reasons:</p><ul><li>No market need</li><li>Ran out of cash</li><li>Team problems</li><li>Pricing/product/business models issues</li><li>Competition</li></ul><p>One small problem I have with these reasons. They are all reasons the <strong>founders</strong> mentioned when asked to tell why their startups failed. <br>What might be missing? :thinking_face:<br>Let’s say a company’s marketing sucks. Ask the exed VP Marketing and he’ll most likely give you a list of valid reasons. Ask the CEO and he’ll probably give you one — the VP Marketing… See my point?</p><h3>Been there, failed that…</h3><p>I’m of course not saying that all startup CEOs are lousy, but the fact of the matter is if their startup failed they’ve probably earned a significant share of the blame. Now I’m not saying this as a ‘condescending’ VC executive. I’m saying this as a 3 time CEO of startups that shut down (I’ll save my success stories for a different post).</p><p>It’s very hard to blame entrepreneurs for not succeeding. These guys are making such a huge sacrifice, taking such big risks and many times just put their lives on hold for their ‘baby’. Yet, statistically speaking, they/we are stupid, crazy or completely irrational. Whichever one you choose, most founders will probably not be offended. They know what they are up against, and yet they believe! Believe in their innovative concept, believe in their technology, believe in their market fit and they believe in their ability to raise money. Ask them and they’ll also (not surprisingly) tell you they believe in themselves, maybe even most of all. In their ability to lead, to manage, to make tough decisions, to prioritise, to set goals, to motivate their team, to build a business plan, to get into the users’ head… Hold on!</p><p>I can honestly believe entrepreneurs when they say they are the best at coming up with their specific idea and they might even be the best at fitting a technology to that challenge. But what are the chances that the founder is the best (or even just good) at all the other traits mentioned above? I’m pretty confident that if asked directly, most founders will admit they’ve still got a lot to improve on.</p><h3>But here’s the catch: Being an entrepreneur and being a great Startup CEO don’t often come together. At least not naturally…</h3><p>There’s a terrible misconception that the most important trait for a startup CEO to possess is an extremely high level of motivation. As if that is the problem and solution to most startup problems. Adeo Ressi, of ‘Founders Institute’ will tell anyone listening that <em>“</em><a href="https://fi.co/insight/the-1-reason-why-startups-fail-according-to-adeo-ressi"><em>At the end of the day there is only one thing that kills a company, that is when the founder gives up</em></a><em>”. </em>To me this is like saying the cause of people dying in hospitals are doctors announcing time of death… From my experience, following quite a few startups that eventually crashed and burned, most CEOs give up way too long after their company has effectively died. The same also goes to pivoting. It’s a very hard decision, but one that needs to be made on time. Prolonging it is not healthy.</p><p>Please don’t misunderstand what I say. It’s not that motivation isn’t important. It is, very much. But when talking startups, one may acknowledge it as a given. The vast majority of entrepreneurs are highly motivated individuals, that’s not what’s going to make you stand out of the crowd. The problem is not Ressi’s quote, the problem is entrepreneurs believing and following it blindly. In 99% of the cases extraordinary motivation will push you forward a few more inches against your barrier, but believing is not enough to get you through in the long run. You must look yourself in the mirror and acknowledge that.</p><blockquote>Motivation is like conceiving in a boxing match. The better you get at it the long you’ll last. But if that’s all you focused on you’ll never win the match. The problem is that once you begin conceiving it’s very hard to focus on anything else.</blockquote><h3>‘Ran out of money’ is not a cause, it’s a symptom</h3><p>Most startups die when they’ve run out of money. It’s not a cause it’s a fact. Naturally, we think they reach that point because things went wrong. I argue otherwise. From my experience most CEOs were simply not prepared. Their day to day might run perfectly and production outputs very high. Yet their paths, strategy, roadmap prioritization were not well decided, if set at all. Startup die because companies don’t maximize their opportunity to succeed. And obviously, if they don’t succeed enough before money runs out the story ends there. Being a good CEO means not only running the show, but also running the future — managing yourself. Now that’s much easier said than done for one person with hundreds of decisions constantly on his mind.</p><h3>Who’s your boss?</h3><p>Technically, it’s your board of directors (whenever and if ever they meet). So who is better managed, your CTO (managed by you) or yourself (being managed by the board)?</p><p>I’m guessing you’re the better boss. Partially because the board’s job isn’t actually to manage, but to guide and supervise. And <strong>mainly because you are there and they aren’t </strong>(on a regular basis). So who’s the boss?</p><blockquote>“You looking at me?” — Al Pacino, Taxi Driver</blockquote><p>Startups fails because of many possible reasons: no market need, run out of cash, team problems, pricing and more. But most of these are actually the cause the CEO not being managed properly. Face it, you are the CEO’s boss. <a href="https://seths.blog/2010/12/the-worlds-worst-boss/">Seth Godin wrote in his blog</a>:</p><blockquote>If you had a manager that talked to you the way you talked to you, you’d quit. If you had a boss that wasted as much of your time as you do, they’d fire her. If an organization developed its employees as poorly as you are developing <strong>yourself</strong>, it would soon go under.</blockquote><h3>How does one become a better boss to his CEO self?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y6cbT_QTUtYKovtYSv-lxg.jpeg" /><figcaption>Develop a split personality</figcaption></figure><p>My advice — develop a split personality. Force yourself to stop and view the CEO’s work at predetermined periods. Evaluate their (your) goals setting, priorities, decision making processes, time management, dealing with responsibility, influence, leadership and other critical skills. Don’t let your CEO of the hook. Make them accountable. Make it clear that motivation alone is not enough. Don’t sympathize! Work to find solutions.</p><p>Remember<strong>, A great CEO is THE most critical asset a startup has.</strong> You can have the best idea, best tech and best team. But without a great CEO to connect the dots and leverage them, the company will always be coming up short…</p><p><em>About the writer:<br>Yoav Yechiam is 4 time entrepreneur currently working on his 5th. He’s a startup strategy consultant and the founder of Y-Perspective Consulting. Apart for his love for startups he specializes in Product strategy and Analytics. Recent altMBA graduate (shout out to the alumni) and most importantly father to 3 boys and husband to (the beautiful) Hadas</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2c113475422" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/truth-needs-to-be-told-startups-fail-because-ceos-have-lousy-bosses-d2c113475422">Truth needs to be told — startups fail because CEOs have lousy bosses</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[KISS? My Ass!]]></title>
            <link>https://medium.com/@yoavyechiam/kiss-my-ass-385118508de0?source=rss-66350b557286------2</link>
            <guid isPermaLink="false">https://medium.com/p/385118508de0</guid>
            <category><![CDATA[hebrew]]></category>
            <category><![CDATA[keep-it-simple-stupid]]></category>
            <category><![CDATA[עברית]]></category>
            <dc:creator><![CDATA[Yoav Yechiam | The Product Alliance]]></dc:creator>
            <pubDate>Thu, 06 Sep 2018 11:48:01 GMT</pubDate>
            <atom:updated>2018-09-06T12:24:17.926Z</atom:updated>
            <content:encoded><![CDATA[<p>מי שחי את עולמות האונליין כיזם, איש מוצר, מעצב ואפילו מפתח, וודאי נתקל במנטרה — מוצר חייב להיות פשוט. באנגלית אוהבים להשתמש בקיצור KISS = Keep It Simple Stupid ניתן די בבטחון להגיד שבנושא הזה קיים קונצנזוס.</p><p>אז באתי לפרק אותו או לפחות הרגיז רבים תוך כדי ניסיון D-;</p><p>לוגית, זה הרי נשמע מצוין. תיבנו מוצר שברור לכולם מה הוא עושה ואיך משתמשים בו. “מוצר שתוכלו להסביר לאמא שלכם” אוהבים לומר. אבל לוגית גם פיתוח waterfall נכון יותר מ agile (מקיף, שלם, מדויק, יורד לפרטים הקטנים = מושלם. לא?).</p><p>“שטויות, כל המוצר המובילים הם פשוטים להבנה ושימוש” יגידו רבים. ויפציצו בדוגמאות כמו: גוגל, פייסבוק, יוטיוב, אינסטגרם ואפילו האייפון. כל זב חוטם שהוריד 3 אפליקציות בחייו יסביר בבטחון ש”לדור ה Millennials יש יכולת ריכוז של 8 שניות, ואם הם לא הבינו את הקונספט עד אז הם יסירו את האפליקציה”. “לוקח לאפליקציה שלכם יותר מ-5 שניות לעלות? חבל לכם על הזמן, לא יהיה שם אף אחד עד שהיא תסתיים…”</p><p>נשמע הגיוני בתאוריה, אבל תפיסה במציאות או במחקרים אמיתיים אין.</p><p>אז Keep it simple — my ass. באתי לאתגר ולהראות שבהרבה יותר מקרים ממה שחשבתם דווקא מורכבות, הצורך ללמוד איך להשתמש באפליקציה, ההשקעה הנדרשת מהמשתמש ותהליך הגילוי, הם אלו שייצרו את החיבור העמוק ואת הבנת הצורך בין המשתמש למוצר. וחיבור כזה תמיד יחזיק יותר זמן וידרוש הרבה פחות טריגרים חיצוניים (מישהו הזכיר כמה הוא אוהב שמציקים לו עם הודעות פוש, נכון?).</p><p>דוגמאות? בבקשה…</p><p>בוא נבחן האם האפליקציות המובילות באמת פשוטות או שפשוט התרגלנו אליהן? אולי הערך שאנחנו מקבלים מהן או שהעובדה שכולם כבר שם, הן שגרמו לנו לאמץ אותן? בואו נבחן כמה מהן:</p><p>פיסבוק — זוכרים? לא את המוצר שאנחנו מכירים היום עם אפליקציה, לייק ופיד (מישהו יכול לדמיין את <strong>ה</strong>פייסבוק בלי פיד?). <strong>ה</strong>פייסבוק שפרצה לעולם לא הכילה את כל הפיצ’רים. אפשר להגיד הכל היה פשוט, אבל לא פשוט להגיד שהיה קל להבין מה הם עושים (נראה אתכם מסבירים לאמא מה זה פייסבוק בשנת 2004/5). 8 שניות להבין מה קורה? יותר בכיוון של רבע שעה להירשם, להזין פרטים, לענות על שאלות אודותך (זה היה עיקר הפרופיל אז) ולעלות תמונה. למי יש כוח לזה? זה בחיים לא יעבוד, נכון?</p><p>פורטנייט — אם פייסבוק בתחילת הדרך זה עתיק מידי (ועל פוקימון גו כבר טחנתי לא מעט), אז מה תגידו על פורטנייט? (רק אל תגידו שאתם לא מכירים…) — פורטנייט הוא אחד המשחקים המורכבים והמסובכים שקיימים היום. סרטוני ההדרכה הקצרים שלו הם 5 דקות לכל הפחות. ושלא נדבר על הורדה והתקנה שתיקח לכם עשרים דקות לפחות. Simple? אם הכוונה היא למות תוך חצי דקה אז זה באמת פשוט. אבל כדי להצליח לשחק ולשרוד (לא מדבר בכלל על האפשרות לנצח) צריך ללמוד והרבה!</p><p>אז אולי בעצם מורכבות זה משהו חיובי? אולי זה מנפה את אותם משתשמים שעבדנו קשה מאוד להעביר אותם onboarding רק בשביל לאבד אותם דקה אחרי. אולי מורכבות או ההתגברות עליה מרגיש לנו כמשתמשים כהישג בפני עצמו והשקעה שעשינו ללמוד ולהבין כצעד שמבדיל ביננו לאלו שעדיין לא מבינים…</p><p>פסיכולוגית, אנחנו אמנם לא אוהבים לא להבין ואת זה שמכריחים אותנו ללמוד. אולם מצד שני אנחנו מכורים לסיפוק של השגת ‘שליטה’ (mastery) ביכולת מסויימת. זה ככל הנראה גורם לנו להרגיש סוג של התנשאות מעל אלו שעדיין לא עשו זאת.</p><p>דוגמה מצויינת היא משחק (אם אפשר לקרוא לו כזה) שנקרא פנטזי ליג (Fantasy sport). אוהדי הספורט הצעירים יחסית, וודאי יכירו אותו. האמריקאים (הלא צעירים בכלל) משחקים אותו כבר 60 שנה. מדובר על משחק… לא, אין סיכוי שאצליח להסביר אותו כאן… אבל הוא קשור לספורט, סטטיסטיקות וסוג של מסחר. בשביל להיות טוב ולנצח, שחקן חייב לעשות המון מחקר וחישובי אקסלים למיניהם. למי שלא מכיר, זה וודאי נשמע כמו משחק ש<strong>ממש, אבל ממש לא מעניין לשחק</strong>, אבל עצם התחרות היא על כמה כל שחקן הצליח לפצח את הנוסחה המורכבת לנצחון. Simple נכון? מסתבר ש 60 מיליון אמריקאים משקיעים בממוצע יותר מ-3 שעות בשבוע לפיצוח המורכבות והם חולים על זה.</p><p>מסקנות: אל תפחדו ממורכבות ומזמן שנדרש להבנה. מה שחשוב זה הערך שאנחנו נותנים למשתמש והערך כפי שהוא נתפס על ידי אותו משתמש. זה לא הופך את העובדה שלנו כאנשי מוצר ליותר קלה, אבל זה בהחלט פותח אפשרויות ובשאיפה גם מגשר מעל חסמים מנטליים שלא איפשרו לנו להציע פתרון מורכב אך מספק יותר למשתמש.</p><p>Keep it real — not simple, stupid</p><p>אשמח להערות ול’כפיים” אם אהבתם, זה יאפשר לעוד אנשים למצוא את המאמר</p><p>שנה טובה!</p><p>יואב יחיעם | Y-Perspective</p><p>Analytics, Product, Strategy Solutions</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=385118508de0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Could the 3rd most popular TED Talk of all time simply be wrong?]]></title>
            <link>https://medium.com/what-the-f-ck-is-product-strategy/could-the-3rd-most-popular-ted-talk-of-all-time-simply-be-wrong-fad96cd344a3?source=rss-66350b557286------2</link>
            <guid isPermaLink="false">https://medium.com/p/fad96cd344a3</guid>
            <category><![CDATA[y-perspective]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[simon-sinek]]></category>
            <category><![CDATA[product-consulting]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Yoav Yechiam | The Product Alliance]]></dc:creator>
            <pubDate>Thu, 02 Nov 2017 17:00:18 GMT</pubDate>
            <atom:updated>2017-11-22T14:28:33.893Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*eXH_Z1C9D7gdlcRLOyENYQ.jpeg" /><figcaption>Sounds good, but really do they?</figcaption></figure><p>Simon Sinek is one the most popular lectures out there. His TED talk “<a href="https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action">How great leaders inspire action</a>” is the 3rd most popular TED talk of all time. You might remember it by the oft-repeated mantra: “people don’t buy WHAT you do, they buy WHY you do it!” Simon is a great lecturer — not many can argue with that. Nevertheless, I am going to go against the tide and argue that Simon (along with many of his 34 million viewers) is wrong. When it comes to success, HOW matters significantly more than WHY.</p><p>Simon mentions provide a few examples: Apple, the Wright brothers, and even Martin Luther King. Companies, ventures, and movements that succeeded because their leaders viewed their challenge from the inside out, starting with ‘why’, contrary to the common conception. Thus Simon proposes we make decisions by thinking in this order:</p><ul><li>Why do we do what we do?</li><li>How do we do it?</li><li>What do we do?</li></ul><p>His reasons indeed sound very convincing. So how can I claim to prove them wrong?</p><p>You see, I am not saying the Wright brothers did not have the right WHY. I am saying that so did many other teams who eventually did not succeed. The same goes for the Apple case presented. It looks to be a perfect example of survivorship bias, where adding rationale after the fact puts us in danger of believing that the same rationale will lead to future success. We humans have a tendency to judge and conceptualize results based on observations of (only) those who came out on top. Neglecting to consider that the lesson to be taught could actually be with the ones who didn’t make it. Simon is doing exactly that when he claims companies’ WHY (their mission statement) is their reason for success. When he does that he is not taking into consideration those companies which might have had a great WHY yet didn’t take the right path and eventually failed.</p><p>Let’s look at this from the a different perspective: Airbnb, Tinder, Snapchat and even Facebook. Can you identify a clear WHY that explains why they do what they do? Actually, you probably could, in retrospect. But was it there when they took their first steps? Was that what caused them to reach product / market fit? Let’s be honest, if you had asked Mark Zuckerberg or Brian Chesky (Airbnb) back when they were just beginning “What’s your purpose? What’s your cause? Why do you get out of bed in the morning?” their answers would have probably ranged between getting rich and getting laid….</p><p>Simon isn’t completely wrong. The then-startup-now-mammoth companies leading the world do have a clear WHY, and one can argue that these WHYs are what is steering those ships. But that is irrelevant to the 99.99% of the companies out there (a.k.a. us). From visionaries, entrepreneurs, to SMBs and even enterprises, for us the WHY is romantic, but impractical per se.</p><p>For most companies, big to small, the best approach for reaching their goals is <strong>Strategy</strong>, a.k.a. the HOW. Knock yourself out with any WHY you like: “to change the world”, “to challenge the status quo” or “to democratize pet food distribution”. The TED talk viewers didn’t buy WHY Simon said what he said, they bought HOW he said it…</p><p>If you view the talk again you’ll surely notice that it was the rhetoric, intonation, expressions and language that made the talk. Shouldn’t we have all asked ourselves WHY Simon gave this talk? After all, that was the entire point… Well, I’m guessing most of us got stuck and fascinated by HOW it was presented and looked past that… And in all fairness, the results clearly show success.</p><p>You see, the problem is much deeper than a ‘guru’ lecture here or an inspiring “all you have to do” article there. I have nothing against Simon Sinek. He has (other) great leadership lectures. The problem is the ignorance of translating a vision directly into actions before <strong>seriously </strong>considering the path. It happens so often because our point of view shows us many successful companies where we understand the concept and vision — the WHY. We also obviously understand WHAT these companies do (UI, features, agile development processes). But how often do we zoom out to look at the paths these companies did not take. Had we done that we would have probably noticed endless options of what to do that were not done. The great Michael Porter is quoted for saying “Strategy is choosing what not to do”. Now let’s be honest, how true is that?</p><p>If we stop trying to imitate successful companies and focus more on studying what made companies with great ideas bust, we might have a lot more to learn from. Any company, big or small, has so many WHATs to do (concepts, features, optimizations). Leaders need to acknowledge that, and make the effort to thoroughly strategize HOW they can increase their chance of reaching their goals. Many times a big part of that is the ability and flexibility to iterate and adapt to the market.</p><p>As Bono sings “We thought that we had the answers, it was the questions we had wrong”.</p><p><em>Yoav Yechiam is the Owner and Chief Consultant at </em><a href="http://www.y-perspective.com/"><em>Y-PERSPECTIVE</em></a><em> a Product Strategy Consulting firm. He is also a lecturer and does pro-bono mentoring for early stage startup.</em></p><p><em>Originally published at </em><a href="https://medium.com/pminsider/could-the-3rd-most-popular-ted-talk-of-all-time-simply-be-wrong-22c392e3d8b3"><em>PMInsider</em></a><em> on November 2, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fad96cd344a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/what-the-f-ck-is-product-strategy/could-the-3rd-most-popular-ted-talk-of-all-time-simply-be-wrong-fad96cd344a3">Could the 3rd most popular TED Talk of all time simply be wrong?</a> was originally published in <a href="https://medium.com/what-the-f-ck-is-product-strategy">What the F*ck is Product Strategy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Could the 3rd most popular TED Talk of all time simply be wrong?]]></title>
            <link>https://medium.com/agileinsider/could-the-3rd-most-popular-ted-talk-of-all-time-simply-be-wrong-22c392e3d8b3?source=rss-66350b557286------2</link>
            <guid isPermaLink="false">https://medium.com/p/22c392e3d8b3</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[simon-sinek]]></category>
            <dc:creator><![CDATA[Yoav Yechiam | The Product Alliance]]></dc:creator>
            <pubDate>Thu, 02 Nov 2017 17:00:18 GMT</pubDate>
            <atom:updated>2019-09-11T13:07:31.995Z</atom:updated>
            <content:encoded><![CDATA[<h3>Could Simon Sinek’s Popular TED Talk Be Totally Wrong?</h3><h4>How great leaders REALLY inspire action</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F20zuePhxD7P9DWgYnsG5g.jpeg" /></figure><p>Simon Sinek TED Talk is one of the most popular lectures out there. “<a href="https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action">How Great Leaders Inspire Action</a>” is the 3rd most watched TED talk of all time.</p><p>You might remember it by the oft-repeated mantra:</p><blockquote>“People don’t buy what you do, they buy why you do it!”</blockquote><p>Simon is a great lecturer — not many can argue with that. Nevertheless, I am going to go against the tide to argue that Simon (along with many of his 34 million TED Talk viewers) is wrong. When it comes to success, HOW matters significantly more than WHY.</p><h3>Simon Sinek’s TED Talk: How Great Leaders Inspire Action</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fqp0HIF3SfI4%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dqp0HIF3SfI4&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fqp0HIF3SfI4%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/867f142a497ed006ed2eb867c7bf2c81/href">https://medium.com/media/867f142a497ed006ed2eb867c7bf2c81/href</a></iframe><p>Simon provides a few examples: Apple, the Wright brothers, and even Martin Luther King. Companies, ventures, and movements that succeeded because their leaders viewed their challenge from the inside out, starting with ‘why’, contrary to the common conception.</p><p>Thus, Simon proposes we make decisions by thinking in this order:</p><ul><li>Why do we do what we do?</li><li>How do we do it?</li><li>What do we do?</li></ul><p>His reasons indeed sound very convincing. So how can I claim to prove them wrong?</p><p>You see, I am not saying the Wright brothers did not have the right ‘why’. I am saying that so did many other teams who eventually did not succeed. The same goes for the Apple case presented. It looks to be a perfect example of survivorship bias, where adding rationale after the fact puts us in danger of believing that the same rationale will lead to future success.</p><p>We humans have a tendency to judge and conceptualize results based on observations of (only) those who came out on top. Neglecting to consider that the lesson to be taught could actually be with the ones who didn’t make it. Simon is doing exactly that when he claims companies’ ‘why’ (their mission statement) is their reason for success. When he does that he is not taking into consideration those companies which might have had a great WHY yet didn’t take the right path and eventually failed.</p><p>Let’s look at this from the a different perspective: Airbnb, Tinder, Snapchat and even Facebook. Can you identify a clear ‘why’ that explains why they do what they do? Actually, you probably could, in retrospect. But was it there when they took their first steps? Was that what caused them to reach product-market fit? Let’s be honest, if you had asked Mark Zuckerberg or Brian Chesky (Airbnb) back when they were just beginning “What’s your purpose? What’s your cause? Why do you get out of bed in the morning?” their answers would have probably ranged between getting rich and getting laid….</p><p>Simon isn’t completely wrong. The then-startup-now-mammoth companies leading the world do have a clear WHY, and one can argue that these WHYs are what is steering those ships. But that is irrelevant to the 99.99% of the companies out there (a.k.a. us). From visionaries, entrepreneurs, to SMBs and even enterprises, for us the WHY is romantic, but impractical per se.</p><p>For most companies, big to small, the best approach for reaching their goals is <strong>Strategy</strong>, a.k.a. the HOW. Knock yourself out with any WHY you like: “to change the world”, “to challenge the status quo” or “to democratize pet food distribution”. The TED talk viewers didn’t buy WHY Simon said what he said, they bought HOW he said it…</p><p>If you view Simon Sinek’s TED talk again, you’ll surely notice that it was the rhetoric, intonation, expressions and language that made the talk. Shouldn’t we have all asked ourselves WHY Simon gave this talk? After all, that was the entire point… Well, I’m guessing most of us got stuck and fascinated by HOW it was presented and looked past that… And in all fairness, the results clearly show success.</p><p>You see, the problem is much deeper than a ‘guru’ lecture here or an inspiring “all you have to do” article there. I have nothing against Simon Sinek. He has other great leadership lectures beyond his TED Talk. The problem is the ignorance of translating a vision directly into actions before <strong>seriously </strong>considering the path. It happens so often because our point of view shows us many successful companies where we understand the concept and vision — the WHY. We also obviously understand WHAT these companies do (UI, features, agile development processes). But how often do we zoom out to look at the paths these companies did not take. Had we done that we would have probably noticed endless options of what to do that were not done. The great Michael Porter is quoted for saying “Strategy is choosing what not to do”. Now let’s be honest, how true is that?</p><p>If we stop trying to imitate successful companies and focus more on studying what made companies with great ideas bust, we might have a lot more to learn from. Any company, big or small, has so many WHATs to do (concepts, features, optimizations). Leaders need to acknowledge that, and make the effort to thoroughly strategize HOW they can increase their chance of reaching their goals. Many times a big part of that is the ability and flexibility to iterate and adapt to the market.</p><p>As Bono sings “We thought that we had the answers, it was the questions we had wrong”.</p><p><em>Yoav Yechiam is the Owner and Chief Consultant at </em><a href="http://www.y-perspective.com/"><em>Y-PERSPECTIVE</em></a><em> a Product Strategy Consulting firm. He is also a lecturer and does pro-bono mentoring for early stage startup.</em></p><figure><a href="https://productmanagementinsider.com/?utm_source=pmi&amp;utm_medium=article"><img alt="" src="https://cdn-images-1.medium.com/max/531/1*yPRWnRlzXXe8hWuwg2xETA.png" /></a></figure><figure><a href="https://alphahq.com/?utm_source=pmi&amp;utm_medium=article"><img alt="" src="https://cdn-images-1.medium.com/max/530/1*d6feM7YM9xI2c0CPC8XhSA.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=22c392e3d8b3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/could-the-3rd-most-popular-ted-talk-of-all-time-simply-be-wrong-22c392e3d8b3">Could the 3rd most popular TED Talk of all time simply be wrong?</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>