<?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 Mikhail Sukhov on Medium]]></title>
        <description><![CDATA[Stories by Mikhail Sukhov on Medium]]></description>
        <link>https://medium.com/@webmisha?source=rss-808e3df2a869------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*KmZL1yTQlAmpvOy3Iic_IA.jpeg</url>
            <title>Stories by Mikhail Sukhov on Medium</title>
            <link>https://medium.com/@webmisha?source=rss-808e3df2a869------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:21:56 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@webmisha/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[How I Finally Passed the Danish PD3 Exam]]></title>
            <link>https://webmisha.medium.com/how-i-finally-passed-the-danish-pd3-exam-edc64f413edc?source=rss-808e3df2a869------2</link>
            <guid isPermaLink="false">https://medium.com/p/edc64f413edc</guid>
            <category><![CDATA[danish]]></category>
            <dc:creator><![CDATA[Mikhail Sukhov]]></dc:creator>
            <pubDate>Wed, 01 Jul 2026 19:05:03 GMT</pubDate>
            <atom:updated>2026-07-15T19:09:36.965Z</atom:updated>
            <content:encoded><![CDATA[<p>Before I passed the PD3 exam, I had read dozens of stories from people who had already done it. I was always amazed by how easy they made it sound. Many people wrote that they had passed after only two years of studying, often with very good grades. I always wondered if they were simply more gifted at learning languages than I was, because languages have never come naturally to me. Every new word takes effort, speaking has always been stressful, and for a long time PD3 felt like a huge obstacle that I wasn’t sure I would ever overcome. In the end, though, I did pass, and I hope that by sharing my experience I can make someone else’s journey a little easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*437-zAEtlvilR_U-nltBSg.jpeg" /></figure><p>My Danish journey began in April 2023 when I enrolled in a language school. Everything seemed to be going well at first. I passed Module 1 without any problems, then successfully completed Module 2, and honestly believed I would continue progressing at the same pace. That confidence disappeared when I reached Module 3. I failed the exam, prepared for a retake, and only managed to pass part of it. I tried again and failed once more. After repeating the same cycle several times, I realized that simply working harder was not enough. I needed to change the way I was learning.</p><p>I decided to leave the language school and hire a private tutor. Looking back, this turned out to be another mistake because I chose the wrong person. At that time I didn’t know how to evaluate tutors, and nobody had explained what I should actually be looking for. I simply picked someone with good reviews and hoped that would solve my problems. Unfortunately, it didn’t. I continued studying, registered for the final PD3 exam, and failed again. Throughout 2025 I kept signing up for new exam dates, paying the fee each time, preparing as seriously as I could, and still walking away disappointed. Every failed attempt was frustrating, but after each one I carefully analyzed what had gone wrong and tried to improve before the next attempt. Eventually, on my third attempt at the final exam, I finally passed.</p><p>Looking back now, I can clearly see three mistakes that slowed down my progress more than anything else.</p><h3><strong>The 1st was choosing the wrong tutor</strong></h3><p>A tutor is not just someone who explains grammar. The right tutor motivates you, makes you enjoy learning, and helps you believe that progress is possible even when it feels painfully slow. Motivation is incredibly important when learning Danish because there will be periods when you feel like you’re making no progress at all. During those moments, a good tutor can make the difference between continuing and giving up. Eventually I found someone who suited my learning style perfectly, and I would happily recommend him to anyone preparing for PD3, his name is <a href="https://www.italki.com/i/reft/AE6BFb/Ac0DE0b/danish?hl=en&amp;utm_source=copy_link&amp;utm_medium=share_teacher">Mika Christiansen</a>, and he is best of the best. At the same time, I know that every student is different, so my biggest recommendation is not a specific teacher but the platform <a href="https://www.italki.com/">italki</a>, where you can try lessons with different tutors until you find someone who truly fits your personality and learning style.</p><h3>The 2nd mistake was studying in the wrong environment</h3><p>For a long time I tried to study at home, but there was always something competing for my attention. Household chores, my phone, or simply the feeling that home was a place to relax rather than concentrate made it difficult to stay focused. After experimenting with different places and schedules, I discovered that the local library worked perfectly for me. Every Saturday and Sunday I would arrive in the morning and spend most of the day studying there. I also accepted something important about myself: after a full day of work I simply didn’t have the energy or motivation to study effectively, and forcing myself only made me dislike the process. Instead of feeling guilty, I built a routine around weekends, and that routine became one of the biggest reasons I eventually succeeded. Even now, after passing the exam, I still enjoy going to the library because it became associated with focus and progress.</p><h3>The 3rd lesson was realizing that I had been spending far too much time on grammar and not nearly enough time speaking</h3><p>Grammar is important, but speaking is what really determines your success in the PD3 exam. I tried language clubs, group classes, and different conversation events, but none of them suited me particularly well. What made the biggest difference was finding a language partner for one-on-one conversations. I used <a href="https://tandem.net/">Tandem</a> to connect with someone who wanted to improve their Russian while helping me improve my Danish.</p><p>We spoke regularly, corrected each other’s mistakes, and gradually those conversations became easier and more natural. My confidence grew with every session, and I honestly believe that those conversations contributed more to my final result than countless hours spent memorizing grammar rules.</p><p>If there is one thing I learned from this experience, it is that passing PD3 is not only about intelligence or language talent. It is about finding an approach that works for you and continuing even after setbacks. Everyone learns differently, and what failed for me may work perfectly for someone else. The important part is not to assume that failure means you are incapable of learning Danish. Sometimes it simply means you need a different teacher, a different study environment, or a different way of practicing.</p><p>I genuinely hope that some of these lessons will help you avoid the mistakes I made. If this article saves even one person a failed exam attempt, months of frustration, or unnecessary stress, then sharing my story was absolutely worth it. I wish you the best of luck with your PD3 journey, and I hope that before long you’ll be writing your own success story.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edc64f413edc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Почему мы создаем стратегию компании, но забываем про личную стратегию]]></title>
            <link>https://webmisha.medium.com/%D0%BF%D0%BE%D1%87%D0%B5%D0%BC%D1%83-%D0%BC%D1%8B-%D1%81%D0%BE%D0%B7%D0%B4%D0%B0%D0%B5%D0%BC-%D1%81%D1%82%D1%80%D0%B0%D1%82%D0%B5%D0%B3%D0%B8%D1%8E-%D0%BA%D0%BE%D0%BC%D0%BF%D0%B0%D0%BD%D0%B8%D0%B8-%D0%BD%D0%BE-%D0%B7%D0%B0%D0%B1%D1%8B%D0%B2%D0%B0%D0%B5%D0%BC-%D0%BF%D1%80%D0%BE-%D0%BB%D0%B8%D1%87%D0%BD%D1%83%D1%8E-%D1%81%D1%82%D1%80%D0%B0%D1%82%D0%B5%D0%B3%D0%B8%D1%8E-ed469430e3cb?source=rss-808e3df2a869------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed469430e3cb</guid>
            <category><![CDATA[личная-стратегия]]></category>
            <dc:creator><![CDATA[Mikhail Sukhov]]></dc:creator>
            <pubDate>Tue, 23 Dec 2025 22:41:45 GMT</pubDate>
            <atom:updated>2025-12-23T22:41:45.786Z</atom:updated>
            <content:encoded><![CDATA[<p>В современной корпоративной среде наблюдается устойчивый парадокс: руководители высшего звена, демонстрирующие исключительную компетентность в разработке и реализации долгосрочных стратегий для своих организаций, систематически игнорируют разработку личной жизненной стратегии. Это явление не является следствием недостатка навыков или дисциплины. Напротив, анализ данных свидетельствует о том, что отказ от личного стратегирования является результатом сложного взаимодействия когнитивных искажений, профессиональной деформации и специфических организационных структур, которые поощряют корпоративное планирование, одновременно создавая барьеры для индивидуального.</p><h3>Психологические механизмы уклонения</h3><p>Одной из фундаментальных причин отсутствия личной стратегии у топ-менеджеров является феномен гиперболического дисконтирования. Этот механизм заставляет индивида отдавать предпочтение немедленным вознаграждениям — таким как закрытие квартальной сделки, одобрение совета директоров или решение операционного кризиса — перед долгосрочными, более значимыми, но отдаленными целями личного развития и благополучия. В нейробиологическом контексте принятие решений в условиях стресса активирует «горячие» исполнительные функции, которые ориентированы на немедленное удовлетворение и снижение риска в текущий момент, в то время как «холодные» функции, ответственные за долгосрочное планирование, подавляются.</p><p>Джордж Эйнсли в своей фундаментальной работе «Specious Reward: A Behavioral Theory of Impulsiveness and Impulse Control» он одним из первых предложил использовать гиперболическую кривую для описания того, как люди и животные обесценивают будущие вознаграждения. Его теория объясняет феномен «инверсии предпочтений» (preference reversal): человек может предпочесть 100 долларов через месяц вместо 110 через месяц и один день, но если выбор стоит между «сегодня» и «завтра», он выберет меньшую сумму немедленно.</p><p>Однако именно Джеймс Мазур считается автором классической математической формулы гиперболического дисконтирования. Модель которой объясняет, почему менеджер выбирает работу над стратегией компании (немедленная обратная связь и социальное подкрепление) вместо личного планирования (отложенный результат):</p><p>V = A/(1 + kD)</p><p>Где V — воспринимаемая ценность вознаграждения, A — его абсолютная величина, D — задержка во времени, а k — индивидуальный коэффициент дисконтирования. Для топ-менеджера в корпоративной среде значение D для бизнес-целей минимизировано за счет систем квартальной отчетности и KPI, тогда как для личных целей (здоровье, семья, самореализация) D измеряется годами, что делает их текущую ценность в глазах мозга ничтожной.</p><p>Дэвид Лайбсон в статье «Golden Eggs and Hyperbolic Discounting» перенес эти психологические модели в сферу экономики и управления. Он показал, как гиперболическое дисконтирование заставляет людей (включая топ-менеджеров) недоинвестировать в долгосрочные активы («золотые яйца», такие как личные пенсионные планы или образование) и перерасходовать ресурсы в краткосрочном периоде.</p><p>Эти работы доказали, что человеческий мозг не рассчитывает выгоду рационально (экспоненциально), как предполагала классическая экономика. Вместо этого мы демонстрируем «смещение к настоящему» (present bias): ценность будущего вознаграждения падает очень резко при минимальных задержках в ближайшем будущем, но снижается плавно, когда речь идет о далеких горизонтах планирования. Это и объясняет, почему менеджеру так трудно найти мотивацию для личной стратегии, результаты которой проявятся лишь через годы.</p><h3>Иллюзия завершенности истории и ловушки идентичности</h3><p>Исследования McKinsey и HEC Paris указывают на существование «иллюзии конца истории» (End of History Illusion). Суть искажения заключается в том, что люди любого возраста склонны верить, что они значительно изменились в прошлом, но останутся практически неизменными в будущем. Лидеры, достигшие уровня C-suite, часто воспринимают свою идентичность как «завершенный проект». Они фокусируют энергию на защите и трансляции уже сформированного образа (проецировании идентичности), а не на поиске путей дальнейшей эволюции.</p><p>Этот процесс подкрепляется четырьмя специфическими ментальными ловушками идентичности:</p><ol><li>Стремление к простым историям: Желание видеть мир через призму понятных нарративов о героях и злодеях ослепляет лидера в отношении сложности собственной жизни.</li><li>Чувство правоты: Успех в бизнесе создает нейробиологическую зависимость от ощущения собственной правоты, которое является скорее эмоцией, чем результатом логики. Это мешает критическому анализу личных дефицитов.</li><li>Поиск согласия: Эволюционная потребность в социальном одобрении заставляет лидеров следовать общепринятым сценариям успеха («быть эффективным для компании»), игнорируя индивидуальные потребности.</li><li>Иллюзия контроля: Стремление к прямому контролю над результатами, возможное в бизнесе, оказывается недостижимым в личной сфере, что вызывает тревогу и заставляет менеджера избегать планирования того, что он не может полностью контролировать.</li></ol><h3>Почему профессиональные навыки не переносятся в частную жизнь</h3><p>Явление, известное как «синдром детей сапожника» (The Cobbler’s Children Syndrome), в контексте высшего руководства приобретает критические масштабы. Специалисты, виртуозно владеющие инструментами прогнозирования и риск-менеджмента, оказываются беспомощными в управлении собственной жизненной инфраструктурой.</p><p>Исследования юридических и финансовых руководителей показывают, что пренебрежение личной стратегией часто оправдывается «хроническим дефицитом времени», который на деле является симптомом зависимости от кризисного управления. Менеджеры подсознательно «любят» стрессовую среду, так как она дает быстрый дофаминовый отклик, в то время как долгосрочное личное планирование требует тишины и глубокой рефлексии, к которой мозг лидера становится не приспособлен.</p><h3>Профессиональное эго и иллюзия неуязвимости</h3><p>Топ-менеджеры часто страдают от убеждения в собственной исключительности и неуязвимости. Это приводит к отказу от планирования таких сценариев, как болезнь, потеря дееспособности или внезапная смена карьеры. Опрос гарвардских выпускников выявил, что те, кто в начале карьеры был полон оптимизма, через 20 лет часто оказывались в ситуации личного кризиса именно из-за нежелания признать вероятность негативных сценариев в частной жизни. Страх показаться «слабым» перед коллегами или подчиненными заставляет лидера «прорываться» сквозь личные проблемы вместо того, чтобы стратегически их решать.</p><h3>Как мы распределяем жизнь по остаточному принципу</h3><p>Клейтон Кристенсен, анализируя причины неудач успешных менеджеров в личной жизни, указывает на фатальную ошибку использования маржинального анализа в вопросах этики и отношений. В бизнесе мы принимаем решения на основе дополнительных затрат на одно действие, но в личной жизни полная стоимость «разового» отступления от стратегии оказывается катастрофической.</p><p>Индивиды склонны недоинвестировать в семью и личное развитие именно потому, что эти сферы не дают немедленной отдачи. Когда компания требует внимания, результат виден сразу. Когда внимание требует ребенок или собственное здоровье, отсутствие инвестиций не проявляется мгновенно. К моменту, когда отсутствие стратегии становится очевидным, «капитал отношений» или «капитал здоровья» часто оказывается полностью исчерпан.</p><h3>Теория «Работы, которую нужно выполнить» в отношениях</h3><p>Многие руководители терпят неудачу в личной жизни, потому что подходят к семье с позиций «что я хочу получить», а не «какую работу я должен выполнить для своих близких». В бизнесе понимание потребностей клиента является основой стратегии. В личной жизни менеджеры часто игнорируют «работу», на которую их «нанимают» супруги и дети — обеспечение эмоциональной безопасности, присутствия и сопричастности. Отсутствие стратегии в этой области ведет к тому, что менеджер пытается «откупиться» от семьи материальными ресурсами, что в долгосрочной перспективе не заменяет стратегического присутствия.</p><h3>Почему личные обещания не становятся обязательствами</h3><p>Одной из «скрытых» причин краха стратегий (как корпоративных, так и личных) является нарушение координации действий. Исследования McKinsey показывают, что только 27% руководителей считают свои организации эффективными в переводе стратегии в действие. В личной жизни этот процент еще ниже. Проблема заключается в отсутствии «культуры обязательств» по отношению к самому себе.</p><p>Топ-менеджеры часто используют «ложное согласие» (fake agreement) в личных отношениях и в диалоге с собой. Они говорят «да» личным планам (отпуску, спорту, чтению), заранее зная, что при малейшем давлении со стороны бизнеса эти обещания будут нарушены. Это создает «долг доверия» перед самим собой, который со временем приводит к апатии и потере смысла.</p><h3>Хореография исполнения и удовлетворенность</h3><p>В бизнесе завершение этапа стратегии подтверждается декларацией о выполнении и анализом обратной связи. В личной жизни этот этап часто отсутствует. Менеджер может достичь цели (например, заработать определенную сумму), но не «объявить» себе о завершении этого этапа, продолжая бежать в том же ритме по инерции. Без четкой фиксации достижений и рефлексии доверие к собственной личной стратегии подрывается, и она начинает восприниматься как пустая формальность.</p><h3>Организационная идентификация и риск поглощения личности</h3><p>Топ-менеджеры подвержены риску чрезмерной организационной идентификации (OI) — восприятию своего «Я» как неотделимого от компании. Когда человек говорит «мы», имея в виду корпорацию, он передает право на разработку своей жизненной траектории работодателю.</p><p>Данные указывают на то, что высокий уровень OI изначально снижает риск выгорания за счет чувства сопричастности, однако при достижении определенного порога связь становится обратной. Сверх-идентификация ведет к трудоголизму, который нейропсихологически близок к аддикции. В этой стадии личная стратегия становится не просто «забытой», а опасной для лидера, так как она требует признания автономии личности от корпоративных целей.</p><h3>Конфликт профессиональной и организационной идентичности</h3><p>У многих лидеров возникает внутренний конфликт между тем, кем они должны быть согласно стандартам своей профессии (например, объективный финансовый директор), и тем, кем их требует быть организация (например, лояльный член команды, скрывающий риски). Этот конфликт поглощает весь когнитивный ресурс, не оставляя энергии на построение личной стратегии. В результате индивид выбирает путь наименьшего сопротивления — полное слияние с текущей ролью.</p><h3>Почему SWOT и BSC не помогают лидеру в жизни</h3><p>Топ-менеджеры привыкли к определенному набору инструментов, которые при попытке применения к личной жизни вызывают отторжение или оказываются неэффективными.</p><ol><li>Ограничения SWOT-анализа: Этот инструмент в личном планировании часто превращается в статичный список, лишенный приоритизации. В отличие от бизнеса, где угрозы часто внешние и поддаются количественной оценке, в личной жизни главные угрозы — внутренние (прокрастинация, страхи, потеря смыслов), и SWOT не дает механизмов работы с ними.</li><li>Провалы Balanced Scorecard (BSC): В корпорациях BSC часто критикуют за избыточность KPI. Попытка внедрить личный BSC с 20–30 показателями (здоровье, финансы, хобби, обучение, семья) приводит к информационной перегрузке. Когда система личного планирования становится сложнее, чем сама жизнь, менеджер забрасывает её.</li><li>Неприменимость PEST-анализа: Анализ политических и макроэкономических факторов полезен для транснациональной компании, но для личной стратегии он часто становится источником тревоги, не предлагая путей личного влияния на ситуацию.</li></ol><h3>Влияние отсутствия личной стратегии на корпоративные результаты</h3><p>Пренебрежение личным планированием не является изолированным делом руководителя; оно напрямую влияет на качество принимаемых им бизнес-решений. Исследования показывают, что компании, возглавляемые лидерами в состоянии выгорания (следствие отсутствия стратегии), демонстрируют худшие финансовые результаты и более высокую текучесть кадров.</p><p>Дефицит личной стратегии ведет к «туннельному зрению» и снижению когнитивной гибкости. Руководитель, чья жизнь не сбалансирована, чаще склонен к рискованным, импульсивным решениям или, наоборот, к параличу анализа в условиях неопределенности. Более того, разрыв в восприятии ментального здоровья между топ-менеджерами и их подчиненными (согласно McKinsey, менеджеры оценивают атмосферу на 22% лучше, чем сотрудники) часто объясняется тем, что сами руководители потеряли контакт со своими потребностями и не могут адекватно оценить состояние других.</p><h3>Экономика действий и цена ошибки</h3><p>В условиях неопределенности процесс принятия решений становится «экономикой действий», где время и информация являются дефицитными ресурсами. Руководитель без личной стратегии тратит эти ресурсы неэффективно, так как он не может отличить истинно важные бизнес-задачи от тех, которые лишь заполняют вакуум его личной нереализованности. Это ведет к созданию стратегий, которые на бумаге выглядят логично, но физически невыполнимы командой из-за эмоционального истощения лидера.</p><h3>Методы восстановления личного стратегического фокуса</h3><p>Для того чтобы топ-менеджмент начал уделять внимание личной стратегии, необходимо сместить парадигму от «тайм-менеджмента» к «управлению энергией и смыслами».</p><h3>Стратегия как акт личной ответственности</h3><p>Топ-менеджеры забывают про личную стратегию не потому, что они плохие стратеги, а потому, что они слишком хорошие «корпоративные солдаты», попавшие в ловушку системы, которая вознаграждает за самоотречение. Однако современный контекст требует от лидера перехода к модели «аутентичного управления», где успех компании является следствием, а не заменой личного процветания.</p><p>Разработка личной стратегии требует мужества столкнуться с неопределенностью собственной жизни, которая гораздо выше неопределенности любого рынка. Лидеры, нашедшие время на этот процесс, не только страхуют себя от выгорания и кризиса идентичности, но и создают более устойчивые, человечные и эффективные организации. В конечном счете, мерилом жизни руководителя будет не сумма прибыли на его счету, а количество людей, которым он помог стать лучше, начиная с самого себя.</p><p>Посмотрим теперь как личная стратегия усиливает корпоративную и почему это происходит.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed469430e3cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Path to Agile Coaching]]></title>
            <link>https://webmisha.medium.com/from-software-developer-to-agile-coach-my-path-to-people-and-processes-6ec23cdffe2f?source=rss-808e3df2a869------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ec23cdffe2f</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[agile-coach]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Mikhail Sukhov]]></dc:creator>
            <pubDate>Sun, 25 Aug 2024 06:51:42 GMT</pubDate>
            <atom:updated>2024-11-12T11:41:37.242Z</atom:updated>
            <content:encoded><![CDATA[<p>My name is Mikhail, and my career journey has been a dynamic one. I graduated from Moscow State Technical University in 2006 with a Master’s in Engineering, majoring in Computer Science.</p><p>Starting as a Software Developer in 2003, I presented a project on human behavior simulation at a scientific conference in 2005. This experience made me realize that I’m more interested in people than computers.</p><p>I then spent four years as a Project Manager in the tech industry, blending my technical skills with team management. My interest in shaping products led me to work as a Product Manager for seven years, where I notably helped develop and patent a <a href="https://patents.google.com/patent/US20180039638A1/en?inventor=mikhail+sukhov&amp;oq=mikhail+sukhov">recommendation system</a> in the U.S.</p><p>Eventually, I discovered <a href="https://medium.com/@webmisha/how-to-build-up-your-own-strategy-87fccca08bfc">my true passion</a>: improving processes in large organizations. For the past five years, I’ve been an Agile Coach, co-creating a <a href="https://medium.com/@webmisha/team-maturity-model-86781671eb44">maturity model </a>and launching <a href="https://medium.com/@webmisha/%D0%BF%D1%80%D0%BE-discovery-sprints-e7f6cd48e124">discovery sprints</a>. I love working with people and processes, and I’m excited about where this journey will take me next.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ec23cdffe2f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to implement Impediment List]]></title>
            <link>https://webmisha.medium.com/how-to-implement-impediment-lists-8bbebb94b7af?source=rss-808e3df2a869------2</link>
            <guid isPermaLink="false">https://medium.com/p/8bbebb94b7af</guid>
            <category><![CDATA[impediment-list]]></category>
            <category><![CDATA[impediment]]></category>
            <dc:creator><![CDATA[Mikhail Sukhov]]></dc:creator>
            <pubDate>Mon, 01 Jul 2024 20:42:32 GMT</pubDate>
            <atom:updated>2024-07-01T20:42:54.754Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is an Impediment List?</h3><p>An impediment list is a tool used in Scrum to track obstacles or issues that prevent a team from completing their tasks efficiently. These impediments can range from technical issues, such as bugs or software limitations, to organizational challenges, like unclear requirements or inadequate resources.</p><h3>Types of Impediments with Examples</h3><ol><li>Technical Impediments: A critical server crash, Lack of automated testing frameworks.</li><li>Organizational Impediments: Inadequate management support, Bureaucratic processes slowing down decision-making.</li><li>Process-Related Impediments: Dependencies on other teams, Insufficient documentation.</li><li>Interpersonal Impediments: Conflicts within the team, Lack of communication or trust among team members.</li></ol><h3>Levels of Impediments</h3><p>1. Team Level: Managed by the Scrum Master, these impediments are usually identified during daily stand-ups or sprint retrospectives. The Scrum Master documents them, often using tools like Jira, and works to resolve them quickly to maintain team productivity.</p><p>2. Cluster Level: Handled by a Tech Cluster Lead, these impediments affect multiple teams within a cluster. They are typically addressed in broader retrospectives involving representatives from each team.</p><p>3. Company Level: Overseen by the CTO, these impediments impact the entire organization. They are often strategic in nature and require high-level intervention to resolve.</p><h3>How Impediments Arise</h3><p>Impediments often come to light during retrospective meetings, where the team reflects on challenges faced during the sprint. For cluster or company-level impediments, an overall retrospective may be held to gather insights from multiple teams and address widespread issues.</p><h3>Ownership of the Impediment List</h3><p>1. Team Level: The Scrum Master owns the team impediment list, similar to how the Product Owner manages the product backlog. This ownership includes identifying, documenting, and facilitating the resolution of impediments.<br> <br>2. Cluster Level: The Tech Cluster Lead is responsible for the cluster impediment list, ensuring that issues affecting multiple teams are addressed.<br> <br>3. Company Level: The CTO owns the company impediment list, tackling strategic and organizational challenges.</p><h3>Steps to Implement an Impediment List</h3><p>1. Initialization:<br> — Set up impediment lists in tools like Jira for each level: team, cluster, and company.<br> — Create Kanban boards with statuses such as “To Do,” “In Progress,” and “Done” to track progress.</p><p>2. Escalation Mechanism:<br> — Develop a process for escalating impediments from team level to cluster and company levels, similar to bubbles rising in a glass of Schweppes.<br> — Handle sensitive impediments (e.g., those involving personnel changes) with extra care.</p><p>3. Regular Reviews:<br> — Conduct regular reviews at cluster and company levels, ideally during overall retrospectives, to discuss and resolve impediments.<br> — Allocate time at the beginning of these meetings to review the current impediments and their statuses.</p><h3>Conclusion</h3><p>The impediment list is a powerful tool for systematically addressing obstacles at various levels within an organization. By using a structured approach to identify, document, and resolve impediments, teams can enhance their efficiency and collaboration. Regular reviews and an effective escalation mechanism ensure that no impediment goes unnoticed or unaddressed, promoting continuous improvement across the organization.</p><h3>Sources:</h3><ul><li><a href="https://www.scrum.org/resources/navigating-impediments">Scrum.org on Navigating Impediments</a></li><li><a href="https://leanagiletraining.com/better-agile/the-impediment-list/">Lean Agile Training on The Impediment List</a></li><li><a href="https://www.techagilist.com/">Tech Agilist on Strategies for Scrum Masters</a></li><li><a href="https://www.ostendo.io/blog/how-to-create-an-impediment-list-in-scrum/">Ostendo.io on Creating an Impediment List</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8bbebb94b7af" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build up Your own Strategy]]></title>
            <link>https://webmisha.medium.com/how-to-build-up-your-own-strategy-87fccca08bfc?source=rss-808e3df2a869------2</link>
            <guid isPermaLink="false">https://medium.com/p/87fccca08bfc</guid>
            <dc:creator><![CDATA[Mikhail Sukhov]]></dc:creator>
            <pubDate>Tue, 26 Dec 2023 10:46:45 GMT</pubDate>
            <atom:updated>2024-11-12T12:13:06.526Z</atom:updated>
            <content:encoded><![CDATA[<p>It is crucial to have a clear understanding of your personal strategy to have a precise vision of what you do and why in your daily activities, in order to be happy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FCDsOEqV42No4J5FZXkWDw.png" /></figure><p>To simplify this process, I’ve prepared a filled-out template that outlines three key areas: work, self, and family. This is essential to ensure harmony across these three areas and prevent any imbalance.</p><p>Simply copy this template below into Word or Google Docs and adapt it for your own needs.</p><p>_________________________________________________________________</p><h3>1. My Motivation and Purpose</h3><p>I help companies and individuals structure information to achieve the best possible outcomes, transforming chaos into order. I listen carefully, distill the essentials, and focus on what’s most valuable. With this superpower, I assist teams in optimizing processes, provide one-on-one mentorship, and track progress to help people reach their goals.</p><h3>2. Current Status and Challenges</h3><p><strong>2.1. Family:</strong> My family is my team, offering unwavering support and a foundation for personal growth. I actively contribute to shaping our family culture, which we see reflected in our children, enriching our lives, and creating a warm, welcoming place to come home to, no matter where I am. Currently, I’m focused on balancing quality time and individual needs within the family, navigating the challenge of nurturing each person’s growth while maintaining unity.</p><p><strong>2.2. Work:</strong> When I find joy in my work, financial success tends to follow naturally. I’m actively seeking and refining strategies for effective money management, believing that a shared budget approach for both family and work teams fosters trust, transparency, and responsibility. The current challenge is achieving consistency in this financial framework, aligning it with changing needs while maintaining flexibility.</p><p><strong>2.3. Self:</strong> I derive joy from each interaction, whether with teams or individuals, and find deep satisfaction in personal progress. It feels as though I’m working toward something genuinely meaningful, something that’s been a long time coming. My current challenge is to sustain this momentum of growth and joy, while also managing the balance between professional commitments and personal goals.</p><h3>3. The Future in 1, 3, and 10 Years</h3><h4>3.1. Desired outcomes in 1year</h4><ul><li><strong>3.1.1. Work</strong>: <em>Witness the dynamics confirming my belief that “happy teams create better products.” Implement OKRs in logistics to enhance cross-functional teamwork and transparent progress tracking.</em></li><li><strong>3.1.2. Family</strong>: <em>Maintain a strong bond during self-isolation, developing meaningful home traditions and rituals.</em></li><li><strong>3.1.3. Myself</strong>: <em>Continue physical activity, mastering calisthenics tricks and maintaining a healthy lifestyle.</em></li></ul><h4>3.2. Desired outcomes in 3 years</h4><ul><li><strong>3.2.1. Work</strong>: <em>Consolidate positive practices in team management. Introduce a less traditional and more collaborative model, influencing others to contribute to this development.</em></li><li><strong>3.2.2. Family</strong>: <em>Explore and enjoy outdoor activities such as hiking and camping. Identify a preferred housing model for future development.</em></li><li><strong>3.2.3. Myself</strong>:: <em>Embrace a favorite sport with my family.</em></li></ul><h4>3.3. Desired outcomes in 10 years</h4><ul><li><strong>3.3.1. Work</strong>: <em>Contribute to a company with a well-established turquoise culture, aligning personal aspirations with the company’s evolutionary goals. Actively engage in the market, aiding less advanced but interested individuals in advancing their careers.</em></li><li><strong>3.3.2. Family</strong>: <em>Reside in an ideal location. Guide my children toward independence, fostering strong relationships built on trust.</em></li><li><strong>3.3.3. Myself</strong>: <em>Embrace a favorite sport with my family.</em></li></ul><p>_________________________________________________________________</p><p>You can then turn this into quarterly and yearly goals. Feel free to reach me out on LinkedIn: <a href="https://www.linkedin.com/in/mikhailsukhov/">https://www.linkedin.com/in/mikhailsukhov/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=87fccca08bfc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Plan a Meeting]]></title>
            <link>https://webmisha.medium.com/%D0%BA%D0%B0%D0%BA-%D1%81%D0%B4%D0%B5%D0%BB%D0%B0%D1%82%D1%8C-%D0%BF%D0%BB%D0%B0%D0%BD-%D0%B2%D1%81%D1%82%D1%80%D0%B5%D1%87%D0%B8-fbae3e570545?source=rss-808e3df2a869------2</link>
            <guid isPermaLink="false">https://medium.com/p/fbae3e570545</guid>
            <dc:creator><![CDATA[Mikhail Sukhov]]></dc:creator>
            <pubDate>Fri, 11 Feb 2022 08:44:33 GMT</pubDate>
            <atom:updated>2022-07-27T08:25:06.663Z</atom:updated>
            <content:encoded><![CDATA[<p>Suppose the meeting is complex, such as a workshop or a strategic session. In that case, the moderator needs to have an exact plan by the minute to understand whether he can meet the specified interval and achieve the result while having a margin of time.</p><p>It might look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cmRzteasQjurb8VVGyRYeg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fbae3e570545" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Start a New Team]]></title>
            <link>https://webmisha.medium.com/%D0%BF%D0%BB%D0%B0%D0%BD-%D0%B7%D0%B0%D0%BF%D1%83%D1%81%D0%BA%D0%B0-%D0%BD%D0%BE%D0%B2%D0%BE%D0%B9-%D0%BA%D0%BE%D0%BC%D0%B0%D0%BD%D0%B4%D1%8B-1a566254c79e?source=rss-808e3df2a869------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a566254c79e</guid>
            <category><![CDATA[запуск-новой-команды]]></category>
            <category><![CDATA[скрам]]></category>
            <dc:creator><![CDATA[Mikhail Sukhov]]></dc:creator>
            <pubDate>Wed, 19 Jan 2022 09:59:03 GMT</pubDate>
            <atom:updated>2022-08-13T08:15:30.208Z</atom:updated>
            <content:encoded><![CDATA[<p>In order to launch a new team, there are several steps that need to be well facilitated.</p><h4>Step 1. Product Owner shares product vision</h4><p>It is important for everyone to understand why, how and why we are making this particular product, for whom and how we will understand that we have achieved success.</p><h4>Step 2. Choose a new team name</h4><p>It’s great when the name inspires everyone. For example “Team A” or “BFG”. It is important that the whole team say that the name is OK, so you can brainstorm and choose the best option.</p><h4>Step 3. Team agreements “We do, we don’t do, we allow”</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eW7WZ1zYu1_25SROmdT7lQ.png" /></figure><p>If the team is new or there are new members, it is reasonable “on the shore” to say “ground rules” in the following format:</p><ol><li>Create a board in Miro and split it into three columns</li><li>Each of the participants is invited to write stickers of a certain color on the topic of what is acceptable to do in a team, for example: “Strive to work on the sprint goal”, “Help and educate others”; what is unacceptable, such as “hate and discount”, “late for meetings” and what is acceptable, such as “checkmate”, “jokes below the belt”</li><li>Next, similar ones are combined and the facilitator asks each participant if he agrees that the card should be on the board. If someone disagrees — the card should be placed in the “Discuss” column and discuss them in the remaining time or schedule another meeting. It is important that if at least one disagrees, then the rule is not accepted and is not hung on the board.</li></ol><p>Further, these rules are digitized and placed in the command space of the team. It is reasonable to revise agreements if a new participant appears.</p><h4>Step 4. Tell about the principles of work, if it is, for example, Scrum</h4><p>In this block, if appropriate, you can give an overview of the Scrum theory, answer questions, agree on what tools we use (boards, trackers, roadmaps).</p><h4>Step 5. Make a “starmap” or “star map” of competencies</h4><p>Along the competency vertical, for example: Go, PHP, Architecture, Facilitation, Scrum. Horizontally, first and last name, specialization, for example: QA engineer. At the intersection, points are put together (I want to study), dashes (I don’t want to study) and asterisks (I know and can teach others). Based on these data, the team and the team leader understand what is missing to create a product, what to upgrade and strengthen.</p><h4>Step 6. Approve the schedule of events</h4><p>If you haven’t done this yet, then right at the meeting put all the necessary events on the calendar and start with grooming or zero sprint planning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a566254c79e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to build processes at an IT company]]></title>
            <link>https://webmisha.medium.com/%D0%BA%D0%B0%D0%BA-%D0%B2%D1%8B%D1%81%D1%82%D1%80%D0%BE%D0%B8%D1%82%D1%8C-%D0%BF%D1%80%D0%BE%D1%86%D0%B5%D1%81%D1%81%D1%8B-%D0%B2-it-%D0%BA%D0%BE%D0%BC%D0%BF%D0%B0%D0%BD%D0%B8%D0%B8-34ce674b4719?source=rss-808e3df2a869------2</link>
            <guid isPermaLink="false">https://medium.com/p/34ce674b4719</guid>
            <category><![CDATA[бизнес-процессы]]></category>
            <category><![CDATA[cto]]></category>
            <category><![CDATA[it]]></category>
            <category><![CDATA[cpo]]></category>
            <dc:creator><![CDATA[Mikhail Sukhov]]></dc:creator>
            <pubDate>Mon, 06 Dec 2021 08:53:41 GMT</pubDate>
            <atom:updated>2022-08-13T15:26:03.786Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uAvRtYPPUMKgqVcy.png" /></figure><p>Processes are the best thing you can do as a CTO or Product Director. This is an investment, the foundation in which your teams will already live: the house that you are laying, rooms, railings, terraces, windows, doors, and how you organize this foundation, this frame, will depend on how everything will be work. It is important to lay this foundation at the very beginning and make it scalable, adhere to certain principles.</p><p><strong><em>Fundamental principles.</em></strong></p><p>It will be based on 5 principles from which the toolkit follows.</p><p><em>1. The principle of the “red thread”</em></p><p>It is necessary that it is clear from top to bottom throughout the company how exactly the task of a simple engineer who works at a computer that stands on the Daily Stand Up and talks about what he did for the sprint goal is related to the company’s strategy. It is necessary that this link be like a red thread that can be traced from Daily Stand Up to quarterly goals, from quarterly goals to annual goals, from annual goals to the company’s strategy, that is, two-week sprint goals → quarter goals → year goals → company strategy, strategic initiatives. This connection had to be clear so that the engineer could definitely tell that he was working on something very important. This will bring some clarity to his work and motivate him to work in this company.</p><p>2. <em>Clarity and transparency</em></p><p>All process artifacts must be publicly available. The company’s strategy should be in a public place and visible to everyone, everyone should understand it, share it, ask questions. It should not be Bullshit Bingo, it should be meaningful, understandable, inspiring and capacious text that is broken down into specific projects with specific responsibilities and the ability to see the progress of the work. The goals of all departments should be available, anyone can log in and see the dependencies — everything is transparent and accessible: all team backlogs, tasks, sprints, demo results — everyone sees everything.</p><p>Exceptions may be: results of retrospectives, individual development plans for employees, one-on-one results, salaries. All this remains out of the public domain. But the most important artifacts that affect the first principle — the principle of the red thread — should be accessible and transparent.</p><p><em>3. The presence of a feedback loop (experimental loop).</em></p><p>At first, you plan something, agree on it, go to iteration (to work) — it can be a week, a month, a year. During this movement, you will track the result so that everything goes according to plan, so that your sprint goals are achieved. You make cuts like this. At the end, you conduct a demonstration, show the results, get feedback — what was good, what was bad — collect this feedback and bring it inside yourself, inside your team. Conduct a retrospective, reflection: what could have been done better, and learn from this experience. It’s about testing hypotheses, team work, people doing one-on-one, strategic projects, everything. That is, a loop that closes and gives feedback must work on all, all cycles.</p><p><em>4. Cool engineering and product practices</em></p><p>All engineers want to work in cool teams with a cool engineer, with strong practices. Nobody wants to work on old frameworks with a lot of bugs, a lot of monolith. Product managers don’t want to work with people who don’t develop hypotheses in a meaningful way, who just want you to complete their task without filtering it through the filters: “symptom” → “problem” → “problem selection” → “solution” → “solution selection” “. This is product work — the search for the best solution, an entrepreneurial approach, so it is very important to build cool product and engineering processes, set some kind of baseline and strive for this level. This is important for the whole company, for hiring, when you have very cool technical and product processes, for motivating employees, for product quality,</p><p><em>5. High in the work of an engineer and a product manager</em></p><p>Product Manager and Engineer should be fun to work in a team. He should come to work every time and get high, he should be cool from people, from processes, from what he can do within this framework, from freedom, from the absence of bureaucracy. All processes are created primarily for people, so that they can create and create within the framework of their cubes, bricks, small blocks. At the same time, there should be some rules that help them in this. As there are rules of the road, and people drive cars, travel long distances and enjoy the freedom of movement, but there are some restrictions to move safely, not to disturb others, so that it is environmentally friendly.</p><p>Likewise with processes. The happiness of a simple engineer in a team is primary. He should feel very good, and this signal must be taken into account in the first place, since the user for the processes is him. If the people are good, then the company will be good. They will stay for a long time, make very cool and high quality products.</p><p><strong><em>Based on these principles and five tracks below</em></strong></p><h3><em>1. Tech Strategy Track</em></h3><p>The strategy of the technical department is aligned with the strategy of the product department and cascades from the strategy of the company.</p><p>At the strategy level, we:</p><p>– consider trends and tensions;</p><p>- describe the situation — as it is now and how we want;</p><p>– “as we want” we describe in the format of technical projects;</p><p>– we determine those responsible for these technical projects;</p><p>- decompose into tasks;</p><p>- we lower these technical projects to the level of R&amp;D;</p><p>– we start tracking them once a quarter (but once a month is better).</p><h3><em>2. OKR’s Track</em></h3><p>It consists of Objectives and Key Results. There should not be many of them (recommended 3–5). Then they are tracked once a month, determining what needs to be completed, what needs to be reformulated, where to focus, where to add resources. These OKRs should be aligned with roadmaps and sprint goals. If you look at the roadmaps of the teams, then the top left will be the highest priority OKR, and the bottom left will be the least priority. Next, by sprints, you can see the work plan for a specific quarter associated with OKRs.</p><h3><em>3. New Opportunities Track</em></h3><p>Here business is working on what markets to enter, what opportunities to take. This is an analysis of the market of competitors, this is financial modeling, unit economics. It’s about some big things, big stakes, big opportunities that you can go to. An example is Yandex.</p><p>When Yandex was doing search, it saw an opportunity in a taxi and went to this market. But before entering the taxi market, they analyzed several directions and tested them, that is, these are such great business opportunities.</p><h3><em>4. Product Discovery Track</em></h3><p>It consists of:</p><p>backlogs of symptoms and problems;</p><p>– user research;</p><p>– A/B testing;</p><p>- Prototyping and UX testing.</p><p>As a result, we get justified initiatives, as an increment, that is, it is very important to conduct a demo before development, and when we talk about product Discovery, if we use the same analogue with Yandex.Taxi, then at this stage we are exploring how to improve user experience in within the framework of the “taxi” product, what can be offered to a person so that he feels good, he would be happy to use a taxi, and so on.</p><h3><em>5.Delivery Track</em></h3><p>At this stage, the tasks are already ready, they are justified, it is clear what to do. Tasks are taken in sprints, engineers write code — they perform grooming when they decompose tasks into subtasks (subtasks). After the sprint, there are demonstrations (sprint reviews), after the reviews — retrospectives. At the retrospective, they analyze the performance of the sprint, how it was possible to remove certain obstacles, what can be done to reduce the queues, thereby lowering the so-called Time-to-market (T2M).</p><h3><em>6. People Grow Track</em></h3><p>And the last track is the track of human development. The necessary prerequisites are profiles — who is Junior, Middle, Senior. Team development plans are an equally important prerequisite. They can be made in the form of starmaps — what competencies are missing, who else is needed — and, using the profiles and development plans of teams, you can draw up individual development plans for each manager and engineer.</p><p>Everyone has this development plan, individual goals to move according to this plan, grow, and receive feedback based on the 360 ​​assessment mechanism, which is held every six months. It is very important to preserve the loop principle here. Managers spend one on one with their employees, talk about a development plan or even a personal strategy about what a person wants, and help him develop. In this case, the leader goes to the level of a coach, which helps the employee grow.</p><p><strong>Important! </strong>When one of the parts of this system does not work, then you should not expect good quality. Only if you have all the components at a basic level can you have a working system, and your home will be beautifully equipped so that residents can live there, enjoy the conveniences and ergonomics that you laid in the foundation from the very beginning. The business will be able to grow the way you intended, thanks to this foundation, thanks to the organization of the work of people.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34ce674b4719" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to share Knowledge in an IT company]]></title>
            <link>https://webmisha.medium.com/%D0%BA%D0%B0%D0%BA-%D1%80%D0%B0%D1%81%D0%BF%D1%80%D0%BE%D1%81%D1%82%D1%80%D0%B0%D0%BD%D1%8F%D1%82%D1%8C-%D0%B7%D0%BD%D0%B0%D0%BD%D0%B8%D1%8F-%D0%B2-it-%D0%BA%D0%BE%D0%BC%D0%BF%D0%B0%D0%BD%D0%B8%D1%8F%D1%85-cebbf813d80a?source=rss-808e3df2a869------2</link>
            <guid isPermaLink="false">https://medium.com/p/cebbf813d80a</guid>
            <category><![CDATA[знания]]></category>
            <category><![CDATA[it-компания]]></category>
            <category><![CDATA[управление-знаниями]]></category>
            <dc:creator><![CDATA[Mikhail Sukhov]]></dc:creator>
            <pubDate>Mon, 29 Nov 2021 08:49:38 GMT</pubDate>
            <atom:updated>2022-08-13T15:26:54.246Z</atom:updated>
            <content:encoded><![CDATA[<p>I spoke at the <a href="https://www.volgablob.ru/ru/vb-trend-2021">VB Trend 2021</a> conference, where I talked about the sharing of knowledge in IT companies. Below is a video and a transcript of my speech.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QB7aUxXMuYBJZ8BQ51fVTA.jpeg" /></figure><p><strong>1. Start sharing knowledge in companies</strong></p><p>If we talk about knowledge and the lifetime of an employee, then the most critical moment is when he comes to the company. He doesn’t know anything. He needs to get on board very quickly and go a certain way. Various tools come to the rescue: checklists, bodysuits, etc.</p><p>Then he somehow lives and exists within some context, within the framework of a project or team. If we take the same Microsoft, it has a portal that you can look at: a specific employee; what kind of team; in which unit is located; which cluster contains this unit; What exactly does he do? and where he sits. And each employee has a personal Wikipedia about projects about his or her tasks, and without talking to him, without opening an Email, you can understand what is happening and what you are dealing with.</p><p>The manager plays a significant role in leading the employee along his career track. However, a systematic (systematic approach) is needed to describe it clearly and work like a clock for quick knowledge extraction.</p><p>We need a system around knowledge so that a person who works in a company understands the game’s rules — what should be in a team, in a project. It should describe it. There should be centers of expertise that can contact in case of assistance. And when he exists in a company, it is crystal clear to him how to grow and what knowledge helps him along the way.</p><p>It is possible to make decisions about whether an employee works well or badly based on his quarterly or annual performance, and after the Performance Review has been passed and a 360 assessment has been collected, you can understand whether the employee is above or below expectations, whether he exceeds the current level or not. And Wiki helps him answer frequently asked questions.</p><p>For example, an employee is constantly approached by a manager who deals with a CRM system and asks to talk about it. To avoid wasting an hour each time, he can describe the essential things about the CRM system on Wiki. A person can go in and read it. It is the first support line, and he can clarify expert questions with the employee.</p><p>If, after reading the Wiki, a person does not understand anything and comes up with fundamental questions about it, it is necessary to rewrite it. Then with each iteration, it will become more evident. It makes no sense to describe and constantly support some complex things that change often, but some simple things, for example, who is involved in the CRM system, what parts it consists of, which employee is responsible for what, contacts, you need to describe.</p><p><strong>2. How to overcome the zero step</strong></p><p>The zero-step problem is very acute. Let’s take the IT department for 100 product teams. Those who overcome the first zero step should be centers of expertise (guilds) — guys responsible for information security, quality assurance, performance, frontend, backend, and delivery. Their task is to write precisely how team practices should work and to translate this knowledge through Wikipedia, through confluence inside. There may be quite a few such people — 1–2 people are enough — for example, Staff Engineer, Senior+, experts in a particular area.</p><p>If we talk about teams, she needs to keep documentation: what happens to the team; what is this command; what does she do, etc., and so on. Now there is a very fashionable theme — Knowledge Management. There are Scrum-masters and a Knowledge Manager-master — a person responsible for maintaining knowledge so that there is up-to-date information on the project or the product. Therefore, the system must work from the level of centers of competence to the level of teams.</p><p>If we talk about people, all people are different, but generally, they can be divided into three frequently occurring segments.<br>The first segment is ready to accept any tool, for example, Knowledge Management. They say: “What cool things, we will introduce it, how much we missed it.” The second segment says, “I don’t know, we’ll see. We have worked without it. We need additional resources.” And the third segment says: “No, this is additional time. We will not spend our resources on this.”</p><p>Here the strategy is simple — to work with volunteers. They are located, they begin to act first, and the segment that looked doubtful looks at those who started and begins to pull themselves up. In the end, the third segment, which did not want to waste resources, remains in the minority. However, in addition to enthusiasm, there must be a project driver. It may be a technical or product director interested in this or a responsible Project Manager for implementing this project. It should not be a chaotic process that is not controlled.</p><p>So, the system is slow but transforming.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FzE4J1yPufew%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DzE4J1yPufew&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FzE4J1yPufew%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/457b028790c382d631fc1ba59408d253/href">https://medium.com/media/457b028790c382d631fc1ba59408d253/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cebbf813d80a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create goals based on OKR’s approach]]></title>
            <link>https://webmisha.medium.com/%D0%BA%D0%B0%D0%BA-%D1%81%D1%84%D0%BE%D1%80%D0%BC%D1%83%D0%BB%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D1%82%D1%8C-%D1%86%D0%B5%D0%BB%D0%B8-%D0%BF%D0%BE-okr-81448f3561b8?source=rss-808e3df2a869------2</link>
            <guid isPermaLink="false">https://medium.com/p/81448f3561b8</guid>
            <category><![CDATA[цели]]></category>
            <category><![CDATA[okr]]></category>
            <dc:creator><![CDATA[Mikhail Sukhov]]></dc:creator>
            <pubDate>Mon, 15 Nov 2021 07:49:51 GMT</pubDate>
            <atom:updated>2024-01-18T13:35:11.197Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is OKRs</h3><p>OKRs, which stands for Objectives and Key Results, is a popular goal-setting framework used by organizations to define and track their objectives and the measurable outcomes that indicate success. The main purpose of OKRs is to align teams and individuals with the overall strategic goals of the organization, fostering transparency, focus, and accountability.</p><p>Here’s a breakdown of the components of OKRs:</p><ol><li><strong>Objectives:</strong> Objectives are qualitative, aspirational goals that describe what an organization or team aims to achieve. They are typically concise, inspiring, and focused on the desired outcomes. Objectives provide direction and purpose.</li><li><strong>Key Results:</strong> Key Results are specific, measurable outcomes that indicate progress toward achieving the objectives. They are quantifiable and time-bound, providing a clear way to assess success. Key Results serve as the checkpoints or milestones that help teams stay on track.</li></ol><p>The structure of OKRs encourages ambition, transparency, and continuous improvement. Objectives should be challenging but achievable, and key results should be specific and measurable. Progress is regularly tracked and evaluated, often on a quarterly basis.</p><p>OKRs are widely used in various industries and have been popularized by successful companies, including Intel and Google. The framework helps organizations prioritize their efforts, improve communication, and ensure that everyone is working towards common goals. It’s a flexible system that can be adapted to different organizational sizes, structures, and industry contexts.</p><h3>Why is OKRs</h3><p>OKRs (Objectives and Key Results) serve several purposes and offer numerous benefits for organizations. Here are some reasons why OKRs are considered valuable:</p><ol><li><strong>Clarity and Focus:</strong> OKRs help provide clarity by articulating specific objectives and the key results that will indicate successful achievement. This clarity ensures that everyone in the organization understands the direction and priorities.</li><li><strong>Alignment:</strong> OKRs align teams and individuals with the broader organizational goals. When everyone is working towards common objectives, it promotes cohesion and prevents teams from working at cross-purposes.</li><li><strong>Transparency:</strong> OKRs foster transparency by making goals and progress visible to everyone in the organization. This transparency can enhance communication, collaboration, and understanding of how each person’s work contributes to the overall mission.</li><li><strong>Accountability:</strong> By setting measurable key results, OKRs create a sense of accountability. Team members know what is expected of them and are accountable for delivering on their commitments. Regular check-ins and evaluations provide opportunities to address challenges and make adjustments.</li><li><strong>Agility and Adaptability:</strong> OKRs are often set on a quarterly basis, allowing organizations to be agile and adapt to changing circumstances. If priorities shift or new opportunities arise, OKRs can be adjusted accordingly.</li><li><strong>Motivation and Engagement:</strong> Well-crafted OKRs inspire and motivate teams by providing a sense of purpose and achievement. Employees are more engaged when they understand how their work contributes to the overall success of the organization.</li><li><strong>Continuous Improvement:</strong> The regular cadence of setting, tracking, and reviewing OKRs facilitates a culture of continuous improvement. Teams can learn from both successes and failures, making adjustments to improve performance in subsequent quarters.</li><li><strong>Strategic Execution:</strong> OKRs help organizations execute their strategies by breaking down high-level goals into actionable and measurable steps. This strategic alignment ensures that day-to-day activities contribute to the long-term success of the organization.</li><li><strong>Adoption of Best Practices:</strong> OKRs have been successfully implemented by leading companies such as Google, Intel, and others. Leveraging the best practices established by these organizations allows others to benefit from a proven and effective goal-setting framework.</li></ol><h3>How to implement OKRs from the scratch</h3><p>As a manager aiming to implement the OKR approach in the Technical Department of our organization, the following five steps will guide the process:</p><p><strong>Step 1: Decide on the OKR Master</strong></p><p>During the initial 3–6 months of implementation, designate an OKR Master responsible for ongoing governance. This individual should gain in-depth knowledge about metrics and organizational connections across different layers. Unlike a Scrum Master or Agile Coach, the OKR Master must be an experienced Product Manager with a profound understanding of context, metrics, and the ability to formulate new metrics using product analytics.</p><p>The specific title may not carry significance, but within Google, this role is commonly referred to as Product Operations or ProductOps.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Flnf_xpc3ld0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dlnf_xpc3ld0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Flnf_xpc3ld0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f02d7652e9171c1eb80086c8273feb24/href">https://medium.com/media/f02d7652e9171c1eb80086c8273feb24/href</a></iframe><p><strong>Step 2: Build the Hierarchy of Metrics</strong></p><p>Develop a hierarchy of metrics, as OKRs are centered around measurable outcomes and a product management mindset. This involves establishing a logical connection between L2 OKRs for each team and high-priority metrics on L1, substantiated by mathematical reasoning. Avoid the common mistake of basing OKRs on Epics or Tasks and measuring progress as a percentage. Instead, focus on challenging the product and measuring user satisfaction, steering clear of a time-to-market approach.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0TarNKobCHw5T4hzdNfbzA.png" /></figure><p><strong>Step 3: Connect L0 and L1 OKRs</strong></p><p>Consistently link all levels from the Company (L0) to our Technical Department (L1). Identify relevant L0 OKRs for the Technical Department and align them with L1 OKRs. In the absence of L0 OKRs initially, utilize input from the CEO, encompassing strategy, KPIs, and other data to understand the department’s contribution to overall success. Conduct alignment meetings for better clarity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vFp0T1IPcqrjpE8Z-lkNWQ.png" /></figure><p><strong>Step 4: Connect L1 and L2 OKRs</strong></p><p>Establish a connection between L1 and the hierarchy of metrics to guide each team in formulating L2 OKRs. This phase is complex, requiring time to coach teams into becoming more outcome-oriented and customer-centric, especially if they are accustomed to traditional project management. Enhance teams’ product maturity quarter by quarter, fostering capabilities such as A/B testing and UX research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*z5Aeo-3RfHOv-mrS3QRp8g.png" /></figure><p><strong>Step 5: Set up Traction Meetings on L1/L2 OKRs</strong></p><p>Implement traction meetings to track progress on OKRs, encourage insightful discussions within the Product Management group, and gather inputs from VPs. This approach cultivates a mature product management culture founded on feedback, mutual learning, and data-driven discussions. Typically, L1 OKRs are set annually, while L2 OKRs are established quarterly, paralleling the sprint cycles (Scrum every two weeks) with OKRs reviewed monthly.</p><p>Here is an example of Level 0 (L0) OKRs within the United States-based company Uber:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eKdUYF-kKZ01AEu2gbrZDw.png" /></figure><h3><strong><em>What to read or to watch at the next step</em></strong></h3><ul><li>step 1: watch <a href="https://www.youtube.com/watch?v=mJB83EZtAjc">How Google sets goals: OKRs / Startup Lab Workshop</a> (1.20h, it’s very useful, and you will fully understand the process)</li><li>step 2: read <a href="https://www.whatmatters.com/resources/google-okr-playbook">Google’s OKR PlayBook</a></li><li>step 3: read book <a href="https://www.amazon.com/Measure-What-Matters-Google-Foundation/dp/0525536221">“Measure What Matters”</a> from John Doerr, who implemented OKRs in Google</li><li>step 4: watch <a href="https://www.coursera.org/learn/okr">OKR Certification: Leadership and Goal Setting</a> from John Doerr</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81448f3561b8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>