<?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 David Adams on Medium]]></title>
        <description><![CDATA[Stories by David Adams on Medium]]></description>
        <link>https://medium.com/@davidmjadams?source=rss-88e6ee670484------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RxvNrGeE2EqOO6Ys7MtTfA.jpeg</url>
            <title>Stories by David Adams on Medium</title>
            <link>https://medium.com/@davidmjadams?source=rss-88e6ee670484------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 13:51:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@davidmjadams/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[Slop Defence: holding back the tide]]></title>
            <link>https://davidmjadams.medium.com/slop-defence-holding-back-the-tide-8997e24d6152?source=rss-88e6ee670484------2</link>
            <guid isPermaLink="false">https://medium.com/p/8997e24d6152</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[thoughts]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[David Adams]]></dc:creator>
            <pubDate>Mon, 04 May 2026 12:16:01 GMT</pubDate>
            <atom:updated>2026-05-04T12:16:01.254Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nFPQA9BsVavQPy17.jpg" /></figure><p>There’s an important question about agent coding that’s not been answered yet. It’s clear starting software has changed forever… What’s less clear, is what happens next.</p><p>It’s impossible to avoid all the talk of people vibe-coding an app over a weekend. Or one-shotting something impressively complex. The chatter is non-stop. At this point, AI coding feels like magic. The speed to MVP is immense.</p><p>But it’s not that simple. Starting has always been the easy part.</p><p>Writing new software is simple. It’s a blank page. No decision debt, no technical debt, only possibilities.</p><p>I’ve found it takes about 18–24 months to truly feel the weight of your past decisions. Up until that point, you can keep adding features, making quick trade-offs, and you won’t get burnt. It’s why more elaborate architectures feel like overkill at first. Often they are. Who needs inversion of control when you’re starting?</p><p>Over time, you start to feel the tension of making changes. It’s easy to fall into the trap of “we don’t dare touch that part”.</p><p>When that happens, teams start arguing: do we patch around it or rewrite it?</p><h3>Speed-run the start, speed-run the… entropy?</h3><p>Vibe-coded apps speed-run the “easy” phase. They get you from idea to working software faster than ever before.</p><p>It’s becoming increasingly clear that this is the future. I don’t see this going back in the box. Most software will eventually be written this way.</p><h3>How to fight the tide</h3><p>I’m bullish that the old best practices become more important than ever. Not to make us feel like we’re important, but to hold off the inevitable decay of the codebase. Best practices are hard-won lessons from past mistakes. They give you guardrails. They make changes feel safe. They keep the humans in touch with the core of the business.</p><p>But more than those, DDD becomes essential. By modelling your software to accurately represent the real world and your users’ problems, you keep the connection between the code and the humans.</p><p>Tools like Cucumber, where you get human and machine-readable product specs, feel like they’ll matter more than ever. If it were possible to buy shares in a testing framework, I’d go all in.</p><p>Too human and you end up with loose instructions and scant guardrails. Too robot and the humans disengage.</p><h3>What I’ve seen</h3><p>I’ve spent a fair amount of time with AI coding in recent months. I’ve experienced everything from the initial “holy-moly, this is going to change the world forever” to “no robot, it didn’t work, try again… NO, try again”.</p><p>The pattern is pretty clear: with the right guardrails, you can get far. Without them, you get a lot of convincing-looking code, with nothing working.</p><p>By ‘guardrails,’ I mean proper testing at all levels, well-defined tasks, constraints, and clear scoping.</p><h3>The ageing question</h3><p>How does this all age in a long-lived system? I don’t think we’ve really seen yet.</p><p>If vibe-coding speed-runs the creation process, does it also speed-run the natural entropy of software? Do you hit the “no one touches that bit” phase sooner?</p><p>And if it does, does that patch-vs-rewrite argument show up earlier, too? Not because the code is worse, but because nobody has enough context to change it safely.</p><p>If you build this way for years, at what point does the human fall into a diminished-responsibility trap? When nobody knows why anything is as it is. Do you just point more robots at it and hope for the best?</p><h3>Thinking “Only machines need to be able to read it” is dangerous</h3><p>Asking the AI to explain the code is useful. It can help you get your bearings.</p><p>But I’ve heard people suggesting it doesn’t matter if you can’t read the code because only machines need to read it now.</p><p>For now, and I suspect for a long time, that’s a nonsense.</p><p>Because after all, it doesn’t “know” anything. It can’t “know” anything. It’s just unbelievably good at predicting the next token. But it’s statistics, not knowledge, and that facade of understanding can be dangerous. You do know, so if you’re going to hand off the building to a machine, please ensure you have guardrails that you define. You control. You understand.</p><p>By following the old best practices of a well-defined domain, proper architectural patterns and robust, human-readable tests, you give yourself the best chance of building something that lasts.</p><p><em>Originally published at </em><a href="https://simpleshapes.io/articles/slop-defence-holding-back-the-tide/"><em>https://simpleshapes.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8997e24d6152" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You won’t be left behind by AI]]></title>
            <link>https://davidmjadams.medium.com/you-wont-be-left-behind-by-ai-1c03b0322270?source=rss-88e6ee670484------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c03b0322270</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[David Adams]]></dc:creator>
            <pubDate>Fri, 14 Apr 2023 15:27:47 GMT</pubDate>
            <atom:updated>2023-04-14T15:27:47.308Z</atom:updated>
            <content:encoded><![CDATA[<p>I can’t decide whether I should be excited or terrified by the current pace of AI developments. On thinking about it, the answer is yes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sbeXJYFs6ZNKcCMv.jpg" /><figcaption><em>Source: </em><a href="https://unsplash.com/@jeremybishop"><em>Jeremy Bishop</em></a><em> via </em><a href="https://images.unsplash.com/photo-1502209524164-acea936639a2?ixlib=rb-4.0.3&amp;ixid=MnwxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8&amp;auto=format&amp;fit=crop&amp;w=1470&amp;q=80"><em>Unsplash</em></a></figcaption></figure><p>A wave is coming. If you don’t learn to surf now, you will be swallowed up and left for nothing. The wave is AI.</p><h3>This isn’t true</h3><p>It is true that a lot of people will make a lot of money from AI. I’d be surprised if it doesn’t fundamentally change most industries. However, this doesn’t mean you have to swim with the tide (I’m done with sea metaphors now). If you are aware of the new possibilities, it’ll work out just fine.</p><h3>You don’t have to retrain in AI</h3><p>If AI is the area you find most interesting, please do pursue it. The world needs your passion and creativity. If it’s not for you, which will be the case for most people, that’s fine too. Continue doing what you’ve always done. Follow your instincts. Use your unique combination of talents (and it is unique, no one has your lived experience) however you are driven to. Just maintain a keen focus on how you will use them to bring value to the world. Or, don’t. You don’t have to bring anything to anyone if that’s not what drives you.</p><p>You can benefit from AI, without being an expert. AI-powered tools like <a href="https://www.grammarly.com/">Grammarly</a> or <a href="https://openai.com/product/gpt-4">GPT-3/4</a> help writers improve their work without needing much (if any) knowledge of AI.</p><h3>We have always progressed</h3><p>Humans have an immense capacity to change and adapt. Just look at how most people, though often traumatised by it, made it out the other side of the pandemic intact.</p><p>Open source changed software development for the better. This was a positive development. Starting a new software company was once prohibitively expensive and time-consuming. Then suddenly, you didn’t need to write every low-level component yourself. Whole packages existed to solve recurring problems. Progress accelerated.</p><p>Just as industrialisation was a huge change catalyst, the internet, smartphones, and now AI are part of the progress of nature. AI has transformed various industries such as the automotive industry with self-driving cars or the retail industry with AI-powered chatbots improving customer service.</p><h3>How to survive?</h3><p>Smart, talented, curious people will always prosper. As long as the thing that drives you is a desire to create and bring new things into existence that didn’t exist before, you’ll flourish, whatever comes.</p><p>Tools change. Human creations continue, but in new, previously impossible forms.</p><h3>Humans can human</h3><p>In his book <a href="https://www.waterstones.com/book/deep-medicine/eric-topol/9781541644632">Deep Medicine</a>, Eric Topol argues that while AI will take over many aspects of analysis, prediction, and treatment, doctors will be able to return to the more human-centric aspects of their profession, which bureaucracy has eroded. By providing real human warmth and care, healthcare professionals can improve patient outcomes and experiences.</p><p>This can be true for almost all industries. In finance, AI-powered tools are helping with fraud detection and portfolio management, allowing financial advisors to focus on building relationships with clients and providing personalised advice.</p><p>User satisfaction will be more important than ever. If we can remove the mundane and the bureaucratic from our remit and leave it to the machines, an exciting possibility emerges. We can regain some of what we’ve lost. By leveraging this new breed of advanced computation, we can lean into what it lacks: our humanity. With the release from the admin burden, we will be able to achieve more, faster than ever.</p><h3>Don’t hide, embrace</h3><p>Hiding is not the answer. Shutting off to the world around and hoping it will all go away won’t help. You can smash as many Spinning Jennies as you like; the mills are never going to be the same.</p><p>A world of new possibilities is coming. It doesn’t matter whether it starts with a stick of butter or a million GPUs. Keep up to date. Experiment. Flow. Connect. Concentrate on what you want to bring to the universe and use whatever the best tool available for <em>you</em> is.</p><h3>Original prompt</h3><p>I wrote this on a plane. Seeing as I’m writing about AI, I thought I’d practice what I’m preaching. I used GPT-4 as my editor; below is the starting prompt I used to tweak the text.</p><p>You are my copy editor. Please provider grammatical and structural improvement suggestions for the below text.</p><p>Write edits like this: [text to remove”new text], so I can see what changes are suggested. You must not change the overall tone or style, you must not make significant changes, it must appear to be written by me with the same emphasis. Your goal is to make the writing more easy to read and engaging and to point out any major inaccuracies or omissions.</p><p>The text is written in markdown.</p><p>Text below: …</p><p><em>Originally published at </em><a href="https://simpleshapes.io/articles/you-wont-be-left-behind/"><em>https://simpleshapes.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c03b0322270" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build less, listen more — the antidote to failed products]]></title>
            <link>https://davidmjadams.medium.com/build-less-listen-more-the-antidote-to-failed-products-14bd0c762a64?source=rss-88e6ee670484------2</link>
            <guid isPermaLink="false">https://medium.com/p/14bd0c762a64</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[David Adams]]></dc:creator>
            <pubDate>Mon, 20 Dec 2021 13:55:43 GMT</pubDate>
            <atom:updated>2021-12-24T09:07:07.791Z</atom:updated>
            <content:encoded><![CDATA[<h3>Build less, listen more — the antidote to failed products</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uit8cl-JBeTmpctXQmUrnA.jpeg" /><figcaption><a href="https://unsplash.com/@brett_jordan">Brett Jordan</a> via <a href="https://unsplash.com/photos/mS20cgMWaPw">Unsplash</a></figcaption></figure><p>Picture the scene; you’re about to start work on a greenfield project. It’s a wide-open space, and you can’t wait to jump in and get started. This is what it’s all about — the limitless potential of an idea.</p><p>Once you get started, reality bites a little. The limitless potential begins to surface some limits, some hard edges that complicate matters. It’s so, so easy to fall in love with your idea, go heads down into build mode and not come up for air until you ship.</p><h4>You’re going to fail.</h4><p>You can’t just pick an idea, build it, close your eyes and hope for the best. You can’t just assume folks will care that it exists. You might get lucky, but nine times out of ten, you won’t. Then it will be too late, and you will be in too deep and out of money. But there is a simple antidote.</p><h4>Get. Feedback. Every. Step.</h4><p>Not feedback that sounds like “oh yeah, I would use that” or worse, “I wouldn’t use it, but I can see others using it”. Accept no less than people paying money for your product to make progress in their lives. If your product is free, accept no less than users taking the action that makes you money. Be it commission, service fees or whatever. Until you are sure that people will use it and there is a path to making money, don’t go deep into building. Build as little as possible and learn at every step. Enhance your understanding of your users and their needs with each turn.</p><p>Build less. Listen more.</p><h3>Build less</h3><p>Eric Ries told us to “cut your product in half, then halve it again”. This is advice I’m guilty of ignoring. Even Ries says he is guilty of this. When embarking on a new product or significant feature, ask yourself this: Could I learn the same amount in a shorter amount of time? If you figure out how to do that, ask the same question again. Be brutal.</p><p>If we are building something nobody wants, who cares if it’s on time, on budget, elegant, scalable. The worst software is beautifully written, following all the best software patterns, but barely anyone using it. It’s waste of the worst kind — a total waste of talent and time. I’d take junk software that is heavily used over well-written software any day of the week. Sure, it comes with a different set of problems. But with usage, you get time, and you can turn your software into beautiful software with time.</p><h4>Just enough</h4><p>The most prolific makers appear inhuman. Shipping new products seemingly daily. The trick is not grinding at all hours; it’s doing just enough to get feedback. Often it may be a webpage with a signup form. Or maybe just a Typeform and a payment link. It’s usually all you need to start learning and course-correcting. Build a mechanism to get enthusiasm, speak to your potential users and refine. Do this indefinitely. You don’t need a backlog; it will be outdated in about four days.</p><p>Everything you build is not covering your bases; it’s weakening your proposition, making it harder to see the signals of what’s working and what isn’t. It’s committing your team to work that might not get used.</p><p>You can get far by providing a facade of a complete end to end journey, missing all but 100% essential features. Manual steps are your friend until you have volume.</p><h4>Should I add more?</h4><p>Maybe you feel like you need to offer choice to make people happy? All this means is you don’t know their problems well enough, or you’re going to too broad a segment. Find the power users first, build out around them and convert others to see it their way. Don’t keep throwing stuff until something sticks.</p><p>You can’t build your way to product-market fit. Without a problem people want to be solved, a job they need to be done building won’t help.</p><h3>Listen more</h3><p>You need to talk to your users and get out of the way. Listen more, listen deeply. Don’t frame questions around confirming/denying your assumptions. Talk over a few subjects; you’re getting warmer when you detect strong emotions. Dial in. Would they pay for it, how much? If not, then it’s probably not a must-have solution. People love an opportunity to talk about themselves. It’s human nature. With a small incentive, it’s easy enough to get people on a call. Most people want to help.</p><p>Do you understand all of their problems? Hint; you don’t. You probably won’t ever. But ask yourself this: are you doing everything you can to make sure your understanding improves week on week? If not, try harder.</p><h4>Where do I start?</h4><p>Before long, you will have a bank of user issues waiting to be solved. The next problem is knowing where to focus. There’s not an easy answer here, but I find using the following two questions helpful.</p><p>Is the problem causing strong emotions? Frustration? Passion? If so, you may be on to something.</p><p>Can you imagine a world where you can make money from solving this problem?</p><p>Yes to both, and we’re in business.</p><h3>Finally, Focus</h3><p>How many core problems are you working on? If the answer isn’t one, you’re at risk.</p><p>Focus, then focus again.</p><p><em>Originally published at </em><a href="https://simpleshapes.io/articles/build-less-listen-more/"><em>https://simpleshapes.io</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14bd0c762a64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everything starts today]]></title>
            <link>https://davidmjadams.medium.com/everything-starts-today-9786b54d194c?source=rss-88e6ee670484------2</link>
            <guid isPermaLink="false">https://medium.com/p/9786b54d194c</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[motivation]]></category>
            <dc:creator><![CDATA[David Adams]]></dc:creator>
            <pubDate>Fri, 10 Dec 2021 15:59:20 GMT</pubDate>
            <atom:updated>2021-12-10T15:59:20.767Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Skateboarder about to start skating" src="https://cdn-images-1.medium.com/max/1024/1*iJOeJKPH99faClKL6RHocQ.jpeg" /><figcaption>Source: <a href="https://unsplash.com/@narmanatakan">Atakan Narman</a> via <a href="https://unsplash.com/photos/yiuzbxR1c5s">Unsplash</a></figcaption></figure><p>I like meditation, but I never do it. I did manage my at-best-annual session recently. The session spoke of approaching life as if you’d just arrived here on earth, straight into your life. Without all the past baggage. Without the pre-built neural pathways. What if you just took things on present facts and acted accordingly. How would your reactions differ? I found this surprisingly enlightening and reassuring.</p><p>While attempting meditation, I probably shouldn’t have quickly made it all about work. But I did. It is a helpful lens.</p><p>I’ve spent the past god-knows-how-long working in the startup world. I love it. I also hate it sometimes. It’s a never-ending stream of hard problems. Every success uncovers the next hard problem, then feels less like a success. It’s hard not to be beaten down by it from time to time.</p><p>It’s supposed to be this way.</p><p>This is a note to self to say this is ok. Normal. Good. This is progress. Aristotle famously wrote, “The more you know, the more you realize you don’t know.” This is why new ideas always seem alluring because you haven’t uncovered the hard edges yet. You can’t get anywhere worthwhile without hard work and perseverance. It is supposed to be hard.</p><p>So here’s the point. Take each day as it comes. Approach it knowledge in hand, but without past fears and biases. Make it your goal to end every day better than you started. Each week better than the last. Each month… ah, you get the point.</p><p>Make sure you celebrate the successes. They are what it’s all about.</p><p>Let’s begin. Again.</p><p><em>Originally published at </em><a href="https://simpleshapes.io/articles/everything-starts-today/"><em>https://simpleshapes.io</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9786b54d194c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How we’ve embraced One-Pagers at Poncho]]></title>
            <link>https://davidmjadams.medium.com/how-weve-embraced-one-pagers-at-poncho-aa18aa62be91?source=rss-88e6ee670484------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa18aa62be91</guid>
            <category><![CDATA[one-pager]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[David Adams]]></dc:creator>
            <pubDate>Wed, 15 Sep 2021 08:50:16 GMT</pubDate>
            <atom:updated>2021-09-15T08:50:16.009Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aLNATn4_8tXJS8Cr.jpg" /></figure><p><em>If you just want to see the one-pager template we use, skip to the bottom of this article</em>.</p><p>I’ve been from the school of <em>what problem are we actually trying to solve</em> for as long as I can remember. But this was more in the conversations we were having, rather than anything too strategic. We’d do the research, have the questions and debate, then everything would go into JIRA (sorry) as a story. Losing the fidelity and nuance.</p><p>For a while now at <a href="https://poncho.care/">Poncho</a>, we’ve been using <a href="https://www.productplan.com/learn/product-one-pager/#:~:text=A%20product%20one%2Dpager%20makes,confidence%20in%20the%20decision%2Dmaker">One-Pagers</a> to document product themes and assess priorities. We use these themes in tandem with the <a href="https://info.amplitude.com/north-star-playbook">North Star Framework</a>, to tie everything back to customer and business goals. These then go into a <a href="https://www.prodpad.com/blog/how-to-build-a-product-roadmap-everyone-understands/">Now, Next, Later roadmap</a>. It’s working out well.</p><p>When I started looking into it, I struggled to find many examples of one-pagers people were using in the wild. So I thought it might help someone, somewhere if I shared mine.</p><p>It draws on the work of some great minds, <a href="https://twitter.com/rjs">Ryan Singer</a> (particularly <a href="https://basecamp.com/shapeup">Shapeup</a>), <a href="https://twitter.com/johncutlefish">John Cutler</a>, <a href="https://twitter.com/simplybastow">Janna Bastow</a> and others. I found John Cutler’s <a href="https://medium.com/@johnpcutler/great-one-pagers-592ebbaf80ec">Great One-Pagers</a> especially helpful.</p><p>We’ve been using variations of this format with success for a while. If some of the sections/wording seem like they have been lifted, almost verbatim, from the works mentioned above, trust your instincts.</p><p>Below is the template that our one-pagers start from (we don’t always use all sections), with explanations of what is expected in each section.</p><p>We use these to write-up themes, which are high-level bodies of work — based on user outcomes rather than features. Once we have the required understanding of the problem, we write up a selection of user stories, which have a simpler format. We’ve avoided the common <em>As a user, I would like, So that</em> format. While I understand the good intention this format has, I have so often seen it misused so that all you end up with is a feature requirement with a bunch of filler words. We’ve stuck to simple, plain English descriptions. So far, so good.</p><p>A key point here is that the stories still don’t start as “build exactly this”, but give a general problem to solve and some boundaries, in the context of the user and their problem.</p><p>I’ve learnt a few lessons so far. In an early-stage startup, you often can’t justify decisions with hard data — you’d mostly be data dredging and finding patterns in anomalies. You have to rely more on qualitative sources (user interviews, customer feedback) and even gut instinct. As you scale and have enough customers and data to meaningfully benchmark with quant data you can add this to your arsenal and make a solid case based on numbers.</p><p>Here are the templates, I hope they are useful for someone :)</p><p>This is the format we should aim to use for all significant new work. You only need to include the sections where there are relevant details. One-pagers can cover work that could take anywhere between 1 week (tactical) and 3 months (strategic).</p><p>Less than 1 week and it’s probably too small to need this, more than 3 months and it’s probably too long a feedback loop. Just a guideline — YMMV.</p><p>Some of the below might appear like it requires certainty. It doesn’t. But It does force you to stake a claim. You’re not expected to know the exact probabilities of success, but stating clearly what you know with some certainty and what is little more than an educated guess is important.</p><h3>One-pager theme template</h3><h4>Brief (tweet-length)</h4><p>Summarise the work in a sentence or two. What’s the background and why is this in consideration. Remember, this is a bet — what are we betting on? Is it high-risk high-reward or a sure thing?</p><h4>What’s the problem being solved?</h4><p>Is it business (make more money) or user (achieve a goal)? What is wrong with the current state, what problem are people facing? How can we improve this? What is the ideal outcome?</p><h4>North star input</h4><p>Which North star input does this relate to? How will this affect it?</p><h4>Customer feedback?</h4><p>Any direct feedback from customers relating to this? Requests from departments or clients etc? Have we tried to solve this problem before? What happened?</p><h3>Success criteria</h3><h4>What’s the hypothesis?</h4><p>If we solve this problem, what will happen? Will it lead to greater engagement? Better retention? More revenue? What would success look like?</p><h4>How can we measure success?</h4><p>Pick one key metric as a proxy for this outcome, how can we track it and what numbers indicate things have gone well?</p><h4>Pivot/proceed/pull gates</h4><p>We don’t want to ship and hope. We don’t want to chase a sunk cost. At what points and what metric measurements should we try something different, keep going or pull the feature entirely?</p><p>Will we roll out with a subset of users? At what points do we increase user % in that pool? At what point do we do a full roll-out?</p><h3>Impact</h3><h4>Confidence</h4><p>Would you bet a significant amount of your own money on the success of this? What can we learn early on to double that bet? Or halve it? Or Reduce it to zero? What % chance of success would you say there is (gut-feel is fine)?</p><h4>Size of impact</h4><p>How big would success be for the company? What’s the financial size of the opportunity? What’s the size of the opportunity in user engagement?</p><h3>Timeframe</h3><h4>Big or small bet?</h4><p>Is this a big bet or a small bet? With big bets, they require a longer time investment 4weeks+, so should have a larger reward. That reward should be worth taking the risk of the time cost. Small bets should be wrapped up quickly, probably with lesser rewards. We don’t want to end up giving up too much time to these. If there is significant delay, it’s worth asking if we should stop altogether.</p><h4>Why now/cost of delay</h4><p>What do we unlock by moving on this now? What would happen if we waited 6 weeks? 3 months? 1 year? What’s the risk if we do nothing?</p><h3>Story Template</h3><h4>What is the desired user outcome?</h4><p>If we implement this feature, what do you hope will happen? What problem is it solving? For who? How might we measure this?</p><h4>Tweet length description</h4><p>In a sentence or two describe what you are proposing we implement.</p><h4>North star input</h4><p>Which North star input does this relate to? How will this affect it?</p><h4>What’s the cost of delay?</h4><p>What will happen if we don’t do this now, this week, this month, at all?</p><p><em>Originally published at </em><a href="https://simpleshapes.io/articles/how-weve-embraced-one-pagers/"><em>https://simpleshapes.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa18aa62be91" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CEO of the Product works, just not as you think]]></title>
            <link>https://davidmjadams.medium.com/ceo-of-the-product-works-just-not-as-you-think-57781b019400?source=rss-88e6ee670484------2</link>
            <guid isPermaLink="false">https://medium.com/p/57781b019400</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[David Adams]]></dc:creator>
            <pubDate>Thu, 02 Sep 2021 17:06:13 GMT</pubDate>
            <atom:updated>2021-09-02T17:06:13.660Z</atom:updated>
            <content:encoded><![CDATA[<p>Fifteen years ago 😅 Ben Horowitz wrote the seminal <a href="https://a16z.com/2012/06/15/good-product-managerbad-product-manager/">Good Product Manager/Bad Product Manager</a>. This included the famous statement: “A good product manager is the CEO of the product”.</p><p>A lot has been said about how this isn’t true. How PMs often don’t have budget authority, or others have greater decision making power. I agree with some of that sentiment. But it is more helpful to think of it in a leadership context.</p><p>A good Product Manager leads by example, works to build consensus on direction, trusts and empowers their team to do their best work, claims failures as their own and successes as the teams. This sounds a lot like some of the best CEOs I’ve worked with. Sure, a PM can’t do it by force or by stamping their authority… but neither would a good CEO in 99% of cases.</p><p><em>Originally published at </em><a href="https://simpleshapes.io/articles/ceo-of-the-product/"><em>https://simpleshapes.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57781b019400" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Go left — great acquisition and onboarding beats a great product]]></title>
            <link>https://uxdesign.cc/go-left-great-acquisition-and-onboarding-beats-a-great-product-5ae0358aa07a?source=rss-88e6ee670484------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ae0358aa07a</guid>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[lean-startup]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[David Adams]]></dc:creator>
            <pubDate>Tue, 26 Nov 2019 11:21:23 GMT</pubDate>
            <atom:updated>2019-11-27T22:39:32.642Z</atom:updated>
            <content:encoded><![CDATA[<h3>Go left — great acquisition and onboarding beats a great product</h3><figure><img alt="White arrow on green brick, pointing left" src="https://cdn-images-1.medium.com/max/1024/0*XPE43w4B-oqvGlMD.jpg" /><figcaption><em>Source: </em><a href="https://unsplash.com/@jannerboy62"><em>Nick Fewings</em></a><em> via </em><a href="https://images.unsplash.com/photo-1525081905268-fc0b46e9d786?ixlib=rb-1.2.1&amp;ixid=eyJhcHBfaWQiOjEyMDd9&amp;auto=format&amp;fit=crop&amp;w=1950&amp;q=80"><em>Unsplash</em></a></figcaption></figure><p>Last year, I was fortunate enough to attend a <a href="https://www.thesprintbook.com/">Design Sprint</a> workshop run by their creator <a href="https://jakeknapp.com/">Jake Knapp</a>. On Day one of the sprint, you create a map, where you outline the product journey and decide on which activity to focus.</p><p>To get things moving, the map starts with a high-level skeleton, using the actions: discover, learn, start. Framing the steps a user may take into broad categories. It’s helpful to get things moving and offers a framework for the team to work with. Once the map is drawn out, and the team is happy with it, you pick a target. This target will be the focus of the sprint. It could be a core product interaction, onboarding, acquisition etc. There was something Jake said when introducing this section that has stuck with me ever since. I’m paraphrasing, but he said if you are unsure where to focus, or you are stuck deciding between two areas — <strong>go left</strong>.</p><p>He went on to mention that from the hundreds of design sprints he’s run, he learnt that more often than not, the most important section is discover. Why? Because you only get one chance to make a first impression. If a customer doesn’t completely understand how your product will improve their life and how they can start using it straight away, you will almost certainly lose them. You can have the best product hiding behind your onboarding, if users don’t make it that far it may as well not exist.</p><h3>Focus on the product?</h3><p>More often than not, if the team know what they are doing and are in an environment which allows them to make the right calls, they will focus on creating a killer product. They listen carefully to their users and craft a solution that elegantly helps them fulfil their needs. This is great; it is essential for success.</p><p>But this isn’t the most important thing. At least, not in the early days when you are bringing a new product or significant feature to market. Without users, it doesn’t matter how great your product is. It isn’t going to solve their pains if you lose them on the homepage.</p><p>Likewise, if you have a fantastic feature that only 1% of your active users will find, 99% will gain nothing from its existence.</p><h3>Your funnel is a basic equation</h3><p>You need to focus on getting as many people through your acquisition/onboarding funnel as possible. Let’s assume your acquisition starts through your homepage. Say you get 1000 users to your landing page, and you get a 1% conversion to active users, congratulations, you have just acquired ten users. The more people you get through, the more opportunities you have to delight them. If you focus too heavily on the product and neglect the onboarding, sure, you may retain 70% of users. But 70% of 10 is 7. If instead, you built the most elegant, intuitive, onboarding process, you could do better with those 1000 visitors. If you got that conversion rate up to just 5%, you now have acquired 50 users. To retain the same number, you only need a retention rate of 14%. Get the conversion up to 10%, and you only need to retain 7%.</p><p>Before you start wondering, I don’t think the goal of building new products is to get seven users. But hopefully, you get the point. If you start moving these numbers, you can see a significant difference. The earlier in the funnel you effect, the greater magnitude of results. A 5% conversion with a 25% retention, beats a 1% conversion with 100% retention. Small improvements in conversion have a magnitude effect.</p><h3>Keep the core, hold off on the filler</h3><p>Your core is what’s important; it’s what will get users beyond your homepage. If the central problem your product is solving is important, they will put up with a less than 100% solution. Understanding their pains and are helping them to ease them matters. This won’t last for long; they will want more soon. In the early days, you are just trying to buy enough time to stay alive.</p><p>Until you have established a mechanism to acquire users at scale, you don’t need to handle them at scale. As long as the interface is polished, the low-frequency backend actions can be manual until they need to be. If nobody has signed up for a paid account, you don’t need a billing function yet. Embrace the <a href="https://en.wikipedia.org/wiki/Wizard_of_Oz_experiment">wizard of Oz technique</a>; it might just buy you enough time to flourish.</p><p><em>Originally published at </em><a href="https://simpleshapes.io/articles/go-left-great-acquisition-and-onboarding-beats-a-great-product/"><em>https://simpleshapes.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ae0358aa07a" width="1" height="1" alt=""><hr><p><a href="https://uxdesign.cc/go-left-great-acquisition-and-onboarding-beats-a-great-product-5ae0358aa07a">Go left — great acquisition and onboarding beats a great product</a> was originally published in <a href="https://uxdesign.cc/">UX Collective</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your engineering team is (probably) too big]]></title>
            <link>https://medium.com/swlh/your-engineering-team-is-probably-too-big-7072ddb123bd?source=rss-88e6ee670484------2</link>
            <guid isPermaLink="false">https://medium.com/p/7072ddb123bd</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[lean]]></category>
            <dc:creator><![CDATA[David Adams]]></dc:creator>
            <pubDate>Tue, 05 Nov 2019 10:21:50 GMT</pubDate>
            <atom:updated>2019-11-06T11:16:18.412Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Black and white image of a large crowd" src="https://cdn-images-1.medium.com/max/1024/1*YuMdHDRIqMT4RCi6pNbE8Q.jpeg" /><figcaption><em>Source: </em><a href="https://unsplash.com/@curranrob"><em>Rob Curran</em></a><em> via </em><a href="https://unsplash.com/photos/sUXXO3xPBYo"><em>Unsplash</em></a></figcaption></figure><p>Of all the places you can spend money in a tech company, the engineering team is often by far the largest cost-centre. Similar to digital ads, it’s also a place where, if you aren’t careful, you can waste a lot of money.</p><h3>If less is more, think how much more more would be</h3><p>When you’re trying to grow a new product, it’s the obvious place to start when you want to go faster. You want more customers and more revenue; the natural first place your mind lands is more features. Who doesn’t want more things? But to deliver more, you’re going to need more people.</p><p>Sure, more engineers mean more cost, but how else are you going to get everything you want shipped? It is a great feeling to see everyone super busy, cranking out lines of code and shipping features like there’s no tomorrow. This is what a high performing team looks like. Our velocity is through the roof! But hold on for a moment there. Since when did the quantity of output mean anything? Going fast is not a destination.</p><h3>Fix your leaky bucket</h3><p>Sadly, you can add 100, or 1000 engineers or designers or anyone else for that matter. You will then have an even longer list of things you absolutely must ship. More importantly, you are just burning cash. Just like a startup trying to grow rapidly by throwing money at ads, doubling down on acquisition, without giving a second thought to retention. Sure your acquisition numbers will look good, but you’ll retain naff all, and your costs will pass right through your bucket and out through the gaping hole in the bottom.</p><p>If you don’t have an engine that can reliably turn $1 into $2, think twice about meaningfully increasing your burn rate.</p><p>If what you build is not well targeted, does not solve a core need, then it’s the same as the leaky bucket — money spent without return. There’s no use saying it’s an investment for the future if you aren’t observing a key metric moving in the right direction</p><h3>Long term costs v short term costs</h3><p>Adding another member to the team is a permanent cost. It amazes me how much more willing management teams are to hire new people than spend a few hundred dollars on a piece of software to help the team do their job. Or have an engineer spend a couple of days manually implementing something instead of just buying it. When you consider the maintenance cost, it’s even more ridiculous.</p><h3>More is not more</h3><p>It’s an attractive fallacy, but it is a fallacy. Just because you are shipping lots of shiny new things, it doesn’t mean anything unless what you ship is valuable. More often than not, shipping less would get you further. If each new line of code, each new feature doesn’t help move your customers closer to achieving their goals faster or more thoroughly, then it is time wasted. If you built something nobody wants, you might as well have stayed in bed. It’s worth caveating that it is fine to ship the wrong thing if that is in service of learning what the right thing is. Expect to make missteps, but try to limit the investment they need.</p><h3>Communication complexity</h3><figure><img alt="Lines of communication illustration" src="https://cdn-images-1.medium.com/max/1024/0*JGCpHWwWXEmrenwR.jpg" /><figcaption><em>Source: </em><a href="https://www.leadingagile.com/author/davenicolette/"><em>Dave Nicolette</em></a><em> via </em><a href="https://www.leadingagile.com/2018/02/applying-brooks-law/"><em>Leading Agile</em></a></figcaption></figure><p>Small teams have an incredibly low communication burden, with a team of two or three, everyone is within immediate reach. A consensus can be reached quickly, and ongoing debates to satisfy a room full of egos shouldn’t come into it. The more people you add, the more obfuscation happens, the further the team are from the real problems. More management burden, more planning time, more meetings. The longer you can resist this, the better.</p><h3>Small but mighty</h3><p>The good news is, you can achieve a lot with a few people. Below are a few examples of teams that have achieved incredible feats with surprisingly small teams.</p><p>As of last month, <a href="https://notion.so/">Notion</a> had more than 1M users, all with just eighteen full-time employees. Not engineers, employees. <a href="https://superhuman.com/">Superhuman</a> raised $33M at a valuation of $280M in May, has just 10 engineers. Even <a href="https://basecamp.com/">Basecamp</a>, a 20-year-old company only has around 50 employees. They have over 3M accounts.</p><p>These aren’t simplistic products either, but they are all laser-focused on solving real problems their users have.</p><h3>How to do it</h3><h4>Make bets, you’re not expected to get everything right</h4><p>Randomness and chance still play a massive part in any success you may have, however well researched and prepared you are. This is fine; you have to embrace it. By making bets on what you believe to be the best way forward, you limit your exposure to risk. If you only spend two weeks on an experiment to test appetite for a specific feature, if it bombs, you haven’t wasted much time. If you go full steam ahead and drop six months of development effort into delivering all the bells and whistles, you have a huge exposure. You have zero guarantee that the effort was worth it.</p><h4>Record your decisions and goals, reflect and improve</h4><p>It’s all very well to experiment, but how do you know when your experiment has yielded results you can be confident in to build on? It’s hard, there’s no getting away from that. But by writing down your intentions, what you hope to build, what it should achieve, the investment needed, and how you’re going to measure success, you have a guide. Don’t stop here, if you don’t reflect on whether you met your goals after you launched and again after your feature has been in the wild for a month or so, you won’t be much further ahead than the blind feature machines.</p><h3>When is it safe to grow</h3><p>This isn’t to say never increase the size of your engineering team. Far from it. But if you are going to, make sure that you have a strong indication that the time and money invested has a high probability of making a return and getting you and your customers closer to achieving your goals. Once you’ve fixed the leaky bucket, you can then fill it up with water. Or engineers. Or whatever you want.</p><p><em>Originally published at </em><a href="https://simpleshapes.io/articles/your-engineering-team-is-too-big/"><em>https://simpleshapes.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7072ddb123bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/your-engineering-team-is-probably-too-big-7072ddb123bd">Your engineering team is (probably) too big</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[Creating a high performing product organisation]]></title>
            <link>https://medium.com/swlh/creating-a-high-performing-product-organisation-77d86ed4c86?source=rss-88e6ee670484------2</link>
            <guid isPermaLink="false">https://medium.com/p/77d86ed4c86</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[David Adams]]></dc:creator>
            <pubDate>Tue, 15 Oct 2019 08:58:54 GMT</pubDate>
            <atom:updated>2019-10-15T12:42:52.845Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SgqIk-4tApOmw2DG.jpg" /></figure><p>When you’re building a product, it’s tough to avoid the distractions and stay focused. Getting your entire product development team on song is crucial to your success.</p><p>Over the past few years, I’ve worked for organisations of all shapes and sizes; Startups, agencies, large orgs, and where I work now, Kamet Ventures a startup incubator. I’ve seen incredible high performing teams and disparate messes. There are a few key elements that rear their heads time and again; when done right can lead to great things, when done poorly can blow the whole thing up.</p><h3>The team</h3><p>I’d choose a great team and a less exciting product over a fascinating subject matter and a bad team any day. I’m not talking about the skills and abilities of the team. They are valuable, but the functioning of the team is so much more important. I’m convinced the vast majority of people working in our industry are smart and have huge potential. The environment and support they receive are vital in unlocking this potential. The first step and a hard one for many is trust.</p><h3>Trust by default</h3><p>The most obvious trait of the inexperienced manager is micro-management. It’s such an easy trap to fall into. I know I have in the past. Ultimately, as a manager, you are responsible for the teams’ output. So it’s only natural to want to make sure that it meets your exacting standards. But there is no getting away from the fact this is a weakness. It’s a fast route to a demoralised, ineffective team.</p><p>Where to start? Start from the assumption that the team is made up of adults that are qualified to do their jobs. Give guidance, ensure everyone is crystal clear on their objectives. Empower them to make decisions. Only step into the details in the rare cases where the outcome is sub-par. If you need to intervene, do it. But there is nothing more demoralising than a manager whose actions show they don’t trust you to do your job.</p><p>Trust breeds empowerment, which breeds motivation and productivity. Control breeds contempt saps enthusiasm and gets weak results. If you’re micro-managed and not trusted to get your job done well, you end up trying to placate your manager, not your end-user.</p><h3>Clear shared vision and goals</h3><p>Clearly defined goals, short and long term, enable efficient, effective decision making. Repeat them often. Once you have a vision that the entire team can recite instinctively, you can work together and be subservient to the greater needs of the company.</p><p>I joined a startup a few years ago, where the team was not in a healthy state. There wasn’t a clearly defined vision for the product, and there were fractures in the organisation. Sales, marketing, design and development teams were thinking in terms of what would make their area better. What would be the most elegant solution for them? What would make them look better?</p><p>With a lot of hard work and communication, we managed to turn things around. Once we knew what we were working towards, we could prioritise what would get us there. Conversations changed to focus on what was best for the company. Who had more capacity to take the load off a swamped teammate? Could we reduce the scope and kill non-core features? Could we get away with building a good-enough-for-now solution?</p><h3>Test everything against this vision</h3><p>Any time a request comes in, from a customer, an executive or a team member test it against your vision. If it does not move you towards your goal, then drop it.</p><h3>No fixed roadmap</h3><p>Fixed, long-term roadmaps are a fallacy. If you think you can accurately plan out what will happen over the next 6, 12 or 24 months, you are mistaken. Product development is a highly volatile environment. You always have new information to act on. If you commit to 12 months of a fixed, time-bound roadmap, you cannot react to change. Your competitors will. They will leave you in their dust.</p><p>In <a href="https://basecamp.com/shapeup">Shape Up</a>, Ryan Singer makes the distinction between imagined and discovered tasks. <strong>Imagined tasks</strong> are what you think you will need to do before you have started building the thing. As anyone who has made a product knows, this is pretty much never what you end up doing. <strong>Discovered tasks</strong> are the real work you have to do. The things you discover once you have started. The <em>we didn’t anticipate this taking so long</em> tasks.</p><h3>But I need to tell people what is coming</h3><p>Of course, you do. I’m not delusional. Prefer <a href="https://www.prodpad.com/blog/how-to-build-a-product-roadmap-everyone-understands/"><strong>themes</strong> over <strong>time-horizons</strong></a>. What does this mean? A theme relates to a customer need, a real, discovered need that you have uncovered. By defining your roadmap by themes, you leave scope to change and shift the definition of the features when you come to discover exactly what is needed. The closer the theme is to being needed to be done, the more in-depth you will define it. There is no point defining anything much further out. In 6 months, your whole landscape will have shifted. Invest the time only where it is essential to move things forward.</p><h3>Appetite is key</h3><p>Another theme highlighted in Shape Up is appetite. Before the team embarks on building a feature, they set the appetite for it. How core is it to the business? If it needs doing but is not a central feature, then it would have a low appetite. Get it done, but forgo the bells and whistle. A large appetite would be something that is the core problem that your product solves. So go the extra mile here. Ask whether it move your core metrics.</p><p>For me, this is the most fun part of product development. Reducing things down to the smallest version they can be and still solve the core problem. Can you hammer the scope down more, can it be cut entirely?</p><h3>Make customers demand features</h3><p>Andrew Chen writes elegantly about the <a href="https://andrewchen.co/the-next-feature-fallacy-the-fallacy-that-the-next-new-feature-will-suddenly-make-people-use-your-product">next feature fallacy</a>. This refers to the mistaken notion that you need to add the next killer feature, then suddenly everyone will start using your product like never before. Either you are close to solving a real problem they have, or you are not. If there is something they need to get their job done, they will let you know. The crucial features will come up again and again until they are impossible to ignore. Just by leaving new feature ideas and requests to one side for a few weeks can make a big difference. More times than not, you will never hear of this idea again. If it’s essential, you won’t be able to avoid it.</p><h3>Embrace randomness and uncertainty</h3><p>Building new products is an unforgiving and ever-changing game. You can get lucky with an average product, process and team. Conversely, you can have everything going for you and still come up short. Don’t just accept this uncertainty, but embrace and optimise for it. Run short, low investment experiments to test customer demand for features. Only when they give you a strong signal jump into building them out in-depth.</p><h3>Don’t waste time on reversible decisions</h3><p>Jeff Bezos wrote about decision making in one of his <a href="https://www.sec.gov/Archives/edgar/data/1018724/000119312516530910/d168744dex991.htm">share-holder letters</a>:</p><p>“Some decisions are consequential and irreversible or nearly irreversible — one-way doors — and these decisions must be made methodically, carefully, slowly, with great deliberation and consultation. If you walk through and don’t like what you see on the other side, you can’t get back to where you were before. We can call these Type 1 decisions.</p><p>But most decisions aren’t like that — they are changeable, reversible — they’re two-way doors. If you’ve made a suboptimal Type 2 decision, you don’t have to live with the consequences for that long. You can reopen the door and go back through. Type 2 decisions can and should be made quickly by high judgment individuals or small groups.”</p><p>If a decision is reversible, you shouldn’t spend much time debating on if it is the correct one. Test it out and if it doesn’t work reverse it.</p><p>You don’t have to agree on everything. Indeed you shouldn’t. Healthy debate and conflicting opinions are signs of a healthy organisation.</p><h3>Be intentional</h3><p>Above everything, the key to all this is to be intentional in your actions. To continually ask the question of does this matter? Does anyone genuinely care about this feature? It’s easy to get swept away by the never-ending tide of things to do. But be intentional too about where to not spend too much time. Nobody wants to look back on their past year and think if only I hadn’t spent all my time on distractions.</p><p><em>Originally published at </em><a href="https://simpleshapes.io/articles/creating-a-high-performing-product-organisation/"><em>https://simpleshapes.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77d86ed4c86" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/creating-a-high-performing-product-organisation-77d86ed4c86">Creating a high performing product organisation</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 best product is no product]]></title>
            <link>https://medium.com/swlh/the-best-product-is-no-product-bf80be54c1f6?source=rss-88e6ee670484------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf80be54c1f6</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product]]></category>
            <dc:creator><![CDATA[David Adams]]></dc:creator>
            <pubDate>Fri, 27 Sep 2019 11:09:19 GMT</pubDate>
            <atom:updated>2019-09-28T09:57:58.371Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_uCUxI_l8ynHuMQZ.jpg" /></figure><p>The best UX is no UX. The best code is no code. Pretty much everything I, and probably you, have worked on would be better if it wasn’t there.</p><h3>What?</h3><p>Ok, so I’m being a touch facetious. That’s not quite what I mean. I’m not saying there is no value in products or the work that we do. Just that they are a means rather than an end.</p><h3>Nobody wants to buy a product. Nobody wants to use software.</h3><p>What they want is to achieve a goal. That might be a social goal — connecting with friends, improving self-esteem. Or a functional goal — getting food to eat, paying an invoice. It could be anything in between. But at its core, it’s about solving a real problem someone has. Getting paid on time, finding love, improving your home; the needs have existed long before technology or products existed even as concepts.</p><h3>Don’t create the wrong thing</h3><blockquote><em>let’s connect a GAS OVEN CONTROLto the internet, what could go wrong? 🆗🆒 </em><a href="https://t.co/HJkybD5VJB"><em>pic.twitter.com/HJkybD5VJB</em></a></blockquote><blockquote><em>- Internet of Shit (@internetofshit) </em><a href="https://twitter.com/internetofshit/status/832640027314225152?ref_src=twsrc%5Etfw"><em>February 17, 2017</em></a></blockquote><p>Nobody needs an internet-connected gas hob.</p><p>There is a big difference between the things people will buy and the things that they need. There is also a big difference in the mindset of companies that are creating products in either of those categories.</p><p>Nobody needs a fridge that can browse the internet, a lightbulb that can change colour via an app, or a coffee machine that makes you coffee through the internet. These are all things that someone in an office somewhere decided that people love, so they should add. It’s evident in the proliferation of touch screens on an increasingly random selection of devices. Even when in some cases, especially cars, it reduces usability to the point of being dangerous.</p><h3>How to create the right thing — the ideal state</h3><p>“By looking at [problems] in a solution-neutral way, teams can consider the ideal state-a hypothetical, imaginary and perfect experience that is free of constraints, compromises and contradictions.” — Clayton Christensen (Harvard Business Review)</p><p>The point of all this is that whatever you are making, it serves only as a solution to a specific problem set and <strong>no more</strong>. Customers don’t care about your product, they just want you to get things done for them and get out of their way.</p><p>Using this as a lense, we can create far superior products, saving time and money. Focus on framing the problem a long time before you even start considering solutions.</p><h3>Ideal state, backwards</h3><p>Without any constraints on time, budget, people or technology what is the ideal state for a customer? Assuming you can’t achieve that, work backwards until you can. In most cases, you will have to work backwards a few steps until a product or technology even come into it. If then, and only then, you need to build something, get stuck in.</p><h3>How can we do this with no code, no interface?</h3><p>Always be asking how you can reduce your product to it’s simplest possible form.</p><h3>The best interface is no interface</h3><p>If your product is an app, the ideal interaction is for the user’s problem to be solved instantly, without any interaction. Nobody wants to record the calories they consume in a day. They want to be healthier, fitter or thinner. Interacting with an interface, in this case, is necessary now. But if you could do it from a photo, that’s better. If you could do it just from sensing what you have eaten with no interaction, that’s your ideal state. 99% of the time this isn’t possible, but if you frame the problem this way you will focus on building less.</p><h3>The best code is no code</h3><p>Software takes time to build, takes time to change and takes time to improve. It introduces risks of bugs, security breaches and maintenance costs. Every new feature introduces a maintenance cost, risks and customer support needs. Every decision to build something should not be taken lightly. You are inadvertently taking on a cost burden that you may not fully appreciate. The less you have to maintain the more you can focus on your real reason for existing. It’s certainly not for software.</p><h3>Focus on outcomes</h3><blockquote><em>“We need to hire 10 developers in the next four months”</em></blockquote><blockquote><em>“That’s $2–3 million dollars a year…”</em></blockquote><blockquote><em>“Yup. Things are crazy!”</em></blockquote><blockquote><em>“Could you walk me through your last ten product decisions…how did they contribute to mid/long term sustainable growth?”</em></blockquote><blockquote><em>“We have no idea, but…”</em></blockquote><blockquote><em>- John Cutler (@johncutlefish) </em><a href="https://twitter.com/johncutlefish/status/1175483723946455040?ref_src=twsrc%5Etfw"><em>September 21, 2019</em></a></blockquote><p>It’s unbelievable how so many people are happy to throw vast sums of money at rushing towards a hastily constructed roadmap. All without really knowing whether this will produce the needed outcome. Tell these people you need to spend more time planning or researching, you will likely be met with a blank stare. This is the reality of countless companies of all sizes.</p><h3>Stay nimble</h3><p>The good news is you have an advantage, staying laser focussed allows you to stay nimble, keep the team smaller for longer and build something your customers love. Taking this approach is not the easiest path in the short term, you will have to resist strong forces to just get ahead and start building.</p><p>You have scarce resources, scarce time and scarce money. Focus on building only what is necessary. The rest is the road to nowhere.</p><p><em>Originally published at </em><a href="https://simpleshapes.io/articles/the-best-product-is-no-product/"><em>https://simpleshapes.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf80be54c1f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/the-best-product-is-no-product-bf80be54c1f6">The best product is no product</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>
    </channel>
</rss>