<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="https://www.evanmaxon.com/feed.xml" rel="self" type="application/atom+xml" /><link href="https://www.evanmaxon.com/" rel="alternate" type="text/html" /><updated>2026-08-08T20:53:06+00:00</updated><id>https://www.evanmaxon.com/feed.xml</id><title type="html">Evan Maxon</title><subtitle>I&apos;ve been working in product management and development for over a decade — long before I knew that there was an actual job title for it. This site aims to help new product owners learn the art of owning product so they can find job fulfillment and build products that add value to the lives of others.</subtitle><entry><title type="html">Not All Time Is Equal</title><link href="https://www.evanmaxon.com/blog/not-all-time-is-equal" rel="alternate" type="text/html" title="Not All Time Is Equal" /><published>2023-10-24T15:00:00+00:00</published><updated>2023-10-24T15:00:00+00:00</updated><id>https://www.evanmaxon.com/blog/not-all-time-is-equal</id><content type="html" xml:base="https://www.evanmaxon.com/blog/not-all-time-is-equal"><![CDATA[<p>The adage “time is money” prioritizes a regenerative resource over an irreplaceable one. The statement, and the underlying mindset, ignore opportunity costs. We can always acquire more money, but we can never recapture time.</p>

<h3 id="always-trade-money-for-time">Always trade money for time</h3>

<p>This is the economic basis of companies. Trading money for the time of employees, contractors, and vendors to produce goods and services that, in turn, generate money.</p>

<p>How well is your company spending time?</p>

<p>The obvious answer typically focuses on projects. <em>ALL. THE. PROJECTS.</em> The <em>what</em> you are doing: new projects, initiatives, product development, client selection (or lack thereof).</p>

<p>And yet, it’s not about <em>more</em>.</p>

<blockquote>
  <p>People think focus means saying yes to the thing you’ve got to focus on. But that’s not what it means at all. It means saying no to the hundred other good ideas that there are. You have to pick carefully. <em>I’m actually as proud of the things we haven’t done as the things I have done. Innovation is saying no to 1,000 things.</em><br /><br />Steve Jobs</p>
</blockquote>

<p>Do less.</p>

<p>Do less, better.</p>

<p>Ruthlessly discriminate between what you will do and what you won’t.</p>

<p>Time today is more valuable than time tomorrow. This week is worth more than next week. Both are 168 hours long. Yet, my success next week requires urgency and intentionality now. Next week will be too late.</p>

<blockquote>
  <p>The best time to plant a shade tree was 20 years ago…</p>
</blockquote>

<p>This is crucial: how you spend time now determines the success of your company later.</p>

<h2 id="the-org-chart-of-time">The org chart of time</h2>

<p>Typically, the most expensive time in a company is that of the CEO. This is the role that, generally, the company trades the most money for their time. And a good CEO - one that casts clear vision and creates an environment for employees to execute on that vision - is under compensated.</p>

<p>And even with that being true, the time of the CEO is not the most valuable.</p>

<p>The most valuable time belongs to those directly involved in creating the product or delivering the service. When the do-ers’ time is wasted (<a href="https://www.paulgraham.com/makersschedule.html">meetings</a>, spread too thin on projects, lacking focus, not working on the most valuable work), the company’s ability to deliver on its promises is diminished.</p>

<p>When the United Auto Workers (UAW) go on strike, the auto industry comes to a standstill, restricted to selling from existing inventory. That’s a crystal-clear example of the true value of do-er time.</p>

<p>Ruthlessly protect the do-ers’ time as much as you do your brand, your vision, your company culture.</p>

<h2 id="the-stewardship-of-employee-time">The stewardship of (employee) time</h2>

<p>My charge is to steward (”spend”) the company’s most valuable resource: the time of our developers. My time is not as valuable as that of my development teams.</p>

<p>While it’s not itemized on my job description (maybe it should be?), the most important part of my job is to protect their time and ensure they are working on only the most valuable tasks at any given moment. It also means ensuring that vision and priorities are communicated, blockers removed, and decisions made.</p>

<p>If they work on the wrong thing today, we are that much further from converting their work (their time) into value for our customers. (Who, in turn, pay us. Cash flow is king!)</p>

<h3 id="tldr">tl;dr</h3>

<blockquote>
  <p>The best time to plant a shade tree was 20 years ago. <strong>The second best time is today.</strong><br /><br />ancient proverb</p>
</blockquote>

<p>Time is an irreplaceable resource and more valuable than money. Companies trade money for time, but often misuse the latter by not focusing on the most critical tasks. Prioritize and protect the time of the do-ers, or those directly responsible for creating a product or delivering a service, as this time is the most valuable for the company’s success. Mismanagement of this precious resource will severely affect a company’s ability to deliver value.</p>

<ul>
  <li>Focus. Say no to more so that you can do less, better.</li>
  <li>Optimize the work lives of those that produce revenue generating products.</li>
  <li>Empower those that steward your most valuable resources to say “no” more - to clients, to co-workers, and even to the CEO. 😉</li>
