<?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 Herman Veitch on Medium]]></title>
        <description><![CDATA[Stories by Herman Veitch on Medium]]></description>
        <link>https://medium.com/@hgveitch?source=rss-10d7673e1cc1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ozVanPMvm_9nzoTnUKFVFQ.png</url>
            <title>Stories by Herman Veitch on Medium</title>
            <link>https://medium.com/@hgveitch?source=rss-10d7673e1cc1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:32:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hgveitch/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[Your Brain Is Not Broken]]></title>
            <link>https://hgveitch.medium.com/your-brain-is-not-broken-0acd0f703e32?source=rss-10d7673e1cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/0acd0f703e32</guid>
            <category><![CDATA[neuroscience-of-burnout]]></category>
            <category><![CDATA[burnout-recovery]]></category>
            <category><![CDATA[reverse-burnout-brain-fog]]></category>
            <category><![CDATA[chronic-stress-symptoms]]></category>
            <category><![CDATA[burnout-recovery-coaching]]></category>
            <dc:creator><![CDATA[Herman Veitch]]></dc:creator>
            <pubDate>Thu, 14 May 2026 12:11:42 GMT</pubDate>
            <atom:updated>2026-05-14T12:11:42.862Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>The Neuroscience of Burnout and the Path to Recovery</strong></h3><p>Many high achievers reach a point where a long weekend or a week at the beach no longer helps. You wake up on Monday morning feeling just as depleted as you did on Friday afternoon. This is not simple tiredness. It is not a lack of discipline. Recent research from 2016 to 2026 confirms that burnout is a measurable, biological syndrome. By understanding the <strong>neuroscience of burnout</strong>, you can stop blaming yourself and start a recovery protocol that actually works.</p><p><strong>Chronic Stress Symptoms and Solutions</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kgNDpx4qfr02guOc4XBozw.jpeg" /></figure><p>Burnout is a state of vital exhaustion. It happens when job demands consistently outweigh your internal and external resources. This chronic mismatch triggers three specific changes in your brain that explain common <strong>chronic stress symptoms and solutions</strong>.</p><p>First, your <strong>Amygdala</strong> — the brain’s stress alarm — becomes enlarged and hyper-reactive. This is why you feel “on edge” 24/7. Even small emails trigger a full-blown stress response. Second, your <strong>Prefrontal Cortex</strong> actually thins. This area handles logic and focus. When it weakens, you experience “brain fog.” Simple decisions feel like mountain climbing. Third, your <strong>Reward System</strong> numbs out. Tasks that used to bring a sense of accomplishment now feel empty.</p><p><strong>How to Reverse Burnout Brain Fog</strong></p><p>A common mistake is treating burnout like physical fatigue. If you have a broken leg, you do not just sleep; you get a cast to provide external structure. Burnout is similar. Sleep is passive. Learning <strong>how to reverse burnout brain fog</strong> requires <strong>Active Recovery</strong>. You must engage in specific protocols to down-regulate your nervous system and “rewire” the neural pathways that chronic stress has damaged.</p><p>Because burnout affects your logic centre, you are trying to solve the problem with a compromised “CEO.” This is exactly why self-help often fails. It is difficult to plan a recovery strategy when the planning centre of your brain is offline.</p><p><strong>The Role of an Executive Burnout Specialist</strong></p><p>This is where an <strong>executive burnout specialist</strong> becomes a mechanical necessity. In my practice, I act as an external structure for your brain while it heals. We do not just talk about feelings; we implement a system to restore your cognitive and emotional capacity.</p><ul><li><strong>Calming the Alarm:</strong> We identify specific “Job Demands” that keep your Amygdala on high alert. We use physiological resets like Non-Sleep Deep Rest (NSDR) to signal to your nervous system that the threat is over.</li><li><strong>Rebuilding the Logic Centre:</strong> While your Prefrontal Cortex recovers, I provide the organisational structure you currently lack. We audit your workflows to reduce “cognitive friction,” giving your brain the space it needs to thicken those neural connections.</li><li><strong>Reactivating the Reward System:</strong> We move beyond “getting things done.” We use values-based coaching to align your daily actions with what matters to you. This “wakes up” your reward system and makes work feel meaningful again.</li></ul><p><strong>Sustainable Burnout Recovery Coaching</strong></p><p>The most important takeaway from modern research is that these changes are <strong>reversible</strong>. Your brain is plastic. It is not permanently damaged; it is simply adapted to a high-stress environment. You can move from a “threat” state back to a “growth” state.</p><p><strong>Burnout recovery coaching</strong> provides the external structure your brain needs to navigate this shift. You do not need more discipline. You need a better strategy and the right partnership to execute it. Recovery is an active process. It starts with the decision to stop trying to fix a systemic biological problem with a longer nap.</p><p>If you recognise yourself in the description of the enlarged alarm or the thinning logic centre, let’s talk. We can move you from exhaustion to a state of sustainable, resilient flow. I invite you to reach out for a consultation. Whether for yourself or a loved one who is struggling, the path to recovery is paved with science, structure, and support.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0acd0f703e32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Self, My Ego, and I]]></title>
            <link>https://hgveitch.medium.com/my-self-my-ego-and-i-ea6e35ba7a60?source=rss-10d7673e1cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea6e35ba7a60</guid>
            <category><![CDATA[universal-truths]]></category>
            <category><![CDATA[self]]></category>
            <category><![CDATA[beauty]]></category>
            <category><![CDATA[belonging]]></category>
            <category><![CDATA[ego]]></category>
            <dc:creator><![CDATA[Herman Veitch]]></dc:creator>
            <pubDate>Thu, 23 Apr 2026 09:10:49 GMT</pubDate>
            <atom:updated>2026-04-23T09:10:49.880Z</atom:updated>
            <content:encoded><![CDATA[<h3>“Just be yourself”</h3><p>This advice is often heard. Sometimes, when we stress ourselves about presenting before people, going on a blind date, or preparing for an interview, and others want to encourage us, they give this advice. <br> But who is this self that we should be? And how am I to be this self? Am I not myself automatically?</p><p>Buddhist and Zen traditions say there is no self. Some Neuroscience findings agree with them and say it is just a projection of the mind. Then how can I be something that is not there?</p><p>Traditional psychologists like Freud and Jung complicate understanding by pulling the self apart. Freud thinks the self is an Id, an Ego and a Superego. Jung adds an extra layer of the collective unconscious. For me, this just complicated the issue. To understand their ideas, I need to learn the language of 20th-century European men, look up definitions of definitions. And at some point, I lose the plot. Yes, each field has its own vocabulary, and for someone schooled in it, it clicks. But for the normal guy, it is a stretch.</p><p>Modern psychology does not make it less complicated with multi-layered personality tests like the Myers-Briggs, Big-5 or the Geneogram. And while these approaches recognise the complexity of who we are, it still needs explaining to be fully understood. At least the language used is easier to understand.</p><p>So, what am I and you to do to arrive at a workable solution to these questions?</p><h3><strong>Occam’s razor</strong></h3><p><em>“All things being equal, the simplest explanation is the best one”</em></p><p>At the risk of oversimplifying life into a binary understanding, I am going to suggest a simple two-fold framework. Self and Ego. These two are not opposites. For me, the Self is nestled in the Ego.</p><figure><img alt="A circle inside a circle. The inner circle is the self and the outer circle is the ego" src="https://cdn-images-1.medium.com/max/337/1*goYW38KILu2gxT2cKB24BA.png" /><figcaption>The Self is nestled in the Ego</figcaption></figure><p>The function of the Ego is to serve and protect our psyche. Like when we put on a warm coat when it is cold outside. The Ego wraps around us purely because it is the defensive barrier between us and the outside world.</p><p>Some vilify the Ego as the enemy and give it all kinds of nefarious motivations or drivers. This approach is unhelpful. It leads to us struggling against our own Ego. Trying to gain the upper hand. Unfortunately, the more we resist something, the stronger it gets, and when we look closely, the one doing the struggle is just another part of the ego.</p><p>The ego has an evolutionary function. If it did not have such a function, it would not have existed. Better to understand the function and update the operating system than just ignore or fight it.</p><p>I would like to suggest a different approach. That of a business owner and a manager. The Self is the business owner of your life’s business. The Ego is the manager, responsible for running the business. <br> Managers need the guiding hand of the owner. When managers receive no direction from the owner, they do what they think best. So do not blame them when they try their best, and it does not result in the healthy growth of the business.</p><h3><strong>The Ego</strong></h3><p>If your Ego is a manager, and your life’s business is a shop. There are a few truths to examine through this metaphor.</p><p>A clarification about the truth is needed. “The Truth” is too big to contain. Whenever the truth is claimed, it is always just a sliver of the bigger Truth. Anybody who claims to have found the complete truth has no understanding of reality and should not be believed. All truths presented by us humans are our limited understanding based on the insights we gained by engaging with reality. These personal or lived truths are good and appropriate for the individual. When shared or presented, it must be understood as but an attempt to share the light, in the hope that it will enlighten the listeners as it has enlightened the sharer. Therefore, with this hope, share elements of the truth understood through a metaphor.</p><p><strong>#1</strong></p><p>The first truth is what Nietzsche calls “Amor Fati.” Love your fate. He sees fate as the culmination of cause and effect that brings you to the here and now — the time, culture, socioeconomic status, family and environment you were born in. In other words, do not pontificate on things that you have no control over. The love part of love your fate is also not the nihilistic acceptance of your circumstances. Love is a verb. My understanding of what love is, I learned from Scott Peck in <em>The Road Less Travelled.”</em> I paraphrase:” Love is what you do, or not do, to leave your beloved better off.” In our conversation, to love your fate is to do things that will leave your fate better off. It is not passive. <br> In terms of our Ego metaphor, this means that your shop is on the street, it is. Sure, there are other shops in malls, on high-end streets or in bad neighbourhoods. Yours is where it is. Love your fate. Teach your manager to make the “community” in which your shop is, a better place. It is a waste of energy to complain about better opportunities elsewhere. If you cannot make it on your street, you will not make it in any other location. Your shop is your shop.</p><p><strong>#2</strong></p><p>The second truth is that you are not your image. In our shop metaphor, your business has a display window. Some managers fixate on the appearance of your shop. Jung talks about our personas. The masks we present to the outside world. This is an important piece of the Ego’s work and cannot be dismissed as superficial. Personas or masks keep us safe from social harm and help us navigate expectations. Just remember, you are not your masks. I highly recommend you keep your display window clean and presentable. <br> Be warned, though, our manager sometimes falls into false advertising. Displaying items or “special offers” in our windows that are not true to the core of our business. When clients find that they have been duped into transactions, the word will start to spread that this shop is not to be trusted. Rather overdeliver than over-promise.</p><p><strong>#3</strong></p><p>This brings us to the third truth. You are not what you have or what you do. The Ego often trips us up by leading us to believe that our worth is in what we accomplish. The script goes something like this: “I have to prove that I am worthy through my actions. If the world sees my contribution, it will love me and reward me.” Linked to this is the above-mentioned truth about our image, which is the tripwire of “I am what I own.” The Ego find value in the material things we have (or lack of value because we do not have things like others). <br> In our Life’s business, we either provide services or products. Our managers (the Ego) want to prove to us that we have made the right decision to appoint them to this important position. They then stock our shop with activities or products to sell. What unfortunately happens if the owner gives no guidance is that the Ego stockpiles items that are not made by us. Without guidance, Ego buys every travelling salesperson’s trinkets and include it in the stock list. <br> What we fail to make clear as business owners of our lives is that we are a boutique shop. We offer very unique, handmade items. In this universe, there is nobody who has the unique DNS that you have. This unique code interacts with the environment you are in (your fate as Nietzsche describes it). Creating a once-off evolutionary mutation in this time and space you are in. We are a boutique shop that caters for a niche audience. In this truth lies our value.</p><p><strong>#4</strong></p><p>The fourth truth flows from this. You are not who you know or who knows you. Yes, we are relationship-driven beings. To belong is a key factor in our psychological well-being and resilience. But not all relationships are equal.<br> In our metaphor, clients walk into our shop. Some just browse, some buy, some become friends. As owners of our shop, we need to train the manager to deal appropriately with each type of client. To be civil with the browsers, carry the buyers on their hands, and go the extra mile for the friends. <br> Through thousands of years, humankind has survived by cooperation. Embedded in cooperation is a hierarchical structure. Based on the unique contribution we discussed in truth three, the hierarchy is functional and natural. In our metaphor, there are different types of shops on our street, each serving the community. Unfortunately, the Ego trips up at this point by comparing the number of feet going in and out of the other shops. It argues that to get more feet, we must become everything to everybody. Forgetting that the comparison is not the number of feet, but the service or product addressing the needs of the community. That diversity makes the community resilient. Rather than being sad that there are fewer feet in your shop, be glad that the other shop is addressing the need. Make a point to refer some of the browsers to the right shop. When their needs are met, they start trusting you, and your belonging is strengthened.</p><p>In summary. You are the owner of your life’s business, and it is your responsibility to train your manager.</p><p>Let us now focus on the owner.</p><h3><strong>The Self</strong></h3><p>I do not know your Self.</p><p>It is an immense privilege and honour when someone shares their Self with me. It is a rare and valuable gift I receive, and I reverently hold it with care. I do this because I know how difficult it is to unpack a Self. I am in my fifties, and I am still in the forge with my own Self.<br> When I say “I do not know your Self,” I acknowledge that your fate is unknown to me, and I will not pretend that I have the answer. Just a possible answer. What I share here is how I think the world works, and I invite you to take what resonates with you and park the rest. <br> That said, what I share here are universal truths (as I understand them) that I believe will help us answer the question of being present and confident in our Self.</p><p><strong>Your beauty.</strong></p><p>The first truth about you is that you are beautiful and awesome.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*N0c3njKlIBr-nfL4u3cNcA.jpeg" /><figcaption>The beauty of being part of the whole</figcaption></figure><p>We touched on this truth above, talking about your life’s business as a boutique shop. Let us now go deeper. For this, we lean into Brian Cox’s perspective.<br> The universe is mostly just a collection of mindless atoms and vast, empty spaces. On their own, those atoms don’t “mean” anything. But then, you show up. You are how the universe understands itself. Without you to look at the stars, they’d still burn, and galaxies would still collide, but nobody would be there to say, “Wow”. In a galaxy of 400 billion stars, you are a rare “data point” for the universe’s self-awareness, the only part of the cosmos capable of laughter, love, or wonder. You are, quite literally, the sensory organs of the cosmos.<br> We like to think we’re separate from the world “out there,” but that’s a misunderstanding of reality. It is a literal chemical truth: you are made of “star stuff”. Every carbon atom in your body was forged in the heart of a dying star billions of years ago. And it’s not just your materials that are special; it’s your history. You are the result of a four-billion-year-old unbroken chain of life. From the very first cell to the person reading this right now, nature never once dropped the torch of your specific lineage. In a violent, chaotic universe, your existence is a statistical miracle of survival.<br> The Second Law of Thermodynamics says the universe is moving from order to disorder, or “entropy”. Everything eventually decays. Yet, life is a temporary, highly ordered structure on that long road to disorder. You are a brief moment where the universe “bunched up” its energy into a localised pocket of immense complexity. You are a temporary biological masterpiece forged in the hearts of ancient suns<strong>.<br> </strong>We might feel tiny on this “thin blue dot” of a planet, but our value comes from that very rarity. There is a profound beauty in being a finite, fragile creature in an infinite, eternal universe. Because our time is limited, every moment of consciousness matters.</p><p>So, when you think about your Self, remember you aren’t just a bystander in the cosmos. You are a fragile, finite vessel of infinite meaning. You are the universe’s rare experiment in self-reflection. That we exist at all, on a planet that is “just right,” is a gift of pure physics and biology — one that makes you, quite simply, beautiful and awesome</p><p><strong>You belong</strong></p><p>The second truth about you is that you belong. You are part of the whole, not a standalone masterpiece. The same science that tells us we are rare also tells us that we are deeply, fundamentally “plugged in.” You aren’t just a guest in the universe; you are a feature of it</p><p>Think about a single cell in your toe. That tiny cell carries your entire genetic code — it is “you” in miniature. In the same way, you carry the fundamental laws of the universe within your own structure. You are a “cell” within the body of the cosmos, performing a very specific, vital function: conscious awareness. <br> The universe isn’t some cold container that just happens to hold you. It is the body that grows you. Your life is a “metabolic” process of the Earth’s biosphere, as natural and necessary as a heartbeat. Just as your toe cell depends on your heart for oxygen, you depend on the fusion of distant stars for the elements that keep you alive. <br> In physics, there’s really no such thing as “empty” space. Everything is made of overlapping fields. From this perspective, you aren’t an isolated object floating in a void; you are a specific “vibration<strong>”</strong> in the same field that creates the stars and the air. <br> I like to think of it this way: a wave is not a visitor to the ocean. A wave is simply something the ocean <em>does</em>. In that same sense, a human being is something the universe <em>does</em>. You are a localised expression of a universal field, a “seamless fabric” where you and the stars are made of the same thread.<br> If you ever feel like you don’t belong on this planet, just look at your own chemistry. You are quite literally geology in motion. The minerals in your bones and the iron in your blood are the exact same materials found in the mountains and the soil. You are the planet Earth expressing itself through biology. Even on a microscopic level, you are never truly alone. You are a walking ecosystem of trillions of cells and microbes, a “whole” made of “wholes”. This internal community is a perfect mirror of your external connection to the rest of the world. You belong because you are a participant in a four-billion-year conversation of life.<br> Ultimately, your “belonging” is functional. If the universe is a vast system of energy, then consciousness is the system’s way of checking in on itself. You are the nerve ending of the cosmos. You are the point where the universe becomes tactile, where it can finally feel, see, and record the experience of being. <br> The energy driving your thoughts and your heartbeat today has existed since the dawn of time. It cannot be destroyed; it only changes form. You are a brief, brilliant knot in the<strong> </strong>eternal thread of energy, a localised pulse in a single, massive conversion of light into complexity.</p><p>So, remember you don’t have to “earn” your place here. Your belonging is a physical mandate. You are the specialised tissue through which the cosmos finally opens its eyes. You aren’t just in the universe; you are of it, a vital part of the symphony that has been playing since the very beginning.</p><p><strong>You are multidimensional and ever evolving</strong></p><p>The last truth emerges out of all the previously mentioned truths. You are complex and dynamic.</p><p>Your Self is a cord weaved together from too many threats to name. There is the threat of you being beautiful, of belonging in a huge universe, of your genetic make-up, a threat of the historic time and space you were born into, threats of the societal and family culture you live in, threats of childhood, adolescence, and young adult experiences. They all weave together to make up who you are. Each plays a role, and none can be dismissed. There is a diversity in you, a rich multidimensionality. Let no one (not even yourself) box you into one thing. <br> At the same time, you are ever becoming, refreshed and staying stable. Roughly 1% of the body’s 30 trillion cells are replaced daily (about 330 billion), with gut cells renewing in days and blood cells in months, while some, like neuron or lens cells, may last a lifetime. The same is true for the Self. The above-mentioned weaving never stops.</p><p>You are also a living, walking paradox. At the same time, you are fragile and strong — a delicate arrangement of carbon that would vanish in a vacuum, yet a biological fortress that has withstood four billion years of planetary chaos. You can be kind and cruel, carrying both the advanced empathy that builds civilisations and the ancient, protective instincts of the hunter. You are the point where the rigid laws of physics meet the unpredictable freedom of the human spirit.</p><h3><strong>In the end</strong></h3><p>This is true only when the Owner of the business is present and takes the lead. When the Manager is in charge of the business, the weaving stops and starts to fray. The Self becomes a stagnant pool that stinks over time. It is our responsibility to respond to the invitations of life and become a living stream, flowing with the contours of our fate.</p><p>George Bernard Shaw’s wisdom, “<em>Life is not about finding yourself. Life is about creating yourself,</em>” is appropriate for our conversation. It invites us to engage in becoming ourselves. For me, “creating yourself” is more of a process of uncovering yourself. Throwing out the unnecessary junk the manager stuffed into the business, to expose the true handcrafted work of art that can fill your shop.</p><p>This asks us to know the core elements that make up our true self, then settle down in a lifelong journey to master the skills to use these elements in each unique (or common) circumstance our fate places us in.</p><p>The call to action is to do the hard work and step into your authentic self, train your manager in their appropriate role and function, and in the process, just be yourself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea6e35ba7a60" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Biological Tax of Status Theatre]]></title>
            <link>https://hgveitch.medium.com/the-biological-tax-of-status-theatre-c5c2e47fcc08?source=rss-10d7673e1cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5c2e47fcc08</guid>
            <category><![CDATA[goodharts-law]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[psychological-safety]]></category>
            <category><![CDATA[data-fidelity]]></category>
            <dc:creator><![CDATA[Herman Veitch]]></dc:creator>
            <pubDate>Tue, 31 Mar 2026 09:48:58 GMT</pubDate>
            <atom:updated>2026-03-31T09:48:58.439Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>How Goodhart’s Law Destroys Information Fidelity</strong></h3><p>Organisational health is often measured by a series of targets. However, a mechanical trap exists in this approach. Charles Goodhart observed in 1975 that when a measure becomes a target, it ceases to be a good measure. This is Goodhart’s Law. In a business context, this means that if a leader rewards a “Green” status report, the team will produce “Green” reports regardless of the actual state of the project. This is status theatre. It is a rational survival mechanism that carries a heavy biological tax.</p><figure><img alt="Street artist performing with a mask" src="https://cdn-images-1.medium.com/max/1024/1*9Znfblzew0w0QWi3hj2vtQ.jpeg" /></figure><p>Status theatre consumes the cognitive resources of the team. Instead of resolving systemic friction, employees spend time on the management of perception. Chris Argyris defines this as an “organisational defence” in <em>Overcoming Organisational Defences</em>. People hide the truth to stay safe. This behaviour destroys information fidelity (the quality of faithfulness or loyalty to the source). A leader receives a polished lie instead of an unvarnished signal. This makes strategic clarity impossible.</p><p>The shift to organisational observability breaks this cycle. Observability does not use data to judge individuals; it uses data to understand the system. By decouple metrics from punishment, a leader creates the psychological safety needed for truth. As Amy Edmondson notes in <em>The Fearless Organisation</em>, the highest-performing teams are those where it is safe to report failure. When the data is a mirror rather than a hammer, the biological tax of status theatre disappears.</p><p><strong>The tyranny of the target.</strong></p><p>The use of metrics as targets often leads to unintended consequences. Jerry Z. Muller describes this in <em>The Tyranny of Metrics</em> as the “performance paradox.” By focusing on a narrow set of numbers, a leader encourages the “gaming” of the system. For example, if a customer support team is measured solely on “call duration,” they may hang up on complex problems to meet their target. The metric is met, but the customer experience is destroyed.</p><p>Observability provides a countermeasure to this paradox. It looks at the whole system through a wide lens of telemetry. It does not just track the “What” (call duration) but allows the leader to see the “Why” (the complexity of the issue). Peter Senge argues in <em>The Fifth Discipline</em> that one must look at the underlying structures that generate behaviour. If the structure rewards speed over quality, the team will prioritise speed. Observability makes these structures visible.</p><p>This visibility enables side-of-desk resilience. A team identifies the friction in their own processes because they have access to the same telemetry as the leader. They do not need to hide a failure; they use the data to fix it. This is the hallmark of a human-technical system that values truth over narrative. It allows the organisation to self-correct before a small error becomes a strategic crisis.</p><p><strong>From control to curiosity.</strong></p><p>The role of the leader must move from control to curiosity. This is the essence of the “chief fidelity officer” role. Instead of the enforcement of a target, the leader asks: “The data shows an unusual pattern; what can we learn from this?” This shift in posture changes the entire information flow of the organisation. It replaces fear with investigation.</p><p>As W. Edwards Deming wrote in <em>Out of the Crisis</em>, the elimination of fear is the prerequisite for quality. When a leader uses observability to create a “glass house” of transparency, they remove the incentive for status theatre. They reclaim the human bandwidth of their team for innovation. They ensure that information fidelity remains high, even as the organisation scales.</p><p>Reflect on your last management meeting. Was the goal to find the truth or to confirm the target? Excellence is the reward for those who choose the truth.</p><p>References</p><ol><li><strong>Charles Goodhart:</strong> <em>Problems of Monetary Management</em> (1975).</li><li><strong>Amy Edmondson:</strong> <em>The Fearless Organisation</em> (Wiley, 2018, p. 56).</li><li><strong>Chris Argyris:</strong> <em>Overcoming Organisational Defences</em> (Prentice Hall, 1990, p. 82).</li><li><strong>Peter Senge:</strong> <em>The Fifth Discipline</em> (Doubleday, 2006, p. 112).</li><li><strong>W. Edwards Deming:</strong> <em>Out of the Crisis</em> (MIT Press, 1982, p. 102).</li><li><strong>Jerry Z. Muller:</strong> <em>The Tyranny of Metrics</em> (Princeton University Press, 2018, p. 18).</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5c2e47fcc08" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Physics of Observability]]></title>
            <link>https://hgveitch.medium.com/the-physics-of-observability-c725a537cfec?source=rss-10d7673e1cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c725a537cfec</guid>
            <category><![CDATA[data-fidelity]]></category>
            <category><![CDATA[telemetry]]></category>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Herman Veitch]]></dc:creator>
            <pubDate>Tue, 31 Mar 2026 09:28:57 GMT</pubDate>
            <atom:updated>2026-03-31T09:28:57.526Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>High-Cardinality and the Death of the Dashboard</strong></h3><p>Strategic clarity requires a shift from static monitoring to dynamic observability. Monitoring relies on the dashboard: a collection of predefined metrics that track known failure modes. This approach assumes a leader knows which questions to ask before a crisis occurs. Charity Majors argues in <em>Observability Engineering</em> that monitoring is only a subset of observability. In a complex human-technical system, the most significant risks are unique. They do not leave a predictable signature on a standard graph.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qmRXa1IIuhkuGb8tA7IKrA.png" /></figure><p>The mechanical limit of monitoring is low cardinality. Cardinality refers to the number of unique values in a dataset. A dashboard that tracks “average response time” is low cardinality; it hides individual outliers in a sea of averages. Observability requires high-cardinality telemetry. This allows a leader to isolate a single event, such as a specific customer’s journey or a single task in a pipeline. Baron Schwartz notes that without this granularity, the data acts as a filter rather than a mirror. High-cardinality data enables the interrogation of the “Why” behind a systemic friction point.</p><p>This technical requirement supports side-of-desk resilience. When the telemetry is granular, the team identifies the root cause of a bottleneck without a lengthy investigation. They see the raw signal. Nicole Forsgren demonstrates in <em>Accelerate</em> that high-performing organisations use this visibility to reduce lead time for changes. By moving the focus from averages to events, a leader eliminates the “blind spots” that lead to strategic debt.</p><h3><strong>Interrogating the unknown-unknowns.</strong></h3><p>A system is observable when a person can understand its internal state solely by the examination of its external outputs. This is a principle of control theory. In a business context, this means the data must be exploratory. Static dashboards fail because they only answer questions a leader has already thought to ask. Nassim Taleb describes the “Black Swan” event as a failure that exists outside the range of normal expectations. Observability is the tool for the identification of these events before they manifest as a collapse.</p><p>By use of high-fidelity telemetry, a leader asks arbitrary questions of the system. This is “exploratory data analysis.” One might ask: “Why did the sales process slow down for customers in the Western Cape during the last hour?” A low-cardinality dashboard only shows a general dip in sales. An observable system allows the leader to drill down into the specific telemetry of those transactions. This is the difference between a status report and a diagnostic tool.</p><p>This clarity reduces the need for “status theatre” meetings. The truth is available in the telemetry. As W. Edwards Deming noted in <em>The New Economics</em>, management by results is often a failure of the system. A leader should instead manage the process through the understanding of variation. Observability provides the resolution needed to see that variation in real-time.</p><h3><strong>The end of the “Green” status report.</strong></h3><p>The “Green” status report is a common artefact of low-fidelity monitoring. It creates a false sense of security while the system accumulates hidden friction. True observability removes the binary of “Pass/Fail” and replaces it with a spectrum of systemic health. This transparency is the foundation of the human-technical bridge. It aligns the technical reality of the work with the human narrative of the team.</p><p>Reclaim of organizational visibility requires an investment in the architecture of the data. It is not enough to collect more data; one must collect the right data. This means the capture of context for every event. When a leader understands the “Why,” they empower the team to execute side-of-desk fixes. This is the path to excellence in a complex world.</p><p>Reflect on your current reporting structure. Is it a mirror of the truth, or a filter of the noise? Strategic clarity begins with the courage to look at the raw signal.</p><p>References</p><ol><li><strong>Charity Majors, Liz Fong-Jones, &amp; George Miranda:</strong> <em>Observability Engineering</em> (O’Reilly, 2022, p. 14).</li><li><strong>Baron Schwartz:</strong> <em>Monitoring vs. Observability</em> (VividCortex, 2017).</li><li><strong>Nicole Forsgren:</strong> <em>Accelerate</em> (IT Revolution Press, 2018, p. 42).</li><li><strong>W. Edwards Deming:</strong> <em>The New Economics</em> (MIT Press, 2000, p. 94).</li><li><strong>Nassim Nicholas Taleb:</strong> <em>Antifragile</em> (Random House, 2012, p. 272).</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c725a537cfec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Psychological Safety as a Data Metric]]></title>
            <link>https://hgveitch.medium.com/psychological-safety-as-a-data-metric-ee1089dde3a9?source=rss-10d7673e1cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee1089dde3a9</guid>
            <category><![CDATA[leadership-clarity]]></category>
            <category><![CDATA[psychological-safety]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[information-fidelity]]></category>
            <dc:creator><![CDATA[Herman Veitch]]></dc:creator>
            <pubDate>Tue, 17 Mar 2026 10:19:04 GMT</pubDate>
            <atom:updated>2026-03-17T10:19:04.817Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Psychological Safety is the bandwidth of your organisational truth.</strong></h3><p>We often discuss culture as if it were a luxury — something to be addressed once the real business of revenue and growth is settled. However, in a high-stakes environment, culture is actually the mechanical bandwidth of your information system. If your team does not feel safe to report a failing project, a security vulnerability, or a missed milestone, your information fidelity (the quality of faithfulness or loyalty to the source) drops to zero. You can explore <a href="https://www.hbs.edu/faculty/Pages/item.aspx?num=54851">Amy Edmondson’s research at Harvard Business School</a> to see that the most successful teams aren’t the ones who make fewer mistakes; they are the ones who feel safe enough to report them.</p><figure><img alt="Futuristic image of an electronic highway" src="https://cdn-images-1.medium.com/max/1024/1*BceFgSPp4ZOLe7f38Dp7tg.jpeg" /><figcaption>Bandwidth of your organisational truth</figcaption></figure><p>When safety is low, employees engage in what Chris Argyris calls organisational defences. They polish the truth. They wait until a problem is unavoidable before mentioning it. This is not a lack of character; it is a survival instinct. If the leadership reacts to bad news with blame, the human system will naturally filter the signal to protect itself. This creates a state of systemic blindness where the leadership is the last to know that the organisation is off track. To reclaim your strategic clarity, you must stop treating safety as a “soft” value and start treating it as the prerequisite for accurate data.</p><p>By implementing a culture of radical transparency — as advocated by <a href="https://www.principles.com/">Ray Dalio in Principles</a> — you move from a state of fear-based filtering to a state of shared consciousness. This is where the technical signals, such as DORA (DevOps Research and Assessment) metrics, align with the human narrative. When it is safe to say I don’t know or I made a mistake, the organisation gains the ability to self-correct in real-time.</p><p>Does your current leadership style encourage the truth, or does it reward a polished lie?</p><h3><strong>Building Side-of-Desk Resilience through Psychological Safety.</strong></h3><p>The ultimate benefit of a high-safety environment is side-of-desk resilience. This is the ability of a team to identify and fix a systemic issue autonomously, without needing a formal directive or a marathon meeting. As <a href="https://www.mcchrystalgroup.com/capabilities/team-of-teams">General Stanley McChrystal outlines in Team of Teams</a>, this requires a level of trust where information flows horizontally as well as vertically. When a team member sees a problem, they should feel empowered to address it at the side of their desk because they know the organisation values the signal more than the hierarchy.</p><p>Without psychological safety, side-of-desk work becomes a hidden burden that leads to burnout. People fix things in secret, fearing that their initiative will be seen as a distraction from their formal KPIs. But in a high-fidelity system, these autonomous corrections are the very things that keep the organisation agile. By utilising information fidelity as a metric, you encourage your team to act as architects of the system rather than just cogs in the machine. You move away from the crisis of control and toward a state of distributed excellence.</p><p>This shift requires the leader to act as a chief fidelity officer. Your job is to ensure that the human-technical bridge is strong enough to handle the unvarnished truth. This means rewarding the reporting of red status and treating every failure as a masterclass in systemic health. It is about creating a “Circle of Safety,” as Simon Sinek describes it, where the team can focus their energy on external challenges rather than internal politics.</p><p>Are you rewarding people for fixing problems quietly, or for bringing them into the light?</p><h3><strong>Reframing the “Biological Tax” of information filtering.</strong></h3><p>Information filtering carries a heavy biological tax. When employees have to constantly manage how they are perceived, they use up cognitive resources that should be spent on innovation and problem-solving. This is the extraneous load that slows down your organisation. By contrast, a high-safety environment reduces this load, allowing for high performance. As <a href="https://www.google.com/search?q=https://www.goodreads.com/book/show/32475.High_Output_Management">Andy Grove noted in High Output Management</a>, the manager’s highest leverage activity is eliciting the truth so that the best decisions can be made.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6465b35d8df5e11a87d5eade1b7cae96/href">https://medium.com/media/6465b35d8df5e11a87d5eade1b7cae96/href</a></iframe><p>Implementing this requires a commitment to the technical health of the organisation as well. You cannot have human truth without technical observability. By using DORA (DevOps Research and Assessment) metrics to provide a neutral, data-driven view of performance, you remove the subjectivity from the conversation. The data becomes a mirror, not a hammer. This allows the team to focus on the logic of the problem rather than the politics of the person.</p><p>The future of leadership is not in the hands of the person with all the answers, but in the hands of the person who creates the safest environment for the truth to be told. By embracing psychological safety as a data metric, you are choosing to build a grounded, stable scaffold for your future. You are ensuring that your organisation is not just bigger, but better. Reclaiming your human bandwidth is the first step toward reclaiming your excellence.</p><p>Reflect on the last time someone told you something you didn’t want to hear. How did you react? That reaction set the fidelity level for the rest of your team. Excellence is the reward for those who have the courage to listen.</p><p><strong>References</strong></p><ul><li><a href="https://www.hbs.edu/faculty/Pages/item.aspx?num=54851">Amy Edmondson — The Fearless Organisation</a></li><li><a href="https://www.principles.com/">Ray Dalio — Principles: Life and Work</a></li><li><a href="https://www.google.com/search?q=https://www.mcchrystalgroup.com/library/team-of-teams/">General Stanley McChrystal — Team of Teams</a></li><li><a href="https://www.google.com/search?q=https://www.goodreads.com/book/show/32475.High_Output_Management">Andy Grove — High Output Management</a></li><li><a href="https://www.google.com/search?q=https://www.goodreads.com/book/show/1041005.Overcoming_Organizational_Defenses">Chris Argyris — Overcoming Organisational Defences</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee1089dde3a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Physics of Information Fidelity]]></title>
            <link>https://hgveitch.medium.com/the-physics-of-information-fidelity-5ddd4721be69?source=rss-10d7673e1cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ddd4721be69</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[leadership-clarity]]></category>
            <category><![CDATA[information-theory]]></category>
            <dc:creator><![CDATA[Herman Veitch]]></dc:creator>
            <pubDate>Tue, 17 Mar 2026 09:54:55 GMT</pubDate>
            <atom:updated>2026-03-17T09:54:55.481Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Information Fidelity is the most overlooked metric in organisational architecture.</strong></h3><p>We often mistake “more communication” for “better communication.” In most boardrooms, the response to a project delay is to schedule more meetings, send more emails, and create more dashboards. However, if we apply Claude Shannon’s Mathematical Theory of Communication, we see that these actions often increase the “noise” in the system rather than the “signal.” Information fidelity (the quality of faithfulness or loyalty to the source) is a measure of how much truth actually survives the journey from the engine room to the bridge. When we treat fidelity as a soft skill, we ignore the physics of organisational collapse.</p><figure><img alt="Inside a morden architectural building" src="https://cdn-images-1.medium.com/max/1024/1*MbkE5kJHeBl5p37f1pBjCg.jpeg" /><figcaption>Organisational Architecture</figcaption></figure><p>The core problem is the signal-to-noise ratio. As an organisation grows, the distance between the source of truth — the developer, the salesperson, the technician — and the decision-maker increases. Every layer of management and every manual reporting tool acts as a “channel” that introduces entropy. If your technical systems are cluttered with bad code or fragmented data silos, the “biological tax” on your team to extract the truth becomes unsustainable. You can explore <a href="https://www.edwardtufte.com/book/the-visual-display-of-quantitative-information/">Edward Tufte’s work on data-ink ratios</a> to see how visual clutter in our reporting further degrades our ability to see the signal.</p><p>This is a human-technical engineering challenge. We must move away from manual “status updates” that are prone to human error and toward automated observability. By utilising DORA (DevOps Research and Assessment) metrics — such as Deployment Frequency and Lead Time for Changes — we create a high-fidelity loop that reflects the actual state of the system in real-time. This reduces the “extraneous cognitive load” described in <a href="https://www.researchgate.net/publication/48828982_Cognitive_Load_Theory_and_the_Format_of_Instruction">John Sweller’s Cognitive Load Theory</a>, allowing your leaders to spend their energy on strategy rather than interrogation.</p><p>Does your current technical infrastructure provide a “signal” or just more “noise”?</p><h3><strong>Scaling Information Fidelity by reducing “Strategic Debt.”</strong></h3><p>When fidelity is low, the organisation accumulates strategic debt — the cost of making decisions based on outdated or distorted mental maps. This is the primary reason for the “Crisis of Control” highlighted in the <a href="https://medium.com/@hgveitch/the-greiner-growth-model-redefines-how-leaders-navigate-organisational-crises-e15d06238676">Greiner Growth Model</a>. When leaders feel they are losing the signal, their instinct is to pull back and centralise. But as <a href="https://www.goodreads.com/book/show/13629.The_Mythical_Man_Month">Frederick Brooks noted in The Mythical Man-Month</a>, adding more communication overhead to a complex project only makes it later. The solution is not more control; it is higher fidelity.</p><p>High-fidelity organisations treat information flow as a primary capital asset. They understand that a “single source of truth” is not a technical luxury but a strategic necessity. By investing in the fidelity of their data systems, they enable “Side-of-Desk Resilience,” where teams can self-correct because they are looking at the same unvarnished reality as the CEO. This alignment minimises the “Information Delays” that <a href="https://www.goodreads.com/book/show/3828902-thinking-in-systems?from_search=true&amp;from_srp=true&amp;qid=zoGqwuVEDW&amp;rank=1">Donella Meadows identified</a> as the most frequent cause of systemic instability.</p><p>Utilising information fidelity as a diagnostic tool allows you to identify where your “Human-Technical Bridge” is failing. It forces a hard-headed look at whether your dashboards are “Status Theatre” or actual “Signals.” To lead effectively in a volatile market, you must be a “Chief Fidelity Officer,” ensuring that the truth of the customer’s experience and the engine room’s capacity is the only currency that matters.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/355e0256da4e25fc60bcefce6bdc680f/href">https://medium.com/media/355e0256da4e25fc60bcefce6bdc680f/href</a></iframe><p>Is your “Definition of Done” for a project including the establishment of a high-fidelity feedback loop?</p><h3><strong>The future of leadership is the engineering of fidelity.</strong></h3><p>True organisational resilience is built on the quiet foundation of accurate information. By embracing the physics of information fidelity, you move your organisation toward a state of “Antifragility.” You stop reacting to the symptoms of noise — the “surprises” and the “emergencies” — and start managing the health of the signal. This shift ensures that your organisation remains a stable scaffold for your people to do their best work, even as you scale through the Greiner revolutions.</p><p>As a leader, your role is to act as the “Protector of the Signal.” You must have the courage to simplify your systems and the discipline to demand unvarnished data. By modelling this “Human-Technical” synthesis, you teach your team that clarity is the ultimate form of respect. Information fidelity ensures that the “truth” of your strategy is clearly reflected in the “logic” of your machine. Reclaiming your signal is the first step toward reclaiming your future.</p><p>Reflect on the last decision you made. Was it based on a “High-Fidelity” signal or a “Polished” report? Resilience is built in the deliberate act of clearing the path for the truth. Excellence is the reward for those who choose to listen to the signal within the noise.</p><p><strong>References</strong></p><ul><li><a href="https://people.math.harvard.edu/~ctm/home/text/others/shannon/entropy/entropy.pdf">Claude Shannon — A Mathematical Theory of Communication</a></li><li><a href="https://www.google.com/search?q=https://www.edwardtufte.com/tufte/books_vdqi">Edward Tufte — The Visual Display of Quantitative Information</a></li><li><a href="https://itrevolution.com/product/accelerate/">Nicole Forsgren, et al. — Accelerate: The Science of Lean Software and DevOps</a></li><li><a href="https://www.goodreads.com/book/show/3828902-thinking-in-systems?from_search=true&amp;from_srp=true&amp;qid=zoGqwuVEDW&amp;rank=1">Donella Meadows — Thinking in Systems</a></li><li><a href="https://www.researchgate.net/publication/48828982_Cognitive_Load_Theory_and_the_Format_of_Instruction">John Sweller — Cognitive Load Theory</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ddd4721be69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Managing the Risks of Smart Growth prevents organisational fragility.]]></title>
            <link>https://hgveitch.medium.com/managing-the-risks-of-smart-growth-prevents-organisational-fragility-9477ba341c5d?source=rss-10d7673e1cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9477ba341c5d</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[scalability]]></category>
            <category><![CDATA[smart-growth]]></category>
            <category><![CDATA[leadership-focus]]></category>
            <dc:creator><![CDATA[Herman Veitch]]></dc:creator>
            <pubDate>Thu, 12 Mar 2026 08:56:02 GMT</pubDate>
            <atom:updated>2026-03-12T08:56:02.279Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Managing the Risks of Smart Growth</strong> is the necessary counterweight to the “Growth at all costs” dogma that dominates modern business. Most leaders treat growth as an unalloyed good — a sign of health and vitality. However, growth is also a high-stress event that can shatter the “human-technical” foundation of a company if not handled with care. You can explore <a href="https://www.goodreads.com/book/show/8304431-smart-growth?from_search=true&amp;from_srp=true&amp;qid=v10NTWR6hu&amp;rank=9">Edward Hess’s foundational research at the Darden School of Business</a> and <a href="https://www.goodreads.com/book/show/13530973-antifragile?ref=nav_sb_ss_1_11">Nassim Taleb’s concept of Antifragility</a> to see that as systems get larger, they often become more brittle and prone to catastrophic failure. When we grow “dumb,” we increase our technical debt and strategic complexity faster than we increase our revenue.</p><p>The core philosophy of <strong>Managing the Risks of Smart Growth</strong> is that growth should be a <em>consequence</em> of excellence, not a <em>strategy</em> for it. Rapid expansion often creates “systemic noise” that drowns out the “information fidelity” needed to make good decisions. When you add people, processes, and technology at a breakneck pace, you risk the “Great Training Robbery,” where your culture is diluted because you cannot integrate new hires as fast as you recruit them. This leads to operational bloat, where the organisation becomes a “giant with feet of clay.”</p><p>This is a <strong>human-technical</strong> challenge of the highest order. It requires us to view growth not as a scoreboard, but as a risk to be mitigated. By applying the principles of <strong>Managing the Risks of Smart Growth</strong>, we can install “seismic dampers” — like deliberate pauses for refactoring and cultural alignment — that allow the organisation to expand without losing its structural integrity. We must shift our focus from “How fast can we grow?” to “How well can we scale?”</p><p>Is your current growth trajectory building a more resilient system, or just a bigger one?</p><figure><img alt="Open Laptop with growth chart displayed" src="https://cdn-images-1.medium.com/max/1024/1*vrK_h6Fa7BqRiSFIDt4FbA.jpeg" /><figcaption><strong>Managing the Risks of Smart Growth</strong></figcaption></figure><h3><strong>Managing the Risks of Smart Growth requires a “biological” understanding of scale.</strong></h3><p>Traditional management views an organisation as a machine where you can simply add more “parts” to get more “output.” <strong>Managing the Risks of Smart Growth</strong> challenges this by applying the “Dunbar Number” and “Brooks’ Law” (adding manpower to a late software project makes it later) to the corporate environment. These concepts prove that as a network grows, the number of communication channels grows exponentially, not linearly. This creates a “complexity tax” that can eventually stall the entire system.</p><p>For example, when a team grows beyond 150 people (the Dunbar Number), the “human” bonds that maintain trust and alignment begin to fray. You can no longer rely on informal relationships; you must implement formal systems. If these systems are too rigid, you trigger a “Crisis of Red Tape” (as seen in the Greiner Model). <strong>Managing the Risks of Smart Growth</strong> involves building “Modular Architectures” — both in your software and your team structures — that allow units to remain small and high-fidelity even as the overall organisation expands.</p><p>Utilising <strong>Managing the Risks of Smart Growth</strong> means acknowledging the “Biological Tax” of change. Every new process added is a new cognitive load for your employees. If you don’t retire old processes as you add new ones, you reach a state of “process saturation” where innovation dies. Smart growth requires a “one-in, one-out” policy for complexity, ensuring that the organisation remains lean and “antifragile” regardless of its size.</p><p>Which of your current “legacy processes” is acting as an anchor on your growth?</p><h3><strong>The “Human-Technical” synthesis for Managing the Risks of Smart Growth.</strong></h3><p>The most successful leaders don’t just scale their revenue; they scale their “Information Fidelity.” <strong>Managing the Risks of Smart Growth</strong> is about ensuring that the “truth” of what is happening on the front lines isn’t lost as it travels up the hierarchy. This requires a technical infrastructure that provides real-time, unvarnished data and a human culture that values “Psychological Safety” — the freedom to report bad news without fear of retribution.</p><p>Without this synthesis, you enter a state of “Strategic Debt.” You make decisions based on outdated mental maps because the “noise” of the growing organisation is too loud to hear the “signal” of the market. <strong>Managing the Risks of Smart Growth</strong> involves using tools like “Post-Mortems” and “Continuous Simulation” to ensure that your mental maps are updated at the same speed as your headcount. It is the practice of maintaining “Optimal Arousal” in the team — keeping them challenged enough to grow, but not so stressed that they break.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d6ffbf123325af83315ce04302441a39/href">https://medium.com/media/d6ffbf123325af83315ce04302441a39/href</a></iframe><p>Implementing <strong>Managing the Risks of Smart Growth</strong> requires the courage to say “no” to opportunities that would overstretch your “Human Systems Architecture.” It is the discipline of “Sequential Growth” — mastering one level of complexity before moving to the next. This ensures that you aren’t just building a bigger company, but a better one.</p><p>Are you rewarding your managers for the “Size of their Empire” or the “Health of their System”?</p><h3><strong>Using Smart Growth to build a grounded, stable scaffold for the future.</strong></h3><p>The ultimate goal of <strong>Managing the Risks of Smart Growth</strong> is to create an organisation that can endure for decades, not just a few “hyperscale” years. By prioritising technical health, human focus, and information fidelity, you are building a grounded, stable scaffold. You are moving away from the “loud” franticness of unmanaged expansion and toward the “quiet” confidence of structural integrity.</p><p>As a leader, your role is to act as the “Governor” of the system — ensuring that the speed of growth never exceeds the speed of learning. By modelling this “Strategic Patience,” you teach your team that excellence is a non-negotiable standard. <strong>Managing the Risks of Smart Growth</strong> is the hallmark of a “Human Systems Architect” who understands that the strongest buildings aren’t the ones that grow the fastest, but the ones with the deepest foundations.</p><p>Reflect on your current expansion plans. If you were forced to grow at 50% of your current planned speed, what “quality” improvements would you finally have time to make? Resilience is built in the deliberate act of choosing fidelity over volume. Excellence is the reward for those who have the wisdom to grow smart.</p><p><strong>References</strong></p><ul><li><a href="https://www.goodreads.com/book/show/8304431-smart-growth?from_search=true&amp;from_srp=true&amp;qid=v10NTWR6hu&amp;rank=9">Edward Hess — Smart Growth: Building an Enduring Business by Managing the Risks of Growth</a></li><li><a href="https://www.goodreads.com/book/show/13530973-antifragile?ref=nav_sb_ss_1_11">Nassim Nicholas Taleb — Antifragile: Things That Gain from Disorder</a></li><li><a href="https://www.goodreads.com/book/show/3828902-thinking-in-systems?from_search=true&amp;from_srp=true&amp;qid=zoGqwuVEDW&amp;rank=1">Donella Meadows — Thinking in Systems: A Primer</a></li><li><a href="https://www.hbs.edu/faculty/Pages/item.aspx?num=54851">Amy Edmondson — The Fearless Organisation</a></li><li><a href="https://www.goodreads.com/book/show/56883977-friends?ref=nav_sb_ss_2_12">Robin Dunbar — Friends: Understanding the Power of Our Most Important Relationships</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9477ba341c5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Greiner Growth Model redefines how leaders navigate organisational crises.]]></title>
            <link>https://hgveitch.medium.com/the-greiner-growth-model-redefines-how-leaders-navigate-organisational-crises-e15d06238676?source=rss-10d7673e1cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/e15d06238676</guid>
            <category><![CDATA[greiner-model]]></category>
            <category><![CDATA[leadership-crisis]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[scalability]]></category>
            <dc:creator><![CDATA[Herman Veitch]]></dc:creator>
            <pubDate>Thu, 12 Mar 2026 08:41:00 GMT</pubDate>
            <atom:updated>2026-03-12T08:41:00.864Z</atom:updated>
            <content:encoded><![CDATA[<p>The Greiner Growth Model (explained below) is the essential diagnostic tool for any leader who feels like their organisation is constantly “hitting a wall.” We are often taught that growth is a smooth, linear progression — a ladder where each rung represents more revenue and more people. However, reality is far more turbulent. You can explore <a href="https://hbr.org/1998/05/evolution-and-revolution-as-organizations-grow">Larry Greiner’s seminal HBR research</a> and the updated <a href="https://www.adizes.com/organizational-lifecycle">Ichak Adizes’ work on Corporate Lifecycles</a> to see that growth is actually a series of “evolutionary” periods punctuated by “revolutionary” crises. When we mistake a necessary revolution for a failure of leadership, we inadvertently freeze the system.</p><h3><strong>The Anatomy of the Model</strong></h3><p>To visualise this, imagine a graph with the vertical axis showing organisation size and the horizontal axis showing age. The path of growth isn’t a straight line; it is a series of long, upward “Evolutionary” waves. At the end of each wave, the line jaggedly shifts — this is the “Revolutionary” crisis. Each stage is defined by a specific management focus, and each crisis is the result of that focus reaching its limit.</p><p>The brilliance of The Greiner Growth Model lies in its predictability. It suggests that the very management style that brought you success in one phase will become the primary “anchor” that causes a crisis in the next. For example, the creative, “all-hands-on-deck” energy of a startup eventually leads to a Crisis of Leadership, where the founders can no longer manage every detail. To move forward, the organisation must evolve into a more structured, directed phase. If the leadership refuses to update their “mental map” and cede control, the company enters a state of systemic stagnation.</p><p>This cycle of evolution and revolution is a human-technical necessity. It requires us to build organisational structures that are not just “scalable,” but “adaptable.” By using the Greiner Growth Model, leaders can stop reacting to crises with panic and start greeting them as “growth signals.” This shift in perspective reduces the “biological tax” of anxiety on the team, allowing them to focus on the structural changes needed to unlock the next level of performance.</p><p>At which stage of the Greiner Model is your organisation currently “stuck”?</p><h3><strong>The Greiner Growth Model identifies the hidden “revolutions” required for scale.</strong></h3><p>Most leaders try to avoid internal conflict at all costs. However, the Greiner Growth Model proves that these conflicts — or “revolutions” — are the only way to shed the skin of an outdated operational model. Each of the five phases ends with a specific crisis that cannot be solved by “working harder.” It can only be solved by changing the underlying human-technical architecture of the company.</p><ul><li>Phase 1: Creativity ends in a Crisis of Leadership. (Need for professional management).</li><li>Phase 2: Direction ends in a Crisis of Autonomy. (Need for delegation).</li><li>Phase 3: Delegation ends in a Crisis of Control. (Need for coordination).</li><li>Phase 4: Coordination ends in a Crisis of Red Tape. (Need for collaboration).</li><li>Phase 5: Collaboration ends in a Crisis of Internal Growth/Saturation. (Need for external alliances).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OC28KdwxvkNnGPgb1u2Fxg.png" /><figcaption>Greiner Growth Model as Phases</figcaption></figure><p>For instance, Phase 3 (Delegation) often leads to a Crisis of Control. The top-level leaders feel they are losing touch with the front lines, and their instinct is to “pull back” and centralise power. But the Greiner model teaches us that the solution isn’t more control; it’s better Coordination (Phase 4). By understanding this, you can bypass the “amygdala hijack” that occurs when a leader feels their authority is slipping and instead focus on building the technical systems (like better information fidelity) that allow for distributed excellence.</p><p>Utilizing The Greiner Growth Model allows you to act as an “organisational architect” rather than a “firefighter.” It provides the clarity needed to install “seismic dampers” before the next tremor hits. By anticipating the specific crisis of your current phase, you can prepare your team’s mental maps for the shift. This creates a culture of “predictive resilience,” where the team expects change and views it as a sign of successful expansion.</p><p>How can you reframe your current “operational friction” as a necessary revolution for your next stage of growth?</p><h3><strong>Navigating the Greiner Growth Model by managing the “biological tax” of change.</strong></h3><p>Every time an organisation shifts from one Greiner phase to the next, the “human material” of the company pays a biological tax. The transition from “Creativity” to “Direction,” for example, requires people who were hired for their “rebel” spirit to suddenly follow “standard operating procedures.” This creates a spike in cortisol and a sense of loss. The Greiner Growth Model is therefore not just a business chart; it is a map of human psychological endurance.</p><p>If we don’t acknowledge this tax, we suffer from “systemic freeze.” The organisation becomes “stuck” between phases — too big to be a startup, but too chaotic to be an enterprise. To bridge this gap, we must integrate “Active Rest” and “Mental Rehearsal” into our scaling strategy. We must give our people the cognitive space to mourn the “old way” so they can embrace the “new way.” This is the human-technical solution for maintaining performance excellence during a revolution.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/03bcb5572ca3e001bd3c72f2202c79ee/href">https://medium.com/media/03bcb5572ca3e001bd3c72f2202c79ee/href</a></iframe><p>Implementing the Greiner Growth Model requires a commitment to “Double-Loop Learning.” You must constantly audit whether your current “Success Metrics” are actually the very things that will cause the next crisis. By rewarding the team for identifying “Phase Friction,” you lower the psychological cost of the revolution. You transform the organisation into a “Learning Laboratory” where every crisis is treated as a masterclass in systemic evolution.</p><p>Is your current “Leadership Style” appropriate for the Greiner phase you are entering, or the one you are leaving behind?</p><h3><strong>Using the Greiner Growth Model to build an antifragile organisation.</strong></h3><p>The ultimate goal of using The Greiner Growth Model is to reach a state of “Collaboration” where the organisation is both highly structured and highly flexible. This is the “Antifragile” state — where the system actually improves when it is put under stress. This is only possible when the human-technical bridge is strong. Your technical systems (data, KPIs, software) must provide enough “Information Fidelity” to allow your human teams to make high-fidelity decisions without needing constant top-down direction.</p><p>By adopting the Greiner Growth Model, you are choosing to lead with intention. You are moving away from the “loud” drama of unexpected crisis and toward the “quiet” confidence of intentional evolution. You are building a grounded, stable scaffold that allows your people to do their best work, even as the ground beneath them shifts. This is the definition of excellence: the ability to scale without losing your soul.</p><p>Reflect on the most recent “internal conflict” in your team. Was it a sign of failure, or was it the first signal of a Greiner Revolution? The path to a resilient future is built one intentional phase shift at a time. Resilience is not about avoiding the crisis; it’s about having the map to navigate through it. Reclaiming your perspective on growth is the first step toward reclaiming your future success.</p><p>References</p><ul><li><a href="https://hbr.org/1998/05/evolution-and-revolution-as-organizations-grow">Larry Greiner — Evolution and Revolution as Organizations Grow (HBR)</a></li><li><a href="https://www.adizes.com/organizational-lifecycle">Ichak Adizes — Corporate Lifecycles: How Organizations Grow and Die</a></li><li><a href="https://www.goodreads.com/book/show/18085530">Geoffrey Moore — Crossing the Chasm</a></li><li><a href="https://www.goodreads.com/book/show/19723223-antifragile">Nassim Nicholas Taleb — Antifragile: Things That Gain from Disorder</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e15d06238676" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Stripe Report on the $3 Trillion Impact of Bad Code reveals a global economic siphon.]]></title>
            <link>https://hgveitch.medium.com/the-stripe-report-on-the-3-trillion-impact-of-bad-code-reveals-a-global-economic-siphon-217b1d826cab?source=rss-10d7673e1cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/217b1d826cab</guid>
            <category><![CDATA[developer-experience]]></category>
            <category><![CDATA[stripe-report]]></category>
            <category><![CDATA[technical-debt]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Herman Veitch]]></dc:creator>
            <pubDate>Tue, 10 Mar 2026 09:06:46 GMT</pubDate>
            <atom:updated>2026-03-10T09:06:46.994Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong> serves as a wake-up call for every leader who views software development as a commodity rather than a core strategic engine. We often treat “bad code” as a localised technical nuisance — a series of bugs that need squashing or a slow interface that requires optimisation. However, when we aggregate these “minor” frictions across the global economy, we find a massive loss of productivity. You can explore the <a href="https://stripe.com/files/reports/the-developer-coefficient.pdf">primary Stripe Report: The Developer Coefficient</a> and compare it with <a href="https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/developer-velocity-how-software-excellence-fuels-business-performance">McKinsey’s Developer Velocity Index</a> to see how high-performing companies treat code as their most valuable asset. When we ignore the systemic impact of low-quality code, we are essentially allowing a $3 trillion leak in our collective balance sheet.</p><p>The frustration most executives feel regarding “slow” development cycles is often a direct result of the findings in <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong>. The report highlights that the average developer spends roughly 17 hours a week — nearly 42% of their time — dealing with “bad code” and technical debt. This is not just a waste of talent; it is a “biological tax” on the creative energy of your most expensive employees. If your team is spending half their time fixing what they’ve already built, they have zero capacity to innovate for the future. We must shift our focus from “hiring more developers” to “increasing the coefficient” of the ones we already have.</p><figure><img alt="Dubble pipeline through green forest" src="https://cdn-images-1.medium.com/max/1024/1*hoMVp1NrjDXZ4T7nHQxhAg.jpeg" /></figure><p>This economic siphon is a <strong>human-technical</strong> crisis that requires a structural response. It is not enough to simply “work harder” or “sprint faster.” In fact, pushing for higher velocity without addressing the underlying quality issues only exacerbates the problem. By ignoring the data in <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong>, organisations remain trapped in a cycle of diminishing returns. We must redefine our metrics of success to prioritise technical fidelity and developer focus over raw output.</p><p>What would your organisation achieve if your developers regained 17 hours of innovation time every single week?</p><p><strong>The Stripe Report on the $3 Trillion Impact of Bad Code challenges the “Velocity at all costs” mindset.</strong></p><p>Traditional business metrics often prioritise the speed of feature delivery over the health of the system. <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong> proves that this “Velocity at all costs” mindset is economically illiterate. When we push for short-term speed, we accumulate high-interest debt that eventually slows the entire organisation to a crawl. Gartner research supports this, indicating that technical debt now consumes up to 40% of the average IT budget. This is the technical equivalent of a company spending 40% of its revenue just to pay the interest on its credit cards.</p><p>To navigate this, we must adopt the “Developer Coefficient” mentioned in the report — a measure of how much a company’s technical environment empowers or inhibits its developers. <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong> suggests that the “Developer Coefficient” is a more accurate predictor of long-term success than headcount. High-coefficient companies provide their teams with clean abstractions, modern tools, and the “psychological safety” to address technical debt early. Low-coefficient companies, by contrast, treat developers as “cogs in a machine,” leading to the very frictions that fuel the $3 trillion global loss.</p><p>Utilizing <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong> as a diagnostic tool allows us to identify where our “human-technical” bridge is failing. It forces us to ask whether our technical architecture is a scaffold for growth or a cage of complexity. By prioritising “Developer Experience” (DX), we are not just being “nice” to our engineers; we are making a hard-headed business decision to stop the $3 trillion bleed. We are choosing to invest in the fidelity of our systems to ensure the longevity of our strategy.</p><p>Does your current “Definition of Done” include paying down the technical debt created during the sprint?</p><p><strong>Overcoming the “Attention Debt” highlighted in The Stripe Report on the $3 Trillion Impact of Bad Code.</strong></p><p>The most profound insight within <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong> is that the cost of bad code is primarily a cost of human attention. Every time a developer has to navigate a convoluted codebase, their “cognitive load” spikes. This “Attention Debt” is the silent killer of organisational excellence. According to research on “Flow State” and “Deep Work,” it takes an average of 23 minutes for a knowledge worker to regain focus after a distraction. “Bad code” is a constant source of these micro-distractions, effectively preventing your team from ever reaching peak performance.</p><p>This is where the <strong>human-technical</strong> synthesis becomes critical. We must treat the codebase as a “Cognitive Environment.” Just as an architect designs a physical office to facilitate collaboration and focus, a software architect must design a codebase to facilitate clear thinking. <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong> makes it clear that we can no longer afford to treat code as a secondary concern. We must actively manage the “Information Fidelity” of our systems to ensure that the “truth” of the business is clearly reflected in the logic of the machine.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/78fd441c5d533497c6032032862814c6/href">https://medium.com/media/78fd441c5d533497c6032032862814c6/href</a></iframe><p>Implementing the lessons of <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong> requires a shift from “Heroic Leadership” to “Systemic Leadership.” Instead of rewarding the developer who stays up all night to fix a crisis, we should reward the developer who built the system so clearly that the crisis never occurred. By rewarding “Maintenance and Rehearsal,” we lower the cognitive load on the entire team, allowing them to remain on the “Optimal Arousal” section of the Yerkes-Dodson curve.</p><p>How can you pivot your “Recognition Program” to celebrate the prevention of complexity rather than the resolution of a crisis?</p><p><strong>A human-technical framework to reclaim your share of the $3 trillion loss.</strong></p><p>To reclaim the productivity lost to bad code, we must integrate the findings of <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong> into our capital allocation strategy. We must stop viewing “refactoring” as a technical luxury and start seeing it as a mandatory “maintenance of capital.” A successful <strong>human-technical</strong> framework involves three specific pillars:</p><ol><li><strong>Observability (Technical):</strong> Implementing DORA metrics (Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Restore Service) to measure the actual health of the development pipeline.</li><li><strong>Cognitive Load Management (Human):</strong> Structuring teams around “Bounded Contexts” to ensure that no single developer is responsible for more complexity than a human brain can reasonably hold.</li><li><strong>The 20% Rule (Systemic):</strong> Committing 20% of every development cycle to paying down the debt identified in <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong>.</li></ol><p>By adopting these pillars, you are building a “Seismic Damper” for your organisational architecture. You are creating a buffer that absorbs the “kinetic energy” of market shifts without shattering your technical foundation. This is the path to “Antifragility” — creating a system that doesn’t just survive the $3 trillion crisis but thrives by being more efficient than its competitors. <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong> is not a death sentence; it is a roadmap for those willing to lead with fidelity.</p><p>Are you measuring “Velocity” (how fast you move) or “Velocity of Value” (how fast you solve the customer’s problem)?</p><p><strong>The Stripe Report on the $3 Trillion Impact of Bad Code ensures long-term stability and excellence.</strong></p><p>True organisational resilience is found in the alignment of your technical reality with your strategic intent. By taking the data in <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong> seriously, you are choosing to lead with intelligence and care. You are moving away from the “loud” noise of wasteful effort and toward the “quiet” confidence of a healthy system. This shift ensures that your organisation remains a stable scaffold for your people to do their best work.</p><p>As a leader, your role is to act as the primary “Protector of the Coefficient.” You must have the courage to say “no” to a feature today so that you can say “yes” to ten features tomorrow. By modelling this strategic patience, you teach your team that quality is not a compromise — it is the very engine of speed. <strong>The Stripe Report on the $3 Trillion Impact of Bad Code</strong> reminds us that the cost of doing it wrong is far higher than the cost of doing it right the first time.</p><p>Reflect on your current development backlog. What percentage of it is focused on reclaiming the “17 hours” lost to bad code? The path to a $3 trillion opportunity begins with a single, clear-headed decision to prioritise technical health. Reclaiming your team’s focus is the first step toward reclaiming your future success. Resilience is built in the deliberate act of clearing the path for excellence.</p><p><strong>References</strong></p><ul><li><a href="https://stripe.com/files/reports/the-developer-coefficient.pdf">Stripe — The Developer Coefficient Report: The $3 Trillion Impact of Bad Code</a></li><li><a href="https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/developer-velocity-how-software-excellence-fuels-business-performance">McKinsey — Developer Velocity: How software excellence fuels business performance</a></li><li><a href="https://itrevolution.com/book/accelerate/">Nicole Forsgren, Jez Humble, and Gene Kim — Accelerate: The Science of Lean Software and DevOps</a></li><li><a href="https://www.gartner.com/en/information-technology/glossary/technical-debt">Gartner — Managing Technical Debt (2023)</a></li><li><a href="https://itrevolution.com/book/the-phoenix-project/">Gene Kim — The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=217b1d826cab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Original Technical Debt Metaphor redefines how we value systemic agility.]]></title>
            <link>https://hgveitch.medium.com/the-original-technical-debt-metaphor-redefines-how-we-value-systemic-agility-c53ffa300b8e?source=rss-10d7673e1cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/c53ffa300b8e</guid>
            <category><![CDATA[technical-debt]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[leadership-focus]]></category>
            <dc:creator><![CDATA[Herman Veitch]]></dc:creator>
            <pubDate>Tue, 10 Mar 2026 09:04:13 GMT</pubDate>
            <atom:updated>2026-03-10T09:04:13.609Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>The Original Technical Debt Metaphor</strong> is one of the most misunderstood concepts in modern management. Most leaders view “technical debt” as a synonym for sloppy work, a lack of professional discipline, or “bugs” that need to be fixed. However, the original intent of the metaphor was far more strategic and nuanced. You can watch <a href="https://www.youtube.com/watch?v=pqeJFYwnkjE">Ward Cunningham’s original explanation</a> of the concept and read <a href="https://martinfowler.com/bliki/TechnicalDebtQuadrant.html">Martin Fowler’s exploration of the Debt Quadrant</a> to understand how this bridge between finance and engineering was first built. When we mislabel debt as “bad code,” we miss the opportunity to manage it as a strategic asset.</p><p>The core tension of the metaphor is not about the quality of the code itself, but the relationship between the code and our understanding of the problem. When we first ship a product, we are inevitably working with an incomplete “mental map” of the market. <strong>The Original Technical Debt Metaphor</strong> suggests that we “borrow” time by shipping code that reflects our current, limited understanding, with the intention of “paying it back” later by refactoring the code as our understanding matures. If we fail to pay back this debt, the interest — in the form of increased complexity and reduced speed — eventually bankrupts our ability to innovate.</p><p>This gap between knowledge and implementation is the primary source of organisational friction. In a high-stakes environment, the pressure to deliver often forces teams to accumulate debt without a clear “repayment plan.” This leads to a state of technical insolvency where the team spends 100% of their energy just keeping the lights on, leaving zero room for growth. We must shift our perspective from seeing debt as a “failure” to seeing it as a “loan” that must be managed with extreme financial and technical rigour.</p><p>How can you identify the difference between a “strategic loan” and “reckless spending” in your current codebase?</p><p><strong>The Original Technical Debt Metaphor is a debt of understanding, not just a debt of code.</strong></p><figure><img alt="Person writing code on PC" src="https://cdn-images-1.medium.com/max/1024/1*d1aGcWWIAWfekBFDZ6SSvg.jpeg" /></figure><p>To understand this shift, we must address the <strong>semantic drift</strong> that has occurred over the last thirty years. While “Technical Debt” is now often used as a catch-all excuse for any system that is slow or “buggy,” the <strong>Original Technical Debt Metaphor</strong> was never intended to describe a lack of skill. Instead, it was designed as a strategic bridge — a way to explain to non-technical stakeholders that shipping code is a form of “borrowing” against our future understanding of the problem.</p><p>Ward Cunningham famously stated that the debt is not the code itself, but the lack of understanding that the code reflects. <strong>The Original Technical Debt Metaphor</strong> is fundamentally about the delta between what we knew <em>then</em> and what we know <em>now</em>. As the business learns more about its customers and the technical challenges it faces, the old code becomes “debt” because it no longer aligns with the new reality. If we don’t update the code to reflect our new understanding, we are effectively operating with an outdated mental map.</p><p>This creates a <strong>human-technical</strong> conflict. The technical system (the code) stays static, while the human understanding (the strategy) evolves. The longer this gap persists, the more “interest” the organisation pays. This interest isn’t just a slower release cycle; it is a biological tax on the developers who must navigate the cognitive dissonance of working on a system that no longer makes sense. This leads to burnout and a loss of “information fidelity,” as the “truth” of how the system works is lost in a sea of workarounds and patches.</p><p>What parts of your current system are “lying” about the way your business actually works today?</p><p><strong>Managing the Original Technical Debt Metaphor through the lens of human attention.</strong></p><p>The most expensive “interest” paid on technical debt is the loss of human focus. <strong>The Original Technical Debt Metaphor</strong> reveals that “bad code” is actually an attention-leaking machine. When a developer encounters a piece of “debt-ridden” code, their cognitive load spikes as they try to untangle the original intent from the current mess. This consumes the same mental energy required for innovation, empathy, and high-level decision-making. By allowing debt to accumulate, we are effectively taxing the most valuable asset in our company: the focused attention of our people.</p><p>This is where the <strong>human-technical</strong> bridge becomes essential. We must treat technical debt as a “Psychological Safety” issue. If developers are afraid to report the debt they encounter — or if they are punished for taking the time to pay it back — they will begin to hide the “broken windows” of the codebase. This leads to a culture of silence and systemic fragility. By making the debt “visible” through transparent reporting and deliberate “refactoring sprints,” you empower your team to maintain the health of the system.</p><p><strong>Comparing Modern Usage vs. The Original Metaphor</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/aa58a3417f612fae57beb39dd4a31e57/href">https://medium.com/media/aa58a3417f612fae57beb39dd4a31e57/href</a></iframe><p>Implementing a “Prudent Debt” strategy requires a disciplined commitment to the “Rule of Three”: the first time you do something, you just get it done. The second time, you wince at the duplication. The third time, you refactor. This ensures that you are only paying back the debt that is actually costing you interest. It transforms <strong>The Original Technical Debt Metaphor</strong> from a source of shame into a tool for professional excellence and organisational resilience.</p><p>How can you create a “Debt Amnesty” day to allow your team to reveal the hidden complexity in your systems?</p><p><strong>A human-technical framework for reclaiming systemic agility.</strong></p><p>To successfully manage <strong>The Original Technical Debt Metaphor</strong>, we must integrate technical health into our primary business metrics. We cannot treat “technical debt” as a separate category that is managed only when there is “free time.” In a high-growth environment, there is never any free time. Therefore, the payment of debt must be built into the “definition of done” for every task. This is the <strong>human-technical</strong> solution for ensuring that the organisation remains “antifragile” and capable of sustained performance.</p><p>One practical way to do this is to dedicate 20% of every development cycle to “maintenance and repayment.” This is not a “nice-to-have”; it is a “seismic damper” for your technical architecture. It prevents the buildup of the $3 trillion economic anchor described in the recent Stripe report. By making this investment, you are ensuring that your team has the cognitive space to stay curious and the technical flexibility to stay fast. You are building a company that is not just shipping code, but shipping understanding.</p><p>By adopting this framework, you are choosing to lead with fidelity. You are acknowledging that the “technical” is always a reflection of the “human.” When you fix the code, you are actually fixing the team’s ability to think clearly. <strong>The Original Technical Debt Metaphor</strong> is ultimately a call to stay humble and stay hungry for learning. It is a reminder that our best work is always a “work in progress,” and that true excellence is found in the continuous evolution of our mental maps and our machine code.</p><p>Are your current KPIs incentivising your team to take on “reckless debt” to meet artificial deadlines?</p><p><strong>The Original Technical Debt Metaphor ensures long-term stability and excellence.</strong></p><p>True organisational resilience is found in the ability to move without the weight of the past. By embracing <strong>The Original Technical Debt Metaphor</strong>, you are choosing to build a company that can endure. You are moving away from the frantic firefighting of “bug fixes” and toward the quiet confidence of structural integrity. This shift fosters a culture of excellence where people feel proud of the systems they build and the service they provide.</p><p>As a leader, your role is to act as the primary “Debt Manager” for your organisation. You must have the courage to slow down and pay back the “interest” when the signs of systemic fatigue appear. By modelling this discipline, you teach your entire team how to manage their own energy and focus. This creates a self-healing system that can navigate the volatility of the modern market with ease and grace. Reclaiming your technical health is the first step toward reclaiming your future success.</p><p>Reflect on the one area of your codebase that causes the most “fear” for your team. What would happen if you treated that fear as a signal of high-interest debt and scheduled a “repayment sprint” today? Resilience is built in the deliberate act of clearing the path for the future. Excellence is not the absence of debt, but the wisdom to manage it well.</p><p><strong>References</strong></p><ul><li><a href="https://www.youtube.com/watch?v=pqeJFYwnkjE">Ward Cunningham — The Debt Metaphor (Video)</a></li><li><a href="https://martinfowler.com/bliki/TechnicalDebtQuadrant.html">Martin Fowler — The Technical Debt Quadrant</a></li><li><a href="https://www.goodreads.com/book/show/4845.Code_Complete">Steve McConnell — Code Complete: A Practical Handbook of Software Construction</a></li><li><a href="https://stripe.com/files/reports/the-developer-coefficient.pdf">Stripe — The Developer Coefficient Report: The $3 Trillion Impact of Bad Code</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c53ffa300b8e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>