<?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 Despot Jakimovski on Medium]]></title>
        <description><![CDATA[Stories by Despot Jakimovski on Medium]]></description>
        <link>https://medium.com/@despot.jakimovski?source=rss-8525fb4b6497------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*gdNLryffIhrj0bLp4ngG-Q.jpeg</url>
            <title>Stories by Despot Jakimovski on Medium</title>
            <link>https://medium.com/@despot.jakimovski?source=rss-8525fb4b6497------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:40:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@despot.jakimovski/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[One on one retrospective]]></title>
            <link>https://medium.com/@despot.jakimovski/one-on-one-retrospective-423bfe4f2616?source=rss-8525fb4b6497------2</link>
            <guid isPermaLink="false">https://medium.com/p/423bfe4f2616</guid>
            <dc:creator><![CDATA[Despot Jakimovski]]></dc:creator>
            <pubDate>Mon, 20 Apr 2026 12:32:18 GMT</pubDate>
            <atom:updated>2026-04-20T12:32:18.165Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are just tuning in, this is part of the series of thoughts about stuff I encounter regarding Engineering Managers.. ^</p><p>Today’s pick is on 1:1 retros. To me, this is part of a selfimprovement process, or learning process that we ought to undertake. A revision of <a href="https://medium.com/p/f73e59eee9d8">the first “contracting” 1:1</a>. Often we find oureslves overwhelmed from too many meetings, and “97 things every EM should know” gives it as a reliever. Perhaps you could find this motivating, to take a step back. It might also open new possibilities.</p><p>To me the reality is that often we are restricted with time and “pulling the correct level” is the thing that is most important. So I would prescribe this as a trial, for ppl that appreciate it and benefit from it. Hence the most important question that you could ask (that resonated most with me) is “What is the least we could do and still have a valuable one-on-one meeting?”. Structure is important and I try it at least once with my team members. At that point I find out whether it is helpful to me or them.</p><p>Below is a list of items by “97 things every EM should know” that might be helpful.</p><p>Questions that you might ask yourself if you are not liking the 1:1s:</p><ul><li>What is my secret goal for these meetings?</li><li>What is my spoken goal for them?</li><li>What is the other person’s goal for them?</li><li>What is the company’s goal for them?</li><li>What would happen if we stopped doing them?</li><li>What parts are valuable to me and which feel like a waste?</li><li>What parts are valuable to them and which feel like a waste?</li><li>What is the least we could do and still have a valuable one-on-one meeting?</li><li>What do we need to add, subtract, change?</li></ul><p>Points that you might change in the 1:1s:</p><ul><li>How often you meet (it doesn’t have to be the same frequency with each person)</li><li>What time you meet (it doesn’t have to always be at the same time)</li><li>Who runs the meeting (how could you take turns running the meeting?)</li><li>Where you meet (consider a walking meeting or a breakfast meeting)</li><li>What preparation both of you do for the meeting (try more, or less, prep)</li><li>The agenda for the meeting</li><li>The goal of the meeting</li><li>The length of the meeting</li><li>The communication medium (face-to-face, telephone, Slack, Skype, etc.)</li><li>What you could combine it with (a meal, a walk, a commute, etc.)</li></ul><p>Lead the way..</p><h3>Reference</h3><p>My experience. :)<br>[1] <a href="https://www.linkedin.com/in/ACoAAABhf9EBElKVMD8r7Ld8mtftcyp43d7cOD0">Camille Fournier</a>, “97 Things Every Engineering Manager Should Know”, 2019, book<br>[2] Marcus Blankenship<br>[3] Dr. <a href="https://www.linkedin.com/in/ACoAAAHihN0BlojkMraMQYmhMDlKJR5RzgJtHG8">James Stanier</a>, “Become an Effective Software Engineering Manager: How to Be the Leader Your Development Team Needs”, 2020, book</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=423bfe4f2616" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OKRs for Engineering (Managers)]]></title>
            <link>https://medium.com/@despot.jakimovski/okrs-for-engineering-managers-82c718a1f92?source=rss-8525fb4b6497------2</link>
            <guid isPermaLink="false">https://medium.com/p/82c718a1f92</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[okr]]></category>
            <dc:creator><![CDATA[Despot Jakimovski]]></dc:creator>
            <pubDate>Sun, 05 Feb 2023 20:49:03 GMT</pubDate>
            <atom:updated>2023-02-05T20:49:03.957Z</atom:updated>
            <content:encoded><![CDATA[<p>In the oven… 😉</p><h3>Resources</h3><p><a href="https://medium.com/@despot.jakimovski/kpis-for-engineering-managers-2269077271e6">KPIs for Engineering (Managers)</a> <br>The <a href="https://www.linkedin.com/posts/despotjakimovski_kpis-for-engineering-managers-activity-7022898318837989376-CArd?utm_source=share&amp;utm_medium=member_desktop">“KPIs for Engineering (Managers)” Linkedin resource</a> for additional audience to comment, interact and share with.<br>Metrics for Engineering (Managers) (in the oven ..)<br><a href="https://www.scaledagileframework.com/metrics/">SAFe Metrics</a><br>Scrum Metrics <a href="https://www.atlassian.com/agile/scrum/scrum-metrics#:~:text=What%20are%20scrum%20metrics%3F,improve%20a%20team&#39;s%20agile%20journey.">1</a> <a href="https://www.scrum.org/resources/blog/how-12-principles-agile-manifesto-work-real-life">2</a></p><h3>Other:</h3><p><a href="https://medium.com/@despot.jakimovski/coaching-204a862eca63">Coaching</a></p><p>General <a href="https://medium.com/@despot.jakimovski/one-on-ones-7685e56dab32">One on ones</a> (for all seniority levels of managers):</p><p><a href="https://medium.com/@despot.jakimovski/cadence-1-1s-fd574db565b6">Cadence (1–1s)<br></a><a href="https://medium.com/@despot.jakimovski/agenda-1-1s-1b0cefd5d8c3">Agenda (1–1s)<br></a><a href="https://medium.com/@despot.jakimovski/first-contracting-one-on-one-f73e59eee9d8">First 1–1s</a><br>Prior to 1–1s <em>(in the oven ..)</em><br><a href="https://medium.com/@despot.jakimovski/during-an-one-on-one-23996f3ee7a5">During One-on-ones</a><br>After 1–1s <em>(in the oven ..)</em><br>Location (1–1s) <em>(in the oven ..)</em></p><p><strong>One-on-Ones for (Engineering) Manager of Managers</strong>:</p><p>Cadence (MoMs’ 1–1s) <em>(in the oven ..)</em><br>With whom? (MoMs’ 1–1s) <em>(in the oven ..)</em><br>Agenda (MoMs’ 1–1s) <em>(in the oven ..)</em><br>During a 1–1 (MoMs’ 1–1s) <em>(in the oven ..)</em><br>During Interviewing (MoMs’ 1–1s) <em>(in the oven ..)</em><br>1–1s with Senior Peers from other functions (MoMs’ 1–1s) <em>(in the oven ..)</em></p><h3>Reference</h3><p>My experience. :)<br>[1] <a href="https://www.amazon.com/Nicole-Forsgren-PhD/e/B0775YPSMZ/ref=dp_byline_cont_book_1">Nicole Forsgren PhD</a>, <a href="https://www.amazon.com/Jez-Humble/e/B003SNGS8E/ref=dp_byline_cont_book_2">Jez Humble</a>, <a href="https://www.amazon.com/Gene-Kim/e/B00AERCJ9E/ref=dp_byline_cont_book_3">Gene Kim</a> , <a href="https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339/ref=sr_1_1?crid=35W0452NXGXLA&amp;keywords=Accelerate&amp;qid=1669473730&amp;s=books&amp;sprefix=accelerate%2Cstripbooks-intl-ship%2C213&amp;sr=1-1">“Accelerate” book</a> (forward by <a href="https://martinfowler.com/">Martin Fowler</a>)<br>[2]<br>[3] <a href="https://www.linkedin.com/in/ACoAAABhf9EBElKVMD8r7Ld8mtftcyp43d7cOD0">Camille Fournier</a>, “The Manager’s path”, 2017, book<br>[4] <a href="https://www.linkedin.com/in/ACoAAAC0KdQBkikUIfCPY2nyso3lWQqRKXj_ViQ">Will Larson</a>, “An Elegant Puzzle: Systems of Engineering Management”, 2019, book<br>[5] Dr. <a href="https://www.linkedin.com/in/ACoAAAHihN0BlojkMraMQYmhMDlKJR5RzgJtHG8">James Stanier</a>, “Become an Effective Software Engineering Manager: How to Be the Leader Your Development Team Needs”, 2020, book<br>[6] <a href="https://www.linkedin.com/in/ACoAAABGxRoBnuBYhMjEI-IDRulBwJ2glEHG41U">Marcus F.</a>, <a href="https://lnkd.in/dghjKmQB">https://lnkd.in/dghjKmQB</a>, youtube videos</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82c718a1f92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[KPIs for Engineering (Managers)]]></title>
            <link>https://medium.com/@despot.jakimovski/kpis-for-engineering-managers-2269077271e6?source=rss-8525fb4b6497------2</link>
            <guid isPermaLink="false">https://medium.com/p/2269077271e6</guid>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[okr]]></category>
            <dc:creator><![CDATA[Despot Jakimovski]]></dc:creator>
            <pubDate>Sun, 22 Jan 2023 12:04:09 GMT</pubDate>
            <atom:updated>2023-02-05T20:50:10.551Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*SScTdWuRHWWzjwz3XGjCcA.jpeg" /></figure><p>For the impatient, glance at the key takeouts at the bottom. “Listen” button at the top for vision free while hiking 😉</p><p>For each KPI, follows: a paragraph about the KPI definition, benefits, what it measures, a paragraph on my experience with it (useful example of how I used it), and a <em>Tags</em> paragraph, so you can search each one in case you need to use it at a certain organizational level. Make sure you look at the benefit in order to understand whether you need to focus on it currently or phase it off for another time.</p><p>Starting with perhaps the most prioritized and frequently used¹ metric, <strong>Lead Time</strong>. Lead Time is the overall time to deliver an increment of software from the appearance of a new customer/PO work request in the workflow to deployment to live (complete SDLC). Measures <strong>continuous delivery</strong>. <strong>High level KPI</strong> useful for <strong>all engineering management levels</strong>, especially <strong>C-Suite</strong> as it gives insight into how effectively an organization delivers. The main <strong>benefit</strong>/outcome is <strong>increasing the organization’s ability to receive new features</strong> (increase ‘velocity’ of the delivery team) <strong>by shortening the Lead Time</strong>.<br>During my Pacesetting VPoE leadership, we maintained <strong>high level meetings with the SEMs</strong> where we discussed the Lead Time and an action plan on its improvement. <strong>SEMs were coming up with and driving the plan</strong>. It was the <strong>VPoE’s responsibility to refocus</strong> (by setting goals / OKRs or other) on the most impactful parts of the Lead Time, <strong>and enable the SEMs if required</strong>. We also used Lead Time in our Iteration Review meetings during SAFe or Scrum of Scrums within enablement companies to understand how the team(s) are doing. From there we analyzed what is offending and created an action plan.<em><br>Tags</em>: KPI Granularity = high level; Organizational Level = all; Key Organizational Level = C-suite; Eng Management Level = all; Key Eng Management Level = C-suite, Eng Manager of Managers;</p><p>Following up with <strong>Cycle Time</strong>, also prioritized high but this time by the most granular organizations, the eng team. Cycle Time starts when new work enters “in progress” (someone is working on it), and ends <a href="https://tulip.co/blog/cycle-vs-lead-vs-takt/">when the work is ready for releasing</a> or <a href="https://linearb.io/blog/cycle-time/#:~:text=Cycle%20Time%20Definition-,In%20software%20development%2C%20cycle%20time%20is%20the%20time%20from%20first,work%20started%20to%20work%20delivered.">after being released</a>. It is a <strong>dev metric</strong> that measures the efficiency of the dev process, its health. The main <strong>benefit</strong>/outcome is <strong>speeding up the dev process by finding bottlenecks and reducing them</strong>. <br>For example, as an SEM for a Pacesetting company, I found out that <strong>it took 20% of the time to do the E2E testing effort</strong>. By investigating, I identified that 60% of the time, a. manual testing tool was not used properly (manual testers were spending a lot of time questioning each other on already written manual test scenarios), and 40% of the time b. some of the E2E scenarios were written in a way that was testing part of the service (no proper E2E scenarios). The QA and I had a discussion and identified a few process changes that could be made to first tackle a. as we spent most of the time there. The next few iterations I checked regularly whether the new process is being followed, while paying attention to the QA quality bar — the minimum standards required so the work can be passed to the next phase. You need to make sure that the speed doesn’t lower the quality bar. While QA was finding the rhythm in improving a., we discussed and worked on b. We identified which ‘E2E’ tests are not proper, and checked whether there are tests for those in the appropriate level of the testing pyramid. An integration test, a PACT test here and there, and we reduced b. to near 0. We also doubled down on automating the critical areas, least brittle, manual E2Es. Automation was part of business as usual in the pacesetting company. <br>Similarly, I have (you could have) identified <strong>bottlenecks in</strong> other <strong>parts of SDLC</strong>. Developing tasks in a certain area, or technology, writing UTs, ITs, contract tests. For each, there is a different set of solutions. <br>Another <strong>example</strong>, while working in a Enablement Service company, by using Cycle time, in our SAFe process iteration, we identified that the <strong>acceptance of tickets (reviewing by the SEM for technical parts or PO for business parts) was slow</strong>, and it impacted the overall cycle time since some of the tickets were rejected later in the iteration. Similarly, yet another <strong>example</strong>, <strong>code reviews were lagging and creating the same issue</strong>. We agreed on at most 4hrs commit being unreviewed, and a short discussion (pairing) between the implementer and main reviewer on the task in order to discuss on the concept / direction of how it would be implemented. With this we prevented most of the late rejections. <br>If you haven’t figured it out so far, <strong>the better the Cycle Time, the better the Lead Time</strong>, as it is a subset. This is why the <strong>senior Engineering Managers</strong> (DoE, VPoE, C-level) <strong>will look at the Lead Time and request a more detailed inspection of the Cycle Time by the Engineering Managers or teams</strong>. <strong>The more autonomy (or the lesser enablement required by) the team or Engineering Manager shows in solving the Lead Time challenges, the more senior or ripe that team or Eng Manager is, and the more opportunities for growth will be given</strong>. The more senior the engineering manager is (highest c-level), the lower amount of time they have to explain how a challenge needs to be solved³⁴⁵⁶.<br><em>Tags</em>: KPI Granularity = narrow level; Organizational Level = team; Eng Management Level = SEM; Agile Framework = all;</p><p>The third KPI that is usually pretty high (2nd) in the priority of engineering operations¹ is <strong>Deployment Frequency</strong>. It is the frequency of deploying (the developed features) to live. Measures <strong>continuous delivery</strong>. It is a <strong>High level KPI</strong> used by both the (<strong>operations</strong>/devops) <strong>team</strong> and the <strong>senior eng management levels</strong>, as it gives insight into how fast the organization propagates changes to the customer. The main <strong>benefits</strong>/outcomes are <strong>a.</strong> the ability to <strong>get early feedback</strong> and with that, <strong>do changes in an isolated manner</strong>, rather then deploying a big chunk (epic), and having it dropping the customer use from only a subset of offending changes =&gt; spending more time and resources by fixing the dependent code and reducing the availability time of the non-offending code/features for the customers; <strong>b. time to market</strong> (reaching the customer sooner than your competitors). This is done by organizations through deploying <strong>rapidly small</strong> software <strong>increments to live</strong>. <br>When I entered a <strong>pacesetting company as an SEM</strong> I was given to manage 4 products (this was a company that grew by acquiring other products/companies). I managed one more product than the other SEMs (my first achievement — something that set me aside within the company). These <strong>products had no release for &gt;2 years</strong>. By <strong>measuring the Deployment Frequency KPI</strong>, setting it as part of the product’s OKRs (making it a priority), and hence <strong>understanding the challenges (in this case, lack of tests on all levels in the pyramid, lack of automation (of tests and deployment), …)</strong> and working on them with the team, I managed to make them <strong>releasable each quarter</strong>. Once I became a VPoE, I also worked on an <strong>initiative called ShipEvery7 days</strong>, in order to ripe the benefits a. and b. (check above). I drove the creation of the <strong>ShipEvery7 checklist</strong> for my organization (SEMs/teams/products). Made the products releasable every 7 days, proving the checklist impacting positively the delivery speed / deployment frequency. Once the SE7 checklist was presented, it was <strong>adopted by the whole organization of ~100+ products</strong> (another achievement of mine). With time, senior eng management was tasked with <strong>assessing which checklist items were most impacting and would take the least amount of time to automate. We automated part of it, and even further increased the delivery speed</strong>. <br>My <strong>experience with enablement companies</strong> shows that going into higher deployment frequency (DF) depends on different factors. For service companies, it depends on the client. I used to work for a client that had a high engineering maturity (usually after the product has years of tenure), the DF is high. When working with other types of clients, usually it meant that clients were <strong>aware of operations’ benefits</strong> (proposed by the service company), <strong>but the priority went into the development and operations was a side thing</strong>. In <strong>startup companies</strong>, depending on the leadership’s operational impact, they might have pushed for operations as a second priority, but it was <strong>all about problem solving, autonomy, usually with little time</strong>. A startup I used to work for had the <strong>Lead Time, NetPromoterScore prioritized</strong> and had the <strong>Deployment Frequency right around the corner</strong>. So a <strong>skeleton (the minimum automated operations) for deployment</strong> were there, but there were a lot of manual steps and the edge cases for deployment were part of the knowledge of the developers and operations (devops) employees.<br>It’s all about priorities, but I can’t stress enough the importance of <strong>having at least the minimum automated operations to make quick deployments as a second priority done after/while you are looking at the Lead Time (or Cycle Time)</strong>.<br><em>Tags</em>: KPI Granularity = high level; Key Organizational Level = (Operations) Team, Senior Eng Management; Key Eng Management Level = (Operations) SEM, Eng Manager of Managers;</p><p>What follows below is a list of other KPIs ordered by frequency that I (or others) used. Though, you might not be using them in this order. Y<strong>ou would be faced with a challenge, and by looking at the benefit from a certain KPI, decide which one is important to you</strong> (for your current quarter for example). <strong>Some</strong> of the KPIs will be <strong>part of business as usual</strong>, but <strong>you need to choose one to three KPIs that will be the ones that will make a big positive impact for your highest eng challenge(s)</strong>. <br><strong>Choosing</strong> the appropriate metrics <strong>depends on</strong>:<br>- <strong>the company culture</strong> (for example, in a top-down company most of the KPIs and OKRs will be generated and required of you, whereas in a flat hierarchy, you would need to generate these yourself or with your team)<br>- <strong>the phase the product or company is in</strong> (in one company, we had a phase where we were doing investigations (RCAs/5whys) intensively as we noticed that the solutions from previous quarters were not reducing defects greatly for instance; than we had a phase where we focused on ship every 7 since we wanted to get faster feedback from clients and time to market; than a phase to focus on reducing costs; a phase to focus on SEMs writing tech deep dive improvements for engineers and VPoEs writing improvements for SEMs. In an enablement company, you might be just starting with the team and it might be crucial for you to create relationships and psychological safety with your team and keep just the business as usual metrics for a period without creating one to three high level focused challenging metrics)<br>- <strong>your role</strong> (the more senior eng management role you have, the more it would be expected of you to define the high level metrics; if lower level eng management role, than you need to define narrower metrics; if you are a TL you might be able to propose changes in metrics, but might be that you need to come up with metric improvements during an iteration review ceremony)<br>- <strong>organizational level</strong> (metrics might be required to be generated by (group of) groups or even on an individual level)<br>- other<br>, <strong>so make sure you understand the environment and conditions you are in, and try to find a creative solution within the limits of that environment</strong>. Don’t make the mistake of rushing to change the limits immediately. <strong>First, understand and learn and practice within the limits for a period, and then and only then, think about challenging the limits</strong>. <strong>You might think that you see an opportunity, but might be mistaken or the team/organization might not be ready for that change, so make sure you are creative within the limits</strong>.</p><p><strong>4. Time to restore service</strong><br><strong>5. </strong>Sprint/iteration <strong>Velocity</strong> or Delivered Story Points <br><strong>6. Sprint Burndown</strong> <br><strong>7. Release Burndown</strong><br><strong>8. Flow Efficiency</strong><br><strong>9. Escaped defects</strong> <br>Defect Containment (Reduce the trailing 4 weeks average incoming defect rate from Qn(QarterN) baseline of &lt;x&gt; by &lt;y&gt;) was one of our <strong>high level KPI</strong>s in order to improve on the <strong>quality</strong> of the product. <br><strong>10. Code Coverage</strong><br><strong>11. Sprint Target Completion</strong> <br><strong>12. Cumulative flow</strong> <br><strong>13. Code Stability or Code Churn</strong> <br><strong>14. Change fail rate</strong> <br><strong>15. Code Simplicity</strong></p><p>Different tools like <a href="https://docs.sonarqube.org/latest/user-guide/metric-definitions/">SonarQube have some of the above narrower engineering KPIs cover and might give even more narrower KPIs</a> that you can use depending on your challenge.</p><h4><strong>Quality</strong> metrics counterweight for non-quality metrics</h4><p>If you dive deep into bettering your performance non-quality metrics, you might end up reducing the quality of your output. So counterweight your non-quality metrics (like Cycle Time, Deployment Frequency…) with your quality metrics (like Escaped Defects), Definition of Done, Definition of Ready, and any other Quality Bars existing between different type of teams within your organization (we used to have a Quality Bar for a architectural deliverable produced by the Architecture Teams that was required by the Feature teams — we wouldn’t pass a deliverable if it didn’t pass the QB) or between the organization and the customer (Net Promoter Score).</p><h4>A few words about agile methodology metrics</h4><p>All agile practices Kanban, Scrum, Scrum of Scrums, SAFe… rely on some set of metrics. <br>The bare minimum for Kanban, for instance, is Velocity. For high level metrics (like OKRs, that I am going to be discussed in another post — in the oven), Scrum has a Sprint Goal Success, SAFe, for instance, has iteration Objective and iteration Key Results (OKRs) and even further it has an OKR for the whole PI (Product Increment — usually lasting for a quarter). <br>It might be the case that you are working under some less restrictive agile process like Scrum where few metrics are recommended. In that case, if you require, you will go into defining your own KPIs and OKRs. On the other hand, you might be working within a more structured agile methodology, like SAFe, and then a lot of the metrics will be recommended. For instance, <a href="https://www.scaledagileframework.com/metrics/">SAFe</a> has Value Stream KPIs like Retention (Software Product), Net Promoter Score (Fulfillment), Mean Time to Resolution (Support), has its OKR structure (as described above) and Flow metrics (for instance Flow Time, that is equivalent to the Lead Time). For more, check also <a href="https://www.scaledagileframework.com/metrics/">the SAFe “Four Critical Success Factors for Effective Measurement”</a>.</p><h3>Key takeouts</h3><p>How do you choose the metrics? Y<strong>ou would be faced with a challenge, and by looking at the benefit from a certain KPI, decide which one is important to you</strong> (for your current quarter for example). Good start to choose from is the ordered list I show in <a href="https://medium.com/@despot.jakimovski/kpis-for-engineering-managers-2269077271e6">the post</a>, check any tools for narrower KPIs (like SonarQube) and check the recommendations from the agile methodology you follow (for instance <a href="https://www.scaledagileframework.com/metrics/">SAFe</a>). <strong>Some</strong> of the KPIs will be <strong>part of business as usual</strong>, but <strong>you need to choose one to three KPIs that will be the ones that will make a big positive impact for your highest eng challenge(s)</strong>.</p><p><strong>Choosing</strong> the appropriate metrics <strong>depends on</strong>:<br>- <strong>the company culture</strong> <br>- <strong>the phase the product or company is in</strong> <br>- <strong>your role</strong> <br>- <strong>organizational level</strong><br>- other<br>, <strong>so make sure you understand the environment and conditions you are in, and try to find a creative solution within the limits of that environment</strong>. Don’t make the mistake of rushing to change the limits immediately. <strong>First, understand and learn and practice within the limits for a period, and then and only then, think about challenging the limits</strong>. <strong>You might think that you see an opportunity, but might be mistaken or the team/organization might not be ready for that change, so make sure you are creative within the limits</strong>.</p><p><strong>Counterweight your non-quality metrics</strong> (like Cycle Time, Deployment Frequency…) <strong>with your quality metrics</strong> (like Escaped Defects), <strong>Definition of Done, Definition of Ready</strong>, <strong>and</strong> any other <strong>Quality Bars</strong> existing between different type of teams within your organization (we used to have a Quality Bar for a architectural deliverable produced by the Architecture Teams that was required by the Feature teams — we wouldn’t pass a deliverable if it didn’t pass the QB) or between the organization and the customer (Net Promoter Score).</p><p>Check <strong>above</strong> for the ordered by frequency (of need) <strong>15 KPIs</strong> that helped me in my career.</p><p>Looking forward to hearing your questions and comments on experiences. 😉 Feel free to do it in public or in private.</p><h3>Resources</h3><p>The <a href="https://www.linkedin.com/posts/despotjakimovski_kpis-for-engineering-managers-activity-7022898318837989376-CArd?utm_source=share&amp;utm_medium=member_desktop">“KPIs for Engineering (Managers)” Linkedin resource</a> for additional audience to comment, interact and share with.<br>Metrics for Engineering (Managers) (in the oven ..)<br><a href="https://medium.com/@despot.jakimovski/okrs-for-engineering-managers-82c718a1f92">OKRs for Engineering (Managers) (in the oven ..)</a><br><a href="https://www.scaledagileframework.com/metrics/">SAFe Metrics</a><br>Scrum Metrics <a href="https://www.atlassian.com/agile/scrum/scrum-metrics#:~:text=What%20are%20scrum%20metrics%3F,improve%20a%20team&#39;s%20agile%20journey.">1</a> <a href="https://www.scrum.org/resources/blog/how-12-principles-agile-manifesto-work-real-life">2</a></p><h4>Other:</h4><p><a href="https://medium.com/@despot.jakimovski/coaching-204a862eca63">Coaching</a></p><p>General <a href="https://medium.com/@despot.jakimovski/one-on-ones-7685e56dab32">One on ones</a> (for all seniority levels of managers):</p><p><a href="https://medium.com/@despot.jakimovski/cadence-1-1s-fd574db565b6">Cadence (1–1s)<br></a><a href="https://medium.com/@despot.jakimovski/agenda-1-1s-1b0cefd5d8c3">Agenda (1–1s)<br></a><a href="https://medium.com/@despot.jakimovski/first-contracting-one-on-one-f73e59eee9d8">First 1–1s</a><br>Prior to 1–1s <em>(in the oven ..)</em><br><a href="https://medium.com/@despot.jakimovski/during-an-one-on-one-23996f3ee7a5">During One-on-ones</a><br>After 1–1s <em>(in the oven ..)</em><br>Location (1–1s) <em>(in the oven ..)</em></p><p><strong>One-on-Ones for (Engineering) Manager of Managers</strong>:</p><p>Cadence (MoMs’ 1–1s) <em>(in the oven ..)</em><br>With whom? (MoMs’ 1–1s) <em>(in the oven ..)</em><br>Agenda (MoMs’ 1–1s) <em>(in the oven ..)</em><br>During a 1–1 (MoMs’ 1–1s) <em>(in the oven ..)</em><br>During Interviewing (MoMs’ 1–1s) <em>(in the oven ..)</em><br>1–1s with Senior Peers from other functions (MoMs’ 1–1s) <em>(in the oven ..)</em></p><h3>Reference</h3><p>My experience. :)<br>[1] <a href="https://www.amazon.com/Nicole-Forsgren-PhD/e/B0775YPSMZ/ref=dp_byline_cont_book_1">Nicole Forsgren PhD</a>, <a href="https://www.amazon.com/Jez-Humble/e/B003SNGS8E/ref=dp_byline_cont_book_2">Jez Humble</a>, <a href="https://www.amazon.com/Gene-Kim/e/B00AERCJ9E/ref=dp_byline_cont_book_3">Gene Kim</a> , <a href="https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339/ref=sr_1_1?crid=35W0452NXGXLA&amp;keywords=Accelerate&amp;qid=1669473730&amp;s=books&amp;sprefix=accelerate%2Cstripbooks-intl-ship%2C213&amp;sr=1-1">“Accelerate” book</a> (forward by <a href="https://martinfowler.com/">Martin Fowler</a>)<br>[2] <br>[3] <a href="https://www.linkedin.com/in/ACoAAABhf9EBElKVMD8r7Ld8mtftcyp43d7cOD0">Camille Fournier</a>, “The Manager’s path”, 2017, book<br>[4] <a href="https://www.linkedin.com/in/ACoAAAC0KdQBkikUIfCPY2nyso3lWQqRKXj_ViQ">Will Larson</a>, “An Elegant Puzzle: Systems of Engineering Management”, 2019, book<br>[5] Dr. <a href="https://www.linkedin.com/in/ACoAAAHihN0BlojkMraMQYmhMDlKJR5RzgJtHG8">James Stanier</a>, “Become an Effective Software Engineering Manager: How to Be the Leader Your Development Team Needs”, 2020, book<br>[6] <a href="https://www.linkedin.com/in/ACoAAABGxRoBnuBYhMjEI-IDRulBwJ2glEHG41U">Marcus F.</a>, <a href="https://lnkd.in/dghjKmQB">https://lnkd.in/dghjKmQB</a>, youtube videos</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2269077271e6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enablement and Pacesetting leadership]]></title>
            <link>https://medium.com/@despot.jakimovski/enablement-and-pacesetting-leadership-dc022abc2090?source=rss-8525fb4b6497------2</link>
            <guid isPermaLink="false">https://medium.com/p/dc022abc2090</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[pacesetting]]></category>
            <category><![CDATA[enablement]]></category>
            <dc:creator><![CDATA[Despot Jakimovski]]></dc:creator>
            <pubDate>Tue, 17 Jan 2023 11:34:53 GMT</pubDate>
            <atom:updated>2023-01-17T11:49:30.857Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/813/1*WfI4rzz-6lK1WkSkgY_DIw.jpeg" /></figure><p>I want to give my take on enablement and pacesetting from the perspective of someone that worked in a large pacesetting organization (working on both startup and other business products - think Amazon or a pacesetting startup), and small and large enablement companies (think Accenture service company or any small, medium, large product company). The <strong>unique</strong> set of companies I have been part of give yet another <strong>take on what enablement and pacesetting</strong> can mean, so read up if you are into either 😉.</p><p><strong>Both types of leadership should be ordered sequentially in the path of leading when the company culture focuses on one and uses the second to some degree.</strong> So why sequentially?! <strong>Enablement</strong> revolves around motivation, helping, creating a buy-in, and creating a healthy challenge. This <strong>comes first</strong> and it is based more on the experience and sparse data on the challenges. Pacesetting revolves around performance data. Here, extensive data (like KPIs, OKRs and other) are the driver. Pacesetting culture requires leaders to understand the data and navigate the path to the better project/product/company state. Pacesetting requires motivation through data. <strong>Pacesetting characteristics would come second</strong> to enablement, as they are used to check the insights that come from observing the system using mostly your experience (through enablement).</p><p>Although both can be used in conjunction, <strong>companies focus on one of them</strong>. The reason for this is <strong>time</strong>. Neither a person, nor an organization can do everything. There needs to be focus on something. <strong>It is hard, especially for C-level leaders, to align everyone on both</strong>. <strong>Smart people (and organizations) focus on one, and use the other type of leadership to some extent</strong>, which is quite demanding and requires experience and effort.</p><p>Once a challenge is found, investigation follows (with different techniques like root cause analysis-RCAs, 5 whys e.t.c.), and offending behavior (the behavior causing challenge(s)) is found. Once the offending behavior is found, it is communicated in order for 1. acceptance to set in, 2. a plan to be created on how to remove the offending behavior when the situation happens, and 3. apply the corrective plan when the situation happens again. This is the postulate of personal and organizational growth and the way each problem is solved. <br>The other part of the process is deciding <strong>what to do when the corrective actions don’t change the offending behavior</strong>, and how many tries should be enough. There are different tools to handle this. One being <strong>a. tying the failures to the motivation for growth.</strong> One of the keys to enablement is to understand the (career and private) motivations of the people you lead, using the carrot rather than the stick. If the person with offending behavior understands that they are not going to get to the point where they wanna be (where they are motivated to go), then they will think twice about not changing the behavior. Another one is <strong>b. rotating the person/team with the offending behavior</strong> to another team, organization or client (in service companies). There could also be the case of <strong>c.</strong> someone <strong>being fired</strong>, usually as a last resort. There are other tools in the leadership sack apart from these. <br>Even though either leadership or company can use any of these, from my experience, I could witness that (predominantly) <strong>enablement companies tend to use a., and b. and almost never go to c., and pacesetting companies use the motivation of c. to a large extent.</strong> The later do this as they want quick results, and the organization is set up in such a way to speed up every process, perhaps growing the people faster, with the downside of additional pressure, and not leaving too much space for communication, understanding each position and working on it to a higher extent. In pacesetting companies the motivation is tied to the performance and not always there is space/time left for understanding the person’s career and personal motivations in order to impact them to change their behavior. They usually, additionally motivate financially. Enablement companies tend to ripe the benefits of psychological safety, but growth happens slower compared to pacesetting companies. It does happen though. Speed depends on additional aspects of the company culture.</p><p><strong>Setting up processes for generating performance data can be taken as invasive</strong>, regardless of the type of leadership culture. As enablement companies tend to invest less time in generating performance data (KPIs, OKRs and other engineering metrics), the invasive feeling is lower (and psychological safety is higher). There might be a couple of components <strong>why the invasive feeling arises</strong>. Either <strong>a. the person feels responsible and skillful enough to be let alone to take care of a certain challenge</strong>, and might take this as mettling in their own affairs; <strong>b. the person is slacking and want to abuse</strong> the lack of monitoring to keep doing what they want; or <strong>c. performance data is misused to punish without grounds</strong> (in case when the bigger picture is not taken into consideration), causing the person to do a push back (hiding from the stick — think, the carrot and stick analogy). From my experience and in my opinion, I am (and expect others to be) ok with the extent of metrics being requested, up to the limits of time available for metrics of the type of company culture or leadership style. Metrics can always be beneficial if leaders/companies use them with the right intent, to increase the understanding of the reality and lower the subjectivity. Like anything, performance data (dominant in pacesetting leadership) can be misused (depends on the leader/culture), but then again, higher subjectivity from following your experience and guts mostly (dominant in enablement leadership), can be misused. <strong>As an extreme, I have been part of a company where we were monitored on which applications we used and how much time, having screenshots made every 10 min from the desktop, making a repository of data that can help leaders (me being part of the leaders and the one being monitored as well) to understand how someone that is more performant uses their time compared to someone that is a lower performer and have a conversation to improve their behavior.</strong> On the other side, they were also, although very rarely, misused. It all depended on the leader and sub-organization. As for any challenge, misuse, disagreement, it should be reported and we should have the faith in the leadership that this will be changed. Eventually we have a chance of leaving that leader/organization, if they don’t change the offending behavior. My point here being is that performance data is good, if the company/leader/team has or requires the time for it.</p><p>In my opinion, <strong>neither leadership type is better or both are good :)</strong> . Performance data has the caveat of being localized (not taking the whole picture into consideration), so the key when using <strong>pacesetting</strong> is to <strong>choose the metrics better</strong>. If some don’t conform with your experience and gut feeling, then you would need to investigate why and create new ones. Obviously not always leaders have time to do this for each metric challenge (<strong>prioritizing on the most impactful</strong>), but they do <strong>need to try</strong>. Otherwise citing data to make decisions without checking your experience would lead to unexpected results, long term. The upside of pacesetting is that data, however localized, <strong>doesn’t lie or is subjective. It builds confidence about reality.</strong> <br>On the other hand, <strong>enablement</strong> does <strong>impact the moral and performance tenfold</strong> by providing psychological safety, an environment where people can come closer to fulfilling their potential. The main downside here being <strong>subjectivity</strong> to an extent. <br><strong>Abuse</strong> by people (given our human nature and the company culture) <strong>can happen in both, so having a check on this is crucial to the success</strong> of each style of leadership.</p><p>— — —</p><p>For additional audiance to comment, interact and share with check the <a href="https://www.linkedin.com/posts/despotjakimovski_enablement-and-pacesetting-leadership-activity-7021078717246451712-MlZM?utm_source=share&amp;utm_medium=member_desktop">Enablement and Pacesetting Leadership Linkedin resource</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dc022abc2090" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[First (contracting) one-on-one]]></title>
            <link>https://medium.com/@despot.jakimovski/first-contracting-one-on-one-f73e59eee9d8?source=rss-8525fb4b6497------2</link>
            <guid isPermaLink="false">https://medium.com/p/f73e59eee9d8</guid>
            <category><![CDATA[one-on-one]]></category>
            <category><![CDATA[contracting]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[first]]></category>
            <category><![CDATA[engineering-management]]></category>
            <dc:creator><![CDATA[Despot Jakimovski]]></dc:creator>
            <pubDate>Thu, 10 Nov 2022 00:10:04 GMT</pubDate>
            <atom:updated>2022-11-10T00:21:15.844Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J5NdYC-ElCKO2aX0p_FNyA.jpeg" /></figure><p>For the impatient, glance at the key takeouts at the bottom. “Listen” button at the top for vision free while hiking 😉</p><p>Like every first, it’s different, exciting, full of potential and makes you a bit anxious. “This time I am going to set them closer to where they wanna go. It’s going to be even better than the last one…”.</p><p>Knowing the rules of any “game” sets you better for success. Same goes for one-on-ones. Many things are different, company culture, leadership style, characters. <strong>Knowing which (collaborative) “game” you both are playing, what the limits are, and where the boosters lie, will enable you to play it better and rip the benefits stronger.</strong> Most of these limits and boosters are part of both of you. So what better way of discovery than a couple of questions to contract what you are going to be doing. Hence the craft’s name for it, “contracting”³ (or “partnering with your manager”² if you look at it unidimensionally).</p><p>Ease them into it. Explain it is a simple exercise of asking questions to both of you that will inspire conversation of what is expected of either.</p><h3>The questions</h3><h4>The goals questions</h4><p>Finding the <strong>motivations of people</strong> and the overlap with <strong>what the product/service/project/company wanna do</strong>, will reveal a way to push any of them forward. So one of them <strong>will not stay a contained effort</strong>, but rather, once overlaps are revealed, <strong>they will allow for the action of either to inert the other into progress</strong>. The interest in improving in how code is structured, for instance, may improve on maintainability, extensibility and in turn improve on being more efficient, and on delivery of the product. This might also reveal an organizational skill for the person, that can implicate benefit in improving on processes, Convey’s law for team organization, e.t.c. In turn, the product being in the payment industry domain, might fulfill the employee’s need to work within better standards, or the possibility to explore or push the boundary of an architecture. A traveling domain might better satisfy the person’s need to contribute to the human condition, more than working on a gambling domain, for instance.</p><ol><li><strong>What are your career long term (3–10years) and short term (3–6months) goals?</strong></li><li>What are your private goals?</li></ol><p>Make sure they understand its safe for them to be open and the answers are going to work to their advantage. Explain how. Give your own answers as well. They will also understand how they can help you fulfill your goals.</p><p>If you get too generic answers make sure you ask follow up questions. For instance:</p><p>a. What would be valuable for you in the one on one?<br>b. What, more specifically, are you excited about? <br>c. Why did you change your team, company?</p><h4>The support questions</h4><ol><li><strong>How can your manager support you?</strong></li><li>How can your peers support you?</li><li>(for manager of managers) How can your team support you?</li><li><strong>Which areas you want most support with?</strong>³</li></ol><p>You should start practicing being silent even in your first one on one. Aim for up to 30% talking and rest of the time listening, and “resist the urge to suggest areas yourself if they are struggling to come up with them”³.</p><h4>The feedback receiving way questions</h4><p>Both of you want to understand how to fulfill as much of the feedback potential as possible. For that, you need to learn how it is most suitable for either to hear it. It’s one thing to master the skill of diplomatically relaying feedback. It’s even better when you know what makes the other less defensive. “Doing it in a way that you think they’ll be most able to hear it is invaluable”⁵.</p><ol><li>How would you like to receive feedback?</li></ol><p>If you need more specifics, drill down with some of the follow-up questions:</p><p>a. What medium do you like me to use (face-to-face, chat, email..)?<br>b. Routine? 1:1s or informal?<br>c. Transparent? Public or private?<br>d. “Do you prefer to get such feedback in writing so you have time to digest it, or are you comfortable with less formal verbal feedback?”¹</p><h4>The limits questions</h4><p>To me, these are the most interesting questions. Most are focused on what to do. But what not to do brings so much finesse to the one-on-ones. It reveals a big part of the mojo.</p><ol><li><strong>What can be a challenge for us working together?</strong></li></ol><p>Keep in mind, also, it is fine if they come up with preconceptions about you. This will change so the answers will change as well. Its important to start with something.</p><p>2. <strong>What makes you grumpy?</strong>¹<br>3. How would you manifest grumpiness (body, vocally…)?</p><p>If you know the signs of a negative feeling, you would be able to change the behavior. Grumpy is great since it encompasses a lot of emotions. Some follow-up questions if you need to drill down:</p><p>a. How do you react to a variety of negative emotions: disappointment, frustration, and anger?³ <br>b. How do I know when you’re in a bad mood or annoyed?¹<br>c. Are there any manager behaviors that you know you hate?¹</p><p>4. What do we do when we notice that we are grumpy?</p><p>Make a plan on what to do so you get out of the situation. A good idea is to be able to be opened to each other and be able to share that when it happens.</p><h4>The <strong>confidentiality</strong> questions</h4><p>Some people want to be more visible to the bigger organization and some people wanna do their thing in private. Respecting this will help you move the person and product/company further.</p><ol><li>How confident is the content from our meetings?³</li></ol><p>This can be different for different parts of the organization. Think, their manager or peers.</p><h4>Going the distance</h4><ol><li>How do you treat yourself?</li></ol><p>Use this to accent a praise.</p><h3>The resolution</h3><p>To give a better chance to the contracting, think about posting them the questions before the meeting or placing them in the event. This will let them think about aspects they haven’t thought about before and provide a better quality for the first one-on-one.</p><p>“You started talking candidly, which should set the tone for further interactions.”³</p><p>You should also repeat this exercise in some time to reassess and be on top of things.</p><h3>The testemonials</h3><p>When leads asked how they felt about this formal format of contracting vs an informal approach, the following were some great insights in why contracting is valuable.</p><p>Although it might feel a bit more formal than usual, they love the grumpy question. They feel that nobody bothered to ask them and even they haven’t thought of that being a point of discussion, but when talked about, they felt it could be of big help.</p><p>They notice some aspects that they wouldn’t otherwise notice and explore.</p><p>The cadence announced by the first one on one felt like they are on a good path to find the right path to success on time instead of getting a late review at year’s end or quarterly.</p><h3>Three key contracting questions and the <strong>revelation</strong></h3><ol><li>What are your career and private long term and short term goals?</li><li>How would you like to receive feedback?</li><li>What makes you grumpy, how do I notice this and what do we do about it when we notice it?</li></ol><p>The revelation: “Nobody bothered to ask me what makes me grumpy and I never thought it would be so interesting and important to explore to me.”</p><h3>Summary of high level contracting questions</h3><ol><li><strong>What are your career long term (3–10years) and short term (3–6months) goals?</strong></li><li>What are your private goals?</li><li><strong>How can your manager support you?</strong></li><li>How can your peers support you?</li><li>(for manager of managers) How can your team support you?</li><li><strong>Which areas you want most support with?</strong>³</li><li>How would you like to receive feedback?</li><li><strong>What can be a challenge for us working together?</strong></li><li><strong>What makes you grumpy?</strong>¹</li><li>How would you manifest grumpiness (body, vocally…)?</li><li>What do we do when we notice that we are grumpy?</li><li>How confident is the content from our meetings?³</li></ol><h3>Resources</h3><p>0. <a href="https://medium.com/@despot.jakimovski/coaching-204a862eca63">Coaching</a></p><p>General <a href="https://medium.com/@despot.jakimovski/one-on-ones-7685e56dab32">One on ones</a> (for all seniority levels of managers):</p><p>1. <a href="https://medium.com/@despot.jakimovski/cadence-1-1s-fd574db565b6">Cadence (1–1s)<br></a>2. <a href="https://medium.com/@despot.jakimovski/agenda-1-1s-1b0cefd5d8c3">Agenda (1–1s)<br></a>3. <a href="https://medium.com/@despot.jakimovski/first-contracting-one-on-one-f73e59eee9d8">First 1–1s</a><br>4. Prior to 1–1s <em>(in the oven ..)</em><br>5. <a href="https://medium.com/@despot.jakimovski/during-an-one-on-one-23996f3ee7a5">During One-on-ones</a><br>6. After 1–1s <em>(in the oven ..)</em><br>7. Location (1–1s) <em>(in the oven ..)</em></p><p><strong>One-on-Ones for (Engineering) Manager of Managers</strong>:</p><p>8. Cadence (MoMs’ 1–1s) <em>(in the oven ..)</em><br>9. With whom? (MoMs’ 1–1s) <em>(in the oven ..)</em><br>10. Agenda (MoMs’ 1–1s) <em>(in the oven ..)</em><br>11. During a 1–1 (MoMs’ 1–1s) <em>(in the oven ..)</em><br>12. During Interviewing (MoMs’ 1–1s) <em>(in the oven ..)</em><br>13. 1–1s with Senior Peers from other functions (MoMs’ 1–1s) <em>(in the oven ..)</em></p><p><a href="https://www.linkedin.com/feed/update/urn:li:share:6996265093445378048/">The “First One-on-Ones” Linkedin resource</a> for additional audience to comment, interact and share with.</p><p>…</p><h3>Reference</h3><p>My experience. :)<br>[1] <a href="https://www.linkedin.com/in/ACoAAABhf9EBElKVMD8r7Ld8mtftcyp43d7cOD0">Camille Fournier</a>, “The Manager’s path”, 2017, book<br>[2] <a href="https://www.linkedin.com/in/ACoAAAC0KdQBkikUIfCPY2nyso3lWQqRKXj_ViQ">Will Larson</a>, “An Elegant Puzzle: Systems of Engineering Management”, 2019, book<br>[3] Dr. <a href="https://www.linkedin.com/in/ACoAAAHihN0BlojkMraMQYmhMDlKJR5RzgJtHG8">James Stanier</a>, “Become an Effective Software Engineering Manager: How to Be the Leader Your Development Team Needs”, 2020, book<br>[4] <a href="https://www.linkedin.com/in/ACoAAABGxRoBnuBYhMjEI-IDRulBwJ2glEHG41U">Marcus F.</a>, <a href="https://lnkd.in/dghjKmQB">https://lnkd.in/dghjKmQB</a>, youtube videos<br>[5] <a href="https://www.linkedin.com/in/larachogan/">Lara Hogan</a>, <a href="https://lnkd.in/dnxKqMdh">https://lnkd.in/dnxKqMdh</a>, blog</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f73e59eee9d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One-on-Ones for (Engineering) Manager of Managers]]></title>
            <link>https://medium.com/@despot.jakimovski/one-on-ones-for-engineering-manager-of-managers-acf90dc1832f?source=rss-8525fb4b6497------2</link>
            <guid isPermaLink="false">https://medium.com/p/acf90dc1832f</guid>
            <category><![CDATA[manager]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[one-on-one]]></category>
            <dc:creator><![CDATA[Despot Jakimovski]]></dc:creator>
            <pubDate>Sun, 02 Oct 2022 14:16:58 GMT</pubDate>
            <atom:updated>2022-11-14T20:15:57.232Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kwf0OminwUOBl98K8Aobaw.jpeg" /></figure><p>For the impatient, glance at the key takeouts at the bottom. “Listen” button at the top for vision free while hiking 😉</p><p>I have written a lot on the one-on-one topic in my previous blog posts, that cover the one-on-one topic from a general perspective. Whatever I’ve written so far are aspects that apply, in general, for both (Engineering) Manager of teams and (Engineering) Manager of managers. So why this direction? <strong>An (engineering) manager of a manager is a niche breed and you would not find a lot of knowledge shared on what is specific for these roles</strong>. Even the books I read on engineering management have scarce insights. <strong>You</strong> might have found yourself <strong>thrusted in </strong>leading a larger organizational structure, <strong>leading people that lead or manage/lead other people</strong>, without getting the applicable role name. Or you might have come into a natural progression of becoming a manager of managers as I once did. So this is for you, the person that is aching to find something tangible on the specifics of being an (engineering) manager of managers, or for <strong>the curious</strong> ;) .</p><p>So how do one-on-ones differ for manager of managers to manager of teams? To understand this we need to look at the different aims of the two types of managers/leaders.</p><h3>The (Eng) Manager of Managers difference</h3><p>Under the umbrella of a <strong>manager of teams</strong>, I would place::</p><ul><li>An (Engineering) Manager of a single team of individual contributors, or</li><li>Tech/Team Leads, in some case when there is no (Engineering) Manager or most of the management responsibilities have been delegated to the TL, or</li><li>An (Engineering) Manager of <strong>multiple teams</strong> of individual contributors, where all of the management and leadership activities are done by a single (eng) manager. The tech leads, if any, are more senior grade engineers that take on more of the technical leadership within the team.</li></ul><p>Under a <strong>manager of managers</strong>, on the other hand, I understand someone that leads other managers of teams (see above). Typically:</p><ul><li>Senior (Engineering) Manager (Senior EM)</li><li>Director of Engineering (DoE)</li><li>Vice President of Engineering (VPoE)</li><li>Head of Engineering/Development (HoE HoD)</li><li>Chief Technical Officer (CTO)</li></ul><p>Now that we clarified my blog posts’ terminology, let’s consider their aim.<br><strong>The manager of teams aims </strong>to improve, enable, help, unblock, guide <strong>on the individual contributions from the people they lead.</strong> <strong>The manager of managers aims at the teams and organization under the manager being led</strong>. The difference is one of magnitude. “New level of abstraction added (the managers)”¹.</p><p>How does the one-on-ones slice apply to this difference? Generally, <strong>the one-on-ones will revolve around the organization that the manager leads instead of their contributions</strong> (or rather this would be in the background). So you would be asking questions like</p><ul><li>“What is the health of the teams?”</li><li>“What is blocking your organization from delivering on the goals at hand?”</li><li>instead of asking</li><li>“How are you doing with your individual contribution tasks?” e.t.c.</li></ul><p>“You are accountable for not only your manager but all ppl that they lead.”⁴</p><h3>Characteristics of (Eng) Manager of Manager one-on-ones</h3><p><strong>The more senior roles you take, the more people’s problems you will deal with than other types of problems</strong>. So <strong>expect this in your one-on-ones</strong>. Have an efficient way of dealing with those, so you can allocate some time on other one-on-one aspects. I hear this over and over. The last instance where someone (Head of Development :) ) stressed that they deal with more people’s problems than others, was within my current company. Apart from it being my experience, this seems to be a hard set truth, so consider it :). Some leaders voice that as well⁴.</p><p>As you are thrusted into senior management/leadership roles, you would also be expected to define more of the vision yourself and you would be getting less feedback from your manager, then your peers. “Nobody will feel responsible to give you feedback”², so you would need to define your organization’s direction yourself. So, one of the <strong>key differences as a manager or managers</strong> is that you would be <strong>looking for feedback (to form the vision or direction) in the One-on-ones with the team that you lead and</strong> <strong>one-on-ones with your peers</strong>. I want to remind again, as you become more senior, you need to take into account more and more of your peer’s goals while considering how to achieve yours (check Building Relationships post for more).</p><p>If you haven’t switched between different engineering disciplines (like development, testing, operations e.t.c.), or you haven’t diversified on other discipline responsibilities within yours (eg.: taking on automated testing while developer), you will not have the expertise of the other. In this case, as you are given to lead a bigger organization, you might <strong>no</strong>t have the <strong>expertise in the discipline of some of your teams</strong>. <strong>Managing</strong> those <strong>requires</strong> keeping a firmer grip (<strong>asking questions around all aspects of management and progress</strong>, even around the ones that seem to go great).<br>“Follow up on all the little things until you are sure what you don’t need to follow up on”¹. Ex:</p><ul><li><em>Is recruiting happening?</em></li><li><em>Are the managers coaching the teams?</em></li><li><em>Goals written up?</em></li><li><em>Reviewed?</em></li><li><em>Status of project?</em></li><li><em>Production incident/postmortem happened/report read?</em></li></ul><h3><strong>The key aspect and the characteristics</strong></h3><p>An (engineering) manager of a manager is a niche breed and you would not find a lot of knowledge shared on what is specific for these roles. I already explained most on one-on-ones that applies to all types of managers/leaders, and this is specific to the niche.</p><ol><li>The (Eng) Manager of Managers one-on-ones will revolve around <strong>the organization that the manager, you lead, leads instead of their contributions.</strong> “You are accountable for not only your manager but all ppl that they lead.”⁴</li><li>Characteristics of (Eng) Manager of Manager one-on-ones:</li></ol><ul><li><strong>Expect in your one-on-ones that you will deal with more people’s problems than other types of problems</strong>.</li><li><strong>Look for feedback (to form the vision or direction) in the One-on-ones with the team that you lead and</strong> <strong>one-on-ones with your peers</strong>., as your manager will feel less and less responsibility to do so.</li><li>If you have <strong>no expertise in the discipline of some of your teams</strong>, <strong>managing</strong> <strong>those </strong>requires asking questions around <strong>all aspects </strong>of management and progress.</li></ul><h3><strong>Summary</strong></h3><p>A. An (engineering) manager of a manager is a niche breed and you would not find a lot of knowledge shared on what is specific for these roles.</p><p>B. <strong>You</strong> might be <strong>thrusted in </strong>leading a larger organizational structure, <strong>leading people that lead or manage/lead other people</strong>.</p><p>C. Under the umbrella of a <strong>manager of teams</strong>, I would place::</p><ul><li>An (Engineering) Manager of a single team of individual contributors, or</li><li>Tech/Team Leads, when most of the management responsibilities have been delegated to the TL, or</li><li>An (Engineering) Manager of <strong>multiple teams</strong> of individual contributors, where all of the management and leadership activities are done by a single (eng) manager.</li></ul><p>D. Under a <strong>manager of managers</strong>, on the other hand, I understand someone that leads other managers of teams (see above). Typically:</p><ul><li>Senior (Engineering) Manager (Senior EM)</li><li>Director of Engineering (DoE)</li><li>Vice President of Engineering (VPoE)</li><li>Head of Engineering/Development (HoE HoD)</li><li>Chief Technical Officer (CTO)</li></ul><ol><li><strong>The manager of teams aims </strong>to improve, enable, help, unblock, guide <strong>on the individual contributions from the people they lead.</strong></li><li><strong>The manager of managers aims at the teams and organization under the manager being led</strong>.</li><li>The difference is one of magnitude. “New level of abstraction added (the managers)”¹.</li><li><strong>the one-on-ones will revolve around the organization that the manager, you lead, leads instead of their contributions.</strong></li><li>“You are accountable for not only your manager but all ppl that they lead.”⁴</li><li>Characteristics of (Eng) Manager of Manager one-on-ones:</li><li><strong>Expect in your one-on-ones that you will deal with more people’s problems than other types of problems</strong>.</li><li><strong>looking for feedback (to form the vision or direction) in the One-on-ones with the team that you lead and</strong> <strong>one-on-ones with your peers</strong>., as your manager will feel less and less responsibility to do so.</li><li>you need to take into account more and more of your peer’s goals while considering how to achieve yours (check Building Relationships post for more).</li><li>If you have <strong>no expertise in the discipline of some of your teams</strong>, <strong>managing</strong> those <strong>requires</strong> <strong>asking questions around all aspects of management and progress</strong>.</li><li>“Follow up on all the little things until you are sure what you don’t need to follow up on”¹. Ex:</li></ol><ul><li><em>Is recruiting happening?</em></li><li><em>Are the managers coaching the teams?</em></li><li><em>Goals written up?</em></li><li><em>Reviewed?</em></li><li><em>Status of project?</em></li><li><em>Production incident/postmortem happened/report read?</em></li></ul><h3>Resources</h3><p>0. <a href="https://medium.com/@despot.jakimovski/coaching-204a862eca63">Coaching</a></p><p>General <a href="https://medium.com/@despot.jakimovski/one-on-ones-7685e56dab32">One on ones</a> (for all seniority levels of managers):</p><p>1. <a href="https://medium.com/@despot.jakimovski/cadence-1-1s-fd574db565b6">Cadence (1–1s)<br></a>2. <a href="https://medium.com/@despot.jakimovski/agenda-1-1s-1b0cefd5d8c3">Agenda (1–1s)<br></a> 3. <a href="https://medium.com/@despot.jakimovski/first-contracting-one-on-one-f73e59eee9d8">First 1–1s</a> <br>4. Prior to 1–1s <em>(in the oven ..)</em><br>5. <a href="https://medium.com/@despot.jakimovski/during-an-one-on-one-23996f3ee7a5">During One-on-ones</a> <br>6. After 1–1s <em>(in the oven ..)</em><br>7. Location (1–1s) <em>(in the oven ..)</em></p><p><strong>One-on-Ones for (Engineering) Manager of Managers</strong>:</p><p>8. Cadence (MoMs’ 1–1s) <em>(in the oven ..)</em><br>9. With whom? (MoMs’ 1–1s) <em>(in the oven ..)</em><br>10. Agenda (MoMs’ 1–1s) <em>(in the oven ..)</em><br>11. During a 1–1 (MoMs’ 1–1s) <em>(in the oven ..)</em><br>12. During Interviewing (MoMs’ 1–1s) <em>(in the oven ..)</em><br>13. 1–1s with Senior Peers from other functions (MoMs’ 1–1s) <em>(in the oven ..)</em></p><p>The <a href="https://www.linkedin.com/posts/despotjakimovski_one-on-ones-for-engineering-manager-of-activity-6982344120069439488-QbGz/">“One-on-Ones for (Engineering) Manager of Managers” Linkedin resource</a> for additional audience to comment, interact and share with.</p><p>…</p><h3>Reference</h3><p>My experience. :) <br>[1] <a href="https://www.linkedin.com/in/ACoAAABhf9EBElKVMD8r7Ld8mtftcyp43d7cOD0">Camille Fournier</a>, “The Manager’s path”, 2017, book<br>[2] <a href="https://www.linkedin.com/in/ACoAAAC0KdQBkikUIfCPY2nyso3lWQqRKXj_ViQ">Will Larson</a>, “An Elegant Puzzle: Systems of Engineering Management”, 2019, book<br>[3] Dr. <a href="https://www.linkedin.com/in/ACoAAAHihN0BlojkMraMQYmhMDlKJR5RzgJtHG8">James Stanier</a>, “Become an Effective Software Engineering Manager: How to Be the Leader Your Development Team Needs”, 2020, book<br>[4] <a href="https://www.linkedin.com/in/ACoAAABGxRoBnuBYhMjEI-IDRulBwJ2glEHG41U">Marcus F.</a>, <a href="https://lnkd.in/dghjKmQB">https://lnkd.in/dghjKmQB</a>, youtube videos</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acf90dc1832f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[During an One-on-one]]></title>
            <link>https://medium.com/@despot.jakimovski/during-an-one-on-one-23996f3ee7a5?source=rss-8525fb4b6497------2</link>
            <guid isPermaLink="false">https://medium.com/p/23996f3ee7a5</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[during]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[one-on-one]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Despot Jakimovski]]></dc:creator>
            <pubDate>Sun, 25 Sep 2022 16:24:46 GMT</pubDate>
            <atom:updated>2022-11-14T20:25:31.705Z</atom:updated>
            <content:encoded><![CDATA[<h3>During One-on-ones</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/777/0*TtjT8Gd_fCu7GWym" /></figure><p>For the impatient, glance at the key takeouts at the bottom. 😉</p><p><strong>If 1–1s were a language, <em>agenda</em> would be the <em>noun</em>. What you do <em>during a 1–1</em> would be the <em>verb</em>.</strong></p><p>Early in my career I have found out that one of the key aspects of getting engineering solutions is <strong>active listening</strong> as a tool in constructive argumenting to build a better solution or unblock a situation. I have mentored on active listening throughout my career with improved outcomes for the mentees’ goals. Yet, even at a senior management level, I sometimes caught myself discussing more than required at the expense of the employee not sharing enough. Did you feel the same? Being heard feels natural to all people. We all have information, ideas and some aspects that we feel the others need to know about. So, active listening is something you need to train and pay attention to, as a leader, in order for you to make a positive impact.</p><p>Of course, you need to cut short lengthy conversations especially in case of time pressure. It also depends on the meetings. If you are in a meeting where you need to relay some aspects to the ones that you are leading, you would need to speak more than listen. Though in 1–1s, you should be definitely <strong>actively</strong> listening.</p><h3><strong>Look for the “Call for help”</strong></h3><p>The main behavior you need to train yourself to do is <strong>listen and absorb the context</strong> since whatever the employee discusses is a prelude. The key for you to jump in is when the employee directly asks for help or says they are struggling with a challenge. What if they never reach this point? You <strong>use guided questioning</strong>, the companion to active listening, <strong>to direct them towards the call for help</strong>.</p><p><strong>Avoid intervening before the call for help</strong>, even if you want to speed up the improvement of an employee or organization and feel tempted to jump in. It may be taken as <strong>intrusive, condescending</strong> and might have a neutral or <strong>negative impact</strong>. Apart from that, you might <strong>give a solution for a problem that doesn’t exist</strong>. The employee might want to take you to another “call for help”. This meeting also, primarily, is for them to grow.</p><p>Here are some guiding question examples from Dr. James³, that I would group into the following.</p><p>The employee not sharing:</p><ul><li>“How has your work been going this week?”</li><li>“What are you working on today?”</li><li>“Tell me about those production issues we had last week.”</li></ul><p>Subject seems to go curiously perfect:</p><ul><li>“Do you think that we’re measuring our uptime well enough?”</li><li>“How best could we ensure that we’ve got all of the right metrics being logged ahead of time?”</li></ul><p>The employee is bottling up feelings:</p><ul><li>“How are you feeling about our deadline in June?”</li></ul><h3>Taking notes and who does it?</h3><p>It should be an agreement between you and the employee. I always try to motivate <strong>employees to type in key aspects from a conversation</strong>. This way we both see which part of the context is important to them. I also motivate them to <strong>type in their APs</strong> (action points) so it engraves better in their mind. <strong>You do the same for</strong> the aspects you believe are important from the context, <strong>the “call for help”</strong> and your (or some other stakeholder) APs. In contrast, Camile¹ and Dr. James³ proposed that the manager take all notes.</p><p>The <strong>goal</strong> of taking notes is to build:</p><ol><li><strong>transparency</strong></li><li><strong>trust</strong> towards you <strong>and acceptance</strong> of you (APs that you will be doing on behalf of them).</li><li>a “context of what has happened”¹</li></ol><p>I would leave 5min before the end of the meeting in order to “review the notes at the end of the meeting”³. You can also alternatively, “leave time at the end to add notes … if you’re distracted by having a computer open in front of you during the meetings”.¹</p><h3><strong>The andon cord</strong></h3><p><strong>Keep a lookout on the signal for uncomfortable subjects (the andon cord) that you agreed to in your contracting during your first one-on-one, and act accordingly</strong>.³ Reassess whether you need to go into the topic if it’s too personal or too off topic. Some subjects might be better handled by someone else in (or out of) the organization.</p><h3><strong>Coaching during a 1–1</strong></h3><p>As explained in <a href="https://medium.com/@despot.jakimovski/coaching-204a862eca63">my Coaching blog post</a>, depending on seniority level and employee’s place in the learning curve of the subject, you should start from coaching and, if required, move to the right of mentoring, directing, intervening.⁴<br><strong>For important issues, </strong>you should <strong>direct or intervene</strong>, as the gears will stop moving otherwise.<br><strong>For unimportant and not urgent issues, grow the capability of the employee(s)/organization. </strong>You can <strong>move to the left of the framework (depending on the employee’s place in learning curve and seniority)</strong>. The issue is not important so there is space for the employee to wrestle with the issue in order to build knowledge. What you do stays longer in memory, rather than just hearing it. Do it twice, and then it becomes a reflex.</p><p>If an issue is repeating, you need to move to the right of the framework and give clearer feedback. <strong>Great example</strong>⁴ would be:</p><ul><li>If they are complaining about the relationship with the PO or the delivery manager, you start coaching them on how to approach that relationship.</li><li>If that doesn’t work, mentor them with your own experience (did you try grabbing a coffee, explaining it to them).</li><li>If that doesn’t work, direct them.</li><li>Otherwise you will start intervening.</li></ul><p>If you hear an issue repeated from a couple of their peers, check whether you have enough time set aside in your 1–1 for their interpersonal challenges. The importance of handling repeating issues within your 1–1s is high, as it is one of the ways of managing conflict.¹</p><h3><strong>Giving feedback</strong></h3><p><strong>Effective feedback giving revolves around having psychological safety and preventing the other being in a defensive situation.</strong> <strong>Otherwise, whatever you say will sink in slower</strong> (the mind is preoccupied defending rather than listening). You need to make them understand where they have done a great job, as everyone believes they provided effort and they did great overall. Once they are in this state of mind, it is easier for you to relay your message across. Of course there are cases when the employee will be defensive regardless of your approach, but you can practice on being open for feedback until they are at an acceptable level. Asking about the situation from the feedback, before giving it is also important. You need to listen to both sides of the story, so that you give objective feedback.</p><h4><strong>The cadence of giving feedback</strong></h4><p><strong>Praise and corrective feedback regarding immediate unprofessional activities</strong> (raising their tone, bad language, malice, missing critical sessions, e.t.c.), <strong>should be done immediately</strong>. The media and privacy are best agreed between the two of you prior in the Contracting phase (check it as part of my “First one-on-one” blog). At the minimum give it in private, after the meeting.</p><p>Some companies have quarterly 360 peer reviews and feedback sessions or performance review sessions. Leaders usually give feedback on these meetings, based on their experience and other peer experiences with the employee. <strong>In order for you to have objective quarterly feedback, do motivate peers to give feedback real time in order for the employee to have time to correct</strong>. Otherwise making a decision based on the quarterly feedback, is not going to be received as a fair approach. “You can use this time to review progress toward goals, whether they are formal or personal”¹.</p><h4>Giving feedback and firing</h4><p><strong>When</strong> it comes to <strong>firing someone</strong>, in a prior pacesetter company, in order for the process to go smoothly, we were instructed to <strong>first be Spock and then Mother Teresa</strong> (btw, she was born in my hometown :) ). Being Spock meant we had to be rational and face the employee with the reasons why they are being fired. Plus, be direct. Moneyball’s quote sums it perfectly “Would you rather get one shot in the head or five in the chest and bleed to death?”. “They are professionals.”. Only when they accept the reasons for being fired, should you be attentive. For instance, write a letter of recommendation, propose options (Mother Teresa). <strong>In order to be Spock</strong>, I had to <strong>keep a track of all the positives and challenges that the employee faced</strong>. So the one on one was a perfect way to do this within the shared historical document¹. While working with the employee, prior to the decision to fire them, don’t get fixated on writing bad behavior / challenges only. <strong>Keep your mind focused more on positive behaviors and challenges</strong>. This will <strong>set you both for success</strong>.</p><h3><strong>Healthy challenge and pressure</strong></h3><p>As in any situation, <strong>a person requires a healthy challenge in order to grow or to finish some creative, non repeating task</strong>. You would also be required to set expectations in order to achieve your organizational goals with the employee. This usually means, <strong>you would need to apply some pressure</strong>.</p><p>Some people have understood the life lesson that they need to change or challenge themselves, even slightly, in order to have a better life or be more successful. Others didn’t. Some generally adaptable people are in life phases or moments in the day where they require more stability.</p><p>On the other hand, your team needs to achieve a goal. You might find yourself expecting more from different professional reasons. Sometimes the organization is such that those goals are set higher than what an employee is in the mood for. Hence <strong>the atmosphere in your one one one might lack a good feeling</strong>. This is ok, <strong>and you need to accept it</strong>.</p><p>When you are in a company that values employee’s space and lets people choose the deliverables and timeline to a higher extent (like through Scrum or SAFe planning without meddling too much), be careful not to push the employee too high in the challenge zone. This might backfire, even though you had your company’s best interest in mind. You need to act more as an enabler and choose the level of challenge to suit the goals, employees motivations and mood.</p><p>In companies that set the pace and goals top-down, you can allow yourself to set the challenge (push) higher, more than the challenge that the employee is comfortable with. But do so, only if you feel there is no other way for the goal to be achieved. As you go along, you will become better at finding the balance for it.</p><p>In any case, the employee needs at least a minimum challenge, as not to stay in the comfort zone, and you need to pay attention for them not to go to the alarm zone. And, if they are not happy with the challenge, always remind them how this challenge helps the goal or it is part of the job at hand. <strong>Be concise</strong> (let them talk more, be silent), and if time, guide them with questions. <strong>However the discussion goes, make sure you repeat your expectation and ask for a commitment</strong>.</p><p>Marcus refers to this part as the challenging “evil” part, as you sometimes need to “lean into the pain” in order for them to learn better, and “you don’t have to strive for a great feeling”.⁴</p><h3><strong>Handling interpersonal problems between your immediate employees</strong></h3><p>When your direct employee A complains about another direct employee B, let A know you understand certain feelings for A’s behaviors, and point to why B might have a certain behavior and try to coach/ mentor/ direct/ intervene B. As Marcus⁴ points out, “You shouldn’t shut A down, but you should come to the point of agreeing that B is bad (otherwise you haven’t done your job for B as manager — you look bad)”.</p><h3>Three key takeouts, the <strong>revelation</strong>, and an example :)</h3><p>If 1–1s were a language, <em>agenda</em> would be the <em>noun</em>. What you do <em>during a 1–1</em> would be the <em>verb</em>.</p><ol><li><strong>Avoid intervening before the call for help</strong>. Actively listen and absorb the context, and use <strong>guided questioning</strong> to direct them <strong>towards the call for help</strong>.</li><li><strong>Effective feedback giving</strong> revolves around having <strong>psychological safety</strong> and <strong>preventing</strong> the other <strong>being</strong> <strong>defensive</strong>. Otherwise, whatever you say will sink in slower.</li><li><strong>In order to grow or to finish some creative, non repeating task</strong>, an employee requires <strong>a healthy challenge (pressure) </strong>from your side that <strong>might put</strong> the <strong>meeting in a bad feeling. Accept it</strong>.</li></ol><p><strong>The revelation</strong><br>Keep a lookout on the signal for uncomfortable subjects (the andon cord) that you agreed to in your contracting during your first one-on-one, and act accordingly.³</p><p><strong>Great example</strong>⁴<br><strong>of building an organizational or employee capability, when having a not urgent and unimportant issue</strong>, would be: If they are complaining about the relationship with the PO or the delivery manager, you start coaching them on how to approach that relationship. Otherwise, mentor them with your own experience (“did you try grabbing a coffee, explaining it to them”). Otherwise, direct them. Otherwise intervene.</p><p>For a lot more gems, check the full blog post. ;)</p><h3>Summary</h3><ol><li><strong>If 1–1s were a language, <em>agenda</em> would be the <em>noun</em>. What you do <em>during a 1–1</em> would be the <em>verb</em>.</strong></li><li>in 1–1s, you should be definitely <strong>actively</strong> listening.</li><li><strong>listen and absorb the context</strong></li><li><strong>use guided questioning to direct them towards the call for help</strong>.</li><li><strong>Avoid intervening before the call for help</strong> (neutral or <strong>negative impact: intrusive, condescending, </strong>might <strong>give a solution for a problem that doesn’t exist</strong>)</li><li>Check example questions in blog.</li><li><strong>Employees should type in key aspects from the conversation and their APs</strong> (action points).</li><li><strong>You</strong> do the same, including <strong>putting down the “call for help”</strong>.</li><li>The <strong>goal</strong> of taking notes is to build: <strong>transparency, trust</strong> towards you <strong>and acceptance</strong> of you (APs that you will be doing on behalf of them), and a “context of what has happened”¹.</li><li>I would leave 5min before the end of the meeting in order to “review the notes at the end of the meeting”³.</li><li>“leave time at the end to add notes … if you’re distracted by having a computer open in front of you during the meetings”.¹</li><li><strong>Keep a lookout on the signal for uncomfortable subjects (the andon cord) that you agreed to in your contracting during your first one-on-one, and act accordingly</strong>.³</li><li><strong>For important issues, </strong>you should <strong>direct or intervene</strong></li><li><strong>For unimportant and not urgent issues, grow the capability of the employee(s)/organization. </strong>You can <strong>move to the left of the framework (depending on the employee’s place in learning curve and seniority)</strong>.</li><li><strong>Great example</strong>⁴ would be: If they are complaining about the relationship with the PO or the delivery manager, you start coaching them on how to approach that relationship. Otherwise, mentor them with your own experience (“did you try grabbing a coffee, explaining it to them”). Otherwise, direct them. Otherwise intervene.</li><li>If an issue is repeating, you need to move to the right of the framework and give clearer feedback.</li><li>If you hear an issue repeated from a couple of their peers, check whether you have enough time set aside in your 1–1 for their interpersonal challenges.</li><li>The importance of handling repeating issues within your 1–1s is high, as it is one of the ways of managing conflict.¹</li><li><strong>Effective feedback giving revolves around having psychological safety and preventing the other being in a defensive situation.</strong> <strong>Otherwise, whatever you say will sink in slower.</strong></li><li>You need to make them understand where they have done a great job, as everyone believes they provided effort and they did great overall. Once they are in this state of mind, it is easier for you to relay your message across.</li><li><strong>Praise and corrective feedback regarding immediate unprofessional activities should be done immediately.</strong></li><li><strong>In order for you to have objective quarterly feedback, do motivate peers to give feedback real time in order for the employee to have time to correct</strong>.</li><li><strong>When</strong> it comes to <strong>firing someone</strong>, <strong>first be Spock and then Mother Teresa</strong></li><li><strong>In order to be Spock</strong>, I had to <strong>keep a track of all the positives and challenges that the employee faced</strong>.</li><li>Even when firing is a possibility in an organization<strong>, keep your mind focused more on positive behaviors and challenges</strong>. This will <strong>set you both for success</strong>.</li><li><strong>A person requires a healthy challenge (pressure) in order to grow or to finish some creative, non repeating task</strong>.</li><li><strong>You would need to apply some pressure. The atmosphere in your one one one might lack a good feeling</strong>. This is ok, <strong>and you need to accept it</strong>.</li><li><strong>Be concise</strong>. <strong>However the discussion goes, make sure you repeat your expectation and ask for a commitment</strong>.</li><li>The challenging “evil” part: you sometimes need to “lean into the pain” in order for them to learn better, and “you don’t have to strive for a great feeling”.⁴</li><li>When your direct employee A complains about another direct employee B, let A know you understand certain feelings for A’s behaviors, and point to why B might have a certain behavior and try to coach/ mentor/ direct/ intervene B.</li><li>As Marcus⁴ points out, “You shouldn’t shut A down, but you should come to the point of agreeing that B is bad (otherwise you haven’t done your job for B as manager — you look bad)”.</li></ol><h3>Resources</h3><p><a href="https://medium.com/@despot.jakimovski/one-on-ones-7685e56dab32">One on ones</a><br><a href="https://medium.com/@despot.jakimovski/first-contracting-one-on-one-f73e59eee9d8">First one-on-one</a><br><a href="https://medium.com/@despot.jakimovski/cadence-1-1s-fd574db565b6">Cadence (1–1s)</a><br><a href="https://medium.com/@despot.jakimovski/agenda-1-1s-1b0cefd5d8c3">Agenda (1–1s)</a><br><a href="https://medium.com/@despot.jakimovski/coaching-204a862eca63">Coaching</a></p><p>The <a href="https://www.linkedin.com/feed/update/urn:li:activity:6979840256552390656/">During One-on-ones Linkedin resource</a> for additional audiance to comment, interact and share with.</p><p>…</p><p>Reference</p><p>[1] <a href="https://www.linkedin.com/in/ACoAAABhf9EBElKVMD8r7Ld8mtftcyp43d7cOD0">Camille Fournier</a>, “The Manager’s path”, 2017, book<br>[2] <a href="https://www.linkedin.com/in/ACoAAAC0KdQBkikUIfCPY2nyso3lWQqRKXj_ViQ">Will Larson</a>, “An Elegant Puzzle: Systems of Engineering Management”, 2019, book<br>[3] Dr. <a href="https://www.linkedin.com/in/ACoAAAHihN0BlojkMraMQYmhMDlKJR5RzgJtHG8">James Stanier</a>, “Become an Effective Software Engineering Manager: How to Be the Leader Your Development Team Needs”, 2020, book<br>[4] <a href="https://www.linkedin.com/in/ACoAAABGxRoBnuBYhMjEI-IDRulBwJ2glEHG41U">Marcus F.</a>, <a href="https://lnkd.in/dghjKmQB">https://lnkd.in/dghjKmQB</a>, youtube videos</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23996f3ee7a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Coaching]]></title>
            <link>https://medium.com/@despot.jakimovski/coaching-204a862eca63?source=rss-8525fb4b6497------2</link>
            <guid isPermaLink="false">https://medium.com/p/204a862eca63</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Despot Jakimovski]]></dc:creator>
            <pubDate>Fri, 16 Sep 2022 15:27:27 GMT</pubDate>
            <atom:updated>2022-09-17T12:59:19.792Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*bAvaxB9xyDAIl2E7tSziDQ.jpeg" /></figure><p>For the impatient, glance at the the key takeouts at the bottom. 😉</p><p>The moment you rise in seniority level, you would find yourself needing to teach others. Naturally, you would tell the other person what they need to do to solve some issue, based on your experience. Most of the time this goes ok. You would notice, though, that your direction is not always fruitful or not to the extent you were hoping. Someone might even react badly to a certain direction. Or, when you are a leader, you might notice that the ones you lead are not growing as fast as you want. As you read or you are being mentored on the subject, you notice that there are different ways on how to enable someone to solve certain challenges and grow.</p><p>Most people use the <strong>terms teaching, coaching, mentoring, directing interchangeably</strong>, though <strong>there are subtle differences in <br>a. seniority level at which you apply, <br>b. maximizing growth potential, <br>c. how fast you want the problem to be solved</strong>. <br>Marcus’ distinction⁴ plays well with my practice.</p><p>Following are the ways of teaching ordered by lowest to highest growth potential of the person you teach. Growth potential is usually inversely proportional to seniority and proportional to the time to resolution of the challenge. Although sometimes, someone at a more junior level, might come to a resolution faster than you intervening.</p><h3><em>Intervention</em></h3><p>As mentioned, the most natural thing we do is letting someone know what they need to do. And, sometimes the other, usually junior person would <strong>fail those instructions repeatedly</strong> (fixing failure with build tools, e.t.c.) or <strong>the cost of failing them repeatedly is high</strong> (deployment on a staging environment that clients use, or even more so, on production). If you are a <strong>manager of engineering managers</strong>, a similar situation would be when <strong>resolution of a certain subject depends on you rather than the manager’s area of responsibilities</strong> (perhaps outside of your organization), and hence the manager would not be able to resolve the issue even if they go to their peers within your organization. In these cases, you would need to intervene.</p><p>Definition: Doing the things yourself on behalf of someone. “<strong>Let me do this thing for you</strong>.”<br>Growth potential: <strong>Lowest<br></strong>Time to resolution: <strong>Highest<br></strong>Level: Junior, or any in case urgent and important<br>Recommendation: Most invasive way. <strong>Avoid it</strong>, as it has the lowest growth potential. It is not a good sign. A red flag to think about why this is happening and how to push them out of this position.</p><h3><em>Directing</em></h3><p>The person you are teaching has an <strong>understanding</strong> that <strong>after trying</strong>, <strong>when</strong> they are <strong>stuck</strong>, they should <strong>come to you for direction</strong>, as they know you know how to do the task or goal. The person trying and after a certain amount of time coming back to you, <strong>keeps the delivery of the tasks or goals within the estimated time</strong>.</p><p>There is yet another level of teaching that stands between intervening and directing, that should be used usually by team leads rather than managers. Sometimes direction itself wouldn’t be enough, and you wouldn’t want to go into intervention as you believe the person has the capacity to solve the challenge, but might be missing some aspects that they are struggling to achieve. You would <strong>pair up to start revealing (intervening) step by step</strong>. If you both don’t know, admit that you don’t know, to show vulnerability in order to build trust and psychological safety. And try to <strong>uncover the unknown for the other person</strong>. You do this <strong>until you feel that the other has enough knowledge to continue</strong> and let them continue by themselves. Sometimes this process might lead to solving the solution, ending up with full intervention. Maybe the best phrase for this would be <strong>pair-intervene-direct</strong>.</p><p>Definition: “<strong>Do these things to solve it</strong>”<br>Growth potential: <strong>Low<br></strong>Time to resolution: High<br>Level: Junior to Medior<br>Recommendation: Use it when <strong>the person is just starting on the learning curve, and mentoring (below) is too high of a challenge for them</strong>.</p><h3><em>Mentoring</em></h3><p>You let them choose between options so they can think for themselves what the pros and cons are for each option and learn and fortify that process in order to use it themselves in future. You are providing a bit less of your experience (and more growth possibility) than when mentoring, yet more of your experience than when coaching.</p><p>Definition: “<strong>You can try A or B.</strong> <strong>What do you think about it?</strong>”<br>Growth potential: High<br>Time to resolution: Medium (to High if the employee has mastered decision making and applying the solution)<br>Level: Medior<br>Recommendation: <strong>Use it when the employee can’t come up with ideas/solutions or they don’t feel psychologically safe enough</strong> (they require a bit more hand holding).</p><h3><em>Coaching</em></h3><p>Definition: <strong>Guided questioning of the employee to unlock answers within them</strong>.<br>Growth potential: <strong>Highest<br></strong>Time to resolution: Lowest (to High if the employee has mastered solution proposition, decision making and applying the solution)<br>Level: <strong>High<br></strong>Recommendation: Use this with caution, as the more junior the person is, they might take this approach as “I am not good enough, as I can’t think of any solutions.” e.t.c. Some <strong>psychological safety</strong> is required for them to increase their growth potential. So <strong>keep explaining the reason</strong> for guiding them in this way, <strong>while using the other approaches</strong> (mentoring, directing) in order <strong>to unlock a higher growth potential in them </strong>and eventually reach coaching.</p><p>— — — — — —</p><p>Generally, the “Level” at which you apply might slightly differ. Try to <strong>apply these tailored to the person you are leading</strong>. Some people tend to excel for different subjects and seniority levels. If the challenge is not important or urgent, always try to start from Coaching and move to the right of the Coach, Mentor, Direct, Intervene framework.</p><h3><em>Three key takeouts an eureka and a quote</em></h3><ol><li>Use <strong>Guided questioning </strong>of the employee <strong>to unlock answers within them </strong>(<strong>Coaching</strong>) when possible for <strong>highest growth potential</strong>.</li><li><strong>“You can try A or B.</strong> <strong>What do you think about it?</strong>”(<strong>Mentoring</strong>) <strong>when </strong>the employee has <strong>no ideas/solutions.</strong></li><li>“<strong>Do these things to solve it</strong>”(<strong>Directing</strong>) when the <strong>employee tries</strong>, but gets <strong>stuck</strong>, they are just <strong>starting on the learning curve, </strong>and <strong>mentoring </strong>is <strong>too high of a challenge</strong> for them.</li></ol><p>The eureka<br><strong>Pair-intervene-direct</strong>: an approach between directing and intervening where you <strong>pair up and start revealing (intervening) step by step</strong>, <strong>until</strong> <strong>the other has enough knowledge to continue</strong>, to prevent full intervention, get them to grow as much as possible, and to build a relationship and trust.</p><p>The quote<br><strong>If</strong> the challenge is <strong>not important or urgent</strong>, always try to <strong>start from Coaching and move to the right of the Coach, Mentor, Direct, Intervene framework</strong>.⁴</p><h3><em>Summary</em></h3><ol><li>Using <strong>coaching, mentoring, directing </strong>depend on <br><strong>a. seniority level at which you apply, <br>b. maximizing growth potential, <br>c. how fast you want the problem to be solved</strong>.</li><li>Intervene when an employee <strong>fails instructions repeatedly, </strong>the <strong>cost </strong>of failing them repeatedly is <strong>high, or when a manager of engineering managers</strong>, <strong>resolution of a certain subject depends on you</strong> and the manager can’t resolve it.</li><li><strong>Intervention</strong>: “<strong>Let me do this thing for you</strong>” junior, so we can <strong>get to the resolution faster</strong>.</li><li><strong>Avoid it</strong> as it has the <strong>lowest growth potential</strong>, and never a good sign.</li><li><strong>Directing</strong> (“<strong>Do these things to solve it</strong>”) when the <strong>employee tries</strong>, but gets <strong>stuck</strong>, they are just <strong>starting on the learning curve, and mentoring </strong>(below) <strong>is too high of a challenge</strong> for them.</li><li>Directing helps <strong>keep the delivery of the tasks or goals within the estimated time</strong>.</li><li><strong>Pair-intervene-direct</strong> when someone is failing a direction, but you feel the person has the capacity, or you want to build a relationship and trust.</li><li>Pair up to <strong>start revealing (intervening) step by step</strong>, uncover the unknown for the other person, <strong>until</strong> you feel that <strong>the other has enough knowledge to continue</strong>. Might end up with full intervention<strong>.</strong></li><li><strong>Mentoring</strong> (“<strong>You can try A or B.</strong> <strong>What do you think about it?</strong>”) <strong>when the employee can’t come up with ideas/solutions </strong>or they don’t feel psychologically safe enough (juniors might think “I am not good enough, as I can’t think of any solutions.”)</li><li>Coaching: <strong>Guided questioning of the employee to unlock answers within them</strong>.</li><li>Use <strong>coaching when</strong> <strong>possible</strong> (usually for medior and senior employees) <strong>as highest growth potential</strong>.</li><li><strong>For building psychological safety</strong> in juniors <strong>keep explaining the reason</strong> for guiding them in them with higher then current teaching types, eventually reaching coaching level to unlock a higher growth potential in them.</li><li>Try to <strong>apply these tailored to the person you are leading</strong>.</li><li><strong>If</strong> the challenge is <strong>not important or urgent</strong>, always try to <strong>start from Coaching and move to the right of the Coach, Mentor, Direct, Intervene framework</strong>.⁴</li></ol><h3>Resources</h3><p><a href="https://www.linkedin.com/feed/update/urn:li:share:6976563239438462976/">The Coaching Linkedin resource</a> for additional audiance to comment, interact and share with.</p><p>…</p><h3>Reference</h3><p>[4] <a href="https://www.linkedin.com/in/ACoAAABGxRoBnuBYhMjEI-IDRulBwJ2glEHG41U">Marcus F.</a>, <a href="https://lnkd.in/dghjKmQB">https://lnkd.in/dghjKmQB</a>, youtube videos</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=204a862eca63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agenda (1–1s)]]></title>
            <link>https://medium.com/@despot.jakimovski/agenda-1-1s-1b0cefd5d8c3?source=rss-8525fb4b6497------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b0cefd5d8c3</guid>
            <category><![CDATA[one-on-one]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Despot Jakimovski]]></dc:creator>
            <pubDate>Thu, 08 Sep 2022 21:01:10 GMT</pubDate>
            <atom:updated>2022-11-14T20:26:49.100Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OORA2LdVzM1fmvd5q82F3g.jpeg" /></figure><p>For the impatient, glance at the the key takeouts at the bottom. 😉</p><h3>Grounding your 1–1 behavior</h3><p>The agenda is the 1–1 structure that will <strong>ground the behavior during the 1–1s</strong>. This way you gain most in the spent time.</p><p>When discussing an item we tend to fill all the time with that item if nothing else to talk about. This might make you both <strong>miss something important, prevent you talking about appropriate subjects and sufficiently</strong>. When you have a list, it is easier to roughly estimate how much time you would need for each item.</p><p>All of us have a <strong>natural tendency towards a certain area of 1–1s</strong>. This can be because of your character (something practiced unconsciously most of your life), or something you practiced within your career. You might be good in other areas, but the practiced behavior turned into a reflex. This will make it comfortable for you to talk about certain areas and not others. <strong>Having an agenda will give you a check on that</strong> tendency, and it will be up to you to push yourself in the other direction out of your comfort zone. One of my natural strengths lies within people management, and coaching. I like to help people so it is naturally easier for me to engage them in this area. This is why I used to push myself in other areas till I felt a balance. The agenda helped with this.</p><h3><strong>Always have an agenda</strong>.</h3><p>All engineering managers (from the resources) agree on this, except maybe Camile in “The Catch-up” type of 1–1¹ explains that when possible, she would do fluid natural meetings without agenda ahead, in order to let her direct reports drive the conversation. To her, this introduces creativity, but then goes on to say that it “can turn into a complaining session or therapy” and you need to “prevent unchecked long conversations”¹.</p><p>I would <strong>maybe do the first one or two as fluid meetings</strong>, to allow for getting out whatever they feel like discussing if it feels cold to them having an agenda. Another time for fluid meetings is perhaps after a long time coworking within a company as an experienced engineering manager with the other person, since this is the only time you will get a sixth sense on whether the 1–1 is lacking something. <strong>Otherwise, always have an agenda. I can be flexible with the agenda, but it is there to ground us both</strong>.</p><h3><strong>Shareable document</strong></h3><p>Having one will reduce maintenance of two separate lists instead of one, <strong>increase collaboration and find misalignments, increase transparency</strong>, between you and if agreed and needed with others as well. Each time you need to recollect something that you talked about, to summarize on the key takeaways and action points at the end of each meeting, the shareable document will be there for you.</p><p>I personally use workflowy but you can choose the application for the format and functionality to suit you both (google docs e.t.c.).</p><h3><strong>Who enters items in the agenda</strong>?</h3><p>As it’s in the <strong>best interest of employees</strong> to discuss 1–1 subjects that they are interested in, in order to grow and keep on succeeding, I believe they are <strong>mostly responsible for adding items</strong>.</p><p>Once it is understood what goes in the agenda and what doesn’t, the employee will add those 1–1 items properly. If they are not adding 1–1 items, then try to inspect whether that item has some 1–1 aspects that can be talked about. Otherwise keep explaining that these non1–1 items either belong to another ceremony or belong outside of the scope of the business.</p><p>The <strong>manager also supplements the agenda with items that reflect that person from a 1–1 standpoint</strong>. Perhaps someone approached you, the manager, for good or bad feedback for the employee, or you heard some challenges regarding the project they are working on or team or organization they are leading. Usually I add items seldom or whenever needed.</p><p>Camile¹ has this approach. James is a bit more forthcoming “they and you need to enter, in the shared doc”³ , but then hints “their meeting, not yours” in another section, so you can probably tweak this slightly depending on the organizational setting, your ways, and the employee’s needs.</p><p>If possible, instill a habit for yourself and the employee, of <strong>adding the items during the week</strong> instead of right before the meeting starts. This way, you would not require to remember a lot, and the only thing left prior to the meeting will be prioritizing the items.</p><h3><strong>Topics</strong></h3><p>I divide the topics in the high level categories below.</p><h4><strong>People problems</strong></h4><p>Being complex creatures, interpersonal problems are a vast topic. When it comes to what the employee can do usually what helps is guided questions around seeing other perspectives, making someone conscious about something, making them understand another colleague/stakeholder. You will sometimes need to discuss the employee’s interpersonal issues with another person in order to help them forward.</p><h4><strong>Planning</strong></h4><p>Are there deadlines? Are we on track with the schedule? Are there impactful items with small effort that can help us reach the deadline? If not, is there something we can scope out?</p><h4><strong>Giving Feedback</strong></h4><p>Understand how the person wants to receive good and bad feedback (so it is most effective) and apply it. Don’t forget to praise them when they have done something positive. As humans, in order to survive, we become wired towards the negative (we can spot it easily), so it is important to check whether you give enough praise. If the employee is a manager, have they been doing this with their team?</p><p>Camile¹ feels that engineering managers tend to go towards discussing planning items mostly and in her experience, cautions that making time for feedback and coaching is important.</p><h4><strong>Coaching</strong></h4><p>Guided questioning is a skill very useful for this area. You would also need to dip in your own experience, show vulnerability to build trust in order for the person to accept most of the coaching. Or you would need to figure out which person can help coach them on a certain item if required.</p><p>I appreciate Marcus’s revelation regarding coaching. He suggests that the manager should understand whether an item is urgent and important, and where the employee is on the learning curve. Then you would be able to move to the proper level of the framework: coaching, mentoring, directing and intervening.⁴ The more to the left, the more you gain, but an alarm zone for juniors. The more to the right, the less of a challenge(learning) for the employee, but required when there is higher urgency and importance. If there is room, you can agree with the employee that you both fill in importance &amp; urgency next to each item. This way they would get the most growth possible.</p><h4><strong>Technical deep dives</strong></h4><p>What are the pros and cons regarding different solutions of the same technical problem? The more senior engineering management roles you have, the higher level the guided questions would be. What is the architecture of the requirement you are working on? Dr. James has a couple of good examples as well: “Ask about NFRs, that might reveal weak points, or just understand the work and part of infrastructure it belongs to.”³</p><h4><strong>Process deep dives</strong></h4><p>I remember reading a book from someone from Netflix that helped handle the scalability challenges, saying that one of the most important things they did was trying to make it easy for organizations to succeed and in most of the time it meant, if possible, removing a process completely. If this is not a possibility, you can try reducing the steps. Do automate as much as possible, too.</p><h4><strong>Other role insights</strong></h4><p>In high school, where I grew up, I was (we were all) curious about what different jobs meant, did and how they did it. I felt quite removed from what the end goal was and hence mostly followed what I was told at school. The more knowledge I had about different professions, the better I was able to apply myself to the things that mattered (while still balancing common knowledge and culture — I can appreciate the value of generalists). Like in that long ago case, during my career I often saw managers that didn’t want their employees to know what they did or said they would explain a role but they were vague or didn’t follow up on it. Don’t kill their curiosity. If your goal is to grow that person, and it should be, you should find a way to satisfy that curiosity and <strong>explain what you did on a certain task (Dr. James³) or allow for a person to shadow (if enough time and person senior enough) or find someone that can share some insights for some other roles that the employee is interested in</strong>. This will make them apply themselves closer to what your goals are. You just bet on their motivation. They will repay the organization kindly.</p><p>According to Dr. James, discussing relevant articles and department or company direction are also topics to be discussed, though I would tie these into the previous topics above.</p><h4><strong>A few more thoughts on topics</strong></h4><p><strong>Status and Progress updates should not be done during a 1–1</strong>. They can be done as part of other ceremonies or through a different medium, or found in tracking tools, or are repeating from another meeting you had, and just take valuable time from the 1–1. The only time you should do a progress update according to Camile is “when you have someone who’s off on a side project that you’re not personally overseeing”.</p><p>I would like to end the Topics section with a quote from Dr. James “The <strong>connecting themes</strong> are <strong>sharing, building trust, tech thinking, and interpersonal problems</strong>. If you spend time on any of these, you have a valuable one on one.”³</p><h3>Three key takeouts, a no-no, and a quote :)</h3><ol><li>The agenda <strong>grounds the behavior during the 1–1s</strong> to gain most of the time spent.</li><li>Always have an agenda in a shareable document, created mostly by the employee.</li><li>Topics should be some of: People problems, Planning, Giving Feedback, Coaching, Technical deep dives, Process deep dives, Other role insights</li></ol><p>The no-no: !Status and !progress updates!</p><p>“The <strong>connecting themes</strong> are <strong>sharing, building trust, tech thinking, and interpersonal problems</strong>. If you spend time on any of these, you have a valuable one on one.”³</p><h3>The summary</h3><ol><li>The agenda <strong>grounds the behavior during the 1–1s</strong> to gain most of the time spent.</li><li>allows you to talk about appropriate and important subjects and sufficiently.</li><li>keeps your natural tendency towards a certain area of 1–1s in check</li><li>Always have an agenda.</li><li>maybe do the first one or two as fluid meetings if it feels cold entering agenda items at first. Otherwise 4. :) I can be flexible with the agenda, but it is there to ground us both.</li><li>Shareable document to increase collaboration, find misalignments and increase transparency.</li><li>Employee mostly enters items.</li><li>The manager also supplements the agenda with items that reflect that person from a 1–1 standpoint.</li><li>habit of adding the items during the week to reduce forgeting some items</li></ol><p>Topics</p><ol><li>People problems</li><li>Planning</li><li>Giving Feedback</li><li>Coaching</li><li>Technical deep dives</li><li>Process deep dives</li><li>Other role insights</li><li>Status and Progress updates should not be done during a 1–1.</li><li>Do a progress update only “when you have someone who’s off on a side project that you’re not personally overseeing”.</li><li>“The <strong>connecting themes</strong> are <strong>sharing, building trust, tech thinking, and interpersonal problems</strong>. If you spend time on any of these, you have a valuable one on one.”³</li></ol><h3>Resources</h3><p>0. <a href="https://medium.com/@despot.jakimovski/coaching-204a862eca63">Coaching</a></p><p>General <a href="https://medium.com/@despot.jakimovski/one-on-ones-7685e56dab32">One on ones</a> (for all seniority levels of managers):</p><p>1. <a href="https://medium.com/@despot.jakimovski/cadence-1-1s-fd574db565b6">Cadence (1–1s)<br></a>2. <a href="https://medium.com/@despot.jakimovski/agenda-1-1s-1b0cefd5d8c3">Agenda (1–1s)<br></a>3. <a href="https://medium.com/@despot.jakimovski/first-contracting-one-on-one-f73e59eee9d8">First 1–1s</a><br>4. Prior to 1–1s <em>(in the oven ..)</em><br>5. <a href="https://medium.com/@despot.jakimovski/during-an-one-on-one-23996f3ee7a5">During One-on-ones</a><br>6. After 1–1s <em>(in the oven ..)</em><br>7. Location (1–1s) <em>(in the oven ..)</em></p><p><strong>One-on-Ones for (Engineering) Manager of Managers</strong>:</p><p>8. Cadence (MoMs’ 1–1s) <em>(in the oven ..)</em><br>9. With whom? (MoMs’ 1–1s) <em>(in the oven ..)</em><br>10. Agenda (MoMs’ 1–1s) <em>(in the oven ..)</em><br>11. During a 1–1 (MoMs’ 1–1s) <em>(in the oven ..)</em><br>12. During Interviewing (MoMs’ 1–1s) <em>(in the oven ..)</em><br>13. 1–1s with Senior Peers from other functions (MoMs’ 1–1s) <em>(in the oven ..)</em></p><p><a href="https://www.linkedin.com/posts/despotjakimovski_agenda-11s-activity-6973749286974963712-rOA5?utm_source=share&amp;utm_medium=member_desktop">The Agenda(1–1s) Linkedin resource</a> for additional audiance to comment, interact and share with.</p><p>…</p><p>Reference</p><p>[1] <a href="https://www.linkedin.com/in/ACoAAABhf9EBElKVMD8r7Ld8mtftcyp43d7cOD0">Camille Fournier</a>, “The Manager’s path”, 2017, book<br>[2] <a href="https://www.linkedin.com/in/ACoAAAC0KdQBkikUIfCPY2nyso3lWQqRKXj_ViQ">Will Larson</a>, “An Elegant Puzzle: Systems of Engineering Management”, 2019, book<br>[3] Dr. <a href="https://www.linkedin.com/in/ACoAAAHihN0BlojkMraMQYmhMDlKJR5RzgJtHG8">James Stanier</a>, “Become an Effective Software Engineering Manager: How to Be the Leader Your Development Team Needs”, 2020, book<br>[4] <a href="https://www.linkedin.com/in/ACoAAABGxRoBnuBYhMjEI-IDRulBwJ2glEHG41U">Marcus F.</a>, <a href="https://lnkd.in/dghjKmQB">https://lnkd.in/dghjKmQB</a>, youtube videos<br>[5] <a href="https://www.linkedin.com/in/ACoAAAEQSn4BZr_C1gLc2eKuoS6LEku5sGKOLtw">Lara Hogan</a>, <a href="https://lnkd.in/dnxKqMdh">https://lnkd.in/dnxKqMdh</a>, blog</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b0cefd5d8c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cadence (1–1s)]]></title>
            <link>https://medium.com/@despot.jakimovski/cadence-1-1s-fd574db565b6?source=rss-8525fb4b6497------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd574db565b6</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[one-on-one]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[cadence]]></category>
            <dc:creator><![CDATA[Despot Jakimovski]]></dc:creator>
            <pubDate>Wed, 07 Sep 2022 20:32:01 GMT</pubDate>
            <atom:updated>2022-11-14T20:27:17.385Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RlF6RWzRYScBKa90B-Wv_g.jpeg" /></figure><p>For the impatient, glance at the the key takeouts at the bottom. 😉</p><h3><strong>How often</strong>?</h3><p>In the words of a relative of mine, when talking about his marathon run successes, <strong>consistency is the key</strong>. “If a certain day I feel overwhelmed with problems and challenges, even when not feeling like running, I put on my running clothes, and go out. I make a deal with myself: Run for a couple of meters at least, and then, if you still dislike it, go home. 9 out of 10 times, I continue my 10K run.”🏃.</p><p>During my first engineering management experience, after a while, a lot more work piled up. Pressure mounted. I prioritized and pushed back. At the same time, I was looking for a descope win to handle one or two more priorities. I thought 1–1s are not that impactful 🙄. All is going ok with my reports. A challenge here and there. <strong>Surely, I (and the report) can handle it without a meeting or two</strong>. I reduced the cadence of the 1–1s. It took some time for <strong>problems</strong> to <strong>start creeping up</strong>. It wasn’t evident to me, but as soon as I started getting the consistency back, I felt a positive change in solutions.</p><p>For the people just starting their management journey, do them <strong>regularly, every week</strong>. Once you get in the groove, you can reduce the cadence, but still do them regularly. I like Camille’s more experienced junior manager approach “<strong>just don’t eliminate them completely</strong>”¹ . It’s a more savvy approach to the “every week without a fail” from Dr. James Stanier³, Marcus Frödin⁴. But even she agrees “you need to do regularly scheduled 1–1s … if you’re not a CTO with years and years of management experience”¹.</p><h3>When can you reduce the cadence?</h3><p>I do it, when I feel a <strong>junior person responds indifferently</strong> in the 1–1s / has a laid back approach to their career growth. Both they and I need to be in the game for them to benefit. Most of the time, they want to grow. They sometimes don’t realize it, though. Part of your job is to try and unlock this by looking for their career (and even private) motivations. Net net, “their meeting, not yours”³.</p><p>On the other hand, a <strong>senior</strong> is a sharp arrow. If they don’t have a bumpy project and they are <strong>in the zone</strong>, I managed to slightly reduce the cadence without any consequences.</p><p>I <strong>doubled the time</strong> <strong>when</strong> there was a <strong>bad mojo between an employee and me</strong>.</p><p>But, never, I mean never eliminate them and only cancel them seldom.</p><p>Camile, as a more fluid manager, if she <strong>“bumps” into the person often</strong> and manages to go through some 1–1 topics, she reduces the cadence.¹ How often we “bump” into each other with the new <strong>remote</strong> or hybrid <strong>work style</strong>, challenges this. Even though I try to take the opportunity when I meet someone, I am a more structured person, and I appreciate the value brought by the predictability of the 1–1 meeting. At the end of the day, <strong>it’s about both of your preferences</strong>.</p><h3>When?</h3><p>The <strong>basic</strong> approach is <strong>“do it at the same time”</strong>. Then you can extend it. I try not to do them Monday, as everyone is getting up to speed and becoming productive, or Friday afternoon, since I am letting others and myself wind down with the rest of the activities. I usually do them <strong>before business day ends</strong>, as they could <strong>focus on the meat of the work during the day</strong>. The downside is <strong>less focus</strong> at the <strong>end</strong> of the <strong>day</strong>. For me, it mostly revolves around productivity. Camile¹ does them Tuesday to Thursday to avoid rescheduling because of long weekends, and in the morning before things get busy.</p><h3>How Long?</h3><p>At one point, in a previous pacesetter leadership style organization, due to high load, they instructed us to do 5min 1–1s. Although we all took pride in working at a company that proactively read white papers on approaches and tried to integrate them, effectively making us improve on a daily basis, I still laugh at the thought of it. :) What can you possibly do in 5min? Start a conversation? :) Like every failure, it was a good learning experience!</p><p>I start off with 1hr contracting (will explain it in another post) in the first 1–1 and then do <strong>45min 1–1 meetings with a 15 min preparation</strong> left for the managed. <strong>Then</strong> I <strong>change the length</strong> as I see fit for them. I like Marcus’s structure⁴, reserving <strong>30min</strong> for <strong>critical things</strong> and 30min for <strong>long term growth</strong>, and also considering the amount of time it takes to prepare, the longer the meeting.</p><h3>3 key takeaways and a surpries</h3><ol><li>Be consistent. Do them regularly and at the same time.</li><li>Reduce when junior indifferent, senior in the zone. Double for bad mojo.</li><li>45min. 1–1s with 15min prep time. Change to fit as you go.</li></ol><p><strong>The surprise</strong>: Remote work challenging fluid 1–1 wins (watercooler chat).</p><p><a href="https://www.linkedin.com/posts/despotjakimovski_one-on-ones-activity-6973351542754029568-PuSf?utm_source=share&amp;utm_medium=member_desktop">The linkedin post</a> for an additional audiance.</p><h3>The summary</h3><p><em>How often?</em><br> 1. Consistency is king. <br> 2. Reguraly, every week.<br> 3. Just don’t eliminate them completely.<br> 4. Reduce it beyond boundary and problems will start creeping up.<br> <br><em>When can you reduce the cadence?</em><br> 5. when junior indifferent (“their meeting, not yours”), <br> 6. senior in the zone. <br> 7. Double down for bad mojo between an employee and yourself.<br> 8. Do it fluid whenever you can (help reduce them). Challenged by remote work style.</p><p><em>When? </em><br> 9. Do it at the same time<br> 10. before business day ends (pros: can focus on the meat of the work during the day. cons: less focus at day end)</p><p><em>How long?</em><br> 11. 1hr contracting in the first 1–1 <br> 12. 45min 1–1 meetings with a 15 min preparation. <br> 13. Change to fit for them.<br> 14. reserve 30min for critical things and 30min for long term growth</p><h3>Resources</h3><p>0. <a href="https://medium.com/@despot.jakimovski/coaching-204a862eca63">Coaching</a></p><p>General <a href="https://medium.com/@despot.jakimovski/one-on-ones-7685e56dab32">One on ones</a> (for all seniority levels of managers):</p><p>1. <a href="https://medium.com/@despot.jakimovski/cadence-1-1s-fd574db565b6">Cadence (1–1s)<br></a>2. <a href="https://medium.com/@despot.jakimovski/agenda-1-1s-1b0cefd5d8c3">Agenda (1–1s)<br></a>3. <a href="https://medium.com/@despot.jakimovski/first-contracting-one-on-one-f73e59eee9d8">First 1–1s</a><br>4. Prior to 1–1s <em>(in the oven ..)</em><br>5. <a href="https://medium.com/@despot.jakimovski/during-an-one-on-one-23996f3ee7a5">During One-on-ones</a><br>6. After 1–1s <em>(in the oven ..)</em><br>7. Location (1–1s) <em>(in the oven ..)</em></p><p><strong>One-on-Ones for (Engineering) Manager of Managers</strong>:</p><p>8. Cadence (MoMs’ 1–1s) <em>(in the oven ..)</em><br>9. With whom? (MoMs’ 1–1s) <em>(in the oven ..)</em><br>10. Agenda (MoMs’ 1–1s) <em>(in the oven ..)</em><br>11. During a 1–1 (MoMs’ 1–1s) <em>(in the oven ..)</em><br>12. During Interviewing (MoMs’ 1–1s) <em>(in the oven ..)</em><br>13. 1–1s with Senior Peers from other functions (MoMs’ 1–1s) <em>(in the oven ..)</em></p><p>…</p><p>Reference</p><p>[1] <a href="https://www.linkedin.com/in/ACoAAABhf9EBElKVMD8r7Ld8mtftcyp43d7cOD0">Camille Fournier</a>, “The Manager’s path”, 2017, book<br>[2] <a href="https://www.linkedin.com/in/ACoAAAC0KdQBkikUIfCPY2nyso3lWQqRKXj_ViQ">Will Larson</a>, “An Elegant Puzzle: Systems of Engineering Management”, 2019, book<br>[3] Dr. <a href="https://www.linkedin.com/in/ACoAAAHihN0BlojkMraMQYmhMDlKJR5RzgJtHG8">James Stanier</a>, “Become an Effective Software Engineering Manager: How to Be the Leader Your Development Team Needs”, 2020, book<br>[4] <a href="https://www.linkedin.com/in/ACoAAABGxRoBnuBYhMjEI-IDRulBwJ2glEHG41U">Marcus F.</a>, <a href="https://lnkd.in/dghjKmQB">https://lnkd.in/dghjKmQB</a>, youtube videos<br>[5] <a href="https://www.linkedin.com/in/ACoAAAEQSn4BZr_C1gLc2eKuoS6LEku5sGKOLtw">Lara Hogan</a>, <a href="https://lnkd.in/dnxKqMdh">https://lnkd.in/dnxKqMdh</a>, blog</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd574db565b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>