<?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 Amy Hakobyan on Medium]]></title>
        <description><![CDATA[Stories by Amy Hakobyan on Medium]]></description>
        <link>https://medium.com/@amyhakobyan?source=rss-7bab47f8f309------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*j0-B330GQRSit5_1QNZHfw.jpeg</url>
            <title>Stories by Amy Hakobyan on Medium</title>
            <link>https://medium.com/@amyhakobyan?source=rss-7bab47f8f309------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:00:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@amyhakobyan/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[Network Effect: Balancing Growth and Sustainability in Product Management]]></title>
            <link>https://medium.com/design-bootcamp/network-effect-balancing-growth-and-sustainability-in-product-management-c23c52399ae6?source=rss-7bab47f8f309------2</link>
            <guid isPermaLink="false">https://medium.com/p/c23c52399ae6</guid>
            <category><![CDATA[growth-marketing]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[growth]]></category>
            <category><![CDATA[growth-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Amy Hakobyan]]></dc:creator>
            <pubDate>Mon, 22 May 2023 18:54:33 GMT</pubDate>
            <atom:updated>2023-05-24T08:37:16.904Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently finished a book called <strong>“The Cold Start Problem”</strong> by Andrew Chen. Chen uses his expertise as a venture capitalist<strong> </strong>and his extensive experience developed at the premier venture capital firm, Andreessen Horowitz, and as an executive at Uber to come up with a systematic approach to one of the most common startup problems, the “cold start problem” by leveraging the power of <strong>networks effects</strong>.</p><p>Just a tad bit later Chen brings <strong>meerkats</strong> into the picture. Strange, I know. But I’m sold.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F6pUBXVTai18Iw%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fheadlikeanorange-meerkat-bbc-the-meerkats-6pUBXVTai18Iw&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2F6pUBXVTai18Iw%2Fgiphy.gif%3Fcid%3D790b76112b387ce9241ddece665c33a6b93fbc3f3e1aa363%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="234" frameborder="0" scrolling="no"><a href="https://medium.com/media/3ce995801031723280212345b7fbb073/href">https://medium.com/media/3ce995801031723280212345b7fbb073/href</a></iframe><p>So that being said, I wrote a short recap of the section that focuses on Network Effect, topping it with some outside research.</p><h3>Network effects: The power of a strong network for startup growth trajectory</h3><p>In the current tech landscape, it has become more and more difficult for startups to breakthrough. If we speak numbers, only 1% of startups go on to become unicorns. So, scaling your product becomes the top question on the founders agenda, but how can this be achieved?</p><p>Chen describes <strong>the network effect</strong> as the underlying factor for growth.</p><p>A network effect occurs when a product gets more valuable as more people use it. In order for a product to be successful, it’s not enough to build an awesome product and ship it- people have to actually come around and use it. What’s the use of listing your property in Airbnb if there are no renters? What’s the use of signing up in a social media network if there are no other users, and specifically your friends, around?</p><p>A networked product without a network is a useless thing — a telephone with no one to call, a ride sharing app with no drivers, a network of rooms to rent with no renters.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*8EIEPY19y3lWmkp5IQHSmw.png" /></figure><p>But aside from ensuring the existence of users for your product, these have to be the right users at the right time. Let’s look at the image above. If you were to open the Uber app from Seattle and all the drivers were spread across other cities of the USA with no one in close proximity, what would the use of Uber be to you?</p><p>Or, if you went on Tinder in hopes to find a match and all the matches were 1000 miles away, what use would Tinder have to you?</p><p>So how does a business solve these issues and move to amassing a large user base, while being usable to the right audience at the right time? The answer is- by using the power of network effects.</p><h3>Metcalf’s law</h3><p>One of the most prominent laws about Network effect was brought forward by Robert Metcalfe, stating that the value of a network is <strong>proportional to the square of its participants.</strong></p><p>In other words, the more people that are connected to a network, the more valuable the network becomes. Metcalfe developed this law based on his experience with Ethernet and the idea that the value of a communication network increases as more devices are connected to it. However, Metcalfe’s Law does not take into account factors such as the quality of connections or the varying value that different participants bring to the network.</p><p>It’s here that Meerkat’s law comes into the picture.</p><h3>Meerkat’s law</h3><p>In “The Cold Start Problem” Chen draws inspiration from the behavior of Meerkats, who benefit from living together in groups. Meerkats need to stay together in groups to survive and the more meerkats stay together, the easier it is to grow and stay safe. There is a minimum number of “meerkats” or participants required for growth to happen, called <strong>Allee’s threshold</strong>. However, growth is limited, as there is a point of overpopulation where the network’s value plateaus or even declines due to overcrowding and degraded experiences, called <strong>carrying capacity</strong>. Meerkat’s Law emphasizes the importance of considering the ecological dynamics of networks and the need to find the right balance between growth and sustainability.</p><p>Thus, the value of a network cannot be determined solely by the number of participants, but rather value and impact of overcrowding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*FMtf5FMR9VsGioKSK3uNnA.png" /></figure><h3><strong>Applying Meerkat’s law in Product Management</strong></h3><p>Meerkat’s Law doesn’t apply solely to the realm of animals. We, Product Managers, can derive great value of applying it to our work, too. Here are a few examples on different steps of the user’s journey:</p><ol><li><strong>User acquisition and onboarding:</strong> When a new product or service is launched, it’s important to consider the rate at which new users are onboarded. If user growth happens too fast and there aren’t enough resources in terms of infrastructure, support and more, this can lead to a decline in user experience, causing churn and poor retention. We can use Meerkat’s Law to guide the pace of user acquisition, ensuring that the product can effectively handle and support the increasing number of users without sacrificing quality.</li><li><strong>Quality over quantity</strong>: Meerkat’s Law states that there is a point where the value of a network plateaus or declines due to overcrowding. We can use this principle to prioritize quality over quantity. Instead of solely focusing on acquiring a large number of users or customers, product managers can focus on attracting the right users who bring meaningful value to the network. For example, don’t just launch a referral program with no filtering criteria as you may end up with a lot of fraud accounts who do no good to the value of your product. Speaking the meerkat vocabulary, if the goal is to strengthen the group of meerkats, make sure to bring on meerkats rather than wolves, deer and other animals on board. We need to approach growth thoughtfully ensuring that the network maintains its value and avoids the negative effects of overcrowding.</li><li><strong>Retention and engagement: </strong>Meerkat’s Law also highlights the importance of retaining and engaging existing users. While user acquisition is important, we should also focus on providing a great user experience and value to those part of our network, fostering meaningful interactions, and continuously improving the product. By prioritizing user satisfaction and engagement, we can increase the long-term sustainability and value of the network.</li><li><strong>Monetization strategies:</strong> Meerkat’s Law can influence the selection of monetization strategies for a product. We should consider strategies that align with the network’s growth and sustainability. In this scope we may try to strike a balance between offering value-added paid features or subscriptions while ensuring the core product remains accessible and valuable to a wide range of users.</li></ol><h3>Keeping in Allee’s threshold in mind</h3><p>Also, as PMs we need to keep an eye on the importance of reaching <strong>Allee’s Threshold</strong> for the growth of the product to accelerate. Allee threshold in product management refers to the minimum number of users or participants required to create and sustain network effects and positive feedback loops within a product or platform ecosystem. The concept is derived from the work of Martha Allee, who studied the role of network effects in business and economics. There are many examples of this in products we use- you have probably heard of Facebook’s famous “<strong>7 friends in 10 days</strong>” theory. Similarly, Slack needs at least 3 users of the same group to use it to be of actual value.</p><p>The Allee threshold is significant because it represents a critical mass of users necessary for the product or platform to achieve <strong>self-sustaining growth</strong>. Below this threshold, the network effects may not be strong enough to attract and retain users, resulting in a stagnant or declining user base.</p><p>Some key considerations regarding the Allee threshold in our day to day lives as product managers would be:</p><ol><li><strong>User acquisition:</strong> Product managers need to focus on acquiring a sufficient number of users to surpass the Allee threshold. This often involves implementing effective marketing strategies, referral programs, influencer marketing campaigns, partnerships, and other growth initiatives to attract early adopters and build initial traction.</li><li><strong>Value proposition:</strong> For users to join a product and retain, the product must offer a compelling value proposition. The features and benefits should align with the target users’ needs and have advantages over alternative solutions. The value proposition should be communicated effectively to potential users to drive adoption.</li><li><strong>User engagement and retention:</strong> Beyond user acquisition, product managers should focus on strategies to engage and retain users. Otherwise it’s just a huge funnel with no resulting outcome. The network effects that contribute to growth are reliant on active and satisfied participants. This may involve continuously improving the user experience, introducing new features, and building a sense of community for existing users .</li><li><strong>Feedback loops</strong>: The Allee threshold can be reinforced by positive feedback loops within the product or platform. For example, as more users join, the network becomes more valuable, leading to increased engagement, content creation, and interactions. These positive feedback loops contribute to extended growth and reinforce the network effects.</li><li><strong>Network expansion:</strong> Once the Allee threshold is surpassed, product managers can leverage the network effects to expand into new markets, attract additional user segments and more. If we look at Tinder’s example, it first launched in one campus and then expanded to the next one, and the next one, effectively capturing the large majority of the world countries. The same goes with Uber that launched in just a small area and expanded further on. The larger user base and the network effects create a strong foundation for growth and expansion opportunities.</li></ol><p>There’s much more to be said about network effects, but I feel like it would be too much to fit into a single article. In an upcoming article I will cover more aspects of network effect and how they help in driving growth.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c23c52399ae6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/network-effect-balancing-growth-and-sustainability-in-product-management-c23c52399ae6">Network Effect: Balancing Growth and Sustainability in Product Management</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Survivor bias: A Product Manager’s Outlook]]></title>
            <link>https://medium.com/@amyhakobyan/survivor-bias-a-product-managers-outlook-a0e78e2d001a?source=rss-7bab47f8f309------2</link>
            <guid isPermaLink="false">https://medium.com/p/a0e78e2d001a</guid>
            <category><![CDATA[perception]]></category>
            <category><![CDATA[cognitive-bias]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Amy Hakobyan]]></dc:creator>
            <pubDate>Wed, 19 Apr 2023 18:27:58 GMT</pubDate>
            <atom:updated>2023-04-19T18:27:58.017Z</atom:updated>
            <content:encoded><![CDATA[<p>Let’s play pretend today. Imagine that you are an experienced investor who receives a random letter in the mail from a stockbroker. Knock-knock.</p><p>The broker claims to know which stocks will go up/down in value in the near future. You give it a smirk, thinking someone is trying to fool you out of your savings. In the end, it’s not the first scam that has landed your inbox. But despite your skepticism, you keep an eye on the stock and notice that <em>it does, in fact, increase in value a few weeks later</em>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F5qFjc1bTPivNSY1Rez%2Fvideo&amp;display_name=GIPHY&amp;url=https%3A%2F%2Fgiphy.com%2Fclips%2Fmrnigelng-cooking-show-uncle-roger-5qFjc1bTPivNSY1Rez&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2F5qFjc1bTPivNSY1Rez%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="480" height="270" frameborder="0" scrolling="no"><a href="https://medium.com/media/6b01a6e34af96051aeca04ffd38aa582/href">https://medium.com/media/6b01a6e34af96051aeca04ffd38aa582/href</a></iframe><p>This repeats itself several times, with correct predictions every time, and a couple weeks later you find yourself thinking: <strong>this just can’t be a coincidence!</strong></p><p>Blown away by your dreams of a bright future in Neverland you invest your money …</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FlptjRBxFKCJmFoibP3%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fandersonpaak-money-pool-lptjRBxFKCJmFoibP3&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExazV1dHM5bWp3ZnJxOHk5N3V0YnFrcjV0amU0NTl2dW5kaGdob3J2cyZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FlptjRBxFKCJmFoibP3%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/6a5aae76036616d0f10d8424f5375828/href">https://medium.com/media/6a5aae76036616d0f10d8424f5375828/href</a></iframe><p>…and end up with nothing because it was all a well thought-out scheme. <strong>But how?</strong></p><h3>Unveiling the truth</h3><p>What happened in reality is that the broker simply had a very large pool of contacts (say, 20000) and sent 2 versions with 50/50 distribution to all users claiming the price of the stock would go up in Version A and that it would go down in Version B. As a result, part of the users <strong>got a right prediction</strong>. The same was repeated with the “right prediction” group several times and by the end of the sequence some users received several right predictions in a row, pushing them to invest.</p><p>In reality though this is not due to any special knowledge or expertise on the broker’s part. Instead, it is simply a matter of starting with a large enough sample size and the <strong>inability of the end user to see all the failed cases along the way.</strong></p><p>It’s here that the notion of <strong>survivor bias</strong> comes into picture.</p><blockquote>Survivorship bias, or survivor bias, occurs when you tend to assess successful outcomes and disregard failures. This sampling bias paints a rosier picture of reality than is warranted by skewing the mean results upward.</blockquote><blockquote><a href="https://statisticsbyjim.com/basics/survivorship-bias/">Jim Frost, Statistics by Jim</a></blockquote><h3>Looking back into history: a WW2 case</h3><p>A very interesting case of survivor bias occurred during WW2. As the Allies bombed German cities, the Germans shot down a lot of Allies’ planes. So, the planes needed more armor to withstand the fire. But adding armor made the planes heavier and reduced their range, so the military had to figure out where specifically to add the armor to be efficient.</p><p>They examined the bombers that came back from enemy territory and saw that bullet holes were centered along the wings, around the tail gunner, and down the center of the body. So, they assumed that since these were the areas most heavily affected by bombing, <strong>what they needed to do was strengthen these areas even more.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*YflzwcBBCcDLXEM14sqcJQ.png" /></figure><p>However, a statistician named Abraham Wald realized that <strong>they were only looking at the planes that survived</strong>, missing out on the planes that didn’t make it. So in reality, the planes that didn’t come back had critical areas, <strong>like the cockpit and engines</strong>, hit by bullets. So, instead of strengthening areas heavily hit by fire for planes that returned, <strong>they needed to do just the opposite and add armor where there were no bullet holes.</strong></p><p>By ignoring the non-survivors, the military <strong>fell into the survivorship bias</strong> <strong>trap.</strong></p><p>Survivorship bias is a problem in analyses where we focus on successful cases and ignore failures, <strong>leading to incomplete and skewed results</strong>. We tend to <strong>confuse correlation with causation </strong>by assuming that specific attributes caused success without considering other cases with similar characteristics that may not have succeeded.</p><h3>A Product Manager’s outlook on Survivor bias</h3><p>As commonly as cases of survivor bias happen in everyday life, they also tend to occur in Product Managers’ journeys. As Product Managers, we frequently come across instances where survivor bias may be present <strong>especially in data analysis and research environments</strong> where there is a threat to make a common mistake of relying too heavily on the feedback and behavior of the “survivors,” or the most active and engaged users of a product, while ignoring or undermining the needs and feedback of the broader user base. Focusing so much on the “social butterflies” of the products we work at results in <strong>catering the solution to a way narrower audience</strong>, leaving out a large chunk of the TAM from our radar.</p><p>Some types of survivor bias in a PM’s life can be:</p><ol><li><strong>Power user bias:</strong> This happens when we focus solely on the feedback of the most active users of our product (power users), causing us to miss out on feedback from the majority of the product’s user base. This can create a bias towards features that largely benefit the power users but leave out the needs of the larger user base.</li><li><strong>Sampling bias:</strong> In conducting user research, we as PMs should include different groups of users for a fuller outlook. If certain demographics are left out from research, they will get underrepresented in data. The resulting features will cater to the needs of specific groups only, reducing adoption.</li><li><strong>Feature request bias:</strong> We’ve all heard the “users want this” phrase when relating to feature requests. However, we should keep in mind that we shouldn’t approach building new features based on requests from the most vocal users as they may be quite low in value for the majority of our user base.</li><li><strong>Positive feedback bias:</strong> This has to do with a PMs ego and is pretty easy to succumb to. I myself made this mistake more frequently than I’d want to admit to, especially as I was getting started in Product Management. We all want to hear that the features we built are great value for the users and a success for the business. This is why we may be <strong>subconsciously inclined towards listening to the positive feedback</strong> <strong>only</strong> and ignoring negative feedback. This can create a bias towards investing in features that users may not actually find useful.</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FqlrBlSDevEdFeW5JwV%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Ftheoffice-qlrBlSDevEdFeW5JwV&amp;image=https%3A%2F%2Fmedia3.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExdXQxZGVzdXNtd3lkYmdsYXppbXZ5b2U4NGxjcHNhZ3lhNjQyYXR6ZCZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw%2FqlrBlSDevEdFeW5JwV%2Fgiphy_s.gif&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="361" frameborder="0" scrolling="no"><a href="https://medium.com/media/9e514d57d28c9faf8bc69a28365c40e4/href">https://medium.com/media/9e514d57d28c9faf8bc69a28365c40e4/href</a></iframe><p><strong>5. Survivor product bias:</strong> In competitor research, we may sometimes only consider successful products and ignore failed products, which may result in developing <strong>a false sense of what it takes to succeed in the market</strong> and a tendency towards fallibilities that lead competitor products to fail.</p><p><strong>6. Platform bias:</strong> If we concentrate too much on feedback from users who engage with our product through a particular platform or channel, we may overlook crucial feedback from users who engage with our product through other channels resulting in a distorted approach to prioritization of upcoming features.</p><p><strong>7. Confirmation bias:</strong> When we (often subconsciously) only seek out feedback that confirms our assumptions and neglect feedback that challenges them, we end up developing <strong>a false sense of the success of our product</strong>. This may create a bias towards what the future of the product will look like and what feature set to build.</p><h3>Overcoming survivor bias in our day-to-day work</h3><p>As I navigate through my journey in product management, I frequently remind myself to make sure to do the following:</p><ol><li><strong>Not limit myself to just one source of data</strong></li></ol><p>It’s important to look beyond our usual data sources (e.g. Amplitude, Tableau, Mixpanel) to get a different perspective. Relying solely on our quantitative data or user research can lead us down a narrow path and give an incomplete, distorted picture. That’s why we should <strong>overlap quantitative and qualitative insights</strong> to truly understand our customers’ experience and what motivates them.</p><p><strong>2. Keep in mind that data can be biased, too</strong></p><p>Another thing to keep in mind is that <strong>data isn’t always neutral</strong>. It can be influenced by the people who collect it, intentionally or unintentionally. To make sense of the data, we need to understand the context it was gathered in. When was it collected, and what was the mood of the people being interviewed?</p><p><strong>3. Keep some “what if” scenarios in mind</strong></p><p>It’s also helpful to play around with “what if” scenarios to expand our field of vision. For example, if a customer looking for a dress can’t find the exact word to describe it, what if they could use an image to search instead? By exploring different scenarios and possibilities, we can come up with more innovative solutions that truly meet our users’ needs.</p><p>As any cognitive bias, survivor bias is tricky, but the more we know about it, the better prepared we are to handle it in our day-to-day work.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0e78e2d001a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Minutiae of Modern Office Life: Focusing on What Matters]]></title>
            <link>https://medium.com/sfl-newsroom/the-minutiae-of-modern-office-life-focusing-on-what-matters-b937ba347997?source=rss-7bab47f8f309------2</link>
            <guid isPermaLink="false">https://medium.com/p/b937ba347997</guid>
            <category><![CDATA[office-culture]]></category>
            <category><![CDATA[workplace-culture]]></category>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[workplace]]></category>
            <dc:creator><![CDATA[Amy Hakobyan]]></dc:creator>
            <pubDate>Tue, 19 Dec 2017 07:19:49 GMT</pubDate>
            <atom:updated>2017-12-19T07:23:13.561Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“I like work: it fascinates me. I can sit and look at it for hours.”</blockquote><blockquote>― <a href="https://www.goodreads.com/author/show/3352.Jerome_K_Jerome"><strong>Jerome K. Jerome</strong></a></blockquote><p>A couple of years ago, I worked for this IT office that claimed to be the next thing in technology. And for a while, so I believed.</p><p>But one day, I discovered myself <em>sitting </em>in a 6-something hour <em>standup </em>discussing whether one of the slogans on a flyer should be “Because your work matters” or “Because work matters”, with endless flows of philosophy from my then-boss, all uttered in between of munching on his gluten-free, protein-rich meal.</p><p>At a point, I stopped listening, and concentrated on what I was doing: spending 6 hours of my life on listening to a lengthy lecture on something so trivial, while we had our marketing strategy unfinished and were lagging behind with feature delivery for our product.</p><p>As I embarked on my lengthy, 1-hour commute back home that night, I went over all the instances at my workplace when I spent hours on things that didn’t matter, sitting in endless meetings, gushing over the shade of blue in our new newsletter or spending months on choosing a voiceover for a 30 second long video. And finally, finally, it dawned on me.</p><h3>Get Shit Done</h3><p>You heard it. Get your work done. It’s fine thinking about detail when you have the cornerstones set and the core project ready. You can moan all you want about the shape of the “Submit” button when you are on time with the features and functionality. But let’s be honest, all those 15-minute-turned-into-3-hours standups are just a distraction, the new way of lazing around while soothing your ego that you’re doing something important.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SMyApc6kwb1bfBZo." /></figure><p>Don’t give me your “no-nonsense high-priority task performer” look. There comes a time on the timeline of employment when people don’t buy into that bullshit anymore. Mine’s been a couple of years ago.</p><p>So yeah, give your users the features they expect. Give them features. Think of shades, and subtleties and implications later on the way. Because you know, in order to think ‘bout the color of a button you should at least have its functionality ready at hand.</p><h3>Don’t Let the Moaners Ruin Your Mood</h3><p>You know that creep in the office that never has a nice word to say about <em>anything</em>? You sure do. This modern office atrocity has many faces: it can be your teammate, your boss, your manager, your colleague who doesn’t know shit about your project. What these people have in common is: they have an opinion about whatever you’re doing, and this opinion is no good. <em>Nothing</em> you do is good enough.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*Wfz3QBHHhoh5faQa." /></figure><p>It’s important to remember that criticism is all good as long as it is constructive criticism. If you find yourself in the mayhem of a workplace where all you do is receive criticism, question if you’re in the right place at the right time. Have a better suggestion? Great! Let’s discuss it! Simply wanna talk trash for the utter purpose of talking trash? Know where hell is? Now you go right there.</p><h3>Give. Yourself. A Break.</h3><p>Busy bee. In between of endless meetings, networking events, feedback sessions and retrospectives, there is still one more thing that is (or is supposed to be) happening: <strong>work</strong>. Yeah. You do have to finish that report, and create a roadmap, and think of/work on features and so much more. And with all that “noise” in the background, and jumping from task to meeting and from meeting to team building sessions, this almost-nonexistent phenomenon, work, suffers greatly, making you suffer along the way.</p><p>Overtime… Deadlines… All-nighters. I bet you know these words.</p><p>Staying overtime or pulling two all-nighters in a row is the modern-day workplace heroism that I also call <strong>Bad. Time. Management.</strong> And yes, if you’re going to boast about the 50 hours overtime you worked this week, I’m not impressed. How about thinking the quality/quantity correlation? No, for real. Get a life.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/0*KFJBJc4F9Vafd-7C." /></figure><h3>First, Second, Third… Priorities</h3><p>Ultimately, you need to prioritize your tasks and set boundaries. In many workplaces, there are only “urgent” “high priority” tasks. I had this experience in the same company with the 6-something-hour-standups. My boss would rush into my room with another “urgent” task, setting its deadline to yesterday, only to forget about it for 2 weeks or forever.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*IpioCh3pd5zrcuNG." /></figure><p>As I grew more experienced, I learned to distinguish between work that needs to be done now, and work that can wait till tomorrow. I learned to pick between a task and an outing with my family. Sometimes, you gotta pick the job. But that is sometimes.</p><h3>What do You Want?</h3><p>What you want matters. Let that sink in. There are 24 hours in a day. Don’t make all of them the “rush” hour. Focus on the bigger picture while also remembering to stay sane. In the end, the color of that freakin’ button won’t matter a decade from now. Your sanity? I BET IT WILL!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/459/0*Fr_LEQNPQvEmU4oQ." /></figure><h3>Your Takeaways?</h3><p>Stay Sane. Get things done. Block out the negative minds. Stop being busy without purpose. Accomplish great things.</p><p>Feel pressured by the mundanity of your workplace? Life is too short. Please, please <strong>work somewhere awesome!</strong></p><p>If you’ve ever felt the pressure I spoke about, and wondered if there’s a chance for a change, I’ll tell you the good news: there is! I made my own move to <a href="http://www.sflpro.com/">SFL</a> 2 years ago, and got to see work done at the time when it’s supposed to be done. More good news? They are <a href="https://sflpro.com/job/">hiring</a>!</p><p><a href="/service/mailto:info@sflpro.com">Let’s talk!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b937ba347997" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sfl-newsroom/the-minutiae-of-modern-office-life-focusing-on-what-matters-b937ba347997">The Minutiae of Modern Office Life: Focusing on What Matters</a> was originally published in <a href="https://medium.com/sfl-newsroom">SFL Newsroom</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>