<?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 Varun Mittal on Medium]]></title>
        <description><![CDATA[Stories by Varun Mittal on Medium]]></description>
        <link>https://medium.com/@varun-mittal?source=rss-90dd3373cfcc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*M4KeQJZyw4iPllNcYytLHw.jpeg</url>
            <title>Stories by Varun Mittal on Medium</title>
            <link>https://medium.com/@varun-mittal?source=rss-90dd3373cfcc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 20:27:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@varun-mittal/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[Inside the mind of a Creative-Product-Leader]]></title>
            <link>https://medium.com/finn-no/inside-the-mind-of-a-creative-product-leader-444fa90cdf47?source=rss-90dd3373cfcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/444fa90cdf47</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Varun Mittal]]></dc:creator>
            <pubDate>Wed, 16 Jun 2021 10:07:54 GMT</pubDate>
            <atom:updated>2021-06-17T21:23:20.605Z</atom:updated>
            <content:encoded><![CDATA[<h3>Inside the mind of a Creative Product Leader</h3><h4>The 3-floor-mindset</h4><p>If you are a person who cares deeply about building beautiful products that delights customers, then using the 3-floors-mindset will help you become the creative product leader your team deserves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eZ0N8hpis3RkVl2snGXyGg.png" /></figure><p>So we’re on the same page, what is creativity and who is a product leader?</p><p><strong><em>Creativity:</em></strong> for some reason people attribute creativity to designer or artists but really creativity is just <strong>the ability to transcend traditional ways of thinking to develop new and original ideas. </strong>It’s available to all of us.</p><p><strong><em>Product leader:</em></strong> anyone who is a proponent for building products customers will love and isn’t willing to ship junk is a product leader. Developers, designers, product managers, data scientists, are all product leaders.</p><p>This blog is broken down into 3 sections that build the 3-floor-mindset, where learnings from each floor will equip you to become a better, more creative product leader.</p><h3>Floor 1 — Ignite Curiosity</h3><h4>Learn from kids</h4><p>Many people live their lives with something I call the <strong>creative fallacy</strong> — a belief that creativity is something you are endowed with from birth, otherwise you are forever imprisoned to the un-creative corner. Fortunately, there is ample evidence that this isn’t true.</p><p>We’re all born rather creative and very curious. Kids use this curiosity to learn about the world around them — each day they try to piece it together. If you have kids, you know they ask a lot of questions; and if you don’t, recall your own childhood or this video should give a good indication.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F6y5Zcat0-_U%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D6y5Zcat0-_U&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F6y5Zcat0-_U%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/fa089d678c4b1174c9d1f696e022c0a4/href">https://medium.com/media/fa089d678c4b1174c9d1f696e022c0a4/href</a></iframe><p>Unfortunately as we get older, this curiosity can be beaten out of us by busy parents and teachers. The blame doesn’t rest on their shoulders entirely. For that, we have the industrial era to blame — organised and built with cogs and replaceable parts (you and me).</p><p>In order for the industrial machine to work, you had to be less you, and more like a lego brick— predictable, unoriginal, and most importantly replaceable.</p><p>I remember when I was at school, I traded my free time to complete homework assignments for hopes of getting an A. Not because I was particularly curious about a topic, in fact I’m pretty sure I didn’t even understand all of it, but because I was lead to believe that good grades was the way into higher classes and eventually into higher education.</p><p>Summer holidays excited me for the wrong reasons. It most certainly wasn’t about having 6 weeks off to learn something new or to go deeper into a subject that interested me. It was 6 weeks off to do absolutely NOTHING or NOWT in Yorkshire vernacular, where I grew up.</p><p>What I was getting at school was education (forced), rather than learning (voluntary). If I was taught to be curious, I would have spent my childhood doing what kids do best, asking questions and probing trying to figure out how things work.</p><h4>The infinite learner</h4><p>As adults, we rely on convention and what we’re told by others because that seems a whole lot easier than breaking things down to think for ourselves. We let our past, our history, our education decide what we are and aren’t capable of doing.</p><p>For me that epiphany came in Summer 2011 whilst travelling with a friend after my exchange year in Canada. One day he randomly blurted out, “most summers I read about 15–20 books”. My jaw dropped because up until this point, I hadn’t voluntarily read any books except those required for school.</p><p>Deciding to challenge myself that day I stepped into a book store and walked right to the <em>“Most popular books this week”</em> section and bought my first book — <a href="https://www.goodreads.com/book/show/36578942-the-100-year-old-man-who-climbed-out-the-window-and-disappeared">The The 100-Year-Old Man Who Climbed Out the Window and Disappeared.</a> I enjoyed it enough to go back to the bookstore another time.</p><p>Not knowing much about books or what genre I would enjoy, I picked up <a href="https://www.goodreads.com/book/show/11468377-thinking-fast-and-slow?from_search=true&amp;from_srp=true&amp;qid=epK3wchXBD&amp;rank=1">Daniel Kahneman’s Thinking Fast and Slow</a> (again from the <em>“Most popular books this week”).</em> If anyone has read it, you can anticipate the challenge the faced me given it was my 2nd voluntary read. At the end of 400-some pages, I had a 100 questions that I didn’t have the answers to — and most importantly it had lit the fire of curiosity in me again.</p><p>Enough to start questioning if Structural Engineering (the Masters I was about to complete) was something I wanted to pursue long term. Turned out I wasn’t curious enough about it; what excited me was technology and consumer-software products, it was after all the era that saw the rise of the iPhone and consumer-focused start ups. So I got a job working in product management in London.</p><p>There was lots happening in the industry as most companies were busy digitalising and moving desktop software to the cloud and trying to figure out value based pricing. The high-school-me would have walked away with 4 weeks off with NOWT to do attitude, but the newly-curious-me had other plans. With no background in finance and the willingness to learn, I spent days and weeks watching YouTube videos, reading books and consuming many articles on product bundling and pricing strategies. Endowed with this new knowledge, I ended up creating the foundation of SaaS pricing models for many products that I managed at the time that are still in use today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ODg1EsKBCHMA-ZVqWLliHQ.jpeg" /></figure><p>Key takeaway: you don’t need any formal education, or previous experience in a topic, just <strong>curiosity and yearning to be an infinite learner </strong>— by doing so, you open yourself to so many more possibilities. When was the last time you did something for the first time?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c2I_4jVA5c4dHjyo_dM6Ug.png" /></figure><p>Thinking for ourselves requires that we understand and reason from first principles.</p><h3>Floor 2 — Reason from first principles</h3><h4>Do you want to play as cook or chef?</h4><p>You need to decide as a product leader, if you want to be the chef or the cook. (I’m borrowing this analogy from <a href="https://waitbutwhy.com/2015/11/the-cook-and-the-chef-musks-secret-sauce.html">Tim Urban’s post</a>)</p><p><strong>Chef, </strong>someone who has the ability to create recipes because he or she understands the fundamentals of cooking, how different spices work together in harmony, what vegetables or meats to go together. Chefs are forever trying to create new recipes by a tremendous amount of experimentation and exploration. The chef is said to be reasoning from first principles. He thinks for himself.</p><p><strong>Cook, </strong>on the other hand is<strong> </strong>someone who’s very good at copying what has already been done. There are of course different levels of cooks. Some are completely by the book, measuring precisely every ingredient; some get confident enough to swap out an ingredient or two. Few might even get a little creative by combing two recipes. For cooks, even if they manage to create something new, they won’t understand how or why it worked because they are borrowing from the work of others.</p><p>The spectrum looks a little bit like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oj2hiOfe8f4iJLr1gMp9yg.jpeg" /></figure><h4><strong>How this applies to product leaders</strong></h4><p>As a product leader when you play cook — taking what already exists and improving on it, you outsource all your thinking to someone else — you end up living in the shadows of others.</p><p>Those that came before you, must have had their own views of how things work at a specific point in time. They add assumption blocks with time to build the tower of assumptions. With a world of cooks adding on top of each other, the collective tower grows.</p><p>When it’s your turn, and you decide to play cook, you add your new assumption on top of the existing tower without questioning it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*slvX0BSglezCyCphEW7x1Q.png" /></figure><p>If instead you step back, start reasoning from first principles, and look at those assumptions made by those before you, you’ll find they either no longer make sense or that they never really did, and people just blindly copied everyone else. When you cut through these flawed analogies you’ll see what is possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zNSYCmvoevdwYqz3rCPcjQ.png" /></figure><h4>Some examples</h4><ol><li><strong>Tesla on door handles</strong></li></ol><p>Instead of copying what others have been doing for years. They instead asked what should a door handle be? Does it need to stick out all the time? Can we make it flush with the rest of the car body? Why has it always been like this?</p><p>They managed to redefine the door handle twice already. Once for the Model S and again for Model 3.</p><figure><img alt="Same car door handles across multiple makes. Tesla redesigning the door handle." src="https://cdn-images-1.medium.com/max/1024/1*HvbSY_4NFzRlc4VLnWexVg.jpeg" /></figure><p><strong>2. Apple and Samsung on smartphone keyboards</strong></p><p>Steve Jobs during the <a href="https://www.youtube.com/watch?v=MnrJzXM7a6o">launch of the iPhone</a> elaborated on how they ended up with the product. They didn’t start by saying, “Right, so people seem to have gotten use to this kind of keyboard more than that kind, and everyone seems to struggle with hitting the right key on their keyboards — so let’s get creative and make the best phone keyboard the world has seen!”</p><figure><img alt="Same phone keyboard across multiple makes and models. Apple and Samsung redesigning the phone." src="https://cdn-images-1.medium.com/max/1024/1*qW2x53Ans4zQJ8e6RLNPaw.jpeg" /></figure><p>Instead they looked at the existing phones and realised they are all so rigid with the same keyboard even though different applications that run on the phone may require a different interface.</p><p>What happens if you think of a great idea some time from now, you’re stuck with the product you already shipped.</p><p>They simply asked, “What should a mobile device be?” and in their reasoning from ground up, a physical keyboard didn’t end up as part of the plan at all. It didn’t take a genius to come up with the design of the iPhone — it’s actually pretty logical — <a href="https://varun-mittal.medium.com/5-the-big-deal-with-innovation-1f905f969994"><strong>it just took the ability to not copy</strong></a><strong>.</strong></p><p>The real power of first-principles thinking is moving away from incremental improvements and into the world of progressive possibilities. When we take what already exists and improve on it, we are in the shadow of others — we inherit a world that conforms to what they think, their conventions and their possibilities, not ours.</p><p>There is absolutely nothing wrong with looking at what others are doing. In fact analogies are beneficial — they can help make a complex problem easier to communicate and understand. However, blindly copying others without your own reasoning would be foolish. <strong>Analogies can’t replace understanding.</strong> While it’s easier on your brain to reason by analogy, you’re more likely to come up with better answers when you reason by first principles.</p><blockquote>“It’s just as intellectually lazy to believe everything you see, as it is to deny everything you see.”</blockquote><blockquote>— Neil deGrasse Tyson</blockquote><p>As we get older, we start relying on convention and what we’re told by others because that’s a whole lot easier than breaking things down into first principles and thinking for ourselves.</p><p>Key takeaway: First-principles reasoning cuts through dogma and removes the blinders. We can see the world as it is and see what is possible. We move away from incremental improvements and into the world of progressive possibilities. We stop living in the shadow of others. We end up becoming the chef.</p><blockquote>“As to methods, there may be a million and then some, but principles are few. The man who grasps principles can successfully select his own methods. The man who tries methods, ignoring principles, is sure to have trouble.”</blockquote><blockquote>— Harrington Emerson</blockquote><h3>Floor 3 — Work like an artist</h3><p>Do you think Vincent van Gogh painted The Starry Night on his first attempt and became famous over night?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/756/0*oXeWl7PGyHQHmS6x.jpg" /></figure><p>I highly doubt he did. How many not-so-good paintings did he have to paint before he figured out how to make the one that would be a hit?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tvDBViVmnSln0rJ0kgpCqw.png" /></figure><p>The industrial era required us to be right. Every time. Make an error in the spreadsheet, you’re out. Make a mistake in the production line, you lose your job. Argue with your Boss, you’re fired.</p><p>But the world an artist dreams of creating doesn’t exist yet, it has no right answers. To be creative is to be on the frontier, to invent the next thing, the things for which there isn’t a manual or playbook. If there was, someone would have done it already.</p><h4>You don’t need reassurance</h4><p>Kids need reassurance because they lack experience and they don’t know what to expect. We reassure them because we try to protect them. Seeking reassurance isn’t helpful to those of us who work to make change happen, to challenge the status quo for a better future. We do things that might not work which means exactly that — they might not work.</p><p>We have no choice but to trust ourselves to lead the way. Reassurance is futile — it’s a short-term feel-good effort. It shifts the focus — from generously and doggedly following the practice of an artist — to making sure we are successful.</p><p>No one owes us anything. No one owes us an applause or thanks. The feeling of being owed destroys our ability to be generous and creative. A standing ovation is hardly worthy if the audience is obliged to do so. Working in anticipation forces us to search for reassurance and the perfect outcome, and away from work where self-trust and generosity are valued. It’s only when we lack confidence and trust in the work we do, we seek external feedback and validation. <strong>Gratitude isn’t a bad thing, but believing we are owed gratitude is.</strong></p><p>When we do creative work for generous reasons, and not for reciprocity, we stop believing that we are owed anything by others. We do the work, simply because we care.</p><p>Do you trust yourself enough to commit to engaging with a product idea regardless of the chance of success?</p><h3>When you’re ready, cut the wood</h3><p>Your job as a product leader is to be on the frontier, a place that doesn’t have a recipe book.</p><p>Using the 3-floors-mindset: being an infinite learner, a chef who reasons from first principles and thinks for himself/herself and works like an artist, is ready to mark the piece of wood and start cutting. Once you cut the wood, there will be many who can help you improve and refine it.</p><p>The hardest job is getting the piece of wood and knowing how it should be cut. The job of the creative product leader.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hXli85OCf-S7NI2NahvCZA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V6XWD7RJuH1XJUiSDPDNKA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=444fa90cdf47" width="1" height="1" alt=""><hr><p><a href="https://medium.com/finn-no/inside-the-mind-of-a-creative-product-leader-444fa90cdf47">Inside the mind of a Creative-Product-Leader</a> was originally published in <a href="https://medium.com/finn-no">FINN.no Blog – Product, Design, and Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#6 The first rule of innovation is: you don´t talk about innovation]]></title>
            <link>https://medium.com/swlh/5-the-big-deal-with-innovation-1f905f969994?source=rss-90dd3373cfcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f905f969994</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Varun Mittal]]></dc:creator>
            <pubDate>Thu, 11 Mar 2021 23:22:49 GMT</pubDate>
            <atom:updated>2021-03-26T19:06:12.820Z</atom:updated>
            <content:encoded><![CDATA[<h4>Give people a problem to solve</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dpzkiFvblQfAfAR6iofVNA.png" /></figure><p><strong><em>“We´re going to be innovate this year”</em></strong></p><p><strong><em>“Our top priority for the coming year is to innovate more”</em></strong></p><p><strong><em>“We have increased our budget to spend on innovation this year”</em></strong></p><p>Innovation I feel is one of those icky topics these days that everyone is talking about and seemingly it is the #1 priority in most companies, yet I fear most don´t understand what it really entails.</p><p>The way I approach this type of topic is to ask myself what I don’t fully get — I look for foggy spots in my knowledge and read all I can until my brain is fried. At this point, the feeling of overwhelming frustration takes over and I have no idea what to make of anything I have just read or how to synthesise it. The next phase is usually a period of impasse which could last days, weeks or even months. Then one day, out of the blue, listening to a completely unrelated podcast or reading an article, a light bulb in my brain goes off and I discover a novel way to explain the thing that had previously “fried my brain”. This as I will explain later, is in essence what <em>innovation is about.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sjSt_KaEcyrzKWDfnQBXUQ.jpeg" /></figure><p>One disclaimer before we start:</p><p>There are many different schools of thought on how to describe innovation, but I use innovation in its broadest sense. Innovation = creating something novel that solves a problem.</p><p>With that out of the way, let’s dive in. This chapter is broken into 3 parts:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dHmU_SYjyinxVayGoTMQYg.jpeg" /></figure><blockquote>1. What is innovation?</blockquote><blockquote>2. Why innovation happens?</blockquote><blockquote>3. How innovation happens?</blockquote><h3>Part 1 — What is innovation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mqTw0He4_Z1E3-KdQGHS3A.jpeg" /></figure><p>The year is 1707, the fleet of Admiral Sir Clowdisley Shovell had just been wrecked near the Isles of Scilly through not being able to gauge the correct longitude position of the fleet. Over two thousand men, including Shovell, were lost.</p><p>This was not an isolated case. Problems with determining longitude was a major issue for the safe passage across the vast oceans leading to many lost vessels and a good number of shipwrecks.</p><p>Pin-pointing the location of the ship without the benefit of modern technology was a huge challenge for 18th century sailors. To locate their position on a map, navigators had to know two things: latitude and longitude.</p><blockquote>The earth is divided into a grid like any X-Y graph where:</blockquote><blockquote><strong>X-axis</strong> is the <strong>longitude. </strong>lines<strong> </strong>going pole to pole — used to find out how far <strong>east</strong> or <strong>west</strong> a place is.</blockquote><blockquote><strong>Y-axis</strong> is the <strong>latitude, </strong>lines running parallel to the equator — used to find out how far <strong>north</strong> or <strong>south</strong> a place is.</blockquote><blockquote>If a navigator knew both his latitudinal and longitudinal position on that grid, he could figure out precisely where his ship was positioned at sea.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*hs2nZLo9fiCPxX9P.jpg" /><figcaption>Earth grid</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*VOVs7j5Q7X7tEaX0.jpg" /><figcaption>Latitude and longitude</figcaption></figure><p><strong>The latitude part </strong>— comparatively easy. Sailors used a tool called a sextant to measure the angle created by the noon sun, the ship, and the visible horizon. This angle could then be converted to degrees latitude by using a chart. Simple — now we know where we are on our Y-axis.</p><p>The longitude part — very difficult. In fact, so difficult that in July 1714, British Parliament convened a Board to examine the problem and set up a £20,000 prize for the person who could invent a device that could accurately determine longitude at sea. The rotation of the Earth on its axis and its revolution around the Sun made it infinitely hard to create a method that would allow for a measurement like for latitude.</p><p><strong>What did navigators do about this problem? </strong>One solution was to sail to the desired latitude, then set a course due east or west until landfall was reached. Another solution was called deductive reckoning — navigators would keep track of the ship’s speed every half hour, then calculate the distance they had traveled. If one knew the latitude, course and distance the ship had traveled, an educated guess could be made as to the ship’s longitudinal position on a map or globe.</p><p>For years, people had believed the solution lay in understanding the night sky and astronomy would inevitably hold the solution to the longitude problem. They just had to develop more charts and build better equipment. However this led to nowhere.</p><p>In the end, the solution was rather simple: <strong>a clock.</strong></p><p>Most people would have wagered a bet on the astronomers, but in fact the solution came from an unexpected source — a <a href="https://en.wikipedia.org/wiki/John_Harrison"><strong>watchmaker, John Harrison</strong></a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*28z6NQSByetNmMMX.jpg" /><figcaption>Source: Google doodle</figcaption></figure><p>Harrison built his first <a href="https://en.wikipedia.org/wiki/Longcase_clock">longcase clock</a> in 1713, at the age of 20 and over the years had become a component clock maker. Clocks weren´t as accurate as they are now — they kept slowing down — making an accurate clock was in fact an extremely difficult endeavour. Nevertheless, Harrison managed to build a sea clock that would be worthy of solving the longitude problem.</p><p>The sailors would now set their sea clock to Greenwich time (GMT)(where longitude is 0°). At some time during the day, the sun is at its highest position in the sky — 12:00 noon. In Greenwich, you have now set your clock to the sun — it says 12:00 noon.</p><p>As you travel eastwards or westward, you repeat the same experiment by waiting until the sun is at the highest point. You take the time from your second sea clock and subtract it from the time on your Greenwich clock. Multiply the time difference by 15 and you can find out your longitude.</p><blockquote><strong>Longitude = (Local time — Greenwich time) X 15degrees</strong></blockquote><p>(15 degrees of longitude = 1 hour difference; 1 degree longitude = 4 minutes difference.)</p><p>Harrison´s sea clock albeit a simple solution, compared to the astronomical observations most sailors and the Royal Society had looked towards for the longitude problem, was at least 10X better than the status quo.</p><p>We can see from this short tale, that innovation is really about a novel solution that is at least 10X better. Innovation is about solving a problem. This could be done by connecting two disparate ideas or cross-pollinating two different departments. This is what I alluded to at the start —I find a way to climb up the hills of clarity not by reading more of the same topic but instead from new information from a completely disconnected subject.</p><p>Some other 10X innovation test examples:</p><ul><li><strong>Tesla electric cars</strong> — pass the 10X improvement over internal combustion cars</li><li><strong>Iphone</strong> — passes the test over the antiquated Blackberries and Nokias.</li><li><strong>Iphone 12 Pro</strong> — doesn´t pass the test. It had some new features and functionality but nothing revolutionary compared to the status quo.</li></ul><h3><strong>Part 2 — Why innovation happens</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zrH6e3myR1mhb-Sgj-Y1fg.jpeg" /></figure><p>Today, innovation is #1 priority for most companies, and yet most don´t even know how innovation happens. Leaders often ask, “<strong>Why aren´t we innovating</strong>?”, or “<strong>Why are we so slow to innovate</strong>?”</p><p>The problem with the question “Why aren´t we innovating or why are we slow?” is that it’s misunderstanding how progress happens. Instead of asking why innovation sometimes <em>stops</em>, we have to ask the question:</p><p><strong><em>Why does innovation or technological progress ever happen at all?</em></strong></p><p>The mistake of the first question is the intuitive but incorrect notion that innovation naturally happens on its own over time — it doesn’t. I can tell you this for sure, because my online bank has the exact same horrible user interface it had in 2010. The way technology works is that by default, it stands still, and it moves forward only when something <em>pushes </em>it forward.</p><p>We have the same misconception when we think about evolution. Natural selection doesn’t make things “better” by itself — it only optimises biology to best survive in the environment it finds itself in. When something in that environment changes — a predator becomes faster or a certain type of food becomes scarce — species that were previously optimised to the environment no longer are. This change forces the genetics of the species to react in order to optimise to the new environment.</p><p>In the natural world, when food on the ground becomes scarce, species will feel the pressure of hunger and over time, their genetics will re-optimise by developing good bodies for climbing or long necks or wings. A running species that becomes a climbing species hasn’t become <em>better — </em>just better fit for the current circumstances.</p><p>Optimisation in the natural world of species is simple because the end goals are simple: the core needs of biological creatures are always the same — to self-preserve and reproduce.</p><p>Similarly, in the business world, we need to figure out the core goals and needs of companies. Companies are run by people — human beings — who are biological creatures. Like any other biological creature, our first instinct is to always satisfy our basic needs — food, shelter, clothing. Assuming these are met, thinking about innovation isn´t something that would help these people towards optimising for their environment.</p><p>So if we want innovation and technological progress, what kind of yearning do we want people to feel?</p><p>Turns out there are two pretty powerful drivers:</p><h4><strong>Greed</strong></h4><p>Uncontrolled longing for increase in material gain; or social value, such as status, or power. In a capitalist world, the more value you create for others, the more you are able to charge for it. So company executive will strive to create better products and services in order to optimise, which just means making as much money as they possibly can.</p><h4><strong>Ambition</strong></h4><p>Whilst greed can lead to incremental progress, if you really want to move the needle (10X improvements), you need ambition — the desire and determination to achieve something. Reasons for this kind of ambition can vary — it could be the desire to be famous and renowned, to leave one’s mark. Or the pure confidence in oneself to change the world because the status quo frustrates the hell out of you.</p><p>In an established industry full of incumbent winners running on greed (making as much money as possible) is like the highest layer of trees in a crowded rainforest. They’ll push upward only as needed, nudging and elbowing each other for little gains and victories as they compete for sunlight, mostly trying to keep their place in the canopy. Greed only wants sunlight — it doesn’t care how high up it is when it gets it.</p><p>But below, under the canopy, is the ambitious hungry underdog <em>yearning</em> for sunlight and will spend 15 hours a day working on getting it. When the breakthrough comes (he climbs the hills of clarity) — underdog <em>bursts </em>up through the canopy into the open sky and spreads its leaves out wide. Suddenly, the trees that had been on top are blocked from the sun. Greed is now replaced by the much more powerful drive of <em>survival</em>, and innovation kicks into high gear as they scramble upwards for their life.</p><p>The environment has been changed — it’s been <em>disrupted</em> — and in this new world, created by the underdog disruptor, companies have to innovate in order to re-optimise for this new environment. Some end up back on top, others die — and at the end of it all, a 10X improvement has been made.</p><p>We all witnessed an example of this when Apple rocketed through the mobile phone canopy in 2007 and forced all of the other companies to make a smartphone or die. Samsung managed to get itself back into the sun. Nokia did not. Tesla is now bursting through the automobile canopy and forcing other car companies to figure out how to get some sun again. In time we will know the Nokias and Samsungs of the automobile canopy.</p><p>This makes one beg the question: <strong>why don´t companies stop the underdogs from reaching the canopy? </strong>It turns out existing companies at the top of the canopy become too complacent because they don´t have to compete for the sunlight — it just comes to them so why waste resources when you can easily get the sun. It´s only when the environment changes, they are forced to re-optimise for the new environment.</p><p>This leads us nicely to our next part: how to innovate then.</p><h3>Part 3 — How innovation happens</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QjURT9Ca2kOSnTbQ0bZL6g.jpeg" /></figure><p>When companies say their #1 priority is innovation, they´ve completely failed to understand the drivers behind it. Saying we must innovate this year, is like saying we must fill up our car with petrol or electricity. Sure you can fill up your car with fuel, but why do you want to fill your car.</p><p><strong>Innovation for the sake of innovation sounds like this:</strong></p><blockquote>You: “Hey neighbour, “what are you working on?”</blockquote><blockquote>Neighbour: “Innovation”</blockquote><blockquote>You: “What are you doing?”</blockquote><blockquote>Neighbour: “didn’t you hear, INNOVATION”</blockquote><blockquote>You: “But what?”</blockquote><blockquote>Neighbour: “Innovation”</blockquote><blockquote>You: “What do you plan to do with the innovation?”</blockquote><blockquote>Neighbour: “I am going to sell it to others”</blockquote><p>Innovation is a lot like that. Just innovating for the sake of innovating doesn’t make sense. Doesn’t paint a picture for why you set out in the first place. We don’t buy a car simply so we can buy more fuel. Car is a lot more valuable if we can go somewhere.</p><p>Now we know, we can´t innovate, simply by saying innovate. We learnt earlier that one of the main drivers behind innovation and technological progress is ambition. That explained why people innovate. Next question, how? Answer: give them a problem to solve</p><h4>A Problem to solve</h4><p>Simply put, what is that thing that you want to find a solution for.</p><p>This could be your reason to exist — which we discussed in the first chapter of this mini series. Your reason to exist or your vision might be suggestive of an imminent environment change or maybe you yourself are a catalyst for that change. Instead of waiting for some other underdogs to come rocketing up through the canopy and change the environment, you yourself decide to do it.</p><p>Tesla having just burst through the canopy of the automobile industry and being satisfied with its newly acquired sunshine, is instead already trying to change the environment before anyone else does by being a leader in autonomous driving. All because they see this as a way to “accelerate the advent of sustainable transportation” — their reason to exist.</p><p><strong>How did we get the cordless screwdriver? </strong>Did someone in Bosch say, “This year we are going to innovate. We don´t know what, but we are going to innovate.” No.</p><p>The credit for the cordless power tools goes to NASA.</p><p><strong>The problem to solve:</strong> We´re dangling by a cord attached to this space station, going 27,600km/hour around the Earth, there is no place to plug-in my power tool to make repairs.</p><p>The innovation was a derivative of the problem: battery powered power tools to replace parts on the Space Station. Later the consumer industry caught on and put the same technology in our hands so we could drill a hole in our walls to hang up a painting without having to find a power socket first.</p><p>Try another, <strong>how did we get the MRI machine</strong> — the most powerful machine amongst all a doctor has in his arsenal, allowing conditions to be diagnosed without cutting you open. Did the medical professionals agree at some conference: lets innovate this year. I think you know the answer. So how did we get the MRI machine?</p><p>For that we must thank the physicist, <a href="https://en.wikipedia.org/wiki/Isidor_Isaac_Rabi">Isidor Isaac Rabi</a>. <strong>His problem</strong>: get a better understanding of how stars and planets are formed by studying gas clouds. Afters years looking into this problem, he finally figured out that nucleus of atoms resonate at different frequencies based on where the atom is on the periodic table, when it encounters radio waves.</p><p>It then took a clever medical technologist to create a machine that can be used to put humans inside of it and be able to distinguish one tissue from another. I don´t know about you but I am very glad for the cross-pollination that allowed for the MRI — much better they can figure out what´s wrong with me without cutting me open first.</p><p>For innovation, there must be a problem to solve first.</p><p>The underlying quality needed to make innovation happen: <strong>Perseverance </strong>— persistence in doing something despite difficulty or delay in achieving success.</p><p>Innovation is trial and error. Innovation is something that fails and fails, until is succeeds. <strong>Innovation is something that happens when passionate people doggedly soldier on despite failures because they can see the light at the end of the long tunnel.</strong> There are no quick wins. Yet, most companies set a timeframe on innovation. They lack the foresight and the willingness to admit there are many unknowns. They think they have it all and incremental changes are enough to make the revenue needed to keep share holders happy.</p><p>If your problem or reason to exist is something you believe in deeply, you will keep trying until you find a solution. If it was easy, someone would have done it already. Remember innovation must be at least10X better than the status quo.</p><p>Innovation is hard but it will all be worth it when you finally burst up through the canopy and change the environment and force all the incumbents to re-optimise. Do not give up too easily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*41sWrieeI9WB-zxsb8GCQw.jpeg" /></figure><p>Continue with the series</p><ul><li><a href="https://varun-mittal.medium.com/how-to-build-a-company-that-lasts-e2246c1ce399">Intro: How to build a company that lasts</a></li><li>#1 Why do you exist</li><li>#2 Bold leaders double down</li><li>#3 Do you know your competitors</li><li>#4 Short-term money dilemma</li><li>#5 The right way to increase your company´s worth</li><li>#6 The first rule of innovation is: you don´t talk about innovation</li><li><a href="https://medium.com/swlh/we-don-t-build-feature-here-the-secret-to-empower-and-align-teams-using-the-vision-tree-cc8302684f51">#7 How to align your entire team and empower them</a></li><li>#8 Company-centric metrics vs user-centric metrics</li><li>#9 Build teams that help customers make progress</li><li>#10 How to escape when you´re stuck in a rut</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f905f969994" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/5-the-big-deal-with-innovation-1f905f969994">#6 The first rule of innovation is: you don´t talk about innovation</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[How to build a company that lasts]]></title>
            <link>https://varun-mittal.medium.com/how-to-build-a-company-that-lasts-e2246c1ce399?source=rss-90dd3373cfcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2246c1ce399</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Varun Mittal]]></dc:creator>
            <pubDate>Thu, 11 Mar 2021 23:10:19 GMT</pubDate>
            <atom:updated>2021-03-24T11:12:30.840Z</atom:updated>
            <content:encoded><![CDATA[<h4>A company that doesn´t fall of the life balance beam.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ac6Vi_SJ2NWqXM45wIbu2Q.jpeg" /></figure><p>This is a foreword to a mini series on how to build a company that survives ravages of time.</p><p>Companies are complex adaptive systems with many intricate parts, that are required to work in symphony, and when they fail to do so, can be detrimental to the livelihood of the said company.</p><p>In some ways companies are a bit like us humans. They are born as small entities and they have the potential to grow.</p><p>For human to grow, they require surplus metabolic energy (calories we consume); this is the difference between the total metabolic energy minus the energy we use to maintain existing cells.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3RJyU6siv_-WQoLpdOKJIA.jpeg" /></figure><p>Similarly for companies, to grow, there needs to be additional capital (financial energy) available after paying off the existing cost of conducting business (salaries, infrastructure, other costs). Organisations achieve this by minimising costs so as to increase profits which can then be inserted back into the company for further growth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vVlf93FCGwxKWVByFTUZUw.jpeg" /></figure><p>Eventually both companies and humans reach an impasse (this is life on the balance beam), when the cost of maintaining the status-quo is equal to the incoming energy or capital.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q3d_5vtAB7yCCz__irzx9A.jpeg" /></figure><p>Eventually us mortal-humans fall of the balance beam, when the cost of maintaining existing cells is greater than the the incoming metabolic energy and as we age, we slowly drift off the balance beam towards the end of life. We have through the advent of better healthcare, access to clean water and sanitation, managed to increase the number of years a human can expect to live, however we have not managed to delay falling off the balance beam indefinitely. (Hopefully one day technology might help up move up from the balance beam)</p><p>Unlike us humans, a company on the other hand, has two possibilities:</p><blockquote>Either, it can fall off the balance beam towards the end of life because the cost of doing business is a lot higher than incoming capital. This can happen for many reason: <strong>your customer´s preferences change, your customers adopt another product, or your product no longer meets the needs of your your customer.</strong></blockquote><p>Or,</p><blockquote>You manage to go upwards from the balance beam, extending life of your company. That is the aim of this mini-blog series.</blockquote><p>Falling off the balance beam can be described in many ways, but I define it as losing marketshare for consecutive years to a point when you are not able to recover whilst new entrants or other incumbents in the market are consistently meeting customer needs so that their revenue and market share increases.</p><p>To exemplify this, we can think of the classic case study examples: Apple vs Blackberry, Netflix vs Blockbuster, Facebook vs MySpace.</p><p>What follows is a series of short essays that provide a guide on how to think about things that matters when building a company that lasts — prevents it from falling off the balance beam.</p><p>These are the topics I am writing about — I will release them as and when they are ready. These chapters can be read in isolation.</p><ul><li>Intro: How to build a company that lasts</li><li>#1 Why do you exist</li><li>#2 Bold leaders double down</li><li>#3 Do you know your competitors</li><li>#4 Short-term money dilemma</li><li>#5 The right way to increase your company´s worth</li><li><a href="https://varun-mittal.medium.com/5-the-big-deal-with-innovation-1f905f969994">#6 The first rule of innovation is: you don´t talk about innovation</a></li><li><a href="https://medium.com/swlh/we-don-t-build-feature-here-the-secret-to-empower-and-align-teams-using-the-vision-tree-cc8302684f51">#7 How to align your entire team and empower them</a></li><li>#8 Company-centric metrics vs user-centric metrics</li><li>#9 Build teams that help customers make progress</li><li>#10 How to escape when you´re stuck in a rut</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2246c1ce399" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why should you care about personalisation and customer experience?]]></title>
            <link>https://medium.datadriveninvestor.com/why-should-you-care-about-personalisation-and-customer-experience-7f0b8f778068?source=rss-90dd3373cfcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f0b8f778068</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Varun Mittal]]></dc:creator>
            <pubDate>Tue, 05 Jan 2021 21:58:34 GMT</pubDate>
            <atom:updated>2021-02-04T14:56:00.523Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why should you care about personalisation and customer experience</h3><p>Online marketplaces and platforms have grown substantially and online purchases of goods and services in 2019 accounted for an estimated total of 1.92 billion.</p><p>Technology today has become democratised to an extent where it is no longer the differentiator. People rarely need write code or algorithms from the ground up — for much is easily available via open source repositories that can be duplicated or branched. The thing that is difficult to replicate is the experience marketplaces can provide to its customers.</p><blockquote>Marketplaces that will succeed in this decade won´t be the ones with the latest or shiny technology, but those that can offer the customer delightful experiences. For every marketplace has access to the same technology.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lcjEBLyc8veUIK4f.jpg" /></figure><p>Personalisation is one aspect of customer experience, a very crucial one. In order to demonstrate, lets create a parallel — online marketplace experience to one in a restaurant. You go, you dine, pay and leave.</p><p>You often fail to acknowledge that going to a restaurant is a lot more than that. We leave much more than a payment and a tip — we leave our footprint.</p><h3>Your visit to Restaurant: Lamu 🥘🍱🍢🍸</h3><blockquote><strong>Visit 1:</strong> You go to a restaurant; the hostess tell you to wait 15 minutes until your table is ready; you sit at the table; you order food; you pay the bill and leave.</blockquote><blockquote>If you liked the food, so you will go back.</blockquote><blockquote><strong>Visit 2:</strong> The hostess don´t remember who you are; takes you to your table after a 10 minute wait; you order some food; pay the bill and leave.</blockquote><blockquote>(You went back because of the food, not because of the service)</blockquote><blockquote><strong>Visit 3:</strong> On your 3rd visit, the chef happens to be sick, so there is a different chef. The food this time ends up being mediocre. You pay the bill, and leave.</blockquote><h3>Your visit to restaurant: Milliways 🥘🌮🍱🍢🍸🍹🍾</h3><blockquote><strong>Visit 1:</strong> You walk into the the restaurant; tell the hostess about your reservation. <br>You don’t have to wait; she shows you to your table. She pours water; helps you with the napkins and freshly baked bread. Leaves you with the menu and the wine list 🍷📖. She tells you about her favourites and asks about any allergies you might have.</blockquote><blockquote>She returns a little while later; takes your order; the food is served without an unsatisfactory wait. Your wine glasses is always topped up. Not one moment goes by where you feel something is lacking.</blockquote><blockquote>The hostess even gives you a small glass of their house champagne and dessert on the house.</blockquote><blockquote>(You think to yourself not the food but the service too was exceptional. The staff was courteous and cared about making you feel special)</blockquote><blockquote><strong>Visit 2: </strong>You walk into the restaurant, the hotness actually remember you and asks if you would prefer to have the same table as last time or try another part of the restaurant.</blockquote><blockquote>She remembers which wine you ordered last time and suggests a wine which you might like based on that purchase. She even recalled your fish allergy and suggests a menu to accommodate that.</blockquote><blockquote>(You feel that the restaurant knows you really well and takes care of all your wishes)</blockquote><blockquote><strong>Visit 3:</strong> Same experience as before. The hostess remembers you, shows you to your table.</blockquote><blockquote>But this time the chef is sick so there is a replacement and the food ends up being not so good.</blockquote><h3>The big question: which restaurant do you pick for the 4th visit?</h3><p>The first two visits at both restaurants were splendid. The image of the delicious food served on your 1st and 2nd visits are the things of the past. You can barely remember.</p><p>The only thing that kept you going back to Lamu was the food, i.e. the product. The day the product failed to meet your needs, you will trade future visits for a new restaurant (new product).</p><p>If you’re like most people, when Milliways failed to deliver delicious food, you might be inclined to overlook the poor product because the experience of being at their pleasing to your senses. The fact the hostess remembered your name, the wine you usually order, the fact you’re allergic to fish, left an impression on you. You know they have your best interest at heart.</p><p>Returning our focus back to the online marketplaces and platforms. Much like Milliways, customers are more forgiving and willing to overlook occassional poor product mistake given they have a pleasurable experience otherwise. If you on the other hand you don´t focus on the customer experience, and you entire reputation is relying on your product, the day your product fails, customer will run to the next product.</p><p>In this era, the companies who will succeed are the one who are able to offer a truly memorable and pleasing experience to the customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iG98ZEV2_xALyBOD.jpg" /></figure><h3><strong>Tl;dr</strong></h3><p>For online marketplaces, customers generate troves of data and leave a footprint. Companies should this to provide a tailored experience for the next time we come in to their online store. Luckily many companies are doing this already and it will improve even more over the years.</p><p>Companies that are able to build proactive systems for personalisation are bound to see customers acquiring more of their products. <strong>Personalisation leads to acquisition.</strong> This should come as no surprise because we all expect “special treatment”, much like how Milliways treated its customers making them feel special. Those that enable this special treatment for customers will see the biggest boost in performance and returning customers.</p><p>Most people today — through the mass adoption of mobiles and digital products — have a clear definition of what they believe to be a good experience on the web and mobile, with a set of standards that they apply to all products. This creates an expectation that spills over to all other products they try and drives customers to leave a website within minutes if its unattractive, difficult to use or offers a poor experience. This trend is forcing more businesses to redesign their products that offer a pleasing experience and is personalised to a point it helps customers make progress but isn´t creepy.</p><p>Today, if you have a poor experience on eBay or Gumtree, or find their website is ancient and difficult to use, you´re bound to switch to another marketplace like Amazon.</p><p>I believe customers will stop placing their loyalty amongst known brands, but rather on the overall experience. Online marketplaces and platforms that are able to differentiate themselves through a meaningful and personalized user experience will benefit the most. For, personalisation leads to acquisition.</p><p><strong>Gain Access to Expert View — </strong><a href="https://datadriveninvestor.com/ddi-intel"><strong>Subscribe to DDI Intel</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f0b8f778068" width="1" height="1" alt=""><hr><p><a href="https://medium.datadriveninvestor.com/why-should-you-care-about-personalisation-and-customer-experience-7f0b8f778068">Why should you care about personalisation and customer experience?</a> was originally published in <a href="https://medium.datadriveninvestor.com/">DataDrivenInvestor</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 2 — How to Work Like an Outcome Team]]></title>
            <link>https://medium.com/swlh/how-to-work-like-an-outcome-team-50843e850e4e?source=rss-90dd3373cfcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/50843e850e4e</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Varun Mittal]]></dc:creator>
            <pubDate>Wed, 18 Nov 2020 21:46:45 GMT</pubDate>
            <atom:updated>2020-11-20T10:02:03.712Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 2 — How to Work Like an Outcome Team</h3><p>In the previous post <a href="https://medium.com/swlh/part-1-the-simplest-explanation-to-outcome-and-feature-teams-90b46ca247ca">The Simplest Explanation to Outcome and Feature Teams</a>, I tried to explain the difference between the two.</p><p>We got to know the two characters of our story: Delivery Dan and Experimenting Eve. Additionally, we learnt that consumer products require a different way of working. Releasing new features does not necessarily increase value for the customers. New features can actually make the product more complicated than before and customers might even struggle to use the product.</p><p>Now suppose both Dan and Eve started working for product teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*YUaHnDLD4j81vbDlxk4ICw.png" /></figure><p>Delivery Dan will care about <strong>delivering features</strong> <em>(feature teams)</em><strong>📦🚚</strong></p><p>Experimenting Eve will want to ensure her <strong>customers make progress</strong> <em>(outcome teams) </em><strong>🚀🎯</strong></p><blockquote><strong>For all matters, outcome teams could be called mission teams, impact teams — or by any other name, the name is not important, — for it is the mandate for teams which is the centerpiece, which is to deliver value to customers, not features. </strong>Think of an outcome as something that has an postive impact on your customers/users, and thereby also your business. Something that you will continue to work towards over time. The solutions to deliver on this outcome will change with time.</blockquote><p>Lets give both Delivery Dan and Experimenting Eve a task and see how they tackle it.</p><h3>Here is the brief:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*TNCMnf1Go6Zp7lIyjggGqQ.png" /><figcaption>Well in the centre of village</figcaption></figure><blockquote>A charity hires you to help increase the standard of living in the village. You notice villagers spend a lot of time walking to the river to carry water.</blockquote><blockquote>The charity believes having a well in the village would allow the villagers to use their time for other activities — ones that would allow them to improve their standard of living.</blockquote><h3><strong>Delivery Dan is on it.</strong></h3><p>Nothing is going to stop him building that well. He takes the brief and breaks it down into various features to deliver and rallies his team on making sure they deliver these on time. Along with the features, he also finds metrics to measure success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8eLyXUaQC9z23aAzlS9xeA.png" /></figure><p><strong>Goal</strong>— <em>Increase standard of living in the village </em><strong>🥅🥇🏆</strong></p><p><strong>Solution</strong>— <em>Build a well</em><strong>💡</strong></p><p><strong>Features to deliver 📦🚚</strong></p><ol><li><em>Hole</em></li><li><em>Casing</em></li><li><em>Brickwork</em></li><li><em>Pump</em></li><li><em>Pulley system</em></li><li><em>Buckets</em></li></ol><p><strong>Metrics for success🎯</strong></p><ol><li><em>Rate of water output</em></li><li><em>Measure capacity</em></li></ol><h3><strong>Experimenting Eve also tries to figure out a solution.</strong></h3><p>She doesn´t rush into thinking about any features to launch but instead spends time thinking about how she wants her customers life to be better. In this case it is about increasing their living standards; she takes a pensive approach to understand what it would take and how could one measure being on the right path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/497/1*3FUsHHUnnBdtNy3-5qvEyA.png" /></figure><p>Here is her method, which we can all apply in increasing value to our customer when we deliver new functionality.</p><h3><strong>#1 Goal 🥅🥇🏆</strong></h3><p>(Where do you want to go; what do you want to achieve?)</p><blockquote><strong>Increase standard of living in the village</strong></blockquote><h3><strong>#2 Write the outcome the team focus on 🚀</strong></h3><p>(<em>Think of an outcome as something that has an impact on your customers/users </em>and thereby also your business<em>. Something that you will continue to work towards over time. The solutions to deliver on this outcome will change with time.)</em></p><blockquote><strong><em>Increase standard of living in the village</em></strong></blockquote><p>Eve ensures that the outcome for her team is aligned with the goal; in this case it is the same.</p><h3><strong>#3 Write hypotheses that could deliver on this outcome 🔬</strong></h3><p>(Write all the hypotheses that could apply to your outcome and goal in #1 and #2)</p><blockquote><strong><em>We think if we can reduce the time villagers take to carry water home, they will have more time to do other things like study that will increase standard of living.</em></strong></blockquote><h3><strong>#4 Write experiments 🧪</strong></h3><p>(Write experiments for each of your hypotheses. Experiments can be features too and their main purpose is to test the hypothesis)</p><ol><li><em>Provide bottled water in the village</em></li><li><em>Put a pipe from the nearest river with a pump</em></li><li><em>Build a well</em></li></ol><h3><strong>#5 Define and measure the relevant metrics</strong> <strong>🎯</strong></h3><p>(Metrics you pick should be truly representative and indicative of progress towards the outcomes you care about. Don´t pick metrics for the sake of having metrics. Stop and think. Make them meaningful.)</p><ol><li>Reduction in time to carry water</li><li>Amount of leisure time</li><li>School enrolment rate</li><li>Adult literacy</li></ol><p>As you can infer from this illustrative case study, to work like an outcome team, like Eve, requires a different mindset.</p><p>Delivery Dan rushed to a solution and started to measure things which were not best suited to evaluate success. Stop and think about it for a minute. Does measuring “Rate of water output” suggest any improvement in standard of living? Unfortunately it does not. If you measure the wrong thing, you will never learn what you are doing wrong, and your next steps will lead you down the wrong path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_5ViaYcnbVPwK3EdTjY1xQ.jpeg" /></figure><p>Consider this for example: after building the well Dan discovers the living standards have not improved for the residents. What do you think Delivery Dan would do next? What would be his next move? Perhaps he would suggest that the pump is below par, and inadequate at pumping water, and we need to install a better pump. A better pump would certainly increase the rate of water output he would say, because that is the metric he is optimising for. For we already know, rate of water output does not improve standard of living.</p><p>An outcome driven team is much akin to Eve´s approach. She didn´t take the brief for granted. She stopped and thought about the goal. Instead of getting started on the idea mentioned in the brief, she thought of it as a hypothesis.</p><blockquote>A <a href="https://en.wikipedia.org/wiki/Hypothesis"><strong>hypothesis</strong></a><strong> </strong>in science is a<strong> proposed explanation to a phenomenon. </strong>Hypotheses are based on observations and thoughts, they are not self-evident. We need to find evidence before relying on them.</blockquote><p>Eve rewrites the brief into a testable hypothesis.</p><blockquote>Brief: “If villagers had a well in the centre of village, they could use their time for other activities”</blockquote><blockquote><strong>Hypothesis: “We think if we can reduce the time villagers take to carry water home, they will have more time to do other things like study that will increase standard of living.”</strong></blockquote><p>She uses this hypothesis to write a number of experiments to find evidence. Experimenting Eve, unlike Delivery Dan, doesn´t believe that building a well will increase the standard of living. There is no proof yet; it is merely a hypothesis. She wants evidence.</p><p>Using experiments which range from being very cheap and easy like distributing bottled water or putting in a pipe from the river instead of building a well right away, she tries to validate if a reduction in time spent carrying water has an affect on standard of living.</p><p>She uses metrics that have a direct correlation with the standard of living — for example “amount of leisure time” or “school enrolment rate”. When she finds a solution that does increase standard of living, she can implement it and make it work for the residents and the charity.</p><p>This way of working, also allows her freedom when all her experiments fail. Where Delivery Dan was stuck, the only suggestion he had up his arsenal was a new, fancier pump; Eve writes a new hypothesis: “<strong>We can increase living standard if more people could attend school at night after finishing their daily chores.” </strong>She will then be able to create new experiments to validate or invalidate this.</p><p>Delivery Dan, after implementing the features (the well components), will continue to add more features like better pump, fancier pulley system without ever knowing if the standard of living is actually improving for village residents because he is measuring “rate of water output” and will optimise all new features with that aim — <strong>increase rate of water output</strong>.</p><p>Delivery Dan, knowingly or unknowingly mistakes “making stuff” for making progress and mistakes building well for being done. Eve measures success using the correct metrics and will not stop until she improves lives of the residents.</p><p>I must emphasis, that Delivery Dan also has good intentions but unfortunately his methods are not the best fit for delivering customer value.</p><p>If you have made this far, another examples using Airbnb. Can you spot the difference between the two approaches? Which one would have a more positive impact on customer and thereby the business itself?</p><blockquote>🥅 <strong>Goal:</strong> Increase number of guests on Airbnb</blockquote><blockquote>🚀 <strong>Team Outcome: </strong>Convince first time guests to use Airbnb</blockquote><blockquote>🔬<strong>Hypothesis</strong>: Travellers often judge the Airbnb based on photos and having good photos will increase the chance of bookings</blockquote><blockquote>🧪<strong>Experiment 1</strong> Provide a list of local photographers</blockquote><blockquote>🧪<strong>Experiment 2</strong> Send a photographer to take photos</blockquote><blockquote>🧪<strong>Experiment 3</strong> Write a blog telling people how to take photos</blockquote><blockquote>🎯<strong>Metric:</strong> #5000 new guests/per week</blockquote><blockquote>🥅 <strong>Goal:</strong> Increase number of guests on Airbnb</blockquote><blockquote>📦 <strong>Feature</strong>: Build a machine learning tool that makes apartment photo look good</blockquote><blockquote>🎯<strong>Metric</strong>: #photos optimised using new tool</blockquote><h3>Tl;dr</h3><p><strong>For all matters, outcome teams could be called mission teams, impact teams — or by any other name, the name is not important, — for it is the mandate for teams which is the focus, which is to deliver value to customers, not features. </strong>Think of an outcome as something that has an impact on your customers/users. Something that you will continue to work towards over time. The solutions to deliver on this outcome will change over time.</p><h3>5 steps to working like Experimenting Eve</h3><p><strong>#1 Goal you want to reach 🥅🥇🏆</strong></p><p><strong>#2 Write the outcome the team focus on 🚀</strong></p><p><strong>#3 Write hypothesis that could deliver on this outcome 🔬</strong></p><p><strong>#4 Write experiments and features to test hypothesis 🧪</strong></p><p><strong>#5 Define and measure the relevant metrics</strong> <strong>🎯</strong></p><p>This is my thesis on how I think we could be more like Eve and help improve the lives of our customers. They don´t care about features, they care of making progress.</p><p>Next — Reasons why feature teams struggle to transform into outcome teams (coming soon)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50843e850e4e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/how-to-work-like-an-outcome-team-50843e850e4e">Part 2 — How to Work Like an Outcome Team</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[Part 1 — The Simplest Explanation to Outcome and Feature Teams]]></title>
            <link>https://medium.com/swlh/part-1-the-simplest-explanation-to-outcome-and-feature-teams-90b46ca247ca?source=rss-90dd3373cfcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/90b46ca247ca</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Varun Mittal]]></dc:creator>
            <pubDate>Thu, 12 Nov 2020 11:44:14 GMT</pubDate>
            <atom:updated>2020-11-18T21:48:36.286Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 1 — The Simplest Explanation to Outcome and Feature Teams</h3><p>There is a lot of talk about being an outcome team or a feature team in product companies these days. But what does that mean, which one is better and why should you care?</p><p>First, let me start by trying to explain the difference between the two from my own experience in a completely different environment to product development.</p><p>A couple of years ago I moved to Oslo from London. As many of you will know, moving to another country and not speaking the local language can hinder communication and sometimes give you the sense of missing out or feeling left out.</p><p>If you have been in a similar situation, you might have decided to sign up to language course. That is what I did.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tc-R9fUizvLU9gkj95h9QQ.png" /></figure><p>I went to my first class, excited to learn. There was a teacher, lets call him Dan and his job I presume, was to teach the language or at least help increase my proficiency beyond the status quo. That shouldn´t be too hard.</p><p>The course consisted of 2 classes per week for 6 weeks. Each class lasted 2 hours. That´s 24 hours altogeher.</p><p>I attended the first class on Monday where Dan broke down the 2 hour class like so:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*C0peppPW0SZhhIP3oD_yVg.png" /><figcaption>Dan´s breakdown of the 2 hour lesson</figcaption></figure><p>At the end of the class, I was chuffed and left with a sense of accomplishment, having learnt something.</p><p>I returned 2 days later on Wednesday, excited to learn more. The lesson unfolded in a similar manner and 2 hours later I walked out of the classroom, having made some progress. This went on for another 2 weeks and I began to notice that my progress had plateaued, and each class became very repetitive. It was no longer fun. I start to doubt myself and wonder if I´m really cut out for learning another language.</p><p>When I showed up to the next class, we had a new teacher, lets call her Eve. Dan was on sick leave.</p><p>I noticed that Eve had a very different style of teaching. She organised the lessons in a very different way.</p><p>We started with a youtube video about a local commercial, followed with 20 minutes of a sitcom. Opening the newspaper, reading it together and analysing world politics.</p><p>At the end, she asked us to complete a quick feedback form, asking what we found engaging, what we felt worked and what didn´t. I left the class feeling having learnt something again.</p><p>Whence I returned to the next class, I was not entirely sure how this was going to turn out. Much to my surprise, Eve had planned a whole new lesson.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YK9MtMz2ZIu5N8sLCqHrlg.png" /><figcaption>Eve trying different things to see what helps the students learn</figcaption></figure><p>She seemed be experimenting and gathering what works and doesn´t work with her students. Her lessons varied a lot.</p><p>If you have managed to follow along this far, you will be wondering what does any of this have to do with outcome teams or feature teams. Some might have figured it out, but if you haven&#39;t, here is the approach the two teacher followed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*8KFG-ySD1Ic_hZsi-zJn5g.png" /></figure><p><strong>Delivery Dan</strong>: <em>Sat down, realised he had to deliver 24 hours of lessons. Created a plan to deliver a lesson and repeated the same plan for all the lesson.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/561/1*_PW6ri5LR89QLUvZ-vy6Ow.png" /></figure><p><strong>Experimenting Eve</strong>: <em>Sat down, realised she has 24 hours to help people learn the language. I will try different approaches and see what works. I will try to learn from each lesson and see how I can introduce new ways to help my students learn.</em></p><p>See the difference between the two approaches: where Dan focused more on delivering lessons, Eve cared about helping the students learn more.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/845/1*2sIsbrDLKlcmo5L2qwM54A.png" /></figure><p>If we translate this into product development. Delivery Dan is what you would refer to as a feature team. Delivering features is the sole purpose. They ship one feature after the other.</p><p>Experimenting Eve is focused on an outcome. She cares about if her students learn the language or not. <strong>Similarly, outcome teams care more about helping their customers make progress and get value from their products. </strong>They constantly experiment and measure progress. Iterate, add and remove functionality.</p><p>Ultimately, everyone in product teams wants to help their customers get the most out of their product and continuously increase the value they provide.</p><p>So one might ask, shouldn´t everyone in product development be more like Experimenting Eve and care about outcomes?</p><p>The answer is yes, but unfortunately there are a lot of teams that are more like Deliver Dan. No one is to blame, we just need to understand how we ended up here and change our thinking. To do that we must go back in time.</p><p>Before software or software products become so central to our lives, they were primarily made for business purposes. Businesses would sell to other businesses (like Salesforce, IBM, Jira), often known as B2B.</p><p>When your focus is B2B, each customer usually has 10–1000s of users. In order to attract a new customer (10-1000s of users), you usually had to build a new feature specific to the needs of that customer in order for them to buy your product.</p><p>So the revenue graph would look something like this, where an additional feature meant more revenue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/740/1*a9gYR8zbupv-lvvYrMff0g.png" /></figure><p>Slowly, with the proliferation of internet and consumer (people like me and you) having more connected devices (phones, laptops, TVs, watches etc), more and more companies started to focus on consumer products. This meant a business would build a product it can sell directly to consumers— some examplar products are spotify, netflix, uber and the like. This meant instead of having a business-to-business relation, you instead had a business-to-consumer relationship, known as B2C.</p><p>The goal for most companies is to create user value, or at least enough value that the customers keep using your product and paying for it.</p><p>Where we struggled was to understand how to keep creating value and acquire new customers as well as keep the existing ones satisfied. We started to conflate value with features. The legacy from the past kicked in, where addition features use to mean new customers which in-turn meant more revenue.</p><p>Instead, the graph looks more like this. Success is now measured by value delivered to customers and not number of features delivered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PBzN1aacRWcCCfz5g2wrLQ.png" /></figure><p>Feature teams might deliver more features than outcome teams but they don´t necessarily create more value for theie users. B2C products requires a different way of working. We need to be more like Experimenting Eve and care about outcomes. We should be focused on helping our customers make progress via our product.</p><p>To get new customers or satisfying existing ones is about simplification of our value offering, making beautiful products that are easy to use and helping customers make progress. It is less about increasing the number of features but understanding customer pain points and removing friction.</p><p><a href="https://varun-mittal.medium.com/how-to-work-like-an-outcome-team-50843e850e4e">Next— How to work like an outcome team</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90b46ca247ca" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/part-1-the-simplest-explanation-to-outcome-and-feature-teams-90b46ca247ca">Part 1 — The Simplest Explanation to Outcome and Feature Teams</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[The Secret to Empower and Align Teams Using the Vision Tree]]></title>
            <link>https://medium.com/swlh/we-don-t-build-feature-here-the-secret-to-empower-and-align-teams-using-the-vision-tree-cc8302684f51?source=rss-90dd3373cfcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc8302684f51</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Varun Mittal]]></dc:creator>
            <pubDate>Sun, 18 Oct 2020 12:10:37 GMT</pubDate>
            <atom:updated>2021-03-24T11:13:23.470Z</atom:updated>
            <content:encoded><![CDATA[<h3>#7 The Secret to Empowering and Aligning Teams Using the Vision Tree</h3><p>After another disappointment at the rowing world championships in 1998, something had to change for the Great Britain mens rowing team. Last time the GB Men’s Eight won an Olympics gold medal was in Stockholm 1912. If they continued to do what they had always done, they would continue to get what they had always gotten.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EbndFyOyXIScX5W2m9IlzA.jpeg" /><figcaption>Credit: Peter Spurrier</figcaption></figure><p>Then something changed. Preparing for the 2000 Olympics, they tried a new approach. The team developed a new strategy and went from being average to gold medalists in the Sydney Olympics 2000.</p><p>Within their one simple strategy, there lay many critical elements to success. People mistakenly presume it is all about the performance on the day of race but in reality it is everything leading up to the day — the way they train, what they eat, how they measure progress, what things they focus on.</p><p>Lots of people are involved and everybody has to make hundreds of decisions. The solution: they tried to answer one question no matter what they did.</p><h3><strong>Will it make the boat go faster?</strong></h3><p>With every decision or opportunity, the team member would try to answer that one question: <strong>Will it make the boat go faster?</strong></p><p>Tempted to have a few beers this Saturday? <strong>Will it make the boat go faster?</strong> No it will not… So no beers.</p><p>Should I have chicken or salmon for dinner? <strong>Will it make the boat go faster? </strong>They are both healthy options, pick any.</p><p>This meant that each team member could take autonomous decisions, and follow opportunities and still keep focus on the main goal.</p><p>Much like in business, it is not the day the new product is launched, it is everything leading up to the moment. The big question is, how can you align teams to focus on the big business goal and still have autonomy to make the right decisions and follow opportunities?</p><h3>Build Something People Want</h3><p>One of the hardest things working in a cross-functional team is talking the same lingo. People in various roles struggle to tie their work to the company´s overall goals and ambitions. I think of this as the “silver burrito” problem — a clever marketing stunt where you can get everyone to imagine a different burrito inside the wrapping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*v0GqdlbYr7qzPuRPObbRjQ.jpeg" /><figcaption>Silver burrito — everybody imagines a different burrito inside it</figcaption></figure><p>People at every level in your business have to make tens or hundreds of decisions everyday, how can you help them make the right decisions? As a product leader your role is to align everyone in the team or company to speak the same language. How do you get everyone to focus on solving real problems and not making micro-incremental changes. How do you get your team to make a step change and create something that truly delights people.</p><p>We have all fallen prey to feature exhaustion (<a href="https://www.youtube.com/watch?v=Hr1rN3jibIk&amp;t=665s">watch Jared Spool</a> explain this in his insightful talk, Building a Winning UX Strategy), to a point our product has become too complicated for people to use. This is usually when a startup focusing on a specific problem launches a simple to use product and wins over the audience. Sometime we are cognisant of this and clean up our product offerings but most of the time we do nothing.</p><p>I propose a methodology I call <strong><em>“The Vision Tree”</em></strong> which I have adopted to align everyone and pull in the same direction. It is way to connect and map everything that we do with the product/company <strong>vision. </strong>We break the vision down into tangible goals; goals are made up of various <strong>outcomes; </strong>to reach each outcome, we have<strong> </strong>various <strong>hypotheses or customer problems</strong>; hypotheses are verified and tested using <strong>experiments</strong>. In order to make sense of the methodology, I will try to follow along with examples I have created using Airbnb as the case study(this might not be the actual mapping for Airbnb but easy to understand for all of us).</p><p>Lets define each of the aforementioned terms along with an example and then we will put it all together at the end.</p><h3><strong>1. Vision</strong></h3><p>What is the future you want to create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fc3Fxe7gSMRJgSewVDRSTQ.jpeg" /><figcaption>Vision for tomorrow for Airbnb</figcaption></figure><p>A side note: Simon Sinek in his book The Infinite Game, talks about “moon landings” not being a vision or just cause. So JFK´s “land a man on the moon, before this decade is out and return him safely to Earth” is more like a concrete goal and less like a vision. (If you have time, I still recommend you watch the <a href="https://www.youtube.com/watch?v=TuW4oGKzVKc">inspiring speech</a> by JFK or continue reading).</p><p>Vision is about the future, it describes a world we hope to live in. It´s a vision that doesn´t yet exist and it should be a future so appealing that people are willing to make sacrifices in order to advance it.</p><h3>2. <strong>Goal</strong></h3><p>These are defined as concrete and measurable business goals we would need to achieve to realise our vision.</p><p>For each goal you should have a key metric to know when you have successfully met this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qqpa-VQ3mm3aLBkIg7Q4Ww.jpeg" /><figcaption>Break the vision down to business goals</figcaption></figure><h3>3. <strong>Outcomes</strong></h3><p>This is what is defined as a change in human behaviour that drives business results. They shouldn´t change over time and they are definitely not a feature.</p><p>Like we did for each business goal, create a lever or metric for each outcomes. This is how you define success for each of the outcomes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*elOAs2pB-VyIR1vj7gsMWg.jpeg" /><figcaption>Outcomes and metrics for the business goal: Increase total bookings on Airbnb</figcaption></figure><p><strong>A quick note on leading vs lagging indicators.</strong></p><blockquote>If we measure revenue, it is what we call a lagging indicator i.e. we only know what the customer have done in the past and it is bad proxy to predict the future behaviour.</blockquote><blockquote>If we can demonstrate that newsletter opens predict return visits, then newsletter opens becomes a leading indicator. These leading indicators are much better at predicting the success of our experiments to test the hypothesis.</blockquote><p>So for each outcome you should try to have at least one leading indicator you guide decision making.</p><h3>4. <strong>Writing hypotheses</strong></h3><p>A good hypothesis should have two parts:</p><ul><li>What we believe</li><li>The evidence we need in order to know if we are right or wrong</li><li>Eg. Travellers often judge the Airbnb based on photos and having good photos will increase the chance of bookings. We will see if this moves us closer to the 5000 new guests/per week.</li><li>Eg. Travellers are reluctant to try something for the first time so if we can reduce the cost of them trying Airbnb, we can increase first time guests. We will see if this moves us closer to the 5000 new guests/per week.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0ageHDkhXBoRNN-xQv9-9w.jpeg" /><figcaption>Hypothesis with insights</figcaption></figure><h3>5. <strong>Experiments</strong></h3><p>Think of these as the various way of testing and finding evidence to validate or invalidate each of our hypotheses. Experiments can have varying degrees of completion and exactness.</p><ul><li>Mock ups</li><li>Low or high-fidelity prototypes</li><li>A/B tests</li><li>MVPs</li><li>Wizard of Oz</li><li>New features</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ytZ6MHUH7_nLpDmFlZbGYw.jpeg" /></figure><h3>Vision to Experiment Tree</h3><p>Putting it all together, we can map the vision down to each experiment or feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1EnklxCDXJYzKDOlsLzI7w.jpeg" /><figcaption>Vision to experiment tree</figcaption></figure><p>This is a way of empowering and aligning an entire team to look at the bigger picture. When more people in your team are empowered to contribute, the chance of innovative solutions goes up.</p><p>Can you endow people in your team or company, a version of <strong>“will it make the boat go faster?”</strong>. Sometimes it might not be as simple as that if you have a very diverse business, but you should have levers or metrics your team can focus on and use to navigate every day. For example, the metrics set for the outcomes in the aforementioned Airbnb case study, are a good starting point.</p><p>People in your team can look at each outcome and think of various hypotheses and experiments/features to try to move the needle for the outcome metric. When you run these experiments to test hypotheses, those that successfully move the needle in the right direction, should become part of your product.</p><p>While it may be tempting to persevere with those failing features, you should really consider abandoning them. It might be disheartening to nip a blooming bud especially if it shows some promise. If it isn´t sufficiently moving the outcome metrics, it doesn´t deserve your attention. Walt Disney went to great lengths to ensure his creative teams properly vetted and killed ideas when necessary. There is even a phrase for this in the literary world by Stephen King:</p><blockquote>“<strong>Kill your darlings</strong>, <strong>kill your darlings</strong>, even when it breaks <strong>your</strong> egocentric little scribbler’s heart, <strong>kill your darlings</strong>.”</blockquote><p>I found this methodology helps to connect the work everyone does with the business goals. Gives everyone a version of <strong>“will it make the boat go faster”</strong> to make faster and better decisions. You avoid being stuck in a rut if a particular set of features doesn’t work.</p><p>Most of the time, I notice product teams fall in love with a solution and spend a lot of time developing the feature and get super excited to launch it. When the uptake of the feature is limited, they keep tweaking it and A/B testing variations. This usually happens over a year or so before someone decides to introduce a new feature. A/B tests are usually done on traffic and not necessarily if it solves a customer problem or not. With the vision tree method, you can use the parent hypothesis, and new insights, to try another experiment with a different approach.</p><p>If we look at the Airbnb example from above, <strong>our initial hypothesis </strong>was:</p><blockquote>Travellers are siloed across the city when travel and would have a better time if they could hang out with other travellers. Airbnb trips would be significantly more meaningful if they could meet other traveller.</blockquote><p><strong>Experiment/Feature we launched</strong>: Organise meet ups and invite other travellers to meet each other.</p><p><strong>Insights/Results from the experiment:</strong></p><blockquote>Travellers don’t necessarily enjoy hanging out with other travellers, but instead travellers want to find high quality non-tourist things to do. Hanging out with other travellers is one solution, not the actual problem. Later they launched Airbnb Experiences which has been tremendously successful.</blockquote><p>Next experiment/feature experiment: <strong>Organise events held by locals</strong></p><p>We know that was extremely successful and evolved into Airbnb Experiences.</p><p>Everyone talks about moving fast and solving customer problems but most teams start with a solution in mind and reverse engineer a problem. When that happens and the feature doesn’t work, you are left with few moves.</p><p>Using the vision tree method above, you can align your entire team and remove yourself from being the bottleneck and at the same time ensure everyone is pulling in the same direction.</p><p>The alternative is to micromanage everyone and tell them exactly what feature to develop every day and keep developing features until your product is so complicated, people struggle to use it. Just remember, this is not inspiring for the team, no one understands how their work ties to the company goals. Also this is very taxing on your time.</p><p>When it comes to products, I like to use the words of Antoine de Saint Exupery:</p><blockquote>Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.</blockquote><p>You can apply this thinking, not only to business but also personal goals you want to achieve.</p><p>TL;DR</p><p>To align your entire team and empower them, give a version of <strong>“will it make the boat go faster”</strong> to make decisions and map everything from your vision to the experiments/features you work on.</p><ol><li>Have an inspiring vision so appealing people are willing to make sacrifices to advance it</li><li>Have a concrete business goal and a key metric to measure success (lagging indicator)</li><li>Write outcomes that drive the business goal (outcomes usually don´t change over time but how they are solved does)</li><li>Create metrics for each outcomes (leading indicator)</li><li>Write hypothesis to realise each of the outcomes</li><li>Create experiments (features, mock-ups, minimum awesome products) to test your hypothesis and see if you can move the levers you created for each outcome</li><li>Only keep the features that have an impact on the outcome metric. Kill all other features.</li></ol><p>Continue with the series</p><ul><li><a href="https://varun-mittal.medium.com/how-to-build-a-company-that-lasts-e2246c1ce399">Intro: How to build a company that lasts</a></li><li>#1 Why do you exist</li><li>#2 Bold leaders double down</li><li>#3 Do you know your competitors</li><li>#4 Short-term money dilemma</li><li>#5 The right way to increase your company´s worth</li><li><a href="https://varun-mittal.medium.com/5-the-big-deal-with-innovation-1f905f969994">#6 The first rule of innovation is: you don´t talk about innovation</a></li><li>#7 How to align your entire team and empower them</li><li>#8 Company-centric metrics vs user-centric metrics</li><li>#9 Build teams that help customers make progress</li><li>#10 How to escape when you´re stuck in a rut</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc8302684f51" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/we-don-t-build-feature-here-the-secret-to-empower-and-align-teams-using-the-vision-tree-cc8302684f51">The Secret to Empower and Align Teams Using the Vision Tree</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[What I learnt about building software from Stranger Things]]></title>
            <link>https://medium.com/swlh/what-i-learnt-about-building-software-from-stranger-things-21ff8da49c9e?source=rss-90dd3373cfcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/21ff8da49c9e</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[vision]]></category>
            <category><![CDATA[stranger-things]]></category>
            <dc:creator><![CDATA[Varun Mittal]]></dc:creator>
            <pubDate>Tue, 05 Nov 2019 14:22:01 GMT</pubDate>
            <atom:updated>2019-11-06T11:17:02.916Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Tv7DWS_mZ8VEoXTASl_uzw.jpeg" /></figure><p>I can say this on behalf of almost everyone, by the time the credits roll at the end of the movie or TV show, we leave or switch to something else. Never quite appreciating the village of people involved in making that movie or TV show.</p><p>After I finished watching Stranger Things, they had created spotlights on various aspects on how the show was made which I recommend you watch. They focused on design, character choice, director, special effects, camera angles, photography; however, what was central to all the spotlights was the vision and story presented by the writers and producers, The Duffer Brothers. This was the moment I realised that making a good TV shows is much like building software products customers love.</p><p>To explain my thinking, I will borrow the concept of the golden circle approach by Simon Sinek.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*srO7E7K_NrWXf6OC1pk6pg.png" /><figcaption>Golden Circle</figcaption></figure><p>At the core is the WHY (what’s your vision, what do you really want to achieve), and then comes HOW (the various teams, process and systems involved in bringing your cause to life) and finally, the WHAT (the product you ship to your audience).</p><p>To exemplify, I have created a golden circle for Stranger Things below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-oyGKPF6QE2po2U_vuUZEQ.png" /></figure><p>Imagine a world where such a structure didn’t exist and the producer/director decided to instruct the camera director which angle to hold the camera and where to take the shot, to the visual effects team on how to light a particular scene, telling the sound director which songs to include for each scene, commanding the designers to find newspapers and household items that would resemble a typical household in the 1990s. Sure, they might be able to put together a TV show but at best, it would be mediocre and nothing more. Not only is it exhausting telling others what to do every single day, you fail to utilise their expanse of knowledge and experience in their relevant departments.</p><p>Here is how the Duffer Brothers did it. They started with a very strong vision and story line of what they wanted to achieve. They didn’t go around instructing the camera director, the visual effects team, the editors, the sound director what to do, they instead presented their vision and script of the TV show which should also resemble the movies they love and grew up watching in the 80s and 90s. They trusted the people they hired to know their ends of the things in terms of execution. The village of people involved in making the show used their knowledge and experience to deliver to that vision.</p><p>Their production designer, Chris Trujillo and his team was in charge of creating the sets that would depict the plot and they kept referring to the script (the vision) to find the needed inspiration for what to do. To create an authentic set that represent a particular time period requires a 1000 decisions — that sheet on the bed, the cassette tape on the bedroom dresser, the newspapers on the breakfast table, wallpaper, floor finishes, coffee cups and so much more. To a point that you could point the camera anywhere and find very specific objects that would represent the character. All this was possible because the Duffer Brothers pained a very clear vision and story for everyone to follow.</p><p>Same when it comes to Director of Photography, Tim Ives. There are so many details when it comes to filming that have never occurred to me before, like what style of camera movements or style of lenses to use. The answer to that question, the vision of the Duffer Brothers. Some scenes describe a region that’s neither here nor there, something devoid of any sort of life, that it felt nothing existed there. How do you find a way to represent that. Should the writer instruct the director of photography how to light this scene or let the experts work it out. In this case photography team decided to light it in a way that there was no discernible light source by rigging a bunch of space lights (like white china balls in the ceiling) and used grid cloth to soften the light. They placed black theatrical drapes all the way around somekind of hockey rink with a lip of water to get the reflection of anybody that was there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xBRM6mgekdNvfJ_aZjH6OQ.jpeg" /><figcaption>A region devoid of any life</figcaption></figure><p>The Duffer Brother’s philosophy was to hire people who know more about an area and are more talented in that department than you and let them do their thing — that is when magic happens. They are open to ideas from all other people and the best idea always wins. The result, a TV show which got 8.8 on IMDB and 93% from Rotten tomatoes.</p><p>This is exactly what we should be doing when building software — by starting with a strong vision. The CEO and product leaders should be the embodiment of the product vision so that everyone in different departments can do things they are good at, to deliver on that vision.</p><blockquote><em>Steve Jobs famously said,</em> <strong>“ It doesn’t make sense to hire smart people and tell them what to do; we hire smart people so they can tell us what to do”</strong></blockquote><p>Most companies spend a lot of energy and effort to hire smart people to help them build the right products. However we often end up telling them what to do. I am guilty of this myself - on occasions I asked developers and designers to simply add a new button or build a feature without painting a vision or customer problem to them. Luckily I have learnt from my mistakes and now I start with the problem first and present the bigger picture so the entire team can focus on how best to solve that problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cGac1otw6_DRamjM-mCbSw.png" /></figure><p>The CEO of the company and product leaders need to be very good at articulating the vision so that all the teams can pull in one direction. When you are a small team of 2 or 3 people it is easy to focus and share the vision because the founder often sits very close and talk about their reason for existence all the time and what problems they are solving. However, as that team increases to even 20-30 people, and leaders try to follow revenue avenues, the vision gets blurry, and often resorts to telling people which specific things to do — like build this new feature because a customer is requesting this, or do a new marketing campaign so we can sell more of this product with a new feature. You may be able to manipulate the market and customers for the short term but it doesn’t guarantee any long term success.</p><p>For long term success, the leaders have to have a strong vision so that everyone can make concerted efforts in the same direction. The designers can think about the user experience and design that will deliver on that vision, the sales team can attract and speak to the customers who buy into that vision rather than waste time speaking to an arbitrary list of customers, the marketing team can send a focused message to those who are attracted to the vision. By having a strong vision, you needn’t have everything planned upfront but have a direction you want to pursue or problem you want to solve. This will act as the guiding star for your entire team when it comes to decision making.</p><p>If the vision, the how (the various teams and systems) and the what (the product features and design) are tightly aligned, then the team succeeds. If they aren’t in harmony, there chaos, time is wasted in endless discussions and at best they make a mediocre product that somehow floats along but never making a name nor money.</p><blockquote>You hire people who know more and are more talented in their departments than you are and you let them do their thing — that is when magic happens. So present a clear vision and a story to your team.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21ff8da49c9e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/what-i-learnt-about-building-software-from-stranger-things-21ff8da49c9e">What I learnt about building software from Stranger Things</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[If you want to build an awesome product, don’t building an all-cuisine restaurant]]></title>
            <link>https://varun-mittal.medium.com/if-you-want-to-build-an-awesome-product-dont-building-an-all-cuisine-restaurant-7a64142b67e7?source=rss-90dd3373cfcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a64142b67e7</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[vision]]></category>
            <category><![CDATA[value-proposition]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Varun Mittal]]></dc:creator>
            <pubDate>Mon, 09 Sep 2019 14:29:41 GMT</pubDate>
            <atom:updated>2019-09-09T18:43:05.136Z</atom:updated>
            <content:encoded><![CDATA[<h3>If you want to build an awesome product, don’t build an all-cuisine restaurant</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*byk1f_vULCImWy03" /><figcaption>Photo by <a href="https://unsplash.com/@alvaroreyes?utm_source=medium&amp;utm_medium=referral">Alvaro Reyes</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>“Great companies are built on great products” — Elon Musk</blockquote><p>The hard truth about start-ups or start-ins: the journey from the initial product idea to market success is riddled with uncertainty. You feel like you’re walking in dark room of unknown dimensions. Every now and then, a light goes on and guides you forward. Not quite a floodlight that illuminates your path, but a spotlight that provides the much-needed comfort and some direction. Embrace these moments, before you know it, more and more spotlights start to turn on and suddenly you’ll get a sense of where you are, where you have travelled and where to go next.</p><p>Finding these spotlights is not easy, it requires great persistence and a lot of walking in the dark.</p><p><strong>So, how do you find these spotlights?</strong></p><p>One way that works for me, is asking the right question. When I feel like I have reached an impasse or lack clarity, the breakthrough usually comes in the form of a different question or rewriting the problem statement than to keep iterating on the original question.</p><p>If you’re trying to make progress with your idea or product, and find you are stuck, start by asking a different question.</p><blockquote><em>Instead of,</em> <strong>“why is no one signing up to our product”</strong><em>, try</em> <strong>“what people could actually benefit from our product?”</strong><em>.</em></blockquote><blockquote><em>Instead of </em><strong>“how much should we charge for this product”</strong><em>, try </em><strong>“how much time/effort do we save our customer if they use our product”</strong><em>.</em></blockquote><p>Try to avoid leading questions because it will bias the response you get. A great book to read on formulating questions correctly, is <a href="http://momtestbook.com/">The Mom Test</a> by Rob Fitzpatrick. Accusatory questions usually result in defensiveness, closed question result in a yes or no answer with no new ways to move forward or spark. The right question is key to increasing your chances of turning on one of those spotlights. When you’re working on building something new, focus on the right question than having all the answers.</p><p>By asking the right question, you may cause friction but don’t expend a lot of energy avoiding it. Rather, you should invite and leverage it, just like stones rubbing together get polished over time, we can also use friction to smooth out the rough edges of our product. Never aim to have a meeting where everyone nods in agreement. Sometime you need disagreements to see the gaps and flaws in your plan. When consensus is easily reached, is it usually because the participants are less interested in the topic; however, when you have disagreements, people are more likely to put in the extra effort on figuring out gaps in their knowledge to understands the reasons for disagreement. This is important, because it means that your team members are more engaged in solving problems and you’re that one step closer to turning on a spotlight. <em>(Side note: if you are interested in learning more about how disagreements urge people to understand more, you can read </em><a href="https://harvardmagazine.com/2012/03/twilight-of-the-lecture"><em>“concept testing” by Eric Mazur</em></a><em>)</em></p><p>One thing we often get wrong (I am guilty of this myself), despite having asked the right question and found one of the spotlights, is that we try to please and accommodate all potential customers. I admit it is hard to say no to a customer when you’re in the early stages of building your product. However, you will learn over time, that trying to accommodate for everyone’s needs only dilutes your product vision and offering. The more you dilute your offering, the less likely it is that your product will revolutionize the industry you’re focusing on.</p><p>Accommodating for everyone makes it hard to have a defining value proposition. I think the food industry figured this one out a long time ago before anyone else did.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6wUBp1FQg-McR7UgbVyYuQ.jpeg" /></figure><p>You always have friends telling you, “there is this really good Indian restaurant I went to yesterday” or “did you hear about the Japanese place that opened last week”. You rarely get recommendation for “that takeaway that opened 2 weeks ago, and sells salads, burgers, pizza, sushi, curries”. Because it is likely going to be nothing more than mediocre. Just like top rated restaurants specialise in one cuisine, make your product unique so your customers know exactly what they can accomplish at the offset.</p><p><strong>Same goes for sports.</strong> You can’t be a champion at more than one sport; you must find <strong>the one sport</strong> that you are really good at and then stick to it. You never see Tiger Woods trying to compete in golfing and skiing. Why is that?</p><p>It is because of the hundreds and thousands of hours of practice, dedication and perseverance it takes to be good at something. If he tried to compete in both golfing and skiing, he would merely be mediocre at both at best. So, it’s no wonder why when you’re trying to build products, and try to be good at everything (solving all your customer’s problems) you end up being very generic and create nothing revolutionary.</p><p>What I am trying to say is that, when building your product, don’t try to please everyone because you will end up not pleasing anyone nor will you get anyone recommending your product to others. Focus on what problem you can be good at solving. When you reach a roadblock, find clarity by asking the right question and don’t be afraid of some friction — it only polishes the rough edges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a64142b67e7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Public transport vs cloud computing, or is it the same?]]></title>
            <link>https://varun-mittal.medium.com/public-transport-vs-cloud-computing-or-is-it-the-same-35323aa69dd9?source=rss-90dd3373cfcc------2</link>
            <guid isPermaLink="false">https://medium.com/p/35323aa69dd9</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Varun Mittal]]></dc:creator>
            <pubDate>Tue, 26 Mar 2019 14:01:08 GMT</pubDate>
            <atom:updated>2019-03-26T14:01:08.952Z</atom:updated>
            <content:encoded><![CDATA[<p>I have recently moved back to London, and need to commute to the office every day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/891/0*mtSTT9dzmjZWi0hq.png" /></figure><p>Having a car is exciting — I will have more control, I will be able to leave home as I please, and use it as much as I want so long as I remember to fill it with fuel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/0*uI5o4CmsWUrBxCqp.png" /></figure><p>But is it the best solution?</p><p>Owning a car has many drawbacks. I will have to pay for parking, pay for fuel, pay for maintenance, pay for repairs when something goes wrong, buy insurance in case I crash or someone breaks into my car, and find parking in central London (that’s always a pain). All this adds up to be pretty expensive.</p><p>My other option is to use the London underground. I can show up at the station with a book in my hand, use my oyster card which has a monthly pass (sometimes I buy a one off ticket), get on the train, not stress about sitting in traffic, get off the train, put my headphones in and walk to the office. It’s London, so I will probably have to scramble to find that umbrella in my bag.</p><p>What’s more, I don’t need to pay for fuel, worry about maintenance, or pay for insurance and never worry about parking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/893/0*rFrUE0vW7gCqCSS6.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/0*HUkv-7nwli8h5pWL.png" /></figure><p>Cloud computing is like using the London underground, and on premise servers like owning a car. Using the cloud, you can pay for the service either on a subscription basis, or just when you need to use it. You don’t need to worry about maintenance, because that is addressed by someone else. Or worry about upgrades or repairs — that is all taken care of and you receive quality service. With regards to crashes or someone breaking in, there is a dedicated team working towards cyber security too, keeping the baddies away.</p><p>In software we are actively pursuing opportunities within software-as-a-service and the cloud. You will be able to log on to one of the SaaS applications and use it as and when you need. Does it make sense to buy a “car” if you only drive it for 2 hours a day? It DOES NOT! With SaaS, the pricing model will likely change to a subscription/consumption/transaction-based pricing model.</p><p>That is why more and more organisations are now realising the value of using cloud computing. As an example of companies that are pushing the technology to the next generation of IT, here is an article from <a href="https://www.mckinsey.com/business-functions/digital-mckinsey/our-insights/managing-it-transformation-on-a-global-scale-an-interview-with-shell-cio-alan-matula">McKinsey which interviewed Shell</a> on their journey to cloud deployment.</p><p>You can use the service from anywhere as long as you have internet access. Whereas if you had a “car” you are restricted i.e. your work might be limited to the office space and you might not be easily able to pick up where you left off from another location or collaborate with colleagues across the world. Using the cloud solves these issues.</p><p>Better for the environment too. When your cloud needs fluctuate, the server capacity scales up and down accordingly. So, you only use the energy you need and don’t leave an oversized carbon footprint.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35323aa69dd9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>