<?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 Marek Pohlodek on Medium]]></title>
        <description><![CDATA[Stories by Marek Pohlodek on Medium]]></description>
        <link>https://medium.com/@marek.pohlodek?source=rss-47d7e81c0574------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*q5s9ojf9l3ou3HS7c1IDkg.png</url>
            <title>Stories by Marek Pohlodek on Medium</title>
            <link>https://medium.com/@marek.pohlodek?source=rss-47d7e81c0574------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:37:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@marek.pohlodek/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[Burnout Schmurnout: Outsmart Burnout With This Amazing Guide]]></title>
            <link>https://medium.com/@marek.pohlodek/burnout-schmurnout-outsmart-burnout-with-this-amazing-guide-ea9bc85e6c20?source=rss-47d7e81c0574------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea9bc85e6c20</guid>
            <category><![CDATA[stress]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[burnout]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[satire]]></category>
            <dc:creator><![CDATA[Marek Pohlodek]]></dc:creator>
            <pubDate>Tue, 08 Aug 2023 08:35:55 GMT</pubDate>
            <atom:updated>2023-08-08T08:35:55.994Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_HhprOvlBvLwB4Gs_gJTNg.png" /></figure><p>Welcome, dear reader, I’m glad you made it. Here lies the ultimate guide for navigating the treacherous unicorn-infested swamps of burnout! No more cookie-cutter advice. Instead, I’ve gathered the most daring, eyebrow-raising, and side-splitting strategies that are perfect for techies and non-techies alike. Prepare to be enlightened as we embark on this mending rollercoaster together.</p><p><strong>⛔️ Denial is Your Friend</strong> — Burnt out? Absolutely not! Just put on a happy face, throw on that irresistibly charming smile, and let denial work its magic. Not only will you save a fortune on therapy bills, but after you master the art of hiding your true feelings, you’ll also be on your way to becoming an expert at navigating the treacherous terrain of pointless meetings and office politics — all while keeping your inner turmoil under wraps. Your colleagues will marvel at your unwavering positivity, even as you secretly plot your escape to a deserted island in your daydreams.</p><p>🙉 <strong>Ignore the Experts</strong> — Speaking of therapy and mental health professionals… Pfft! Who needs ‘em? You’re a professional yourself, after all. You’ve got this all on your own, champ. Trust your gut and soldier on! What are you, a baby? And hey, if you ever feel like you’re not qualified to handle your own burnout, that’s just your imposter syndrome kicking in. Embrace it! After all, feeling like a fraud is a surefire sign that you’re totally crushing it at life. So, just keep doing what you’re doing and ignore any nagging doubts or pesky recommendations from those so-called “experts.” This also gives you more time for WebMD self-diagnoses.</p><p>🔁 <strong>Workaholic Wonderland</strong> — Instead of taking a break (which would give you more time to worry about burnout), ramp up the work! There’s no such thing as too much work. Free weekends? Holidays? That’s just a myth. Real winners work 24/7, 365 days a year at the minimum. And hey, why not add a side hustle or two to spice things up? What about that consulting thing you always wanted to do? Nothing says “I’m totally handling burnout” like grinding away at your passion project after a long day at your main gig. After all, money never sleeps, and neither should you! Remember, burnout is just a state of mind; you can always make time if you’re truly committed to success.</p><p>🔗<strong> Become One with Work </strong>— Merge your work and personal life until they’re indistinguishable. Answer emails at 4 AM, take work calls during family dinner, and sleep with your laptop. Wire your subconsciousness so that all of your dreams are solving work-related problems, so even when you’re resting, you’re really putting in overtime!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*21uq5zBUFDPGSw-ol94Dkg.png" /></figure><p>🎯<strong> Setting goals?</strong> — Goal-setting is for losers and takes up an unnecessary amount of time that could be utilized better. You’re better off “just doing” and hoping for the best. What’s the point of having priorities when you can just roll the dice every day? You’ll be a pioneer in the art of chaos management, inspiring others to embrace disorder and uncertainty as the new normal!</p><p>👑 <strong>Micromanage Mania </strong>— Don’t trust your team. They can’t handle anything without you — you are the glue that holds everything together. Double-check every single thing they do. Bonus points if you do everything yourself and then complain about doing everything yourself! Your team will never have to worry about making decisions, as you’ll single-handedly ensure that everything is under control.</p><p>⏳ <strong>Time Management? </strong>— Again, schedules and prioritization are for amateurs and people who are not able to improvise and make it up as they go. Embrace the chaos! Work on everything, everywhere, all at once (🍩), and remember: multitasking is the key to unlocking your true potential. You’ll be a shining example of “organized” chaos, making your coworkers feel better about their own time management skills — one way or another!</p><p>🤐 <strong>Zip It! </strong>— Keep your feelings bottled up, and don’t ever let anyone actually know that you are feeling burned out, under the weather, or that you cannot see the light at the end of the tunnel. Why share your struggles when you can brood in silence? No one needs to know you’re a human with emotions. Stoicism is the name of the game!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*newmeDh6VHxbicNU7ytiPw.png" /></figure><p>🍩 <strong>Enjoy the little things</strong> — Personally, after waking up, I make sure to drink a flat white (soy milk-only hombre) with an energy drink chaser. “Healthy” food? Ha! Don’t deprive yourself. What else is going on in your life? Calories (like weekends or work-life balance) are just a myth. Feast on donuts, pizza, and soda all day, every day. Your body is a temple, but who says temples can’t be filled with junk? It’s going to make you feel soooo good.</p><p>👻 <strong>Ghost Your Support System</strong> — Who needs friends, family, or colleagues? Embrace your inner lone wolf (wolves are alphas). Drop off the radar, ignore everyone’s calls, and show them you don’t need anyone! This will make everyone just appreciate you more, as nobody likes a complainer.</p><p>🔄 <strong>Stick with the Status Quo</strong> — Don’t even think about exploring new opportunities, or changing things up. Embrace where you are! What’s really the point of trying something new? What if it gets even worse down the line? Are you actively trying to make the biggest mistake of your life?</p><p>🚫 <strong>No Learning &amp; Chilling Zone</strong> — Personal development? Overrated. Rest? For the weak. You’ve already peaked, and you know it all! Why waste time on books, podcasts, coaching, therapy, or workshops when you’re the ultimate guru?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JTVixz8NwjVwTbbIF0zz6Q.png" /></figure><p>🎉 <strong>Congratulations</strong>! You’ve now learned the secret to living a life of utter chaos and complete disregard for your own well-being. With these groundbreaking strategies, you’ll be well on your way to becoming a living legend in the world of burnout. After all, who needs sanity and happiness when you can have unbridled stress and disarray? Remember, fortune favors the bold, and you’re now officially part of the bravest few. Now go forth and conquer burnout by embracing the madness!</p><p><em>(Or better yet, maybe just ignore this entire thing and actually take care of yourself instead.)</em></p><p><em>Thanks a lot for checking out this article! Needless to say, it’s a bit different to what I usually write, but I hope it clicked with you. If you liked what you read, feel free to connect with me on </em><a href="https://www.linkedin.com/in/marek-pohlodek/)"><em>LinkedIn</em></a><em>, or read one of my other articles below!</em></p><ul><li><a href="https://medium.com/@marek.pohlodek/5-huge-mistakes-i-made-in-my-first-months-as-a-product-manager-232b7d8a2b92">5 huge mistakes I made in my first months as a product manager</a></li><li><a href="https://medium.com/swlh/use-meetings-as-a-last-resort-31ec769bcae0">Use meetings as a last resort</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea9bc85e6c20" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 huge mistakes I made in my first months as a product manager]]></title>
            <link>https://medium.com/swlh/5-huge-mistakes-i-made-in-my-first-months-as-a-product-manager-232b7d8a2b92?source=rss-47d7e81c0574------2</link>
            <guid isPermaLink="false">https://medium.com/p/232b7d8a2b92</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[product]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Marek Pohlodek]]></dc:creator>
            <pubDate>Mon, 23 Mar 2020 13:36:44 GMT</pubDate>
            <atom:updated>2020-03-23T13:36:44.596Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QnerP-_hugJ_Ig0G" /></figure><h3>Focusing on the solution, not the problem</h3><p>A few weeks after I started working as a product manager, I was assigned a low-stakes product that lost its owner and kind of just lived a life of its own. Occasionally something happened when someone had the time for it, and sometimes nothing happened for weeks.</p><p>It was supposed to be a tailor-made internal solution, inside of an already existing and quite heavily used internal application, that was supposed to solve an issue one of our engineering teams.</p><p>At the time, the product already had a history. Decisions were made, trade-offs happened, merge requests were merged, deadlines were stated and not fulfilled, stakeholders asked for updates and showed their frustration… everyone was getting anxious, and I wanted to push this to the finish line and get a quick win. So I took some time to study the history, understanding the product and how it was supposed to work, and so on. Then I started focusing on the delivery, helping the team inch it towards the win.</p><p>You probably see where this is going. I was helping with delivery, but we were building the wrong thing.</p><p>In my defense, I did talk to the requestors, but in reality, I should’ve spent the first hours and days asking very different questions than I was. It took me a couple of uncomfortable interviews to figure out that the solution that we invested our time into was no longer solving issues that the team was experiencing, and many of the features that were at the beginning specified as must-haves have shown to be too difficult and time-consuming to make into a reality by the product team.</p><p>I knew the <em>what</em> and the <em>how</em> from my own research, and I believed I knew the <em>why </em>because the problem was clear to me. If I dug deeper, just a bit deeper, and asked some uncomfortable questions, I would’ve understood that the solution wasn’t going to work on the first day. However, I accepted it, started to like it, and it took me too long to challenge it. <strong><em>Why</em></strong><em> are we doing it </em><strong><em>like this?</em></strong></p><p>In the end, it was all just good old sunk cost fallacy. And since there was no owner, nobody felt in the right to make the decision to scrap it. So we scrapped it, and started again and right. The problem was clear and simple, but the solution was inefficient and unusable and not solving the right problems.</p><p>While my example was pretty specific for a certain scenario, the advice that I have is simple and universal, and commonly known. Make sure that you identify what the core of the issue you are solving is, and don&#39;t fall in love with the first solution you come across, even if you have already invested time and effort into it. <strong>Fall in love with the problem.</strong></p><h3>Focusing too much on delivery</h3><p>Looking back, even at the example above, I’ve spent a <em>big</em> portion of my time focusing on delivery, and not even close to enough time on discovery. Focusing too much on any one thing is an issue, so you should strive to find a healthy balance. And a balance that works best for your company. In some companies, a product manager will be there to fill in the gaps and serve as a patch for certain things and processes that are not working very well — which could be unfulfilled deadlines. If you are lucky, you will be living your <a href="https://www.goodreads.com/book/show/35249663-inspired"><strong>Inspired</strong></a> dreams filled with a bit of everything that makes Product Management such an awesome career.</p><p>If you are working for a company where product managers are expected to be Project Managers, you will most likely find it hard to find time to do everything else while focusing on driving projects forward, keeping stakeholders informed, and getting rid of impediments &amp; roadblocks. If on top of that, you are also a meeting facilitator, cross-team coordinator, a scrum master, a tester, … you might not even get to <em>think</em> about doing any discovery work.</p><p>You should be talking to your customers, even if you have dedicated UX Researchers. You should be aware of what your competition is doing and do regular checks yourself, even if you have Market Analysts. You should do experiments and try to find the best solution together with your team. You should be doing all of that and much more, so make sure that you get your feet wet as soon as possible, and don’t take no for an answer. Don’t just be a deadline keeper, or you might get stuck doing that forever.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a_xRP_yJVzJTbFvh" /></figure><h3>Not involving engineers, designers, and analysts from the start to “spare them the trouble”</h3><p>For a while, I honestly thought I was doing people a favor. I didn’t want to bother anybody, especially engineers, and I also felt the need to prove myself and show that I could prepare that fleshed out specification myself. I would write the specs down in detail and hand it to them so that they could use their time for the most valuable thing they know how to do — coding. “Don’t worry, leave this <em>unnecessary</em> ideation to me”, right?</p><p><strong>Very, very wrong.</strong></p><p>On one hand, an engineer’s time is precious and should be handled with care (for example, don’t invite them<em>, or anyone else,</em> to <a href="https://medium.com/swlh/use-meetings-as-a-last-resort-31ec769bcae0">useless meetings</a>). On the other hand, great product managers include developers, designers, analysts and sometimes others who will be involved anyway from the beginning, because they know that working together with them will allow them to find the best possible solution, and how to validate it and build it right.</p><p>Especially at the beginning of your journey, you are going to get things wrong. You are much more likely to get things wrong if you only think about them by yourself with minimal involvement from the rest of the product team. Involving people is going to make everyone’s job easier — not harder — and you shouldn’t be afraid to ask for opinions, or straight up ask for help.</p><h3>Making assumptions &amp; taking things personally</h3><p>This piece of advice is useful for life in general, and it&#39;s also quite self-explanatory. Especially in product development, it can make everyone’s life hell if people&#39;s assumptions don’t match.</p><p>Here the advice comes first. Don’t make assumptions about your users, your product team, or your stakeholders and their needs.<strong> Just don’t.</strong></p><p>When building a product, or anything, ask questions, see if users or data support your assumptions, but don’t just assume something and call it a day. Even dealing with interpersonal relationships, it’s better to verify what you think is happening, because sometimes it’s not, and it can lead to some juicy office drama.</p><blockquote>Without data, you’re just another person with an opinion.</blockquote><p>Working as a product manager, there will also be times when people who don&#39;t see into your head and all of the decisions you made and why you made them (so, most people) will question you, and your decisions, or make assumptions as to why you have made some decisions. There will be times when they will heavily disagree with you, and tell you that your brilliant idea is not a brilliant idea. Sometimes, they will be right. It&#39;s a part of the job. Hopefully, most of this feedback will be constructive, and you will use it to move you forward. Either they will be right, and they will save the company some trouble and time, or they are wrong, and you might decide to communicate your decision making process more in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_JEnHPFC1krJoY3I" /></figure><h3>Not communicating enough</h3><p>Communication is where it all starts and ends. If you are not communicating enough with your product team, stakeholders or users, you&#39;re gonna have a bad time.</p><p>Especially if you are working with a <strong>remote team</strong>, you have to make sure that you are on the same page. You don&#39;t have the luxury of bumping into each other near the watercooler and resolving a small misunderstanding without it becoming an issue. You have to make sure you have channels open that allow for all kinds of information to flow through, and more importantly that everyone feels safe to speak their mind, and know that they can bring up anything for discussion.</p><p><strong>When in doubt, overcommunicate.</strong></p><p>Are you not sure if your team is interested in what you have to say? Would you mention it or would you ask your colleague about it during lunch or coffee? If yes, it&#39;s probably worth mentioning it. The same goes for updating your stakeholders — are you not sure if they&#39;d be interested in what happened in the last two weeks, even though the answer is “nothing happened”? The answer is probably yes.</p><p>“There has been no new development since the last time, we are trying to figure out if there&#39;s an easier way to do it. I&#39;ll update you in the next two weeks.” is much better than silence, followed by more silence, followed by an “Ok, we can&#39;t do that.”.</p><p>When working remotely you have to very actively decide to communicate, while if you are working with people together in the same room, information usually flows by itself. Make those extra steps and keep everyone informed. If you don’t, it might come back to bite you in the ass.</p><p><em>Thanks a lot for checking out this article! If you liked what you read, feel free to connect with me on </em><a href="https://www.linkedin.com/in/marek-pohlodek/)"><em>LinkedIn</em></a><em>, or read one of my other articles below!</em></p><p><a href="https://medium.com/swlh/use-meetings-as-a-last-resort-31ec769bcae0">Use meetings as a last resort</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=232b7d8a2b92" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/5-huge-mistakes-i-made-in-my-first-months-as-a-product-manager-232b7d8a2b92">5 huge mistakes I made in my first months as a product manager</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Use meetings as a last resort]]></title>
            <link>https://medium.com/swlh/use-meetings-as-a-last-resort-31ec769bcae0?source=rss-47d7e81c0574------2</link>
            <guid isPermaLink="false">https://medium.com/p/31ec769bcae0</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[efficiency]]></category>
            <dc:creator><![CDATA[Marek Pohlodek]]></dc:creator>
            <pubDate>Wed, 17 Jul 2019 06:08:25 GMT</pubDate>
            <atom:updated>2022-01-07T15:41:07.052Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*orniFGTTlrWcpdPe" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=medium&amp;utm_medium=referral">Charles Deluvio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Has this ever happened to you?</h3><p>You’re sitting at your desk, and you decide to check your emails. Among other things, you see a Google Calendar invitation called “<em>Important meeting about project X</em>”. There’s no information about the meeting anywhere to be found, and it’s happening early tomorrow morning. You’re not even involved in the project at this point, but it’s someone with a fairly important position in the company that sent you the invite, so you decide you will go because it will probably be important — otherwise, they wouldn’t have invited you… right?</p><p>You get to the meeting, and there are 7 other people already sitting down, while 14 were invited in total. You ask your colleague if he knows what this meeting is about, but he has no idea either. The facilitator is 5 minutes late because he got the wrong room. There are remote people who are supposed to be joining the meeting, but nobody made it clear which tool they should use to jump in. When they finally join, there are some technical issues which take a few minutes to fix. You wait for a few more minutes for any other people who might be late, but nobody else joins in the end.</p><p>The facilitator starts explaining why this meeting is happening, and after 15 minutes of nothing, it’s getting clearer and clearer.</p><p><strong>You didn’t have to be there. None of you had to be there.</strong> This could’ve been a Slack message, an email, or a hallway conversation.</p><p>Most people are on their laptops doing something else, and there are no real next steps or any outcome out of the meeting after 30 or <em>(god forbid) </em>60 minutes.</p><p>If you are going through hell, keep going, they say…</p><blockquote><strong>Disclaimer</strong></blockquote><blockquote>I’m writing this from the point of view of a Product Manager, a role which sometimes gets flak for facilitating <strong>a lot of meetings</strong>. And at times <strong>lots</strong> <strong>of meetings</strong> with <strong>lots of people.</strong></blockquote><blockquote>The article is mainly focused on cases when there are more than two people in a meeting (or solving a problem), and it will most likely make the most sense to people who are working with remote teams. However, the best practices can be used anytime, anywhere.</blockquote><blockquote>If that sounds like something you’d be interested in, read on!</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BRl3BoGipdfeREwB" /><figcaption>Photo by <a href="https://unsplash.com/@karishea?utm_source=medium&amp;utm_medium=referral">Kari Shea</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What would’ve been better?</h3><p>The story above is hopefully something that nobody has to sit through, ever, or at least not on a regular basis. It’s a one-off fluke that gets corrected right then and there.</p><p>But a meeting like that is <em>not </em>the thing that usually happens. <strong>Usually, one or two things out of that story are enough to make a meeting feel somewhat dreadful.</strong></p><p>Maybe it was not really clear what the meeting was supposed to be about and what <em>exactly </em>should’ve been achieved by taking 30 minutes out of peoples day. Maybe it’s the first time everyone is hearing about the problem, and they need time to think it through first. Maybe people were not <em>at the meeting </em>enough and they didn’t pay attention. Maybe the equipment wasn’t working…</p><p><strong>All meetings are not necessarily the devil. </strong>If done correctly, with at least some preparations on both sides and with respect for other peoples time in mind, meetings definitely have their space in the workplace and can be an effective way to resolve many problems. But for a huge portion of cases, there will be a more effective and productive way how you can solve things, and in a way where people will not have their morning or evening sliced into <em>“before meeting”</em> and<em> “after meeting” </em>times. This can result in people not being able to concentrate, not being able to get into the right state of mind for work that is necessary to code (or any other creative work), and making them generally less productive.</p><p>I believe that the reason why bad meetings happen is simple. With tools like Google Calendar, it’s just so extremely easy to do them nowadays.<strong> It’s low-effort.</strong> You click a few times, pick a few names and voila!</p><p><strong>With great power </strong>(of inviting people to meetings), <strong>comes great responsibility</strong> (of only doing it when you can’t solve whatever you have to solve more effectively)<strong>. And low-effort meetings are very ineffective.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7FfL3vhM_T4x1SHGrEI0Tg.jpeg" /></figure><h4>What to do before inviting people for a meeting</h4><p>Before you even start thinking about the word <em>meeting</em>, there’s plenty of things you can do.</p><ul><li>Share all information about the problem somewhere publicly beforehand (<a href="https://slack.com/"><strong>Slack</strong></a><strong>)</strong>, and start an <strong>async discussion</strong> with relevant stakeholders. They will join in when they have the time, and if something is complex enough and cannot be handled asynchronously or in a different way, they might even recommend a meeting themselves.</li><li>Use a tool like <a href="https://www.loom.com/"><strong>Loom</strong></a><strong> </strong>to prepare a quick (video) summary of the problem/project. What is the difference between speaking for 10 minutes at the beginning of a meeting and doing that same 10-minute speech in advance? Share it with the relevant people you would’ve invited to the meeting, and give them a way to see it and discuss it, when they have the time. Just last week I’ve decided to use this for a smaller project kick-off, and the feedback was positive. (I recommend you give <a href="https://www.loom.com/"><strong>Loom</strong></a><strong> </strong>a shot)</li></ul><h4>Try to think outside of the meeting box</h4><p>Even for certain situations when a meeting might be the first choice, like <strong>team meetings</strong>, or <strong>kick-off </strong>and <strong>sizing meetings</strong> for certain projects, there might be a better, less invasive alternative, or a way to make them more effective.</p><ul><li>Use <a href="https://slack.com/"><strong>Slack</strong></a><strong>, </strong><a href="https://www.loom.com/"><strong>Loom</strong></a><strong> </strong>or another lool as mentioned above to provide an easily digestible summary.</li><li>Provide a way for general discussions or in case something about the problem is unclear into a document which you share with all stakeholders. <a href="https://www.dropbox.com/paper"><strong>Dropbox Paper</strong></a><strong> </strong>or <a href="http://docs.google.com/"><strong>Google Docs</strong></a> work great as you can assign actions to people, but any other collaboration tool will work.</li><li>For <strong>team meetings</strong>:<br>- If taken seriously, standups on <a href="https://slack.com/"><strong>Slack</strong></a><strong> </strong>work great and allow people to give their inputs when they feel comfortable to do so.<br>- Gather all information and notes from all members for other <strong>team activities </strong>(retrospectives, …) beforehand and engage in discussions in advance where applicable. If you do go with a meeting, it will make them extra quick and effective. Also, half of your meetings notes are now done before the meeting even started!</li><li><strong>Don’t get me started on status meetings. </strong>Why would you need everyone in the same room at the same time to tell you how a project is going? Unless stakeholders agree that there is a blocker that needs to be discussed, <a href="https://www.atlassian.com/software/jira"><strong>JIRA</strong></a><strong>, </strong><a href="https://slack.com/"><strong>Slack</strong></a><strong>, </strong><a href="https://www.loom.com/"><strong>Loom</strong></a><strong>, </strong><a href="https://www.dropbox.com/paper"><strong>Dropbox Paper</strong></a><strong>, </strong><a href="http://docs.google.com/"><strong>Google Docs</strong></a><strong> </strong>… you see the pattern here.</li></ul><h4>What to do when meetings actually have to happen?</h4><p>When you’ve considered all your options and a <strong>meeting seems like the most effective way to deal with a problem</strong>, make sure that you make it as effective as possible, and that you appreciate the time of everyone you invite.</p><ul><li><strong>Put all the information about why the meeting is happening into the summary of the meeting invitation</strong>: the agenda; summary of the <em>problem</em>; what should be the outcome of the meeting; links or other sources that could be useful before or during the meeting</li><li><strong>Provide a way for people to discuss the <em>problem </em>beforehand</strong>, in a collaboration tool or a shared document.</li><li><strong>Invite only the people who are necessary for the meeting</strong>, if you are not sure if someone should be invited, you can mark them as optional.</li><li><strong>Get in the meeting room before the meeting starts</strong>, and prepare all of the materials that could be referenced during it. Test the equipment in case you will be hosting people on a call. Avoid delays.</li><li>Make sure that<strong> </strong>the people you are inviting<strong> don’t have any other meetings at that time</strong>, <strong>respect their time and their set blockers</strong> (or possible no-meetings-days), and try to<strong> schedule the meeting in advance</strong> (tomorrow morning does not give the people enough time to prepare)</li><li><strong>Always take meeting notes</strong> and write down <strong>actionable next steps </strong>with responsible people assigned to them. Set deadlines to encourage action, and follow-up in case of inaction. Share it with the attendees and anyone else who might be interested.</li><li><strong>Less is more.</strong> I am known for sometimes going a little bit overboard with my summaries, at times including more information than is necessary <em>(I’m working on it)</em>. A huge block of text will most definitely get fewer responses and less engagement than 2–5 sentences. A 15-minute meeting will be better received than a 90-minute meeting. Prepare, and work on making all of the information easily understandable and digestible.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UMlGKGiPQEt5UoSN" /><figcaption>Photo by <a href="https://unsplash.com/@danedeaner?utm_source=medium&amp;utm_medium=referral">Dane Deaner</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>What to do before and after accepting an invitation for a meeting</h4><p>Yes, you have responsibilities too! While I truly believe that if you have no idea what the meeting you were just invited to is about, you shouldn’t have to attend, it will most likely keep happening if no actions are taken.</p><ul><li>If there is no indication what the meeting is about, you could decline the invitation, let the inviter know why, <strong>and ask them to update the invitation with all the relevant information, </strong>or try and get them to engage in the topic in some other way<strong>.</strong> You are most likely not the only person who will have no idea what the meeting should be about, so you will be doing others a favor as well!</li><li>If you know you won’t be able to make it to the meeting, decline in advance so that the inviter is aware.</li><li>If the inviter did their due diligence and prepared information for you to digest beforehand, <strong>read it and engage in the topic before the actual meeting</strong> at a suitable time for you. There’s nothing worse for an inviter than knowing that even if they spent all that time for the preparations, nobody bothered to read anything.</li><li>When you are at the meeting,<strong> be at the meeting! </strong>The sooner you can figure out the next steps regarding whatever you are meeting about, the sooner you can go back to doing <strong>uninterrupted </strong>work. Highly effective meetings are quick.</li></ul><h3>Takeaways</h3><ul><li>Unnecessary or ineffective meetings can have devastating consequences on productivity, but meetings with a clear summary, agenda, and information provided beforehand <strong>are not the devil!</strong></li><li>Try out handling problems/projects for which you would’ve normally created a meeting in a way which doesn’t require everyone to be in the same room at the same time, and let me know the results!</li><li>If a meeting has to happen, preparation from both parties is really important and should not be skipped. Preparation will make the meeting go smoother, and faster.</li><li>Make sure you are on time, and <strong>if you are at the meeting, be at the meeting</strong>.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31ec769bcae0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/use-meetings-as-a-last-resort-31ec769bcae0">Use meetings as a last resort</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>