<?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 Aleks Ritov on Medium]]></title>
        <description><![CDATA[Stories by Aleks Ritov on Medium]]></description>
        <link>https://medium.com/@aleksritov?source=rss-372700c2dc4a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*5GNp9PNpGDnDgJhT_F7E8g.jpeg</url>
            <title>Stories by Aleks Ritov on Medium</title>
            <link>https://medium.com/@aleksritov?source=rss-372700c2dc4a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:24:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aleksritov/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[30. Do not postpone a release]]></title>
            <link>https://medium.com/@aleksritov/30-do-not-postpone-a-release-40ed9ea4ac28?source=rss-372700c2dc4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/40ed9ea4ac28</guid>
            <category><![CDATA[releases]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Aleks Ritov]]></dc:creator>
            <pubDate>Tue, 26 May 2020 10:12:26 GMT</pubDate>
            <atom:updated>2020-05-26T10:12:26.069Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CavtCW4VAyG43UkChdqUHw.png" /></figure><p>When launching this series of Tales, I decided to publish a new Tale every Tuesday and Thursday. Usually I write them well in advance, but the last couple of days I spent in bed with fever, feeling totally exhausted. My mind was empty and the only thing I could think about was my illness. Here’s why I decided to write about not feeling great. And how this is by no means a reason to postpone a release.</p><p>My team and I demonstrate our results to the company on a regular basis. We call it a ‘demo’. The demo is a regular thing and we never move its dates. The new functionality that we’re demonstrating has to be in production, no testing servers are allowed. No one is going to punish the team if they have nothing to show during the demo, but we always try to get as much done as possible. If we feel we’re not going to meet the deadline, we think about ways to simplify the functionality to make sure we release it before the demo. Postponing a release is the worst thing that can happen in software development.</p><p><strong>PREV: </strong><a href="https://medium.com/@aleksritov/29-heres-why-you-need-a-technical-backlog-459a6a01086c">29. Here’s why you need a technical backlog</a></p><blockquote>Tales of a Product Owner: concentrated wisdom about project management, team creation and UX.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40ed9ea4ac28" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[29. Here’s why you need a technical backlog]]></title>
            <link>https://medium.productcoalition.com/29-heres-why-you-need-a-technical-backlog-459a6a01086c?source=rss-372700c2dc4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/459a6a01086c</guid>
            <category><![CDATA[it-development]]></category>
            <category><![CDATA[technical-debt]]></category>
            <dc:creator><![CDATA[Aleks Ritov]]></dc:creator>
            <pubDate>Tue, 26 May 2020 10:09:31 GMT</pubDate>
            <atom:updated>2020-05-27T14:00:14.481Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6WKawHnCRpQd7grGAXfINQ.png" /></figure><p>Product owners and their development teams always face the same problem: the product owner advocates for new features, while the developers demand time for refactoring. The technical part often gets neglected, causing technical debt to pile up. The problem, however, is not in the harsh reality of the business world, but in the programmers’ inability to manage the technical backlog properly. Their backlog usually consists of tasks like “To refactor a controller.” The value of such tasks is not obvious to the product owner. Here are the key principles of turning scrappy tasks into a proper backlog:</p><ol><li><strong>VALUE.</strong> Tasks need to be organized into epics; each epic must contain a clear, valuable action. Here’s an example of a bad epic: “Refactor the project”, and a good one: “Improve the building speed from 5 minutes to 20 seconds.” Another bad example: “Rewrite JS”. And a good one: “Improve the speed of new report development from 2 weeks to 1 day.”</li><li><strong>EVALUATION.</strong> Each separate task and each epic in the technical backlog need to be evaluated using the same units as in your product backlog. Store points, S/M/L — anything works, just make sure it gets evaluated.</li><li><strong>REGULARITY. </strong>Managing a technical backlog needs to become a regular thing in your calendar. In our team, we hold 1.5-hour backlog grooming sessions twice a week.</li></ol><p>Following these principles will make it easier for the development team to communicate with their product owner and set correct technical tasks in each sprint.</p><p><strong>NEXT: </strong><a href="https://medium.com/@aleksritov/30-do-not-postpone-a-release-40ed9ea4ac28">30. Do not postpone a release</a></p><p><strong>PREV: </strong><a href="https://productcoalition.com/28-technical-debt-and-how-to-handle-it-71f6db5a300b">28. Technical debt and how to handle it</a></p><blockquote>Tales of a Product Owner: concentrated wisdom about project management, team creation and UX.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=459a6a01086c" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/29-heres-why-you-need-a-technical-backlog-459a6a01086c">29. Here’s why you need a technical backlog</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[28. Technical debt and how to handle it]]></title>
            <link>https://medium.productcoalition.com/28-technical-debt-and-how-to-handle-it-71f6db5a300b?source=rss-372700c2dc4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/71f6db5a300b</guid>
            <category><![CDATA[technical-debt]]></category>
            <dc:creator><![CDATA[Aleks Ritov]]></dc:creator>
            <pubDate>Wed, 20 May 2020 17:10:52 GMT</pubDate>
            <atom:updated>2020-05-26T10:09:53.296Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U_ub8VO1Lmc3_uFn4IF5Cw.png" /></figure><p>You most probably know how credit cards work. You take out a loan from a bank for whatever reason and you are given a grace period of a month or two to pay back the money you owe. If you fail to pay back within the grace period, you will be charged interest, which increases like a snowball as it is rolled on.</p><p>It’s the same with technical debt. You’re rushing to release new product features, while taking out a loan from your “future self”. It’s OK at the beginning, but after a while, it starts bothering you. Eventually, it accumulates to the point where it leads to bankruptcy. To know how to deal with it, you need to understand the basics of loans.</p><ol><li>Evaluate the loan amount. This is the most difficult part. I’ll talk about it in my next Tale.</li><li>Put together a payment schedule. Payments need to be regular and equal.</li><li>If the payment is overdue, have a serious conversation about it with your team. Just like banks do.</li><li>If your team misses the payment deadline several times in a row, call debt collectors. In our case, this means arranging for external team management.</li></ol><p>And remember that loans are easy to take out, but not so easy to pay back.</p><p><strong>NEXT: </strong><a href="https://medium.com/@aleksritov/29-heres-why-you-need-a-technical-backlog-459a6a01086c">29. Here’s why you need a technical backlog</a></p><p><strong>PREV: </strong><a href="https://medium.com/@aleksritov/27-technical-debt-and-who-is-to-blame-f5707152cbb">27. Technical debt and who is to blame</a></p><blockquote>Tales of a Product Owner: concentrated wisdom about project management, team creation and UX.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71f6db5a300b" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/28-technical-debt-and-how-to-handle-it-71f6db5a300b">28. Technical debt and how to handle it</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[27. Technical debt and who is to blame]]></title>
            <link>https://medium.com/@aleksritov/27-technical-debt-and-who-is-to-blame-f5707152cbb?source=rss-372700c2dc4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5707152cbb</guid>
            <category><![CDATA[technical-debt]]></category>
            <dc:creator><![CDATA[Aleks Ritov]]></dc:creator>
            <pubDate>Wed, 20 May 2020 16:45:31 GMT</pubDate>
            <atom:updated>2020-05-21T09:51:55.414Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*krSWZvt3dhduVpmCGUFykg.png" /></figure><p>Some years ago, my team and I accumulated a huge technical debt, which has completely paralyzed the development of our product. Any change to the product was taking weeks to implement and resulted in multiple errors. The team lost motivation, conflicts began to arise. The retrospective meetings weren’t helping either. The product development almost stopped, and business representatives were getting more and more concerned about the situation. The question arose: Who is to blame? Scrum says that as a Product Owner, I am responsible for the product’s success, while the responsibility for technical implementation, including technical debt, falls on the team’s shoulders.</p><p>However, I see things differently. A Product Owner has influence over everything that affects the product. I kept nagging my team that it was time to address the technical debt and architecture, but it never went beyond mere words. It was my responsibility to foresee the breakdown and take action. What sort of action is something I’m going to talk about in my next Tale. The key takeaway here is that the product manager is responsible for everything, even for things that are outside the scope of their responsibilities.</p><p><strong>NEXT: </strong><a href="https://productcoalition.com/28-technical-debt-and-how-to-handle-it-71f6db5a300b">28. Technical debt and how to handle it</a></p><p><strong>PREV: </strong><a href="https://medium.com/@aleksritov/26-theory-should-not-outpace-practice-e0fe81548d7e">26. Theory should not outpace practice</a></p><blockquote>Tales of a Product Owner: concentrated wisdom about project management, team creation and UX.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5707152cbb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[26. Theory should not outpace practice]]></title>
            <link>https://medium.com/@aleksritov/26-theory-should-not-outpace-practice-e0fe81548d7e?source=rss-372700c2dc4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0fe81548d7e</guid>
            <category><![CDATA[theory-and-practice]]></category>
            <dc:creator><![CDATA[Aleks Ritov]]></dc:creator>
            <pubDate>Mon, 18 May 2020 12:36:05 GMT</pubDate>
            <atom:updated>2020-05-20T16:46:09.557Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DuV-DRTXdqRyWLUhLtlgBQ.png" /></figure><p>My relative used to work for a community centre during the Soviet times. Most of her working hours she spent drinking tea in the reception area. Once she surprised me with a quote from a gun manual, which she knew by heart: “The trigger pushes the sear bar of the lock up until the sear pawl disengages from the full-cock notch and allows the tumbler and hammer to rotate forward, firing the gun. She told me that every year she had to pass the firearm proficiency exam. I was shocked and asked how often she gets to use a fire gun. She laughed and said she’d never even held it in her hands in her entire life.</p><p>There are so many stories out there when people pass a proficiency test, but haven’t really got a clue about the subject they’re studying. In Russian schools, for example, children learn the tenses in English language, but even those with the best grades can barely speak conversational English. A product manager is a very popular job nowadays, with so many educational articles, webinars, meetups and conferences about how to become a great product manager. Learning is no doubt important, but make sure that your theoretical knowledge does not outpace practical skills by a long shot.</p><p><strong>NEXT: </strong><a href="https://medium.com/@aleksritov/27-technical-debt-and-who-is-to-blame-f5707152cbb">27. Technical debt and who is to blame</a></p><p><strong>PREV: </strong><a href="https://medium.com/@aleksritov/25-learn-how-to-fire-people-2a885be0d961">25. Learn how to fire people</a></p><blockquote>Tales of a Product Owner: concentrated wisdom about project management, team creation and UX.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0fe81548d7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[25. Learn how to fire people]]></title>
            <link>https://medium.productcoalition.com/25-learn-how-to-fire-people-2a885be0d961?source=rss-372700c2dc4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a885be0d961</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[hr-software]]></category>
            <dc:creator><![CDATA[Aleks Ritov]]></dc:creator>
            <pubDate>Mon, 18 May 2020 12:33:59 GMT</pubDate>
            <atom:updated>2020-05-18T21:31:17.529Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nexrd1gGdsDhjLGqp1byWA.png" /></figure><p>At SEMrush, the development teams do all the hiring and firing themselves. Over the past years, I have had the pleasure of working with two teams. One of them was good at firing and lived a happy life. The other one wasn’t and they experienced lots of technical and personal issues. Bad employees paralyze work. They write a bad code, which remains a real pain in the neck even after they leave. They make the team’s existence unbearable. Sometimes, it takes firing one person to save the entire team and the product.</p><p>People are afraid of firing their colleagues: “But we hung out together and played table soccer at lunch”. In this respect, it is more difficult for us than for companies where the ‘bad manager’ does the evil job of firing. I try to encourage my team by telling them that firing is based on the principle of free will (in Russian language, for example, the words “fire” and “will” are related.) A fired programmer is very unlikely to end up on the street begging for money: they’ll quickly find a new job and live happily ever after. Don’t be afraid of firing. And remember that hesitating can cost you dearly.</p><p><strong>NEXT: </strong>26. <a href="https://medium.com/@aleksritov/26-theory-should-not-outpace-practice-e0fe81548d7e">Theory should not outpace practice</a></p><p><strong>PREV: </strong><a href="https://productcoalition.com/24-hiring-people-is-a-basic-skill-e5557a905d45">24. Hiring people is a basic skill</a></p><blockquote>Tales of a Product Owner: concentrated wisdom about project management, team creation and UX.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a885be0d961" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/25-learn-how-to-fire-people-2a885be0d961">25. Learn how to fire people</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[24. Hiring people is a basic skill]]></title>
            <link>https://medium.productcoalition.com/24-hiring-people-is-a-basic-skill-e5557a905d45?source=rss-372700c2dc4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5557a905d45</guid>
            <category><![CDATA[hiring-tips]]></category>
            <category><![CDATA[hiring-for-startup]]></category>
            <dc:creator><![CDATA[Aleks Ritov]]></dc:creator>
            <pubDate>Wed, 13 May 2020 22:05:52 GMT</pubDate>
            <atom:updated>2020-05-13T22:05:52.024Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X7w3xc_sBle_LQttO4PjiQ.png" /></figure><p>My team has recently taken over a new product. In 3 months, we had to find, hire and train a whole new team to replace us: a manager, 2 back- and 2 frontend developers, and a QA specialist. Interviewing and hiring staff is a basic skill that every member of the product team should have. Here are some of our tips:</p><ol><li>Write the job descriptions yourself. Use a simple language to portray your product. Do not trust HR to do it unless you want a standard corporate text that sounds pretty boring.</li><li>Invite for an interview only those candidates who have examples of code they’ve written (in case of devs) or a portfolio (designers). If they have nothing to show, ask them to do a test. This will help you rule out candidates with a strong CV, but whose skills are insufficient.</li><li>Specify your candidate requirements to recruiters so that your team doesn’t end up receiving tons of CVs that don’t quite match your job criteria.</li><li>Don’t attend interviews as a whole team at once. Nevertheless, all members of the team should be able to conduct interviews and evaluate both technical and soft skills. If anyone is lacking those abilities, be sure to teach them.</li><li>Know how to sell your product to the candidates — good candidates usually have several job offers on their hands. When selling your product, be honest and don’t exaggerate its value: you want your new colleague to stay in the company for years, not just a couple of months.</li></ol><p>Other than that, be patient and stay positive.</p><p><strong>NEXT: </strong>Coming soon...</p><p><strong>PREV: </strong><a href="https://medium.com/@aleksritov/23-product-manager-is-the-same-as-lead-ux-ee2209ce1866">23. Product Manager is the same as Lead UX</a></p><blockquote>Tales of a Product Owner: concentrated wisdom about project management, team creation and UX.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5557a905d45" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/24-hiring-people-is-a-basic-skill-e5557a905d45">24. Hiring people is a basic skill</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[23. Product Manager is the same as Lead UX]]></title>
            <link>https://medium.com/@aleksritov/23-product-manager-is-the-same-as-lead-ux-ee2209ce1866?source=rss-372700c2dc4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee2209ce1866</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Aleks Ritov]]></dc:creator>
            <pubDate>Wed, 13 May 2020 16:12:08 GMT</pubDate>
            <atom:updated>2020-05-15T09:38:35.126Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x3SKq-PXLUsvLRlE584H3Q.png" /></figure><p>To attend our Global Marketing Day conference, users were asked to fill in a form to register. After that, they received an email with a link to confirm the registration. However, we started receiving complaints that the registration link was broken. Both QA and the development team looked into this, but couldn’t find where the problem was. So I found all users who complained about the broken link and looked at their session logs in more detail. It turned out they all started the registration on desktop and then tried completing it on mobile. In this case, clicking on the confirmation link from an iPhone resulted in an error.</p><p>We tested the registration process separately for desktop and mobile devices, but in real life people use both at the same time. For me, situations like this are an example of real UX. They are difficult to forecast and can be spotted only by keeping a close eye on the project. These cases are usually dealt with by a product manager, because they are involved in the UX more than anyone else in the team. This is why 7 years ago I quit drawing interfaces and concentrated on product management.</p><p><strong>NEXT:</strong> <a href="https://productcoalition.com/24-hiring-people-is-a-basic-skill-e5557a905d45">24. Hiring people is a basic skill</a></p><p><strong>PREV: </strong><a href="https://medium.com/@aleksritov/22-the-quickest-way-to-learn-is-through-practice-59f65f03e0a2">22. The quickest way to learn is through practice</a></p><blockquote>Tales of a Product Owner: concentrated wisdom about project management, team creation and UX.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee2209ce1866" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[22. The quickest way to learn is through practice]]></title>
            <link>https://medium.productcoalition.com/22-the-quickest-way-to-learn-is-through-practice-59f65f03e0a2?source=rss-372700c2dc4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/59f65f03e0a2</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Aleks Ritov]]></dc:creator>
            <pubDate>Mon, 04 May 2020 08:31:08 GMT</pubDate>
            <atom:updated>2020-06-15T10:03:17.200Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U0COexp7W1dN_d7KGbrAeg.png" /></figure><p>There are two approaches to training boxers. The first one, which I call the “Soviet” approach, starts with grasping the technique. Children are drilled for years, learn how to punch properly, and sharpen their boxing skills. The “American” approach, on the other hand, takes into account the individual characteristics of a boxer. A newbie boxer is invited to fight in the boxing ring, while the coach assesses his main strengths that will be built upon. Both approaches have proven effective in giving rise to great boxers, but the American approach tends to have quicker results.</p><p>In 2011, I had 15 UX designer vacancies. This was more candidates than the market could offer at the time, so we decided to open a UX design school within our company and apply the American approach to training. Our students went straight to practice and obviously made a lot of mistakes. Tutors would then go through the mistakes and focus on areas for improvement. The rest was up to the student and their willingness to self-study: we provided very little help with this. Some students were put off by it, some couldn’t cope with the speed of learning. But those who “survived” the school are now working in the world’s leading companies.</p><p><strong>NEXT: </strong>Coming soon…</p><p><strong>PREV: </strong><a href="https://medium.com/@aleksritov/21-two-general-principles-for-improving-any-process-3240fceafe6d">21. Two general principles for improving any process</a></p><blockquote>Tales of a Product Owner: concentrated wisdom about project management, team creation and UX. New tale every Tuesday and Thursday!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59f65f03e0a2" width="1" height="1" alt=""><hr><p><a href="https://medium.productcoalition.com/22-the-quickest-way-to-learn-is-through-practice-59f65f03e0a2">22. The quickest way to learn is through practice</a> was originally published in <a href="https://medium.productcoalition.com/">Product Coalition</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[21. Two general principles for improving any process]]></title>
            <link>https://medium.com/@aleksritov/21-two-general-principles-for-improving-any-process-3240fceafe6d?source=rss-372700c2dc4a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3240fceafe6d</guid>
            <category><![CDATA[process-improvement]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Aleks Ritov]]></dc:creator>
            <pubDate>Wed, 29 Apr 2020 17:04:16 GMT</pubDate>
            <atom:updated>2020-04-29T17:09:08.400Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EpImksKTO2i-qsL529p8lg.png" /></figure><p>Over the last year I have experienced several planned hospital admissions, both for myself and with my mother. I had the opportunity to compare 3 public hospitals and one private hospital. Let’s talk about the actual admission process. In public hospitals, you are first asked to queue in the admission area. It then turns out you’re waiting in the wrong line and have to go to the next one. Then you find out something is wrong with your insurance certificate, so you need to go elsewhere to fix it. You end up running from one room to another, trying to solve the algorithm. In a private hospital, however, you go to reception, and from there you are taken straight to the wards.</p><p>It seems to me that fixing this mess is quite easy — all it takes is a new streamlined process. The funny thing is that this mess is actually the result of the process. To fix it, two principles should be followed:</p><ol><li>The actual executors must be interested in optimizing the process.</li><li>They must have the authority and resources to transform the process.</li></ol><p>Check if these principles work for your team.</p><p><strong>NEXT: </strong><a href="https://medium.com/@aleksritov/22-the-quickest-way-to-learn-is-through-practice-59f65f03e0a2">22. The quickest way to learn is through practice</a></p><p><strong>PREV: </strong><a href="https://medium.com/@aleksritov/20-translation-is-a-great-way-to-improve-the-original-text-baa9c9001b15">20. Translation is a great way to improve the original text</a></p><blockquote>Tales of a Product Owner: concentrated wisdom about project management, team creation and UX. New tale every Tuesday and Thursday!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3240fceafe6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>