<?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 Jose L Ugia on Medium]]></title>
        <description><![CDATA[Stories by Jose L Ugia on Medium]]></description>
        <link>https://medium.com/@joseluisugia?source=rss-ebd6793b60e8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2R81CQLQLN4zJfG_I3nkVw.jpeg</url>
            <title>Stories by Jose L Ugia on Medium</title>
            <link>https://medium.com/@joseluisugia?source=rss-ebd6793b60e8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 18:36:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@joseluisugia/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[The Mean Startup 2 –The Paradox of Speed]]></title>
            <link>https://medium.com/@joseluisugia/the-mean-startup-2-the-paradox-of-speed-e35c000c2cbc?source=rss-ebd6793b60e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e35c000c2cbc</guid>
            <category><![CDATA[speed]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[corporate-culture]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Jose L Ugia]]></dc:creator>
            <pubDate>Thu, 10 Nov 2016 22:44:35 GMT</pubDate>
            <atom:updated>2017-10-03T22:06:49.773Z</atom:updated>
            <content:encoded><![CDATA[<p>Startups, <a href="https://en.wikipedia.org/wiki/Startup_company">by definition</a>, flourish in an ecosystem where there is no room for stillness. To the contrary, fast motion and transformation are reflected in undoubtedly relevant aspects such as time to market, prototyping, iterative development, emerging technologies, burn rate, growth, pivoting, and so on. Note the essence of time and quickness on each of them.</p><h4>The Broken Speedometer</h4><p>For eons, we have been assessing velocity of development in a very superficial way: <strong>linearly</strong> and <strong>visually</strong>. For example, if your job is to walk from point A to B, and these two points are 10 <a href="https://en.wikipedia.org/wiki/Bamboo_(unit)">bamboos</a> apart from each other, by the time you walk 5 bamboos you will be half way to finishing your job. This approach works great for activities that can be clearly described using a short list of tangible steps, like for example, gathering fruits, planting seeds, washing dishes, cooking, hunting, etc.</p><p>In startups (<a href="https://www.kickstarter.com/projects/682782635/flip-band-the-simplest-way-to-stick-to-your-goals">even the simplest ones</a>), challenges tend to sit far away from such simplicity. Not only there is a bunch of independently moving parts that need to be put together to create some meaning, but also many of these parts require complex abilities such as <strong>creativity</strong>, <strong>resilience</strong> or <strong>curiosity</strong>. Take as an example the task of designing a consistent experience for two mobile clients and a web front-end. Concluding that the work is 33% done when there is a finished design for one of the mobile clients would be like determining that Beethoven was 55.5% done with symphonies after he wrote the <a href="https://www.youtube.com/watch?v=_4IRMYuE1hI">fifth</a>.</p><p>This same <strong>superficiality</strong> is seen in engineering, when progress is assessed by looking at the number of lines of code changed or commits authored in version control systems, hours sitting in a desk at an office or the ability to give up weekends in order to attenuate the effect of a pathologic inability in management to plan adequately or stick to a certain direction.</p><p>Companies looking at these indicators to assess progress are a gold mine for precisely the kind of engineers that you do <strong>not</strong> want to share your pull requests with. Since all that is needed in order to be successful in one of these companies is to write simple and bulky code, be the one who spends the longest amount of time in the office working on your own thing, or come in every other weekend to watch your favourite team play on a bigger screen.</p><p>As a result, objective indicators like fluency of communication, achievements based on informed estimations or productivity are completely disregarded. Does this sound familiar?</p><h4>My Teacher Hates Me</h4><p>Chances are your teacher did not hate you back then, nor your manager does today. Most likely, he or she likes you and wants the best for you; or at least, wants the best for the project you are working on.</p><p>Unproductive and sterile approaches such as the aforementioned are more likely to be a result of a religious belief in primitive models, lack of experience or empathy, or as discussed in <a href="https://medium.com/@joseluisugia/the-mean-startup-1-fear-tradition-6fa4dc0a09c7#.kbz36kp9w">the previous part of this series</a>, a cocktail of factors like external pressure, fear, social limitations or emotional stillness.</p><p>What’s more important is that, if the way progress or speed is evaluated in your company is flawed, it is fairly likely that other fundamental managerial aspects could be greatly improved as well. Better yet, these other managerial imperfections will tend to negatively affect the overall speed and productivity of your people much more prominently than any positive impact produced as a result of encouraging everyone to work on holidays. That was a long sentence, here is an example:</p><p><em>Bernie was concerned about his next deadline, so he decided to work two extra daily hours for the rest of the month. Disregarding the fact that he could become a bit less productive, tired, irritable, lower the quality of his work and lose some motivation on the way; he estimated that he could accelerate progress by a respectable 8.5%. Good job!</em></p><p><em>Unfortunately for Bernie and his company, on the first week during that milestone, one of his managers recalled a feature that </em><strong><em>suddenly became</em></strong><em> </em><strong><em>unimaginably</em></strong><em> </em><strong><em>more important than anything else</em></strong><em>. Bernie had to help there. That slowed him down a 67% on that week. On the third week, a new customer reached out asking for a demo of the product, requesting a few minor changes. Bernie, who is a multi-use engineer, had to provide support there as well. That slowed him down another 78% on that week. At the end of the milestone, he was able to </em><strong><em>accelerate progress by 8.5%</em></strong><em> by spending more hours sitting in front of his computer, but these other poorly handled events on the planning and organisational side </em><strong><em>slowed him down an average of 36.25% overall</em></strong><em>. As a result, he was late to the planned deadline. To alleviate that, his colleagues in management brilliantly decided to ask Bernie to jump into a short period of crunch mode. They promised to buy him some pizza.</em></p><h4>Need for Speed: The Race</h4><p>But, can these behaviours really be so destructive? Aren’t most startups supposed to operate in such a reactive and disorganised fashion? Isn’t the term <em>startup </em>equivalent to <em>working-until-your-brain-becomes-delirious</em>?</p><p>To properly analyse the impact of practicing different ways of evaluating velocity of development, place yourself in the following scenario:</p><p><em>You found an imaginary company called “Bug-Free Labs” to develop a predictive service that aspires to take all the hard choices in life for you — which toy is the best, what sport to practice, which university to go to, best beer, Ruby or Scala, merge or rebase, etc. For imaginary reasons, it is important for you to penetrate the market quickly, so you decide to monitor the development of the product.</em></p><p>Three months into the business, this is how the first plot looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*76rmqOoNOK59WXJ5c19PHQ.jpeg" /></figure><p><em>Note that in addition to your actual progress, there is a projected value that represents the potential outcome had you not suffered from some of the flaws/errors mentioned in this article.</em></p><p>Your team is a couple of features behind the expectation. In one hand, you were a bit undecided about the specific direction of the product in the last three months, and together with the pressure coming from external agents, you did not have the chance to plan too much ahead. But hey!, you feel that you are getting close to the right track. Moreover, you are confident that you can fix the situation by asking your colleagues for an extra effort. This lack of direction generated certain demotivation within the team, but it doesn’t seem too important to you at this point.</p><p>Two months later, you evaluate progress again:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WJ_YQ0ZuUSZUVZZtD063Zg.jpeg" /></figure><p>Damn it! Still behind.</p><p>Your people were able to squeeze a few extra hours in (note the thicker blue line), which provided for a slight increase in speed. However, they also turned their brains into more stupid and less productive machines, so the net improvement ended up being relatively low. More important than that, you were still dubious about two potential product directions, which originated a couple of minor adjustments to the product. This seemingly innocuous steering not only neutralised the impact brought by the extra effort in your team, but it made you lag behind a bit more than before.</p><p>At this point you start to feel slightly helpless. There is more pressure coming from the market and shareholders, and the discomfort and confusion within your team starts to form some grey clouds. Out of brilliant ideas, you decide to go for one last push and encourage your team to give the rest.</p><p>Three months later, you witness something that you find hard to believe:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RXqhU5WciS-uzrD6wOtsEQ.jpeg" /></figure><p>After a few of months of late working hours without much clarity on which direction your product is going, your team starts to feel unachieved, guilty, underestimated and exhausted. Also, they start to question your ability to guide them towards a good end, and start to think that they may be wasting their time there. At some point a few of them decide to look for a better life, leaving you with a void in resources from which you are going to need help and time to recover.</p><p>Now, on top of your list of problems, you are short of resources and cannot even dream about a successfully finished product for a while.</p><h4>Inception</h4><p>Hold on for a second… how is it possible that moving faster made everything go slower?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*UZLj4yUiEPOE01ZJgqLrlw.jpeg" /></figure><h4>Virtue vs Vice</h4><p>Remember that you work with people. People have brains, and brains are sensitive pieces of flesh that are conditioned by their circumstances and surrounding environment. If you need a brain to operate effectively, saying it so is not going to be enough; just like it is not enough to sit in front of a bunch of ingredients, close your eyes and scream <em>“Cake, build yourself!” </em>(<a href="https://www.youtube.com/watch?time_continue=59&amp;v=BSBTCOEdLkA">this folk</a> doesn’t count).</p><p>We don’t know it all about the human brain, but we know enough to benefit from a few key features. We know that the human brain:</p><ul><li>Does not operate well under sustained fatigue.</li><li>Is not able to handle multiple currents of information consciously at once.</li><li>Is constrained by the status of the limbic system, that is, it is modulated by emotion.</li><li>Provides chemical reward in presence of empathy.</li></ul><p>In other words, healthy schedules, clear channels of information, simplification of complexity, personal appreciation, honesty, cohesiveness in the mission, operational freedom, silent spaces, among others, are simple, yet very powerful ways to impact <strong>productivity</strong>, <strong>development</strong> and <strong>quality.</strong></p><p>If the previous paragraph sounded scary and you are now ready to enumerate your infamous list of companies that succeeded practicing privacy, military hierarchies, <em>“tough love”</em>, deception, capricious and elitist narcissism or micromanagement, remember that correlation does not imply causality. Companies may or may not be successful regardless of their internal organisation. What you can tangibly measure is how micromanagement alienates, honesty builds trust, privacy creates ignorance and autonomy fosters creative and confident leaders. That’s causality.</p><p>And now that you mention it, I also have my own infamous list of companies that succeed practicing virtuously reinforced cultures. My favourite excerpts are <a href="http://www.valvesoftware.com/company/Valve_Handbook_LowRes.pdf">Valve’s Employee Handbook</a>, <a href="http://www.huffingtonpost.com/entry/employee-benefits-basecamp_us_5697e9b6e4b0ce496423a3d2">Basecamp’s healthy work-style </a>, <a href="http://www.businessinsider.com/tony-hsieh-zappos-holacracy-management-experiment-2015-5?IR=T">Zappos’ Holacracy and weirdness</a>, <a href="http://blog.teamtreehouse.com/work-less">Treehouse’s 4-day weeks</a> and <a href="https://medium.com/u/ac3d4bfd3329">Chad Fowler</a>’s <a href="http://chadfowler.com/2014/01/22/the-crunch-mode-antipattern.html">anti-crunch-mode philosophy</a>.</p><p>Nowadays after all, your company is not anymore a means for your engineers to pay the bills. If your people is with you, that’s because they want to be with you; so help yourself, your team, your shareholders and your customers avoid pushing all of you into induced mediocrity.</p><p>At least not so obscenely.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e35c000c2cbc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Mean Startup 1 – Fear & Tradition]]></title>
            <link>https://medium.com/@joseluisugia/the-mean-startup-1-fear-tradition-6fa4dc0a09c7?source=rss-ebd6793b60e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6fa4dc0a09c7</guid>
            <category><![CDATA[tradition]]></category>
            <category><![CDATA[fear]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[organization]]></category>
            <dc:creator><![CDATA[Jose L Ugia]]></dc:creator>
            <pubDate>Tue, 01 Nov 2016 21:09:33 GMT</pubDate>
            <atom:updated>2017-10-03T22:01:26.592Z</atom:updated>
            <content:encoded><![CDATA[<p>The term <em>“startup”</em> is one of these concepts that one fine day crossed the line of popularity and started to become a cool way to name things. By now, you have probably heard of a bunch of similarly popular terms such as IoT, microservices, machine learning, growth hacking, unicorns, and so on. <br>However, one drawback of cool terms is that everyone wants to become part of what they encompass, and so we end up building impossible bridges between significance and reality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1xo_yst1AOxzfByr2ka-VQ.jpeg" /><figcaption>I am also a car light. Problem?</figcaption></figure><p>In addition to that, most of the times, we humans tend to be irresponsibly superficial about things and especially sensitive to social pressure, and hence, tradition. We resist change, find it hard to say “<em>no”</em> and follow trends, even when we perceive that aspects of them are utterly flawed. Sure, you can blame evolution for that. After all, most of our brains developed to do great at socialising and surviving within a community — and doing anything necessary to succeed on that quest. But it is this very own feature of ours that kept us alive throughout history, the same that creates an inherent bias on how we perceive the world today.</p><h4>Looking back</h4><p>One striking way to recognise this bias is by looking back in time, enough to detach our view from the social constraints and circumstances that create noise and contaminate our view. Consider, for example, the following topics:</p><ol><li>Tolerance for diversity</li><li>Deterioration of fanaticism in religion</li><li>Reduction of political frontiers</li><li>Political decline in discrimination of races</li><li>Physical war</li><li>Political gender discrimination</li><li>Prosperity of science</li><li>Slavery</li></ol><p>Note how what seemed complex or puzzling back in time, is widely adopted and accepted by most of us today — at least from a moral, commonsensical point of view.</p><h4>RAEF</h4><p>But it cannot be only tradition and social bias what today, keep us from objectively evaluating matters like the ones listed before.<br>Thinking myself, I certainly reject topics such as bullfighting, extreme religious events or <a href="https://en.wikipedia.org/wiki/Siesta">holy siesta</a> even though these are very precious traditions in the country where I come from. Hmm… there seems to be more to it.</p><p>Let us go back to the previous list of historical examples, and try to come up with other motivations that may have neglected change from happening on the aforementioned.</p><p><em>(Try to do the same exercise yourself before continuing with the read).</em></p><ul><li><strong>1 &amp; 3 &amp; 7.</strong> Insecurity and uncertainty of the unknown.</li><li><strong>2.</strong> Personal dissatisfaction, lack of control.</li><li><strong>4 &amp; 6.</strong> Jeopardy of privileged status of elite societies.</li><li><strong>5 &amp; 8.</strong> Thirst for control, narcissism.</li></ul><p>Now, if you do the math, these motivations seem to converge towards a very specific set of common denominators, among which <strong>fear</strong> visibly stands out from the rest.</p><h4>Fear + Social Bias</h4><p>Fear, mistrust and social lethargy still show prominently today, continuing to do a fantastic job on preventing us from adopting new knowledge and developments and, as a result, allowing us to profit from them. Personally, I cannot even help but feel certain discomfort towards matters that although I have adopted myself, most of our society has not yet. Here are a few of them:</p><ul><li>Migration</li><li>Economic inequality</li><li>Climate change</li><li>Regular exposure to toxic elements (alcohol, processed foods, radiation)</li></ul><p><em>How do you feel about these topics?</em></p><p>In many cases, the response to that question is plain oblivion. Even though we recognise these as critical topics, it is still hard for us to argue precisely about why they are such undesirable elements of our society that we do not conceive the idea of not taking action in order to alleviate them.</p><p>This takes us back to the idea that our internal wiring favours the collective voice of groups over the objective exactness of globally accepted conventions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WCEj9gOrEDo46gHF6kfTdA.jpeg" /></figure><p>There are probably some obvious examples of that surrounding you at this very moment. Sometimes, it is as easy as to look around for a few seconds and see how other individuals do things like:</p><ul><li>Follow people in a detour even if there is written indication pointing on a different direction.</li><li>Start to clap after a single individual plants the clapping seed, even if you do not believe there is a strong reason for it (e.g.: when planes land — even though most planes do land).</li><li>Drive past a red traffic light if other cars ahead of you do it too.</li><li>Expose different personalities of your own self depending on who you are hanging out with.</li><li>…and we keep opening bananas from the part where it connects to the plant, that is, the area where it is the hardest to break.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GUERZ4geM8_Slj02nwA6mA.jpeg" /><figcaption>Banana plant</figcaption></figure><h4>What are you talking about?</h4><p>But, <strong><em>didn’t you say something about startups?</em></strong> you may argue. Heck, you are right! Yet, all this has a purpose of context.</p><p>In the next part, we will see how these patterns and constraints play a rather relevant role on how we organise our companies, particularly startups.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6fa4dc0a09c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>