</ul>]]></content><author><name></name></author><category term="mindset," /><category term="lean-startup," /><category term="agility" /><summary type="html"><![CDATA[Prioritize and protect the time of the do-ers, or those directly responsible for creating a product or delivering a service, as this time is the most valuable for the company's success.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.evanmaxon.com/assets/images/avatar.png" /><media:content medium="image" url="https://www.evanmaxon.com/assets/images/avatar.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">On Predictability and Responding to Change</title><link href="https://www.evanmaxon.com/blog/on-predictability-and-responding-to-change" rel="alternate" type="text/html" title="On Predictability and Responding to Change" /><published>2023-06-20T15:00:00+00:00</published><updated>2023-06-20T15:00:00+00:00</updated><id>https://www.evanmaxon.com/blog/on-predictability-and-responding-to-change</id><content type="html" xml:base="https://www.evanmaxon.com/blog/on-predictability-and-responding-to-change"><![CDATA[<p>Choose one. Choose wisely.</p>

<p>An organization that is both highly predictable (the aim of <em>project</em> managers) AND able to easily respond to change (the aim of <em>product</em> managers) <em>does not exist</em>. These capabilities exist in opposition to the other. And, in practice, the relationship is often fraught: project managers become exasperated when the doers can’t (or won’t!) provide a firm date for when something will be delivered; product managers are frustrated because project managers seem not to understand that the future is unpredictable.</p>

<p>We constantly face the challenge of balancing predictability and adaptability. Our evolutionary instinct drives us to seek predictability, but the inherent uncertainty of the world demands adaptability. Both predictability and adaptability have their place, but one must happen before the other is possible.</p>

<h3 id="the-desire-for-predictability-is-innate">The Desire for Predictability is Innate</h3>

<p>The instinctive desire to anticipate the future comes from the early human need to survive. Those sounds in the middle of the night? It was safest to assume they came from a predator and that we should take evasive action. Our survival depended on it.</p>

<p>Over time, we developed strategies such as astrology, palmistry, numerology, and tarot to interpret events and signs in an effort to predict the future. Today, we add project plans to this list.</p>

<p>We construct narratives to make sense of our environment and inform our actions. However, these narratives can become a hindrance in our unpredictable world. The recent global pandemic, COVID-19, demonstrated this dramatically. The most well-conceived corporate plans for 2020 were obsolete by March - less than 90 days after the arbitrary start date, January 1.</p>

<p>No matter how meticulously we plan, unforeseen factors can, and will, disrupt everything.</p>

<h3 id="embrace-unpredictability">Embrace (un)Predictability</h3>

<blockquote>
  <p>Everyone has a plan until they get punched in the mouth.<br /><br />Mike Tyson</p>
</blockquote>

<p>Or did you hear it first as…</p>

<blockquote>
  <p>No plan survives first contact with the enemy.<br /><br />Helmuth van Moltke</p>
</blockquote>

<p>We want to tell ourselves that the pandemic was an anomaly, an unforeseeable and once-in-a-lifetime event, and that our plans would have remained intact if not for this global upheaval. But was the pandemic truly abnormal, or is predictability the anomaly? As the adage goes, the only constant is change.</p>

<p>Embrace change. It’s consistent.</p>

<p>If we’re honest, our annual plans, even the best of them, never survive intact. New information, unforeseen events, changing priorities - all these ruin the best-laid plans. In pandemic years and in non-pandemic years alike, chaos reigns. The only difference in 2020 was that the disruption had a name, but the result was the same.</p>

<p>By the second quarter of each year, we’re in revision mode - adjusting the budget, the roadmap, or the project plan to account for the unforeseen and unknowable events that have occurred since the previous November.</p>

<p>The alternative?</p>

<p>Shorten your time horizon. Focus only on what’s in front of you. Strive to ensure that every step you take moves you closer to your North Star. Complete today’s work, and have an idea about what you’ll do tomorrow. But don’t hold too tightly to anything beyond that.</p>

<h3 id="world-building-and-project-planning">World Building and Project Planning</h3>

<blockquote>
  <p>In preparing for battle I have always found that plans are useless, but planning is indispensable.<br /><br />Dwight D. Eisenhower</p>
</blockquote>

<p>The tension between predictability and adaptability is ever-present. It’s important to know when you need a plan, and when you need a compass.</p>

<p>Make and follow a plan when you’ve been there before; when you’ve done this work already.</p>

<p>Examples of places we’ve been and work we’ve done before:</p>

<ul>
  <li>Launching the <em>nth</em> client</li>
  <li>Flying a plane</li>
  <li>Riding the train</li>
  <li>Building a house</li>
  <li>Constructing a wind or solar farm</li>
</ul>

<p>Use your compass when you’re creating a <em>new world</em> and stepping foot in places you’ve never been before.</p>

<p>Examples of <em>new world</em> building:</p>

<ul>
  <li>Creating a new product or product feature</li>
  <li>Growing something - anything! - beyond where it’s been before</li>
  <li>Finding product-market fit</li>
  <li>Solving problems</li>
</ul>

<p>When you hear someone claim that we only need to plan better, more thoroughly, and our new world building would be more predictable, remember that this order is reversed. Only after you’ve done something can you know how to do it again.</p>

<p>Successful planning requires experience of the work to be done.</p>

<p>In essence, follow your compass to solve problems worth solving. Only once the solution is known and proven should you consider devising a plan to do it again.</p>]]></content><author><name></name></author><category term="mindset," /><category term="lean-startup," /><category term="agility" /><summary type="html"><![CDATA[Predictability and agility sit at opposite ends of the same spectrum. Why teams must choose between planning and responding to change — and when each one wins.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.evanmaxon.com/assets/images/avatar.png" /><media:content medium="image" url="https://www.evanmaxon.com/assets/images/avatar.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">Eating soup with forks</title><link href="https://www.evanmaxon.com/blog/eating-soup-with-forks" rel="alternate" type="text/html" title="Eating soup with forks" /><published>2019-10-25T15:00:00+00:00</published><updated>2019-10-25T15:00:00+00:00</updated><id>https://www.evanmaxon.com/blog/eating-soup-with-forks</id><content type="html" xml:base="https://www.evanmaxon.com/blog/eating-soup-with-forks"><![CDATA[<blockquote>
  <p>We need you to build a fork. We have the budget and it’s approved for development. When can you deliver our fork?</p>

  <p>A Company Executive / Line of Business</p>
</blockquote>

<p>And we respond affirming the request.</p>

<blockquote>
  <p>We’ll have that done by next quarter (or some other timeframe that may or may not be reasonable).</p>

  <p>The Execution Team</p>
</blockquote>

<p>An order has been placed. The solution has been defined and the team responsible for building it may or may not know what problem the fork is supposed to solve. But somebody somewhere decided that this was the answer.</p>

<p>The problem is in the mindset. We budget for solutions. Instead, we should budget for problems.</p>

<p>This isn’t another essay on why you should fall in love with the problem. (If you haven’t heard that cliché before, <a href="https://www.google.com/search?q=fall+in+love+with+the+problem&amp;oq=fall+in+love+with+the+problem&amp;aqs=chrome..69i57j0l3.3483j0j1&amp;sourceid=chrome&amp;ie=UTF-8">let me google it for you</a>.) I am advocating a change in how we approach our work and the impact that has on resource allocation, budgeting, and planning.</p>

<blockquote>
  <p>Everything should be made as simple as possible, but no simpler.</p>

  <p>Albert Einstein</p>
</blockquote>

<h2 id="the-problem-with-solutions">The problem with solutions</h2>

<p>When we focus on solutions, we place our trust in someone’s judgment — that they know what the fix should be. Frequently, this is someone that’s on the front lines, an executive, or a small group tasked with defining requirements.</p>

<p>Even when we have someone explore the problem and devise a solution, they often focus all of their energy on a single idea. This is the magic bullet approach. We take a shot and move on — regardless of whether or not we hit the target.</p>

<p><strong>Consider the soup fork.</strong></p>

<p>Someone points out that we have a problem eating soup. It’s messy. We occasionally burn our nose or fingers trying to get it from the bowl to our mouth. We suck at eating soup.</p>

<p>Someone has an epiphany that if we only had a fork, we could eat soup so much better. And they’d be right. We would keep our hands clean. Soup wouldn’t spill. And we’d be able to get those tasty chunks of meat and vegetables. So much less waste.</p>

<p><em>But what about the broth?!?!?!</em> We’d be leaving behind the essence of the soup! Plus, forks are generally terrible with anything that can’t be stabbed.</p>

<p>Ignoring the broth problem, we race forward with the fork research. We convene a committee to define the requirements — the length of the handle; the number of prongs (one, two, three, or four?); and the material. We ask people which fork design they prefer and watch them use the different designs.</p>

<p>No one bothers to question if the fork is the right solution. We’ve been told by higher ups and that discussion is out of scope. (<em>Where are your contrarians?</em>)</p>

<p>With the requirements defined, we bring in the utensil builders and hand them all of our artifacts — sketches of the fork, high fidelity mockups, and possibly even competitors’ forks. You only hire the best utensil builders, but when they ask questions you dismiss them because your solution has been tested.</p>

<p>After six months, the utensil builders deliver the fork — assuming they didn’t get pulled off to work on a higher priority project. We deploy the fork and move on.</p>

<p>The fork-using soup eaters provide feedback that most of the soup is left in the bowl. But the committee has been disbanded and the utensil builders are focused on the next project. Still, someone promises them that we’ll make a better fork. Someday.</p>

<p>The focus on solution building has its own set of systemic issues that need to be addressed.</p>

<ol>
  <li><strong>Resource planning</strong>. We need to keep the utensil builders busy. Because of that, we need to have shovel-ready work at all times. We can’t have any slack in the system.</li>
  <li><strong>Roadmaps</strong>. Related to resource planning, we need to know what they will be working on for the next 12 to 18 months. We also need to be able to communicate to the organization what will be delivered when. To manage this, we hire someone to manage a PowerPoint showing this schedule.</li>
  <li><strong>Half-built solutions</strong>. Inevitably, a project will be interrupted and the solution won’t be finished. Not only that, what has been built isn’t releasable. And by the time we could return to the project, the world moved on and the solution isn’t viable.</li>
</ol>

<p>While there are other systemic issues, these are the most obvious.</p>

<h2 id="the-solution-is-in-the-problem">The solution is in the problem</h2>

<blockquote>
  <p>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.</p>

  <p>Steve Jobs</p>
</blockquote>

<p>By prioritizing problems, we simplify our lives, our organizations, and the risk of building solutions to the wrong problems. We have the freedom to act from the position of humility. We don’t — and won’t — have the answers when we start. But we will be reducing the impact of the problem on the organization throughout the effort, not only at the end.</p>

<p><strong>About that soup-eating problem.</strong></p>

<p>Once we determine that improving the way we eat soup would have the greatest impact on the organization, we assign a capable team to focus on this. The team has utensil builders, soup eaters, possibly even a soup maker. We give them an initial time box of six months and tell them to make eating soup as easy as possible.</p>

<p>For the next six months, this team cycles through the following questions.</p>

<ol>
  <li>How do we know this is a problem?</li>
  <li>How do we know this is a problem worth solving? (Will the affected change their behavior? Will someone pay for this solution?)</li>
  <li>How do we know our solution worked? (Are the affected changing their behavior? Is someone paying us for the solution?)</li>
</ol>

<p>It’ll go something like this.</p>

<p><em>How do we know we have a problem eating soup?</em> Because we are in the soup eating business but can only seem to consume half of it, spilling the rest. We have soup eaters spilling it on the table, on their clothes, and burning their lips and noses when they put their faces into the bowl. We have a lot of waste.</p>

<p><em>How do we know this is a problem worth solving?</em> The soup eaters are asking us to help. We also have the accounting department asking if we can reduce the cost of eating soup.</p>

<p>As we observe the soup eaters — even eating some soup with them — we notice that it’s served in a bowl. This leads to our first attempt at a solution.</p>

<p><strong>First hypothesis</strong>: By picking up the bowl and drinking the soup from it, we can decrease the wasted soup.</p>

<p>With this change made we find that we are able to reduce wasted soup. They were able to consume most of the broth along with the meat and veggies. And we didn’t even have to build anything!</p>

<p>However, we still had soup eaters spill some on their clothes, and burn their lips. They also mentioned that they’d prefer to have a free hand when eating soup and lifting the bowl required two hands. Those that tried one hand spilled more and were more likely to drop the entire bowl.</p>

<p>Coming back from lunch at a nearby sushi spot, someone suggests trying chopsticks.</p>

<p><strong>Second hypothesis</strong>: Chopsticks will reduce waste when eating soup.</p>

<p>This has mixed results. Yes, it helps with the solid objects, but does nothing to improve the broth situation. As a possible solution, the hypothesis is disproved.</p>

<p>The team keeps at it, interacting with the soup eaters and testing new hypotheses as quickly as they can. Within the allotted time for the project, they run several experiments. Some are disproved and others allow the organization to improve.</p>

<p><strong>By the end of the allotted time</strong>, the organization is using an insulated cup. It’s not perfect, but has drastically improved the organization’s ability to eat soup.</p>

<p>At any point during the project, the team can communicate what they’ve learned and how we know the current approach to solving the problem is viable.</p>

<p>The organization has a simple decision to make now. Do we give the team more time to persevere or do we pivot them to tackle another problem? That depends on if improving the way the organization eats soup will have the greatest impact (aka value).</p>

<p>Budgeting to tackle problems, instead of building solutions, gives organizations more flexibility to adapt. This approach also simplifies the demands on the doers and the managers.</p>

<h3 id="the-simple-life">The simple life</h3>

<p><strong>A backlog, not a roadmap</strong>. Since we are budgeting time, we only need to maintain a backlog of problems facing the organization. This list is prioritized by the most pressing to the least important. Once a problem is no longer the highest on this list, we re-prioritize it and move on to whatever is on the top.</p>

<p>By managing a backlog, the roadmap becomes irrelevant. The information conveyed on the roadmap was a fuzzy best guess (aka lies), so trashing it will improve trust and moral.</p>

<p><strong>Resource planning SIMPLIFIED!</strong> Teams will be perpetually productive. You won’t have to worry if there’s enough shovel-ready work to hand off. The only resource question you’ll need to answer is if there are enough teams to tackle the critical problems facing the organization.</p>

<p><strong>Organizational agility</strong>. Gone are the days of waiting for the current project to be delivered (after months or years!) so that we can pick up the next solution. Or pausing the current effort only to have a half-built, never delivered solution that adds no value in its current state.</p>

<p>Instead, value will be delivered at the conclusion of each iteration. The organization will know more about the soup eating problem and likely have a better way to consume it.</p>

<p>Your organization will also be capable of adapting to new challenges and market changes as quickly as leadership can identify them.</p>

<h2 id="change-the-perspective">Change the perspective</h2>

<p>Since time is money, think in terms of time and not money.</p>

<p>Don’t ask <em>how much is this going to cost me?</em> Instead, say <em>I’m willing to give you a set amount of time to reduce the impact of this problem as much as you can</em>. At the conclusion of that time box, you get the freedom to decide if that problem is still painful enough to persevere or if you should pivot your team of experts towards more pressing matters (read: other problems).</p>

<h2 id="how-to-lead-problem-solvers">How to lead problem solvers</h2>

<p>The way to lead problem-tackling teams is different than how to lead any organization. It requires constant vision casting, constraints, and protection from distractions.</p>

<p><strong>Vision casting</strong>. Why does your organization exist? What massive problem are you out to rectify? Similarly, if your organization ceased to exist, what would be the societal ramifications (to non-shareholders and employees)? Vision casting requires that you understand this and communicate it to everyone you encounter on a daily basis. If you need help with this, <a href="https://www.amazon.com/Start-Why-Leaders-Inspire-Everyone/dp/B074VF6ZLM/ref=sr_1_1?crid=2SGXNX5BAET63&amp;keywords=start+with+why+simon+sinek&amp;qid=1571799573&amp;sprefix=start+with+%2Caps%2C272&amp;sr=8-1"><em>Start with Why</em> by Simon Sinek</a> should be your next audiobook (or you can <a href="https://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action?language=en">watch the TED Talk</a>).</p>

<p><strong>Constraints</strong>. Your problem-solving teams will feel empowered if they know they have autonomy. They need to know what they can and can’t change without someone else approving it. To minimize this, the team composition is crucial. Make sure the team includes the appropriate SMEs — or has the executive air cover — to make the necessary changes to systems and processes.</p>

<p><strong>Focus</strong>. Multi-tasking is terrible. It’s destructive to productivity. Protect your team from distractions by allowing them to be dedicated to this effort. Even protect your SMEs and executives necessary for the team to operate with autonomy.</p>

<p>In short, be clear as to why your organization exists and where it is going, how much power your team has, and that the team is protected from distractions.</p>

<h2 id="tldr-aka-the-conclusion">tl;dr (aka the conclusion)</h2>

<p>Stop worrying about how you can fit fork building into your budget. Instead, give your team of experts a set amount of time to improve your ability to eat soup.</p>]]></content><author><name></name></author><category term="tactical," /><category term="how-to," /><category term="mindset," /><category term="lean-startup" /><summary type="html"><![CDATA[Stop worrying about how you can fit fork building into your budget. Instead, give your team of experts a set amount of time to improve your ability to eat soup.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.evanmaxon.com/assets/images/avatar.png" /><media:content medium="image" url="https://www.evanmaxon.com/assets/images/avatar.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">But What’s the MVP of the MVP?</title><link href="https://www.evanmaxon.com/blog/whats-the-mvp-of-the-mvp" rel="alternate" type="text/html" title="But What’s the MVP of the MVP?" /><published>2019-09-17T15:00:00+00:00</published><updated>2019-09-17T15:00:00+00:00</updated><id>https://www.evanmaxon.com/blog/whats-the-mvp-of-the-mvp</id><content type="html" xml:base="https://www.evanmaxon.com/blog/whats-the-mvp-of-the-mvp"><![CDATA[<blockquote>
  <p>You keep using that word. I do not think it means what you think it means.</p>

  <p>Inigo Montoya, <em>The Princess Bride</em></p>
</blockquote>

<p>If you’ve been anywhere near product development, you’ve either heard or muttered (probably both!) something along the lines of “What’s the MVP of this?”, “We need this feature in the MVP.”, or “We can’t go live without that!”</p>

<p>When MVP is used this way, your perspective is wrong. The cart is in front of the horse. The problem is that we cannot objectively explain how we know we are right. How do we know that feature or this functionality needs to exist at all, let alone in the first release? How do we know what will make the product viable? And even this line of questioning is a mis-use of how MVP should be applied.</p>

<h2 id="the-mvp-misunderstanding">The MVP misunderstanding</h2>

<blockquote>
  <p>MVP, despite the name, is not about creating minimal products.</p>

  <p><a href="https://www.startuplessonslearned.com/2009/08/minimum-viable-product-guide.html">Eric Reis, <em>The Lean Startup</em></a></p>
</blockquote>

<p>Yes, <em>product</em> is the third word in the acronym, which may be why we tend to think about MVP in the narrow context of a marketable or releasable solution. Even much of what the Lean Startup community talks about is built on this assumption.</p>

<p>Using, or mis-using, MVP in this way invites jumping to a solution based on the perspective of one or a few individuals (who are probably not the end user).</p>

<p>Along the way to the perceived MVP solution, we miss several key opportunities to minimize risk, conserve resources, and build a customer base while figuring out what the solution really should be. Yes, we can build the airplane while flying it.</p>

<p>When we minimize the time we spend on exploring the problem and jump to a solution, even one we think is an MVP, we increase the risk of not actually solving the problem.</p>

<ul>
  <li>The viability of the solution doesn’t happen until the end of the effort, once you ship it / launch it.</li>
  <li>The resulting product is built on untested, unproven assumptions.</li>
  <li>The end result is usually a product that exceeds the bare minimum requirements (aka viability) to achieve the objective.</li>
</ul>

<p>When we use MVP in this manner, we do the concept — and those we work with - a disservice. The acronym is thought of with disdain and people stop using it. (Which, if you’re going to mis-use it, is this a bad thing?) Then the entire concept gets dropped, and you’re back to your waterfall processes launching expensive, unproven solutions to problems that may or may not exist.</p>

<h2 id="minimum-viable-mvp-a-definition">Minimum Viable MVP (a definition)</h2>

<blockquote>
  <p>It is vain to do with more what can be done with less.</p>

  <p>William of Occam, <a href="https://simple.wikipedia.org/wiki/Occam%27s_razor"><em>Occam’s Razor</em></a></p>
</blockquote>

<p>To better understand MVP, let’s define the term by starting with the end.</p>

<p><strong>Product.</strong> This is the output of our work. Frequently this will be tangible - a landing page, a prototype, designs or mockups, even a working solution - but can also be observation time or interviews. This is the least restrictive part of MVP.</p>

<p><strong>Viable.</strong> The threshold by which something is either useful for a given purpose, or it is not. This is binary. Your product is or is not viable.</p>

<p><strong>Minimum.</strong> Viability is a spectrum, spanning from <em>not at all useful</em> to <em>completely over-engineered</em>. And since we all suffer from <a href="https://fs.blog/2018/01/complexity-bias/">Complexity Bias</a>, we need to qualify the extent that our solution is viable. By including <em>minimum</em> we are aiming at something that just barely meets our needs.</p>

<p>In practice, MVP should be used exclusively in the context of a Build-Measure-Learn cycle (from <em>The Lean Startup</em> methodology). And this cycle is focused on testing hypotheses. Thus, an MVP is the least amount of work we <em>need</em> to do to be able to empirically disprove our hypothesis. We use MVP, but that is because it’s much easier to say, and remember than MVPTCBUTDaH (minimum viable product that can be used to disprove a hypothesis).</p>

<h2 id="mvp-to-mvmp">MVP to MVMP</h2>

<p>The output of a series of MVPs, if you persevere, is a MVMP — a minimally viable marketable product. But how do you go from MVP to MVMP?</p>

<h3 id="focus-on-disprovability">Focus on Disprovability</h3>

<blockquote>
  <p>No amount of experimentation can ever prove me right; a single experiment can prove me wrong.</p>

  <p>Albert Einstein (paraphrased)</p>
</blockquote>

<p>In empiricism, theories and hypotheses must be falsifiable. In other words, if you observe something that contradicts your hypothesis, you’ve proven that your hypothesis is false. And this lets us revise our hypothesis and run new tests!</p>

<p>When testing, your efforts should be spent (and your tests structured) to disprove your hypothesis. We focus on disprovability because the level of effort to falsify a hypothesis is far less than the effort to prove it true.</p>

<p>The discovery of black swans is commonly used to illustrate the concept of disprovability. Prior to 1697, Europeans believed that all swans were white. (Swans in Europe were white.) We can use this to make a falsifiable statement — “all swans are white.” If we focus our efforts on proving this statement is true, we need to observe <em>all</em> swans. However, if we focus on disprovability, we only need to find <em>one</em> non-white swan. (And in 1697, <a href="https://en.wikipedia.org/wiki/Willem_de_Vlamingh">Willem de Vlamingh</a> did just that while exploring parts of Australia.)</p>

<p>Disprovability allows us to explain, with confidence, how we know we are right - because we haven’t been able to prove ourselves wrong <em>and we tried</em>. Another benefit to focusing on disprovability is that we are avoiding confirmation bias.</p>

<p>Therefore, your Minimum Viable Product should be the least amount of work needed to disprove your hypothesis.<sup>1</sup></p>

<h3 id="problem-validation">Problem validation</h3>

<blockquote>
  <p>If I had an hour to solve a problem, I’d spend 55 minutes thinking about the problem and 5 minutes thinking about the solution.</p>

  <p>Albert Einstein</p>
</blockquote>

<p>With a mindset focused on disprovability, the next step that is frequently skipped is understanding the problem. Our partners bring us a request to build a widget that they think will solve their problem. Or, being the problem-solving product people we are, we can quickly come up with ideas to fix this manual process or that work around.</p>

<p>By skipping the problem exploration, we end up with a sitcom solution. It’s that supporting character in a sitcom struggling to launch a business that sounds plausible but if we were to try it would fail. That’s because there was no effort to validate the problem this character’s business is meant to solve. (Barely paraphrased from <a href="https://www.paulgraham.com/startupideas.html">Paul Graham</a>.)</p>

<p>You make money in real estate when you buy the property. In product development, you build successful products by relentlessly exploring the problem. In organizations where solutions are brought to us, we need to be very adept at guiding our partners to step back and search for root causes.</p>

<p>We need to constantly be asking ourselves:</p>

<ul>
  <li><strong>Is this really a problem?</strong>
    <ul>
      <li>How do we know?</li>
      <li>Where did the identification of the problem come from?</li>
      <li>Is the problem we are solving for actually a symptom of something else?</li>
    </ul>
  </li>
  <li><strong>Is this problem worth solving?</strong>
    <ul>
      <li>How do we know that?</li>
      <li>Can we quantify the impact of this problem in terms of lost time, money spent, or even customer frustration?</li>
      <li>Are current work-arounds painful enough that customers will embrace (ie. pay for) a solution?</li>
    </ul>
  </li>
</ul>

<p><strong>So how does MVP fit with problem exploration?</strong></p>

<p>First, take a <a href="https://www.isixsigma.com/methodology/kaizen/many-sides-gemba-walk/">Gemba</a> (or <a href="https://en.wikipedia.org/wiki/Gemba">genba</a>, if you will) walk. Personally observe the situation. Take time to take it in. Spending a few hours to a day - even a week - is a minimally viable product that can be used to disprove a hypothesis. During our observation time, did we see the problem occur? If not, this may be all you need to decide it’s not really a problem or not worth solving if the occurrence is that rare. And <strong>the MVP you had to build was the effort to get to the genba and the time spent observing.</strong></p>

<p>Second, as quickly as possible, <em>quantify the problem</em>. Can you determine frequency, lost time, or lost money? Ultimately, you want a rough estimate of the scope of the problem. <strong>Your MVP to quantify if this is really a problem is only the time spent looking at the data.</strong></p>

<p>Third, as quickly as possible <em>quantify the risk</em> of not addressing the problem. How much could, or will, we lose if we don’t pursue a solution? Our effort to solve the problem <em>will</em> cost us something (time and money), will this be more or less than the cost of letting this problem continue? <strong>Your MVP to determine if this is a problem worth solving is simply the time spent looking at the data.</strong></p>

<p>These are a few suggestions to highlight how little work, an MVP, is needed to determine if the problem exists and if it’s worth solving.</p>

<p>A skeptical and data-driven approach to problem exploration is invaluable. Within this context, take greater pride in work not done.</p>

<h3 id="solution-validation-incremental">Solution validation (incremental)</h3>

<blockquote>
  <p>If you’re not embarrassed by the first version of your product, you’ve launched too late.</p>

  <p><a href="https://www.linkedin.com/pulse/arent-any-typos-essay-we-launched-too-late-reid-hoffman/">Reid Hoffman, LinkedIn co-founder</a></p>
</blockquote>

<p>Using MVPs to incrementally build and validate solutions is more widely used. When exploring solutions, minimally viable products initially need to simply test a hypothesis — not be a viable marketable product.</p>

<p>Consider the following approaches.</p>

<ul>
  <li><strong>Build a landing page for a product that does not exist</strong>, but act like it does. Then drive traffic to the site with Google Ads (or another ad platform) and track how many people click the ‘Buy Now’ button. (This method is spelled out in great detail in <a href="https://www.amazon.com/4-Hour-Workweek-Escape-Live-Anywhere/dp/0307465357">The 4-Hour Workweek</a> by Tim Ferriss.)</li>
  <li><strong>Introduce new elements to existing solutions.</strong> Use non-functional buttons or links that appear to solve a problem (or lead to a solution) and track how many people click on it.</li>
  <li><strong>Do things that don’t scale.</strong> Make the fix <em>appear</em> to be automated by doing behind-the-scenes processes manually. Personally setup new users. Use a spreadsheet as your database — and manually manage it! Each of these is an MVP that provides learning and will guide your future iterations. (For the second time in this post, paraphrased from <a href="https://www.paulgraham.com/ds.html">Paul Graham</a>.)</li>
  <li><strong>Build (ugly) prototypes with off-the-shelf parts.</strong> For electronics, leverage <a href="https://www.arduino.cc/">Arduino</a> and/or <a href="https://www.raspberrypi.org/">Raspberry Pis</a> to build disposable proofs of concepts. Then deploy it and observe how it does, or doesn’t, move you closer to a solution.</li>
  <li><strong>Create mock-ups that simulate the experience.</strong> If the solution needs to have specific dimensions (size and weight), tape together cardboard (from your Amazon orders) and fill it with weights. Then ask your customer to hold it as if it was a finished product. You’ll learn if this is an acceptable form factor.</li>
</ul>

<p>Keep in mind that if one of these MVP tests fails, that’s a good thing! Now you know what doesn’t work. By persevering, pivoting to a different approach, and stringing together a series of the Build-Measure-Learn cycles, <strong>the end result is a Minimum Viable <em>Marketable</em> Product</strong>.</p>

<h2 id="conclusion">Conclusion</h2>

<p>While the disdain is more likely to occur in larger organizations, mis-using MVP crosses all sizes and stages of companies - from startups to Fortune 100. This mis-use leads to risky and costly solutions to problems that may not even exist — or be worth the effort. Instead, we owe it to ourselves and our customers to reclaim the MVP approach to making our world better.</p>

<hr />

<h6 id="footnotes">FOOTNOTES</h6>
<p><sup>1</sup>There’s probably an entire blog post on balancing statistical confidence in the outcome of your tests versus expense and the need to move forward to the next Build-Measure-Learn cycle.</p>]]></content><author><name></name></author><category term="tactical," /><category term="how-to," /><category term="mindset," /><category term="lean-startup," /><category term="mvp" /><summary type="html"><![CDATA[The term and concept of MVP is mis-used. This leads to risky and costly solutions to problems that may not even exist — or be worth the effort. We owe it to ourselves and our customers to reclaim the MVP approach to making our world better.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.evanmaxon.com/assets/images/avatar.png" /><media:content medium="image" url="https://www.evanmaxon.com/assets/images/avatar.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">HMW Kill the Status Quo?</title><link href="https://www.evanmaxon.com/blog/how-might-we-kill-the-status-quo" rel="alternate" type="text/html" title="HMW Kill the Status Quo?" /><published>2019-08-17T15:00:00+00:00</published><updated>2019-08-17T15:00:00+00:00</updated><id>https://www.evanmaxon.com/blog/how-might-we-kill-the-status-quo</id><content type="html" xml:base="https://www.evanmaxon.com/blog/how-might-we-kill-the-status-quo"><![CDATA[<p>My design partner inadvertantly spurred this rant. (Thanks, David!) To support a new feature, I spent the better part of an afternoon mapping out a new process on a glass board. The new process I mapped incorporates existing processes that are controlled by others within our organization. The end result is a comprehensive picture of an experience that is constrained by the status quo — assumptions about how things <em>have</em> to be.</p>

<p>The next morning I find my work had been vandelized with purple post-its. Each of these post-its contained a question that started with “<em>HMW</em>”.</p>

<ul>
  <li><em>HMW</em> allow for a customer to stop the process?</li>
  <li><em>HMW</em> notify customers of the decision?</li>
  <li><em>HMW</em> show the status?</li>
</ul>

<h3 id="hmw--how-might-we"><em>HMW</em> = How Might We</h3>

<p><strong>What the hell is “<em>HMW</em>”?</strong> It took me longer than I’d like to admit to figure out what this acronym meant. Then it clicked. “<em>HMW</em>” translates to <em>How Might We…</em><sup><a href="#footnotes">1</a></sup></p>

<ul>
  <li><strong>How might we do this one task differently?</strong> What are the possibilities here?</li>
  <li><strong>How might we accomplish this step if we have some other constraint?</strong> What if this experience had to be completed in less than 60 seconds? How could we get all of the information we need without ever asking the customer for a single item?</li>
  <li><strong>How might we make it easier for the user?</strong> As a customer, what would the ideal experience be for me to accomplish my goals? Your back-end processes driving this experience are irrelevant to me and the answer to this <em>HMW</em>.</li>
</ul>

<p><em>HMW</em> is about dreaming. <em>HMW</em> is about challenging the status quo.</p>

<h2 id="the-danger-of-the-status-quo">The danger of the status quo</h2>

<p>Why is challenging the status quo so important? Why do we (I) even care?</p>

<p>The status quo of workplace culture is to <strong>not challenge</strong> the status quo. Being the one to do so can be risky to ones career. Yet, adhering to the status quo never leads to innovation. Quite the opposite. Adhering to <em>that’s how we’ve always done it</em> thinking is the wrong kind of constraint. It leads to stagnation and, ultimately, the demise of your organization.</p>

<p>Succintly, the safety of the status quo is risky behavior. Maintaining the status quo is built on assumptions and not data — assumptions that the original decision was right and continues to be right. Even when the original decision was based on data, you shouldn’t assume that it continues to be the correct path going forward.</p>

<h3 id="normalized-deviance">Normalized deviance</h3>

<p>Accepting and propagating the status quo when the original decision was wrong leads to the normalization of deviance.</p>

<blockquote>
  <p>“Social normalization of deviance means that people within the organization become so much accustomed to a deviant behavior that they don’t consider it as deviant, despite the fact that they far exceed their own rules for the elementary safety.”</p>

  <p><a href="https://en.wikipedia.org/wiki/Diane_Vaughan">Diane Vaughan, Ph.D.</a></p>
</blockquote>

<p>The most famous example, and possibly one of the most tragic, is the 1986 space shuttle disaster. The disaster was caused by a failure in the joints on the solid rocket boosters. During exhaustive testing by both NASA and the private contractor, the connective material was found to be faulty. Yet, with repeated successful shuttle launches, the perceived risk the material presented became (unoffically) acceptable. The status quo of poorly performing material directly led to the disaster. (<a href="https://www.process.st/normalization-of-deviance/">Further reading here.</a>)</p>

<p>At worst, accepting the status quo can cost lives. At best, it prevents your organization from finding new and better solutions.</p>

<p>Challenging the status quo needs to be the status quo.</p>

<h2 id="the-art-of-innovation">The art of innovation</h2>

<blockquote>
  <p>“If I’d asked people what they want, it would have been a faster horse.”</p>

  <p>Henry Ford</p>
</blockquote>

<p><a href="https://en.wikipedia.org/wiki/Peter_Thiel">Peter Thiel</a> asks interviewees what they believe to be true that everyone else thinks is false. In addition to gaining insight into someone’s world view, seeing the world different — going against the status quo — leads to innovation. These are not merely incremental advancements, but leaps from one point to another that, in hindsight, appear to be illogical.</p>

<p>In one of his TED talks, Guy Kawasaki advocates fostering a perspective that enables you to jump from one innovation curve to the next.</p>

<blockquote>
  <p>“When we were creating the Macintosh, we weren’t trying to make a slightly better Apple II, or a slightly better MS DOS machine. We were trying to jump to the next curve of personal computing.”</p>

  <p>Guy Kawasaki, <a href="https://www.youtube.com/watch?v=Mtjatz9r-Vc">The art of innovation at TEDxBerkeley</a></p>
</blockquote>

<p>Kawasaki gives the example of the ice industry. Over the course of ~75 years, we saw three innovation curves.</p>
<ul>
  <li>Late 1800s: ice was harvested from frozen lakes.</li>
  <li>1930s: ice was produced in factories.</li>
  <li>Late 1950s: ice was readily available in the household refrigerator.</li>
</ul>

<p>None of the organizations that thrived in each of these curves made it to the next curve. As Kawasaki points out, it’s because organizations define themselves based on what they do, not the benefit they provide. By accepting the status quo of what your organizations does, you’ll fail to make the leap to the next innovation curve.</p>

<blockquote>
  <p>“How do people know what they want until I show it to them?”</p>

  <p>Steve Jobs</p>
</blockquote>

<h2 id="the-dangerous-existence-of-the-contrarian">The dangerous existence of the Contrarian</h2>

<p>Most won’t welcome attempts to <a href="https://en.wikipedia.org/wiki/Who_Moved_My_Cheese%3F">move their cheese</a>.</p>

<p>People generally don’t appreciate being asked uncomfortable questions — because having to explain <em>why</em> something is the way it is, is work. The experience will feel like you are impeding progress. But asking <em>why</em> something is the way it is can uncover practices that don’t need to exist.</p>

<p>By all means, though, avoid playing the devil’s advocate. Being a contrarian for the sake of contrarianism isn’t the goal. And, if you’re labeled a contrarian, expect your role and influence to be diminished.</p>

<p>Instead, be humble and make it known that you seek to understand when asking the uncomfortable questions. It’s seeking to understand that can reduce the resistance to exploring why a given assumption exists. And when others are part of that discovery, the desire to change for the better won’t be a solitary journey.</p>

<h2 id="hmw-kill-the-status-quo"><em>HMW</em> kill the status quo?</h2>

<p><em>HMW</em> isn’t about having arguments, nor is it about advocating positions you don’t hold. It is, however, an approach to thinking through how you would solve a problem if the situation was different, if the fundamental assumptions driving it were changed.</p>

<ul>
  <li><em>HMW</em> foster a culture of identifying and challenging assumptions? Be intentional with this. Formalize ceremonies to ask the <a href="https://en.wikipedia.org/wiki/5_Whys">5 Whys</a>.</li>
  <li><em>HMW</em> embrace contrarians and contrarian thinking? Identify contrarians in your midst. Seek out their perspective. Ask them to ask (uncomfortable) questions.</li>
  <li><em>HMW</em> leverage data to validate/disprove assumptions that drive the status quo? Assumptions that drive status quo behaviours that need to be changed are not data-driven. Don’t be afraid to consult the data. (Just be quick about it.)</li>
</ul>

<p>It’s not easy, nor quick, to change culture. But it will be necessary if your organization wants to make the leap to the next curve.</p>

<hr />

<h6 id="footnotes">FOOTNOTES</h6>
<p><sup>1</sup> I’ve since learned that <em>HMW</em> is part of the Google Design Sprint. To learn more about this process,check out <a href="https://www.gv.com/sprint/"><em>Sprint: How to solve big problems and test new ideas in just five days</em></a> by Jake Knapp.</p>]]></content><author><name></name></author><category term="mindset," /><category term="5whys" /><summary type="html"><![CDATA[To die a death of a thousand status quos. How a vandalized process map underscores the importance of challenging assumptions and killing the status quo.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.evanmaxon.com/assets/images/avatar.png" /><media:content medium="image" url="https://www.evanmaxon.com/assets/images/avatar.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">You Don’t Work in a Startup and Other Last Words</title><link href="https://www.evanmaxon.com/blog/you-dont-work-in-a-startup-and-other-last-words" rel="alternate" type="text/html" title="You Don’t Work in a Startup and Other Last Words" /><published>2019-07-12T15:00:00+00:00</published><updated>2019-07-12T15:00:00+00:00</updated><id>https://www.evanmaxon.com/blog/You-Dont-Work-in-a-Startup-and-Other-Last-Words</id><content type="html" xml:base="https://www.evanmaxon.com/blog/you-dont-work-in-a-startup-and-other-last-words"><![CDATA[<p>As the adage goes, the only constant is change. Thus, embracing a Startup mindset is the only salvation for established organizations. For those of us that have made the leap from small companies to the corporate world, reminding us that we don’t work in a Startup anymore is a threat to the longevity of your organization.</p>

<h2 id="complacency-kills">Complacency Kills.</h2>

<blockquote>
  <p>“Blockbuster didn’t go out of business because of bad customer service.” - <a href="https://www.linkedin.com/in/ariel-simpson-38a16a70/">Ariel Simpson</a></p>
</blockquote>

<p>Hidden within the mindset that established organizations can and should operate differently than Startups are several deadly behaviors. These lead to organizations that plod along believing they are immune to the ever-changing landscape. Blockbuster had a loyal customer base and a dominant footprint but failed to act fast enough in the face of two upstart competitors — one with kiosks and the other using the postal service.</p>

<h3 id="its-all-just-history-repeating">It’s All Just History Repeating.</h3>

<p>Yes, another adage: history repeats itself. In other words, we’ve been down this road before, yet so many are doomed to repeat mistakes because somehow it’s different this time.</p>

<p><strong>Kmart and Wal-Mart.</strong> When the competition between Kmart and Wal-Mart was at its peak — in the late 80s and early 90s — the CEO of Kmart, Joseph Antonini, reportedly referred to Wal-Mart executives as snake-oil salesmen. Likewise, many industry observers dismissed Wal-Mart — crediting its growth to its location in rural areas taking business from dying mom-and-pop stores.</p>

<p>Mr. Antonini’s approach to counter Wal-Mart’s incursion in to Kmart’s territory was to double-down on marketing and merchandising, ignoring — or not recognizing – that Wal-Mart had built a technological and logistical juggernaut that allowed it to offer ‘everyday low prices’. (<a href="https://college.cengage.com/accounting/resources/students/readings/06-read.html">Source</a>)</p>

<p>Mr. Antonini assumed that what had worked in the past would work in the future. Sam Walton, on the other hand, focused on finding operational efficiencies that began as a need (read: constraint) as a franchisee of the Ben Franklin stores to lower costs to gain market share.</p>

<p>While both stores launched in 1962, Wal-Mart upset Kmart by playing the role of the Startup. They, Wal-Mart, had proven customers want low retail prices (compared with an ever changing sale price) and delivered these prices by operating (initially) within known and defined constraints.</p>

<p><strong>Minimills and US Steel.</strong> Unlike Kmart’s demise, the downfall of the traditional, integrated US steel industry lacks charismatic central figures. But the decline is none-the-less spectacular.</p>

<p>Following WWII, the United States dominated steel production globally. An estimated 40% of all steel was made in the US at large, fully integrated steel mills — predominately located from Chicago to Pittsburgh. Unlike the mills in Japan, Germany, and most of Europe, the US mills survived the war unscathed. While this was a blessing to this region of the country for the generation that followed, the new mills built as part of the war recovery leveraged newer technology that were more efficient and less expensive.</p>

<blockquote>
  <p>Rather than adopt the new process, executives at firms such as U.S. Steel, Bethlehem Steel and Republic Steel stubbornly stuck with their outmoded methods. - <a href="https://www.seattletimes.com/business/economy/how-the-american-steel-industry-nearly-committed-suicide-and-not-from-trade/">Jon Talton, Seattle Times</a></p>
</blockquote>

<p>In addition to the rise of foreign steel mills that were technologically superior, Minimills started springing up domestically. Initially, Minimills focused on producing low grade, low quality steel milled from scrap metal. This type of steel offered low profit margins and the legacy steel mills willingly surrendered this production to the minimills (who were well suited to this type of steel production).</p>

<p>By the 1980s, the majority of steel production was from scrap metal. And today, only U.S. Steel remains of the large WWII-era steel companies.</p>

<p>But the demise of the legacy steel producers wasn’t merely a shift in market preference towards lower quality steel. The Minimills did two things that, when combined with renewed international competition, spelled the end for the incumbant steel producers. The first was that they moved up market expanding into higher quality steel. The second was that they didn’t hire experienced steel workers, preferring to train new ones. This helped them find new and better methods by not being trapped by the status quo mindset (eg. “this is how we’ve always done it”). (<a href="https://www.seattletimes.com/business/economy/how-the-american-steel-industry-nearly-committed-suicide-and-not-from-trade/">Source</a>)</p>

<p><strong><a href="https://knowyourmeme.com/memes/all-your-base-are-belong-to-us">All Your Friends Are Belong To Us</a>.</strong> And with the pace of innovation, sometimes even the disruptors get disrupted. One of the first — if not <em>the</em> first — social networks to gain traction was Friendster. Within months, Friendster was replaced by MySpace (where we were all connected by some guy named Tom). And after a decent run, Tom lost all his friends to Mark and we are all stuck with Facebook (and Yahoo! got stuck with Tom).</p>

<p>Though, Facebook is now the one struggling to keep up. The demographic for their core platform is trending older and the primary source of innovation for the company comes from acquisitions. While Facebook doesn’t appear to be clinging to the status quo, I think it suffers from a lack of constraints — money isn’t an issue and that becomes a hindrance.</p>

<p>While the disruption for social platforms wasn’t long and drawn out (though, Facebook may be going through that now), both Friendster and MySpace diverged from Startup practices in two ways — they no longer identified and validated assumptions, and they no longer operated with known constraints (primarily financial).</p>

<h3 id="insulation-by-regulation-so-what">Insulation by Regulation. So What.</h3>

<p>Your choice of insurance (auto, home, health, and even life) used to be based on the company your friend repped. Trading stock used to require a broker. Surely, highly regulated industries are immune to disruption. Right? Consider this. The more the regulations the greater the opportunity for disruption.</p>

<p>Within my industry, <strong>the past decade</strong> has seen the rise of peer-to-peer lending; online mortgages; money trackers and budgeting apps; and web-based financial planning. <strong>Within the past year</strong>, Amazon launched a credit card for credit-challenged consumers; T-Mobile offers checking accounts; Apple is launching a credit card integrated into the iPhone experience; web-only banks, like Monzo, are moving from the more forward-looking market of Europe in to the United States.</p>

<p>The disruption facing retail banking looks very reminiscent of the steel industry just half a century ago. The survival of the current players – both too large to fail and your local community bank — depends on if their leadership is more like Joseph Antonini or Sam Walton.</p>

<h2 id="how-to-survive-the-no-sacred-cows-plan">How to Survive. The No Sacred Cows Plan.</h2>

<p>To improve longterm survival prospects, organizations need to embrace Startup hallmarks: act with a sense of urgency, constantly identify and test assumptions, and embrace constraints.</p>

<h3 id="mindset-1-today-matters-the-power-of-urgency">Mindset #1: Today Matters. (The Power of Urgency.)</h3>

<blockquote>
  <p>“The three most harmful addictions are heroin, carbohydrates, and a monthly salary.” - <a href="https://en.wikipedia.org/wiki/Nassim_Nicholas_Taleb">Nassim Nicholas Taleb</a></p>
</blockquote>

<p>A runway is the amount of time an organization has before it runs out of money and, thus, out of business. All businesses have a runway. For Startups, the need to extend this runway in the near term creates a sense of urgency - to not put off until tomorrow that which can, and should, be done today.</p>

<p>The desire to move fast is a hallmark of Startup culture. Mantras like ‘fail fast’ don’t refer to fatal failures. Instead, they are focused on the small initiatives, the components that together make up the whole. For example, if a sales landing page doesn’t convert enough leads we want to know that as quickly and as cheaply as possible so that we can try a different version.</p>

<p>Established organizations tend to lose any sense of urgency. Maybe this is because moving fast is thought of as being risky, or unnecessary since the organization is now established and insulated by barriers to entry. Furthermore, bureaucracy kills urgency. Yet, once urgency is no longer part of the company culture, it is difficult to re-establish. This places the organization at an even greater risk of being unable to respond to disruption - a very precarious and risky position.</p>

<p>In short, you should have the same sense of urgency working in an established organization that you would in a Startup. Your runway may be longer, but the long-term health of your organization depends on it.</p>

<h3 id="mindset-2-how-do-we-know-we-are-right">Mindset #2: How Do We Know We Are Right?</h3>

<p>Established organizations didn’t become established by being entirely wrong about their offerings in the past. As a result, why should we then think we are going to be wrong in the future? However, just like the investment disclaimer, past performance is not an indicator of future success.</p>

<p>With past success comes the trappings of resources and a false confidence that we <em>know</em> what the market needs or wants. Our exposure to <a href="https://en.wikipedia.org/wiki/Overconfidence_effect">overconfidence bias or effect</a> grows. This leads to organizations that rely on long product development cycles using only internal subject-matter experts to determine the product requirements. Developing products over long periods of time without customer involvement is a recipe for disaster.</p>

<p>Instead, identifying assumptions and seeking to validate them should be the same in an established organization as it is in a Startup. The aim is to build solutions that the market actually wants — which means that several someones somewhere are willing to pay money for your product or service.</p>

<p>The surest approach is to empower small teams focused on solving the most pressing issues to your organization. These teams need to have a high level of autonomy, and be tasked with delivering solutions incrementally in short iterations. Each iteration needs to be driven by user feedback.</p>

<p>Your products and services are assets. And developing them incrementally - with urgency - creates safe, sound ones.</p>

<h3 id="mindset-3-that-which-constrains-us-sets-us-free-the-power-of-constraints">Mindset #3: That Which Constrains Us Sets Us Free. (The Power of Constraints.)</h3>

<p>As Orwellian as it may sound, constraining your teams provides freedom - freedom to move fast and deliver proven solutions. Constraints force creative solutions to problems.</p>

<p>Clearly define the constraints employees must work within — but ensure they have complete autonomy within those constraints. Give them a sandbox. These constraints will force non-traditional thinking to problem solving while also serving to protect the larger organization from risk — security, operational, reputational, and so forth.</p>

<p>In short, constraints force the issue of asking how might we do this differently. This mindset leads to innovation and gives organizations a fighting chance - being part of the disruption instead of being the disrupted.</p>

<h2 id="tldr">tl;dr</h2>

<p>In business, organizations are either growing or dying. Because of this, every business needs to behave with the mindset of a Startup. Failure to do so leads to complacency, malaise, and an inability to adapt to market changes - let alone drive those changes.</p>]]></content><author><name></name></author><category term="mindset" /><summary type="html"><![CDATA[Every business is a Startup. You're either growing or dying. Embracing a Startup mindset is the only salvation for established organizations.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.evanmaxon.com/assets/images/avatar.png" /><media:content medium="image" url="https://www.evanmaxon.com/assets/images/avatar.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry><entry><title type="html">How I Proved a Startup Wasn’t Worth It - For Only $500 (With Details)</title><link href="https://www.evanmaxon.com/blog/how-i-proved-a-startup-wasnt-worth-it-for-only-500-with-details" rel="alternate" type="text/html" title="How I Proved a Startup Wasn’t Worth It - For Only $500 (With Details)" /><published>2019-06-10T15:00:00+00:00</published><updated>2019-06-10T15:00:00+00:00</updated><id>https://www.evanmaxon.com/blog/how-i-proved-a-startup-wasnt-worth-it-for-only-500-with-details</id><content type="html" xml:base="https://www.evanmaxon.com/blog/how-i-proved-a-startup-wasnt-worth-it-for-only-500-with-details"><![CDATA[<p>In one week* - and for just $498.38 - I was able to decide that an idea I’d been mulling over for the past 3 years was not a viable business endeavor. Why share a failure? Because success stories abound, but I learn more from what didn’t work than from what did. What follows is a post mortem of <a href="https://howto.sendbetter.email">SendBetter.Email</a>, a video tutorial series.</p>

<h4 id="the-hypothesis">The hypothesis</h4>

<blockquote>
  <p>Small business and non-profit marketers will subscribe to a tutorial series that details the proper way to setup and use popular email marketing platforms.</p>
</blockquote>

<p>For several years I freelanced providing digital strategy and hands-on support for small businesses and non-profits. As the Digital Swiss Army Knife, I managed and built websites, administered servers, and ran email marketing platforms just to name a few responsibilities. One commonality all new clients shared was that their email marketing platform, usually Mailchimp, was a misconfigured mess.</p>

<p>As a result of this experience, I thought that there was an opportunity to build a subscriber-based website providing this same type of guidance on a larger scale than what I could manage by working with clients directly. Two sites served as inspiration — <a href="https://web.archive.org/web/2019/http://railscasts.com/">RailsCasts</a> (which I subscribed to) and <a href="https://gorails.com/">GoRails</a>.</p>

<h4 id="the-setup">The setup</h4>

<p>Here’s where I close the loop on the ‘one week*’ above. Setting up the infrastructure took closer to six (6) months, while the test only took one week. Yes, this setup was overkill (not lean) and could have been done with much less effort. I did learn how to build a custom WordPress theme in the process — so not all was wasted.</p>

<p><strong>The infrastructure</strong> was made from combining and configuring the following services and platforms.</p>
<ul>
  <li><a href="https://wordpress.org/">WordPress</a> - the self-hosted version</li>
  <li><a href="https://restrictcontentpro.com/">Restricted Content Pro</a> - A premium WordPress plugin to handle subscriptions and access to content</li>
  <li>A custom (read: home-made) WordPress theme</li>
  <li><a href="https://vimeo.com/">Vimeo</a> - video hosting</li>
  <li><a href="https://mailchimp.com/">Mailchimp</a> - The initial subject matter and email platform</li>
  <li><a href="https://stripe.com/">Stripe</a> - Payments platform</li>
  <li><a href="https://www.luckyorange.com/">Lucky Orange</a> - Heat mapping and video recordings of visitors</li>
</ul>

<p><strong>The initial library of content</strong> was eleven (11) episodes mixed between freely available to view (no subscription necessary) and premium episodes (subscription required). <em>My assumption</em> was that visitors would be more likely to subscribe if there were several tutorials available. This assumption turned out to be irrelevant, but did expand the timeline to build the site before launching the tests.</p>

<h4 id="initial-test-objectives">Initial test objectives</h4>

<p>Realizing that the likelihood of having a runaway success from the start was slim, I wanted to establish benchmarks and start the process of optimizating the ads and of the site.</p>

<p><strong>For the ads</strong>, I wanted to learn if general ads promoting the site would perform better than ads for a specific episode. And, using the <a href="https://www.facebook.com/business/help/170372403538781">Facebook Dynamic Creative</a> feature, I wanted to find a combination of images and copy that converted well.</p>

<p><strong>On the site</strong>, I wanted to see if people would watch the  videos and/or read the transcripts; learn what rate a visitor would explore other episodes (pages per visit); and, optimistically, what rate people would subscribe.</p>

<p>Ultimately, the subscription/conversion rate would allow me to calculate the cost per acquisition (CPA) — the key metric to determine the viability of this concept. With a CPA established, you can learn if revenue generated from a subscriber is more or less than the cost of the ads to get that subscriber.</p>

<h4 id="why-facebook-first-or-why-facebook-first">Why Facebook first? Or, why Facebook first.</h4>

<p>Another assumption I had was that Facebook would be the <em>best</em> platform to market through. And by <em>best</em>, I mean that it should allow me to target a relevant, niche audience at a lower cost than another platform (eg. Google Ads).</p>

<p>Based on my original hypothesis, and using Facebook’s advertising platform that leverages demographic information on all of their users, I was able to create a <strong>targeted audience of ~26,000</strong> that “Liked” or have a job title in entrepreneurship, small business marketing, email marketing, and nonprofit marketing.</p>

<p>And to explore which ad composition — both image and copy — would perform better than others, <a href="https://www.facebook.com/business/help/170372403538781">Facebook Dynamic Creative</a> feature was very compelling. Effectively, by uploading up to 10 images, 5 headlines, 5 post descriptions, and a few other items, Facebook will mix-and-match the above and randomly display them until some start to outperform others.</p>

<p>One feature of Facebook that I wasn’t able to benefit from, and might have made a difference in my experience, is to leverage an existing audience — either from a business Page or an existing email list.</p>

<h4 id="facebook-inaction">Facebook (in)action</h4>

<p>My first Facebook frustration was with the infrastructure required to run a single ad. In addition to a Facebook Business Manager account, and an Advertising account, a Facebook Business Page needed to exist. While existing businesses probably already have this, setting these up to simply run some tests was annoying.</p>

<p>The next frustration was figuring out how to navigate through the campaign setup to get to the Dynamic Creative feature. This was less than intuitive. Thanks, Mark!</p>

<p>Facebook ads were launched on a Thursday. By Saturday I knew that the current approach wasn’t going to result in enough traffic fast enough to learn and iterate. The default setting for Facebook ads is to spread out your desired budget over 30 days. On Saturday, I changed this to 7 days but traffic was still slow to come by.</p>

<p>For this type of testing, Facebook’s pricing model isn’t conducive. During setup, the only option provided is impressions — a cost per thousand (aka CPM). In other words, Facebook wants to charge based on the number of times it shows the ad, and not based on the number of times a user clicks on it. Thus, our interests aren’t aligned.</p>

<figure class="image">
<img src="/assets/images/facebook-ads-cpm.png" alt="Facebook Ads report showing a CPM pricing model and an effective cost-per-click of $6.64" />
</figure>

<p>As a result of a CPM pricing model, I received low traffic from Facebook at an effective cost-per-click (CPC) of $6.64. In other words, while Facebook charged me to show the ad, it cost me $6.64 for each actual visitor.</p>

<h4 id="the-first-iteration--google-ads">The first iteration — Google Ads</h4>

<p>By Sunday I was ready to try something new. My $46.47 paid to Facebook had resulted in 7 visitors.</p>

<p>My first visitor, as a result of Google Ads, came quicker and for less money than Facebook — but still not the volume I was hoping for.</p>

<p>However, I did make a mistake when switching to Google Ads that resulted in lower traffic, too. Google estimated that there are 10,000 relevant searches per month, which breaks down to an average of 333 searches per day. And, at an industry-wide average click-through rate of just under 2%, that’s only an estimated 7 visitors per day. Still not enough site traffic to learn quickly and iterate. To help with this, Google does a nice job providing recommendations on a daily basis to improve your paid search efforts. I accepted almost all of these.</p>

<p>By Thursday, a full week after launching the Facebook ads, I’d spent $83.91 with Google Ads and received 40 visitors to my site — mostly to the specific episode. That’s a CPC of $2.10.</p>

<figure class="image">
<img src="/assets/images/google-ads-cpc.png" alt="Google Ads report showing 40 visitors for $83.91 spent, an effective cost-per-click of $2.10" />
</figure>

<h4 id="observing-my-visitors-behavior">Observing my visitors behavior</h4>

<p>Remember that what I wanted to learn was if visitors would watch the full episode videos and/or read the transcripts; learn how curious they would be about other content was available by visiting other episodes; and, if any would subscribe.</p>

<p>To track visitor behavior, I leveraged three services — Google Analytics, Vimeo, and Lucky Orange. Of these three services, Lucky Orange was by far the most useful in helping me determine to pivot to the next concept instead of persevering with SendBetter.Email — and my use of their service only scratched the surface.</p>

<p><strong>What exactly is a Lucky Orange?</strong> They bill themselves as “The Original All-in-One Conversion Optimization Suite,” or as “DVR for your site.” If you’re familiar with services like <a href="https://www.hotjar.com/">HotJar</a>, <a href="https://mouseflow.com/">Mouseflow</a>, or <a href="https://sessioncam.com/">SessionCam</a> — just to name a few — then you are already familiar with the market Lucky Orange competes in.</p>

<p>Of the services Lucky Orange provides, I relied largely on visitor recordings.</p>

<p><strong>What exactly did I learn?</strong> Visitors appeared to be only interested in solving a specific problem and not interested in a source for additional, related content.</p>

<ul>
  <li><strong>13%</strong>. The number of visitors that visited more than one page.</li>
  <li><strong>17 seconds</strong>. The average time spent on the site per visit.</li>
  <li><strong>Zero (0)</strong>. No one watched a video, according to Vimeo.</li>
</ul>

<p>While watching replays of visitors that did stay long enough to register in Lucky Orange I observed that most were on mobile devices, they did scroll deep on the page, but did not appear to be scrolling slow enough to fully digest the content. This leads me to believe that the format (video tutorial) isn’t the right format for this audience.</p>

<h4 id="next-steps">Next steps</h4>

<p>Based on these observations, my next step would be to change the format of an episode. Currently, the content is a video tutorial with a transcript and I would change it to be screenshots with itemized steps to follow. My tests would then focus on increasing the session duration (benchmark: 17 seconds) and decreasing the bounce rate (87%).</p>

<p>By <strong>increasing the session duration</strong>, the assumption is that visitors would be digesting (and possibly acting upon) the content.</p>

<p>By <strong>decreasing the bounce rate</strong>, the assumption is that the visitors found the original content valuable enough to explore other content on the site.</p>

<p>While only the session duration is needed to test the change in format, the bounce rate shows if these visitors are also likely to consider subscribing — my original hypothesis.</p>

<h4 id="next-next-steps">Next, next steps</h4>

<p>If the session duration did improve, but the bounce rate remained high I might try to find ways to better promote other episodes, or buy ads for other episodes that might appeal to a different audience — an audience that might have a greater tendency to subscribe!</p>

<p>If neither the session duration or the bounce rate improves, I would revisit the ads as well as promote other episodes.</p>

<h4 id="in-hindsight">In hindsight</h4>

<p><strong>Build less. Test sooner.</strong> I spent too much time going from concept to testing. Not counting the years I spent thinking about doing this, I spent about 6 months (in my spare time) getting to the place where I could run the tests. This clearly was not a minimally viable product for the purposes of testing the concept.</p>

<p>What I could have — should have — done instead.</p>

<ul>
  <li>
    <p><strong>Use a static website</strong> with one(ish) post and other “protected” posts that required a subscription. While I did learn how to build a custom WordPress theme as part of this experiment (a plus!), reducing the scope would have sped up the setup time. And, I could have simulated the idea that there were other tutorials available — but only to subscribers — without actually spending the time to make those tutorials.</p>
  </li>
  <li>
    <p><strong>Test the post format from the beginning</strong>. This also would have been a time saver and validated from the beginning whether or not the video format was the preferred format.</p>
  </li>
</ul>

<p>In other words, reducing the scope would have cost less and allowed for quicker hypothesis testing.</p>

<p><strong>Google Ads is better than Facebook ads.</strong> Don’t get me wrong, Facebook ads can be very powerful and useful. However, for my scenario, I found Google Ads to be far more effective — cost and garnering traffic.</p>

<ul>
  <li>
    <p><strong>Google Ads is contextually relevant</strong>, while Facebook ads are out of context for the viewers. By this, I mean that when someone encounters an ad in a Google search result, they are related to the question they’ve turned to Google to answer. Users of Facebook, on the other hand, encounter the ads as they are scrolling through their News Feed and not relevant to the mindset they have at the time.</p>
  </li>
  <li>
    <p><strong>CPC is better than CPM</strong>. With the goal of getting traffic to the site, Google Ads’ pricing model (cost-per-click) aligns our interest with theirs. By charging based on impressions (CPM), Facebook is systematically not incented to care about relevant clicks to the extent Google Ads is. This difference also makes Google Ads more cost effective than Facebook.</p>
  </li>
</ul>

<p><strong>Episode ads performed better than generic ads.</strong> On both platforms, the ads for a specific tutorial episode had a much higher click-through rate than the ads for my overall concept.</p>

<h4 id="final-thoughts">Final thoughts</h4>

<p>Did I give up too soon? Maybe.</p>

<p>Though, after 6 months of prep work, the realization that maintaining this effort was going to require weekly dedication to new content, and the lack of traction of visitors showing broader interest, I decided to re-energize myself by moving on to the next idea I’d been mulling. Namely, sharing my thoughts on product development here.</p>

<p>I’d love to know what questions, thoughts, or critiques you have. Send those to me at evan [at] productownering.com.</p>]]></content><author><name></name></author><category term="lean-testing," /><category term="muse," /><category term="testing" /><summary type="html"><![CDATA[Spending only $498.38, I was able to decide that an idea I'd been mulling over for the past 3 years was not a viable business endeavor.]]></summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.evanmaxon.com/assets/images/avatar.png" /><media:content medium="image" url="https://www.evanmaxon.com/assets/images/avatar.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry></feed>