<?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 Pavel Averin on Medium]]></title>
        <description><![CDATA[Stories by Pavel Averin on Medium]]></description>
        <link>https://medium.com/@averpavel?source=rss-a06b14ffee99------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QscNnKHDkS7g6OoUZNpFbQ.png</url>
            <title>Stories by Pavel Averin on Medium</title>
            <link>https://medium.com/@averpavel?source=rss-a06b14ffee99------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:01:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@averpavel/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[Tips for remote managers — online meetings]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://averpavel.medium.com/tips-for-remote-managers-online-meetings-5e20606d55c3?source=rss-a06b14ffee99------2"><img src="https://cdn-images-1.medium.com/max/2600/1*UIjGr4sM9dAB_mokZa9kEw.jpeg" width="5184"></a></p><p class="medium-feed-snippet">Quick and tested bits of advice on how to make your remote meetings better.</p><p class="medium-feed-link"><a href="https://averpavel.medium.com/tips-for-remote-managers-online-meetings-5e20606d55c3?source=rss-a06b14ffee99------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://averpavel.medium.com/tips-for-remote-managers-online-meetings-5e20606d55c3?source=rss-a06b14ffee99------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e20606d55c3</guid>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Pavel Averin]]></dc:creator>
            <pubDate>Sun, 19 Apr 2020 16:39:12 GMT</pubDate>
            <atom:updated>2020-04-19T16:39:12.386Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[What I’ve learned after moving from projects to operations]]></title>
            <link>https://medium.com/how-to-build-products-and-teams/what-ive-learned-after-moving-from-projects-to-operations-18c673e461f0?source=rss-a06b14ffee99------2</link>
            <guid isPermaLink="false">https://medium.com/p/18c673e461f0</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Pavel Averin]]></dc:creator>
            <pubDate>Fri, 02 Nov 2018 18:54:57 GMT</pubDate>
            <atom:updated>2018-11-02T18:54:57.107Z</atom:updated>
            <content:encoded><![CDATA[<p>6 months ago I changed my role from PM team leader to a PMO team leader. What does this additional O mean?</p><p>Previously I managed web and mobile development projects and was a team leader for other project managers. There were different projects: small and large; with a tight deadline and without one; web, cross platform, design and mobile. I worked with some of my clients for couple of years and the best thing what I felt is that we’re doing the awesome stuff together. But at some point I understood that I want to make the next step and start working on shaping the processes and building the company.</p><p>That’s why I became a leader of Project Management Office or PMO. In short, PMO is the part of the organisation which supports delivery process. My PMO is dealing with: talent management and capacity planning (you can find some cool practices here), internal products development and information security.</p><p>So what I’ve learned after the first half a year:</p><h3>Projects vs Operations</h3><p>I thought it will be completely different to lead the operations as there weren’t any specific deadlines. We have some repeatable activities and our goal is to perform them better, faster and smarter. We just need to track the right metrics and make sure we have constant improvements, right?</p><p>Wrong.</p><p>After a few unsuccessful and successful attempts to provide some bigger improvement I understood that we need to treat the changes as a mini-projects. We have to define some clear goal, scope, stakeholders, MVP and start working in iterations. Only this mental trick helped me to start planning and executing the operational improvements.</p><h3>Business vs Delivery</h3><p>Previously, I was mainly focused on the delivery side of the project. It’s when we have some scope, or we help to define it, then we’re working on bringing the maximum value in the shortest time. Of coarse with the best quality.</p><p>When I switched to operations which are tightly connected with a business side of the company, I understood that we always need to take the global picture into account.</p><p>Previously I was managing couple of projects, but now I’m supervising some of the processes for the whole company and there are much more variables to consider. Each choice on the scheduling side will influence the current projects and the new ones. And it’s damn hard to understand which requests has higher priority and which solutions will bring benefit to each side.</p><p>Those choices and issues are hard but very fulfilling when solved successfully.</p><h3>Leading full-time</h3><p>It’s a big difference between doing the work and leading for part time and leading for full time when others are doing the work. I still have the bad habit of involving into the work too much, when the smarter move will be to coach my team to do the work better.</p><p>I see two main issues with involving too much in the work the team is doing:</p><ol><li>The team won’t learn how to deal with issues by itself.</li><li>I won’t have time to do what I should do: strategy and execution.</li></ol><p>Key Takeaways:</p><ul><li>There is always a project. It doesn’t matter if you’re doing ongoing product development, operations or. just leading people. You will deal with timeframes, scope, execution and results evaluation. You can use different approaches for management — scrum, lean, OKR’s or nothing (😱), but considering the changes in operations as micro-projects will help you a lot.</li><li>Think globally. The result of your work will influence others. The wider operations the bigger the outcome. You need to understand dependencies and make choices wisely.</li><li>Become redundant. Don’t do the work for your team (don’t interrupt the progress). Instead — generate vision and strategy and create conditions for execution.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18c673e461f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/how-to-build-products-and-teams/what-ive-learned-after-moving-from-projects-to-operations-18c673e461f0">What I’ve learned after moving from projects to operations</a> was originally published in <a href="https://medium.com/how-to-build-products-and-teams">How to build products and teams</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Synchronous and Asynchronous Communication.]]></title>
            <link>https://medium.com/how-to-build-products-and-teams/synchronous-and-asynchronous-communication-322d4e084302?source=rss-a06b14ffee99------2</link>
            <guid isPermaLink="false">https://medium.com/p/322d4e084302</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Pavel Averin]]></dc:creator>
            <pubDate>Sat, 29 Sep 2018 20:21:05 GMT</pubDate>
            <atom:updated>2018-10-10T06:45:31.428Z</atom:updated>
            <content:encoded><![CDATA[<h3>Synchronous and Asynchronous Communication. What’s the difference, which one to choose and how to establish effective communication within the team 💁‍🙇‍</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Ispv1XHS6NDbO5_C7YpvQ.jpeg" /></figure><p>Have you ever had a feeling that some topics or questions should be discussed in a different way?</p><p>For example:</p><ul><li>there is a pending issue which should be resolved in minutes and somebody sends an email when he could just fire a <strong>@channel</strong> on slack</li><li>impatient team member writes a 500-word essay about quarterly planning on slack and pings for immediate response</li></ul><p>Below is my take on <em>Synchronous </em>and<em> Asynchronous Communication, </em>which one to choose for different kinds of discussions, which tools to use and how to implement them within the team.</p><h4><strong>Synchronous communication</strong></h4><ul><li>Use Slack, Skype, WhatsApp, Facebook Messenger, Telegram — any tool which looks like a chat</li><li>Used when there is a pending issue which requires an immediate reaction. In this case, stakeholders need to have a common understanding of what is <em>urgent. </em>Also, they should use the same tool and be present.</li><li>Fits for low-stakes decisions.</li><li>Short questions and answers. The subject of the conversation changes fast — in hours or days.</li></ul><h4>Asynchronous communication</h4><ul><li>Use E-mails, Google Docs, Confluence, Jira — anything where you’re not supposed to answer immediately</li></ul><p>You can use slack but don’t be frustrated if you won’t get the immediate reaction. Also, the good way to use slack for asynchronous communication is to keep the theme based channels. For example, you have an important decision to take or case to solve. You can create a channel and keep all conversations regarding this topic there. Set the topic for the channel and explain it for all channel members. You can write long messages and don’t require immediate answers. If you notice that conversation starts to lose its focus, simply ask your buddies to move all gifs and non-relevant comments to another channel as you’d like to keep this channel only for discussions about the mentioned topic.</p><ul><li>Fits for high-stakes strategic decisions.</li><li>Long questions and answers. The subject of the conversation stays the same for a long time — weeks, months and even years.</li></ul><h4><strong>How to establish the efficient way of communication in the team</strong></h4><ul><li><strong>Define the communication channels for the different kinds of questions/topics/issues. </strong>Build the matrix of conversation subjects and communication channels. Write there which issues will be discussed on slack, which on jira and which through the e-mail. You can add there <em>“time to answer”</em> (2h, 1d, 1week) or just add <em>sync</em> or <em>async.</em></li><li><strong>Bring the team on board and ask for a feedback.</strong> Explain to them why it’s important to have the common understanding of where and how you could talk about different topics. The team should know that finding the right way for communication is the key to effective collaboration. Show them that they will get more value and less frustration if they will know what to expect from each other when discussing the issues in a more structured way. For example, they won’t be frustrated by not getting the immediate reaction on a slack channel for the request that was defined as non-urgent and the response time was defined as 2 days. Also, they could get more value from the meaningful conversation regarding important topics through the email. Don’t forget to let the team discuss and agree on the communication channels and rules.</li><li><strong>Be consistent</strong>. Once the rules are established and agreed within the team, start to follow them. Changing the habits is hard and you’ll definitely have pitfalls. If you’d like to get the most from the structured approach to communication, you have to be consistent with the execution of those rules. Don’t be afraid to say something like this:</li></ul><blockquote><em>“Thanks for the question and 2 pings, let’s move this conversation to email (another channel, google doc, confluence) where you could give more detailed information about the issue and I’ll be back with the answer till the end of the week”.</em></blockquote><ul><li><strong>Evaluate and adjust. </strong>Not all rules work and it’s normal. If you’ll notice that you have to move some conversations to the synchronous or asynchronous way and this will bring more value to the team, just do it. The key is to help yourself and the team to gain the most from the way you cooperate.</li></ul><p><em>Thank you for reading!</em></p><p><em>If you liked this article please give a clap :)</em></p><p><em>If you’d like to get more articles like this, please follow me on </em><a href="https://medium.com/@Averpavel"><em>medium</em></a><em> or twitter </em><a href="https://twitter.com/Averpavel"><em>@averpavel</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=322d4e084302" width="1" height="1" alt=""><hr><p><a href="https://medium.com/how-to-build-products-and-teams/synchronous-and-asynchronous-communication-322d4e084302">Synchronous and Asynchronous Communication.</a> was originally published in <a href="https://medium.com/how-to-build-products-and-teams">How to build products and teams</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Focus. Slow down to speed up]]></title>
            <link>https://medium.com/how-to-build-products-and-teams/focus-slow-down-to-speed-up-54e879851c8a?source=rss-a06b14ffee99------2</link>
            <guid isPermaLink="false">https://medium.com/p/54e879851c8a</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[focus]]></category>
            <category><![CDATA[slowing-down]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Pavel Averin]]></dc:creator>
            <pubDate>Sat, 18 Aug 2018 14:06:28 GMT</pubDate>
            <atom:updated>2018-08-18T14:06:28.196Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yx4GSRGz3ahX_3RbXRI6qA.jpeg" /></figure><p>I think you’ve noticed that the world is moving with the enormous pace. It’s hard to keep up with the number of news, ideas, buzzwords, etc. And I bet you’d like to achieve more, deliver better results and win all the battles.</p><p>The truth is that you can’t be on top in everything. We can’t catch all the initiatives and be perfect in everything we’re starting.</p><h3>Randi Zuckerberg on Twitter</h3><p>The entrepreneur&#39;s dilemma: Maintaining friendships. Building a great company. Spending time w/family. Staying fit. Getting sleep. Pick 3.</p><p>Here is a short <a href="https://www.inc.com/jessica-stillman/work-sleep-family-fitness-or-friends-pick-3.html">Inc’s article about entrepreneur’s dilemma</a>.</p><p>But what could we do if we set the ambitious goals and want to do something meaningful and achieve the unachievable. This simple rule works for me:</p><blockquote>Less is more. Do whatever you want but not everything at once.</blockquote><p>Recently, I decided to slow down. To keep focus on less amount of initiatives and actually finish them. Or at least deliver them to the point I can make a decision to resign or move forward with it.</p><p>Below are some of the tips I’d like to share with you. Hope they will help you to improve your focus and make you a little happier. Feel free to challenge them, comment and add your tips in the comments.</p><ul><li><strong>Work Initiatives</strong>. We use V2MOMs at work and it’s a great tool to create sync within the company’s initiatives and goals. The only problem is there is often too many goals. Recently we’ve tried the quarterly theme approach: set the single simple goal for the quarter and make sure everyone is aligned with it. After the first quarter of using the theme I can see that we’ve reached the major goal, decision making process was simplified because there was a major criterion and we’ve definitely had less stress. So my advice:</li></ul><blockquote>Set 1 simple major quarterly theme for the company. Set max 3 goals for each department: first one should be directly connected with the main theme.</blockquote><ul><li><strong>Communication</strong>. Slack is awesome and awful tool. It allows us to work faster on simpler tasks, but it slows us down when we need to be focused on something that takes several hours to finish. I’ve cleaned up my slack channels recently and it definitely helped me to be more productive and happier.</li></ul><h3>Pavel Averin on Twitter</h3><p>Cleaned up my @SlackHQ channels. Immediately feel less stressed and more productive: - left the channels I don&#39;t often use - cleaned the sidebar: show only unread channels and sort them scientifically - press shift+esc at the end of the day What are your best tips?</p><ul><li><strong>Books</strong>. I have a plan to read 12 books this year. The problem occurred when I started 1 book, then another and 2 more after that without finishing the single one. I’m not against reading multiple books at once but there should be a limit. Just like in <a href="https://en.m.wikipedia.org/wiki/Kanban">Kanban</a> when there is a limit of work in progress to make sure it’s actually moving forward. <strong>My limit is max 2 books at once</strong>.</li><li><strong>Sport</strong>. Running is a big part of my life. My parents met at <a href="https://en.wikipedia.org/wiki/Orienteering">orienteering</a> sport club when they were in high school. Nowadays, I ran half-marathons and marathons. But also I enjoy going to the gym or doing some other physical activities. To keep focus in sport I do following: pick only one must-have marathon or half-marathon I’d like to run this year and set the number of kilometers I’d like to hit (today’s result 605,8/1000km). Then I pick at least 3 days per week for sport and start moving forward to those goals.</li><li><strong>Personal projects</strong>. Full-time job is never enough for me. I like to explore new ideas, try new challenges and push myself forward. The problem occurs when I start picking too much initiatives and projects. Then usually I don’t finish any of them and become miserable. The clue is to stick with one project for a while, deliver some work, evaluate the result and if it doesn’t make sense to continue — resign.</li></ul><blockquote>Limit number of personal projects to one. Set the similar approach as in work initiatives. Set the minimum and maximum amount of hours you’d like to spend on this project weekly. Track progress and don’t be afraid to resign.</blockquote><ul><li><strong>Rest</strong>. It’s ok if you want to spend some time on doing nothing. Actually, your brain needs to have <a href="https://www.health.harvard.edu/blog/secret-to-brain-success-intelligent-cognitive-rest-2017050411705">some cognitive rest to be productive</a>. That’s why you have to reserve some time on doing nothing.</li></ul><p>Thanks for reading! Get some rest. Or don’t. Do whatever makes you happy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54e879851c8a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/how-to-build-products-and-teams/focus-slow-down-to-speed-up-54e879851c8a">Focus. Slow down to speed up</a> was originally published in <a href="https://medium.com/how-to-build-products-and-teams">How to build products and teams</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Don’t forget about your health. Your Process Health]]></title>
            <link>https://medium.com/how-to-build-products-and-teams/dont-forget-about-your-health-your-process-health-ebcedd3a4581?source=rss-a06b14ffee99------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebcedd3a4581</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[process]]></category>
            <dc:creator><![CDATA[Pavel Averin]]></dc:creator>
            <pubDate>Mon, 23 Apr 2018 20:52:15 GMT</pubDate>
            <atom:updated>2018-04-23T20:52:15.624Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dOrzaITpJquWHJr9Z6UjMw.jpeg" /></figure><p>Let’s talk about health. But not about your physical health — your process health.</p><p>Didn’t you know that each process has it’s own health? Have you noticed that sometimes you have some process or flow but you don’t get the result you want?</p><p>Maybe your process is sick?</p><p>If you feel that something is wrong with it, you don’t have to go to the doctor. You need to change your process lifestyle so it will live longer and happier life.</p><h4><strong>Eat healthy. F</strong>eed your process with a good quality data</h4><p>We (people) need to have a well balanced diet with the right amount of carbs, proteins and fats. It’s important for our health to get still water, fresh vegetables and fruits. Our processes are not so different from us.</p><p>So why we feed it with a poor input data and wait for the awesome outcome?</p><ul><li><strong>Pick the right nutrition.</strong> Identify which data are vital for your process. If needed, deconstruct it to nutrients (like proteins, carbs and fats) and define which ones bring us the</li><li><strong>Choose the right portion</strong>. You don’t need all the data. You only need the right amount of data to keep the process efficient. Process will chunk if there’s gonna be too much data and it will starve if there is lack of it.</li><li><strong>Eat often. </strong>Each process will require some time to digest the data it got and produce the outcome it was created for. Now you know which portion of data is enough for efficient process cycle. Determine the best time for processing data and stick with the schedule.</li></ul><h4><strong>Exercise. Make the process move</strong></h4><p>The good food is not enough to be healthy. We need to move. We need to be active and feel physical pressure from time to time to become faster, better and stronger. As you might guess, the same is with processes.</p><ul><li><strong>Set the goal.</strong> Each runner has her own record she strives to beat on the next marathon. So your process should also has the goal. Without the goal you won’t be motivated enough to get better results. Each process should have the ambitious KPI it aims to achieve. And don’t forget about the timeframe. Each race has it’s date.</li><li><strong>Train</strong>. Now that you have the goal it’s time to work hard to get there. Like runners have their marathon preparation plan, you should have a plan how to get to your goal. If you don’t have one, it’s ok. Experiment! Set the hypothesis, change the process and monitor how the outcome changes. Be consistent and work hard to get to the goal!</li><li><strong>Ready, steady, go!</strong> While you train don’t forget about the main race and the goal you want to achieve. Don’t loose your focus, be prepared for a date you’ve set and show the best possible result!</li></ul><h4><strong>Sleep well. Give it some time to recover</strong></h4><p>The third element of a healthy life is a rest. You need to take some time to recover. During the physical activity we destroy our muscles, during the sleep we build them. Like after a marathon your process need to have a good rest to become stronger.</p><ul><li><strong>Give it some time. </strong>After you achieved a major goal and you’re sure that healthy food and exercise worked, take a break. Don’t be too confident after a big win that you can be even better the next day. Give it some time to stabilize and get used to it’s new strength.</li><li><strong>But not too much. </strong>Don’t sleep too much or you wouldn’t notice you get back to the point you started. After you recovered it’s time to set the next big goal and start training!</li></ul><p>Hope those advices help you to keep your processes healthy and happy.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebcedd3a4581" width="1" height="1" alt=""><hr><p><a href="https://medium.com/how-to-build-products-and-teams/dont-forget-about-your-health-your-process-health-ebcedd3a4581">Don’t forget about your health. Your Process Health</a> was originally published in <a href="https://medium.com/how-to-build-products-and-teams">How to build products and teams</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Capacity Management or how to bring the right people to the right place]]></title>
            <link>https://medium.com/how-to-build-products-and-teams/capacity-management-or-how-to-bring-the-right-people-to-the-right-place-92290af7a574?source=rss-a06b14ffee99------2</link>
            <guid isPermaLink="false">https://medium.com/p/92290af7a574</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[talent-management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Pavel Averin]]></dc:creator>
            <pubDate>Sat, 21 Apr 2018 11:47:59 GMT</pubDate>
            <atom:updated>2018-04-30T19:52:38.887Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Oiq4J-_B3iQOHLgtEq7agg.jpeg" /></figure><p>A month ago, I changed my position in the company and became the leader of the PMO (project, portfolio or program management office — pick the one you like). Our main goal is to make things work efficiently. We all know it’s hard.</p><p>Let me share the approach I took to improve one of the biggest and hardest processes — Capacity Management (scheduling or talent management). Sometimes it is referred to as resource management or planning, but I don’t like those terms. In my case, we work with people, not resources (things). They have skills, dreams, feelings, and the capacity to do an awesome job. Our goal is to make sure that we have the person with the right skills in the right place at the right time. Unfortunately, I can’t tell you that we are always able to satisfy all of those parameters together, but we are trying to create a process which will maximise our outcomes and help us to get where we want.</p><p>I borrowed the concept of 4 pillars of Capacity Management from Jerry Manas. I divided the problems and set the goals to the team according to the following 4 principles: visibility, prioritisation, optimisation, and integration. Let me quickly walk you through each of them.</p><h3>Visibility</h3><p>In order to manage the capacity efficiently we must see the big picture: the demand and supply. If we don’t know what’s going on on the demand side, we can’t make strategic talent allocation and predictions. We need to understand how many people and which skills we need to have available to make the job done.</p><p>The goes for the supply side. How can we predict the expectations of our clients and users if we don’t know who’s available today and who will be available in the nearest or even farthest future?</p><p>Just try to remember how often you’ve experienced the following situations:</p><ul><li>Someone from sales comes to you and says that they’re closing a very important deal and they need to have the best people possible ASAP!</li><li>You hired lots of new people but the project ended unexpectedly. You have a bunch of people without tasks and you need to figure out what to do with them.</li></ul><p>Before we start fixing the problem, we need to make sure everybody sees it. We started with making the process as transparent and visible to everyone as possible. We work with sales and try to get the best guesses about the dates and the skills required for the project. We work with active projects on clarifying the completion dates to make sure we know when the people will be available for the next project. We work with people to understand which skills they have and in which direction they want to develop so that we could help them to get closer to their dream with every next project.</p><p>A few tips for improving the visibility:</p><ul><li><strong>Map your process</strong>. You need to know what the demand and supply are in your case. You also need to know who who’s working on what and what the parameters needed to run the business are.</li><li><strong>Put the data in the system, make it transparent, and explain how to use it</strong>. You can start with a spreadsheet and put the demand on one side with parameters such as the required start date and skills. Then you put the supply with the same parameters on the other side. As the number of requests starts to increase, you might want to think about some automated software for doing this.</li><li><strong>Work on quality and execution</strong>. Without quality data your system is worth nothing. If you don’t trust our system you won’t use it. Make sure you explain the importance of data quality to your team.</li></ul><h3>Prioritisation</h3><p>Ok, now you have the map of the supply and demand and you can start working on improving efficiency. We started with implementing the segmentation of our requests — the categories which show us what we can expect from those requests and which approach we should take for each category. Then, we took a step further and implemented a score which takes into account a number of parameters — it helps us to prioritise requests.</p><ul><li><strong>Create a system which works for you</strong>. It could be a score that will show you which requests are more important than the others. Think what brings the most value to your business and try to deconstruct it into parameters: is it a particular type of clients? Or maybe it is one kind of technology or skills where you have the advantage on the market, and those requests should be addressed first? Combine them and create one indicator that will show you which request is the most important.</li><li><strong>Involve the stakeholders in the creation of the new system</strong>. They need to explain to you what matters to them, and you need to tell them what matters to you. You need to share the same goal, and improved visibility will help you.</li><li><strong>Iterate</strong>. Start executing using this new system. If you see some issues with the score or the indicators you’ve chosen — fix them. You’re developing a process that will maximise the outcome. It takes some time to create one.</li></ul><h3>Optimisation</h3><p>With limited capacity (and it’s always limited) we need to learn how to use it efficiently. From the business point of view, it could be some measured utilisation or other KPIs that will show you that you’re on track. We’ve built dashboards with KPIs visible to everyone so that we all know if we are closer to achieving our goals or not.</p><ul><li>Understand what efficiency means to your business. If you want to spend less and gain more — define which number will show you that you’re moving in the right direction. Collect those KPIs in one place and share it with stakeholders.</li><li>Revise the KPIs often and learn from your mistakes. If you take some actions but don’t see results, try to dig deeper and identify what’s working and what’s not.</li></ul><h3>Integration</h3><p>Everything is connected. Changes in your processes and approaches will cause changes on the other side of the company. The same applies to changes made by your stakeholders — they will affect you in one way or another.</p><ul><li>Map the dependencies. Again, just as was the case with improving the visibility, you need to have a map of stakeholders and processes.</li><li>Identify the risks. Make sure you think upfront about the potential issues and changes in the way other party’s cycle.</li><li>Communicate. Gather the stakeholders together and discuss the plan.</li></ul><p>Those are 4 main areas we’re working to improve at the moment. Will this work? We don’t know. I like to treat everything as an experiment. And even if we fail somewhere, we learn and get back to work with improvements and new ideas.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92290af7a574" width="1" height="1" alt=""><hr><p><a href="https://medium.com/how-to-build-products-and-teams/capacity-management-or-how-to-bring-the-right-people-to-the-right-place-92290af7a574">Capacity Management or how to bring the right people to the right place</a> was originally published in <a href="https://medium.com/how-to-build-products-and-teams">How to build products and teams</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple Product Backlog prioritization]]></title>
            <link>https://medium.com/how-to-build-products-and-teams/simple-product-backlog-prioritization-70c665e9fc96?source=rss-a06b14ffee99------2</link>
            <guid isPermaLink="false">https://medium.com/p/70c665e9fc96</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[product-development]]></category>
            <dc:creator><![CDATA[Pavel Averin]]></dc:creator>
            <pubDate>Sat, 13 Jan 2018 18:40:26 GMT</pubDate>
            <atom:updated>2018-01-14T13:57:39.419Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*EgUEqBQLcktB1rjNay9xBA.png" /></figure><p>Prioritization is the key to successful product management. There are lots of tools which help the team to prioritize the tasks and keep the track on progress. Remember, it doesn’t matter which tool you’re using if you can’t set the right priorities.</p><p>A while ago Intercom wrote about <a href="https://blog.intercom.com/rice-simple-prioritization-for-product-managers/">simple prioritization for product managers</a>.</p><p>I’d like to share with you a different approach for backlog prioritization. This way of defining priorities was described by Mike Cohn in his book <a href="https://www.amazon.com/Agile-Estimating-Planning-Mike-Cohn/dp/0131479415">Agile Estimating and Planning</a>.</p><blockquote>It doesn’t matter which tool you’re using if you can’t set the right priorities.</blockquote><p>What we’ll take into account:</p><h3><strong>Value</strong></h3><p>The business value of having the features. How much money we’ll make or save by having this feature. Sometimes it’s hard to predict or estimate the exact amount of gains or savings which we’ll have after feature implementation. Just give your best guess, this will be enough for setting priorities.</p><h3><strong>Cost</strong></h3><p>The cost of developing and supporting the new features:</p><ul><li>Estimated amount of billable hours, days or weeks</li><li>Costs of licenses, tools, anything that will generate costs during the implementation</li><li>Investments in infrastructure or maintenance</li></ul><h3><strong>Risk</strong></h3><p>The amount of risk we might face during the implementation.</p><ul><li>schedule risk (“We might not be done by October”)</li><li>cost risk (“We might not be able to buy hardware for the right price”)</li><li>functionality risks (“We might not be able to get that to work”)</li></ul><p>But also it might be considered as the amount of risk removed by developing the features. Imagine we’re starting to use new technology and there is a risk that we might not meet our deadline. But if working with this yet unknown technology at the moment will bring more value after finishing implementation and reduce the risk of future failures, it worth trying to go with it earlier.</p><h3><strong>Gained Knowledge</strong></h3><p>The amount and significance of learning and new knowledge created by developing the features.</p><ul><li>Product knowledge. After implementation of this feature we’ll know <strong><em>what to build and not to build next</em></strong>. This is very important for future decisions.</li><li>Project knowledge. The knowledge about the processes and techniques. After working on current feature we’ll know <strong><em>how to build the next ones</em></strong>.</li></ul><h3><strong>Simple Backlog Prioritizer</strong></h3><p>We prepared a <a href="https://docs.google.com/spreadsheets/d/1Elv4bfWWcApQcCUQ9Y3fI6xz1wSb5aVpnAzLmFLuIOM/edit?usp=sharing">table</a> which will help you to prioritize the features, projects or epics in your product backlog. Feel free to copy it and modify on your own use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/0*Ts7vy1aw38TBFbwP." /></figure><p>How to use this Simple Backlog Prioritizer:</p><ul><li>List all your features/larger projects</li><li>Calculate the value. It could be put in money, or just in relative equivalent like on example</li><li>Estimate the cost. Again you shouldn’t be too precise in those estimates.</li><li>Evaluate the risk. You could just use a scale 1–10.</li><li>The table will automatically put the feature with the best Value/Cost rate at the top. This is the feature you want to work on! The one which brings more value with less investment in implementation.</li></ul><p>If you have features with similar Value/Cost ratio go to Value &amp; Risk Rank.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*G82kf0YG1o8UbcfaXiPsEA.png" /></figure><p>The smaller the number in the column the higher the risk and value combined. Based on your risk tolerance at the moment you might be interested in starting developing the riskier feature which might bring more value to the users and product itself.</p><p><em>Thank you for reading!</em></p><p><em>If you liked it and want to know about building teams and awesome products please subscribe on </em><a href="https://medium.com/how-to-build-products-and-teams"><em>Medium</em></a><em>, follow or @</em><a href="https://twitter.com/htb_products"><em>htb_products</em></a><em> or try our </em><a href="http://m.me/htbproducts"><em>chatbot</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70c665e9fc96" width="1" height="1" alt=""><hr><p><a href="https://medium.com/how-to-build-products-and-teams/simple-product-backlog-prioritization-70c665e9fc96">Simple Product Backlog prioritization</a> was originally published in <a href="https://medium.com/how-to-build-products-and-teams">How to build products and teams</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Effective Teamwork starts with shared Terms, Rules and Goals]]></title>
            <link>https://medium.com/how-to-build-products-and-teams/effective-teamwork-starts-with-shared-terms-rules-and-goals-e370a9e8cc28?source=rss-a06b14ffee99------2</link>
            <guid isPermaLink="false">https://medium.com/p/e370a9e8cc28</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Pavel Averin]]></dc:creator>
            <pubDate>Mon, 01 Jan 2018 11:01:02 GMT</pubDate>
            <atom:updated>2018-01-14T13:59:35.779Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U-xzn_S4XcTcQZR2FX4hdw.jpeg" /></figure><p><strong>Understanding in the first place<br></strong>Recently I’ve read <a href="https://medium.com/@hellostanley/design-doesnt-scale-4d81e12cbc3e#.rkp8qq3cs">this amazing article</a> about design adventures in Spotify and I started to think about how important are shared principles, vocabulary, goals and terms to the team. As a project manager, I’m working on different web and mobile projects at the same time. I truly believe that success or failure of each project depends on the fact if all stakeholders are on the same page.</p><p>Shared concepts will save you time, money and nerve cells. It is essential to take care of creating common concepts before investing in actions.</p><p><strong>Why it’s important<br></strong>Imagine you’re the part of the football team. Your team is going to have a very important match (world cup final for example). And you completely don’t know the rules…</p><p>You have no idea what you suppose to do, where to run and why everybody is screaming on you. And now imagine if everybody in the team forgot the rules. It would be a real mess.</p><blockquote>You won’t win if you don’t know the rules of the game you’re playing.</blockquote><p><strong>Terms, rules and goals</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/469/1*n4RLBn3OuSqCpXvk4y3Clw.png" /></figure><p>So it’s getting obvious that you need to understand terms (<a href="https://en.wikipedia.org/wiki/Passing_(association_football)">pass</a>, <a href="https://en.wikipedia.org/wiki/Goal_(sport)#Association_football">goal</a>, <a href="https://en.wikipedia.org/wiki/Offside_(association_football)">offside</a>), rules (<a href="https://en.wikipedia.org/wiki/Laws_of_the_Game_(association_football)">each team consists of a maximum of eleven players</a>) and goals (you need to have more points than the opposite team) to help your team win the game (or at least not suck so much).</p><p>Terms are important because they help you to define the shared vocabulary between team members. Terms help us to understand what we are doing. Terms can take different forms:</p><ul><li>Names of the processes and departments in your company</li><li>Design guidelines for the product</li><li>Names of the components, classes or methods in the code</li><li>Tables and values in the database</li></ul><p>Rules are actions which you should or shouldn’t perform. Those actions could be required, permitted or forbidden. Rules help us to Define how we’re gonna do it. Examples of the rules:</p><ul><li>Workflow in the project</li><li>Deployment or QA checklist</li><li>Weekly, monthly or quarterly procedures (reviews, planning, etc.)</li></ul><p>Goals help us to understand in which direction we should follow and what we want to achieve in the end. Goals help us to answer the question why we’re doing it. Goals examples:</p><ul><li>Sprint/release goals</li><li>Product requirements</li><li>Revenue/sales targets</li><li>Company’s <a href="https://sliwinski.com/v2mom/">v2mom</a></li></ul><p>How to create shared concepts<br>Below you can find some recommendations of how to create and maintain the shared concepts in your teams:</p><ul><li>Start with basic terms — you need to agree on the main subjects of your work and main definition.</li><li>Make sure everyone has an access to information. Use team collaboration tools to create a knowledge base. I really into <a href="https://www.atlassian.com/software/confluence">Confluence</a>, but you just can start with google docs.</li><li>You won’t have a lot of rules in the beginning, but they’ll appear naturally because of mistakes and obstacles. Make sure you documenting them.</li><li>Set the clear goals, make sure everybody knows and understands them.</li><li>Document changes. Irrelevant Terms, rules or goals could cause a lot of problems. Make sure everybody is updated about changes.</li></ul><p><em>Thank you for reading!</em></p><p><em>If you liked it and want to know about building teams and awesome products please subscribe on </em><a href="https://medium.com/how-to-build-products-and-teams"><em>Medium</em></a><em> or follow or @</em><a href="https://twitter.com/htb_products"><em>htb_products</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e370a9e8cc28" width="1" height="1" alt=""><hr><p><a href="https://medium.com/how-to-build-products-and-teams/effective-teamwork-starts-with-shared-terms-rules-and-goals-e370a9e8cc28">Effective Teamwork starts with shared Terms, Rules and Goals</a> was originally published in <a href="https://medium.com/how-to-build-products-and-teams">How to build products and teams</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leadership and simple rules in tough times]]></title>
            <link>https://medium.com/how-to-build-products-and-teams/leadership-and-simple-rules-in-tough-times-d15b31336611?source=rss-a06b14ffee99------2</link>
            <guid isPermaLink="false">https://medium.com/p/d15b31336611</guid>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Pavel Averin]]></dc:creator>
            <pubDate>Sat, 30 Dec 2017 19:38:16 GMT</pubDate>
            <atom:updated>2018-01-14T14:00:29.435Z</atom:updated>
            <content:encoded><![CDATA[<p>Today we’ll talk about leadership. If you’re building product or team you have to obtain some leadership skills to make things work. You can be an expert in some field and could do a wonderful job in your area but you’ll never achieve the highest results by yourself. The team can do much more than an individual oneself.</p><p>Everything is ok on the uphill — when there is a clear goal, enough time and resources and everybody is happy with what they’re doing. But suddenly your team meets the downhill. It’s when you’re suddenly getting a deadline from nowhere, team lacks of resources or skills and basically everything is starting to fall apart. Then<strong> you have to become a leader</strong> and help your team to survive this tough time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*toe240WYzrE7hD6t8lTmwA.png" /></figure><p>What you need to do as a leader when you face downhill:</p><h3><strong>Create clarity</strong></h3><p>You don’t have to explain your team what to do. You need to explain them why they’re doing it and which problems team is trying to solve. Why solving those problems is important and which value it will bring to the users, stakeholders, team itself.</p><p>Examples of questions which will help to create clarity:</p><ul><li>What is our main goal and why? (keep asking again and again until you’ll get to the core, use <a href="https://en.wikipedia.org/wiki/5_Whys">5 whys</a>)</li><li>What is the biggest challenge you are facing right now? Why we’re facing it? Why we can’t solve it?</li><li>Where we can go on a compromise? What is most important for us: quality, budget or time?</li></ul><h3><strong>Set simple rules</strong></h3><p>Ok, we have a clear goal and maybe we have lots of propositions for solutions from the team. But still we have some constraints or obstacles (it’s a downhill). Simple rules will help you to solve complex problems. Read this <a href="https://hbr.org/2012/09/simple-rules-for-a-complex-world">HBR guide</a> on setting simple rules.</p><p>Examples of simple rules:</p><ul><li>Our main goal is <strong><em>X</em></strong>, whatever we do — it should move us further to <strong><em>X</em></strong>.</li><li>We fight procrastination (<em>put here any of the previous mistakes or reasons of problems you defined using previous questions).</em></li><li>We care mostly about <em>Quality</em> (<em>time, budget — choose based on the previous questions</em>).</li></ul><h3><strong>Provide discipline and ownership</strong></h3><p>You’ve set the goal and rules, now it’s time for execution. Success of your team depends on how disciplined you are. As a leader of the team you’re responsible for making sure they follow those rules and if rules still make sense. Listen to<a href="https://en.wikipedia.org/wiki/Jocko_Willink"> Jocko Wilnik </a>on <a href="https://tim.blog/2017/10/20/discipline-equals">Tim Feriss new podcast</a>, he’ll tell you about discipline, execution, problem solving and ownership.</p><p>Quick advices on discipline:</p><ul><li>Create common understanding of <a href="https://medium.com/how-to-build-products-and-teams/effective-teamwork-starts-with-shared-terms-rules-and-goals-e370a9e8cc28">terms, procedures and measures team is using.</a></li><li>Lead by example — make sure you follow the rules you established.</li><li>Build responsibility and ownership. Define the roles, make sure everybody knows who is responsible for what. Remember that you’re responsible for the whole team.</li></ul><p>That’s all you need to lead your team through tough times.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d15b31336611" width="1" height="1" alt=""><hr><p><a href="https://medium.com/how-to-build-products-and-teams/leadership-and-simple-rules-in-tough-times-d15b31336611">Leadership and simple rules in tough times</a> was originally published in <a href="https://medium.com/how-to-build-products-and-teams">How to build products and teams</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Best articles to read if you’re starting with UX design]]></title>
            <link>https://averpavel.medium.com/best-articles-to-read-if-youre-starting-with-ux-design-a493e4679a29?source=rss-a06b14ffee99------2</link>
            <guid isPermaLink="false">https://medium.com/p/a493e4679a29</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Pavel Averin]]></dc:creator>
            <pubDate>Mon, 27 Feb 2017 07:33:41 GMT</pubDate>
            <atom:updated>2017-02-27T18:10:48.492Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iOqfOXNvngmp7Z7mP4nlgA.jpeg" /></figure><p>I’m learning UX design.</p><p>Why?</p><p>Because User Experience is everything and everywhere.</p><p>It doesn’t matter if you’re working on the product as a designer, developer, product manager or tester. It even doesn’t matter if you’re not working on the product development — you’re definitely using products.</p><p>Everything is a product. Each app, site, service you use is a product. And feelings you perceive before, during and after your interaction with the product is your own User Experience.</p><p>That’s why I think it’s important to study UX. Just to be better in everything I do.</p><p>I want to share with you articles and publications which I found useful and interesting if you start learning design.</p><p>Please share your favorite UX design resources in comments.</p><h3>Medium</h3><p>You’ll find a lot of design-related content on Medium. You need just start exploring. Below you’ll find two publications from where you can start your medium surfing.</p><p><a href="https://uxdesign.cc/"><strong>Uxdesign.cc</strong></a></p><p>UX bear is a great collection of articles about User Experience and Product Design. There you’ll find a great advices on what current design trends are, which books to read and which designers to follow. I think it’s a great place to start your adventure with UX design.</p><p>Some of the articles you might be interested in:</p><ul><li><a href="https://uxdesign.cc/ux-trends-2017-46a63399e3d2#.oqhv9lev3">The state of UX in 2017</a> — find out the predictions for 2017 from the professionals</li></ul><p>Those are interesting lists if you’re looking for design books or articles to read:</p><ul><li><a href="https://medium.com/@uxdesigncc/ux-books-fundamental-reading-list-8ba3f36f6bd8#.7ep5w3twd">UX books fundamental reading list</a></li><li><a href="https://uxdesign.cc/the-best-medium-publications-from-design-teams-to-follow-fc609bdd49d2#.kxniagyv7">The best medium publications from design teams to follow</a></li><li><a href="https://uxdesign.cc/the-best-ux-design-authors-to-follow-on-medium-1f791807b08a#.h2m4rq9g9">The best UX design authors to follow on Medium</a></li></ul><p><a href="https://uxplanet.org/"><strong>Uxplanet.org</strong></a></p><p>Another interesting Medium publication which is full of practical advices. This publication contains a lot of articles by <a href="https://uxplanet.org/@101">Nick Babich</a>. He has a talent to gather information about latest web and mobile design trends and best practices and present it in the interesting and easy-to-understand manner.</p><p>Where to start:</p><ul><li><a href="https://uxplanet.org/mobile-design-best-practices-2d16d37ecfe#.7y5kaqbcy">Mobile design best practices</a></li><li><a href="https://uxplanet.org/best-practices-for-onboarding-92f3a9f0b21a#.q29vz7o2g">Best practices for onboarding</a></li><li><a href="https://uxplanet.org/functional-minimalism-for-web-design-4290722cddbd#.3flku6s0h">Functional minimalism for web design</a></li></ul><h3>Other online resources</h3><ul><li><a href="https://www.smashingmagazine.com/">Smashing Magazine</a> — UX, Design, Graphics, Coding. You’ll find there large amount of useful articles and Ebooks.</li><li><a href="https://www.uxpin.com/knowledge.html">Free ebooks from UXPin</a> — Enormous library. Years of experience. Trends, practices and processes. Free.</li><li><a href="https://dribbble.com/">Dribble</a> and <a href="https://www.behance.net/">Behance</a> — Learn from the whole world. Get inspired by other designers and start create by yourself.</li><li><a href="https://material.io/guidelines/#introduction-goals">Google material design guidelines</a> — get deeper understanding on Google’s Material design.</li></ul><p><em>Thank you for reading!</em></p><p><em>If you liked it please give me a ♡, read me on </em><a href="https://medium.com/@Averpavel"><em>medium</em></a><em> or follow on twitter </em><a href="https://twitter.com/Averpavel"><em>@averpavel</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a493e4679a29" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>