<?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[The Good Founder - Medium]]></title>
        <description><![CDATA[Entrepreneurship, leadership, and technology. - Medium]]></description>
        <link>https://medium.com/the-good-founder?source=rss----7138e7a50c1d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>The Good Founder - Medium</title>
            <link>https://medium.com/the-good-founder?source=rss----7138e7a50c1d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 06:46:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/the-good-founder" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[On Momentum In Startups]]></title>
            <link>https://medium.com/the-good-founder/momentum-7e031d0453a4?source=rss----7138e7a50c1d---4</link>
            <guid isPermaLink="false">https://medium.com/p/7e031d0453a4</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[momentum]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Omar Malik]]></dc:creator>
            <pubDate>Tue, 19 Dec 2017 07:00:17 GMT</pubDate>
            <atom:updated>2017-12-19T06:59:46.607Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nd/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>An essay on the origins, common applications of, and anti-patterns surrounding how ‘momentum’ as a cultural prerogative is deployed within early-stage startups. I give an opinion as to when I believe a strong lean towards momentum should happen, and across which part of a startup’s activities founders should encourage aspirations of perfection instead. Here be opinions formed by over a decade of battle-scars, and yet still only part of the picture.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcohe.se%2Ftgfmomentum%2Fembed&amp;url=https%3A%2F%2Fcohe.se%2Ftgfmomentum&amp;image=https%3A%2F%2Fcdn.filestackcontent.com%2FgXYrvqSIS4ikbSPi6dEH&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=cohe" width="530" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/34a6a2f93113b9c5e9875bb356c72aa5/href">https://medium.com/media/34a6a2f93113b9c5e9875bb356c72aa5/href</a></iframe><h3>A Premise</h3><p>In the world of startups, momentum is often considered a virtue, and actually quite often the virtue that rules all others <em>and in the darkness binds them</em>. And for arguably good reason as well; after all, if a small, plucky startup is unable to manufacture agility and continuing forward movement from its size, passion, and focus — then how can it ever hope to ‘win’ versus more established and better funded opponents? If it displays the same inertia of these existing (larger) companies, where exactly is the advantage, and without it, where is the hope of opportunity?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*54Rgec3Ij7SIVRE5uYIa0A.jpeg" /><figcaption>A startup‘s typical relationship with momentum</figcaption></figure><blockquote>In other words, if a startup is not optimising for momentum above all else, does it really embody the qualities that define what it is to be… a startup?</blockquote><h4><strong>If momentum is almost the defining quality of a startup then, is that to say it must be prioritised all the time, in all the places?</strong></h4><p>In many ways, the answer to this question is impossible to be separated from the idea of a startup’s desired ‘culture’, however I’ll skip straight to the answer as I believe it, which does invoke a bias towards a certain type of company culture we at <a href="http://mercp.com/">Mercurial Phoenix</a> favour and look to imbue in all our engagements, both when building <a href="https://cohese.co/">internal</a> <a href="https://bothsides.news/">companies or products</a> and working with <a href="https://www.siemens.com/global/en/home.html">external</a> ones:</p><p><strong>No. :-)</strong></p><p>As with all things, optimise for momentum in moderation and with discretion.</p><p><em>The long read begins now…</em></p><h3>Momentum: The Origin Story</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*I9sfsrdAqDg4VXXpipcQ-Q.gif" /><figcaption>The Zuck</figcaption></figure><p>Popular startup culture has been for at least a decade now taken in by the trope of ‘moving fast and breaking things’. Mark Zuckerberg popularised the approach from the earliest days of Facebook, with his laissez-faire attitude towards all the things, from <a href="http://gawker.com/5636765/facebook-ceo-admits-to-calling-users-dumb-fucks">his perception of users’ human worth</a> to the <a href="https://consumerist.com/2009/02/15/facebooks-new-terms-of-service-we-can-do-anything-we-want-with-your-content-forever/">belief of ownership over them</a> to an <a href="https://www.wired.com/2010/04/report-facebook-ceo-mark-zuckerberg-doesnt-believe-in-privacy/">absence of belief in their right to data privacy</a> and all that lay in between.</p><p>The number of system-affecting bugs that were pushed in the early days of Facebook was effectively used as a point of pride and evidence of this forward-thinking and modern approach to momentum optimisation, though I personally suspect the adage was born more of public relations post-rationalisation of mistakes, rather than an intended belief that it was objectively for the best. <em>#skeptic</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*1Wr_qMieyYWEYedXXilyKg.jpeg" /><figcaption>Bugs FTW!</figcaption></figure><p>How did we end up taking it as true that it is a good thing to break things, and not change our opinion(s) towards this attitude, <a href="https://www.cnet.com/uk/news/zuckerberg-move-fast-and-break-things-isnt-how-we-operate-anymore/">even though even Facebook has since dropped it from their mantra</a>? Was it simply blind following based on the outsized success Facebook represented? Recreate their steps, and history will repeat?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3owyp7DzNOfPY2Fsgo%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3owyp7DzNOfPY2Fsgo%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3owyp7DzNOfPY2Fsgo%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/82f8e80ddbceec0f622659b124bf9f85/href">https://medium.com/media/82f8e80ddbceec0f622659b124bf9f85/href</a></iframe><p>The answer may be linked to technology macro-trends. The concept of ‘breaking things’ has certainly been aided by the reduction in the impact of said ‘breakages’ as time has wore on; measurement and reporting became increasingly standard allowing us to more readily inspect where things aren’t working in the first place, software patches can be subsequently pushed to production environments with near real-time speed courtesy of the increasing wisdom and adoption around <a href="https://en.wikipedia.org/wiki/Continuous_delivery">continuous delivery</a>/deployment, and technology at large has provided the ability to remotely update released software that in a previous life would have been recalled or replaced (hello floppies/CDs).</p><p>Makes sense.</p><p>But does saying that ‘Facebook have dropped <em>momentum</em> <em>above all else</em> from their modus operandi and so also should all other startups’ make sense? Whilst they are obviously a company, <a href="https://www.marketwatch.com/story/facebook-heads-toward-500-billion-market-cap-after-earnings-2017-07-26">they’re definitely not a startup any longer</a>, and so it may be fairer to say that this is a natural evolution for their state of organisational maturation, and all but a necessity of circumstance. With literal billions of users across the company’s properties being now affected by any mistakes that are pushed to production, and lives potentially reduced in droves <a href="http://beta.latimes.com/science/sciencenow/la-sci-sn-facebook-friends-mortality-20161031-story.html">if friend requests are disrupted</a>, slowing progress to minimise risk takes on a far greater sense of purpose.</p><h3>Momentum Vs. Reputation</h3><p>This is the obvious resistance against moving <em>too</em> fast, and often deployed by corporates to justify their inclination to not move fast at all (somewhat disingenuously for the simple bureaucratic realities that prevent them from doing <em>anything</em> fast): if not a fear of reducing life expectancy, it is certainly the fear of reducing their own corporate life expectancy by incurring damage to their public reputation, which therefore must be protected at all costs. (To preserve shareholder value, obviously. <em>#cynic</em>)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FWYERI28ZoE956%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FWYERI28ZoE956%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FWYERI28ZoE956%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/0a82495fad73fe2db6ce34825c1fb9d5/href">https://medium.com/media/0a82495fad73fe2db6ce34825c1fb9d5/href</a></iframe><p>In a world where access to information can be real-time and ubiquitous, and the <a href="https://www.nytimes.com/2015/02/15/magazine/how-one-stupid-tweet-ruined-justine-saccos-life.html">eye of the the internet can be capricious</a>, reputation damage is worth being sensitive towards. So goes the same wisdom in the real world, applied to individuals; your reputation truly does precede you, even if no one actually knows you, as it is now within constant reach even by strangers courtesy of your multiple online presences, continuously scraped, cloned and archived despite your privacy settings. (Sad but true. <em>#cynic</em>)</p><p>So why has this been displaced as a consideration startups naturally pay attention towards, unlike the rest of the world, and despite it feeling like an eminently rational fear which has been an historical cause for concern, frankly not just since the internet but ever since bad news was able to spread quicker than humans were able to outrun it.</p><p>Once again, there is an arguably good reason for this as well. If we take it as accepted that an established company has a reputation to protect, and likely a positive one (at least in parts, to have allowed for the company to succeed in reaching ‘later-stage’), and a human being has by definition a history she would like to leverage for positive experiences in the future (as her experience would have at least in part been acquired through hard-fought blood, sweat and tears), uniquely an early-stage startup has neither a known reputation or even unknown history, and therefore can avoid being preoccupied with its reputation entirely.</p><p><strong>Whilst an early-stage startup obviously <em>does</em> exist metaphysically, for almost every one outside of #tech’s manifestation of privilege, it really is only a theoretical existence.</strong></p><h3>Founders As Momentum Drivers</h3><p>To explain briefly, I suggest an early-stage startup <a href="https://www.theguardian.com/notesandqueries/query/0,,-82446,00.html">only has a theoretical existence</a> primarily because no one knows about it, yet. Even when users do begin to learn about it in a closed sphere (like an infant has a small circle of real world contacts — family, play circle friends, babysitter maybe— but no wider ability to extend its own reach), the ease with which any accumulated history can be practically ‘revised’ (wiped) is a shield that can psychologically protect.</p><p>If a startup makes some bad decisions that become known and affect its beta users, a renaming/registration of a new domain would be frictionless to accomplish (starting again from 0 when you’re only at 0.000001 isn’t hugely burdensome), and almost certainly remove any connections between past negative behaviour and its new manifestation, at least to a cursory Googling depth of research by future users. (This is overly simplistic, but I’m hoping the point is conveyed.)</p><p>As I hope the same is with you, I’m not a fan of ever actively thinking along these lines, and no entrepreneur worth their salt would do, consciously. <em>Our subconscious is another matter entirely though</em>; based on observation, both in hindsight when introspecting, and of others I’ve had direct contact with across my career, I do genuinely believe we allow ourselves, particularly as founders whose job it is to constantly juggle priorities with seriously finite resources, most of which will render rewards sooner if jobs get done faster — logic!—to use the absence of true accountability when relatively few outsiders know about us as a crutch to <strong><em>justify unideal behaviour in the name of momentum</em></strong><em>.</em></p><h4>Momentum By Arrogance</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FyCs6kwQsyP3wI%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FyCs6kwQsyP3wI%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FyCs6kwQsyP3wI%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="363" frameborder="0" scrolling="no"><a href="https://medium.com/media/bedb9ea446036aca392308a162c88385/href">https://medium.com/media/bedb9ea446036aca392308a162c88385/href</a></iframe><p>Even where more than a “relatively few outsiders” know about a startup, I’ve personally seen this crutch be deployed, though from a different psychological place; for these founders (usually more established or connected, hence more outsiders keeping track in the early days), a <a href="https://en.wikipedia.org/wiki/Survivorship_bias">cultivated arrogance</a> allows a cognitive dissonance to seep into their behaviour, separating themselves and their company culture from any grounding belief they will be held accountable for reckless actions, even if ultimately negative in consequence. Even if the founders themselves don’t encourage this attitude within the startup, it often will still spread because they tend to not have preemptively spoken against it. I’ve seen employees often gain confidence and vicariously live through their Connected CEO, seeking to represent her as they believe she would approve, or as far their lens shows them that she does; this often false mirror is exacerbated when the distance between leadership and ground-level staff is organisationally significant, and there is a lack of a transparency culture, further extending the disconnect.</p><p>On account of the world as it is structured, the learned belief of Privilege being exempt from accountability is rooted in historical and everyday examples, though as a trend line goes, <a href="https://www.washingtonpost.com/news/innovations/wp/2016/05/23/theranos-teaches-silicon-valley-a-hard-lesson-about-accountability/?utm_term=.8051f6fb654b">this way of thinking is both antiquated</a> and <a href="https://www.nytimes.com/2017/06/13/technology/uber-travis-kalanick-holder-report.html">its days are numbered</a>. <em>#optimist</em></p><h4>Momentum By Oversight</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FuFtywzELtkFzi%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FuFtywzELtkFzi%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FuFtywzELtkFzi%2F200.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="245" frameborder="0" scrolling="no"><a href="https://medium.com/media/0a94f47c9eb081c73f506d88db72f88e/href">https://medium.com/media/0a94f47c9eb081c73f506d88db72f88e/href</a></iframe><p>Moving away from <a href="https://www.fastcompany.com/3016238/why-your-startups-culture-is-secretly-awful">privilege in #tech</a> though — an intended subject for a future essay — for the average startup that doesn’t have any sort of reputation yet, and only small trickles of outside observers, the feeling supporting momentum tends to be that <strong>there is little risk, and only gains to be made</strong>. In my opinion, the oversight here is that the founders (and indirectly the employees) behind the company <em>do</em> have reputation capital to lose— having history as persons, they must — and these <strong>are</strong> at risk; no wonder then that the startup that cultivates a culture of wantonly ‘breaking things’ in my experience tends to be a) pre-launch (see below), b) run by the inexperienced founder who doesn’t have the wherewithal to account for risk and possible repercussions thereof, or as noted already c) run by the founder who is arrogant enough to believe her profile and connections mollify the risk such that it needn’t be registered (and isn’t).</p><h3>Just Tell Me When Momentum Is Right</h3><p>Ultimately, to continue further and to facilitate something remotely conclusive, I must put my cards on the table and get to when and where optimising for momentum can be acceptable or not:</p><p>When working on an early-stage startup with minimal users, <strong><em>I actually do believe in moving fast and breaking things</em></strong>. Just not <strong><em>all</em></strong> the things, and when it comes to certain things, I actually firmly believe a healthy <em>aspiration</em> to <em>never</em> break anything (i.e. be perfect) is mandatory, whether you have zero users and one employee, or millions and thousands — and despite it being realistic to achieve perfection, or not. (It’s not, of course, but the intention really does count, to your employees, users and ultimately as a message to the world that you are a good citizen — good for marketing too!)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F4JMQMfVDdTFqo%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F4JMQMfVDdTFqo%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F4JMQMfVDdTFqo%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="326" frameborder="0" scrolling="no"><a href="https://medium.com/media/2c379174bf6657bdd8401a831243998e/href">https://medium.com/media/2c379174bf6657bdd8401a831243998e/href</a></iframe><p>To iterate, what I’m espousing is a lean-in towards momentum, combined with a culture that can accommodate selectively leaning away, even sharply and abruptly as required. But what are those areas that <strong>cannot</strong> be selectively excluded, and should <em>always</em> be handled with kid gloves?</p><h4><strong>Answer: Those considerations that pertain to human beings, and everything that encapsulates being ‘human’.</strong></h4><p>These could be employees (yes, that means adopting in some form the <a href="https://www.fastcompany.com/3059673/the-future-of-hr-and-why-startups-shouldnt-reject-it">uncool idea of ‘HR’</a>), or meaningful/impactful touch points with your users and customers, particularly those experiences that have the ability to stay with these people beyond the time that you or your startup will be interacting with them; i.e. anything with enduring human impact. (And not just because of <a href="https://en.wikipedia.org/wiki/Net_Promoter">NPS</a>! <em>#cynic</em>)</p><blockquote>Frankly, I think it signposts a terrible attitude and culture for a startup/founder to adopt an adage that has in all its usages only been intended to apply to functionality and features — and extending its underlying statement to matters of personality, psychology, and <strong>people</strong>.</blockquote><h4>Here’s A Trivial Example</h4><p>We at <a href="https://twitter.com/mercurialp">Mercurial Phoenix</a> have recently launched a studio startup called Cohese. Go <a href="https://cohese.co/">check it out</a> and please <a href="/service/mailto:omar@cohese.co">let me know what you think</a> separately. (You may have noted it’s being used to make sharing all the links in this article better/more connected; <a href="http://deviq.com/dogfooding/">dogfooding ftw</a>!)</p><iframe src="https://cdn.embedly.com/widgets/media.html?type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=instagram&amp;url=https%3A//www.instagram.com/p/BaVDrQ0lPMG/&amp;image=https%3A//i.embed.ly/1/image%3Furl%3Dhttps%253A%252F%252Fscontent-iad3-1.cdninstagram.com%252Ft51.2885-15%252Fs640x640%252Fsh0.08%252Fe35%252F22580313_495600027484772_4407999591006339072_n.jpg%26key%3Da19fcc184b9711e1b4764040d3dc5c07" width="640" height="640" frameborder="0" scrolling="no"><a href="https://medium.com/media/292504ea698619a487475352ffd0076c/href">https://medium.com/media/292504ea698619a487475352ffd0076c/href</a></iframe><p><em>S</em>ince it’s been in public beta, we’ve had to re-provision the infrastructure causing downtime in the first few days, pushed hot-fixes to production a few times (implying there were showstopper bugs on the live site, OMG!), and generally been continuously delivering features/improvements regardless of whether users are on the site, and with <a href="https://headwayapp.co/cohese-updates">announcements only after the fact</a>. To be fair, our architecture and delivery pipeline allow for disruption to the end-user to be minimised (perhaps a future post around engineering ‘momentum-by-design’?), however regardless, I can understand if some may prefer scheduled releases, fairer warning to users, and other practises (perhaps conventionally ‘better’) that could momentarily slow down Cohese’s progress; our attitude has been we have a low enough number of users in our beta such that the pros of optimising for momentum in this respect far outweigh the cons, for now.</p><p>That’s functionality, I’ve already stated my belief that it’s okay to prioritise for momentum and not perfection when it comes to this, and even if end-users are impacted, hopefully they’ll forgive us and not spend their next days/months/years being outraged at an outage, so the impact will not endure. For such an early-stage product it’s a fairly obvious position to take, but <strong>how about where we should aspire for perfection?</strong></p><p>As the leader of Cohese, and perhaps aided by our three-strong team being distributed (i.e. not able to tap me on the shoulder or show me the <a href="https://gph.is/2cguMTh">stink-eye</a>!), it would be easy and convenient to only address incoming requests/queries from the team when it suits my <a href="http://www.paulgraham.com/makersschedule.html">maker’s schedule rather than submit to my manager’s schedule</a> (I also build the product, so wear both hats), and in so doing maximising personal momentum by not switching away from <em>my</em> work context, to favour <em>theirs</em>. In fact though, I actually do the opposite, wilfully sacrificing my own speed in favour of <a href="https://www.joelonsoftware.com/2001/02/12/human-task-switches-considered-harmful/">context switching</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3oEjHMBUxwVJ9iu5JS%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3oEjHMBUxwVJ9iu5JS%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3oEjHMBUxwVJ9iu5JS%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/d3024f5b11a7370846fd4d7ee7f3ce0d/href">https://medium.com/media/d3024f5b11a7370846fd4d7ee7f3ce0d/href</a></iframe><p><strong>Why should you attend every incoming request as a priority </strong>(n.b. not message, but <em>request</em>)<strong>?</strong> Because regardless of the subject matter being queried, whether of true objective consequence or not, invariably when a human asks something of another, some level of emotion and/or psychology is underpinning the communication. It’s <a href="https://www.psychologytoday.com/blog/passion/201601/the-power-asking-help">a tacit admission of vulnerability</a>, and this should be at least respected and acknowledged, even if it cannot be adequately addressed immediately. In fact, one of the most important things when I respond to a question ASAP is not my answer, but rather in providing an answer, I remove any possibility that the void which otherwise would endure is prematurely filled with something at best incorrect and harmless, or more often, incorrect <em>and damaging</em>.</p><p><strong>Really though, the most important reason is because being acknowledged and responded to feels good to the asker, and is a sign of respect by the responder. </strong>Why wouldn’t I then, as a leader, want to give someone that good feeling if I can, and demonstrate that I respect my team in the way I hope they do me?<strong> </strong>(And if being purely economical about the exchange, even reap the subsequent rewards of a <a href="https://warwick.ac.uk/newsandevents/pressreleases/new_study_shows/">happier team in terms of longer-term productivity</a>?)</p><p>For me, it also falls squarely in the category of ‘not being a wanker’. :-)</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxUPGcy5Cr3QrPKWKZi%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FxUPGcy5Cr3QrPKWKZi%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FxUPGcy5Cr3QrPKWKZi%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="214" frameborder="0" scrolling="no"><a href="https://medium.com/media/05f801f2c8ae35a21889d6f40796138b/href">https://medium.com/media/05f801f2c8ae35a21889d6f40796138b/href</a></iframe><h3>The Long Way Home Is Sometimes The Best</h3><p><strong>As human beings, <em>being human</em> sounds like self-evident non-advice.</strong> That’s great if it does to you, truly! In my experience across dozens of companies as employee, consultant, contractor, and even (in a past life, and when not as I am now) as a founder, unfortunately it hasn’t proven to be as self-evident as perhaps it ought.</p><p>In a previous startup of mine, I recall some feedback I received from an advisor regarding a piece of proposed functionality we had on our roadmap which we thought was great, and would <em>certainly</em> maximise the efficiency of completing a common task as performed by our users (consumers), so surely would be a winner. From the users we had spoken to, there was some consensus around this, however his skeptical advice towards the proposal was:</p><blockquote><em>Sometimes people like to take the long way home.</em></blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fm8Mc-38C88g%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dm8Mc-38C88g&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fm8Mc-38C88g%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd274f628413b21e869c0850999f76f1/href">https://medium.com/media/dd274f628413b21e869c0850999f76f1/href</a></iframe><p>It immediately reminded me of the film, <a href="http://www.imdb.com/title/tt1615147/">Margin Call</a>, where I had heard the analogy made <a href="https://movies.stackexchange.com/questions/30881/what-does-will-want-to-say-with-his-response-to-erics-bridge-analogy">more expressively</a>. What it made me think upon was that sometimes the longer journey is not only an arbitrarily preferred path (as it may be), or the more meaningful one (e.g. better views, facilitating ‘thinking time’ or decompression from the work day, an opportunity to catchup on a favourite podcast, etc.), but for non-obvious reasons that may be individual to each person or startup (bringing it back to the present topic), actually the faster route in the medium to long-term.</p><blockquote>In other words, sometimes optimising for momentum in the short-term is counter-intuitive to equipping your company to best make progress in the future.</blockquote><h3>Momentum Anti-Patterns</h3><p>Here are a few, short, non-exhaustive examples I’ve personally witnessed which allude to either this lean towards a detrimentally short-term momentum mindset, or a misapplication of ‘momentum above all things’ in areas of a startup’s activities that I believe are more appropriately suited to aspirations of perfection.</p><p>These are intended to jog your own thinking, as they demonstrate common anti-patterns I’ve seen repeat and that you can look out for in your journey — either when administering your own startup (i.e. identify whether you commit these as a founder and introspect accordingly), or as an employee when assessing your managers/leaders and where you should expect improvement, so you can encourage them to do so. (Best tactics to persuade founders to positively change as an employee is a challenge in itself!)</p><p><strong>As a founder, I’ll push the company along further and faster by going where <em>I</em> think I’m needed (and it’s my company so I know best), rather than making it a priority for me to participate in group ceremonies that are mandatory for <em>the rest.</em></strong></p><p><em>e.g. A founder not believing it’s important to be involved in company-wide retrospectives, or common activities shared by the rest of the team</em></p><p>This alludes to a lack of understanding towards the human aspects of process, and an incorrect lean towards superficial momentum via belief that introspection is the enemy of progress, <a href="https://hbr.org/2017/03/why-you-should-make-time-for-self-reflection-even-if-you-hate-doing-it">which is complete nonsense</a>. It also increases/maintains distance between the founder and the ground-level, thus also creating distance between problems and strategic solutions that ultimately will allow the company to progress further and faster. Fundamentally, it is <a href="http://www.businessnewsdaily.com/4991-effective-leadership-skills.html">a sign of weak leadership</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F23BST5FQOc8k8%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F23BST5FQOc8k8%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F23BST5FQOc8k8%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="269" frameborder="0" scrolling="no"><a href="https://medium.com/media/2709efa4338d1175121ffab5cb556d05/href">https://medium.com/media/2709efa4338d1175121ffab5cb556d05/href</a></iframe><p><strong>As a leader, <em>I</em> do not, nor do I want my team to discuss obviously negative trends happening to my company openly within the company because these will just slow things down, and doing so distracts away from simply doing good work that will stop negative things from affecting us anyway.</strong></p><p><em>e.g. A founder glossing over and/or post-rationalising the exodus of employees in a short space of time</em></p><p>This alludes to a belief that talking about and investigating ‘bad’ things is akin to being distracted by the wrong things, which encourages wilful ignorance and not addressing root causes that are likely to ultimately retard company progress (long term momentum) because of <a href="https://en.wikipedia.org/wiki/Path_dependence">path dependence</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3o7bufVLrPj67YFHQA%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3o7bufVLrPj67YFHQA%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3o7bufVLrPj67YFHQA%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/bdc56f293cacb6a592347c24b7b87d99/href">https://medium.com/media/bdc56f293cacb6a592347c24b7b87d99/href</a></iframe><p><strong>As a manager, my main responsibility is to ensure there is no friction with the team, because disagreement is the enemy of momentum.</strong></p><p><em>e.g. A founder who doesn’t react strongly to stop good talent who challenge the status quo from leaving their company, because in their absence, it makes it easier to forge ahead with their vision without dissent</em></p><p><em>e.g. A company pursuing a strategy of hiring predominantly junior talent, who end up not displaying the confidence (on account of lack of experience) to do anything but tow the company line in the face of more experienced management</em></p><p>This is a false analogy for momentum as it <a href="https://chiefexecutive.net/speeding-change-slowing/">confuses the easy path for the faster path</a>, again steers away from human aspects of process, and doesn’t bode well for the necessary resilience needed to survive the famed startup <a href="https://www.forbes.com/sites/kylewong/2015/08/09/making-it-through-the-startup-trough-of-sorrow/">trough of sorrow</a>. Oh, and startups <a href="http://mashable.com/2016/04/10/dan-lyons-disrupted/#6AGWwVMEciqD">shouldn’t be cults</a>, and <a href="https://www.inc.com/kevin-daum/7-ways-amazing-leaders-encourage-healthy-debate.html">healthy debate</a> should be encouraged.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FR195TgCcRZNZe%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FR195TgCcRZNZe%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FR195TgCcRZNZe%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="245" frameborder="0" scrolling="no"><a href="https://medium.com/media/d2b2afcd97851df8311f9271523646e8/href">https://medium.com/media/d2b2afcd97851df8311f9271523646e8/href</a></iframe><p><strong>As a leader, I believe it’s better to go quickly in <em>any</em> direction rather than spending time figuring out which direction gives us the greatest probability of success before following it; eventually we’ll find out anyway, and in the meantime we’ve maintained ‘momentum’.</strong></p><p><em>e.g. A founder who has a visceral reaction to making data-driven decisions, and/or often overrides those made by subordinates in favour of ‘gut’ or historical knowledge that conflicts with present-day surfaced data</em></p><p>This optimises for an appearance of momentum and/or <em>initial</em> momentum rather than the kind that endures. This is not to say there isn’t a <em>huge</em> place for <a href="https://www.wired.com/2015/03/the-joyless-world-of-data-driven-startups/">vision in startup decisions</a> (I firmly believe there is, and actually my entrepreneurial habits tend to lean in that direction), but really this is more about what would be analogised in engineering parlance as ‘<a href="https://en.wikipedia.org/wiki/Software_architecture">architecture</a>’. Having a plan or model backed by data doesn’t preclude it from being iterated upon for improvement in the future (certainly it should as data changes), however it typically does preclude a thing being <em>entirely wrong</em> to the point where you need to walk back to zero and start again. Picking an unconsidered direction, as I’ve seen it happen, often does lead to this walking back to the beginning — destroying the hope of progress, and <a href="https://www.inc.com/larry-kim/why-startup-pivots-almost-never-work.html">possibly more</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F6Q2KA5ly49368%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F6Q2KA5ly49368%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F6Q2KA5ly49368%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="307" frameborder="0" scrolling="no"><a href="https://medium.com/media/67da2483f26adfdea5fa56a683b69aea/href">https://medium.com/media/67da2483f26adfdea5fa56a683b69aea/href</a></iframe><h3>A Conclusion</h3><p>First of all, if you’ve made it down to here (having actually read all the above, even if skimmed), I applaud you. And I apologise for the length — things got away from me a bit there… ;-)</p><p>Sincerely, thank you for taking the time.</p><p>I’ve attempted to interrogate the culture of momentum within early-stage startups, including a cursory dive into the origins as I see it (this hasn’t been an academic exercise, and so I’m certain there could have been a more thorough dissertation), and a focus on where in my career I’ve observed the deployment of <em>momentum optimisation as crutch for otherwise imperfect behaviour</em>, or where activities designed to catalyse momentum actually have an opposite effect.</p><p>Hopefully the few examples I’ve been able to provide (there are many more that could fill a book, I’m sure!) allow you to move forward and look for these in your journey, as mentioned — either when administering your own startup as a founder, or as an employee when assessing your leaders to know where you can encourage improvement.</p><p>To recap, my fundamental position has been:</p><ul><li>the prevailing culture of optimising towards <strong>momentum within startups should be limited to our consideration of functionality and features</strong>, AND</li><li>momentum should be abandoned when the ‘things’ that may be ‘broken’ (in context of “moving fast and breaking things”) actually take the shape of human persons, with a view to specifically <strong>tune our sensitivity towards psychological protection</strong>, BECAUSE</li><li>fundamentally <strong>doing so actually ensures a greater chance of maintaining medium-long term momentum (and often even in the short-term)</strong>, versus a superficial appearance of momentum, which usually only lasts for a brief period.</li></ul><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F26BGM86XngBjKOqXu%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F26BGM86XngBjKOqXu%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F26BGM86XngBjKOqXu%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/7dc4eae6386b0fcb762d08191f5643cf/href">https://medium.com/media/7dc4eae6386b0fcb762d08191f5643cf/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fcohe.se%2Fbyr0nic&amp;src=https%3A%2F%2Fcohe.se%2Fbyr0nic%2Fembed&amp;type=text%2Fhtml&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;schema=cohe" width="530" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/d6e060644d1399c9a972f4eb736b3d60/href">https://medium.com/media/d6e060644d1399c9a972f4eb736b3d60/href</a></iframe><p>I’m Omar 👋, the Founding Editor of <a href="https://thegoodfounder.com/">The Good Founder</a> and author of these words. You can get to know more about me via these links. Thanks for visiting, and reading the first article of our publication.</p><p>Please give it a few 👏 if you’re so inclined, and similarly please do comment whether in agreement/disagreement, share, and feel free to <a href="/service/mailto:omar@thegoodfounder.com">get in touch</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e031d0453a4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-good-founder/momentum-7e031d0453a4">On Momentum In Startups</a> was originally published in <a href="https://medium.com/the-good-founder">The Good Founder</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>