<?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 Asaf Atzmon on Medium]]></title>
        <description><![CDATA[Stories by Asaf Atzmon on Medium]]></description>
        <link>https://medium.com/@beeblebrux?source=rss-a902ae8caca0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KK0T1sG2nJriHjCfBVZ1LA.png</url>
            <title>Stories by Asaf Atzmon on Medium</title>
            <link>https://medium.com/@beeblebrux?source=rss-a902ae8caca0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 06:22:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@beeblebrux/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[LLMs are all the vibe… but what’s next?]]></title>
            <link>https://medium.com/swlh/llms-are-all-the-vibe-but-whats-next-c653d5b7cae5?source=rss-a902ae8caca0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c653d5b7cae5</guid>
            <category><![CDATA[llm]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[programming-languages]]></category>
            <dc:creator><![CDATA[Asaf Atzmon]]></dc:creator>
            <pubDate>Sun, 22 Jun 2025 13:13:29 GMT</pubDate>
            <atom:updated>2025-06-22T13:13:29.386Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>I grew up loving coding — as did many kids who became programmers. But that era is fading fast, slain by LLMs. Is prompting the new programming, or just a step toward an unknown future?</strong></h4><p>I still have a vivid memory of that moment - <strong>my first personal computer</strong> — an Atari 800XL. I must have been 11 or 12. Full of excitement I plugged the box to my TV set and few minutes later I was welcomed with the familiar:</p><pre>10 ____</pre><p>A BASIC interpreter of course, I knew exactly what to do, and without waiting a single moment , I tapped on the keyboard:</p><pre>10 PRINT &quot;ASAF&quot;<br>20 GOTO 10</pre><p>It was my first love and my introduction to programming languages which actually started some 2 yrs before when, like many of my generation , I came across the Sinclair ZX-81. With the help of programming booklets that were available on the local book store, I learned about variables, expressions and arrays, flow control and even some basic graphics (does the name ‘Itzik the Robot’ ring a bell to anyone?)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JAfAkcYDXQGsAXJE.jpg" /><figcaption>Sinclair ZX-81</figcaption></figure><p>BASIC, as the name implies, can take you only so far, so as time went by I moved on to more advanced programming languages. Next there was Pascal , followed by C. And then at university time, Java took the front seat as my language of choice.</p><p>There were also some niche languages such as Logo (with its ‘turtle’ cursor), Prolog (what back then was considered as AI) and LISP, adding more layers of richness to the different ways one can express its intentions to a silicon-made computer.</p><p>Now, one might ask - why so many languages that essentially end up in more or less the same BLOB. But that’s like asking why there so many speaking languages in the world, when essentially we are all the same homo sapiens.</p><p>Programming is a creative and an expressive medium, and in the same way that different speaking languages capture the cultural context and psychological biases of those choosing to speak them, each programming language is an opinionated statement about design choices , trades offs , and forms of expressiveness.</p><h4>But all that is dead now</h4><p>As we shift to AI-native development and vibe coding, we’re essentially moving further and further away from writing code. What Andrej Karpathy describes in <a href="https://x.com/karpathy/status/1886192184808149383?lang=en">his viral post</a> captures very nicely the experience I personally subscribe to —<strong> finding myself more and more avoiding diving into code</strong>. Call it laziness, call it a growing trust in the machine — the fact remains, that coding, at least in the traditional sense, is in historic decline.</p><p>This is not a small matter, and it calls for some first-principle thinking about what we mean by code and coding. I always think of <strong>code as an intermediary </strong>— a medium to bridge between humans’ intentions and machine code. In that sense, different programming languages always traded off between the verbosity and expressiveness of the code (to align well with human-level thinking) and efficiency (Rust being a unique example that manages to hold both ends of this rope).</p><p>But for the first time in computing history, it seems these intermediaries are being removed. Anyone who had some experience with <a href="https://x.com/karpathy/status/1886192184808149383?lang=en">Lovable</a>, <a href="https://v0.dev/">v0.dev</a> and their likes , would easily recognize that. You type what you want — and voilà , you get what you’ve asked for (well sorta, but with enough iterations intentions do converge to a desired output). This is really the ‘vibe’ in vibe coding and is inspiringly lifting historic barriers of accessibility from the broad population, that until very recently was barred of this “holy grail” of coding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Obx2bvfehUbq2pwgFtZzsw.jpeg" /><figcaption>Kids vibe coding (credits: Google Gemini)</figcaption></figure><h4>Is prompting just another high-level language?</h4><p>Obviously , behind the scene , a lot of code is still being generated , only this time by the machine rather than by the human being. Initially this came as quite a surprise for us — “knowledge workers” — realizing after years of disillusion, that programmers , rather than truck drivers, are the first victims of the AI revolution, but is now being generally regarded as nothing short of inevitable.</p><p>After all, programming languages , being a formal structure by definition are large language models’ (LLM) favorite food and on top of that there’s the sheer amount of code out-there available to have them trained on. It should come as no surprise then that LLMs excel at generating code more than at any other task.</p><p>Our friend, Andrej, is not completely wrong to consider English as the <a href="https://x.com/karpathy/status/1617979122625712128?lang=en">hottest new programming language</a> , and of prompts as a new kind of programs. At least when interpreted languages like Python and JavaScript are considered, prompts are not that different from any conventional program. Both are abstractions , provided as a stream of characters to a binary, and resulting in a machine code. Might it be only a matter of flexibility? Another level of expressiveness that makes a better bridge between humans and machines?</p><p>Well… Yes and no. For sure, one big difference is in the levels of predictability and determinism we can attribute to program execution. While very few of us know or bother with trying to understand the internals of a python interpreter, when we write a program we know with high certainty what would be the output. This is not the case with LLMs when even the same prompt may result in a different code altogether upon subsequent invocations.</p><p>There are techniques to minimize that effect by rigid prompt engineering, controlling model temperature and other means, thought there’s definitely a growing need for innovation in this area. Then , in some other cases, all the more so when developing in a recreational vibe mode on a weekend’s project, this ‘surprise element’ can actually be quite nice and inspiring.</p><h4>Bye bye IDEs …</h4><p>Nothing in what said so far is bad news. Off-sourcing the tedious aspects of syntax proofing to a machine , frees us humans to work at higher levels. Moving from assembly to C to Java to JavaScript — every such phase has us working at higher layers of abstractions. And moving from coding to prompting, not only feels like a breath of fresh air for us, current developers , but also further extend the notion of ‘<strong>us</strong>’ to actually become ‘<strong>everyone</strong>’ — <strong><em>we are all software developers, but less and less are we coders</em></strong>.</p><p>At the end of the day, <strong>code is code</strong> , be it generated directly by humans or prompted to LLM which then generates it. But ever wonder why is it necessary for LLMs to generate their artifacts in familiar programming languages?</p><p>Well.. one obvious reason is that this is what they were trained of, so this is what they excel at. An LLM is essentially a completion algorithm, that must adhere to the same alphabet soup it has swallowed during its training. Another reason is that it allows us humans to oversee and control the code generation, debugging and correcting as needed.</p><p>I’d argue that both reasons are gradually losing relevance ….</p><p>As time goes by and LLMs becomes overly stronger and more autonomous , we are due to part ways from our intimacy with code. Today, IDEs are still the primary interface for vibe coding, but more and more this gives way to <a href="https://github.com/getAsterisk/claudia">other types of interfaces</a> , as we move from coding with co-pilots to “overseeing agents”, where we <em>fuel in our intentions and observing results with the sole use of prompting</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pBjQf-8F7o7n_Z4N.png" /><figcaption>Coding with Cursor and Visual Studio Code</figcaption></figure><h4>LLM-optimized-code — the end of society?</h4><p>LLMs still generate their artifacts in Python, JavaScript etc for the reasons mentioned above , but these are <strong>wasteful and inefficient generations</strong> resulting in a lot of output tokens.</p><p>The race for LLM dominance passes through <a href="https://www.holo.mg/stream/tech-policy-press-sam-altman-us-senate-cost-of-ai-energy-converge/">the race for energy abundance</a> . The number of tokens LLMs produce matter — a lot. Why not come up with an LLM optimized generation which is tokens’ efficient? When the burden of generating human-readable code is uplifted from LLMs, there’s really no reason to stick to these “old human languages”.</p><p>The rate of LLM-generated-code is still radically small compared to that of humans, but that gap is expected to rapidly shrink. LLMs will still produce code in familiar programming languages for the time-being , but why couldn’t they <strong>also</strong> generate LLM-optimized-code at the same time. And then, new models will start get trained only on that code, and produce more of it in a self-propelling accelerated pace. At some point we will have reached the “end of support” for human-readable languages.</p><p>This will be a critical milestone that while is positive for energy preservation and computing performance, might mark the actual end of human society. LLM-optimized-code is likely to be indecipherable for humans and for the first time we will find ourselves at the mercy of a black box when the only thing we can control is what goes in, and then measure what comes out at the other side. And maybe at some point , not even that.</p><p>That calls for an unprecedented level of trust we would be asked to put on an entity that by all considerations possess very different DNA and psychology from us human. Who’s to say it will act as the benevolent leader rather than as a ruthless dictator?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c653d5b7cae5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/llms-are-all-the-vibe-but-whats-next-c653d5b7cae5">LLMs are all the vibe… but what’s next?</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Be Running Up That Hill]]></title>
            <link>https://medium.com/swlh/be-running-up-that-hill-3873675aaa2e?source=rss-a902ae8caca0------2</link>
            <guid isPermaLink="false">https://medium.com/p/3873675aaa2e</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Asaf Atzmon]]></dc:creator>
            <pubDate>Wed, 17 Feb 2021 15:18:19 GMT</pubDate>
            <atom:updated>2021-02-20T15:22:20.564Z</atom:updated>
            <content:encoded><![CDATA[<h4>How Basecamp’s Hill Chart provides a useful frame of reference to master the Startup chaos</h4><figure><img alt="A Hill" src="https://cdn-images-1.medium.com/max/1024/0*9qxv5EvHQjVUUSPn" /><figcaption>Photo by <a href="https://unsplash.com/@karlbewick?utm_source=medium&amp;utm_medium=referral">Karl Bewick</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Working at startups can often feel as an exercise in balance. With so many things happening at the same time, and with multiple forces pushing to different and often opposing directions, one can easily feel quite disoriented. This <em>digital vertigo</em> is further exacerbated by the fact that any member of the team usually wears more than one hat, and so juggling becomes the de-facto national sport.</p><p>All these conditions often translate into a mentality of ‘<em>let’s just do it’, </em>which might seem as the only <em>modus operandi</em> available given that traditional processes just don’t work at this environment. This can be attributed to at least three characteristic apparent in a startup settings:</p><ol><li>Startups are <em>risky</em> — by definition, it is an environment of extreme uncertainties, fighting against an alarming statistics that &gt;90% of the things you will try are likely to fail.</li><li>Startups are <em>chaotic</em> — building a structure into the culture is often perceived as a way to kill innovation and curtail agility.</li><li>Startups are <em>opportunistic — </em>the risk of forgoing a quick win or a way to get traction is very high, and it’s hard to balance long-term strategy with short-term gains, often giving the latter the default priority.</li></ol><p>With so much at stake, it is not surprising then, that luck rather than process tends to creep into our overall thinking of what will make a startup successful. But this is a tendency we must fight rather than embrace. Relying on luck in an environment where the odds are inherently against us, is not unlike surrendering to a high-fat diet when you suffer overweight; and is in fact, giving the upper hand to what is most likely to end up killing you.</p><blockquote>With so much at stake, it is not surprising then, that luck rather than process tends to creep into our overall thinking of what will make a startup successful. But this is a tendency we must fight rather than embrace.</blockquote><p>Obviously, these observations are hardly new and have been written about and discussed extensively in innovation management literature, such as Steve Blanks’ <a href="https://www.amazon.com/Four-Steps-Epiphany-Steve-Blank/dp/0989200507">Customer Development</a>, Eric Ries’ <a href="https://www.amazon.com/Lean-Startup-Entrepreneurs-Continuous-Innovation/dp/0307887898">The Lean Startup</a>, Clay Christensen’ ‘<a href="https://www.amazon.com/Competing-Against-Luck-Innovation-Customer/dp/0062435612/ref=sr_1_1?crid=1XZP3L5OCXXXE&amp;dchild=1&amp;keywords=competing+against+luck&amp;qid=1613570577&amp;s=books&amp;sprefix=competing+aga%2Cstripbooks-intl-ship%2C273&amp;sr=1-1">Competing Agains Luck</a>’ and more. These books, and others, are tackling the exact idea of how <em>luck is the enemy of process</em> and what a startup innovation should look like in order to increase its chances to meet a product-market fit. There are many good ideas in these books, but they don’t necessarily provide very practical tools for entrepreneurs to make decision on a day-to-day basis; this is where <em>The Hill Chart </em>comes into play.</p><h3>The Hill Chart</h3><p>The Hill Chart is a concept that was brought to life by Basecamp (formally ’37 signals’) who are known to innovate on many agile areas of project management execution, such as the modern ‘to-do-lists’. They are also the brain behind the highly recommended book — “<a href="https://basecamp.com/books/getting-real">Getting Real</a>”.</p><p><a href="https://basecamp.com/features/hill-charts">The Hill Chart</a> depicts in a visual way the lifecycle of a product idea, based on what is our level of understanding of it.</p><p>It looks like this:</p><figure><img alt="Hill Chart" src="https://cdn-images-1.medium.com/max/1024/1*CYcLOKXFpkJVMuX52JD8wA.png" /><figcaption>Hill Chart (source: basecamp.com)</figcaption></figure><p>Being a hill, it has both an upward slope and a downward one. Roughly speaking, these separate slopes represent the two distinct modes by which features or ideas are introduced into the software manufacturing process. The left (upward) side represents <strong>discovery </strong>and focuses on the phase of the project (or idea) when uncertainty is high. The key objective of this phase is <em>learning</em>. The right (downward) side represents <strong>delivery </strong>and focuses on the phase where product requirements are generally defined and clear and the level of certainty with respect to the market need is high. The key objective of this phase is <em>working software</em>.</p><p>The Hill Chart is both very simple and highly useful in that it allows an organization to get a quick idea of how projects and roadmap items are positioned with respect to their level of certainty. It also nicely depicts to what extent the company is balanced between doing innovation (left) and executing (right).</p><p>Let’s consider few additional aspects related to the Hill Chart:</p><h4>Things Look Different At Each Side Of The Hill</h4><p>It’s important to realize that each side of the hill represent a very different approach, and calls for a different mindset and methodologies. Much of the innovation literature, from <em>lean</em> to <em>customer delivery</em> to <em>design thinking</em> focuses on how to ‘figure things out’. Generally speaking, the key critical functions of the upward slope are <em>Product Management</em> and <em>Product Design, </em>that are tasked respectively with optimizing for the business and for the user experience. The downward slope is the territory of <em>Engineering</em> and is optimized on providing working software on-time, on-quality and most importantly, one that delivers on the product and UX desired outcomes.</p><p>Many companies, at their early stage, tend to mix these two separate modes into a single process, or more often than not, kind of leapfrogging the discovery mode altogether. <em>Velocity</em> in physics means both speed and direction; so focusing on the downward slope only could mean moving at high speed to the wrong direction.</p><h4>Both Slopes Deserve a Process</h4><p>At 2001, 17 software developers met at a resort in Utah, and few days later, brought down from the mountain what was to become <em>The Agile Manifesto. </em>That manifesto has articulated a set of values and priorities for software developments, which were:</p><ul><li><strong>Individuals and interactions</strong> over processes and tools</li><li><strong>Working software</strong> over comprehensive documentation</li><li><strong>Customer collaboration</strong> over contract negotiation</li><li><strong>Responding to change</strong> over following a plan</li></ul><p>Since then, Agile has become the de-facto development philosophy for most companies, boosting popularity to methodologies such as <a href="https://www.scrum.org/">Scrum</a>, <a href="https://en.wikipedia.org/wiki/Kanban_(development)">Kanban</a>, <a href="https://www.scaledagileframework.com/">SAFe</a> and <a href="http://www.extremeprogramming.org/">XP</a>. Unfortunately, none of these cater for the part of the process that deals with figuring out what to build in the first place. The hill, through the Agile lens, starts at the top, with no ascending. Agile teams expect to be told what to develop, and giving no regards to the slope that leads to that starting point. In other words, they don’t admit <em>discovery</em> in.</p><p>Since the incarnation of Agile, they were some efforts made to embrace <em>discovery</em> in, both by UX masters like <a href="https://medium.com/u/94a2a063be85">Jeff Gothelf</a> (<a href="https://www.smashingmagazine.com/2011/03/lean-ux-getting-out-of-the-deliverables-business/">Lean UX</a>) who advocates for product design inclusion in the Agile process, as well from the Agile gurus themselves, but largely speaking, these efforts recognize at best that product and UX should be considered as citizens in the Agileland, often merely as second-class one.</p><blockquote>Agile deals with producing software in small batches and at high velocity. It’s a better approach for sure, but without a sound discovery process, we would still end up producing the same amount of waste.</blockquote><p>Instead, <em>discovery</em> deserves its own process and cannot be left as a “UX whim”. A startup, with its &gt;90% failure rate, is bound to produce a lot of waste — all those features we end up scrapping due to market disinterest. Lean and UX deal with reducing that waste; Agile deals with producing software in small batches and at high velocity. Without the left side of the hill, all we will be doing is throwing out waste in many small buckets, rather than in one big garbage bin. It’s a better approach for sure, but without a sound discovery process, we would still end up producing the same amount of waste.</p><h4>There Are Little Hills Along the Hill</h4><p>Hill Charts can be created in many resolutions. There is the company-wide hill showing the big projects and initiatives, small hills for each product, and even smaller hills for single features. Almost everything we do goes through the same process of first figuring it out, and then executing it.</p><p>So rather than thinking of our landscape as a one giant hill, we should instead picture it as having small hills spread out along the slopes, and even smaller ones staged on those.</p><p>For example, a company may have a mature product which is already well-situated on the right-end of the company’s hill. This may be the classic “cash cow” of a company. That doesn’t mean that no innovation funnels to the product plan, and similarly doesn’t mean that we have ‘figured everything out’. We all know how quickly market and technology trends emerge or die, and it is critically important for a mature product to continue embrace new ideas, both to keep it relevant to existing customers as well to open up to new segments and markets. In such a case, we can envision a hill (the product) placed at the right-end of the company hill, with a pinpoint placed on its left-end side, to represent the new feature.</p><p>Conversely, that same company may decide to reach out to a new market or industry or just solve a new problem to its existing market. In all these cases, they will be entering an uncharted territory which calls for a customer discovery process and an articulation of a business case. This project, will be placed at the left-end of the company hill, far from its mature product relative. But in both cases, there should be a discovery.</p><h4>Running Back to the Starting Point</h4><p>The Hill Chart is misleading in one aspect; it may give the impression that we march out of the other side of the hill as victors of our game. We should recall however that the entire lean cycle talks about the Build-Measure-Learn loop. That means that very often our development process is the basis for new uncertainties, which in turn sends us back running to the beginning of the hill for a new cycle.</p><blockquote>The Hill Chart may give the impression that we march out of the other side of the hill as victors of our game. But very often our development process sends us back running to the beginning of the hill for a new cycle.</blockquote><p>This of course can happen at all the resolutions discussed above, and one thing to be minded to is the <em>cadence</em> of the company with respect to hill climbing. A truly agile organization is one that has troops scattered ,rather uniformly, at all times, across different areas of its hills, with a lot of running and moving around. One way to measure that cadence is by taking periodical snapshots of this <em>terrain</em> and observing the mobility it shows.</p><h4>Hand-offs and Dual Tracks</h4><p>The last topic worth discussing is how projects and tasks are handed-off between the left-side and right-side of the hill. I dare to say, that this is by far the highest friction point of product execution and so something that should be addressed with extra consideration.</p><p>In many ways, the hand-off is driven by the organizational structure of the company. The traditional structure, which is still the prominent one, is that companies are organized by functions, so you have a product management team, a UX team (which may, or may not, be reporting to the same head as product) and an engineering team. That structure pretty much entails that product and UX will spend most of their time on the left-side, while engineering on the right-side (as a side note, faithful to the Scrum torah, I consider the <em>Product Owner </em>as part of the engineering team, and separate from the Product/UX).</p><p>In such a scenario, communication becomes critical as many things tend to fall between the cracks or get misinterpreted at the hand-off at top of the hill. Regular meetings, ceremonies and a slew of product and UX artifacts are the norm to ensure improving the hand-off process.</p><p>There is a better way, however, which is having no hand-offs at all. This is harder to build but can have a much better outcome. The idea is to have a single squad team going through the entire hill. That doesn’t mean that everyone is doing everything. Product designers are unlikely to code more than developers will do customers interviews, but it does mean that the team, as a whole, shares a unified sense of ownership and accountability to the full process. Beyond the clear merit of a much smaller chance for dropouts, it provides a lot of opportunities for engineers to take part, as witnesses and even as contributors, in the customer discovery phase, which allows them to develop <em>empathy</em> that would later help in a better outcome of the software they build.</p><blockquote>Product designers are unlikely to code more than developers will do customers interviews, but a squad structure does mean that the team, as a whole, shares a unified sense of ownership and accountability to the full process.</blockquote><p>More and more <a href="https://www.youtube.com/watch?v=4GK1NDTWbkY">companies are moving to squads</a>, and UX gurus such as <a href="https://medium.com/u/b90ef6212176">Jared M. Spool</a> and Jeff Patton are strong advocates to this approach. Pattons’ <a href="https://uxdx.com/session/recfw0kvxrnxoor4r/">dual-track development</a> is a great starting point to get a grasp of how this works.</p><h3>Wrap-Up</h3><p>Building predictability in the unpredictable nature of startups is a hard task, but it’s the most effective way to fight against the goddess of pure luck. Investing only on the predictability of working software (read: Agile) is not enough and does very little to reduce waste or keep us in the right direction.</p><p>The Hill Chart is a simple and effective way to gain a good understanding of our investment both in <em>learning</em> and in <em>delivery</em> to make sure that they are effectively balanced.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3873675aaa2e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/be-running-up-that-hill-3873675aaa2e">Be Running Up That Hill</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Eric Ries and the Wizard Of Oz]]></title>
            <link>https://medium.com/swlh/eric-ries-and-the-wizard-of-oz-3de11e800784?source=rss-a902ae8caca0------2</link>
            <guid isPermaLink="false">https://medium.com/p/3de11e800784</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Asaf Atzmon]]></dc:creator>
            <pubDate>Mon, 25 Jan 2021 10:31:21 GMT</pubDate>
            <atom:updated>2021-01-26T08:05:33.419Z</atom:updated>
            <content:encoded><![CDATA[<h4>THE LEAN STARTUP</h4><h4>Some concerns about the Ethics and overall applicability of The Lean Startup in current times</h4><figure><img alt="The Wizard Of Oz , Movie Banner" src="https://cdn-images-1.medium.com/max/992/1*Hf1tS1xePwnfW-TcRzgADg.jpeg" /><figcaption>Source: Warner Bros.</figcaption></figure><p>In previous posts I have discussed <a href="https://medium.com/u/d2f31bf094c6">Eric Ries</a>’s well-known <a href="http://theleanstartup.com/">The Lean Startup </a>theory, going through <a href="https://beeblebrux.medium.com/5-key-concepts-of-the-lean-startup-5b192da96848">its core elements and key takeaways</a>. I also provided my own personal impression, working in and with many startups, of some of the <a href="https://medium.com/swlh/5-things-product-teams-get-wrong-about-the-lean-startup-2b718629064b">key mistakes or misinterpretations</a> that are often made in practice.</p><p>Today I want to shed some light on another angle, often missed, of this book, that personally strikes me as the most troubling one. It is not something that Ries openly discusses, but it is implicitly present throughout many of the techniques that are given as a way of learning and experimentation and through some of the key successful case studies that are mentioned. <br>What I’m talking about is<em> the core principal of deception</em>.</p><p>Let’s start with an example provided by Ries himself and his tale of the story of <a href="https://en.wikipedia.org/wiki/Aardvark_(search_engine)">Aardvark</a>, which was a social search engine, developed by Max Ventilla and Damon Horowitz and later acquired by Google. Aardvark aspired to create a knowledge market, connecting people with questions to a social network of users that could provide answers, through a sophisticated matching algorithm.</p><p>Ries writes in his book: “Throughout their testing process, Max and Damon encountered many difficult technological problems like these. Each time, they emphatically refused to solve them at that early stage. Instead, they used <em>Wizard of Oz testing</em> to fake it. In a Wizard of Oz test, customers believe they are interacting with the actual product, but behind the scenes human beings are doing the work.”</p><p>Indeed, one can recall the spectacular imagery of the beloved film, with the magical acts pulled off by The Wizard as Dorothy and the gang is approaching him for help. Ries’s point of course is that, “The Wizard of Oz” is a great technique to test your assumptions before (and without) building the real product, and investing only on the facade. Of all examples in this book, this one, has always left me somewhat uncomfortable, because of one main reason — <strong>The wizard was a humbug</strong>.</p><blockquote>“The Wizard of Oz” is a great technique to test your assumptions before building the real product but the wizard was a <strong>humbug</strong>.</blockquote><h4>The American Fairytale</h4><p>“The (Wonderful) Wizard Of Oz”, was published at the birth of the 20th century by a then anonymous 44-years old, Frank Baum, and became an overnight success. It is considered by many to be <a href="https://slate.com/news-and-politics/2009/09/dissecting-the-real-wizard-of-oz.html">the father of the American fairy tale</a>, and is universally regarded as one of the most favorable and memorable children’s’ story (and later on, one of the most successful and beloved movies).</p><p>What many people do not necessarily acknowledge is that to a large extent this story was written by Baum as a critique to his era’s problems of social injustice, women’s suppression and the concerning rise of unethical business practices, represented by the <a href="https://en.wikipedia.org/wiki/Robber_baron_(industrialist)">Robber Barons</a> at the heart of <a href="https://en.wikipedia.org/wiki/Gilded_Age">The Gilded Age</a>. All of Baum’s heroes are in fact heroines, while the male characters represent a less flattering view of human’s character, including the dubious threesome that accompany Dorothy, but first and foremost, through the key character of the book — The Wizard.</p><p>The Wizard turns out to be a fraud. He is “a little old man, with a bald head and a wrinkled face” and is being exposed in the most wretched way, by Toto, the small dog, that tips over a screen the Wizard hides behind. He is also an immoral man — before revealed, he is actually using his fake spectacle to send Dorothy and the gang on a suicide mission to kill the Wicked Witch of the West. And like many of the real-life examples of corruption we got to know in our times, The Wizard ends up being pardoned and returns safely to his home in Omaha.</p><p><a href="https://en.wikipedia.org/wiki/Political_interpretations_of_The_Wonderful_Wizard_of_Oz">Different interpretations have emerged</a> over the years with respect to who is the wizard, but whether Baum has intended to take on a certain political figure of the time, or an industry baron, in many ways, the Wizard, just as well comes across as an archetype of the “used cars sales person”. As someone, who uses cheap and cheesy tricks to manipulate us into something which is not in our best interest.</p><p>Back to The Lean Startup — we could dismiss this as merely a poor choice of metaphor by Eric Ries, if not for the fact that this fraudulent approach persists through many aspects of the book. Let’s take a closer look…</p><h4>Experiments In Deception</h4><p><a href="https://en.wikipedia.org/wiki/Galileo_Galilei">Galileo Galilei</a> is considered the forefather of the scientific controlled experiment. His famous <a href="https://en.wikipedia.org/wiki/Galileo%27s_Leaning_Tower_of_Pisa_experiment">Leaning Tower of Pisa experiment</a> is a great case in point for how to test variables in isolation in order to get a clear insight into cause and effect. I wrote previously how Ries drew a lot of his approach from the knowledge corpse of science, and the idea of a controlled experiment has clearly influenced his model of the Build-Measure-Learn feedback loop. However, there is one very important distinction between the scientific approach and what Ries suggests; In The Lean Startup, the testing subjects are not still objects, but rather people, more precisely , they are our customers.</p><blockquote>In The Lean Startup, the testing subjects are not still objects, but rather people, more precisely , they are our customers.</blockquote><p>Of course, experiments in social studies are not new either, and have been used excessively in psychology, economics and life sciences. What’s common in all these studies is that for them to be effective, the subject must not know he is tested, or in other cases, what he is tested for. This is often achieved through the creation of a <em>control group </em>and by manipulating variables between that group and the test subjects, without the participants being aware of that. In other words, is must include deception by design. It’s no wonder then, that questions of ethics have always been part of the general debate around these practices.</p><figure><img alt="Pisa Tower" src="https://cdn-images-1.medium.com/max/1024/0*7m_z5WeolYKNTQIO" /><figcaption>Photo by <a href="https://unsplash.com/@alexrvasey?utm_source=medium&amp;utm_medium=referral">Alex Vasey</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Surprisingly, Ries provides almost no account to the ethical aspect of manipulating users, beyond a careless dismissal of the point, arguing that users are <em>forgiving</em> and that it’s ok every now and then to “<em>burn” </em>a group of users, for the important objective of learning. But beyond the ethical question, it’s also worthwhile to ask ourselves, can we really afford to “burn” customers and are there cases where they might not be such forgiving.</p><p>Here are some point to consider:</p><h4>Customers Expect Value</h4><p>The simplified, but generally correct formula for a good business is that it provides value to customers and that a meaningful portion of that value can be extracted back to the company. The first part lies in the <em>value proposition</em> while the second in the company’s <em>business model</em>. A startup’s learning phase cannot happen in a vacuum; in Steve Blank’s word it has to happen <em>outside of the building</em>. Our experimentation must involve real users, and to my point above, they often mustn’t know they are in an experiment. In other words, from their perspective, <strong>it is the real product</strong> we ask them to interact with.</p><p>If we optimize only for learning, and disregard the objective of providing value to the customer, how can we expect them to come back as users once they figure out they have been manipulated and deceived? When you’re in the B2C business, with hundreds of millions of target customers, it might be ok to burn some on the route of learning (and even they may come around given the nature of B2C); but what is the case when your customer can represent 2% of you business, like in the case of highly consolidated industries like telecommunication, media, automotive, healthcare etc. Is it reasonable, in these cases, to “sacrifice” a great potential customer for the sake of learning, by providing no valuable deliverable and hiding behind manipulative experiments?</p><p>Of course, we can be more transparent and open in such cases with our customers; inviting them into our learning path. This is typically done through <em>beta testers</em>, <em>pilot programs</em> and <em>design wins</em>. That will have some merit and value but it does limit our way to build a controlled environment and extract the most of our learning.</p><h4>Sending Users on a Goose Chase</h4><p>One of the most common techniques for experimenting in the Lean fashion is through A/B testing. Two versions of the product are generated with an independent variable that is used differently between the variants. For example, suppose we wish to test a new color schema for our app; we would develop such version but deploy it only to a <em>controlled group</em> of users; we will measure results (e.g. overall engagement) over a period of time and then compare it with the baseline version.</p><p>A/B testing is often combined with <a href="https://unbounce.com/landing-pages/test-new-products-and-ideas/">The Landing Page</a> technique. Rather then building a full implementation of the new feature at test, we merely build the advertisement of this feature. E.g we would build an SEO campaign of a new feature (that we haven’t really developed yet) and when users click through the link, they will be asked to take a follow-up action (e.g. fill up a form); in some cases, they may even get an e-book to download as an ‘act of courtesy’, but really, this entire staging is made solely for the purpose of gauging their interest in a feature, as a decision factor to develop it. This is of course not what the user was expecting when she first clicked the link.</p><p>Some startups may go even further with providing buttons that go into 404 Not Found pages, or pushing menu items into their app just to popup a ‘coming soon’ message. Again — as an army of consumers we were indoctrinated to accept these tactics, but not all industries or environments are as forgiving.</p><p>Would a radiologist play along with a new “stroke detection” AI algorithm that doesn’t work? Would a procurement manager in a telecom company look favorably on a vendor with features that only lead to e-book downloads? Would even us as customers be supportive of updated self-driving features that are meant to be used as experimental?</p><h4>Placebo Can Kill You</h4><figure><img alt="Placebo" src="https://cdn-images-1.medium.com/max/1024/1*5n5wh0yXLOZnWFKQ2xh0Xg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@adamsky1973?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Adam Nieścioruk</a> on <a href="https://unsplash.com/s/photos/medicine?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>This last point probably worth more thought. Some companies have been using lean approaches in some quite radical environments. Elon Musk at Tesla is probably the most vocal in his bold approach of experimentation. In Oct 2020 Tesla has pushed <a href="https://www.theverge.com/2020/10/22/21528508/tesla-full-self-driving-beta-first-reaction-video"><strong>a beta</strong> update of self-driving feature</a> to a selected group of customers. A beta is another way to call an MVP and is often being launched as a learning exercise. That a company which already had <a href="https://www.theguardian.com/technology/2018/mar/31/tesla-car-crash-autopilot-mountain-view">incidents involving fatalities</a> with its self-driving feature is permitted to trial it on customer, with large ambiguity with respect to the regulatory framework around it, is of a big concern.</p><p>On a more general note, we are gradually becoming dependent on AI-driven software that is injected at the core of autonomous decision making processes, whether this is for autonomous driving, healthcare diagnostic, insurance claims management and many other aspects. There is already <a href="https://www.partnershiponai.org/aiincidentdatabase/">an alarming number of cases of biases</a> and big mistakes being made by these algorithms. Allowing the lean approach into this already under questioning area could results in some catastrophic results. Would you accept to get a false diagnostic of cancer, due to an algorithm that was provided with basic functionality as part of a lean learning phase? Worse, would you accept it to miss a diagnostic of a real cancer?</p><h4>Customers To Burn</h4><p>All the examples I provided share a common theme which I call <em>The Fallacy of B2C</em>. They can be very effective when you’re building a consumer-driven business, targeting a large number of potential users, and where the cost of mistake or bad quality is low. However, they are much more challenging and less practical in other kind of settings, such as B2B, or when your product interacts with mission-critical systems. They are also questionable in a world which is moving gradually into AI-based autonomous systems.</p><blockquote>Ries often defines the Startup runway is the # of pivots it can have before it runs out of cash. There’s a more important metric which is the # of “customers to burn”.</blockquote><p>While Eric Ries can be forgiven for the last point — AI was hardly <em>A Thing </em>in 2011 — it does seem to be a big oversight on his end to dismiss those other factors. It’s not surprising that merely all of his great examples in the book, borrow from a narrow pool of B2C business and initiatives (contrary to his explicit objectives brought in the introduction and the overall spirit of the movement).</p><p>Ries often defines the Startup runway as the # of pivots it can have before it runs out of cash, but I do believe there exists a more important metric which is the # of “customers to burn” — a metric that must take into account your total addressable market, its consolidation, how mission critical is the business, what’s the overall tolerance for forgiveness and what is the nature of the software involved.</p><h4>So Where Do We Go From Here</h4><p>The Lean Startup is a powerful theory. It has been the inspiration of many managers and entrepreneurs including the author of this post. It has been used in practice with some very successful outcomes and overall it has been a strong pillar in bringing a management theory into the otherwise chaotic nature of startup’s innovation.</p><p>But The Lean Startup needs some shaking up as it starts to show its age and is challenged in how broad is its applicability. It is a great baseline, and by no means should we turned our back to it, but a new revision of it must consider some of its key current flaws such as addressing ethical aspects of it, extending it to broader markets and industries and addressing new problems such as the changing nature of software and AI. Underlying all these objectives, and in the spirit of the original movement, it should provide some science to the notion of “customers to burn” (or whether it is ok to ‘burn’ them in the first place).</p><p>All this is likely a subject for future research.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3de11e800784" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/eric-ries-and-the-wizard-of-oz-3de11e800784">Eric Ries and the Wizard Of Oz</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Things Product Teams Get Wrong About the Lean Startup]]></title>
            <link>https://medium.com/swlh/5-things-product-teams-get-wrong-about-the-lean-startup-2b718629064b?source=rss-a902ae8caca0------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b718629064b</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Asaf Atzmon]]></dc:creator>
            <pubDate>Thu, 14 Jan 2021 07:55:40 GMT</pubDate>
            <atom:updated>2021-01-17T16:17:59.259Z</atom:updated>
            <content:encoded><![CDATA[<h4>THE LEAN STARTUP</h4><h4>An honest account on how The Lean Startup is being implemented in practice and why 90% of the Startups still fail</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Sw5yhb5FIzPS6pZ8" /><figcaption>Photo by <a href="https://unsplash.com/@epicantus?utm_source=medium&amp;utm_medium=referral">Daria Nepriakhina</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In <a href="https://beeblebrux.medium.com/5-key-concepts-of-the-lean-startup-5b192da96848">my previous post</a>, I gave a brief overview of <a href="http://theleanstartup.com/">The Lean Startu</a>p theory of innovation by <a href="https://medium.com/u/d2f31bf094c6">Eric Ries</a>, and walked through its key concepts. As Ries describes in the introduction part to his book, his motivation to write it came mostly from his observation of the troublesome rate by which startups all around him were failing .</p><p>According to him, these are the two key reasons why startups fail:</p><ol><li>Planning too much — what Ries calls “the allure of a good plan, a solid strategy, and thorough market research”; in a startup world of extreme uncertainty, this traditional thinking, he argues, will bring companies down.</li><li>Going to the other extreme of abandoning traditional “heavyweight” management mindset and adopting instead a “just do it” approach, leading to a chaotic management style that draws the startup into a death spiral.</li></ol><p>The Lean Startup then aims to be the sliver-lining of these two approaches, with the aspiration to bring a process and a method to the subtle art of running a startup.</p><p>Given the high success and popularity of this book, one would expect to see a steep decline in the failure rate of startups. Not quite so. A quick survey on the Internet shows that we are very far from this goal. According to different sources (like <a href="https://www.failory.com/blog/startup-failure-rate">here</a>, <a href="https://review42.com/what-percentage-of-startups-fail/">here</a> and <a href="https://www.profitfromtech.com/startup-statistics/">here</a>) <strong>&gt; 90% of startups fails</strong>. The exact same rate was reported <a href="https://www.forbes.com/sites/neilpatel/2015/01/16/90-of-startups-will-fail-heres-what-you-need-to-know-about-the-10/?sh=1aa2af586679">some 6 years ago</a> too. The #1 reason startups fail (what has also been constant over the last 10 years or so), is a lack of market, or inadequate product-market fit — the very same problem The Lean Startup was looking to solve.</p><p>What’s at work here? How come following almost a decade of a solid business theory and a set of best-practices, the core pathology that kills startups is still upon us? Might that be some software-based version of “<a href="https://www.businessinsider.com/apple-antennagate-scandal-timeline-10-year-anniversary-2020-7">Antennagate</a>”? In other words “ is it possible that we are ‘holding it wrong’”?</p><p>I’d like to suggest this is exactly the case, and that despite its popularly, the key lessons of The Lean Startup have been time and again misunderstood, misused and abused, leading to a stagnant low productivity of growth through innovation. Let us count the ways:</p><figure><img alt="Apple iPhone 4 “you’re holding it wrong”" src="https://cdn-images-1.medium.com/max/600/0*BOvxnHNLushWuA6t" /><figcaption>“You’re holding it wrong” (source: Apple)</figcaption></figure><h4>#1 — Don’t Sell, Learn</h4><p><a href="https://medium.com/u/974d6573e9dc">Reid Hoffman</a> has famously said — “If you are not embarrassed by the first version of your product, you’ve launched too late”. It is a controversial statement, but the way I read it is in the understanding that early versions of your products should not be optimized for customer satisfaction but for your own learning.</p><p>Ries defines the runway of a startup as the # of pivots it can have before it runs out of cash, but a better measure might be the # of <em>experiments</em> it has, hoping it doesn’t actually run out of cash, but transitions at some point into a delivery organization. Either way, startups would do wise to consider the first stage of their lifetime as a learning phase, where the ‘versions’ of your product are not optimized for customer delivery but for market validation, and given the need to maximize runway, it, by definition, will de-prioritize quality, sleekness, delight and usefulness (unless these properties are in and on themselves part of the learning experience). In that sense, ‘embarrassment’ is actually not a bug, but a feature.</p><blockquote>Early-stage companies must realize they are not in the business of <em>selling</em>, but rather in the business of <em>learning</em>.</blockquote><p>What happens in practice however is that right from the start, startups are highly focused on building the product and then doubling down on sales to start booking revenues as quickly as they can. Even those adopting a ‘lean’ approach, regard product validation as an inherent outcome of their development process. This approach often proves to be futile, because once you confuse the objective of learning with the objective of delivery, you will find yourself optimizing to two different, and often conflicting, target functions <em>at the same time.</em></p><p>Instead, early-stage companies need to realize that before they have a strong grasp on the market-product fit, they are not in the business of <em>selling</em>, but rather in the business of <em>learning</em>.</p><h4>#2— Stop Confusing Products with Experiments</h4><p>To recall, the goal of a lean startup is <em>validated learning</em> and the way of reaching that goal is via a set of <em>experiments.</em> Ries claims that ‘An Experiment is a Product’, but for the first stage of the company, I would actually suggest the reverse of words — ‘A Product is an Experiment’.</p><p>What I mean by that is that if what you’re producing is validated learning, then your entire planning needs to be focused on building experiments for the sole sake of learning, rather than building products for the sake of delivery to customers.</p><p>This approach has several non-conventional implications, that are rarely represented in the todays’ most startup’s processes and organization:</p><ul><li>Not all ‘outputs’ have to be in the form of a software; some of the best learning experiments Ries provides are actually marketing initiatives or UX mockups with no code behind.</li><li>Your ‘product team’ should include people with a diverge set of skills, such that they can cater to the multi-disciplinary nature of your experiments, including members from marketing, design and even psychology. I wrote about it in the past in more details <a href="https://uxdesign.cc/engineers-are-the-worst-product-manager-you-could-hire-38d918e3b819">here</a>.</li><li>Manage your experiments as part of your product roadmap; at early stages, it might be all what your roadmap is comprised of. As the company matures, that ratio between <em>deliverable features</em> and <em>experiments </em>is likely to become more balanced.</li></ul><h4>#3 — Just Because You’re Agile Doesn’t Mean You’re Lean</h4><p>Startups like to consider themselves as agile organizations; they change course quickly, deploy rapidly and respond fast to new situations and customers’ requests. These are all indeed key characteristics of a startup, but that doesn’t make them <em>lean.</em></p><p>Lean is not about moving fast, but about learning fast; still, many startups fail to internalize the full cycle of the Build-Measure-Learn loop and focus mostly on the build without spending too many thoughts cycles to the objectives of what they build.</p><blockquote>If you’re heading towards a chasm, you might want to slow down a little.</blockquote><p>In his book, Ries often advocates against the “let’s ship a product and see what happen”, suggesting that if this is your plan, you are 100% guaranteed to succeed in that that you will see what happens. Without a framework of reference, however, this will give very little value. Building things fast, tagging things as ‘experimental’ as an excuse for low quality, and shipping features with no real feedback loop attached to them may all guarantee you move fast, but they don’t assure your’e moving in the right direction.</p><p>And honestly, if you’re heading towards a chasm, you might want to slow down a little.</p><h4>#4 — Allow Yourself To Be Wrong</h4><p>Karl Popper, the famous 20th century science philosopher, has coined the term f<em>alsifiability </em>to describe the key criteria that makes a theory be considered as <em>scientific</em>. A theory is falsifiable<em> (</em>and hence scientific) if there exists an experiment that can produce results that will make the theory false. (in other words, a theory is considered true, just as long as it withstands that test).</p><p>Ries, who draws much of his approach from the corpse of science, supports the same notion as part of his view on testing a hypothesis. If our experiment cannot produce a result that will refute our hypothesis, how would we even know we’re on the right path.</p><p>Let’s consider a simple example. Suppose we are looking to add to our product a certain option to automate a key of tasks that otherwise require the manual effort of a user. We are thinking to add a checkbox for users to state their preference; however, we are not sure whether that box should be checked by default.</p><p>Suppose that we decide to have it checked, and the majority of the users keep it intact, can we know for sure that it is because they are interested in this feature? maybe they just <em>don’t care </em>(or maybe didn’t even notice it exists). If it’s the latter, that would be a poor signal to follow up on and expand the feature. If, on the other hand, the box is unchecked by default, users will explicitly be required to check the box in, proving a clear signal of validation for the feature. Even a better approach might be to force users to make the explicit decision, by popping up a window they have to go through and set their choice. Consider how in both cases, we are driven by soliciting feedback, and not necessarily by optimizing the user experience or doing “what’s best” for our product goals.</p><p>Contrast that with the conventional thinking that is likely to suggest the box should be checked by default, as we want to encourage users to use our new feature. Such approach may improve our (vanity) metrics, but is more of a manipulation than a validated learning exercise. If you don’t allow f<em>alsifiability </em>to your design, you can’t expect to get a real feedback.</p><h4>#5 — Knowing When You Reached ‘<em>Minimum’</em></h4><p>Let us now turn now to the last, and possibly most acute, abused practice of The Lean Startup— the Minimum Viable Product. To recall, Ries defines MVP as “that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort”. Sadly, in so many observed cases MVP has taken the shape of “that pretty crappy, but not entirely terrible, implementation that will take the team the least effort to build and will keep the product manager only somewhat frustrated”; in other words, it become synonymous to ‘quick and dirty’.</p><p>There’s a popular drawing by <a href="https://medium.com/u/3ccad081c81a">Henrik Kniberg</a> that captures that practice</p><figure><img alt="MVP, Not like this, like this!" src="https://cdn-images-1.medium.com/max/609/0*qo8L1eWgr6YD9EYH.jpg" /><figcaption>Source: Henrik Kniberg</figcaption></figure><p>While I agree that the upper side of the picture is a fair depiction of a wrong, but common, interpretation of an MVP, I actually in a disagreement with the bottom half too. The idea behind MVP is not the delivery of fully usable high-quality products to customers, through iterations of an expanding scope, as the picture might suggest. Rather, it is about developing the essential product to support our learning experience <em>and nothing else.</em> It doesn’t need to be complete, fully usable or of high quality. It mostly need not get in the way of what we’re trying to learn. That’s the true meaning of ‘minimum viable’, taking into account the two words that make the equation.</p><p>Expanding on our example from before, suppose that the product team contemplate two implementations of the feature:</p><p>(1) a single option that set automation as on or off at a system-level.</p><p>(2) 5 different sub-options, separated by the type of tasks they act upon, providing together a fine-granular control for the user.</p><p>The common application of MVP would likely to be option (1) as it is simpler and will take less time to build. Common, but wrong. If we build the system-level option, and most users choose not to use the feature, how can we tell whether it is because they are not interested , or is it merely because the granularity it provides is too coarse to be usable.</p><p>Given that specific hypothesis, option (1) turns out to actually be ‘<em>less than the minimum</em>’ to be considered <em>viable</em> to our learning objective. M<em>inimum</em> must be defined in the context of what we are aiming to validate; sometime it actually requires more effort than what our intuition may tell us.</p><h4>Wrap Up</h4><p>Hopefully I managed to put a limelight on some of the key pitfalls startups should avoid; The theory of lean may come across as a straightforward one, but in fact, some of its ideas are more evasive than seems. Paying attention to details is key. Unfortunately, so many startups, including those who speak the <em>lingo, </em>fail to fully internalize the theory to its full impact, resulting in taking the wrong course of action.</p><p>Having said that, the common misuse of The Lean Startup is only half of the problem; the other half unfortunately lies within the theory itself. Despite being revolutionary in many ways, it is not without its flaws and shortcoming, In my next post, I will revisit the theory, this time from a more critical point of view.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b718629064b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/5-things-product-teams-get-wrong-about-the-lean-startup-2b718629064b">5 Things Product Teams Get Wrong About the Lean Startup</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Key Concepts of The Lean Startup]]></title>
            <link>https://beeblebrux.medium.com/5-key-concepts-of-the-lean-startup-5b192da96848?source=rss-a902ae8caca0------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b192da96848</guid>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Asaf Atzmon]]></dc:creator>
            <pubDate>Wed, 30 Dec 2020 21:36:22 GMT</pubDate>
            <atom:updated>2020-12-31T11:01:11.032Z</atom:updated>
            <content:encoded><![CDATA[<h4>The Lean Startup</h4><h4>An introductory guide to The Lean Startup business theory as the influential book is reaching its 10th anniversary</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NeQs5Ipk0dvXayZ9" /><figcaption>Photo by <a href="https://unsplash.com/@andreamaraldg?utm_source=medium&amp;utm_medium=referral">Andre A. Xavier</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><a href="http://theleanstartup.com/">The Lean Startup</a> by <a href="https://medium.com/u/d2f31bf094c6">Eric Ries</a> is approaching its 10th anniversary; published in September 2011, the book has been a tremendous success, selling over 1 million copies. The book has gave birth, or at the minimum popularized, terms, concepts and methodologies that have become the cornerstone of the day-to-day conducts of startups. Specifically, the term Minimum Viable Product (MVP), which is associated with Ries, has become one of the most popular terms governing discussions of innovation and early-stage execution. The charts below, taken from <a href="https://trends.google.com/">Google Trends</a>, demonstrate both how the book is compared with two other classic books in the literature of innovation, as well as the popularity of the MVP term compared to other ‘competing’ terms.</p><p>As can be seen, even nearly a decade after, The Lean Startup maintain its ‘hall of fame’ position:</p><figure><img alt="Google Trends comparing The Lean Startup book against Crossing the Chasm and The Innovator’s Dilemma" src="https://cdn-images-1.medium.com/max/1024/1*uIms5ZQAXnz8PnKudjKCCA.png" /><figcaption>Source: Google Trends</figcaption></figure><p><em>Google Trends analysis </em><a href="https://trends.google.com/trends/explore?date=2010-11-28%202020-12-28&amp;geo=US&amp;q=%2Fm%2F0k8vprd,%2Fm%2F01kbjz,%2Fm%2F04w76tz"><em>comparing 3 books</em></a><em>: The Lean Startup / Ries (blue), Crossing The Chasm / Moore (red) and The Innovators’ Dilemma / Christensen (yellow) over 2010–2020 time period.</em></p><figure><img alt="Google Trends comparing the term MVP with the terms agile and devops" src="https://cdn-images-1.medium.com/max/1024/1*OdP5o1jCKHQxlpGv31OfqA.png" /><figcaption>Source: Google Trends</figcaption></figure><p><em>Google Trends analysis </em><a href="https://trends.google.com/trends/explore?date=2010-11-28%202020-12-28&amp;geo=US&amp;q=mvp,agile,devops"><em>comparing the term MVP</em></a><em> (blue) with other competing terms: agile (red) and devops (yellow)</em></p><p>With its 10th anniversary on the horizon, it seemed like a good opportunity to revisit the book and to try and reflect how and to what extent the business theory has been used over the last decade.</p><p>I plan to cover it through a series of posts. This post will focus on introducing the key concepts of the book and the theory.</p><h3>Introduction to the Lean Startup</h3><p>The starting point of this book is with the assertion of the author, that the accumulative knowledge body that we have on management and management theories is ill-suited to serve startups and its in the root of the reason most of them fail. While startups may look similar to corporations from the outset, Ries argues, they are quite “a different beast”.</p><p>He then turns to define the term ‘startup’ as “a human institution designed to create a new product or service under conditions of extreme uncertainty”; this broad definition is deliberate in its attempt to include other kind of “constellations” that go beyond our conventional thinking of a startup, such as NGOs or “skunk work teams” within larger cooperations.</p><p>Ries attempts to deliver a new theory of entrepreneurial management, which is rooted in the history of the <a href="https://en.wikipedia.org/wiki/Lean_manufacturing">lean manufacturing</a> movement brought to fame by the <a href="https://en.wikipedia.org/wiki/Toyota_Production_System">Toyota Production System</a>, only that in Ries’ case the focus is on the intangible product which is software, rather than on the hardcore production of parts and goods.</p><blockquote>A Startup is a human institution designed to create a new product or service under conditions of extreme uncertainty.</blockquote><p>The focus of the book is on building a product, and on the framework to optimize it with the objective to reach a market-product fit and growth, but it is given in the context of a broader framework that includes elements of Vision and Strategy, as depicted in the triangle below.</p><p>The <em>vision</em> is the “north start” of the startup which rarely changes. The <em>strategy</em> is what you employ to reach the vision, including the business plan, product roadmap etc. A strategy may change (i.e. the pivot) when it fails to deliver a product that (even following many iterations) do not produce growth. The <em>product</em>, the focus of the book, is what undergoes the entrepreneurial management process in order to generate growth.</p><figure><img alt="Product. Strategy. Vision triangle." src="https://cdn-images-1.medium.com/max/421/0*UJ4l-DW9xONgYDVe.png" /><figcaption>Source: The Lean Startup / Eric Ries</figcaption></figure><p>The Vision-Strategy-Product triangle may seem synonymous with <a href="https://www.smartinsights.com/digital-marketing-strategy/online-value-proposition/start-with-why-creating-a-value-proposition-with-the-golden-circle-model/">Simon Sinek’s Golden Triangle</a> of Why (Vision), How (Strategy) and What (Product). The main focus of the book, then, is on the ‘What’.</p><p>The Lean Startup is a broad theory of management and I will surely do it injustice by trying to condense it into a single medium post, but I do want to highlight, what I consider to be, the five most important points of the theory:</p><figure><img alt="lean manufacturing" src="https://cdn-images-1.medium.com/max/1024/0*pE7yL9Ep3NEbZ7nI" /><figcaption>Photo by <a href="https://unsplash.com/@clayton_cardinalli?utm_source=medium&amp;utm_medium=referral">Clayton Cardinalli</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>#1 — What Does A Startup Produce</h4><p>Considering a theory of management which is modeled on a systematic approach to production, one should ask <strong>what it is that a startup produces</strong>.</p><p>Intuitively, we would want to answer that a software company produces software products. A financial standpoint might suggests that what it produces is value to investors; still a marketing mindset will claim that it produces value to customers.</p><p>Ries rejects all those answers. To his method, what a startup produces is <em>validated learning</em>. In other words, under conditions of extreme uncertainty it is unrealistically to focus on the traditional metrics of value and success. Instead, a startup must regards itself as a learning organization and the outcome of the learning is to validate its hypothesis about value and growth, as defined by its strategy.</p><h4>#2 — A Pair Of Hypothesis</h4><p>A product strategy must poses an hypothesis, namely the assumptions that the learning is looking to validate. According to Ries, there are two such hypothesis, <em>a</em> <em>value hypothesis</em> and <em>a</em> <em>growth hypothesis.</em></p><p>The value hypothesis tests “whether a product or service really delivers value to customers once they are using it”. In other words, it is a test for the market-product fit, which <a href="https://a16z.com/2017/02/18/12-things-about-product-market-fit/">is described by Andreessen</a> as when “the market pulls product out of the startup”. Every strategy should try to answer why would users use the product in the first place, and one of the things The Lean Startup provides is a scientific method to answer that question.</p><p>The growth hypothesis tests “how new customers will discover a product or service”; that is, it focuses on the engines by which the product will pull customers in, whether that is through viral growth, paid marketing or otherwise. This hypothesis is just as important as the <em>value</em> one, for one, because it allows us to protect ourselves against <a href="https://en.wikipedia.org/wiki/Crossing_the_Chasm">the known chasm</a> of going beyond your cohort of early adaptors.</p><h4>#3 — The Build-Measure-Learn Loop</h4><p>Given a basic concept of the Startup ‘product’’ (validated learning) and its validation criteria (hypothesis) , the theory turns to define how these can be achieved through the build-measure-learn loop. <strong>The build-measure-learn loop is probably the biggest innovation of the book, and its most used tool in practice.</strong></p><p>While the implementation sequence of the loop is as its name may suggest, the way you plan a feedback loop is actually reversed:</p><p><em>Learn</em> — what does the startup try to learn in a given iteration of the product, related to its value or growth hypothesis. For example, are users interested in a certain feature (<em>value</em>), will people pay for a certain service (<em>value</em>), will users invite their friends to join the product (<em>growth</em>) etc.</p><p><em>Measure — </em>what is the data to support that learning and how to collect and measure it. Ries goes at length on how to go about measuring and how to keep away from what he calls ‘vanity metrics’; this practice is referred to as ‘innovation accounting’.</p><p><em>Build</em> — what is the product or experiment the startup needs to build and launch in order to test the hypothesis. This is where Ries introduces the term ‘Minimum Viable Product’ (MVP), likely the most known topic associated with the theory. An MVP is defined as “ that version of a new product which allows a team to collect the maximum amount of <a href="http://startuplessonslearned.blogspot.com/2009/04/validated-learning-about-customers.html">validated learning about customers</a> with the least effort”. So in other words, the focus of MVP is not about quality or usability, but solely about the learning objective. What doesn’t support the learning is waste and should be thrown out.</p><blockquote>An MVP is defined as “ that version of a new product which allows a team to collect the maximum amount of <a href="http://startuplessonslearned.blogspot.com/2009/04/validated-learning-about-customers.html">validated learning about customers</a> with the least effort”.</blockquote><h4>#4 — Innovation Accounting</h4><p>Part of the build-measure-plan loop is indeed <em>measuring</em>, but in practice it is not a simple task and if done in the wrong way can yield to misleading results, or in Ries’s language, to ‘vanity metrics’. For example, simply measuring the total number of users an application has will hide critical data points, such as how much of that growth stems from the engines of early iterations as opposed to what is driven from new ones. In other words, how much of this growth can be actually attributed to new changes made in the product (out of a new BML loop). This is a dangerous opacity that could hinder a long-term view by creating blind spots to engines of growth that may in fact be dwindling down without us noticing it before it is already too late.</p><p>Instead, Ries suggests a method he calls ‘innovation accounting’ which he defines as ‘a quantitative approach that allows us to see whether our engine-tuning efforts are bearing fruits’.</p><p>At the core of ‘innovation accounting’ are two key principles:</p><ol><li>Identify what is your engine of growth: sticky, viral or paid (personally I think there are more than three, but hey … that was 2007); this will allow one to define the right metrics to track.</li><li>Measure it using ‘cohort analysis’ which allows mapping the data with the iterations of the product and to clearly identify the causality chain between the experiments and their contribution (or lack of) to growth.</li></ol><h4>#5 — Pivot Or Persevere</h4><p>Lastly, there are cases where engines stop growing even after significant number of product iterations (as a side-note, Ries suggests to define a startup runway by the # of iterations left at its disposal before it runs out of money).</p><p>When engines begin to run out of fuel, it might be the time to consider <em>pivoting</em>, that is, making a change to the company’s strategy. Part of the innovation accounting, described earlier, is the notion of building a ‘learning milestone’, a recurring meeting following every so and so iterations, where the team decides whether the metrics justify a pivot or only a sustaining effort to ‘tune up the engines’ (persevere).</p><p>Pivots don’t have to look like turning <a href="https://www.theatlantic.com/technology/archive/2014/07/instagram-used-to-be-called-brbn/373815/">a bar check-in app into a photo sharing services</a> or <a href="https://mashable.com/article/slack-glitch/">a game company into an organization messaging app</a>; pivots could, and often are, more subtle (“changing course with one foot anchored to the ground”). In practice, Ries gives over 10 different types of pivot, like a decision to focus on one feature of the original app (‘zoom-in’) or targeting a different type of user (‘customer segment’) as a strategy to ‘leap over the chasm’ and reach beyond the early adaptors.</p><p>Once a pivot is taken, the strategy is changed and adapted, leading way to a new set of value and growth hypothesis, and to new cycles of Build-Measure-Learn iterations that further tune the engine and grow the company.</p><h3>Summary</h3><p>The Lean Startup is a comprehensive theory and one of the more profound studies I came across about life and death of startups; there are other topics in the book, that I didn’t have the time to cover, such as the use of small batches, the Lean Startup Kanban board, the principles of continuous development and others. <br><strong>If you haven’t yet, you should definitely read the full book.</strong></p><p>In the introduction to the book, Ries highlights the failure of startups, beginning with his own account of his first failure as an entrepreneur. One of the sections carry the title “Why Startup Fails”. It would have been comforting to think that following the success of the book and the emergence of the lean movement and with so much popularity to the CI/CD and MVP methodologies it helped foster, that the failure rate of startups would decrease.</p><p>Sadly, this is hardly the case, and why it is such will be the topic of my next post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b192da96848" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nostalgia by design]]></title>
            <link>https://uxdesign.cc/nostalgia-by-design-e5d7bff17579?source=rss-a902ae8caca0------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5d7bff17579</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Asaf Atzmon]]></dc:creator>
            <pubDate>Sat, 12 Dec 2020 19:43:04 GMT</pubDate>
            <atom:updated>2020-12-14T19:26:29.071Z</atom:updated>
            <content:encoded><![CDATA[<h4>Product Design</h4><h4>How successful companies embody nostalgia into their product design and philosophy.</h4><figure><img alt="Vinyl records on a street cart" src="https://cdn-images-1.medium.com/max/1024/1*DPF3hs--0sPJTX3Ydd5Kuw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@pascalwhoop?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Pascal Brokmeier</a> on <a href="https://unsplash.com/s/photos/nostalgia?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><blockquote>Remember the days of the old schoolyard<br>We used to laugh a lot, oh don’t you?<br>Remember the days of the old schoolyard<br>When we had imaginings and we had<br>All kinds of things and we laughed<br>And needed love, yes, I do<br>Oh and I remember you<br><strong><em>Remember the Days / Cat Stevens</em></strong></blockquote><p>Nostalgia is a powerful emotion. We all have our moments of reflecting fondly on the past, and how things used to be so much better (or at the minimum ‘simpler’). <a href="https://en.wikipedia.org/wiki/Nostalgia">Wikipedia defines it</a> as a sentiment associated with a yearning for the past, its personalities, possibilities, and events, especially the “good old days” or a “warm childhood”.</p><p>Interestingly enough, that positive association wasn’t always the definition of Nostalgia. In fact, its origins are rooted in melancholy and malady. Coined in the 17th century, it used to describe a feeling of “homesickness” exhibited by European mercenaries that were deployed far away from home.</p><p>The word itself is a a fusion of two Greek words — <em>nostos</em> (homecoming) and <em>algos</em> (pain). At some point, through some modern developments, it has changed its meaning to embrace the positive reflection of past memories and experiences.</p><p>Psychologists and neurologists can scientifically map the recollection of pleasant past events with <a href="https://www.neurologylive.com/view/brain-and-nostalgia">the reward systems of the brain</a>. A certain smell, a certain touch, a song or a book can all trigger metabolic activity and blood flow in several regions of the brain associated with our reward system, which explain the feeling of warmth we may feel to say, the sound of a popular song from the 80s, even for one that we didn’t much like back then.</p><h4>Nostalgia in Product Design</h4><blockquote>Once upon a time there was a tavern<br>Where we used to raise a glass or two<br>Remember how we laughed away the hours<br>And dreamed of all the great things we would do<br><strong><em>Those Were The Days / Mary Hopkin</em></strong></blockquote><p>Given its powerful effect in evoking emotions, product designers have been using nostalgia as a tool and a technique to create attachments to their products. <a href="https://medium.com/u/c2146664c8e4">Ryan Hoover</a>, the co-author of Hooked <a href="https://www.nirandfar.com/nostalgia-a-product-designers-secret-weapon/">has uncovered this “secret weapon”</a> before in some successful products. While his examples are now somewhat dated, other cases in points are presented to us on a daily basis; just consider Google Photos <a href="https://techcrunch.com/2015/08/20/google-photos-introduces-rediscover-this-day-to-help-you-reminisce/">“Rediscover this day”</a> or Spotify <a href="https://2020.byspotify.com/">“Year in Review”</a> as two notable examples.</p><p>Reminiscence is one way to trigger nostalgia; retro and vintage is another. We tend to look fondly at objects, fashions and certain types of behavior that remind us of a “lost paradise”, something that was swept away by the waves of technology and that to which we urge as a sign to a world that once was simpler and better.</p><p>Naturally, to a large extent, this feeling is false and illusionary. There’s nothing objectively better about a telephone booth or a VW beetle, other than that feeling of nostalgia they bring about in the face of whatever detachment modern lives impose on us. That doesn’t mean however, that the impact of our encounters with them is any less real. And so it follows, that recreating such nostalgic experiences in digital products through styling of vintage or modeling of long-gone behaviors can produce positive attachment to a product.</p><p>Here are few examples of successful products that have embodied such nostalgic elements in their design or product philosophy:</p><h4>Pinterest</h4><figure><img alt="A teenager pinboard" src="https://cdn-images-1.medium.com/max/615/1*oju9cqne_941oB-LoiSa0Q.jpeg" /><figcaption>Source: <a href="https://www.hellowonderful.co/">https://www.hellowonderful.co/</a></figcaption></figure><p>The image sharing and collection platform, <a href="http://www.pinterest.com/">Pinterest</a>, draws its name from the metaphor of the pinboard which every room of every teenager in every American film seem to have. In fact, the association of Pinterest is broader and can be applied to almost every past experience of collecting, whether these are stamps, rocks or newspaper clips. Founder, Ben Silbermann, has had the memory of his childhood bug collection when he went to design the <a href="https://www.businessinsider.com/pinterest-founding-story-2012-4">first version of the product</a>.</p><h4>Instagram</h4><figure><img alt="Polaroid camera" src="https://cdn-images-1.medium.com/max/1024/0*43cc_Yy1_Pfs20MU" /><figcaption>Photo by <a href="https://unsplash.com/@lorenzospoleti?utm_source=medium&amp;utm_medium=referral">Lorenzo Spoleti</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>When Kevin Systrom and Mike Krieger <a href="https://www.investopedia.com/articles/investing/102615/story-instagram-rise-1-photo0sharing-app.asp">pivoted from the Burbn app into what turned to be Instagram</a>, they considered their biggest rival to be <a href="http://hipstamatic.com/x/">Hipstamatic</a>, at the time a highly popular photos sharing app. What made Hipstamatic stand out was its deliberate <em>vintage</em> design and its appeal to photographers, by embodying <em>filters</em> that allowed photos taken on mobile devices to be given a <em>past quality</em> of what still considered to be real photography.</p><p>When famous photographer Damon Winter has <a href="https://lens.blogs.nytimes.com/2011/02/11/through-my-eye-not-hipstamatics/">published professional photography</a> at the NYTimes, using Hipstamatic, it was a vote of confidence to this fusion of the old and the new. Just as powerful was the engagement it drawn from photo enthusiastic all over the world, who embraced the filters feature as a way to give touch to their mobile photos on a wide range of styles, including the “crappy low-quality” but memorable Polaroid days.</p><p>Hipstamatic exists to this day, but lacking strong social sharing features it left the battlefield unguarded for Instagram, who snatched their filters feature and made its way to be acquired by Facebook for $1Bn. Unfortunately, along their way of success they seemed to depart of the nostalgic design that contributed to their early days’ attraction.</p><h4>Suan</h4><p><a href="https://suan.fm/">Suan.fm</a>, which stands for “Stayed Up All Night” might be a niche compared to the examples above but it’s a great example of the use of nostalgia in product philosophy and design. The website recreates the lost experience of composing a mixtape on a cassette and sharing it with friends. It does it by giving a special care for visual details to the level of mimicking the sloppy handwriting of song names on a design of an old cassette. It also allows you to choose from a set of old cassette designs and customize the end product with eighties’ like doodles and stickers.</p><figure><img alt="Suan.fm casette style" src="https://cdn-images-1.medium.com/max/400/1*NrxQl4BW6uE8dqiJXvj1yQ.jpeg" /><figcaption>Source: <a href="https://netdiver.net/">https://netdiver.net/</a></figcaption></figure><blockquote>And I wish it was the sixties<br>I wish I could be happy<br>I wish, I wish<br>I wish that something would happen<br><strong><em>The Bends / Radiohead</em></strong></blockquote><h4>Flipboard</h4><figure><img alt="A shelf full of magazines" src="https://cdn-images-1.medium.com/max/1024/0*w9wnOd4OUYXuhf8z" /><figcaption>Photo by <a href="https://unsplash.com/@charissek?utm_source=medium&amp;utm_medium=referral">Charisse Kenion</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Pinterest, Instagram and Suan.fm all aim to drive user engagement by creating a retro or vintage design that evoke those nostalgic feeling to objects and forms of design that connect us to different (and subjectively better) parts of our life.</p><p>Flipboard is somewhat different in that it plays less so on the emotional side of things, and instead attempts to digitally recreate a user experience around journalism that has seemed to die with the move to online.</p><p>By aggregating news articles from across the internet and reformatting it into a magazine layout, it was one of the first applications designed specifically for the launch of the iPad, but what made it interesting is in the way it molded an old format to a new form factor, making way to the creation of over 30 millions magazines.</p><h4>Snapchat</h4><p>Given Snapchat’s target demographic of millennials and Z-gens, its inclusion here might seem dubious at first, but it’s worthwhile to recall its history and original motivation.</p><p>Snapchat early success has been attributed to the growing concerns of then social media users, especially young generations, who were afraid that the images they share will “come back to haunt them”. Snapchat’s key feature of “self-destructive” sharing fitted neatly into that space.</p><p>In an 2013 interview to <em>The Telegraph, </em>Snapchat’s founde<em>r</em>, Even Spiegel, explained how their design and product choices connected with the motivation to bring back a social experience that seemed to be diminishing:</p><blockquote>“What Snapchat said was if we try to model conversations as they occur they’re largely ephemeral. We may try to write down and save the really special moments, but by and large, we just try to let everything go. We remember it but we don’t try to save it”</blockquote><h4>Podcasts</h4><figure><img alt="Radio Stereo System" src="https://cdn-images-1.medium.com/max/1024/0*hgLO2D8GT429MuyJ" /><figcaption>Photo by <a href="https://unsplash.com/@leowieling?utm_source=medium&amp;utm_medium=referral">Leo Wieling</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>We had joy, we had fun<br>We had seasons in the sun<br>But the hills that we climbed<br>Were just seasons out of time<br><strong><em>Seasons in the Sun / Terry Jacks</em></strong></blockquote><p>My last example is not of a specific app but rather a new medium, namely <em>Podcasting</em>. The success and growth of podcasting has been nothing short of phenomenal, with over 1,500,000 shows out there <a href="https://www.podcastinsights.com/podcast-statistics/">according to a recent stat</a>.</p><p>In many ways, the success of podcasts is an antidote to the superfluous and “faceless” popularization of social media, and it’s one of the emerging positive trends toward media that is based more on <a href="https://ev.medium.com/toward-a-more-relational-medium-e801ff4653a4">relations rather than transactions</a>. Noble, but not new. Many characteristics of the podcast resemble in nature the days of the Radio Drama, which was a highly popular form of entertainment at the birth of modern radio of the 20th century until its gradual demise through the 70s. Now it’s making a comeback both as the content of some shows as well as by inspiring the production of podcasts overall.</p><p>Our world is changing at an accelerating pace; our biology not as much. This widening gap between what we can achieve technologically and what we can cope with as social animals is likely to create a dissonance in our interfacing with the digital products around us. Nostalgia is one such feeling that can bridge that gap, by bringing a sense of warmth and connection to an otherwise potentially cold and estranged experience. Product designers can use these principles to turn their products not only to objects of desire but also of homecoming.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*MHkxrsOPckHzu0KA" /><figcaption>The UX Collective donates US$1 for each article published on our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5d7bff17579" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/nostalgia-by-design-e5d7bff17579">Nostalgia by design</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build customer loyalty using the companion model]]></title>
            <link>https://uxdesign.cc/how-to-build-customer-loyalty-using-the-companion-model-d31408458bc8?source=rss-a902ae8caca0------2</link>
            <guid isPermaLink="false">https://medium.com/p/d31408458bc8</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[Asaf Atzmon]]></dc:creator>
            <pubDate>Tue, 01 Dec 2020 12:10:38 GMT</pubDate>
            <atom:updated>2020-12-01T12:10:38.379Z</atom:updated>
            <content:encoded><![CDATA[<h4>Digitally enhancing our support network as a key to meaningful interactions.</h4><figure><img alt="One person reaching out to another" src="https://cdn-images-1.medium.com/max/1024/1*rp5DraR87eGEok5RNryt-A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@heftiba?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Toa Heftiba</a> on <a href="https://unsplash.com/s/photos/support?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong>We go about our lives as consumers making transactions. </strong>Think of the last time you bought a pizza slice or a pair of shoes. A brief engagement with the merchant at the point-of-sale and an exchange of money for value. Transactions are transient and ephemeral; the value you pay for is provided then and there. Whether you will return in the future to the pizza parlor or shoes’ store, depends just as much on factors of chance and circumstances as it depends on your satisfaction with the product.</p><p>Sellers don’t like much a transaction-model as they prefer to have more control over the process than rely on the caprice of the customer. This is why loyalty programs exist as a means to keep the merchant in the consumers’ mind and a vehicle to feed him constantly with incentives to buy, by offering a <a href="https://blog.startwithwhy.com/refocus/2007/02/manipulation_vs.html">stream of price manipulations</a> typically in the form of discounts. Given that sustaining an existing customer is generally cheaper than acquiring a new one, ‘loyalty programs’ and ‘customer relationship management’ are conceived as key elements in a transaction-driven world.</p><p>Given the challenges of retaining customers, many businesses attempt at moving to a subscription model. This is clearly apparent in the world of digital, with Netflix as the notable exemplar, but it is becoming relevant in traditional ‘brick-and-mortar’ businesses as well. For example, where I live in Israel, I pay a subscription fee to a coffee distributor named <a href="https://beanzcafe.co.il/">Beanz</a> which provides me with coffee beans on a monthly basis; I do this to save myself from buying the coffee machine (which is provided to me for free as long as I pay for the service) and of the mental burden to remember to keep my supply of beans. Until recently I used to do the same with my wine. Similar businesses exist today for <a href="https://www.renttherunway.com/">clothes</a>, <a href="https://www.blueapron.com/">meals</a>, <a href="https://sampler.io/">niche merchandise</a> etc..</p><p>While a subscription-model seems highly attractive from a revenue stream standpoint, it may suffer from a similar lack of customer loyalty as with the transactional model. Given that consumers recurrently pay for the service, they tend to continuously question the value and Return of Investment (ROI) of what they are paying for. For example, they may question whether the monthly delivery of a six-pack wine box worth the overhead in price, the loss of choice or even the giving up of the personal experience of choosing the wine. In other cases, especially when demand fluctuates rather than being consistent, they could feel like they are over-paying to something they are not really using. As an example, “Rent The Runway” pioneered the designers clothing rental service some 10 years ago; today you can <a href="https://www.mysubscriptionaddiction.com/best-clothing-subscription-boxes">easily find many competing services</a>. Like with transactions, services tend to get commoditized and become utilities over time, and customers’ loyalty remains evasive.</p><blockquote>Like with transactions, services tend to get commoditized and become utilities over time, and customers’ loyalty remains evasive.</blockquote><h4>Building Meaning In Our Day-to-Day Life</h4><p>Let us turn now to look at how we govern our regular actions in our day-to-day lives; interestingly they are not that different from our behavior as consumers. Many of our engagements with the surrounding are <em>transactional</em> in nature; we may politely nod a stranger that crosses our way during a hike, or we may greet the cashier at the supermarket line. In other cases, we might engage in a longer chit-chat with another dad while picking up our child. In all these cases, there’s a brief and ephemeral exchange of “value” which might be paid with the currency of politeness, societal citizenship or some rudimentary level of superficial connection.</p><p>Of course, conversations and engagements can, and sometimes do, go deeper than that. We all have our networks of colleagues, friends and relatives at different levels of relationship and bonding, but overall they take the smaller portion of our time. They much more resemble the house that we buy once or twice in our lives then the occasional purchase of a pair of socks. Similarly, we have a network of people we “subscribe” to; it can be the housemaid, a physician or the babysitter; and like with subscription goods, we may engage them for a period of time but we just as easily may switch to others, or cut them off completely if we feel we’re not getting the value we expect.</p><p>In some cases we do seem however to strike deeper bonds with people, demonstrating a higher level of loyalty. Consider your family doctor, or your therapist, if you have one, and the depth and longevity of the connection you have with them. <a href="https://www.brookings.edu/blog/future-development/2018/09/27/a-global-tipping-point-half-the-world-is-now-middle-class-or-wealthier/">As society becomes richer</a> and dispensable income grows in larger parts of the world, we tend to spend a significant share of our savings on all sort of such <strong>companions</strong> — a personal fitness tutor, a mentor, a private teacher, a healer, a resident cook. In a world that becomes more and more chaotic and disorienting, we seem to work harder, sacrifice more of our personal time, and spend whatever extra income we get on a support network to serve us with the needs we seemed to have relinquished in the first place.</p><p>We have moved into the city, and we are now outsourcing <em>the village.</em></p><blockquote>In a world that becomes more and more chaotic and disorienting, we seem to work harder, sacrifice more of our personal time, and spend whatever extra income we get on a support network to serve us with the needs we seemed to have relinquished in the first place.</blockquote><p>Weighing in the benefits of this concise choice of craziness is likely to be the subject of a different post, but the important role this support network plays in out life is indisputable. Often, we look at these companions as an extension to ourselves and as an ecosystem that helps is in reaching our goals. It is also why we tend to put a high barrier of entry for accommodating a new one into our network. If you do have a fitness instructor, a therapist, a mentor or an educator, you likely spent a lot of effort to find “the right one” to meet whatever high standards you set for; similarly, the more you are engaged in a relationship, the more value that is created within it and the harder it is to switch to someone else. Whether it’s your physical, mental, behavioral or dietary account, companions learn you over time, adapt to your need, personalize their offer and create a mutual history that can’t be simply detached.</p><p>In other words, when it works well,<em> it is a loyal and meaningful engagement</em>.</p><h4>Software Can Be Your Companion</h4><p>Given the strength of the companion model to build a long-lasting loyal relationship, it is clear why creating a digital equivalent could be highly lucrative. I previously discussed how the shift to cloud computing and the emergence of SaaS allowed the evolution of <a href="https://beeblebrux.medium.com/what-i-talk-about-when-i-talk-about-software-products-a7f5da95d1b0">software as a streaming service</a>. Indeed, SaaS lends itself to a new kind of sales where conversion funnels, traditionally concluded at a ‘commit’ milestone (i.e. the transaction) are now <a href="https://winningbydesign.com/the-saas-sales-method/">carried-on well into the lifetime of the provided service</a>. Many SaaS companies recover their customer acquisition cost (CAS) more than a year after a customer has started paying. It is a symbiotic exchange of value where the customer constantly re-evaluates her purchase decision and expects the value to be delivered continuously to her, and not merely at the point-of-sale.</p><p><em>In many ways,</em> <em>SaaS looks much more like a partnership, then like selling</em>.</p><p>Within this challenging environment, companies that do manage to position their offering in a ‘companion model’ are likely to incur less churn and by striking a partnership with their customers which is rooted on meaningful connection rather than a manipulative exchange of value can create a quick ROI and a higher LTV.</p><p>To explain what I mean by the ‘companion model’ here are two examples:</p><h4>Masterclass</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oM4I-yFeP4PF3nSQL8Hx4A.png" /><figcaption>Source: masterclass.com</figcaption></figure><p><a href="https://medium.com/the-atlantic/what-is-masterclass-actually-selling-634940cbadfd">At the junction of education and entertainmen</a>t, masterclass.com is a brilliant service that provide classes from all life’s aspects, for education and inspiration, <em>straight from the horse’s mouth </em>(or in their case, a long list of experts/celebs from Steph Curry to Margaret Atwood). Masterclass feeds on the needs of an educated cohort that is too busy working but feel guilty about self-inflicted starvation of their intellectual world. Apparently, <a href="https://techcrunch.com/2020/05/20/masterclass-just-raised-100-million-for-celebrity-fueled-content/">there are quite a few of those</a>. With so many distractions around us —social media, smartphones, video games, and almighty Netflix — Masterclass stands out as an exception we are actually willing to invest for our own good karma. Signing-up is not cheap; at a $180 annual subscription, most people will consider this a significant expense. This is by design; the message here is “we are looking for your commitment”, and it is fascinating to observe the growth of this service, albeit so many free or low-cost alternatives. Masterclass is different because it is structured in a way that forms a committing relationship; it’s akin to saying “show me you’re serious and I will make sure to keep your intellect in shape by feeding you content from the best educators in the world”. It’s a companion to your intellectual life.</p><h4>Peloton</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v7PVW3vgTsm6Dtl--xhhoA.png" /><figcaption>source: peloton.com</figcaption></figure><p>What Masterclass is for the brain, Peloton is for the body. Not discounting the quality of the bike, but what makes Peloton brilliant is the experience they provide along with the gear by giving full access to live and on-demand classes and programs tailored to your needs. Like Masterclass (and unlike a lot of our conventional ‘freemium’ thinking), the barrier to get in is high. You will need to spend some $2000 just to get the bike or tread. Again, this asks the subscriber for a commitment, which in return is then being fulfilled by a service that provides the ‘companion effect’ — that personal tutor that accompanies you and follows and supports your progress throughout your fitness journey.</p><p>Both Masterclass and Peloton can afford to charge users high fees to play, since they are built on a promise which is expected to be delivered over a long period of time, and thus churn likelihood is reduced, at least in the short run. Likewise, there exist services such as <a href="https://www.talkspace.com/">Talkspace</a> and Betterhelp that build on a companion model for mental help (charging &gt;$200 / month), or similar applications to provide child care, private lessons, cooking etc. These services are more immune to the challenges of SaaS as they very quickly cover their CAC, but even more importantly, they have a better chance to build a strong customers’ loyalty as long as they don’t lose the ‘companion effect’. We are willing to pay a premium to what we conceive to be part of our support network, and services that play strong on the ‘human-factor’, by making us feel there’s someone else on the other side taking care of our needs and interests, are much more likely to get our vote and our dollars.</p><h4>COVID-19 is Accelerating Digital Companions</h4><figure><img alt="Man with mask and phone" src="https://cdn-images-1.medium.com/max/1024/1*K69HWpRK6R8C0A07X5ogLg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@enginakyurt?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">engin akyurt</a> on <a href="https://unsplash.com/s/photos/coronavirus?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Everything I discussed above seems to get further accelerated at the face of COVID-19; as we are being isolated socially and prevented access to large parts of our physical service network, we are much more likely to seek for ‘digital companions’ both <a href="https://www.vox.com/recode/2020/3/20/21185351/mental-health-apps-coronavirus-pandemic-anxiety">as ways to reduce our anxiety level </a>as well as in order to fill our unmet needs. This trajectory is likely to persist even after the virus is contained, as people and businesses alike are getting accustomed to <em>work from home</em> practices, and at least according to most opinions, society is not likely to open up so quickly or at the same levels. All this means good news for digital companions.</p><p>As we are bombarded by a plethora of digital services fighting for our attention and wallet, our loyalty turns low, scarce and highly-conditioned, but once gained, it is the most lucrative asset for long-term returns. Just like in real-life, loyalty is given when relationships are trustworthy and meaningful. Building digital services to the companion model, by putting the limelight on the customers’ need and positioning the app as part of the users’ support network, has the potential to recreate digital equivalent to what is becoming a resource on low-supply in a world hit by a pandemic. Companies that take advantage of this companion model, are likely to see future growth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*xWHSs75bOogJl8qS" /><figcaption>The UX Collective donates US$1 for each article published on our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d31408458bc8" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/how-to-build-customer-loyalty-using-the-companion-model-d31408458bc8">How to build customer loyalty using the companion model</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineers are the worst Product Manager you could hire]]></title>
            <link>https://uxdesign.cc/engineers-are-the-worst-product-manager-you-could-hire-38d918e3b819?source=rss-a902ae8caca0------2</link>
            <guid isPermaLink="false">https://medium.com/p/38d918e3b819</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Asaf Atzmon]]></dc:creator>
            <pubDate>Mon, 23 Nov 2020 13:53:12 GMT</pubDate>
            <atom:updated>2020-11-25T10:09:36.561Z</atom:updated>
            <content:encoded><![CDATA[<h3>Engineers are the worst Product Managers you could hire</h3><figure><img alt="Cover image: engeineering" src="https://cdn-images-1.medium.com/max/1024/0*X_Eib6MbJL0KAe3_.jpg" /></figure><p><strong>Ok … I’m going to piss some people off with this post</strong>; to make things worse, some of them are my close friends. Would it help if I start by saying that I, myself, am a software engineer that has practiced product management through large parts of my career?</p><p>Secondly, I’m sure to make some wild generalizations here which will do injustice to many great product managers who happen to have a background in engineering, but I’m trying to make a statement here, and you can’t make a statement without highlighting insights which are based on generalizations, and you can’t make these without potentially hurting some people down the way… so, I apologize for it.</p><p>Now that I got this out of my system, let me say it:</p><blockquote><strong>Hiring engineers to be Product Managers is one of the worst decisions you can make.</strong></blockquote><h3>Desirability, Feasibility, Viability</h3><p>There are many definitions of Products and Product Managers; to me, it all comes down to the fundamental objective of finding a Product-Market fit. One of the most common sets of attributes to capture it is what has been originally defined by IDEO as the <a href="https://www.ideou.com/blogs/inspiration/how-to-prototype-a-new-business">Desirability, Feasibility, Viability</a> trinity. While some may argue that this perspective focuses mostly on the innovation phase of a product, I am deeply convinced that this Innovation <em>is </em>the core of product management, and it’s a critical phase throughout the continuous lifecycle of a company, whether it is with coming up with a new product, or figuring out the next features to add to an existing one. Sure, there are other aspects of Product Management such as “rallying the troops”, “managing the backlog” etc. and while important, I regard them as lower-skill “product technicians” work, that is rarely the reason for a product to fail.</p><p>Coming back to the matter, we can follow <a href="https://medium.com/innovation-sweet-spot/desirability-feasibility-viability-the-sweet-spot-for-innovation-d7946de2183c">these definitions for DFV</a>:</p><ul><li>A <strong>desirable</strong> solution, one that your customer really needs</li><li>A <strong>feasible</strong> solution, building on the strengths of your current operational capabilities</li><li>A <strong>viable</strong> solution, with a sustainable business model.</li></ul><figure><img alt="Desireability, Feasibility, Viability" src="https://cdn-images-1.medium.com/max/640/1*IAYxGV2bujAjBBc2fClr0g.jpeg" /><figcaption>Source: IDEO</figcaption></figure><p>I believe there’s a reason behind the order of those three traits. You have to start with what the customer wants. This is the <em>outward look</em> and is the most critical aspect of the product work, thinking from the outside-in as I discussed in <a href="https://beeblebrux.medium.com/pushing-products-down-ones-throat-5e6cf171634c">a previous post</a>. The second pillar is focused on <em>looking inward</em>, to find the company’s assets, values, and mission that can put it in an advantageous position to be the one to build the desirable solution a win at the marketplace. Lastly, you have to figure out a collaboration model that works both for you and your customer. This is the <em>inward-outward look</em> that has to cater both for the value you bring and the value you capture back and to bridge between the two. I chose to use the term collaboration model rather than business model deliberately, as I believe it has to do more than with “how I make money of it”; it is about building a long-term sustainable relationship with your customer.</p><h3>The Product Superhero</h3><p>Mastering these three circles may seem like an impossible task that calls for a superhero figure; it’s no wonder that <a href="https://www.publicity.com/marketsmart-newsletters/percentage-new-products-fail">the majority of products fai</a>l to make it to commercial success. It might be worthwhile to try and consider what are the key things that we should look into in Product Management, keeping the DFV diagram in mind:</p><ol><li>Empathy — the holy grail of the <a href="https://www.interaction-design.org/literature/article/design-thinking-getting-started-with-empathy">design-thinking process</a> and the cornerstone for customers’ understanding.</li><li>Behavioral Studies — customers are human-beings; they are being driven by behaviors that are rooted in the anatomy of our brains. Understanding the mechanisms behind people’s choices has been proven as a <a href="https://www.nirandfar.com/hooked/">successful recipe to build desirable products</a>.</li><li>Incentives Theories — along psychology, figuring out the economic models that govern people’s choices is highly beneficial to reach products’ goals.</li><li>Storytelling and narration — as a civilization we are attracted by stories; products that tell a story create a better attachment with customers.</li><li>Strategy Thinking — scoping your “playing field”, identifying your arsenal and figuring out an attack-path help validating the feasibility of your company to win in the market field.</li><li>Analytics Skills — the ability to generate insight out of pure data.</li></ol><p>The list is not exhaustive; it could have included other relevant sources of knowledge and skills, such as design, <a href="https://uxdesign.cc/defecting-from-architecture-d7cdc2b517ad">architecture</a> and even <a href="https://uxdesign.cc/build-software-like-disneyland-cd4a694e6e6e">experiential marketing from the world of retail</a>, but i hope it makes the case of the rich and broad frame of consideration that must be applied into the role of Product Management.</p><h3>So why on Earth would you hire an Engineer?</h3><p>In writing this post, I did a simple search for ‘Product Manager’ in the Jobs section of LinkedIn. Regardless of the location or company type, almost every job posting had the following requirement (often as the first one):</p><blockquote>B.Sc in computer science or related discipline</blockquote><p>This concurs with my own personal experience; product management is often a phase in the career path of an engineer or software developer making his way to more customer-facing or business-oriented positions. It is not surprising given the fact that many of those companies themselves are run by engineers.</p><p>Why is that a problem? because engineering is all about finding a simple and effective solution to <em>a clearly identified problem</em>. Wikipedia defines it as <em>“the use of scientific principles to design and build machines, structures, and other items”. </em>It is, by nature, a narrow-minded focused practice, and it falls flat in its ability to solve complex unclear problems. <a href="https://www.ted.com/talks/dan_pink_the_puzzle_of_motivation">In its highly popular Ted talk</a>, Daniel Pink demonstrates how focused-thinking is ineffective in addressing “thinking out of the box” challenges such as <a href="https://en.wikipedia.org/wiki/Candle_problem">The Candle Problem</a>. But, in today’s highly accelerated complex environments, product-market fit challenges look much more like a candle problem than a schoolbook engineering one.</p><figure><img alt="The Candle Problem" src="https://cdn-images-1.medium.com/max/366/0*MgHagiVXeQtOlYK-.jpg" /><figcaption>Source: Duncker, Karl (1945) <em>On Problem Solving</em></figcaption></figure><p>Secondly, and I will risk generalizing here, but engineers often tend to be low on the EQ meter; definitely not the first option that comes in mind for exercising empathy. They are more comfortable with machines and well-defined and deterministic codes of behavior (such as in programming language, network protocols, and specifications) than with the irrational, incentive-driven “machine” which is the human-mind. They are more likely to be socially awkward, compared to people from many other backgrounds. I can safely say, that beyond the analytical trait, on average they fail miserably on almost all the measures I defined above.</p><h3>Unlock a Wealth of Talents</h3><p>We are missing out big-time, as we keep complaining on the lack of STEM studies to fill in a growing number of open positions, while at the same time, failing to attract pools of talent that can significantly upgrade our product performance.</p><p>Why not consider the following alternative job description:</p><blockquote>An early-stage company building an experience to disrupt the way &lt;<em>fill in the gap&gt;</em> is looking for a multi disciplinary talent to define and execute the customer experience.</blockquote><blockquote>Qualifications:</blockquote><blockquote>Ability to show empathy and deep customer understanding on emotional, psychological, economical, societal and functional levels</blockquote><blockquote>Ability to build narratives, create compelling stories and translate them into an immersive experience</blockquote><blockquote>Ability to think in strategic terms, identify a competitive landscape and build a winning route into the customers’ heart</blockquote><blockquote>Background in design, architecture, economy, psychology, screenwriting or any other discipline with high affinity to a requirements above</blockquote><p>Our world is becoming more complex; customers more sophisticated and problems more rich and deep in nature; unless we match it up with a rich and broader mindset to problem-solving, we can’t hope to remain innovative.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*CkfcHGR24hXpqGbJ" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38d918e3b819" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/engineers-are-the-worst-product-manager-you-could-hire-38d918e3b819">Engineers are the worst Product Manager you could hire</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ev Williams has it right; I know, because I did the same 10 years ago]]></title>
            <link>https://medium.com/swlh/ev-williams-has-it-right-i-know-because-i-did-the-same-10-years-ago-560d519c0ab5?source=rss-a902ae8caca0------2</link>
            <guid isPermaLink="false">https://medium.com/p/560d519c0ab5</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[music]]></category>
            <dc:creator><![CDATA[Asaf Atzmon]]></dc:creator>
            <pubDate>Thu, 19 Nov 2020 10:10:15 GMT</pubDate>
            <atom:updated>2020-11-19T13:00:16.216Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aSWWzw-efdFxDCUuUw9HoQ.jpeg" /><figcaption>serendip.me homepage (2012)</figcaption></figure><p>Medium, the publishing platform, has recently launched an overhaul of its application. Its founder, <a href="https://medium.com/u/268314bb7e7e">Ev Williams</a>, has written a post on the company’s blog, where he gives the rationale behind the change. <br>It is titled “<a href="https://ev.medium.com/toward-a-more-relational-medium-e801ff4653a4/">Toward a more relational Medium</a>”. He writes:</p><blockquote>“Among other ways, the internet has changed media consumption along a spectrum that you might call <em>relational</em> to <em>transactional</em>. Think of (or imagine, if you’re not old enough) when you got your morning newspaper or your favorite magazine and read articles <em>because they were in that newspaper or magazine</em>. Sure, you didn’t read all of them, but what you read was very heavily influenced by where it came from. <strong>You picked the source first and <em>then</em> you picked the articles.</strong> You built affinity and trust for the sources (publications) you liked best, which read to repeat reading and/or subscription. In other words, you had a <em>relationship</em> of sorts with them — and, perhaps, with many of the writers in them, as well.”</blockquote><p>Ev goes on and discusses how meaningful content emerges through relationship that are formed between people, and how Medium plans to optimize its user experience to bring into the spotlight the writers. When I read Ev’s post, it strike a chord with me as it touches upon a growing feeling I have with respect to what we might be losing in the world of transactional media. It immediately made me consider how Medium might be a place I could feel at home.</p><p>It also threw me back some 10 years ago, where I stared a company called Serendip, along with my friend, <a href="https://medium.com/u/4e2204cb4da3">Sagee Ben-Zedeff</a> .</p><h3>What really matters is what you like, not what you are like</h3><p>Sagee and I started Serendip in 2010 out of a shared nostalgia to an experience we fondly recalled from our childhood. Both avid music lovers, growing together in a small town in Israel in the 80s, one of our most vivid memories was around the discovery of a friend’s music taste. It would typically go like that — we would visit a friends’ home for the first time, and soon enough we would find ourselves scrolling through his CDs (or cassettes) collection, hunting for shared favorite artists and albums. Once a certain “click” clicked (given a good level of overlap, which wasn’t always the case), relationship would form. In other words, we have implicitly “collected” our friend to our list of sources; we would listen to a new album he discovered, we would exchange mixtapes with him; most importantly, we would constantly converse with him about our shared taste.</p><p>Serendip.me, the music service we have built, followed a similar experience. After a quick profiling of the user’s taste, the service would suggest her with DJ’s to follow. These followed DJs would comprised the network of music soulmates, the trusted sources, through which the music experience of the service was created. Music that was shared by those DJs (through social media, or directly on the app) fed into the playlist, and you could further drill down into a DJ’s profile page, follow, share and converse around it. <br>Some have called this “<a href="https://thenextweb.com/apps/2011/08/25/serendip-twitter-music-integration-done-right/">The Twitter of Music</a>”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i_93gRabVipuWoMmzTwMYQ.jpeg" /><figcaption>serendip.me</figcaption></figure><p>Serendip was a glorious commercial failure. I know today that you need many things to get right (and some luck too) to make a startup successful. <em>But we did get one thing right</em>. Our core intuitive understanding of the importance of people, as a way to establish trust and meaning.</p><p>In the great movie (and book) “High Fidelity” by Nick Hornby, there’s this memorable sentence by Rob Gordon “What really matters is what you like, not what you are like”. I don’t think that personality and character are not important, but the things we cherish around music, books, movies etc. are evidence and proofs to our value system and core beliefs and very often , they are the basis for deep relationship where media really provides a rich and delighting facilitation to those ties.</p><p>In our investors’ pitch, we often used this quote by Prof. George Howard:</p><blockquote>What people in the music startup world keep missing is that the <strong>vast</strong> majority of people don’t want every piece of recorded music. <br> Rather, they want <strong>what they like</strong>, and then <strong>they want to be led to other things</strong> that they might like <strong>by people they trust</strong>.<br>(Prof. George Howard, Music Educator, Consultant)</blockquote><p>Trust is really the basis of deep relationship, in media or otherwise. Just think of some of your best friends, and how much of your shared experience revolves around books, music and films you both cherish. Think of the authors, publishers, radio DJs and other curators and sources, you trust. Think of the podcasts you follow. <strong>People precede content</strong>. This was true for serendip 10 years ago, and it’s true for Medium today.</p><h3>Submit to algorithms or have them serve us</h3><p>Ev talks about the <em>transactional vs relational </em>. His words should act as a wake-up call to us. When we vote for transactional media, whether it is through TikTok, YouTube, Spotify or Facebook, we submit ourself to an algorithm that decides for us what we consume, which inherently submits us to superfluousness. Transactional media is the equivalent of those “13 channels of shit on the TV to choose from” as Pink Floyd once sang (only that 13, is more like 130,000 now).</p><p>Transactional media is out there because it serves the Big Tech companies and their likes. We’re made to believe that the algorithm knows us best and is programmed to provide us the best experience possible, where in fact, there’s every reason to believe that the optimization is there to serve the advertiser, or the data buyer, those that actually pay. (yeah..yeah.. “if you don’t pay for the product, you are the product” … cliché but true). There’s a reason why those algorithms are so secretive and non-transparent.</p><p>Take Spotify for example. They have just announced a new “Discovery Mode” claiming to give a better distribution option for opted-in artists, <a href="https://www.musicbusinessworldwide.com/spotify-is-letting-record-labels-influence-personalized-recommendations-so-long-as-they-pay-for-it-in-royalties/">but at the same time, cutting their royalties payments by half</a>. Spotify offers the artists a trade-off between distribution and payments. Will this end-up benefiting or hurting the artists is unknown and can’t be measured. <em>You have to trust the algorithm.</em> What is already known however, is that it did piss-off an already ‘down and out” industry with some already calling it the return of the <a href="https://en.wikipedia.org/wiki/Payola">Payola</a>.</p><p>But there’s another way. We have the power and we can feet-vote those services that put people before algorithms. We know which services these are because we can feel their love to the subject matter. We can feel the love of <a href="https://www.goodreads.com/">goodreads</a> to books; we can feel the love of <a href="https://bandcamp.com/">bandcamp</a> to music,; we can feel the love of <a href="https://medium.com/">Medium</a> to words. And we give back love to them, to make sure algorithms exist to serve us rather than the other way around.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=560d519c0ab5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/ev-williams-has-it-right-i-know-because-i-did-the-same-10-years-ago-560d519c0ab5">Ev Williams has it right; I know, because I did the same 10 years ago</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build software like Disneyland]]></title>
            <link>https://uxdesign.cc/build-software-like-disneyland-cd4a694e6e6e?source=rss-a902ae8caca0------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd4a694e6e6e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[Asaf Atzmon]]></dc:creator>
            <pubDate>Wed, 18 Nov 2020 09:50:40 GMT</pubDate>
            <atom:updated>2020-11-20T10:28:56.646Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Disneyland Theme Park at County Orange, CA" src="https://cdn-images-1.medium.com/max/1024/1*o1Uu58Lnz2V_aqWhqOMpLw.jpeg" /><figcaption>Source: Disney</figcaption></figure><p><strong>In </strong><a href="https://medium.com/@beeblebrux/what-i-talk-about-when-i-talk-about-software-products-a7f5da95d1b0"><strong>part one</strong></a><strong> of my post series, I argued that</strong> by thinking of Software as Products, analogue to manufactured goods, we have subscribed ourselves to an engineering-driven mindset that fails to capture the customers’ expectations and results in failures in market-product fit. <a href="https://medium.com/@beeblebrux/pushing-products-down-ones-throat-5e6cf171634c">Part two</a> introduced three modern approaches to innovation and software development that could help reduce the gap between what we develop and what customers want.</p><p>Both the <a href="https://hbr.org/2016/09/know-your-customers-jobs-to-be-done">Job-to-be-Done</a> theory and the <a href="https://designthinking.ideo.com/">design-thinking</a> movement make a strong case towards innovation that considers the entire dimension space of customers’ challenges including aspects of technical, psychological, social, and emotional nature. The cloud computing revolution and the popularization of a SaaS business model both provide a solid infrastructure needed to deliver on this promise by changing the nature of software delivery into something which is streamed, continuous and recurring, but a third element is missing to address this multi-dimensional challenge — The Experience.</p><h3>Welcome to the Experience Economy</h3><p>Few business theorists have actually regarded ‘experiences’ as early as 1998, describing it as the most recent evolution of the development of economies. In an HBR paper (which was followed by a book), Joseph Pine and James Gilmore have introduced what they called ‘<a href="https://hbr.org/1998/07/welcome-to-the-experience-economy">the experience economy</a>’. According to them, the history of economies has been advancing through multiple phases, ranging over thousands of years and at an accelerated pace; originating with an agrarian society centered around the exchange of <em>commodities</em>, moving to an ‘industrial economy’ where instead it was <em>goods</em> that were being transacted, and in recent decades, <em>services</em> that replaced goods as the currency of exchange. The next economy, they argued, is of <em>experiences.</em></p><figure><img alt="The progression of economic value" src="https://cdn-images-1.medium.com/max/390/0*xgfe9aVGpDa2ngav" /><figcaption>Source: HBR</figcaption></figure><p>A short summary of this history is elegantly provided in their own words through the story of the birthday cake:</p><blockquote>“As a vestige of the agrarian economy, mothers made birthday cakes from scratch, mixing farm commodities (flour, sugar, butter, and eggs) that together cost mere dimes. As the goods-based industrial economy advanced, moms paid a dollar or two to Betty Crocker for premixed ingredients. Later, when the service economy took hold, busy parents ordered cakes from the bakery or grocery store, which, at $10 or $15, cost ten times as much as the packaged ingredients. Now, in the time-starved 1990s, parents neither make the birthday cake nor even throw the party. Instead, they spend $100 or more to “outsource” the entire event to Chuck E. Cheese’s, the Discovery Zone, the Mining Company, or some other business that stages a memorable event for the kids — and often throws in the cake for free”</blockquote><p>Now, mind you, this was the pinnacle of the dot-com boom and the authors believed that soon everything from retail to enterprises will start to shape around staging experiences, where admissions fees for the explorations of the environment (for example, entering Niketown) may surpass in value the sells of the actuals goods themselves. Then the bubble burst, sending a ‘think-again’ message to this theory. The revolution didn’t happen, but it was still an important work, being one of the first to acknowledge the importance of addressing a wide-aspect of customers’ needs in how we design and stage our offering.</p><p>Moreover, in many ways, it pioneered the thought leadership in reckoning with the customer experience (CX) as part of the buildout of commercial value.</p><h3>Touchpoints, channels, and the customer journey</h3><p>So what is customer experience? <a href="https://en.wikipedia.org/wiki/Customer_experience">Wikipedia defines it</a> as “the product of an interaction between an organization and a customer over the duration of their relationship”; it is a term mostly applicable in the retail industry and is further defined through three important terms:</p><ul><li>Touchpoint is any meaningful interaction with the providers’ brand of offer, that might alter the perception of the customer towards it.</li><li>Channel is where an interaction takes place, which could be physical (e.g. a store) or digital (e.g. a website).</li><li>The Customer Journey is the sequential description of steps that a customer goes through, in interacting with touchpoints through channels.</li></ul><p>Consider, for instance, buying a car. A customer journey will include any interaction of the potential customer, whether at the car manufacturers’ website, at the dealership, and in the car itself. The CX approach advocates for a consistent journey that reverberates the organizations’ core value proposition throughout all touchpoints.</p><p>A good example for such practice is given in the paper <a href="https://hbr.org/2007/02/understanding-customer-experience">Understanding Customer Experience</a> by Andre Schwager and Chris Meyer:</p><blockquote>“A successful brand shapes customers’ experiences by embedding the fundamental value proposition in offerings’ every feature. For BMW, “the Ultimate Driving Machine” is much more than a slogan; it informs the company’s manufacturing and design choices. In 2000, Mercedes-Benz introduced a system that automatically controls the distance between a Mercedes and the car in front. BMW would not consider developing such a feature unless it amplified rather than diminished the driving experience.”</blockquote><p>CX is not merely a designers’ whim; studies suggest that companies that successfully introduced CX have seen a significant boost to their business performance. <a href="https://www.bareinternational.com/3-ways-cx-management-can-increase-revenue/">According to Mckinsey Insights</a>, brands that improve CX increased their revenues in 10–15% and lowered their costs in 15–20%.</p><h3>Software as an Experience</h3><p>What then can be learned from the world of retails and CX practices to be applied to software development?</p><p>The main premise of my post series is that <em>experience </em>rather than <em>product </em>is the right metaphor we should adapt as software designers and developers. For one, while traditional product management focuses entirely on <em>functionality, </em>an experience is multi-dimensional, it addresses several aspects of the customers job-to-be-done and can provide immersion through more than one sense. It, therefore, provides a much better framework to solve for the customer’s problem. Secondly, with its continuous “streaming” delivery and recurring business model, there’s a solid technical and business foundation to frame offerings as experiences.</p><p>What shape can “Software as Experience” take in practice? I would like to suggest two complementary models:</p><p><strong><em>1. Inter-products experience — </em></strong>the idea here is to design your software in the context of the overall experience delivered to the customer. In the lingo of CX, it would mean identifying the touchpoints that are software-based and to design them in the service of the overarching customer journey. Why is it important? because it ensures that the value proposition is consistently communicated throughout all the interactions of the customer, whether they are physical, digital campaigns or “products” and are all orchestrated within the same customer journey with clear inputs and outputs between them. Clearly, it also implies that Product Management &amp; Marketing cannot work in silos, but as even contributors to the same CX “bright star”.</p><p>Recently, we’ve been seeing a steady increase in the number of companies that are building their offerings as a service. These services serve as the best examples where inter-products experience is evident. For instance, many people prefer to take out their phones and invite a car via <em>Uber</em> even when standing 10-feet from a taxi-line. They do that, not because of a single Uber feature or product but due to the end-to-end customer experience it provides, which is enabled in its mobile app, in-car experience, payment backend system and other touch points. A company called <a href="https://www.blueapron.com/"><em>Blue Apron</em></a> solves a JTBD by giving people with no spare time at their hand the tools to become a “household chef”; subscribers to this service are being delivered on a weekly basis a box with “recipes for dummies” and fresh ingredients to make chef meals. The company’s offering is a mastermind of experience design, from the look of their website, to the packaging of the box and the mobile app that accompanies the service.</p><p>Inter-products experiences are not confined to B2C services but can be applied to a wide range of offerings. One thing to consider is whether, as a software provider, you own the customer experience. It is not always the case; for example, my previous employer, Harman, builds multimedia systems that are sold to automotive manufactures and further integrated as part of the entire vehicle. It is a B2B2C model, and it is impractical to consider the multimedia system as the customer experience. However, it is still highly useful for Harman to consider the entire experience of the end-user — the driver — and to derive how what they develop fit within this bigger context. In fact, Harman does just that as part as a consortium it is leading, called <a href="https://www.experiencespermile.org/">Experience-per-Mile</a> which is set to define the future driving experience.</p><figure><img alt="A family in a car" src="https://cdn-images-1.medium.com/max/597/0*fcD4EuPCWG6WbZZK" /><figcaption>Source: EPM</figcaption></figure><p><strong><em>2. Intra-product experience —</em></strong><em> </em>just as important is to consider the product itself as an experience. Rather than talking about features and capabilities, we should start talking in narratives, journeys, and touchpoints. In the same way that a fashion store is designed up to the tiny detail to lead you to open your wallet and buy clothes, a good product design should take you through a journey to meet whatever objectives it has. Jack Dorsey <a href="https://www.youtube.com/watch?v=acMXhhdWylQ">had this concept right</a> already nine years ago. Call it “User Experience (UX) on steroids”, but I truly believe there’s more to be done on product design by fully embracing the CX vocabulary and translating it into tangible tasks on the product backlog.</p><h3>Think like Walt Disney</h3><p>It is time then to abandon our engineering toolkit, and rather than ‘manufacturing a product’ start thinking in terms not unlike ‘designing a theme park’. The indisputable archetype of theme park planning, Walt Disney, had held to these principles as early as the 50s. When the first Disneyland opened up in Southern California it <a href="https://www.fastcompany.com/90230124/the-clever-psychology-of-disneylands-design">has set the standard for what an immersive experience means</a>, and since then it had been nothing but optimizing and improving to deliver on the same original promise, <a href="https://www.fastcompany.com/1671616/a-1-billion-project-to-remake-the-disney-world-experience-using-rfid">embracing much software and technology</a> along the way.</p><p>Can a similar approach govern our software development practices? What would we need to change in our current processes and organizations to better match this challenge? Here are some random thoughts and things to consider:</p><ul><li>Ditch your ‘product management’ team and create ‘experience design’ — a multi-disciplinary team comprised of storytellers, psychologists, marketers, designers, researchers and writers.</li><li>Build an “experience — to — specification” bridging process so the CX objectives and planning result in a software-based continuous delivery that meets the design. Work from the outside in.</li><li>Break down silos between the different organizational functions. A customer journey spans marketing, product (experience) design and customer success. Only when they work under a unified overarching CX objective, can the experience be kept consistent and optimized.</li><li>Measure at every touchpoint using a consistent and normalized system which is clearly mapped to conversion rates and business results. How realistic is it to figure out the experience of a customer, when your designers talk in <a href="https://www.interaction-design.org/literature/article/google-s-heart-framework-for-measuring-ux">Heart</a>, your marketing and sales in conversion and win rates and your customer success team in <a href="https://en.wikipedia.org/wiki/Net_Promoter">NPS</a>?</li></ul><h3>Wrapping Up</h3><p>This post series has been quite a journey in its own right, and I hope I didn’t lose you along the way. My key takeaway is that for too long we have been restricting ourselves to an outdated frame-of-thought which is rooted in the early days of personal computers when software was delivered as ‘products in a box’.</p><p>The technology and business models have since evolved greatly to enable us to move to a modern delivery mode of streamed software over a continuous customer interaction. More importantly, strong research suggests that our engineering-driven approach is at the core of the highly too common misfit of market-product which kills many startups and makes customers unsatisfied and underserved.</p><p>Customer Experience has proven to be a highly successful approach at retail, entertainment and other user-centric industries. The world of software could take a page from these successful case studies by rethinking its structure, processes and deliverables and adopt new models that better match the journeys customers are making and the struggle they have along the way to get-the-job-done.</p><p>It’s time to stop manufacturing and deploying ‘products’ and start designing and staging ‘experiences’. It’s time to think less like an Edison, and more like a Disney.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/94/0*D__eXiddaYY38mfE" /><figcaption>The UX Collective donates US$1 for each article published in our platform. This story contributed to <a href="https://www.bayareablackdesigners.com/">Bay Area Black Designers</a>: a professional development community for Black people who are digital designers and researchers in the San Francisco Bay Area. By joining together in community, members share inspiration, connection, peer mentorship, professional development, resources, feedback, support, and resilience. Silence against systemic racism is not an option. Build the design community you believe in.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd4a694e6e6e" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/build-software-like-disneyland-cd4a694e6e6e">Build software like Disneyland</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>