<?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 Noah Cantor on Medium]]></title>
        <description><![CDATA[Stories by Noah Cantor on Medium]]></description>
        <link>https://medium.com/@nrcantor?source=rss-1268ce1f03dc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oEgxyJyGqgxou1mE1Or7Bg.png</url>
            <title>Stories by Noah Cantor on Medium</title>
            <link>https://medium.com/@nrcantor?source=rss-1268ce1f03dc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:17:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nrcantor/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[Leaving Medium]]></title>
            <link>https://medium.com/@nrcantor/leaving-medium-4f6c393b6f0d?source=rss-1268ce1f03dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f6c393b6f0d</guid>
            <dc:creator><![CDATA[Noah Cantor]]></dc:creator>
            <pubDate>Tue, 14 May 2024 00:07:39 GMT</pubDate>
            <atom:updated>2024-05-14T00:07:39.216Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TDhNHlBXBctEifHC" /><figcaption>Photo by <a href="https://unsplash.com/@jupp?utm_source=medium&amp;utm_medium=referral">Jonathan Kemper</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Hey everybody, I’m going to keep this realtively short. It’s been a great 10ish years, but I’m moving away from Medium. I’m doing it for a few reasons, and I hope you understand.</p><ul><li>I want more control over my content</li><li>I want more control over my relationships with readers/followers/subscribers</li><li>I have an online presence that isn’t just my writing, and I’d like it all to be in one place</li><li>I get more readers on my own, relatively new, site than I got from Medium</li><li>I started a tech leadership coaching practice, and I’d like to make it easy for people to contact me, if they find my work and want to explore working with me.</li></ul><p>If you’d like to keep reading what I’m writing, you can find it here:</p><p><a href="https://noahcantor.com/blog">Epiphanies for Everybody</a></p><p>Thanks for the support over the years. It meant a lot.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f6c393b6f0d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Effective feedback]]></title>
            <link>https://medium.com/@nrcantor/effective-feedback-bbe77d7492a4?source=rss-1268ce1f03dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbe77d7492a4</guid>
            <category><![CDATA[feedback-culture]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[feedback]]></category>
            <category><![CDATA[tech-leadership-coaching]]></category>
            <dc:creator><![CDATA[Noah Cantor]]></dc:creator>
            <pubDate>Tue, 05 Sep 2023 05:46:29 GMT</pubDate>
            <atom:updated>2023-09-05T21:16:17.056Z</atom:updated>
            <content:encoded><![CDATA[<h3>It’s an all too familiar story — girl gets job, girl wants to grow and develop, girl requests feedback, girl gets radio silence or feedback that disappoints. Why does this happen?</h3><p>It turns out there’s a science to good feedback. And it’s significantly different than anything being taught to leaders on how to give feedback. You know the what I mean — the courses that assume that feedback is something people with power give to people without power in order to get them to change their behaviour to look more like what they want. It’s uncomfortable, resentment-building, and rarely works. But it’s what we have, so it’s what most of us do. We can do better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*admgdgCI8NWtyPfQ" /><figcaption>Photo by <a href="https://unsplash.com/@jasonrosewell?utm_source=medium&amp;utm_medium=referral">Jason Rosewell</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>There are some simple things that make feedback effective. They’re not difficult to implement, but as you’ll see, they require a significantly different approach to feedback than the one described above.</p><p>First, let’s look at some of what it takes for feedback to be effective:</p><ul><li>The source has to be credible</li><li>The giver has to be trusted by the recipient</li><li>It has to be believed by the recipient to be conveyed with good intentions</li><li>The recipient is in the right head space to receive it</li><li>It has to be helpful to the recipient</li></ul><p>This isn’t a complete list, but it’s a fairly important subset because everything on the list shares a trait: it’s under the control of the recipient.</p><p>Almost everything about effective feedback requires significant openness from the recipient. That means that feedback can’t simply be given to somebody. And it cannot be done on a schedule that solely suits the giver.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cbqVT8dr_3RIlMDK" /><figcaption>Photo by <a href="https://unsplash.com/@linkedinsalesnavigator?utm_source=medium&amp;utm_medium=referral">LinkedIn Sales Solutions</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Armed with this information, it becomes clear that in order for feedback to be effective, we have to upend the existing paradigm about giving feedback at work. Rather than a manager collecting feedback and giving it to the recipient on an annual basis, or pulling somebody aside for a chat where it feels like the recipient has done something wrong, we need people who want feedback to ask for it. They need to pull the information they’re looking for, from the people they think have it, at a time when they’re ready to hear whatever is going to be said. And even then, it’s possible the giver will give something the recipient isn’t expecting, or respond in a way that the recipient doesn’t anticipate.</p><p>So then, what can someone do when they want feedback? Other than keeping the guidance above in mind, there are a few other things they can do to maximise their chances of getting the feedback they want. Like the previous things, these are within the control of the requester.</p><p>Good requests for feedback should be:</p><ul><li>Specific</li><li>Interactive</li><li>Timely</li></ul><p>Specific requests are easier to respond to than general ones. “How am I doing?” is about as useful as, “good job.” While it might seem like a great idea to allow the giver to have as much leeway as possible, the truth is that being asked for general feedback puts the giver in an awkward spot — what if the feedback given isn’t what was intended? What do they want feedback on? — the more specific the request, the easier it is to respond to, and the greater the chance of getting something relevant and helpful.</p><p>There’s an element of interactivity in effective feedback. It’s not information, handed down from on high, inviolate in its perfection. Feedback is a conversation. It’s a request for help, and a fulfilment of that request, with opportunities to clarify, redirect, or even stop if it goes sideways.</p><p>Last, by making a request soon after the event they want feedback on, the recipient does two things: 1) They maximise their chance of learning. Feedback close to an event ensures details are still fresh and opportunities to learn are at their highest; and 2) They maximise the chance that the giver remembers the events clearly and can provide specific feedback. The greater the time between event and request, the less valuable the feedback will be.</p><p>There’s a genuine skill to excellent feedback. It’s something we all are born knowing, but often lose on our path to adulthood. It can be recaptured, and the experience of feedback can be a joyful one. I am hopeful that with what I’ve said here, you can get closer to having better feedback conversations, and accelerate your own growth.</p><p>I invite anybody who would like to have a better experience of feedback to get in touch.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbe77d7492a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[There’s a graphic making its way around LinkedIn. Perhaps you seen it?]]></title>
            <link>https://medium.com/@nrcantor/theres-a-graphic-making-its-way-around-linkedin-perhaps-you-seen-it-f04d370e43db?source=rss-1268ce1f03dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/f04d370e43db</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Noah Cantor]]></dc:creator>
            <pubDate>Sat, 02 Sep 2023 00:21:15 GMT</pubDate>
            <atom:updated>2023-09-02T00:21:15.820Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Impact of Setting Targets</h3><p>There’s a graphic making its way around LinkedIn. Perhaps you seen it?</p><figure><img alt="Bad example of Goodhart’s Law." src="https://cdn-images-1.medium.com/max/800/1*dcfBu-K6s3uqOVaAUWaC7w.jpeg" /></figure><p>It correctly states Goodhart’s Law, and then uses incorrect illustrations to elaborate. I’ve seen it enough times that I think it’s worth pointing out where it goes wrong.</p><p>Goodhart’s Law doesn’t say, “Don’t measure things,” It says, “Don’t turn your measurements into targets.”</p><p>In the example graphic, maybe the company sells 3000 nails per day. Maybe they aren’t making enough. So management creates a target of 3000 nails. Now people know what to do, right? Wrong. If the system they’re in doesn’t enable the creation of 3000 nails/day, people will cut corners to meet the number — quality, for example, will degrade; nails will be shipped that would previously have been reworked due to QC problems. If the machine makes smaller nails faster, nails will probably get smaller, even if that’s not what customers need. The system needs to change, but the burden has been placed on the people.</p><p>Let me illustrate with a real example from a company I worked with (I was working in a different area, so I was an observer of what was going on, not a participant in rectifying it). We’ll call it Innosure (I hope there’s no real Innosure out there). For years, Innosure had been struggling with major outages, downtime, data corruption, and other major issues. So far, they had managed to keep it out of the public eye, but the board thought it was only a matter of time until something happened that was so big it couldn’t be kept out of the papers.</p><p>Innosure’s board decided that something had to be done. After much deliberation, they settled on a plan: set a limit to the number of allowed P1 and P2* outages that were acceptable; gradually reduce the nuber every year until the company was down to zero; introduce consequences for failure to keep outages below the target; and require reporting on very P1 or P2 outage, so they were in the loop about what was going on. Their thinking was that setting a target of this nature would encourage people to focus on the things that tended to fail, and improve them, so that they didn’t fail. And requiring them to report on them would ensure that they weren’t simply hidden from the board’s sight. All very reasonable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hQanwb5hxK5JHPX-" /><figcaption>Photo by <a href="https://unsplash.com/@kindandcurious?utm_source=medium&amp;utm_medium=referral">Kind and Curious</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Unfortunately, things didn’t work out the way the board thought they would. In fact, things got worse. But why? In order to understand why their mandate failed, it’s important to understand a little of how Innosure worked.</p><p>The way Innosure’s systems worked (development, product, support, infrastructure, and all the interconnected people) was that every year, leadership would set a budget for what they expected to spend over the course of the year. They would also come up with changes and new features they wanted added to the software. These additions would be prioritised and incentivised. And each team, or each area, would be responsible for their delivery. These items <em>always</em> superseded attempts to create more stability, deal with old debt, or otherwise improve existing systems (there’s a lot to unpack to understand why this happened, so for now we’re just going to say that it happened).</p><p>Innosure’s board and executive also weren’t aware of the level of debt and fragility in the system, so when it came time to budget, they were informed mostly by previous budgets, and not by the significant investments required to stabilise or improve their existing technical systems.</p><p>When the mandate was handed down to people responsible for doing the work, they knew it was impossible to achieve the target by doing things the right way — the rest of the organisation wasn’t aligned behind the changes that would have to happen to reduce outages, so none of their normal workload would be reduced in order to achieve the target. Did they let that stop them? Of course not. They had a target, and bonuses riding on achieving them.</p><p>That year, they hit their target. But knowing what we know about the organisation, we can be sure they didn’t do it by doing what the board wanted them to do. So, how did they achieve it? In the end, it was rather simple. As the year went on, and they got closer and closer to hitting the target, they would start recategorising outages from P1 or P2 down to P3 or P4. That way the board didn’t have to be told about them, and it wouldn’t affect their bonuses or push them over the target. It was genius… and terrible for the organisation.</p><p>During a P1 or P2 outage, the entire organisation is mobilised to reduce the impact, recover quickly, and ensure no customers are impacted more than is absolutely necessary. Time and money were spent on rectifying any problems that occurred during a P1 or P2, in order to keep customers from getting upset. By incorrectly categorising P1 and P2 outages as P3 or P4 outages, the following things happened (or didn’t):</p><ol><li>Non-technical teams were not mobilised to ensure customers remained satisfied</li><li>The board was not notified of major outages</li><li>Teams outside those that were immediately affected weren’t available to help resolve problems</li></ol><p>Things got worse. At the end of year 1, the board saw that their plan was working, so they continued with it. As far as they knew, their target was effective. Numbers don’t lie.</p><p>During year 2, things got more fragile. As the appetite for P1 and P2 outages continued to decrease, the number of real P1 and P2 outages increased. But because of the numbers, there were no questions about why there were more outages, or what would have to happen to reduce them. They were on their way down, after all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HKsEfpKy3qXAB_wUv46eow.jpeg" /></figure><p>There is a fix for this problem. The first step is understanding how bad the problem is. And that won’t happen while the target exists. Removing the target allows more honest reporting and measuring of what’s going on. That enables the executive and the board to understand the scale of the problem. And it enables them to try new things to reduce outages. By keeping P1 and P2 outages as a measure, instead of as a target, the variability in frequency can be identified, which then allows the organisation to start identifying patterns and causes (maybe outages go up after big releases, or when the main database server runs out of memory, or when a certain faulty router has a blip).</p><p>By keeping the data as raw as possible, it’s possible to see if particular interventions are effective, or they make things worse. Each time we try something, we can see the impact. It might take time to see it, but we will be able to. As soon as we turn the measure into a target, we skew behaviour. And it’s incredibly difficult to know how we will end up shaping behaviour. Since there are numerous ways the new behaviour could be harmful, and only 1 or 2 ways it could be helpful, we will almost always end up with unintended, harmful behaviour.</p><p>Once it’s clear what’s happening to outages, the second step becomes possible — learn how the various incentives and priorities being set impact the organisation’s ability to stabilise and modernise the existing technical systems.</p><p>Step 3 is to then gather information on what investments would be necessary to start improving the outage data. How to fix or eliminate the patterns (smaller releases, fragmenting the single database, replacing the router, etc), thereby reducing aggregate outages.</p><p>Step 4 is to implement a change, measure its impact, and decide whether it was an intervention worth keeping, or whether it needs to be removed.</p><p>Without Step 1, however, none of the other steps are ever seen or understood, because the scale of the problem can never be understood.</p><blockquote><em>if management sets quantitative targets and makes people’s job depend on meeting them, “they will likely meet the targets — even if they have to destroy the enterprise to do it.” -Deming</em></blockquote><p>Ultimately, the measure was never the problem. The measure is just data. It’s how the measure is used, and whether it’s made into a target, that determines whether there’s a problem.</p><p>* Lots of companies define their own outage scales. What’s important is that a P1 outage usually refers to something that takes the entire system down for all customers. A P2 outage is something that takes the entire system down for some customers, or takes part of the system down for all customers. P3 outages are those that take a part of the system down, but there’s a workaround. Severity is normally a 4 or 5 point scale.)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f04d370e43db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Change (part 1)]]></title>
            <link>https://medium.com/@nrcantor/how-to-change-part-1-ef44079abbba?source=rss-1268ce1f03dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef44079abbba</guid>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[leadership-coaching]]></category>
            <category><![CDATA[technology-leadership]]></category>
            <category><![CDATA[transformational-leaders]]></category>
            <category><![CDATA[organizational-change]]></category>
            <dc:creator><![CDATA[Noah Cantor]]></dc:creator>
            <pubDate>Thu, 31 Aug 2023 23:02:28 GMT</pubDate>
            <atom:updated>2023-08-31T23:02:28.058Z</atom:updated>
            <content:encoded><![CDATA[<p>In my<a href="https://medium.com/@nrcantor/knowing-you-have-to-change-isnt-enough-e1a7baecbea1"> last post</a>, I gave some basic (but possibly difficult) ideas on what to change. Now I want to talk a little bit about how. This will necessarily be incomplete, but it’s a start.</p><p>Looking back at my previous post, what stood out for you as the basis for industrial management? Blame is obvious, but why do we need to know who to blame? Because of the train wreck, management lost all faith in their employees. Identifying every step, and every role, so they would know who to blame is a direct result of that lack of trust.</p><p>So, even closer to the core of industrial management than blame, is mistrust. Nobody is trusted to do the right thing. Nobody is expected to do the right thing without supervision. And the tacit expectation is that without you taking an active role, people would, at best, do nothing or, at worst, usually do the wrong things.</p><p>You probably don’t see yourself this way. I don’t blame you (see what I did there?). I didn’t either. Most of us don’t. But whether we see ourselves this way, or not, is irrelevant. We have, almost all of us, internalised a lifetime of beliefs about how organisations ‘should’ work, and how people ‘should’ behave, that are based on these assumptions. So even if you haven’t adopted them consciously, there’s a good chance that blame and mistrust are the unspoken beliefs that underpin a lot of what you do and how you behave toward your teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iB7xKrJIAR60iJ_C" /><figcaption>Photo by <a href="https://unsplash.com/@shot_by_teo?utm_source=medium&amp;utm_medium=referral">Matteo Di Iorio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Before you read any further, take the time to reflect and think about what I’ve said. Not just here, but in the previous article. Maybe I’ve got you all wrong; maybe you’ve always hated the way that management asks you to behave. You’ve done it, but internally been in a state of constant rebellion and aggravation. Maybe you’ve always been looking for a better way, but haven’t known what it was. The rest of the article will still be here when you get back.</p><p>If you want to shift your viewpoints away from blame and mistrust (no matter how the language has changed to try to hide the origins), start right at the very heart of the matter. Start here:</p><ol><li>What would it look like if my organisation believed, at its core, that people could be trusted?</li></ol><ul><li>How would employees and customers be treated?</li><li>What information would we share, and what would we keep private?</li><li>What would we tell people?</li><li>What processes would we have?</li><li>What governance would there be?</li><li>What practices would we have in place?</li><li>How would we recognise people’s contributions?</li><li>How is that different to what we have today?</li><li>What role do I play in that difference?</li><li>What role can I play in making the change?</li></ul><p>I suspect, based on my own experience, that when you ask these questions, you’ll find that the way you treat people is far from how you would treat people if they were trusted. I’m not singling you out, or trying to shame you — I started in the same place. I went on a journey, just as many others have, of learning new ways of thinking and being that shifted my perspective. We are all on our own journeys.</p><p>Now that you’ve seen how things are different, it’s time to start thinking about how to tackle the change in you that you want to see in your organisation. This is where a guide, a coach, or a mentor, can really speed things up, and help you be honest with yourself about whether you’re tackling the challenges, or shying away from them.</p><p>The reason some sort of guide is so valuable is because what comes next is hard. When you looked inside, and found that your beliefs (hopefully unintentionally) align with blame and mistrust, it may have shocked you. When you thought about how your organisation would behave if it trusted people, you may have found that it’s miles away from where you are.</p><p>What we’re going to do next is answer the questions I posed before. Each one. You don’t have to have complete, or perfect answers. That’s not the aim. Instead, every time you dig deep to answer one of the questions, you may find yourself uncomfortable. Lean into that discomfort. Explore it. Find the cause of the discomfort. Understand it. Accept it. Address it. Come to peace with things. And finally, change it. That’s the change in you that will enable the change in your teams and your organisation.</p><p>If you aren’t ready to face that level of discomfort, that’s OK. There are numerous companies that are highly successful operating under the old management rules. There’s a good chance you’ll be able to finish your career before new ways of thinking become mandatory for success. So you don’t have to be in any rush. But when you’re ready, we’ll be here.</p><p>Knowing that you want to change isn’t enough. You have to want to change, know what you want to change to, and how to change. The process is long and, often, difficult. It will have setbacks. It won’t be smooth sailing. When you’re ready, change will come. And when you’re looking at the world with your new perspective, you’ll marvel at how far you’ve come, and how much different things look, from your new vantage point. New ideas will come to you, and new ways of interacting with people will seem obvious, when they wouldn’t have occurred to you before. It’s a journey I’ve been on, and one I suggest for anybody who hasn’t been on it, yet.</p><p>Let me know if you want a guide.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef44079abbba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Knowing You Have to Change Isn’t Enough]]></title>
            <link>https://medium.com/@nrcantor/knowing-you-have-to-change-isnt-enough-e1a7baecbea1?source=rss-1268ce1f03dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1a7baecbea1</guid>
            <category><![CDATA[transformational-leaders]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[organisational-change]]></category>
            <category><![CDATA[leadership-coaching]]></category>
            <dc:creator><![CDATA[Noah Cantor]]></dc:creator>
            <pubDate>Wed, 30 Aug 2023 00:02:33 GMT</pubDate>
            <atom:updated>2023-09-01T01:56:31.036Z</atom:updated>
            <content:encoded><![CDATA[<p>In my last post I talked about how leaders need to change if they want their organisations to change. I think most leaders on the wrong side of change know something has to be different, but what, exactly? And how?</p><p>It is not enough to know we need to change; we must also know what to change to, and how.</p><p>I can give a start on what, but how is much harder. It’s very much an individual journey. I’m not sure there’s a one-size-fits-all answer. We’ll start with what, and see how things go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TMjXqFnSBcJ7MR16" /><figcaption>Photo by <a href="https://unsplash.com/@goian?utm_source=medium&amp;utm_medium=referral">Ian Schneider</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Your organisation is almost certainly built on command and control principles introduced in the 1800s. I’m not knocking those principles, they served industry well for more than 100 years. But times change, and needs change. Unfortunately, ingrained habits and organisational memory is very difficult to change.</p><p>Let’s go back to the 1800s for a minute. Management at this time, wanted to know what everybody was doing. They wanted to know why. And they wanted to know who to blame when things didn’t happen correctly (see <a href="https://www.leanessays.com/2007/09/train-wreck-management.html">train-wreck management</a> for a primer on why). Company structures, with functional silos, and super-specific job descriptions, are the result of management wanting to know who to blame — who to fire — when things go wrong.</p><p>You know those people in your organisation who won’t step outside their job description? Who won’t help an adjacent area, or lift a finger to do more than they have to? That’s intentional. According to those that created job descriptions, that behaviour is exactly what they intended — nobody steps out of their realm of specialisation. Job descriptions were specifically created as a tool to ensure nobody was doing something they shouldn’t be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bOCMKjxKnyDzfDfa" /><figcaption>Photo by <a href="https://unsplash.com/@rojekilian?utm_source=medium&amp;utm_medium=referral">Sarah Kilian</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Is that you? Is it what you want to be? Is it what you want your teams to be? Does it help you when your developers won’t write tests, your sales people aren’t interested in learning about product, or your product people don’t care about debt or code quality?</p><p>If you want them to change, first you have to let go of the notion that highly siloed, functional job descriptions are useful. You have to let go of the subconscious notion that if things go wrong, at least you’ll know who to blame.</p><p>High-performing organisations don’t blame people when things go wrong. They know the system puts significant restraints on what people can do, and if something went wrong, it’s probably down to how the system works. There’s no point in blaming individuals.</p><p>High-performing organisations trust their staff to make the right decision, given the right information. As a leader, your job is no longer about knowing the right decision, but building an environment where people who know their roles better than you ever will are comfortable making decisions.</p><p>Do you know what erodes people’s willingness to take risks, and therefore make independent decisions? Blame. When someone gets in trouble for a decision made in good faith, it reduces their (and everybody else’s) desire to make decisions. Instead of a workforce of experts collaborating and crafting amazing things, you get a hidebound organisation where all decisions are kicked up to you, and everything moves at a crawl.</p><p>Ultimately, your ability to bring about successful change depends on your desire to acknowledge your own beliefs, face them, and change them. Once you’ve changed your thinking, the rest will be much easier.</p><p>In summary, here are a few things you can do to start introducing change, both in yourself, and in your teams:</p><ol><li>Let go of the notion that blame has any part to play in your organisation</li><li>Reduce the number and specificity of job titles</li><li>When a mistake happens, investigate how the system allowed or encouraged it to happen. Even better, let your people do it, and ask them what they find.</li></ol><p>There’s a lot more to do, but there’s a good chance you’ll find these challenges difficult enough, even as a starting point. They’ll require more change from you than I think you expect.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1a7baecbea1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transformation Starts With You]]></title>
            <link>https://medium.com/@nrcantor/transformation-starts-with-you-c4f6b1468805?source=rss-1268ce1f03dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4f6b1468805</guid>
            <category><![CDATA[leadership-coaching]]></category>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[transformational-leaders]]></category>
            <category><![CDATA[coaching]]></category>
            <dc:creator><![CDATA[Noah Cantor]]></dc:creator>
            <pubDate>Tue, 29 Aug 2023 06:49:40 GMT</pubDate>
            <atom:updated>2023-08-29T06:49:40.521Z</atom:updated>
            <content:encoded><![CDATA[<p>Transformation isn’t just for other people.</p><p>In all the conversations I’ve had, or consultant reports that I’ve read in the last 10 years, every description of &lt;Buzzword&gt; Transformation talks about changing things on the ground, or possibly up as high as middle management. They talk about changing ways of working. They talk about teams doing things differently.</p><p>They don’t talk about the role and responsibility of the executive. There can be no organisational change without leadership change. When you want people to adopt new thinking, behaviours, habits, practices, and approaches, you need to be clear on why they’re adopting them. If you, as the executive, don’t see things through the desired new perspective, then you will not manage things as if the new perspective is reality. If you can’t manage things differently, then all your words and desires are meaningless. People respond to what the system demands, not your words. For many of them, the words are familiar; they’ve heard them before, in one form or another, for years. I don’t need to tell you this; you already know that actions speak louder than words.</p><p>If you tell people to release low risk, well-tested, validated changes, frequently, but you reward heroics, working after hours, and crunch-time commitment, then you will get heroics, working after hours, and crunch-time commitment. You will not get frequent, low-risk, well-tested, validated changes.</p><p>The way you, as a leader, see the world, has to change, if you want your organisation to change. There are no exceptions.</p><p>To transform your organisation, you must first transform yourself. Once you have changed, the needs of your new perspective will become clearer, and the changes you need to make will become much more obvious. If you can’t make that commitment to yourself, you’ll never be able to coerce others to make it, either.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4f6b1468805" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Change starts within]]></title>
            <link>https://medium.com/@nrcantor/change-starts-within-343601bd69c?source=rss-1268ce1f03dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/343601bd69c</guid>
            <category><![CDATA[management-coaching]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[change-leadership]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[technology-leadership]]></category>
            <dc:creator><![CDATA[Noah Cantor]]></dc:creator>
            <pubDate>Fri, 04 Aug 2023 22:39:08 GMT</pubDate>
            <atom:updated>2023-08-04T22:39:08.480Z</atom:updated>
            <content:encoded><![CDATA[<p>“The principal obstruction to an organisation getting to where its managers most want it to be lies in the minds of its managers.” -Russell Ackoff</p><p>Why can we accept that this statement is true, even though it rankles?</p><p>Let’s start with a basic premise. It has been true everywhere I’ve gone, and everywhere I’ve worked: People are doing the best job they know how to do.</p><p>What does this mean?</p><p>It means that the current performance of the organisation is a result of everybody, at every level, doing their job the best way they know how to. Whether it’s janitors, software developers, machinists, managers, or sales people, everybody is doing their best, in the environment they’re in. The results that your organisation is currently getting is what happens when everybody does their best, with their current knowledge and capabilities. That includes you.</p><p>Now let’s introduce another premise: Senior managers at an organisation are responsible for the policies, structures, environment, culture, incentives, etc that make up the system.</p><p>What does this mean?</p><p>It means that the way the system operates — how it rewards and whether it punishes, how it hires, what it values — is determined by its management.</p><p>Now let’s introduce our last premise: Performance of individuals in a system is 95% a result of the system, and 5% the individual’s performance (Deming).</p><p>What does this mean?</p><p>It means that the way that people behave in the system, and their ability to perform well, is determined almost entirely by the system itself. That same system that management is responsible for.</p><p>Taken together, these 3 things lead to the inevitable conclusion that “The principal obstruction to an organisation getting to where its managers most want it to be lies in the minds of its managers.”</p><p>Rather than introduce a massive change program, then, if managers want change, the most effective place to start is with themselves. By facing our internal beliefs, internal understandings, and internal assumptions, we gain the power to change them. As these internal reference points change, our behaviour changes. These changes lead to changes in how and what we manage, which then leads to change in others.</p><p>This is not an easy journey for most people. Working with someone who’s done it can make it faster, easier, and less lonely. I’ve been through it. I started as a technologist in traditional organisations, went through the difficult shift to agile thinking, adopted devops when it was first being formulated, lead organisations, managed teams, and consulted for people in every one of those positions. I can help.</p><p>— — — — -</p><p>👣 If you’ve gotten this far, something I said resonated with you. If you want change for your organisation, and you’re ready to change your beliefs to make it happen — if you’re ready to walk the path — DM me. I’d love to catch up and see if we can help each other.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=343601bd69c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Every high-end tech consultancy has the same problem. It manifests in one of two ways:]]></title>
            <link>https://medium.com/@nrcantor/every-high-end-tech-consultancy-has-the-same-problem-it-manifests-in-one-of-two-ways-df8fe56b9ca?source=rss-1268ce1f03dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/df8fe56b9ca</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[organisational-change]]></category>
            <category><![CDATA[technology-leadership]]></category>
            <category><![CDATA[technology-coaching]]></category>
            <dc:creator><![CDATA[Noah Cantor]]></dc:creator>
            <pubDate>Thu, 03 Aug 2023 05:32:24 GMT</pubDate>
            <atom:updated>2023-08-03T05:33:45.453Z</atom:updated>
            <content:encoded><![CDATA[<p>Every high-end tech consultancy has the same problem. It manifests in one of two ways:</p><ol><li>“We do great work, but it doesn’t outlive our presence.”</li><li>“We do great work, but it never fixes anything.”</li></ol><p>Often a tech consultancy is hired to solve a perceived problem. They come in, and do a lot of work, and cost a lot of money, and the problem doesn’t get solved. Why?</p><p>Not every problem has a clear cause an effect. Just because you see a problem in technology doesn’t mean it originated there. In all likelihood, what you’re seeing is a symptom of a problem that originated elsewhere.</p><p>For example:</p><ul><li>You need to pivot. Your technical people appear incapable of making the necessary changes to support the new direction. So you hire outside help. But why aren’t your internal people able to make the change?</li><li>For years, to keep costs down, training, support, development, growth, and experimentation have all been curtailed. Your people don’t know enough to make the change you want. If you hire a tech consultancy, will your people be able to support what they deliver?</li><li>You’re embarking on a modernisation journey. You have 30 years of legacy systems that haven’t been maintained, updated, or moved-away-from. The people in your organisation are great at maintaining those systems. The people who want to do something different realised a long time ago that they would have to go somewhere else to do it. Are the people you have going to be able to understand the approach that a high-end tech consultancy takes?</li><li>Your systems have grown organically over time. Your sales team have continually told you that adding feature X, or report Y, will win the sale. You added them. Then the next client wanted something different, so you added that. Now your systems are big, inefficient, unwieldy, complicated, and difficult to understand. Will you be able to move quickly when there’s a sudden demand for change?</li></ul><p>I’ve seen this pattern play out repeatedly.</p><p>When a client is frustrated, good tech consultancies want to help. That’s a large part of why people build and work in the services space. Unfortunately, this particular client frustration, while it lands on the consultancy, didn’t originate there. In fact, the consultancy has literally no power to resolve the issue. This is because the problem is a systemic issue in the client’s organisation.</p><blockquote>It doesn’t matter how much you pay your tech consultants, they aren’t going to be able to fix non-tech problems.</blockquote><p>No tech consultancy in the world can fix underinvestment, neglect, or the fact that you’re a sales-driven organisation. Those aren’t things they’re equipped to do. What they are equipped to do is deliver fantastic work that will blow people’s minds, and be fast, secure, scalable, reliable, etc. But none of that matters if it’s built on a foundation made of legacy systems, lack of strategy, inability to say no, or being seen as a cost the business has to bear (instead of a strategic area to invest in).</p><p>Fix those issues first.</p><p>The first step is accepting that mistakes were made. The reason this is important is because a lot of leaders fear the vulnerability associated with admitting mistakes.</p><blockquote>It doesn’t matter who made the mistakes. What’s more, trying to figure out who to blame will make things much worse.</blockquote><p>Regardless of who made the mistakes, the collective decisions of the past have created your present. That means the collective decisions of the present will create your future. There’s no magic wand that will enable you to suddenly do everything you want at the speed you want to do it. There’s only the hard work of either updating or replacing your old systems, investing in your people, ensuring that control of the organisation is collaborative, and not dictated exclusively by one function (I picked on sales in my examples, but it can be any function).</p><p>After you’ve gotten on top of the organisational challenges — your people are learning, churn is decreasing, commincation between you and the other executives is improving, and transparency has increased — then you can hire a high-end tech consultancy. They’ll land in fertile ground, and will accelerate the growth of your people, your products, and your capabilities.</p><p>If this sounds enormously difficult, it’s because it is. Changing the way you make decisions does not come easily. Our decisions are based on our beliefs about how things work, or how things should work. When we admit that we have made a mistake, those beliefs come into question. If we don’t have a new set of beliefs available to us, then we end up sticking with the beliefs we had, which means we end up sticking with the decisions we made. That means we’ll get more of what we’ve always gotten.</p><p>Change comes from external input. Sometimes that’s a person, or a book, or a video, or a chance conversation. But ultimately, new information is required in order to develop new beliefs, and thereby new decisions. If you want to embark on a change journey for your organisation, it’s going to mean embarking on a change journey for yourself. And that’s best done with company — with someone who’s been there before, or someone who can help you see how to approach things differently. Preferably both. So before hiring that tech consultancy, and before starting that change program, get a coach, or some other means of self-discovery and change. The rest will be much easier as a result.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df8fe56b9ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making Money]]></title>
            <link>https://medium.com/@nrcantor/making-money-23312d326c54?source=rss-1268ce1f03dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/23312d326c54</guid>
            <category><![CDATA[business]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[open-management]]></category>
            <category><![CDATA[theory-of-constraints]]></category>
            <dc:creator><![CDATA[Noah Cantor]]></dc:creator>
            <pubDate>Mon, 26 Jun 2023 21:31:52 GMT</pubDate>
            <atom:updated>2023-06-26T21:31:52.326Z</atom:updated>
            <content:encoded><![CDATA[<p>What is the purpose of a business?</p><p>Many people think the purpose is to make money. Nothing more, nothing less. And the quest to make money excuses all manner of sins. If there’s nothing more to an organisation than to make as much money as quickly as possible, all sorts of things come out of it. Taking advantage of customers, employees, pension schemes, the environment, and more, all logically come out of the notion that only right now (or the next 3 months) matters. Raids on pensions, asset stripping, and reducing headcount to the bare minimum are all reasonable actions when this perspective is taken.</p><p>There’s no need to worry about what the future might bring if you’re only concerned with the present. In face, you’re encouraged to mortgage the future to pay for the present.</p><p>Eli Goldratt thought the goal was slightly different. He used to talk about the purpose of a business (any business) being to “make money now and in the future.” It’s remarkable, the enormous impact that can be had with the addition of a few small words.</p><p>“Now and in the future” means that maximising profits today may not serve the goal. It means the ability of the organisation to continue to earn more money in the long-term is a primary consideration for whatever we choose to do today. In fact, when we accept the implications of this subtle change, a massive change in behaviour is very common.</p><p>When you look at the consequences of only caring about profit now, it’s clear that in order to profit in the future, none of those things can happen. Employees and customers have to be looked after, pension/benefit schemes need to be protected, the environment needs to be considered, asset stripping is impossible, reducing headcount becomes a last resort, debt gets paid regularly, and shareholders get put at the end of the queue.</p><p>It’s amazing how a few words can turn conventional thinking inside out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23312d326c54" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Job Description Silos]]></title>
            <link>https://medium.com/@nrcantor/job-description-silos-e5462291933b?source=rss-1268ce1f03dc------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5462291933b</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[conways-law]]></category>
            <category><![CDATA[job-description]]></category>
            <category><![CDATA[silos]]></category>
            <category><![CDATA[technology-leadership]]></category>
            <dc:creator><![CDATA[Noah Cantor]]></dc:creator>
            <pubDate>Sun, 25 Jun 2023 21:31:31 GMT</pubDate>
            <atom:updated>2023-06-25T21:31:31.995Z</atom:updated>
            <content:encoded><![CDATA[<p>When trying to build cross-functional teams, or even teams that just cooperate with each other, don’t underestimate the power of the environment to get in your way (or to help).</p><p>Lots of people are familiar with Conway’s Law, but many people don’t realise that it matters even inside a team.</p><p>If you have a DBA, a tester, a front-end developer, and a back-end developer, your system will reflect each of those specialties. It will have parts that cannot be understood or worked on by anybody but people who fill those roles. What’s more, the job descriptions themselves will discourage people from working on other areas.</p><p>Why?</p><p>Because progress for a DBA look like jr DBA -&gt; DBA -&gt; sr DBA; progress for a tester looks like jr tester -&gt; tester -&gt; sr tester -&gt; staff tester. Your combination of professional ladder and siloed job roles discourage people from learning skills that aren’t directly linked to their roles.</p><p>The more role names and job descriptions you have, the worse it gets. If you want people to share the same work, and the same sense of responsibility, give them the same titles. There will still be areas that draw some people more than others, but by deliberately removing organisational boundaries, and recognising progress that crosses skillsets (and not just progress that deepens them), you remove the systemic pressure to stay in your lane.</p><p>Ultimately, if you want small, cross-functional teams, everybody in the team needs to be able (and willing) to pitch in to get things out the door. Even if it’s not their normal area.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5462291933b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>