<?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 Adam Kureshi on Medium]]></title>
        <description><![CDATA[Stories by Adam Kureshi on Medium]]></description>
        <link>https://medium.com/@adamkureshi.hr?source=rss-bc3ee0c84b4f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Tw_KvFdyqxTgLLdkvu45Pw.jpeg</url>
            <title>Stories by Adam Kureshi on Medium</title>
            <link>https://medium.com/@adamkureshi.hr?source=rss-bc3ee0c84b4f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:18:37 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adamkureshi.hr/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[When AI Gives Us the Answer, What Happens to the Question?]]></title>
            <link>https://medium.com/@adamkureshi.hr/when-ai-gives-us-the-answer-what-happens-to-the-question-79c4e87ffbc3?source=rss-bc3ee0c84b4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/79c4e87ffbc3</guid>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[critical-thinking]]></category>
            <dc:creator><![CDATA[Adam Kureshi]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 19:31:02 GMT</pubDate>
            <atom:updated>2026-11-16T19:31:02.088Z</atom:updated>
            <content:encoded><![CDATA[<p><em>When answers become easier to obtain, what happens to the curiosity, uncertainty and reasoning through which understanding develops?</em></p><p><em>The Thinking Human in the Age of AI | Article 02</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FSzVtu9dT8ZoRFgdvVgTuA.png" /><figcaption>An answer may resolve the question we asked while leaving the questions we should have asked unexplored.AI-generated illustration created with ChatGPT.</figcaption></figure><p>Imagine a manager trying to understand why employees are becoming less engaged at work.</p><p>Team meetings have become quieter, enthusiasm for new initiatives has declined, and employees who once volunteered ideas now seem content to do what is required and little more. The manager suspects a motivation problem. Wanting to address it before the situation deteriorates further, they turn to an AI assistant and ask a seemingly reasonable question: <em>How can I improve employee motivation and engagement?</em></p><p>Within seconds, the system produces a structured response. It recommends recognition programmes, regular feedback, professional development opportunities, team-building activities and improvements to workplace culture. The suggestions are sensible, familiar and reasonably actionable. Some might even produce measurable improvements.</p><p>The manager now has something useful to work with.</p><p>But consider another possibility.</p><p>What if the employees are not particularly unmotivated? Perhaps they have repeatedly been asked for suggestions that were never acted upon. Perhaps decisions are frequently reversed without explanation, or responsibilities have expanded while the authority to make decisions has remained unchanged. What appears to be declining motivation might instead be a response to organisational conditions that make meaningful participation increasingly difficult.</p><p>Under those circumstances, a recognition programme may do little to address the underlying problem. The manager might implement the recommendations diligently, invest resources in new initiatives and still find that employee engagement barely improves.</p><p>The difficulty is not necessarily that the AI produced a poor answer. It may have responded remarkably well to the question it was given. The more interesting problem is that the question contained an assumption that neither the manager nor the system adequately examined.</p><p>And that raises a concern about our growing reliance on artificial intelligence.</p><p>As machines become increasingly capable of answering our questions, what happens to our willingness to question the questions themselves?</p><h3>The Value of Not Knowing</h3><p>There is something uncomfortable about not having an answer.</p><p>Uncertainty can make us feel unprepared, particularly in professional environments where confidence, decisiveness and the ability to offer solutions are frequently rewarded. Managers are expected to make decisions, consultants to provide recommendations and specialists to demonstrate expertise. Even when information is incomplete, there is often pressure to move towards a conclusion rather than remain with uncertainty.</p><p>Yet not knowing is often where meaningful inquiry begins.</p><p>Consider how we approach an unfamiliar problem when a solution is not immediately available. We might start by examining what we already know, identifying what remains unclear and developing several possible explanations. As new information emerges, we may discover that our initial assumptions were incomplete. We might seek advice, examine contradictory evidence or reconsider the problem from a different perspective.</p><p>During this process, something important can happen.</p><p>The question itself begins to change.</p><p>A manager who initially asks why employees are unmotivated might eventually discover that the more useful question concerns how decisions are made within the organisation. A clinician investigating why patients do not follow treatment recommendations might find that the difficulty lies less in patient knowledge than in the practical conditions surrounding their care. A consultant examining declining productivity might discover that the organisation is measuring activity rather than meaningful output.</p><p>In each case, progress comes not simply from finding a better answer, but from developing a better understanding of what needs to be explained.</p><p>This is why uncertainty deserves a more constructive place in our thinking. It can create the space in which assumptions become visible, competing explanations emerge and questions evolve. The process of trying to understand something may reveal information that was not apparent when we first formulated the problem.</p><p>Of course, uncertainty does not automatically produce insight. People can remain confused without learning anything useful, and prolonged deliberation can become an excuse for avoiding necessary decisions. The value lies not in uncertainty itself, but in the inquiry it can encourage.</p><p>Artificial intelligence changes this experience in an interesting way.</p><p>We no longer need to remain uncertain for very long before receiving a plausible explanation. An unfamiliar concept can be explained in seconds, a complicated problem organised into categories, and a recommendation produced before we have had much opportunity to examine our assumptions.</p><p>These are extraordinary conveniences, particularly when time, expertise or access to information is limited.</p><p>But the availability of an answer does not necessarily mean that the underlying uncertainty has been resolved.</p><p>Sometimes, it simply means that we have stopped noticing it.</p><h3>When Thinking Is Outsourced</h3><p>Human beings have always relied on external resources to support their thinking.</p><p>We write reminders because we do not want to remember everything. We use calculators rather than performing every calculation mentally. We consult maps, reference materials, colleagues and search engines to accomplish tasks that would otherwise demand considerable cognitive effort. Much of what we achieve depends on our ability to combine individual knowledge with resources available beyond ourselves.</p><p>In cognitive psychology, this practice is often described as <em>cognitive offloading</em>.</p><p>In their 2016 review, <em>Cognitive Offloading</em>, Evan Risko and Sam Gilbert examine how people use physical actions and external resources to reduce the mental demands of a task. Rather than performing every cognitive operation internally, we can distribute some of that work to the environment around us.</p><p>There is nothing inherently problematic about this. Much of technological progress has involved developing tools that allow us to accomplish more without personally performing every underlying operation. The more interesting question is what we choose to offload.</p><p>Consider the difference between using a calculator to multiply two figures and asking an AI system to determine which figures should be multiplied in the first place. The first delegates a calculation. The second may delegate part of the reasoning required to understand the problem.</p><p>Both can be appropriate. AI may identify relevant variables, suggest relationships or reveal considerations that a person would otherwise overlook. But not every cognitive activity plays the same role in developing understanding.</p><p>There is another aspect to this that becomes apparent when we consider how our relationship with information has changed.</p><p>Not very long ago, searching for an answer often meant entering a question into Google, examining the results and deciding which sources deserved attention. Someone investigating an academic question might search journal repositories, read abstracts, compare papers and gradually construct an interpretation from the material available.</p><p>Search engines were already shaping this experience. Their ranking systems influenced which sources appeared first, and users were not always particularly diligent about examining evidence. The process was never entirely independent or necessarily rigorous.</p><p>Nevertheless, traditional search generally presented us with sources to navigate. Generative AI increasingly presents us with a synthesised answer, drawing on learned patterns and, where available, retrieved information.</p><p>That difference is consequential.</p><p>A 2025 study by Carolin Kaiser and colleagues, involving 1,526 participants in the United States completing practical search tasks, found that people using ChatGPT were faster and more likely to find correct answers than those using Google in the studied conditions. However, ChatGPT users relied significantly less on primary web sources.</p><p>The finding does not suggest that AI-assisted searching is inherently inferior, nor does it establish which approach produces better long-term learning. Faster access to accurate information can be enormously valuable. But it illustrates how the work of locating, selecting and interpreting information can increasingly be delegated to a system that presents its conclusions directly.</p><p>And this raises a further question.</p><p>How much of the information we encounter do we actually absorb?</p><p>Human attention and working memory are limited, particularly when dealing with unfamiliar or interconnected ideas. Accessing information, recognising its relevance, integrating it with existing knowledge and retaining it for future use are different cognitive activities. An explanation can be available to us without becoming part of what we understand.</p><p>We may now have something resembling an oracle capable of responding to an extraordinary range of questions. But the speed at which explanations become available does not necessarily correspond to the speed at which we can make sense of them. Nor does the confidence with which an answer is delivered guarantee its accuracy.</p><p>The concern is not that searching through websites was inherently educational, or that AI cannot improve our understanding. Much of the effort involved in traditional search was simply inconvenient.</p><p>Rather, when the work of finding, selecting and synthesising information becomes less visible, we may have fewer natural opportunities to examine how an answer was constructed and which alternative interpretations were left out.</p><p>Imagine a junior analyst asked to investigate why a business is becoming less profitable. AI might produce a useful framework involving declining revenue, rising costs, inefficient processes and changing customer demand. But unless the analyst examines the relationships between these factors, identifies missing evidence and tests which explanations fit the organisation’s circumstances, the framework remains a starting point rather than a diagnosis.</p><p>Used differently, the same AI-generated structure could make the investigation more productive. It could help the analyst develop competing hypotheses, identify relevant data and recognise relationships they might otherwise have overlooked.</p><p>The distinction is not between using AI and refusing to use it.</p><p>It is between delegating work in ways that support our understanding and delegating the reasoning through which that understanding might develop.</p><h3>The Seduction of a Good Answer</h3><p>One of the more intriguing characteristics of human understanding is that we are not always particularly good at recognising its limits.</p><p>We can feel familiar with an idea without being able to explain it. We may recognise the terminology used to describe a system and confidently discuss its purpose, yet struggle when asked to explain precisely how it works.</p><p>Psychologists Leonid Rozenblit and Frank Keil explored this phenomenon in their 2002 paper, <em>The Misunderstood Limits of Folk Science: An Illusion of Explanatory Depth</em>. Their research demonstrated that people often overestimate how deeply they understand familiar mechanisms. When asked to produce detailed explanations, participants frequently discovered that their understanding was less complete than they had initially assumed.</p><p>The phenomenon became known as the <em>illusion of explanatory depth</em>.</p><p>It offers an interesting perspective on our interactions with AI.</p><p>A coherent explanation can be surprisingly satisfying. It organises information, connects ideas and provides language through which we can discuss something that previously seemed confusing. An explanation that would once have required considerable effort to locate or construct can now appear almost immediately, presented in a form that is easy to follow.</p><p>But recognising a convincing explanation is not necessarily the same as possessing the understanding required to construct, evaluate or apply it independently.</p><p>More recent research offers an additional perspective.</p><p>In their 2025 study, <em>The Paradox of Information Abundance</em>, Merryn Constable and colleagues examined how people responded to information presented in the style of ChatGPT answers and Google search snippets. Participants tended to find the longer AI-style explanations more trustworthy and informative, yet the shorter responses produced better recognition of information in a subsequent test under the studied conditions. The longer responses were also less likely to prompt a desire to seek further information.</p><p>The findings do not establish that AI generally reduces learning or curiosity. They concern particular questions and answer formats, and differences in presentation are important to interpreting the results. Nevertheless, they illustrate a distinction between how informative an explanation feels and what a person subsequently remembers.</p><p>More information is not necessarily more understanding.</p><p>And an answer that feels complete may reduce the immediate motivation to investigate further, even when additional inquiry would be valuable.</p><p>Consider someone asking an AI assistant to explain why a particular public policy has failed. The system produces a persuasive analysis involving institutional incentives, implementation capacity, funding constraints and political considerations. The reader finds the explanation convincing and may even be able to repeat its central arguments in a subsequent conversation.</p><p>But what happens if someone challenges the assumptions behind it? Can the reader distinguish established evidence from plausible interpretation? Can they identify which explanation matters most, or recognise whether the same reasoning would apply in a different institutional setting?</p><p>Perhaps they can.</p><p>Perhaps they cannot.</p><p>Rozenblit and Keil were studying human understanding long before generative AI became widely available, and their findings should not be treated as direct evidence that AI causes false confidence. Rather, their research identifies a longstanding vulnerability in human judgement that becomes relevant when sophisticated explanations are available almost instantly.</p><p>The practical consequence is that an answer which feels sufficiently convincing may bring an investigation to a premature close. The initial question appears resolved, uncertainty diminishes, and attention moves towards implementation.</p><p>This matters particularly in professional settings, where an answer can quickly become a recommendation, a recommendation can become a decision, and a decision can commit people, resources and institutions to a particular course of action.</p><p>The cost of a poorly framed question is not always visible in the quality of the answer.</p><p>Sometimes, it becomes visible only after the answer has been acted upon.</p><h3>From Asking Questions to Evaluating Answers</h3><p>If artificial intelligence changes how easily we obtain answers, it may also change the nature of the thinking we perform.</p><p>In a 2025 study, <em>The Impact of Generative AI on Critical Thinking</em>, Hao-Ping Lee and colleagues surveyed 319 knowledge workers about 936 reported examples of generative AI use. The researchers examined how participants described their critical-thinking activities and how their confidence in themselves and in AI related to the effort they reported investing.</p><p>Among the findings was an association between greater confidence in AI and lower reported critical-thinking effort. But the study also identified an important shift in the nature of that thinking. Rather than concentrating exclusively on producing information or solutions, workers described activities involving verification, integration and oversight of AI-generated outputs.</p><p>This distinction matters because AI does not necessarily eliminate the need for critical thinking. It can change where that thinking occurs.</p><p>A professional who once spent considerable time developing an initial explanation may now spend more time deciding whether an AI-generated explanation is appropriate. Someone who previously constructed an analysis from the beginning may increasingly evaluate the assumptions, evidence and conclusions of an analysis produced with technological assistance.</p><p>These are meaningful intellectual activities. Evaluating evidence, identifying errors and integrating information into a coherent judgement can require considerable expertise. Yet they are not necessarily identical to the activities they replace.</p><p>The study relied on participants’ self-reported experiences. It does not establish that generative AI causes long-term deterioration in critical-thinking ability. Nevertheless, it raises a useful question about how our intellectual responsibilities may be changing.</p><p>If our work increasingly shifts towards evaluating answers, how do we ensure that we remain capable of recognising when the original question was inadequate?</p><p>Evaluation often begins with something already placed before us. Inquiry sometimes requires stepping outside that frame entirely.</p><p>There is another dimension to this relationship that I find particularly interesting.</p><p>Two people using the same AI system can receive remarkably different responses to what appears to be the same problem. Part of the difference lies in how they frame their questions, what information they provide and which assumptions they bring into the conversation. In systems that incorporate previous interactions or personal preferences, those differences may become even more pronounced.</p><p>In their 2026 study, <em>Interaction Context Often Increases Sycophancy in LLMs</em>, Jain and colleagues examined how conversational context could influence a model’s tendency towards excessive agreement. Their findings suggest that information about a user can, under some conditions, increase this tendency, although the effects differ across models and contexts.</p><p>This does not mean AI becomes a psychological replica of its user. It does, however, suggest that the interaction is shaped partly by the perspectives and information we bring into it.</p><p>In this sense, AI may increasingly function as an extension of our thinking.</p><p>Yet an extension of our thinking is not necessarily an expansion of it.</p><p>Someone who approaches AI seeking immediate confirmation may encounter a different intellectual experience from someone who consistently asks for alternative explanations, challenges assumptions and invites criticism. Neither pattern is determined entirely by the user, and a well-designed system should be capable of offering appropriate disagreement.</p><p>But the distinction matters because asking a question is not always the same as being open to an answer that challenges us.</p><p>Perhaps the real opportunity lies not simply in developing systems that become increasingly familiar with our ways of thinking, but in learning to use them to encounter perspectives that our existing habits might otherwise prevent us from considering.</p><p>The available research does not yet establish whether routine AI use makes people less capable of formulating good questions. What it does suggest is that the conditions under which we search for information, evaluate explanations and decide when to stop investigating are changing.</p><p>Whether those changes strengthen or weaken inquiry remains an important question in its own right.</p><h3>Can AI Make Us More Curious?</h3><p>So far, much of this discussion has concerned what might be lost when answers become easier to obtain.</p><p>But there is another possibility worth taking seriously.</p><p>What if AI enables us to ask questions we would never have considered asking?</p><p>Imagine someone encountering an unfamiliar subject. Previously, exploring it might have required searching through several sources, deciphering technical terminology and identifying which concepts were important enough to investigate further. The effort involved could be considerable, particularly for someone without access to experienced teachers or knowledgeable colleagues.</p><p>An AI assistant can make that initial exploration more accessible. It can explain unfamiliar terminology, suggest relevant concepts, compare competing interpretations and help someone recognise connections between fields that initially appear unrelated.</p><p>A person interested in healthcare delivery, for example, might begin by asking why patients experience long waiting times. Through further inquiry, they might encounter queueing theory, capacity planning, service design, behavioural economics and the relationship between operational efficiency and patient experience.</p><p>Each explanation can generate another question.</p><p>Why do waiting times increase disproportionately when utilisation approaches capacity? Why might patients perceive two equally long waits differently? How do appointment systems influence demand? Why can increasing staffing sometimes fail to resolve a bottleneck?</p><p>What began as a practical operational question can become an exploration of several interconnected disciplines. The person may discover that understanding waiting times requires more than examining the number of patients and available staff. It may involve studying how demand fluctuates, how work moves through a system and how people experience the services they receive.</p><p>In this setting, AI is not merely supplying answers.</p><p>It is helping the user discover what else might be worth understanding.</p><p>The difference lies partly in how the interaction unfolds. An answer can become the end of an inquiry, or it can become the beginning of another. The same explanation that satisfies one person’s curiosity may prompt someone else to investigate its assumptions, explore unfamiliar concepts or compare it with competing perspectives.</p><p>This suggests that the relationship between AI and curiosity is unlikely to be straightforward. A system that makes information easier to access may reduce some forms of intellectual effort while enabling others. Someone who would previously have abandoned a difficult subject may now find it approachable enough to explore. A professional working outside their established expertise may encounter perspectives that would otherwise remain unfamiliar.</p><p>Equally, someone who receives a satisfactory answer may decide there is no reason to investigate further.</p><p>The challenge is not to preserve difficulty for its own sake. There is little value in making knowledge unnecessarily inaccessible simply because struggling to obtain it was once unavoidable. The more meaningful objective is to preserve the kinds of engagement through which people develop understanding, while allowing technology to remove obstacles that do not contribute to that development.</p><p>Sometimes, this may mean asking AI for an explanation. In other circumstances, it may mean asking for competing hypotheses, unresolved questions or reasons why our preferred interpretation could be wrong. And occasionally, it may mean resisting the temptation to request a solution before making a serious attempt to understand the problem ourselves.</p><p>The important distinction is not how much effort we expend, but whether that effort contributes to understanding.</p><h3>Keeping the Question Alive</h3><p>Return to the manager concerned about declining employee engagement.</p><p>The original question was straightforward: <em>How can I improve employee motivation?</em></p><p>The AI system responded with plausible recommendations, many of which might have been useful under the right circumstances. But imagine the manager had approached the conversation differently, beginning not with an assumed diagnosis but with a request to examine what might explain the observed changes in employee behaviour.</p><p>Instead of immediately requesting interventions, the manager might have asked: <em>What are the possible explanations for declining employee engagement, and what evidence would help distinguish between them?</em></p><p>The resulting discussion could have taken a different direction. Rather than beginning with recognition programmes and team-building activities, it might have explored competing hypotheses involving organisational trust, workload, decision-making, leadership practices and the relationship between employees’ responsibilities and their authority.</p><p>The manager would still need to gather evidence, speak with employees and exercise judgement. AI could support that process, but it could not substitute for the responsibility to understand the organisation and the people within it.</p><p>The difference between these interactions is not simply that one prompt is more sophisticated than the other.</p><p>They represent different approaches to uncertainty.</p><p>One begins with an assumed diagnosis and seeks a solution. The other treats the diagnosis itself as something that needs to be investigated. Both may eventually produce recommendations, but the intellectual journey towards those recommendations is different.</p><p>And perhaps that is where the larger significance of AI-assisted inquiry lies.</p><p>As artificial intelligence becomes more capable, we may spend less time struggling to obtain information and more time deciding what information deserves our attention. We may become increasingly skilled at evaluating generated answers while facing new challenges in recognising which questions have been overlooked. We may also discover that AI can help us explore unfamiliar subjects, connect ideas and question assumptions more effectively than we could alone.</p><p>None of these outcomes is inevitable. They depend partly on the systems we use, the incentives surrounding our work and the habits we develop in interacting with increasingly capable technology.</p><p>The ability to obtain an answer is valuable. So is the ability to recognise when an answer is incomplete. But there is something equally important about recognising when we have been asking the wrong question.</p><p>Perhaps the challenge of living with increasingly capable AI is not simply learning how to ask it better questions. It is preserving the intellectual independence to recognise when the questions we are asking, however well answered, are leading us in the wrong direction.</p><p>After all, a system can produce an excellent answer without knowing whether it is the answer we actually need.</p><p>And if we become accustomed to accepting the questions we first formulate, we may find ourselves surrounded by increasingly sophisticated answers to problems we have never properly understood.</p><h3>Research Informing This Essay</h3><p>Risko, E. F., &amp; Gilbert, S. J. (2016) — <em>Cognitive Offloading</em>. <em>Trends in Cognitive Sciences</em>. https://doi.org/10.1016/j.tics.2016.07.002</p><p>Rozenblit, L., &amp; Keil, F. C. (2002) — <em>The Misunderstood Limits of Folk Science: An Illusion of Explanatory Depth</em>. <em>Cognitive Science</em>. https://doi.org/10.1207/s15516709cog2605_1</p><p>Lee, H.-P., et al. (2025) — <em>The Impact of Generative AI on Critical Thinking: Self-Reported Reductions in Cognitive Effort and Confidence Effects From a Survey of Knowledge Workers</em>. <em>Proceedings of CHI 2025</em>. https://doi.org/10.1145/3706598.3713778</p><p>Jain, S., et al. (2026) — <em>Interaction Context Often Increases Sycophancy in LLMs</em>. <em>Proceedings of CHI 2026</em>. https://doi.org/10.1145/3772318.3791915</p><p>Kaiser, C., et al. (2025) — <em>A New Era of Online Search? A Large-Scale Study of User Behavior and Personal Preferences during Practical Search Tasks with Generative AI versus Traditional Search Engines</em>. <em>CHI Extended Abstracts 2025</em>. https://doi.org/10.1145/3706599.3720123</p><p>Constable, M. D., et al. (2025) — <em>The Paradox of Information Abundance: Answers Provided by Popular Information-Seeking Tools Lead to Differences in Trust, Memorability and Desire for More Information</em>. <em>Telematics and Informatics</em>. https://doi.org/10.1016/j.tele.2025.102311</p><h3>Author’s Note</h3><p>This article is part of <em>The Thinking Human in the Age of AI</em>, a series exploring how artificial intelligence is reshaping human learning, judgement and professional expertise.</p><p>My intention is not to argue for or against AI, but to examine the assumptions we make about its impact on how we think, work and develop. Drawing on research, professional observations and systems thinking, I hope to make these questions more accessible and encourage a more thoughtful conversation about what technological progress means for human capability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79c4e87ffbc3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Illusion of Becoming Smarter with AI]]></title>
            <link>https://medium.com/@adamkureshi.hr/the-illusion-of-becoming-smarter-with-ai-8cb267055567?source=rss-bc3ee0c84b4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8cb267055567</guid>
            <category><![CDATA[critical-thinking]]></category>
            <category><![CDATA[human-intelligence]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[future-of-work]]></category>
            <dc:creator><![CDATA[Adam Kureshi]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 19:41:10 GMT</pubDate>
            <atom:updated>2026-11-11T19:41:10.341Z</atom:updated>
            <content:encoded><![CDATA[<p><em>When better answers disguise what we have — or have not — learned.</em></p><p><em>The Thinking Human in the Age of AI | Article 01</em></p><p>Imagine a consultant brought in to investigate why patients at a hospital are spending so much time waiting for care.</p><p>Hospital management has a fairly straightforward explanation: there are not enough staff. Patient volumes have increased, complaints are becoming more frequent, and recruiting additional personnel seems like the obvious response. Before committing to that decision, however, management wants an independent assessment of what is actually causing the delays.</p><p>The consultant has access to patient-flow data, staffing schedules and operational reports. A few years ago, examining this information, developing possible explanations and translating the findings into a credible recommendation might have required several days of work. Today, much of that preliminary analysis can be accelerated with artificial intelligence.</p><p>Using an approved AI system, the consultant examines de-identified operational data, identifies patterns and explores potential bottlenecks. Within hours, a professional report takes shape, complete with charts, supporting analysis and a convincing diagnosis.</p><p>Management is impressed. The consultant has delivered ahead of schedule, and the recommendations appear reasonable.</p><p>Then, during the presentation, a senior clinician raises a question.</p><p>What if the waiting times have less to do with staffing levels and more to do with when patients arrive? Could registration be creating an artificial bottleneck? Have differences in patient complexity been accounted for? And how reliable are the timestamps used in the analysis?</p><p>These are not necessarily objections to the report. They are questions about the reasoning behind it.</p><p>The consultant might respond confidently, explain the assumptions and demonstrate a sound understanding of the hospital’s operations. Alternatively, the consultant might struggle to explain why one interpretation was preferred over another, having relied heavily on the AI-generated analysis.</p><p>Both possibilities are plausible. Neither can be determined simply by looking at the report.</p><p>That is what makes this imagined situation interesting. The final product could be equally impressive in either case, and the hospital might receive genuine value from the work. Yet the quality of the report would tell us relatively little about how much of the underlying reasoning the consultant had actually understood.</p><p>This raises a question that extends well beyond consulting.</p><p><strong>When artificial intelligence helps us produce better work, does it also make us better at the work itself?</strong></p><h3>Doing Better Is Not Always Learning More</h3><p>We naturally associate good performance with competence. When someone writes persuasively, analyses a complicated problem or produces an insightful recommendation, we tend to assume they possess the knowledge and judgement required to do so.</p><p>Although this relationship has never been perfect, consistently producing good work has traditionally offered reasonably useful evidence of professional expertise.</p><p>But performance has never belonged entirely to the individual.</p><p>A surgeon’s effectiveness depends partly on the instruments and team available to them. An engineer relies on modelling software, established standards and the expertise of colleagues. A consultant’s analysis may depend on organisational data and people who understand the operational environment.</p><p>Professional accomplishment has always emerged from some combination of individual ability and the resources available to support it.</p><p>Artificial intelligence does not invent this relationship. What it changes is how readily sophisticated outputs can be produced without the same degree of prior familiarity with the work involved.</p><p>Someone who has never developed a financial model may now generate a credible-looking forecast. A junior analyst can produce a polished strategic assessment. A professional unfamiliar with programming can create functional code, while a student struggling to articulate an argument can produce an essay that reads remarkably well.</p><p>These are not trivial achievements. In many circumstances, they represent genuine improvements in productivity and access to capabilities that would otherwise remain unavailable.</p><p>Yet they also complicate an assumption we rarely needed to examine so closely.</p><p><strong>Being able to accomplish something is not necessarily the same as having learned how to accomplish it.</strong></p><p>Learning researchers have recognised this distinction for decades. In their 2015 review, <em>Learning Versus Performance</em>, Nicholas Soderstrom and Robert Bjork explain why improvements observed during practice do not necessarily demonstrate durable learning.</p><p>A person may perform well under favourable conditions, particularly when guidance or immediate feedback makes a task easier. But the strength of that learning becomes clearer when they must retrieve the knowledge later or apply it in an unfamiliar situation.</p><p>Consider someone learning to play the piano. They may successfully reproduce a passage while following illuminated keys or carefully observing a demonstration. The performance might sound excellent, but that does not necessarily mean they can reproduce the passage from memory, understand its structure or apply what they have learned to another piece.</p><p>The assistance helped them perform. Whether it helped them learn remains a separate question.</p><p>Something similar can happen in professional work. A person may complete an analysis by following AI-generated reasoning without developing the judgement needed to recognise when that reasoning is inappropriate. Equally, they may use the same assistance to understand unfamiliar concepts, test alternative explanations and become more capable than they were before.</p><p>Recent research involving generative AI has made this distinction particularly relevant.</p><p>In a 2026 study published in Nature Human Behaviour, Wiles and colleagues examined how 487 management consultants performed on unfamiliar data-science tasks with access to ChatGPT and associated training.</p><p>The consultants receiving AI assistance performed better on the assigned tasks, demonstrating an expanded ability to undertake work beyond their established expertise.</p><p>However, when their technical knowledge was subsequently assessed without AI assistance, the researchers found no evidence that the assisted group had acquired greater technical knowledge than the comparison group.</p><p>This does not establish that AI prevents learning or causes existing skills to deteriorate. Rather, it demonstrates that improvements in assisted performance need not be accompanied by measurable gains in independent knowledge, at least under the conditions examined.</p><p>The consultants accomplished more with the tool. Whether they acquired equivalent knowledge was another matter.</p><h3>The Performance–Capability Gap</h3><p>The relationship between technological assistance and human capability has a longer intellectual history than generative AI.</p><p>In 1983, Lisanne Bainbridge published <em>Ironies of Automation</em>, examining a paradox in industrial control systems that remains relevant today. As machines assume more routine responsibilities, human operators may still be expected to intervene when something goes wrong, despite having fewer opportunities to practise the skills required for those interventions.</p><p>Although Bainbridge was examining industrial automation rather than artificial intelligence, the underlying tension offers a useful starting point for understanding the challenges of AI-assisted knowledge work.</p><p>Automation can make a system more effective under ordinary conditions while creating new demands on the people expected to manage its exceptions.</p><p>More recently, researchers have begun examining similar tensions in AI-assisted knowledge work. In their 2026 conceptual paper, <em>Fast Outputs, Fragile Expertise: The AI-Enabled Capability Paradox</em>, Ritu Raj and Shreya Pandey propose that increasingly sophisticated AI-assisted outputs may obscure whether professionals are developing the expertise required to produce, evaluate and sustain such work.</p><p>Their argument raises an important organisational possibility: when speed and polished deliverables become dominant measures of performance, the reasoning and practice behind those results may receive less attention. This remains a theoretical proposition rather than an empirically established consequence of AI adoption.</p><p>A 2026 study by Ridha Horchani, examining AI-assisted mathematics learning, offers a more direct illustration of the performance–capability gap. Reanalysing data from a randomised educational experiment, Horchani found that high scores during AI-assisted practice were substantially less informative about students’ subsequent unaided examination performance.</p><p>The study does not establish that AI necessarily weakens learning. Rather, it highlights a measurement problem: when assistance contributes substantially to performance, the resulting scores may become less reliable indicators of what individuals can demonstrate independently.</p><p>The underlying idea is accessible: <strong>what someone can accomplish with technological assistance may differ from what they can reliably understand, evaluate or apply through their developed expertise.</strong></p><p>This is not a newly invented theory, nor is it a formal measure of intelligence. It is a useful way of bringing together established questions about performance, learning and the role of automation in human work.</p><p>Importantly, the existence of such a gap is not necessarily a problem.</p><p>Extending human capability is precisely what good technology is supposed to do. A statistician does not become less competent because software performs complex calculations, just as an architect does not need to abandon computer-aided design to demonstrate professional expertise.</p><p>The ability to select, direct and evaluate sophisticated tools is itself a valuable capability.</p><p>What matters is whether people possess the understanding and judgement their responsibilities require.</p><p>Imagine two analysts using the same AI system to investigate an organisational problem. Both receive similar recommendations, and both produce reports of comparable quality.</p><p>The first examines the assumptions, compares the recommendations against available evidence and challenges conclusions that do not fit the operational context.</p><p>The second accepts the recommendations largely because they appear coherent and technically sophisticated.</p><p>From the perspective of the final deliverable, the difference may be difficult to detect. Yet the two analysts are not necessarily demonstrating the same capabilities.</p><p>One may be developing a deeper understanding through interaction with the system. The other may be becoming increasingly effective at producing the appearance of that understanding.</p><p>Neither conclusion can be established from the report alone. We would need to observe how the analysts reason, what they retain and how they respond when confronted with a different problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m7a26rx_wsVyteANyTSNAg.png" /><figcaption><em>Conceptual synthesis of established research on performance, learning and AI-assisted capability. Framework interpretation by the author; visual created with AI assistance. Illustrative trajectories, not empirical measurements.</em></figcaption></figure><p>AI assistance can extend performance without producing equivalent independent learning. It can also support genuine capability development. Under some conditions, it may even inhibit the development of skills that would otherwise have emerged through practice.</p><p>These possibilities can coexist. Someone might become better at evaluating AI-generated work while becoming less practised at producing certain components from scratch.</p><p>Nor should we assume that every skill displaced by technology deserves to be preserved. Much of technological progress consists precisely of removing tasks that consume time without creating proportionate value.</p><p>The relevant concern is not the disappearance of every manual activity, but the preservation and development of capabilities needed for understanding, judgement and adaptation.</p><p>If AI can generate an excellent answer, what does the professional still need to know to recognise whether that answer is appropriate?</p><p>And if the answer is wrong, what enables them to notice?</p><h3>When Assistance Becomes Understanding</h3><p>It would be tempting to interpret these concerns as evidence that artificial intelligence is making people intellectually dependent.</p><p>But that conclusion would be premature. It also overlooks an equally important possibility: AI can help people learn.</p><p>A study by Erik Brynjolfsson, Danielle Li and Lindsey Raymond, published in <em>The Quarterly Journal of Economics</em> in 2025, examined the introduction of an AI assistant among 5,172 customer-support agents.</p><p>The researchers found that AI assistance increased productivity by approximately 15% on average, with particularly substantial benefits for less experienced and lower-skilled workers. They also identified evidence consistent with workers learning useful practices through repeated interaction with the system.</p><p>Unlike a controlled examination of unaided knowledge, this evidence emerged from patterns observed during a real-world workplace rollout. It nevertheless suggests that AI assistance can support learning, rather than simply substitute for existing expertise.</p><p>This complicates the idea that AI merely substitutes for human knowledge.</p><p>In some environments, AI may make effective practices more accessible. An inexperienced employee can encounter approaches, language and problem-solving techniques that previously might have required prolonged exposure to experienced colleagues. With repeated engagement, some of those practices may become part of the employee’s own repertoire.</p><p>The important question, then, is not whether AI helps or harms learning in general, but <strong>under what conditions assistance becomes understanding</strong>.</p><p>Does the system explain why a recommendation makes sense? Does the person have opportunities to question it? Is there meaningful feedback when something goes wrong? Are users encouraged to compare alternatives, or are they rewarded primarily for completing tasks as quickly as possible?</p><p>A professional who uses AI to explore competing explanations may emerge with a richer understanding of a problem. Another who uses the same system simply to generate a final recommendation may produce equally polished work without undergoing the same learning process.</p><p>The tool may be identical. The experience is not.</p><p>I was reminded of this distinction during a recent leadership workshop, where a particular piece of advice stayed with me:</p><p><strong>“Fall in love with the problem, not the solution.”</strong></p><p>At first, it sounds like familiar advice about innovation and problem-solving. But in the context of artificial intelligence, I think it carries a deeper significance.</p><p>AI has made it remarkably easy to arrive at something that resembles a solution. We can generate recommendations, construct arguments and develop convincing explanations before we have fully understood the problem ourselves.</p><p>The danger is not necessarily that these solutions are wrong. Some may be excellent. It is that the ease of obtaining them can tempt us to move past the very questions through which understanding develops.</p><p>To fall in love with the problem is to remain curious about its underlying causes, question our assumptions and resist becoming prematurely attached to the first plausible answer. It requires us to engage with uncertainty rather than treating it merely as an obstacle to be eliminated.</p><p>Perhaps this is one of the more important distinctions in how we use AI: whether we approach it primarily as a machine for producing answers or as a means of becoming better at asking questions.</p><p>This does not mean independent expertise and AI collaboration must be competing objectives. A capable professional may increasingly be someone who knows how to combine their own judgement with machine-generated analysis, recognising the strengths and limitations of each.</p><p>But that kind of capability must itself be developed. Access to a sophisticated system does not automatically confer the judgement required to use it well.</p><h3>When the Work Becomes the Measure of the Worker</h3><p>The implications become more complicated when we move beyond individual learning and consider how organisations evaluate professional competence.</p><p>Organisations have always relied, at least partly, on observable performance to make judgements about people. Reports, presentations, analyses, project outcomes and other deliverables become evidence of an employee’s effectiveness.</p><p>These signals have never been perfect. A successful project may reflect the efforts of an entire team, favourable circumstances or decisions made long before a particular employee became involved. Nevertheless, they have traditionally provided useful information about professional ability.</p><p>As AI becomes more deeply integrated into knowledge work, the relationship between what someone produces and what they personally understand may become harder to interpret.</p><p>Return to our consultant investigating hospital waiting times.</p><p>The client receives a convincing analysis, perhaps one that genuinely improves patient flow and reduces delays. From the client’s immediate perspective, the engagement may have been successful.</p><p>But suppose the consulting organisation now uses the quality of that report to assess the consultant’s readiness for more complex assignments.</p><p>What exactly has been demonstrated?</p><p>The consultant may be excellent at directing AI systems, synthesising evidence and translating analysis into actionable recommendations. Those are valuable capabilities. Alternatively, the consultant may have relied on recommendations they were not adequately equipped to challenge.</p><p>The same deliverable might support very different conclusions about the professional behind it.</p><p>This creates a distinction between three things organisations often treat as closely related:</p><p><strong>The value of the work produced. The capability of the person producing it. And the conclusions that can reasonably be drawn from observing the result.</strong></p><p>A high-quality deliverable provides evidence about the first. It may offer clues about the second. But the third requires careful judgement, particularly when sophisticated tools have contributed substantially to the work.</p><p>Consider how this might affect professional development.</p><p>A junior consultant who produces excellent analyses with AI may be ready to handle a greater volume of work. But does that necessarily mean they are ready to lead a difficult client conversation, challenge an unreliable dataset or make a recommendation when the available evidence is incomplete?</p><p>Perhaps they are. Perhaps they are not. The finished reports alone may be insufficient to decide.</p><p>The same issue appears in recruitment and education. A polished assignment or impressive analytical exercise may demonstrate effective use of available resources without necessarily revealing how much of the underlying reasoning a person can independently defend.</p><p>None of this suggests that organisations should disregard AI-assisted results. The ability to create better outcomes with fewer resources is an important part of professional value. Indeed, insisting that employees perform every task manually could waste time and limit the benefits of technological progress.</p><p>But <strong>the value of the work and the development of the worker are not identical measures.</strong></p><p>An organisation may improve its immediate productivity while remaining uncertain about whether its employees are developing the capabilities needed to address unfamiliar problems in the future.</p><p>That uncertainty matters because today’s output is not the only thing an organisation depends upon. It also relies on the accumulated knowledge, judgement and adaptability of the people who will confront tomorrow’s challenges.</p><p>There is a further possibility worth considering. If employees are rewarded almost exclusively for speed and polished deliverables, they may have fewer incentives to spend time examining assumptions, testing alternative explanations or understanding why a recommendation works.</p><p>Over time, an organisation could become increasingly effective at producing sophisticated work without becoming equally effective at developing the expertise required to evaluate it.</p><p>This is a plausible organisational risk rather than an established universal consequence of AI adoption. Its significance will depend on the nature of the work, the incentives surrounding it and the opportunities employees have to learn.</p><p>Still, it suggests that organisations may need to become more deliberate about what they are actually measuring.</p><p>A professional’s ability to deliver excellent results with AI matters. So does their capacity to recognise errors, exercise judgement, explain consequential decisions and adapt when circumstances change.</p><p>These capabilities overlap, but they should not automatically be treated as interchangeable.</p><h3>What Are We Actually Becoming Better At?</h3><p>Much of the conversation about AI and work is understandably concerned with productivity.</p><p>How much faster can a task be completed? How much more work can a professional undertake? How much does the quality of the output improve?</p><p>These are legitimate questions. In many settings, the answers will determine whether AI creates meaningful value.</p><p>But productivity is only one dimension of what happens when people work with technology. There is also the question of what the experience does to the person performing the work.</p><p>Does repeated use of AI strengthen their ability to recognise patterns, evaluate evidence and make decisions? Does it expose them to ideas they would not otherwise have encountered? Does it encourage intellectual curiosity, or make it easier to bypass the uncomfortable process of working through uncertainty?</p><p>The answers are unlikely to be uniform.</p><p>A student, an experienced clinician, a junior consultant and a software engineer may interact with the same technology in very different ways. The skills they need to preserve, the knowledge they can acquire and the consequences of misplaced confidence will differ accordingly.</p><p>This is why I find the language of AI making us <em>smarter</em> somewhat unsatisfying.</p><p><strong>Smarter in what sense?</strong></p><p>We may be faster at producing an answer without becoming better at recognising whether it is correct. We may become more effective at structuring an argument without developing a deeper understanding of its assumptions.</p><p>Equally, we may use AI to challenge our thinking, discover unfamiliar perspectives and develop capabilities that would otherwise have taken much longer to acquire.</p><p>Perhaps the more meaningful measure of AI’s contribution to human development is not simply what it enables us to produce, but what remains with us after the interaction.</p><p>Not every skill needs to remain independent of technology. Not every task needs to become a learning exercise. But when understanding and judgement matter, we should be cautious about assuming that improved outputs demonstrate their development.</p><p>Which brings us back to the consultant and the hospital report.</p><p>The analysis may have been excellent. The recommendations may have improved patient care, and the consultant may have delivered genuine value. None of that needs to be diminished.</p><p>But the question raised during the presentation remains important, not because the consultant should have worked without AI, but because professional expertise involves more than producing a convincing answer.</p><p>It also involves knowing what makes that answer convincing, when it might be wrong and what to do when the circumstances change.</p><p>And perhaps that is the question we should carry into an increasingly AI-assisted world:</p><p><strong>As AI makes it easier for us to produce the work of experts, how will we know whether we are also becoming experts ourselves?</strong></p><h3>Research Informing This Essay</h3><ul><li>Soderstrom &amp; Bjork (2015) — <em>Learning Versus Performance: An Integrative Review</em></li><li>Bainbridge (1983) — <em>Ironies of Automation</em></li><li>Wiles et al. (2026) — <em>Generative AI and the Temporary Upskilling of Knowledge Workers</em></li><li>Brynjolfsson, Li &amp; Raymond (2025) — <em>Generative AI at Work</em></li><li>Raj &amp; Pandey (2026) — Fast Outputs, Fragile Expertise: the AI-Enabled Capability Paradox</li><li>Horchani (2026) — Generative AI and the Performance–Capability Gap in a Randomized Mathematics Experiment</li></ul><h3>Author’s Note</h3><p>This article is part of <em>The Thinking Human in the Age of AI</em>, a series exploring how artificial intelligence is reshaping human learning, judgement and professional expertise.</p><p>My intention is not to argue for or against AI, but to examine the assumptions we make about its impact on how we think, work and develop. Drawing on research, professional observations and systems thinking, I hope to make these questions more accessible and encourage a more thoughtful conversation about what technological progress means for human capability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8cb267055567" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Remains When the Consultants Leave?]]></title>
            <link>https://medium.com/@adamkureshi.hr/what-remains-when-the-consultants-leave-bed507fb8da3?source=rss-bc3ee0c84b4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bed507fb8da3</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[organizational-change]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management-consulting]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Adam Kureshi]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 21:01:02 GMT</pubDate>
            <atom:updated>2026-11-04T21:01:02.011Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The Value Paradox | Part III</em></p><p><em>Why lasting transformation depends on what organisations can do without external support.</em></p><p>There is a particular ceremony associated with the completion of a consulting engagement.</p><p>The final presentation is delivered. The recommendations are accepted. The implementation report is signed off. Perhaps a photograph is taken to commemorate the occasion.</p><p>There are acknowledgements, expressions of appreciation, and assurances that the work will make a meaningful difference.</p><p>The consultants pack their belongings, close their assignments, and move on to the next engagement.</p><p>And the organisation returns to work.</p><p>For a while, everything may appear to be going according to plan.</p><p>The new system continues operating. Employees follow the revised procedures. Managers refer to the dashboards developed during implementation. The strategy remains prominently displayed in the organisation’s planning documents.</p><p>Then ordinary organisational life begins to intervene.</p><p>A senior manager is transferred. An experienced employee resigns. A budget is reduced. A technology requires updating. An unforeseen problem emerges that was never anticipated in the original implementation plan.</p><p>The organisation must make decisions, but the people who designed the intervention are no longer there to guide them.</p><p>Perhaps employees know how to operate the system but not how to modify it. Perhaps the strategy explains what should be achieved but offers little guidance when circumstances change. Or perhaps the organisation has inherited the solution without developing the authority or confidence to manage its future.</p><p>This is a hypothetical scenario, but the underlying problem is familiar across organisational transformation.</p><p>It is not confined to consultancy. Similar challenges arise when development partners conclude their programmes, technical assistance teams withdraw, technology vendors complete implementations, or internal transformation teams return to their regular responsibilities.</p><p>In each case, the original intervention may have delivered exactly what was promised. It may even have produced genuine improvements.</p><p>Yet the circumstances that made those improvements possible are not necessarily the same circumstances that will allow them to endure.</p><p>And that leaves us with a question that is often more difficult to answer than whether the project was completed successfully.</p><p><strong>What remains when the people responsible for creating an improvement are no longer responsible for sustaining it?</strong></p><h3>The Third Question of Value</h3><p>In the first article of <a href="https://medium.com/@adamkureshi.hr/who-decides-what-value-is-70acbbcc2281"><em>The Value Paradox</em></a>, I explored how different stakeholders can understand the value of an intervention differently.</p><p>What appears valuable to a funding organisation may not necessarily be recognised as valuable by the institution receiving support or the people using its services.</p><p>The second article examined another problem.</p><p>Even when organisations agree on what they want to achieve, completing the work does not establish that the intended benefits have materialised.</p><p>A system may be delivered without improving services. A strategy may be approved without changing decisions. Employees may receive training without changing how they work.</p><p>But suppose an intervention succeeds.</p><p>Costs decline. Services become more accessible. Processes become faster. Employees work more effectively.</p><p>These are meaningful achievements, and they deserve to be recognised as such.</p><p>Yet there is a difference between producing an improvement and establishing the conditions through which that improvement can continue.</p><p>In international development, the OECD’s Development Assistance Committee recognises sustainability as a distinct evaluation criterion. It concerns whether the net benefits of an intervention continue, or are likely to continue, over time.</p><p>The word <em>net</em> matters.</p><p>A digital system may save employees time while demanding increasingly expensive technical support. A programme may continue operating while the resources required to maintain it steadily exceed the benefits it produces.</p><p>In both situations, the intervention may remain operational without necessarily remaining worthwhile.</p><p>There is also the question of relevance.</p><p>A strategy developed for one set of circumstances may become less useful as priorities change. A technology that once represented a significant improvement may eventually become an obstacle to further progress.</p><p>Sustainability cannot simply mean keeping the original solution alive indefinitely.</p><p>Sometimes, the ability to replace an outdated solution is precisely what demonstrates that an organisation has become more capable.</p><p>The more meaningful question, then, is whether an organisation can continue producing worthwhile outcomes even as the circumstances around it change.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DmvCXUoECcL4w8cD6hYBxA.png" /><figcaption>The Progression of Value: From defining what matters to realising improvements and sustaining them over time.</figcaption></figure><p>This distinction becomes clearer when we examine what happens to interventions long after their initial implementation.</p><h3>When a Project Becomes Infrastructure</h3><p>At the beginning of the twenty-first century, Estonia faced a problem familiar to governments around the world.</p><p>Public institutions possessed information, but their systems were not necessarily capable of exchanging it efficiently. Different agencies maintained separate databases, and information moved through institutional boundaries that made coordination cumbersome.</p><p>Digitising individual departments could improve their internal operations, but it would not automatically solve the wider problem of communication between them.</p><p>Estonia needed more than another government database. It needed a way for different information systems to exchange information securely while allowing participating institutions to retain responsibility for their own data.</p><p>The solution became known as X-Road.</p><p>Its national deployment began in December 2001, following development involving Estonia’s public institutions and private technical expertise. The original procurement was awarded to AS Assert, with Cybernetica among the subcontractors contributing to the system’s architecture and security.</p><p>X-Road provided a foundation through which separate systems could communicate. Rather than requiring government information to be consolidated into one enormous database, it enabled participating organisations to exchange information through a shared technical and organisational environment.</p><p>Today, Estonia’s national implementation is known as X-tee, while X-Road refers to the underlying technology developed through international cooperation.</p><p>But the most interesting part of this story is not simply that Estonia developed a functioning digital platform.</p><p>It is what happened afterwards.</p><p>The technology continued evolving.</p><p>Estonia and Finland formalised cooperation in 2013. The core source code was made openly available during 2015 and 2016. In 2017, the two countries established the Nordic Institute for Interoperability Solutions, or NIIS, to provide a more enduring arrangement for developing the technology.</p><p>NIIS subsequently took responsibility for core software development, while Estonia’s Information System Authority continued administering the country’s national X-tee environment.</p><p>What began as a technical solution acquired institutions, responsibilities, development arrangements, and a wider community capable of supporting its continued evolution.</p><p>The project became infrastructure.</p><p>And that infrastructure developed an institutional life beyond the original implementation.</p><p>There is an important qualification.</p><p>Estonia did not eliminate external technical expertise. Private technology providers continued participating in the wider ecosystem. It would therefore be misleading to present X-Road as a straightforward story of consultants delivering a solution, transferring everything to government, and disappearing.</p><p>The more useful lesson is different.</p><p><strong>Sustainability did not require external expertise to disappear. It required arrangements through which the technology could continue to be governed, maintained, and developed.</strong></p><p>An institution does not necessarily need to possess every technical skill internally. But it must understand the system it relies upon, the responsibilities it retains, the relationships through which it operates, and the decisions required to secure its future.</p><p>X-Road’s continued development does not prove that Estonia has solved every challenge associated with digital government. Nor does it establish that its approach can be reproduced elsewhere without difficulty.</p><p>What it illustrates is that a technological intervention can become the foundation for further institutional development when its continued operation is supported by appropriate arrangements.</p><p>The original achievement was not simply the creation of a platform. It was also the development of the conditions through which that platform could remain useful.</p><p>And this is where the story of sustainability becomes more complicated.</p><p>Because while some interventions gradually become embedded in the institutions they were designed to support, others remain dependent on the conditions under which they were introduced.</p><h3>When Support Outlasts Ownership</h3><p>A different experience emerged from Zambia’s education sector.</p><p>The country’s Primary Reading Programme was introduced to improve literacy teaching in primary schools, including through the use of local languages.</p><p>The programme received support from the United Kingdom’s Department for International Development between 1999 and 2005. It involved changes to teaching approaches, learning materials, and teacher development.</p><p>Years later, researchers Charity Lengwe Meki Kombe and Chaya Herman examined what had happened to the programme after donor support ended.</p><p>Their 2017 study found that it had been poorly sustained, with many elements substantially altered or discontinued.</p><p>The researchers identified several contributing factors, including programme design, stakeholder ownership and motivation, resource availability, monitoring and evaluation, school conditions, and changes in the wider policy environment.</p><p>One finding is particularly relevant.</p><p>The researchers cautioned that innovations requiring inputs and activities beyond the socioeconomic capacity of their intended beneficiaries may prove difficult to sustain.</p><p>This raises an uncomfortable question.</p><p>What happens when an intervention is designed around resources that the receiving institution cannot reasonably maintain?</p><p>A programme may function effectively while externally funded materials, training, technical support, and monitoring are available. But if those resources cannot be replaced or incorporated into routine institutional arrangements, the programme may become increasingly difficult to sustain.</p><p>The problem is not necessarily that the intervention was poorly conceived or that the people involved lacked commitment.</p><p>It may be that the operating conditions required for success were never sufficiently secured beyond the period of external support.</p><p>The Zambia study also identified what the researchers described as a <em>project mentality</em>, where attitudes towards externally supported programmes could undermine ownership and commitment.</p><p>This is especially revealing.</p><p>An intervention can be formally introduced into an institution without becoming something the institution genuinely regards as its own responsibility.</p><p>It may remain, in practice, somebody else’s project.</p><p>There are limits to what we should conclude from this case.</p><p>The research does not establish that the programme achieved nothing, nor does it demonstrate that donor withdrawal alone caused its subsequent difficulties. And a donor-supported education programme is not equivalent to a conventional management-consulting engagement.</p><p>Nevertheless, the sustainability problem is transferable.</p><p><strong>An intervention can improve performance while remaining dependent on conditions that the receiving organisation cannot reproduce.</strong></p><p>The contrast with Estonia is useful precisely because the two cases are so different.</p><p>Estonia illustrates how governance arrangements can support the continued development of an intervention. Zambia demonstrates how resource constraints, programme design, and institutional ownership can affect the continuation of externally supported activities.</p><p>The lesson is not that technology succeeds where education fails.</p><p>It is that the continuation of benefits depends on more than the quality of the original intervention.</p><h3>Teaching Someone to Fish Is Only the Beginning</h3><p>There is a familiar proverb about the difference between giving someone a fish and teaching them how to fish.</p><p>Its appeal is straightforward.</p><p>Providing the fish addresses an immediate need. Teaching the skill creates the possibility of meeting that need independently.</p><p>The distinction is frequently invoked in discussions about development, education, and capacity building.</p><p>But when applied to institutions, the proverb feels incomplete.</p><p>What happens when the person who learned to fish leaves the village? What happens when the equipment breaks, the river changes course, or the community grows?</p><p>An individual skill may be valuable without being sufficient to sustain an entire community.</p><p>The village needs more than someone who knows how to fish.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*akCj1TfbmKm1tftIz4i17g.png" /><figcaption>From individual knowledge transfer to institutional capability.</figcaption></figure><p>It may need shared knowledge, maintained equipment, agreed responsibilities, access to resources, and ways of adapting when circumstances change.</p><p>The same reasoning applies to organisations.</p><p>Training employees to operate a system may address an immediate capability gap. But if only two employees understand its essential functions, the organisation remains vulnerable to their departure.</p><p>A comprehensive operating manual may preserve valuable knowledge. Yet if it is never incorporated into routine practice, it may become little more than an archived document.</p><p>A strategy may identify the right priorities without providing the authority, incentives, or resources needed to act upon them.</p><p>This is why knowledge transfer and institutional capability should not be treated as interchangeable.</p><p>Knowledge can be transferred to individuals.</p><p>Institutional capability requires that knowledge to become usable through organisational arrangements that extend beyond those individuals.</p><p>This involves who makes decisions, how problems are identified, how employees learn from experience, and how responsibilities are maintained when people change roles.</p><p>In that sense, the most valuable intervention may not simply teach an organisation how to operate the solution it has received.</p><p>It may strengthen the organisation’s ability to understand and respond to the next problem.</p><p>And there is evidence that this distinction matters beyond the public sector.</p><h3>Sustaining the Ability to Improve</h3><p>At AstraZeneca’s Turbuhaler production unit in Sweden, researchers Bonnie Poksinska and Dag Swartling examined a Lean improvement programme through a longitudinal study spanning nine years.</p><p>The organisation had introduced Lean practices to improve manufacturing performance. Over the longer transformation journey, the researchers documented substantial improvements in productivity and quality performance.</p><p>But the more interesting finding concerned how the improvement programme evolved.</p><p>Early attempts to introduce standardised work encountered resistance when procedures developed with external consultants did not adequately involve the operators expected to use them.</p><p>The organisation subsequently changed its approach.</p><p>Employees became more directly involved in developing and refining working methods. Teams assumed greater responsibility for daily operations, while managers increasingly focused on supporting and coaching employees rather than simply directing activities.</p><p>As these practices matured, improvement became more firmly embedded in the organisation’s everyday operations.</p><p>The researchers distinguished between two forms of sustainability.</p><p>They called the ability to maintain achieved results <em>first-order sustainability</em>.</p><p>They described the ability to keep the improvement programme itself alive as <em>second-order sustainability</em>.</p><p>The distinction is particularly useful.</p><p>Imagine a hospital reducing average patient waiting times from ninety minutes to fifty-five minutes.</p><p>If it maintains that improvement over several years, it has achieved something worthwhile.</p><p>But suppose patient demand increases, staffing patterns change, or new services are introduced. The original process may no longer be adequate.</p><p>An organisation capable of sustaining improvement should be able to recognise the emerging problem, examine its causes, and adapt its processes rather than automatically requiring another externally led transformation.</p><p>The first form of sustainability concerns the persistence of an improvement.</p><p>The second concerns the persistence of the ability to improve.</p><p>The AstraZeneca study is not evidence that all consultants should withdraw after implementation, nor is it a controlled comparison proving which particular practices caused every observed result.</p><p>Its value lies in showing how improvement can become embedded in the ordinary responsibilities and behaviours of an organisation.</p><p>At that point, the organisation is no longer simply preserving what was introduced.</p><p>It is developing the capability to change what was introduced when change becomes necessary.</p><p>This brings us to a practical difficulty that is often concealed by the formalities of project completion.</p><h3>When Is an Organisation Ready to Take Ownership?</h3><p>How should an organisation know whether it is ready for the consultants to leave?</p><p>The conventional answer often involves a handover checklist.</p><p>Have the documents been submitted? Has the training been completed? Have the operating procedures been approved? Have the designated employees received access to the system?</p><p>These are reasonable requirements.</p><p>But they are largely evidence that a transfer process has occurred.</p><p>They do not necessarily demonstrate that the organisation can exercise the responsibilities it has inherited.</p><p>A hospital may have received training on a digital system without having anyone capable of resolving a significant operational problem. A government department may possess a strategy without having an established process for reviewing priorities when budgets change. A manufacturing business may have adopted new procedures without giving employees the authority to improve them.</p><p>A more meaningful assessment would examine what happens when the organisation must act without the implementation team.</p><p>Who is accountable when performance deteriorates? Can employees diagnose routine problems and escalate unfamiliar ones? Are the necessary resources available through ordinary budgets rather than temporary project allocations?</p><p>Can the organisation replace key personnel without losing essential knowledge? Does it understand its contractual and technical dependencies?</p><p>And perhaps most importantly, can it identify when the original solution is no longer appropriate?</p><p>These questions suggest that handover should be demonstrated through operational capability, not merely documented through administrative completion.</p><p>Consider a hypothetical hospital preparing to assume responsibility for a newly implemented patient-management system.</p><p>Before handover, its internal team might be asked to manage a simulated system disruption, revise a routine workflow, investigate a reporting discrepancy, and explain how a future upgrade would be evaluated.</p><p>The consultant remains available to observe and support, but the hospital’s team leads the response.</p><p>Such an exercise would not guarantee that every future challenge could be managed independently. It would, however, provide stronger evidence of readiness than a signed training attendance sheet.</p><p>This also changes when sustainability should be considered.</p><p>If institutional ownership is discussed only during the final weeks of an engagement, the organisation may have too little time to develop the capabilities it needs.</p><p>Responsibilities must be introduced, practised, tested, and progressively transferred throughout implementation.</p><p>A consultant should not simply ask whether the client has received the necessary knowledge.</p><p>The more demanding question is whether the client has demonstrated the ability to use it.</p><h3>The Difference Between Dependence and Partnership</h3><p>At this point, an obvious conclusion might be that consultants should make their clients completely independent.</p><p>But that would be too simplistic.</p><p>Organisations rarely possess every capability they require internally.</p><p>Hospitals depend on specialist equipment manufacturers. Businesses rely on external technology providers. Governments procure expertise that would be expensive or impractical to maintain permanently within the civil service.</p><p>There are sound reasons for these arrangements.</p><p>The problem is not dependence itself.</p><p>It is dependence that an organisation cannot adequately understand, manage, afford, or change.</p><p>Consider two hospitals operating similar digital systems.</p><p>Both rely on external vendors for specialised maintenance.</p><p>The first understands its contractual arrangements, retains appropriate access to its data, possesses sufficient internal expertise to manage routine operations, and can evaluate alternative suppliers if necessary.</p><p>The second cannot modify basic workflows without the vendor, lacks adequate documentation, and has limited understanding of the costs or consequences of changing providers.</p><p>Both hospitals are externally dependent.</p><p>But they are not equally capable of governing that dependence.</p><p>The distinction has financial implications.</p><p>A system that appears inexpensive to implement may become costly if every minor adjustment requires a separately billed intervention. Conversely, employing a permanent internal team for highly specialised work needed only occasionally may be an inefficient use of resources.</p><p>Sustainability therefore requires judgement about which capabilities should be retained internally, which can reasonably be procured externally, and how the organisation preserves sufficient control over the relationship.</p><p>The initial investment is only part of the economic decision. Ongoing maintenance, retraining, upgrades, replacement costs, and contractual obligations also shape the value that remains.</p><p>This is why a sustainable solution need not be self-sufficient.</p><p>It needs to be governable.</p><h3>When the Next Engagement Begins with a New Problem</h3><p>Perhaps this also invites us to reconsider what a successful consulting relationship should become.</p><p>A consultant may spend one or two years helping an organisation diagnose a problem, develop a strategy, implement a solution, and establish the arrangements needed to sustain it.</p><p>During that period, reliance on external expertise may be entirely reasonable. The consultant understands the intervention, the organisation is learning, and responsibilities are gradually transferred as new capabilities become operational.</p><p>But once the original problem has been addressed, the relationship should be allowed to evolve.</p><p>Suppose a consultancy helps a hospital implement an electronic medical record system.</p><p>The hospital eventually becomes capable of managing routine operations, maintaining its data, and making informed decisions about the technology.</p><p>That should be regarded as an achievement.</p><p>It does not mean the hospital will never require external expertise again.</p><p>The new digital foundation may reveal opportunities for interoperability, clinical analytics, patient-flow redesign, or more sophisticated resource planning.</p><p>These may justify entirely new engagements.</p><p>But the justification should be the value of addressing a new problem, not the preservation of an old dependency.</p><p>The consultant’s contribution evolves as the client’s capabilities mature.</p><p>And sometimes, the most appropriate next engagement is no engagement at all.</p><p>An organisation that can continue independently may be demonstrating precisely the kind of capability the original intervention was intended to create.</p><p>The principle is simple.</p><p><strong>The next engagement should be earned through a new opportunity to create value, not secured by ensuring that the previous problem remains unresolved.</strong></p><h3>What Remains Is the Real Legacy</h3><p>We began with the familiar ceremony of project completion.</p><p>The final report is accepted. The strategy is approved. The system becomes operational. The consultants leave.</p><p>These moments matter.</p><p>They represent real work, expertise, investment, and effort. Without successful delivery, many improvements would never become possible.</p><p>But across this series, a more demanding understanding of value has gradually emerged.</p><p>First, value must be understood in relation to the people and institutions expected to benefit from it.</p><p>Second, value must be demonstrated through meaningful improvements rather than inferred from completed activities.</p><p>And third, those improvements must be capable of enduring beyond the circumstances that originally produced them.</p><p>Estonia’s X-Road illustrates how governance arrangements can enable a technological intervention to continue developing beyond its original implementation.</p><p>Zambia’s Primary Reading Programme demonstrates how resource constraints, programme design, and institutional ownership can affect the sustainability of externally supported activities.</p><p>AstraZeneca’s experience suggests that organisations can move beyond maintaining improvements towards sustaining the capability to keep improving.</p><p>These cases do not share the same objectives, sectors, or operating environments. Nor do they establish that every successful transformation must follow a single model.</p><p>But they point towards a common principle.</p><p>An intervention should leave behind more than the immediate evidence of its own completion.</p><p>It should leave behind the conditions through which its benefits can continue.</p><p>A strategy may eventually become outdated. A technology may require replacing. Employees may move on, leadership may change, and the organisation may confront problems that nobody anticipated during implementation.</p><p>The ultimate question is whether it can respond.</p><p>Perhaps this is the most meaningful legacy of a successful intervention.</p><p>Not simply that the organisation performs better while external support is available.</p><p>But that it becomes better equipped to recognise problems, make decisions, mobilise resources, and adapt when circumstances change.</p><p><strong>The true test of transformation is not whether the organisation can continue doing what the consultants taught it to do. It is whether the organisation can decide what to do when those lessons are no longer enough.</strong></p><p>The consultants may have left.</p><p>The organisation should not have lost its ability to move forward.</p><h3>Author’s Note</h3><p>This is Part III of <em>The Value Paradox</em>, a three-part series examining how organisations define, realise, and sustain value across private enterprise, public institutions, and organisational transformation.</p><p>The interpretations presented here are my own, informed by published research, official documentation, and established thinking on sustainability, organisational learning, and capacity development.</p><p>The opening consulting scenario and hypothetical hospital examples are illustrative. The discussions of Estonia’s X-Road, Zambia’s Primary Reading Programme, and AstraZeneca’s Lean improvement programme draw on publicly documented cases. These interventions differ in nature and should not all be interpreted as conventional management-consulting engagements.</p><p>The distinction between sustaining improvements and sustaining the capacity to improve is drawn from the research of Bonnie Poksinska and Dag Swartling. The broader discussion of institutional ownership and capability is a synthesis of established ideas rather than a claim to an original academic framework.</p><p>The views expressed are personal and do not represent those of any organisation with which I am or have been associated.</p><h3>References &amp; Further Reading</h3><ol><li>OECD (2021). <em>Applying Evaluation Criteria Thoughtfully</em>. OECD Publishing. https://www.oecd.org/en/publications/applying-evaluation-criteria-thoughtfully_543e84ed-en.html</li><li>OECD-DAC (2019). <em>Better Criteria for Better Evaluation: Revised Evaluation Criteria Definitions and Principles for Use</em>. https://www.oecd.org/content/dam/oecd/en/publications/reports/2019/12/better-criteria-for-better-evaluation_f7a307eb/15a9c26b-en.pdf</li><li>Estonian Information System Authority. <em>Data Exchange Layer X-tee</em>. https://www.ria.ee/en/state-information-system/data-exchange-platforms/data-exchange-layer-x-tee</li><li>Nordic Institute for Interoperability Solutions. <em>History of NIIS</em> and <em>X-Road History</em>. https://www.niis.org/history and https://x-road.global/xroad-history</li><li>Kombe, C. L. M., &amp; Herman, C. (2017). <em>Can Education Innovations Be Sustained after the End of Donor Funding? The Case of a Reading Intervention Programme in Zambia</em>. Educational Review, 69(5), 533–553. https://doi.org/10.1080/00131911.2016.1265917</li><li>Poksinska, B., &amp; Swartling, D. (2018). <em>From Successful to Sustainable Lean Production: The Case of a Lean Prize Award Winner</em>. Total Quality Management &amp; Business Excellence, 29(9–10), 996–1011. https://doi.org/10.1080/14783363.2018.1486539</li></ol><p><em>The Value Paradox | End of Series</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bed507fb8da3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Illusion of Value Creation]]></title>
            <link>https://medium.com/@adamkureshi.hr/the-illusion-of-value-creation-f53b1512fbc1?source=rss-bc3ee0c84b4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f53b1512fbc1</guid>
            <category><![CDATA[value-creation]]></category>
            <category><![CDATA[management-consulting]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[organizational-change]]></category>
            <dc:creator><![CDATA[Adam Kureshi]]></dc:creator>
            <pubDate>Fri, 30 Oct 2026 20:31:01 GMT</pubDate>
            <atom:updated>2026-10-30T20:31:01.647Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The Value Paradox | Part II</em></p><p><em>Why completing the work is not the same as solving the problem.</em></p><p>There is a particular satisfaction that comes with completing a project.</p><p>The final deliverable has been submitted. The presentation has been approved. The system has gone live. The last milestone has been marked complete.</p><p>For the people responsible for delivery, these moments matter. They represent months, sometimes years, of effort.</p><p>But something curious happens when we begin treating these moments as evidence that the original problem has been solved.</p><p>A new system is not the same as a better service.</p><p>A completed strategy is not the same as improved decision-making.</p><p>And a trained workforce is not necessarily a workforce that behaves differently.</p><p>These distinctions seem obvious when stated plainly. Yet organisations continue to invest considerable resources in interventions whose success is judged primarily by whether the promised work was completed.</p><p>Perhaps the problem is not that organisations fail to create value.</p><p>Perhaps it is that they declare victory before discovering whether the value has actually emerged.</p><h3>The Comfort of Completion</h3><p>In the first article of <em>The Value Paradox</em>, I explored a deceptively difficult question: <a href="https://medium.com/@adamkureshi.hr/70acbbcc2281"><strong>Who decides what value is?</strong></a></p><p>Different stakeholders can examine the same intervention and arrive at different conclusions about its worth.</p><p>A funding organisation may focus on contractual commitments. An implementing partner may point to completed deliverables. An institution may assess whether its capabilities improved. The people receiving a service may be concerned with whether their experience actually became better.</p><p>These perspectives are not necessarily incompatible. But they do not always align.</p><p>This was the starting point for what I described as the <em>Value Disconnect</em>: the distinction between value promised, enabled, realised, and recognised.</p><p>But what happens when everyone agrees on what an intervention is supposed to achieve?</p><p>The business case is compelling. The investment is approved. The work is delivered according to plan.</p><p>Does that mean value has been created?</p><p>Not necessarily.</p><p>Completion tells us something important about delivery. It does not settle what happened because of that delivery.</p><p>And the problem extends beyond project management. It appears in the way businesses assess profitability, governments evaluate public investments, and institutions judge organisational transformation.</p><h3>When Profit Is Mistaken for Value</h3><p>In 2022, Shell reported approximately $42.3 billion in income attributable to shareholders.</p><p>It is an extraordinary figure by almost any ordinary standard.</p><p>But does earning more than $42 billion necessarily mean the company created an equivalent amount of economic value?</p><p>Not quite.</p><p>Profit tells us something important about financial performance. But it does not, by itself, establish whether the returns generated were sufficient to justify the capital committed to producing them.</p><p>Consider two hypothetical businesses.</p><p>The first generates $100 million in annual net operating profit after tax but requires $2 billion in invested capital.</p><p>The second generates $30 million but requires only $100 million.</p><p>The first appears more successful if we compare operating profits alone.</p><p>But its return on invested capital is 5%, compared with 30% for the second.</p><p>Now suppose both businesses have an estimated cost of capital of 10%.</p><p>The first earns less than its cost of capital. The second earns considerably more.</p><blockquote><em>Despite generating a larger operating profit, the first business earns a return below its assumed cost of capital, while the second generates returns comfortably above it.</em></blockquote><p>This is the logic behind <em>Return on Invested Capital</em> (ROIC) and the <em>Weighted Average Cost of Capital</em> (WACC).</p><p>ROIC measures operating returns relative to invested capital. WACC estimates the return required by those financing the business.</p><p>Their relationship helps establish whether a company is generating returns above the opportunity cost of the capital it employs.</p><p><strong>Economic value depends not only on what a business earns, but also on what it must commit to earn it.</strong></p><p>The hypothetical figures are illustrative, not estimates of Shell’s actual ROIC or WACC. Nor does Shell’s reported profit establish that it failed to create economic value.</p><p>But the example reveals a broader limitation of headline performance measures.</p><p>Even positive economic returns do not settle every question about value. Customers, employees, communities, and the environment may experience consequences that financial accounts do not fully capture.</p><p>An impressive result is not necessarily a complete account of value.</p><p>The same reasoning becomes relevant when organisations invest in transformation.</p><p>Instead of reporting billions in profit, they report systems deployed, strategies developed, employees trained, and milestones completed.</p><p>The numbers may be accurate.</p><p>But do they establish that the investment achieved what it was intended to achieve?</p><h3>When the Business Case Becomes a Delivery Plan</h3><p>Most organisational interventions begin with a promise.</p><p>A digital transformation programme will improve efficiency.</p><p>A new operating model will reduce duplication.</p><p>A consultancy engagement will strengthen performance.</p><p>A public-sector reform will improve access, accountability, or service quality.</p><p>These expectations form the basis of a business case.</p><p>The business case explains why resources should be committed, what benefits are expected, and how the proposed intervention compares with alternative uses of those resources.</p><p>In principle, it connects investment to anticipated value.</p><p>But once an initiative is approved, the organisation’s attention often shifts.</p><blockquote>The original question, “Why are we doing this?”, gradually gives way to a different set of questions.</blockquote><p>Are the deliverables on schedule?</p><p>Has the budget been utilised?</p><p>Have the required approvals been obtained?</p><p>Is implementation proceeding according to plan?</p><p>These are legitimate management concerns. Without them, even worthwhile initiatives can become expensive exercises in disorder.</p><p>The problem emerges when delivery indicators become substitutes for the benefits that justified the intervention.</p><p>Imagine a company investing in a customer relationship management system to improve retention.</p><p>The system is procured, configured, tested, and deployed. Employees receive training. Data is migrated.</p><p>The project closes.</p><p>But customer retention remains unchanged.</p><p>Perhaps employees are not using the system consistently. Perhaps the underlying service problems were never addressed. Perhaps the system provides better information, but nobody has changed how customer complaints are handled.</p><p>The intervention has created a capability.</p><p>It has not necessarily created the intended value.</p><p>A subtle shift in accountability has occurred.</p><p>During approval, the organisation asked whether the proposed investment would produce worthwhile benefits.</p><p>During implementation, it asked whether the promised solution was being delivered.</p><p>At closure, it answered the second question and treated it as though it had answered the first.</p><p><strong>The business case had effectively become a delivery plan, while the original value proposition remained untested.</strong></p><h3>The NHS Experience: When Delivery and Value Diverge</h3><p>One of the more revealing examples comes from England’s National Health Service.</p><p>Launched in 2002, the National Programme for IT was an ambitious effort to modernise healthcare information systems across the NHS.</p><p>Its objectives included improving the availability and use of patient information, developing electronic care records, and establishing digital infrastructure capable of supporting a more connected health system.</p><p>The proposition was compelling.</p><p>Better information could support clinical decisions, reduce duplication, improve coordination, and make services more efficient.</p><p>But delivering technology and realising those benefits proved to be different challenges.</p><p>In its 2011 assessment, the UK’s National Audit Office reported substantial delays in implementing detailed electronic care records.</p><p>It also found that systems deployed in acute hospitals had delivered mainly administrative benefits rather than the clinical benefits originally anticipated.</p><p>This distinction matters.</p><p>An administrative system may improve scheduling, record management, or other organisational processes. These can be valuable achievements in their own right.</p><p>But they do not automatically demonstrate improvements in clinical decision-making, patient outcomes, or the wider performance of healthcare services.</p><p>The programme also produced infrastructure with continuing practical value.</p><p>National services such as NHSmail, the Spine, and digital imaging capabilities formed part of the wider digital foundation developed during this period.</p><p>Describing the entire programme as a failure would therefore obscure meaningful achievements.</p><p>Yet describing it as a success simply because useful infrastructure was delivered would be equally incomplete.</p><p>The difficulty lies in the relationship between what was produced and what had originally been promised.</p><p>The financial evaluation reflected this uncertainty.</p><p>In its 2013 review, the National Audit Office examined Department of Health forecasts of approximately £10.7 billion in lifetime benefits against £9.8 billion in lifetime costs for programmes previously managed under the national initiative.</p><p>These were forecasts, not a final accounting of realised value.</p><p>A substantial proportion of the anticipated benefits remained in the future, and their eventual realisation was uncertain.</p><p><strong>Expected benefits are not the same as demonstrated benefits.</strong></p><p>A programme can have a credible rationale, produce useful assets, and still fall short of its original ambitions.</p><p>It can also create benefits that emerge unevenly, later than expected, or in forms different from those initially anticipated.</p><p>The NHS experience resists a simple success-or-failure narrative.</p><p>It asks us to distinguish what was delivered, what became operational, what changed in organisational practice, and what benefits were ultimately realised.</p><p>These questions are connected.</p><p>They are not interchangeable.</p><h3>The Value Realisation Gap</h3><p>One way of describing the distance between expected benefits and those ultimately realised is through the idea of a <em>Value Realisation Gap</em>.</p><p>The concept is not new. It has been explored through benefits realisation, investment appraisal, business analysis, and organisational change, including more recent discussions about the difficulty of translating projected financial gains into operational results.</p><p>What interests me is a particular dimension of this problem: how value can become diluted as responsibility moves through an organisation, even when the people involved are fulfilling their respective responsibilities.</p><p>Consider five connected stages.</p><h4>1. Promise: What Should Improve?</h4><p>An organisation identifies a problem or opportunity and establishes what it expects to achieve.</p><p>The promise might involve lower costs, better services, improved decision-making, stronger institutional capability, or reduced risk.</p><p>At this stage, value exists as an expectation supported by assumptions.</p><p>The first vulnerability is <strong>assumption risk</strong>.</p><p>The problem may have been diagnosed incorrectly. The projected benefits may be optimistic. The proposed intervention may not be the most effective use of available resources.</p><p>A well-written business case does not eliminate these uncertainties.</p><p>It makes them visible enough to examine.</p><h4>2. Delivery: What Has Been Created?</h4><p>The intervention produces something tangible.</p><p>A system is installed. A strategy is developed. A process is redesigned. Training is delivered.</p><p>These outputs may be necessary conditions for improvement.</p><p>But the second vulnerability is <strong>substitution risk</strong>.</p><p>As delivery progresses, the organisation may begin treating the existence of the solution as evidence that the underlying problem has been addressed.</p><p>The project produces what it promised to produce.</p><p>Whether that production was sufficient to create the intended improvement remains another question.</p><h4>3. Adoption: Is It Being Used?</h4><p>The organisation begins using what has been delivered.</p><p>Employees adopt the system. Managers apply the framework. Clinicians follow the revised procedure.</p><p>This introduces <strong>adoption risk</strong>.</p><p>People may resist the solution, lack the skills to use it, or find that it conflicts with their existing responsibilities.</p><p>Even where formal adoption occurs, usage may remain superficial.</p><p>A new reporting system may be populated because compliance requires it, while decisions continue to rely on informal information channels.</p><p>The organisation has adopted the tool without adopting the behaviour that would make it valuable.</p><h4>4. Change: Is Performance Improving?</h4><p>Adoption begins to alter how the organisation operates.</p><p>Decisions become faster. Errors decline. Coordination improves. Resources are used differently.</p><p>Here, the vulnerability becomes <strong>performance risk</strong>.</p><p>The new way of working may not produce the expected improvement.</p><p>A digital process may reproduce the inefficiencies of its paper predecessor.</p><p>A redesigned approval process may reduce the number of steps while increasing the workload associated with each one.</p><p>Or an improvement in one department may simply transfer costs and delays elsewhere.</p><p>Change has occurred.</p><p>But its consequences are not necessarily beneficial.</p><h4>5. Value: Was the Improvement Worthwhile?</h4><p>Finally, the organisation examines whether the changes produced worthwhile benefits relative to their costs, risks, and consequences.</p><p>Did the investment justify the resources committed?</p><p>Did intended beneficiaries experience meaningful improvement?</p><p>Were important costs or disadvantages shifted onto other stakeholders?</p><p>Were the benefits sustained long enough to matter?</p><p>This introduces <strong>value assessment risk</strong>.</p><p>An organisation may correctly identify improvements but evaluate them against an incomplete definition of value.</p><p>Financial savings may be achieved at the expense of service quality.</p><p>Higher productivity may coexist with employee exhaustion.</p><p>A successful intervention for one stakeholder may impose substantial costs on another.</p><p>The final assessment therefore requires more than confirming that something improved.</p><p>It requires examining whether the improvement was worthwhile, for whom, and under what conditions.</p><p>The five stages are not necessarily linear.</p><p>Adoption may reveal design problems that require further development. Benefits may emerge before implementation is complete. Some outcomes may become visible only after considerable time.</p><p>But the framework highlights a recurring problem.</p><p><strong>At every transition, anticipated value can be lost, delayed, reduced, or redirected.</strong></p><p>The Value Realisation Gap is not simply the difference between a target and a result.</p><p>It is also the accumulation of assumptions, dependencies, and decisions that determine whether an investment becomes a meaningful improvement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RUnb4MhauDp-7TM84pZA4Q.png" /><figcaption>The Value Realisation Gap: A five-stage synthesis illustrating how expected benefits can be lost, delayed, reduced, or redirected as responsibility moves from strategy to delivery, adoption, organisational change, and evaluation. Framework synthesis by the author; visual created with AI assistance.</figcaption></figure><h3>Where Value Gets Lost</h3><p>The five stages explain how value is expected to emerge.</p><p>But they also reveal something more interesting.</p><p>Value does not necessarily disappear because an intervention fails.</p><p>It can disappear because responsibility changes hands.</p><p>A strategy team develops a compelling business case. A project team takes responsibility for implementation. An operational department is expected to adopt the solution. Managers are expected to translate adoption into improved performance. Senior leadership eventually evaluates the results.</p><p>Each group may fulfil its immediate responsibilities.</p><p>Yet no single group may remain accountable for the complete journey.</p><p>This creates a distinction between <em>local success</em> and <em>collective value creation</em>.</p><p>Each team may be evaluated against objectives that are reasonable within its own area of responsibility. The difficulty arises when those objectives are not connected to an enduring responsibility for the original benefits.</p><p>In such circumstances, an organisation does not necessarily suffer from a lack of accountability. It may have plenty of accountability, but directed towards different measures of success.</p><p>The strategy team can demonstrate that the investment was justified by a credible forecast.</p><p>The project team can demonstrate that the solution was delivered.</p><p>The operational department can demonstrate that staff received training.</p><p>Managers can demonstrate that the new process is being followed.</p><p>And leadership may receive a dashboard showing that every major milestone has been achieved.</p><p>Each statement can be accurate.</p><p><strong>The problem is that their collective accuracy does not necessarily establish that value has been created.</strong></p><p>This is what makes the illusion difficult to detect.</p><p>It does not always depend on misleading information or poor intentions.</p><p>It can emerge from an accountability structure in which each participant is rewarded for completing a different part of the journey.</p><p>The evidence accumulates.</p><p>The original question disappears.</p><h3>Why Good Projects Can Produce Disappointing Outcomes</h3><p>It is tempting to explain unsuccessful transformations through poor project management.</p><p>Sometimes, that explanation is justified.</p><p>Projects may suffer from inadequate planning, unrealistic budgets, weak governance, or technical problems.</p><p>But delivery failure is only one possibility.</p><p>A technically successful project can still produce disappointing outcomes.</p><p>Consider a hospital introducing an electronic medical record system.</p><p>The software works. The servers are operational. Users have been trained.</p><p>From a technical perspective, implementation may be successful.</p><p>But clinicians might find the system difficult to navigate.</p><p>Data entry could consume additional consultation time.</p><p>Departments may continue maintaining parallel paper records.</p><p>Critical information may remain inaccessible because the system does not communicate with other applications.</p><p>The technology has been delivered.</p><p>But the operating environment has not necessarily changed in the way the organisation intended.</p><p>This is why implementation requires more than installation.</p><p>It depends on the interaction between technology, people, processes, incentives, and institutional capacity.</p><p>There is also the question of how much change an organisation can realistically absorb. Even a well-designed intervention may struggle when employees are expected to adopt multiple reforms while maintaining their existing responsibilities and service commitments.</p><p>A system designed around an ideal workflow may struggle in an organisation whose actual practices are considerably more complicated.</p><p>A reform that assumes staff have sufficient time, resources, and authority may fail when those conditions are absent.</p><p>A strategy that requires coordination across departments may remain ineffective if those departments have competing priorities.</p><p>In such cases, the intervention may not be inherently flawed.</p><p>The organisation may simply lack the conditions required to realise its potential.</p><p>This raises a question that business cases often acknowledge but implementation plans can underestimate:</p><p><strong>What must the organisation become capable of doing for the promised benefits to materialise?</strong></p><p>Without an answer, delivery risks becoming an expensive exercise in creating unused potential.</p><h3>When the Numbers Tell Only Half the Story</h3><p>If delivery indicators are insufficient, the obvious response is to measure outcomes.</p><p>But even outcome measurement requires care.</p><p>Imagine a public hospital introducing an appointment management system.</p><p>After implementation, average waiting time falls from 90 minutes to 55 minutes.</p><p>That is a meaningful improvement.</p><p>But what caused it?</p><p>Was it the new system?</p><p>Did patient volumes decline?</p><p>Were additional clinicians recruited?</p><p>Did the hospital change its operating hours?</p><p>Or did several factors contribute?</p><p>This is the problem of attribution.</p><p>A change occurring after an intervention is not necessarily a change caused by that intervention.</p><p>A rigorous assessment should consider the baseline, relevant external influences, and, where feasible, what might have happened without the intervention.</p><p>There is also the problem of unintended consequences.</p><p>Suppose a department is evaluated primarily on the number of applications it processes each day.</p><p>Staff may become faster at completing routine cases while spending less time on complex applications.</p><p>The headline productivity indicator improves.</p><p>But applicants with more complicated needs may experience longer delays or poorer service.</p><p>The indicator has captured one dimension of performance while obscuring another.</p><p>These problems do not make measurement pointless.</p><p>They make measurement a matter of judgement.</p><p>A useful performance framework should connect activities to outcomes, examine competing explanations, and consider whether improvement in one area has created costs elsewhere.</p><p>It should also distinguish between leading indicators and realised benefits.</p><p>System adoption rates, training completion, and workflow compliance may provide early evidence that an intervention is progressing.</p><p>But they are not substitutes for examining whether the intended improvements have emerged.</p><p><strong>A good indicator tells us something important. A poor interpretation asks it to tell us everything.</strong></p><h3>Who Owns the Benefit?</h3><p>The problem becomes especially visible when we ask a question that project governance does not always answer clearly.</p><p>Who is responsible for ensuring that the benefits actually materialise?</p><p>A project manager may be accountable for implementing a system.</p><p>A consultant may be responsible for producing recommendations.</p><p>A technology vendor may be contracted to deliver specified functionality.</p><p>But the intended benefits often depend on decisions made by people outside the delivery team.</p><p>A department head may need to redesign workflows.</p><p>Supervisors may need to reinforce new practices.</p><p>Finance teams may need to adjust resource allocations.</p><p>Senior leadership may need to resolve institutional constraints.</p><p>If these responsibilities are not clearly assigned, the organisation can find itself in a peculiar position.</p><p>The project has an owner.</p><p>The deliverables have been accepted.</p><p>The implementation has been declared complete.</p><p><strong>But the benefits have no clear owner.</strong></p><p>This is not merely an administrative oversight.</p><p>It reflects a deeper separation between those responsible for delivering change and those responsible for making that change valuable.</p><p>The distinction is especially important in consultancy and technical assistance engagements.</p><p>External specialists can diagnose problems, develop frameworks, introduce tools, and support implementation.</p><p>But many of the benefits depend on what the receiving organisation subsequently does.</p><p>If responsibility for those benefits is unclear, it becomes difficult to determine whether an intervention is progressing, whether corrective action is required, or who has the authority to make those corrections.</p><p>A more useful approach would assign benefit ownership alongside delivery responsibilities.</p><p>For every major expected improvement, the organisation should be able to identify who is accountable for achieving it, what conditions are necessary, how progress will be assessed, and when the results are expected to become visible.</p><p>This does not guarantee success.</p><p>But it reduces the likelihood that a completed project will be mistaken for a completed transformation.</p><h3>From Deliverables to Demonstrable Improvement</h3><p>What would change if organisations treated value realisation as seriously as project delivery?</p><p>The first difference would appear before an intervention begins.</p><p>Rather than defining success primarily through activities and deliverables, organisations would establish what should improve and how they intend to recognise that improvement.</p><p>A digital system would not be justified solely by its functionality.</p><p>Its business case would explain what decisions, processes, or services the system is expected to improve.</p><p>A training programme would not be evaluated only through attendance and satisfaction.</p><p>It would examine whether participants acquired relevant capabilities and whether those capabilities influenced subsequent practice.</p><p>A consultancy engagement would distinguish between the successful completion of its contractual scope and the longer-term organisational improvements that motivated the engagement.</p><p>These distinctions also require realistic expectations.</p><p>Not every intervention can be held accountable for outcomes beyond its influence.</p><p>A consultant cannot guarantee that a client will implement recommendations. A technology vendor cannot control every aspect of organisational adoption. A training provider cannot independently determine whether managers reinforce newly acquired skills.</p><p>But the limitations of direct control should be made explicit rather than allowing responsibility for value to disappear altogether.</p><p>The second difference would be in how organisations monitor progress.</p><p>Instead of waiting until the end of a project to ask whether it succeeded, they would examine the assumptions connecting delivery to expected benefits.</p><p>Are users adopting the solution?</p><p>Are the intended operational changes occurring?</p><p>Are the benefits emerging at the expected rate?</p><p>What unintended consequences are becoming visible?</p><p>And what needs to change if the original assumptions prove incorrect?</p><p>This turns evaluation from a retrospective judgement into an ongoing management responsibility.</p><p>The third difference concerns honesty about uncertainty.</p><p>Business cases are built on assumptions about the future.</p><p>Some assumptions will prove correct.</p><p>Others will not.</p><p>An organisation committed to value creation should be willing to revise its expectations when evidence changes.</p><p>Sometimes, that means redesigning an intervention.</p><p>Sometimes, it means extending support.</p><p>And sometimes, it means acknowledging that the original investment is unlikely to deliver sufficient benefit to justify continued expenditure.</p><p>The purpose of evaluation should not be to protect the original business case.</p><p>It should be to improve the decisions that follow.</p><h3>The Unfinished Transformation</h3><p>I began this article with the satisfaction of completing a project.</p><p>The final presentation, the approved strategy, the operational system, and the completed milestone all provide tangible evidence that work has been done.</p><p>And that evidence matters.</p><p>Without delivery, many improvements would never become possible.</p><p>But possibility is not the same as achievement.</p><p>Shell’s financial results illustrate why an impressive profit figure cannot, on its own, establish economic value without considering the capital required to generate it.</p><p>The NHS experience illustrates why substantial investment and useful digital infrastructure do not automatically establish that the wider benefits of a transformation have been realised.</p><p>Different sectors. Different objectives. Different methods of evaluation.</p><p>Yet a common analytical problem remains.</p><p><strong>We often become so focused on demonstrating what has been produced that we give insufficient attention to what that production was supposed to make possible.</strong></p><p>Perhaps the real test of an intervention begins when the delivery team announces that its work is complete.</p><p>Does the organisation use what has been created?</p><p>Does that use change how it operates?</p><p>Do those changes produce worthwhile benefits?</p><p>And does anyone remain accountable for finding out?</p><p>These questions do not diminish the importance of completing projects.</p><p>They remind us that completion and value are not interchangeable.</p><p>The distinction also leads to a more uncomfortable question.</p><p>Even when an intervention does produce meaningful benefits, what happens after the consultants, project teams, or external specialists leave?</p><p>Can the organisation preserve those improvements?</p><p>Can it adapt them?</p><p>Can it continue creating value without the people who helped initiate the change?</p><p>Because creating value once is one achievement.</p><p><strong>Building an organisation capable of sustaining it is another.</strong></p><h3>Author’s Note</h3><p><em>This is Part II of </em><strong><em>The Value Paradox</em></strong><em>, a three-part series examining how organisations define, create, demonstrate, and sustain value across private enterprise, public institutions, and organisational transformation.</em></p><p><em>The reflections and interpretations presented here are my own, informed by professional observations, established research, and published evidence. Organisational examples are hypothetical unless otherwise identified. They are intended to illustrate broader systems challenges rather than comment on any particular organisation, project, or individual.</em></p><p><em>The five-stage framework presented in this article is my own synthesis of established ideas in benefits realisation, investment appraisal, organisational change, and business analysis. The term Value Realisation Gap and the broader distinction between anticipated and realised benefits are already present in professional literature. My interpretation focuses particularly on how fragmented accountability can obscure whether intended value has materialised.</em></p><p><em>The views expressed are personal and do not represent those of any organisation with which I am or have been associated.</em></p><h3>References &amp; Further Reading</h3><ol><li><strong>Shell plc (2023).</strong> <em>Fourth Quarter 2022 and Full Year Results.</em> Financial results reporting income attributable to shareholders of approximately $42.3 billion for 2022.</li><li><strong>Shell plc (2024).</strong> <em>Annual Report and Accounts 2023.</em> Financial performance, capital employed, and return measures.</li><li><strong>National Audit Office (2011).</strong> <em>The National Programme for IT in the NHS: An Update on the Delivery of Detailed Care Records Systems.</em></li><li><strong>National Audit Office (2013).</strong> <em>Review of the Final Benefits Statement for Programmes Previously Managed Under the National Programme for IT in the NHS.</em></li><li><strong>International Institute of Business Analysis (2015).</strong> <em>A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3.</em> Particularly the Solution Evaluation knowledge area.</li><li><strong>Marhelski, W. (2025).</strong> <em>The Value Realization Gap.</em> LinkedIn, 3 December 2025. https://www.linkedin.com/pulse/value-realization-gap-wayne-marhelski-tbvyc/</li></ol><p><strong>Next in the series:</strong> <em>What Remains When the Consultants Leave?</em></p><p><em>Why lasting transformation depends on what organisations can do without external support.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f53b1512fbc1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who Decides What Value Is?]]></title>
            <link>https://medium.com/@adamkureshi.hr/who-decides-what-value-is-70acbbcc2281?source=rss-bc3ee0c84b4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/70acbbcc2281</guid>
            <category><![CDATA[organizational-change]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[management-consulting]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <dc:creator><![CDATA[Adam Kureshi]]></dc:creator>
            <pubDate>Sat, 24 Oct 2026 13:01:02 GMT</pubDate>
            <atom:updated>2026-10-30T20:37:08.555Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The Value Paradox | Part I</em></p><p><em>Why organisational success depends on more than the results we report.</em></p><p>I remember a conversation with a colleague that began with a deceptively simple question:</p><p><strong>What constitutes success?</strong></p><p>The discussion soon turned into a debate about impact and outcomes. What distinguishes one from the other? Must an outcome take two or three years to materialise? And at what point does a change become significant enough to be considered an impact?</p><p>Eventually, we worked our way backwards to outputs, the more immediate and tangible products of an intervention.</p><p>But the further we explored these distinctions, the more interesting the question became.</p><p>If an organisation delivers everything it promised, has it succeeded? If those outputs produce measurable outcomes, is that sufficient? And if those outcomes eventually contribute to a broader impact, does that settle the question?</p><p>Somewhere in the discussion, we arrived at something more fundamental.</p><p><strong>Where, in this progression from outputs to outcomes and impact, does value actually emerge?</strong></p><p>It seemed like a natural extension of our conversation. Yet the more I thought about it, the less straightforward the answer appeared.</p><p>Organisations have developed elaborate ways of measuring what they do and what changes as a result.</p><p>But determining whether those changes are genuinely valuable is an altogether different exercise.</p><p>And perhaps that is where our understanding of success begins to become complicated.</p><h3>When Measurement Becomes Meaning</h3><p>Organisations like things they can measure.</p><p>Projects have milestones. Companies have performance targets. Government departments have reporting obligations. Development programmes have results frameworks.</p><p>These mechanisms are necessary. They help organisations allocate resources, monitor progress, and demonstrate accountability.</p><p>But they can also influence what organisations understand success to mean.</p><p>The OECD’s <em>Glossary of Key Terms in Evaluation and Results-Based Management for Sustainable Development</em> (2023) provides a useful starting point for distinguishing outputs, outcomes, and impacts.</p><p>In simplified terms, outputs are the products or services an intervention generates. Outcomes concern changes to which those outputs contribute, while impacts refer to broader, significant effects.</p><p>Time is relevant. Some changes become visible quickly; others require years to emerge. But a reporting horizon is not, by itself, sufficient to explain the nature or significance of a result.</p><p>Imagine a hospital introducing a new patient referral process.</p><p>The guidelines are developed. Staff members are trained. A revised procedure is introduced.</p><p>These are outputs.</p><p>Within a few weeks, clinicians begin following the process. Unnecessary referrals decline, and patients experience shorter waiting times.</p><p>These are potential outcomes, provided the changes can reasonably be linked to the intervention.</p><p>They do not become outcomes simply because a predetermined reporting period has elapsed.</p><p>But even this distinction leaves another problem.</p><p>Suppose the hospital reduces average consultation time by 30%.</p><p>Management might regard this as an improvement in efficiency.</p><p>Yet imagine that shorter consultations lead to missed symptoms, unresolved concerns, and more repeat visits.</p><p>The hospital has improved one indicator while potentially making the overall service worse.</p><p>The reported change may be real. Its value is questionable.</p><p><strong>An outcome tells us what changed. Value asks whether that change was worthwhile.</strong></p><p>And that distinction takes us beyond measurement into something considerably more complicated.</p><h3>The Same Intervention, Different Definitions of Success</h3><p>Consider a private hospital investing in a new inventory management system.</p><p>Executive leadership expects lower operating costs and improved working capital.</p><p>The finance department wants fewer expired medicines and emergency purchases.</p><p>Clinical staff want essential supplies to be available when patients need them.</p><p>Patients want reliable treatment without unnecessary delays or additional purchases.</p><p>Everyone is evaluating the same investment.</p><p>But they are not necessarily evaluating the same benefit.</p><p>A system that reduces inventory costs by keeping stock levels extremely low might satisfy financial targets while increasing the risk of shortages.</p><p>Conversely, maintaining additional stocks of critical medicines may appear inefficient from a narrow financial perspective while improving the hospital’s ability to deliver safe care.</p><p>Neither perspective is automatically wrong.</p><p>They are concerned with different consequences.</p><p>Now consider a public institution receiving technical assistance to improve its operations.</p><p>A funding organisation may focus on agreed objectives, accountability, and responsible expenditure.</p><p>An implementing partner may assess whether the required technical outputs were delivered.</p><p>Government leadership may judge the intervention against institutional priorities.</p><p>Frontline officials may be concerned with whether the proposed changes are practical.</p><p>Citizens may only experience value if public services become more accessible, reliable, or effective.</p><p>Again, one intervention. Several legitimate interpretations of success.</p><p>This is not simply a disagreement about performance indicators.</p><p>It reflects a more fundamental question:</p><p><strong>Value for whom?</strong></p><h3>Creating Value Is Not the Same as Capturing It</h3><p>In private enterprise, value is frequently discussed through profitability, productivity, growth, and competitive advantage.</p><p>These are essential considerations. A business must generate sufficient economic returns to remain viable.</p><p>But financial success does not necessarily provide a complete account of the value an organisation creates.</p><p>A company may increase profits by improving productivity, developing a better product, or reducing waste.</p><p>It may also increase profits by reducing service quality, transferring costs to suppliers, or taking advantage of customers who have limited alternatives.</p><p>Both approaches may improve financial performance.</p><p>Their wider consequences are very different.</p><p>This distinction connects to R. Edward Freeman’s <em>Strategic Management: A Stakeholder Approach</em> (1984), which helped establish stakeholder theory as an influential perspective on organisational strategy.</p><p>Freeman’s work draws attention to the relationships between organisations and the various groups that affect or are affected by their decisions.</p><p>Customers, employees, investors, suppliers, and communities do not necessarily experience organisational success in the same way.</p><p>A business may capture additional financial value without creating an equivalent improvement for its customers or wider stakeholders.</p><p>Public institutions face a related challenge, although their purposes differ.</p><p>A government hospital is not ordinarily established to maximise profit. Its responsibilities may include improving access, delivering safe care, protecting vulnerable populations, and using public resources responsibly.</p><p>A service may be expensive while generating substantial social benefits.</p><p>Equally, a programme may remain within budget while failing to address the needs it was established to serve.</p><p>Mark H. Moore’s <em>Creating Public Value: Strategic Management in Government</em> (1995) offers an influential perspective on this problem.</p><p>Moore’s approach considers public value alongside legitimacy, support, and operational capacity. Public institutions must pursue worthwhile objectives, secure the authority and support necessary to act, and possess the capability to deliver.</p><p>The distinction between private and public value is important, but it is not absolute.</p><p>Businesses must consider relationships, legitimacy, and long-term consequences. Public institutions must consider costs, efficiency, and the practical use of scarce resources.</p><p>Both can become exceptionally good at demonstrating performance against internal measures without necessarily improving what matters most to those they serve.</p><h3>When Everyone Can Claim Success</h3><p>Imagine a consultancy engaged by a manufacturing company to improve productivity.</p><p>The consultants conduct an assessment, identify bottlenecks, redesign workflows, and submit an implementation roadmap.</p><p>The client accepts the deliverables. The engagement closes successfully.</p><p>Six months later, productivity remains unchanged.</p><p>Was the consultancy successful?</p><p>If its responsibility was limited to diagnosis and recommendations, it may have fulfilled the contract.</p><p>But if the purpose of commissioning the work was to improve productivity, the absence of improvement still demands an explanation.</p><p>Perhaps management never implemented the recommendations. Perhaps the proposed changes were impractical. Perhaps the organisation lacked the resources required to act.</p><p>These explanations matter because they point to different problems.</p><p>Contractual completion is not necessarily evidence of organisational improvement.</p><p>Nor does the absence of improvement automatically establish that the consultants failed.</p><p>Now imagine a government department receiving support to strengthen institutional planning.</p><p>A framework is developed. Procedures are documented. Employees attend training.</p><p>Yet the department continues to operate much as it did before.</p><p>Again, several explanations are possible.</p><p>The assistance may have addressed the wrong problem. The recommendations may not have been adopted. Institutional constraints may have prevented implementation.</p><p>Or the intervention may have created capabilities whose benefits are not yet visible.</p><p>Simply counting completed deliverables cannot distinguish between these possibilities.</p><p>The distinction between producing work and demonstrating improvement is not unique to consultancy engagements. It is relevant to digital transformation, organisational reform, public programmes, and almost any initiative intended to change how an institution performs.</p><p>The International Institute of Business Analysis makes a useful distinction in its <em>Business Analysis Body of Knowledge (BABOK Guide), Version 3</em>, particularly within its Solution Evaluation knowledge area.</p><p>Evaluating a solution involves more than establishing whether it performs as intended. It also requires examining the value delivered, identifying limitations, and considering opportunities for improvement.</p><p>A technically functioning solution may still fall short of its potential.</p><p>The difficulty, then, is not always that organisations lack methods for evaluating value.</p><p>Sometimes, it is that the people commissioning, implementing, using, and judging an intervention do not share the same understanding of what that value should be.</p><h3>When the Evidence Cannot Tell Us What Changed</h3><p>This distinction is not merely theoretical.</p><p>In its <em>Results and Performance of the World Bank Group 2025</em>, the World Bank’s Independent Evaluation Group examined the effectiveness of advisory and analytical services.</p><p>These activities can include research, technical advice, policy analysis, and institutional support intended to inform decisions and strengthen capabilities.</p><p>The evaluation examined thousands of such activities and identified a significant weakness in how their results were documented.</p><p>It reported that approximately 40% of completion summaries did not discuss results achieved in their intended outcome areas.</p><p>That finding deserves careful interpretation.</p><p>It does not mean that 40% of those interventions failed.</p><p>It means that the completion reporting did not establish whether the intended changes had occurred.</p><p>The evaluation also highlighted the difficulty of assessing advisory work at the point of completion, when its influence on institutional decisions and practices may only become visible later.</p><p>This creates an important distinction.</p><p>An organisation may successfully deliver the work it was commissioned to produce while remaining unable to demonstrate whether that work achieved its underlying purpose.</p><p>Equally, an intervention may create genuine benefits that its evaluation system is not equipped to capture.</p><p><strong>The absence of demonstrated value is not necessarily evidence that value was absent.</strong></p><p>Sometimes, the disconnect lies not in the intervention itself, but in the relationship between what was delivered, what changed, and what the organisation was capable of recognising.</p><h3>The Value Disconnect</h3><p>I have come to think of this as the <em>Value Disconnect</em>.</p><p>It describes situations in which the value an intervention promises, the capabilities it enables, the benefits it produces, and the value stakeholders recognise do not fully align.</p><p>Four questions help make the disconnect visible.</p><h4>1. What value was promised?</h4><p>Every intervention begins with an expectation.</p><p>A company invests in automation to improve productivity. A hospital introduces a system to strengthen patient safety. A government department receives technical assistance to improve institutional performance.</p><p>But expectations are often expressed in broad terms.</p><p><em>Efficiency. Transformation. Capacity building. Institutional strengthening.</em></p><p>These may be legitimate objectives. Yet without a clear explanation of what should improve, and for whom, success becomes difficult to evaluate.</p><h4>2. What value was enabled?</h4><p>An intervention may create a capability without immediately producing the intended benefit.</p><p>A consultancy develops an operating model. A hospital acquires an information system. A government department receives a planning framework.</p><p>These achievements may be necessary.</p><p>But they represent opportunities for improvement, not necessarily realised improvements.</p><p>A system can be installed without being adopted. A framework can be approved without influencing decisions. Training can be delivered without changing behaviour.</p><h4>3. What value was realised?</h4><p>This is where we examine actual consequences.</p><p>Did productivity improve? Did costs decline without compromising quality? Did patients receive better care? Did the institution become more responsive?</p><p>We also need to consider who benefited and who incurred additional costs.</p><p>An intervention that improves one department’s efficiency by transferring substantial work to another may produce a smaller overall benefit than its headline indicators suggest.</p><h4>4. What value was recognised?</h4><p>Finally, we must examine how stakeholders interpret the results.</p><p>An intervention may produce genuine benefits that some stakeholders do not acknowledge.</p><p>It may also receive enthusiastic support despite limited evidence of meaningful improvement.</p><p>Recognition is influenced by expectations, incentives, experience, and institutional priorities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D06ipqKm6ublgLiJwY6rmQ.png" /><figcaption>The Value Disconnect: Four dimensions of organisational value. Framework by the author; visual created with AI assistance.</figcaption></figure><p>The four dimensions are connected, but they do not necessarily progress in a neat sequence.</p><p>Stakeholder expectations can influence adoption. Early experiences can alter perceptions. Recognition may emerge before benefits have been properly demonstrated.</p><p>The Value Disconnect is not a new theory of benefits realisation.</p><p>Established approaches already distinguish expected benefits from achieved results and recognise the importance of organisational conditions.</p><p>What interests me is another dimension of the problem: <strong>the possibility that the people who define value, enable its creation, experience its consequences, and judge its worth are not the same people.</strong></p><p>The resulting disagreements are not always failures of measurement.</p><p>Sometimes, they arise because stakeholders are answering different questions about the same intervention.</p><p>That is the disconnect the framework is intended to make visible.</p><h3>Why Recognition Matters</h3><p>There is a temptation to treat stakeholder satisfaction as the final verdict on whether an intervention has created value.</p><p>If the intended recipient does not consider it useful, surely it has failed.</p><p>But perception and value are not necessarily identical.</p><p>Consider a new reporting system introduced in a public institution.</p><p>Frontline employees may regard it as an administrative burden. Management may value the improved visibility it provides. Citizens may benefit indirectly if the information leads to better services.</p><p>The system could generate genuine improvements while also imposing unreasonable demands on employees.</p><p>Both observations may be true.</p><p>Michael Lipsky’s <em>Street-Level Bureaucracy</em> (1980) offers an important perspective on why organisational changes do not simply move from policy to practice exactly as intended.</p><p>Lipsky examined how frontline public servants exercise discretion under conditions of limited resources, heavy workloads, and competing demands.</p><p>His work reminds us that implementation takes place within institutional realities, not idealised organisational charts.</p><p>Resistance may reflect legitimate concerns about feasibility and workload.</p><p>It may also reflect incentives to preserve established arrangements.</p><p>Neither possibility should be assumed without investigation.</p><p>Equally, strong institutional support does not guarantee that an intervention creates meaningful value.</p><p>A project may be popular with senior leadership, meet its milestones, and receive positive feedback while producing limited improvement for its intended beneficiaries.</p><p><strong>Stakeholder perceptions are important evidence, but they are not substitutes for examining actual consequences.</strong></p><p>The challenge is to take people’s experiences seriously without assuming that any single perspective provides the complete picture.</p><h3>Who Has the Authority to Define Value?</h3><p>This brings us to a question that is often less visible than the performance indicators themselves.</p><p><strong>Who gets to decide what counts as success?</strong></p><p>In a private company, executives may approve investments and establish performance targets.</p><p>Employees may have limited influence over those decisions, even though they are responsible for implementing the changes.</p><p>Customers may experience the consequences without participating in the original discussion.</p><p>In public institutions, the distribution of authority can be even more complicated.</p><p>Political leadership, government departments, funding organisations, implementing partners, frontline workers, and citizens may all have legitimate interests.</p><p>But they do not necessarily have equal influence.</p><p>Some control resources. Others control administrative approvals. Some define reporting requirements. Others carry the responsibility for implementation.</p><p>And the people most affected by an intervention may have the least influence over how its success is defined.</p><p>This creates a distinction between those who <strong>define value</strong>, those who <strong>authorise or enable its creation</strong>, and those who <strong>experience its consequences</strong>.</p><p>These groups may overlap.</p><p>But when they do not, disagreement becomes more likely.</p><p>Consider a public-sector reform that improves administrative efficiency but reduces access for communities that are already underserved.</p><p>From one perspective, the intervention has succeeded.</p><p>From another, it has failed.</p><p>Resolving that disagreement requires more than selecting a preferred indicator.</p><p>It requires examining the institution’s purpose, legal obligations, resource constraints, and the distribution of benefits and burdens.</p><p>Value is therefore not simply a technical question.</p><p>It is also a question of legitimacy, authority, and whose interests are considered when decisions are made.</p><h3>Not Everything Valuable Is Easily Measured</h3><p>Some forms of value are relatively straightforward to demonstrate.</p><p>Procurement savings can be calculated. Processing times can be measured. Production capacity can be counted.</p><p>Other forms are more difficult.</p><p>What is the value of institutional trust?</p><p>How should an organisation assess improved decision-making capability?</p><p>What is the benefit of a public health institution becoming better prepared for an emergency that may never occur?</p><p>These questions are difficult, but they are not necessarily less important.</p><p>Even private businesses depend on benefits that do not immediately appear as profit.</p><p>Customer trust can influence retention. Employee capability can improve adaptability. Better processes can reduce operational risk.</p><p>Public institutions may generate value by improving resilience, accountability, equity, or preparedness.</p><p>The benefits may emerge slowly or be distributed across groups.</p><p>But difficulty in measurement should not become an excuse for avoiding evaluation.</p><p>If an organisation claims to have strengthened institutional capability, we should be able to ask what the institution can now do that it could not do before.</p><p>If a company claims to have improved customer experience, we should examine what customers actually experienced.</p><p>If a public programme claims to have strengthened service delivery, we should investigate changes in access, quality, responsiveness, or outcomes.</p><p>Not every benefit needs to be converted into money.</p><p>But claims of value should be open to examination.</p><h3>The Question Behind Every Intervention</h3><p>Organisations frequently begin initiatives by asking what needs to be done.</p><p>What systems should be introduced?</p><p>What processes should be redesigned?</p><p>What frameworks should be developed?</p><p>What training should be delivered?</p><p>These are legitimate questions.</p><p>But they concern the means through which improvement is expected to occur.</p><p>They do not necessarily establish why that improvement matters.</p><p>A more useful starting point might be:</p><p><strong>What should become better, for whom, and how would we recognise that improvement?</strong></p><p>This question does not eliminate disagreement.</p><p>Businesses face financial constraints. Employees have legitimate interests. Customers value different aspects of service. Public institutions must balance efficiency, equity, access, and accountability.</p><p>Not every decision can benefit everyone equally.</p><p>But defining intended value makes these trade-offs visible.</p><p>It also helps prevent an organisation from becoming so absorbed in delivering an intervention that it loses sight of why the intervention was undertaken.</p><p>Because once resources are committed, project teams established, and reporting mechanisms introduced, activity develops a momentum of its own.</p><p>Meetings continue. Reports accumulate. Milestones are completed.</p><p>And the original question, <em>what are we trying to make better?</em>, can quietly disappear behind the work being done.</p><h3>From Defining Value to Demonstrating It</h3><p>There is something reassuring about a completed project.</p><p>It has a beginning and an end. It produces tangible evidence of effort. It allows organisations to demonstrate that commitments were fulfilled.</p><p>Value is less accommodating.</p><p>It may emerge slowly. It may be distributed unevenly. It may depend on decisions made long after the original intervention concludes.</p><p>Sometimes, despite considerable effort and expenditure, it may never materialise at all.</p><p>This is not an argument against consulting, technical assistance, digital transformation, or institutional reform.</p><p>These interventions can produce substantial benefits.</p><p>It is an argument for being more precise about what those benefits are supposed to be, and more curious about whether they have actually emerged.</p><p>I find myself returning to the conversation that started this line of thinking.</p><p>We began by discussing success, moved into impact and outcomes, and worked our way back to outputs.</p><p>But the most important question was not where one category ended and another began.</p><p>It was whether the changes we were discussing had made anything meaningfully better.</p><p>Perhaps the question is not simply whether an organisation has created value.</p><p>It is what kind of value was created, for whom, at whose expense, and according to whose definition of success.</p><p>Because organisations do not merely disagree about whether change has worked.</p><p>Sometimes, they disagree about what the change was supposed to accomplish in the first place.</p><p>And even when that disagreement is resolved, another problem remains.</p><p><strong>How do we know that the promised value actually materialised?</strong></p><p>That is where the distinction between delivering work and creating value becomes impossible to ignore.</p><h3>Author’s Note</h3><p><em>This is Part I of </em><strong><em>The Value Paradox</em></strong><em>, a three-part series examining how organisations define, create, demonstrate, and sustain value across private enterprise, public institutions, and organisational transformation.</em></p><p><em>The reflections and interpretations presented here are my own, informed by professional observations, established research, and published evidence. Organisational examples are hypothetical unless otherwise identified. They are intended to illustrate broader systems challenges rather than comment on any particular organisation, project, or individual.</em></p><p><em>The Value Disconnect is an author-developed conceptual framework that draws on established ideas in stakeholder theory, public value, business analysis, and benefits realisation.</em></p><p><em>Any views expressed are personal and do not represent those of any organisation with which I am or have been associated.</em></p><h4>References &amp; Further Reading</h4><ol><li><strong>OECD (2023).</strong> <em>Glossary of Key Terms in Evaluation and Results-Based Management for Sustainable Development.</em> OECD Publishing.</li><li><strong>Freeman, R. E. (1984).</strong> <em>Strategic Management: A Stakeholder Approach.</em> Pitman.</li><li><strong>Moore, M. H. (1995).</strong> <em>Creating Public Value: Strategic Management in Government.</em> Harvard University Press.</li><li><strong>International Institute of Business Analysis (2015).</strong> <em>A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3.</em></li><li><strong>World Bank Independent Evaluation Group (2025).</strong> <em>Results and Performance of the World Bank Group 2025.</em></li><li><strong>Lipsky, M. (1980).</strong> <em>Street-Level Bureaucracy: Dilemmas of the Individual in Public Services.</em> Russell Sage Foundation.</li></ol><p><strong>Next in the series:</strong> <a href="https://medium.com/@adamkureshi.hr/the-illusion-of-value-creation-f53b1512fbc1"><em>The Illusion of Value Creation</em></a></p><p><em>Why completing the work is not the same as solving the problem.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70acbbcc2281" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our Baby Was the Patient. But Were We Part of the Care?]]></title>
            <link>https://medium.com/@adamkureshi.hr/our-baby-was-the-patient-but-were-we-part-of-the-care-4d10f163a050?source=rss-bc3ee0c84b4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d10f163a050</guid>
            <category><![CDATA[patient-experience]]></category>
            <category><![CDATA[patient-centered-care]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[parenting]]></category>
            <category><![CDATA[healthcare-management]]></category>
            <dc:creator><![CDATA[Adam Kureshi]]></dc:creator>
            <pubDate>Sat, 03 Oct 2026 13:01:02 GMT</pubDate>
            <atom:updated>2026-10-03T13:01:02.403Z</atom:updated>
            <content:encoded><![CDATA[<p><em>What our newborn daughter’s phototherapy taught me about separation, family-centred care and who hospitals consider part of the care process.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*179J_ixS5bC-q4ZpJFHOPg.png" /><figcaption><em>When a newborn needs hospital care, the treatment may belong to the patient. The experience rarely belongs to the patient alone. AI-generated illustration created with ChatGPT.</em></figcaption></figure><p>Our daughter was barely a week old when we had to take her back to the hospital.</p><p>She had developed jaundice.</p><p>After her bilirubin levels were assessed, we were told she needed phototherapy.</p><p>Clinically, the idea was straightforward enough. She needed treatment under specialised lights to bring her bilirubin levels down.</p><p>Emotionally, there was nothing straightforward about what came next.</p><p>We had spent barely a week learning how to be parents.</p><p>A week of checking whether she was breathing while she slept.</p><p>A week of learning what different cries might mean.</p><p>A week of feeding, changing, holding and staring at this tiny person who had suddenly reorganised our entire world.</p><p>And then we were expected to leave her in someone else’s care.</p><p>I don’t think either of us was prepared for how much that would hurt.</p><h3>“Don’t Worry. We Have Cameras.”</h3><p>The hospital staff tried to reassure us.</p><p>We were told that our daughter would be looked after by professional staff. There were cameras. She would be monitored.</p><p>I understand what they were trying to communicate.</p><p><strong>Your baby is safe.</strong></p><p>From a clinical and operational perspective, those are important reassurances.</p><p>There are trained people here.</p><p>Someone is watching.</p><p>Your baby is receiving the treatment she needs.</p><p>But that wasn’t quite the question we were asking.</p><p>We weren’t only worried about whether someone would notice if something went wrong.</p><p>We wanted to be with our daughter.</p><p>She was a week old.</p><p>There is probably no particularly sophisticated way of describing what came afterwards.</p><p>It was gut-wrenching.</p><p>My wife and I tried to comfort each other, but emotionally we were somewhere else entirely. It felt as though something had been physically removed from us.</p><p>Rationally, we knew where our daughter was.</p><p>We knew she was receiving treatment.</p><p>We knew there were people caring for her.</p><p>Emotionally, none of that resolved the separation.</p><p>Eventually, sitting away from her became harder than going back.</p><p>So we went to see her again.</p><h3>We Had Seen Phototherapy Before</h3><p>There was another reason the experience surprised my wife.</p><p>She watches several family vloggers on YouTube. Among them was an Asian couple living in the United States who had shared their experience when their baby required phototherapy.</p><p>One detail had stayed with her.</p><p>Their hospital setup allowed the mother to remain in the room with her baby during treatment.</p><p>It was not an academic case study.</p><p>It was simply another family documenting their life.</p><p>But that does not make the observation meaningless.</p><p>Increasingly, this is one of the ways people encounter healthcare beyond their own experience. We hear stories from relatives. We ask friends. We read reviews. We follow people online. We watch births, illnesses and hospital stays unfold in places and systems we may never personally encounter.</p><p>Those experiences quietly expand our understanding of what healthcare <em>can</em> look like.</p><p>For my wife, that particular video had established something quite simple:</p><p><strong>Phototherapy and parental presence did not necessarily have to be mutually exclusive.</strong></p><p>That observation became much more meaningful when it was our daughter under the lights.</p><p>Our experience was different.</p><p>We were reassured that our baby was safe, monitored and professionally cared for.</p><p>But we had already seen another configuration of care in which treatment and parental presence appeared able to coexist.</p><p>The vlog did not tell us what our hospital <em>should</em> have done.</p><p>It made us wonder what might have been possible.</p><p>That distinction matters.</p><h3>The Questions Had Changed</h3><p>This wasn’t the first time during this journey that I had found myself thinking about how patients experience healthcare systems.</p><p>Earlier, I had written about how <a href="https://medium.com/@adamkureshi.hr/when-patients-want-more-than-just-a-hospital-09a29144621d"><strong>trust in an individual clinician can influence which institution a patient is willing to enter</strong></a>.</p><p>Later, a series of pregnancy scans made me think about <a href="https://medium.com/@adamkureshi.hr/the-scan-was-an-episode-the-pregnancy-wasnt-a5683836908f"><strong>what continuity of care actually means to the patient moving through the system</strong></a>.</p><p>But this experience felt different.</p><p>We were no longer deciding <strong>where to go</strong> or <strong>whom we wanted to see</strong>.</p><p>Our daughter was already inside the system.</p><p><strong>The question now was whether there was a place for us inside it too.</strong></p><h3>The Baby Was the Patient</h3><p>Looking back, the hospital’s arrangement made intuitive organisational sense.</p><p>Our daughter was the patient.</p><p>She had a clinical problem.</p><p>The problem required treatment.</p><p>Healthcare professionals were responsible for delivering that treatment.</p><p>We, meanwhile, were her parents.</p><p>But neonatal care makes that separation of roles less straightforward than it first appears.</p><p>A newborn cannot explain what she is feeling.</p><p>She cannot ask what happens next.</p><p>She cannot make decisions about her treatment.</p><p>She cannot feed, comfort or advocate for herself in the way an adult patient might.</p><p>For the first days and weeks of life, caring for the baby and involving the people who care for the baby are unusually difficult to separate.</p><p>That made me wonder whether we were thinking about the care unit correctly.</p><p>Perhaps the question wasn’t simply:</p><p><strong>Was our daughter receiving appropriate clinical care?</strong></p><p>There was another question alongside it:</p><p><strong>How were her parents being incorporated into that care?</strong></p><h3>Healthcare Has Been Thinking About This for a Long Time</h3><p>There is an established healthcare concept for much of what we were experiencing: <strong>patient- and family-centred care</strong>.</p><p>In paediatrics, the idea begins with something fairly intuitive. The family is not incidental to the child’s care.</p><p>The American Academy of Pediatrics describes patient- and family-centred care around principles including dignity and respect, information sharing, participation and collaboration. Its guidance recognises families as integral partners with healthcare teams. Standards for neonatal care also include reasonable parental access and family participation.</p><p>The World Health Organization approaches the issue similarly. Its standards for small and sick newborns include effective communication and meaningful participation, alongside emotional, psychosocial and developmental support.</p><p>That doesn’t mean parents become clinicians.</p><p>But it suggests they need not automatically become visitors either.</p><p>And that distinction changed the way I thought about our experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6YkvqnjmfhPAZfHF5YaLWA.png" /><figcaption><em>Family-centred care changes the question from when parents may enter the care environment to how they can safely participate within it. Framework interpretation by the author; visual created with AI assistance.</em></figcaption></figure><h3>What If Parents Aren’t Visitors?</h3><p>Hospitals inevitably make assumptions about roles.</p><p>There are spaces for patients.</p><p>Workstations for staff.</p><p>Waiting areas for attendants.</p><p>Rules about who can enter particular clinical spaces and when.</p><p>Many of those boundaries exist for good reasons. Infection prevention, privacy, clinical workflow, patient safety and limited space all matter.</p><p>But the physical and operational design of a hospital also reveals something about <strong>who the system expects to participate in care</strong>.</p><p>If parents are conceptualised primarily as visitors, the operational question becomes:</p><p><em>When should they be allowed to see the baby?</em></p><p>If parents are conceptualised as participants in care, the question changes:</p><p><em>How can we safely enable them to remain involved?</em></p><p>That is a very different starting point.</p><p>It doesn’t require parents to replace nurses.</p><p>It doesn’t mean unrestricted access is appropriate in every circumstance.</p><p>It doesn’t place parental preference above clinical safety.</p><p>But it changes what the system tries to accommodate.</p><p>A chair beside a cot.</p><p>Opportunities to feed or comfort the baby where clinically appropriate.</p><p>Clear expectations about when parents can be present.</p><p>A nearby space for families.</p><p>Regular communication when separation is unavoidable.</p><p>These can look like relatively small operational decisions.</p><p>Collectively, they say something much larger:</p><blockquote><strong><em>You are not simply waiting for us to return your baby. You remain part of her care.</em></strong></blockquote><h3>Cameras Answered One Question. They Couldn’t Answer the Other.</h3><p>This helped me understand why the reassurance we received had not quite worked.</p><p>The hospital staff weren’t necessarily saying the wrong thing.</p><p>They were answering a different question.</p><p>Cameras supported observation.</p><p>Professional staff provided clinical competence.</p><p>Monitoring helped keep a vulnerable newborn safe.</p><p>Those things mattered enormously.</p><p>But they addressed one dimension of our anxiety:</p><p><strong>Is our daughter safe?</strong></p><p>They could not fully address another:</p><p><strong>Why are we not with her?</strong></p><p>The hospital could tell us:</p><p><em>Someone competent is with your baby.</em></p><p>What we were feeling was:</p><p><em>But we are not.</em></p><p>Neither statement cancels the other.</p><p>Perhaps that is where family-centred care becomes more than simply being kind to families.</p><p>It asks healthcare organisations to consider whether the family sits outside the care process waiting for information, or somewhere within it.</p><h3>Even Necessary Separation Can Be Designed</h3><p>I don’t know whether there were clinical, infrastructural or operational reasons why one of us could not remain continuously with our daughter during her treatment.</p><p>I also don’t want to retrospectively assume that a different arrangement was necessarily feasible in that particular hospital.</p><p>Healthcare facilities operate within constraints.</p><p>Space is finite.</p><p>Staffing models differ.</p><p>Infection-control requirements matter.</p><p>Clinical acuity varies.</p><p>Not every facility can offer every configuration of care.</p><p>But perhaps that is precisely where the management question becomes useful.</p><blockquote><strong><em>Even when separation cannot be avoided, the experience of separation can still be designed.</em></strong></blockquote><p>How often can parents see their baby?</p><p>Who explains what is happening?</p><p>When will the next update come?</p><p>Can parents participate in feeding or comforting where clinically appropriate?</p><p>Is there somewhere suitable nearby for a recovering mother to sit or rest?</p><p>Does someone acknowledge what separation from a newborn might mean emotionally?</p><p>And if the parents are told to wait, do they know what they are waiting <em>for</em>?</p><p>These questions are not necessarily about luxury.</p><p>They are about whether caregivers have been considered in the design of the care pathway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IISbvp8Mvb6d48XZwMgp7Q.png" /><figcaption><em>The design of a care environment can reveal who the system expects to participate in care. AI-generated illustration created with ChatGPT.</em></figcaption></figure><p>Care Can Be Clinically Coordinated Without Feeling Coordinated</p><p>Healthcare organisations are understandably very good at defining clinical responsibility.</p><p>Someone orders the investigation.</p><p>Someone interprets it.</p><p>Someone admits the patient.</p><p>Someone administers treatment.</p><p>Someone monitors progress.</p><p>Those responsibilities need to be explicit.</p><p>But families experience all the spaces between those responsibilities too.</p><p>Waiting.</p><p>Wondering.</p><p>Trying to understand what happens next.</p><p>Trying to decide whether asking another question will make you difficult.</p><p>Trying to reassure the person sitting beside you when you aren’t particularly reassured yourself.</p><p>A care pathway can therefore make complete sense on paper while feeling very different to the people moving through it.</p><blockquote><strong><em>Care can be clinically coordinated without feeling coordinated to the family experiencing it.</em></strong></blockquote><p>For a newborn, that distinction may matter even more because the family isn’t simply observing the patient’s journey.</p><p>They are already part of it.</p><h3>We Went Back</h3><p>What I remember most clearly isn’t the equipment.</p><p>It isn’t the cameras.</p><p>It isn’t even what the room looked like.</p><p>I remember sitting with my wife away from our daughter.</p><p>Both of us trying to make the other feel better.</p><p>Neither succeeding particularly well.</p><p>Eventually, whatever reassurance we had been given wasn’t enough.</p><p>We wanted to see our baby.</p><p>So we went back.</p><p>Looking back, I don’t interpret that as evidence that the staff weren’t competent.</p><p>I don’t think competence was ever really the issue.</p><p>Our daughter needed phototherapy.</p><p>She needed monitoring.</p><p>She needed professional clinical care.</p><p>But she was also a week-old baby whose parents had spent seven days learning that caring for her meant being close enough to respond when she needed them.</p><p>Those needs do not necessarily have to compete.</p><p>Sometimes clinical circumstances will mean that they do.</p><p>But when they don’t, perhaps good healthcare design should ask whether separating them is necessary at all.</p><p>And when separation <em>is</em> necessary, perhaps managing that experience is itself part of the care.</p><p>Which leaves me with the question I keep returning to:</p><blockquote><strong><em>When the patient is a newborn, who does the healthcare system consider part of the care?</em></strong></blockquote><h3>Author’s Note</h3><p>This article reflects our family’s personal experience during our newborn daughter’s phototherapy. It is not intended as an assessment of any individual clinician or healthcare organisation, and I have deliberately left the hospital unnamed.</p><p>The comparison with another family’s experience shared on YouTube is included for what it was: one of the many informal ways patients and families encounter different models of healthcare and develop expectations about what may be possible. It is not intended as a comparison between national health systems.</p><p>The discussion of patient- and family-centred care is informed by guidance from the <strong>World Health Organization</strong> and the <strong>American Academy of Pediatrics</strong>. WHO’s standards for small and sick newborns include meaningful family participation and emotional and psychosocial support, while AAP guidance recognises families as integral partners in paediatric care.</p><p>This essay also continues a series of reflections on our recent healthcare experiences. The earlier pieces explored how <strong>trust can influence which institution a patient chooses</strong> and how <strong>continuity can mean preserving relationships across a healthcare journey</strong>.</p><h3>References</h3><p>American Academy of Pediatrics. (2012; reaffirmed 2025). <em>Patient- and Family-Centered Care and the Pediatrician’s Role.</em> Pediatrics, 129(2), 394–404.</p><p>American Academy of Pediatrics. (2023). <em>Standards for Levels of Neonatal Care: II, III, and IV.</em> Pediatrics, 151(6).</p><p>World Health Organization. (2020). <em>Standards for Improving the Quality of Care for Small and Sick Newborns in Health Facilities.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d10f163a050" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Scan Was an Episode. The Pregnancy Wasn’t.]]></title>
            <link>https://medium.com/@adamkureshi.hr/the-scan-was-an-episode-the-pregnancy-wasnt-a5683836908f?source=rss-bc3ee0c84b4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5683836908f</guid>
            <category><![CDATA[health-systems]]></category>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[patient-experience]]></category>
            <category><![CDATA[patient-centered-care]]></category>
            <category><![CDATA[healthcare-management]]></category>
            <dc:creator><![CDATA[Adam Kureshi]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 01:16:01 GMT</pubDate>
            <atom:updated>2026-10-01T01:16:01.992Z</atom:updated>
            <content:encoded><![CDATA[<p><em>What a series of pregnancy scans taught me about continuity, patient choice and the way healthcare systems organise care.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LZ1ZnHaTzBy8-N4g60TDgw.png" /><figcaption><em>Each scan was a separate clinical encounter. For us, they were all part of the same pregnancy.</em></figcaption></figure><p>By the later stages of my wife’s pregnancy, ultrasounds had become a familiar part of our routine.</p><p>Book the appointment. Get the scan. Wait for the report. Take it to our obstetrician. Work out what came next.</p><p>From the healthcare system’s perspective, each was a separate diagnostic investigation.</p><p>From ours, they were all part of the same pregnancy.</p><p>I didn’t think much about that distinction at the time.</p><p>Over several months, however, we ended up moving between a large diagnostic network, an independent diagnostician we came to trust, the larger network again when she became temporarily unavailable, and finally the hospital where we planned to have the delivery.</p><p>The clinical need remained broadly similar.</p><p>What changed was <strong>who provided the care, why we chose them and, eventually, whether that choice was ours to make at all.</strong></p><p>Only afterwards did I realise that our rather ordinary sequence of scans had made visible something healthcare management has been thinking about for a long time:</p><p><strong>continuity of care.</strong></p><h3>We Started With the Obvious Choice</h3><p>For our first scan, we went to a large diagnostic network.</p><p>There wasn’t much analysis behind the decision. It was established, recognisable and offered the investigation we needed.</p><p>Then my wife found another option in a distinctly modern way.</p><p>She came across a doctor on social media who operated an independent diagnostic practice from her home. Someone she knew had also recommended her.</p><p>The combination mattered.</p><p>Social media created visibility.</p><p>Recommendation reduced uncertainty.</p><p>So we tried her.</p><p>The difference wasn’t something dramatic. In many ways, it was made up of small things.</p><p>She was candid with us, but warm. She gave us time. She guided us through what she was seeing and took the opportunity to educate us rather than simply complete the scan and move on.</p><p>And there was something about the setting itself.</p><p>It felt homely.</p><p>There wasn’t the same sense of clinical detachment that can sometimes accompany a hospital or large diagnostic environment. For my wife in particular, that combination of time, explanation and warmth seemed to make uncertainty easier to manage.</p><p>We would arrive with questions.</p><p><strong>Her answers usually seemed to leave my wife less anxious than when we had entered.</strong></p><p>So we went again.</p><p>And again.</p><p>There was never a conversation in which we formally declared that she had become our preferred diagnostician. It happened much more quietly than that.</p><p>Our question simply changed.</p><p>Instead of:</p><p><em>Where should we get the next scan?</em></p><p>it became:</p><p><em>Is our doctor available?</em></p><blockquote><strong><em>Recommendation got us through the door. Experience made us return.</em></strong></blockquote><h3>We Noticed Continuity When We Lost It</h3><p>At one point during the pregnancy, our regular diagnostician travelled abroad.</p><p>We still needed a scan, so we returned to the larger diagnostic provider.</p><p>This particular encounter wasn’t a good one for us.</p><p>An interaction with an assistant felt unnecessarily rude. More importantly, we left with greater anxiety than when we had arrived. We had questions about what we were being told and didn’t feel we received the explanation or context we were looking for.</p><p>One encounter obviously cannot represent an entire organisation or the experience of its other patients.</p><p>Nor should clinicians minimise genuine concerns simply to reassure anxious parents.</p><p>But pregnancy changed the way I understood medical information.</p><p>A measurement on a screen may be clinically routine.</p><p>To two expectant parents, it can become the sentence discussed repeatedly on the drive home.</p><p><strong>Clinical information doesn’t arrive in an emotional vacuum.</strong></p><p>What stood out to me afterwards was that our regular diagnostician had never needed to withhold information to make us feel reassured.</p><p>She could be candid.</p><p>The difference was that candour came with explanation, context and time.</p><p>Looking back, I think that mattered particularly for my wife. The purpose of the encounter wasn’t merely to make her feel better, but good communication often meant she left understanding more and worrying less.</p><p>It was during this temporary break from our usual diagnostician that I began to recognise something we had probably taken for granted.</p><p>We weren’t returning to her simply because she could perform an ultrasound.</p><p>We had become comfortable with <strong>how we experienced the ultrasound with her.</strong></p><h3>Then She Returned</h3><p>When our regular diagnostician came back, we returned to her.</p><p>No comparison spreadsheet.</p><p>No formal reassessment of providers.</p><p>We simply booked the next scan.</p><p>In retrospect, that behaviour tells me more about our preference than a satisfaction questionnaire probably could.</p><blockquote><strong><em>Her absence sent us elsewhere. Her return brought us back.</em></strong></blockquote><p>Something had accumulated across those repeated encounters.</p><p>Familiarity.</p><p>An expectation about how the appointment would unfold.</p><p>A sense of how questions would be handled.</p><p>And, perhaps most importantly, we were no longer beginning the relationship again every time we entered the room.</p><p>At the time, I would probably have described this simply as having found a doctor we liked.</p><p>There is a more useful way of understanding it.</p><h3>Healthcare Has a Name for This</h3><p>In a widely cited review of continuity of care, Jeannie Haggerty and colleagues identified three related dimensions: <strong>informational continuity, management continuity and relational continuity.</strong></p><p>Informational continuity concerns whether information from previous encounters follows the patient and is used appropriately in subsequent care.</p><p>Management continuity concerns whether care remains coherent and connected across different providers and over time.</p><p>Relational continuity concerns an ongoing therapeutic relationship between a patient and one or more healthcare providers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XTq-biX80ojARTCssDIruw.png" /><figcaption><em>Continuity of care is multidimensional. Information, management and relationships can remain continuous in different ways.</em></figcaption></figure><p>It was that third dimension that immediately felt familiar.</p><p>What had accumulated across our scans wasn’t simply information.</p><p>It was a relationship.</p><p>We knew who we were going to see. We knew that questions would be given time. My wife knew she could expect candour without necessarily leaving the room feeling more uncertain than when she entered.</p><p>We weren’t rebuilding familiarity from zero each time.</p><p>The <strong>scan</strong> remained episodic.</p><p>The <strong>relationship</strong> had become continuous.</p><h3>Then the Rules of the Journey Changed</h3><p>Our final scan introduced a different dynamic.</p><p>Our preferred diagnostician was available.</p><p>But this time, availability wasn’t enough.</p><p>We were planning to have the delivery at a particular hospital and, as we understood its policy, the relevant investigations needed to be conducted within the hospital’s own system.</p><p>So that is where we went.</p><p>I don’t know the precise rationale behind that policy, and I wouldn’t presume to assign one.</p><p>There could be legitimate clinical and managerial reasons for keeping investigations within an organisation responsible for managing a delivery: information availability, clinical governance, standardisation, accountability or coordination between teams, for example.</p><p>Whatever the rationale, the requirement had a clear effect.</p><p>It kept the investigation within the hospital’s clinical system.</p><p>But it also meant stepping away from the relational continuity we had developed elsewhere.</p><p>That was the tension I hadn’t previously considered.</p><blockquote><strong><em>A healthcare system can preserve continuity across its processes while a patient experiences the loss of continuity with a person.</em></strong></blockquote><p>Those two things can happen at the same time.</p><h3>Continuity Has More Than One Job to Do</h3><p>Healthcare organisations cannot operate purely around individual relationships.</p><p>Information has to travel.</p><p>Investigations need standards.</p><p>Clinical responsibility needs to be clear.</p><p>Different professionals need to coordinate care safely.</p><p>These are not bureaucratic inconveniences. They are essential features of organised healthcare.</p><p>But the patient is simultaneously experiencing something that doesn’t fit as neatly into an organisational chart.</p><p>A relationship.</p><p>Ideally, informational, management and relational continuity reinforce one another.</p><p>But our experience made me wonder what happens when they don’t.</p><p>A patient’s reports can remain available.</p><p>Their clinical pathway can remain coherent.</p><p>Their care can continue.</p><p>And yet, from the patient’s perspective, something continuous can still have been interrupted.</p><h3>Where Patient-Centred Care Enters the Picture</h3><p>That brings the experience into another established idea in healthcare quality: <strong>patient-centred care</strong>.</p><p>The Institute of Medicine included patient-centredness among its six aims for improving healthcare quality, describing care that is respectful of and responsive to individual patient preferences, needs and values, with those values helping guide clinical decisions.</p><p>That doesn’t mean patients should simply receive whatever they request.</p><p>Clinical safety, professional standards and organisational responsibilities still matter.</p><p>But patient-centredness does require healthcare systems to understand what patients value.</p><p>And sometimes what a patient values is not another service or another choice on a menu.</p><p>It is <strong>continuity with a person.</strong></p><p>That creates a useful question for healthcare managers:</p><p><em>Can we preserve the benefits of standardisation and coordination without unnecessarily breaking relationships patients already trust?</em></p><p>There will not always be a way to do that.</p><p>Clinicians take leave. Patients move. Specialist expertise becomes necessary. Referral pathways change. Clinical risk can override preference.</p><p>But recognising relational continuity as something worth preserving is different from assuming every technically appropriate provider is interchangeable from the patient’s perspective.</p><h3>Patient Choice Is More Fragile Than It Looks</h3><p>Our sequence of scans also changed how I think about patient choice.</p><p>At the beginning, our choice was relatively open.</p><p>Recommendation introduced another provider.</p><p>Experience created a preference.</p><p>Repeated encounters created relational continuity.</p><p>Temporary unavailability interrupted it.</p><p>Her return restored it.</p><p>Then an institutional requirement constrained it.</p><p>Our preferences hadn’t necessarily changed.</p><blockquote><strong><em>Our ability to act on them had.</em></strong></blockquote><p>That distinction has an interesting implication for healthcare management.</p><p>Managers routinely look at utilisation: which facilities patients attend, which services they use, where referrals go and where patients drop out.</p><p>But utilisation tells us <strong>where a patient received care</strong>.</p><p>It does not necessarily tell us <strong>where they wanted to receive it.</strong></p><p>A patient attending one provider may have preferred another.</p><p>The preferred clinician may have been unavailable. Insurance may have excluded them. Distance may have intervened. A referral pathway may have directed the patient elsewhere. An institutional requirement may have narrowed the options.</p><p>In other words:</p><p><strong>Utilisation is behaviour observed within a set of constraints.</strong></p><p>If we want to understand patient-centred care, measuring where patients go may therefore be insufficient.</p><p>We also need to understand what they were trying to preserve when they got there.</p><h3>Trust May Travel. Choice Cannot Always Follow.</h3><p>After our daughter was born, I wrote about another part of this experience and described something I called <a href="https://medium.com/@adamkureshi.hr/when-patients-want-more-than-just-a-hospital-09a29144621d"><strong>portable trust</strong></a>: the idea that trust in an individual clinician can influence which institution a patient is willing to enter.</p><p>These scans showed me its limit.</p><blockquote><strong><em>Trust may be portable. Choice isn’t always.</em></strong></blockquote><p>Patients can carry their preferences through a healthcare journey.</p><p>Whether they can act on those preferences depends partly on the system around them.</p><p>Sometimes the constraint is availability.</p><p>Sometimes it is geography or affordability.</p><p>Sometimes it is insurance.</p><p>Sometimes it is a clinical requirement or institutional policy.</p><p>That doesn’t automatically mean those constraints are wrong.</p><p>It simply means that the patient’s eventual destination does not necessarily tell us the whole story of how they got there.</p><h3>The Scan Was an Episode. The Pregnancy Wasn’t.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*23M3NjIZHQFyOuZZEwPnHg.png" /><figcaption><em>Healthcare organisations divide care into encounters. Patients experience what connects them.</em></figcaption></figure><p>None of this occurred to me while we were moving between appointments.</p><p>We were simply trying to get through a pregnancy safely.</p><p>Get the scan.</p><p>Ask the questions.</p><p>Take the report to the obstetrician.</p><p>Move on.</p><p>Only afterwards did the pattern become visible.</p><p>Each provider encountered us for an episode.</p><p><strong>We experienced those episodes as parts of the same journey.</strong></p><p>Healthcare organisations inevitably have to organise care into appointments, investigations, providers and departments.</p><p>Patients stitch those encounters back together into something continuous.</p><p>Good healthcare management has to see both.</p><p>Which leaves me with a different question about continuity than the one I started with:</p><blockquote><strong><em>When a patient asks for continuity of care, do we know what they are actually asking to continue?</em></strong></blockquote><h3>Author’s Note</h3><p>This article reflects our personal experience navigating diagnostic care during my wife’s pregnancy. It is not intended as an assessment of any individual clinician or healthcare organisation, nor does a single encounter represent the quality of care provided to other patients.</p><p>I have therefore deliberately left the providers and institutions unnamed.</p><p>The experience simply gave me a reason to think more carefully about an established healthcare-management idea: <strong>continuity of care</strong>, and particularly the difference between keeping care connected through systems and preserving the relationships patients come to value along the way.</p><p>The discussion of informational, management and relational continuity draws on the work of <strong>Jeannie Haggerty and colleagues</strong>, while the discussion of patient-centred care draws on the <strong>Institute of Medicine’s quality-of-care framework</strong>.</p><h3>References</h3><p>Haggerty, J. L., Reid, R. J., Freeman, G. K., Starfield, B. H., Adair, C. E., &amp; McKendry, R. (2003). <em>Continuity of care: a multidisciplinary review.</em> <strong>BMJ, 327</strong>, 1219–1221.</p><p>Institute of Medicine. (2001). <em>Crossing the Quality Chasm: A New Health System for the 21st Century.</em> National Academy Press.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5683836908f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Patients Want More Than Just a Hospital]]></title>
            <link>https://medium.com/@adamkureshi.hr/when-patients-want-more-than-just-a-hospital-09a29144621d?source=rss-bc3ee0c84b4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/09a29144621d</guid>
            <category><![CDATA[healthcare]]></category>
            <category><![CDATA[health-insurance]]></category>
            <category><![CDATA[patient-experience]]></category>
            <category><![CDATA[medicine]]></category>
            <category><![CDATA[trust]]></category>
            <dc:creator><![CDATA[Adam Kureshi]]></dc:creator>
            <pubDate>Tue, 15 Sep 2026 14:01:03 GMT</pubDate>
            <atom:updated>2026-09-15T14:01:03.209Z</atom:updated>
            <content:encoded><![CDATA[<p><em>What the birth of our daughter taught me about doctors, trust and how healthcare choices are actually made.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*trJwQnFWwS6Hadz6DRhGZg.jpeg" /><figcaption><em>The conversation that started with feeding a newborn led me back to a much earlier healthcare decision.</em></figcaption></figure><p>A few weeks after our daughter was born, my wife and I were sitting at the breakfast table, attempting what had become a fairly standard negotiation: trying to feed ourselves while feeding a newborn.</p><p>Somewhere in the middle of it, my wife said something that caught me completely off guard.</p><blockquote><em>“I miss my doctor.”</em></blockquote><p>My first response was confusion.</p><p><em>What do you mean, you miss your doctor?</em></p><p>She thought about it for a moment and said she missed being pregnant. The appointments. The check-ups. The strange routine that had developed around the antenatal period.</p><p>This surprised me.</p><p>Only a few weeks earlier, I had watched her go through labour. I had seen the discomfort of the final weeks of pregnancy, followed by the pain and exhaustion of childbirth.</p><p>From where I had been standing, pregnancy was not something I expected her to become nostalgic about quite so quickly.</p><p>But her comment stayed with me.</p><p>Perhaps because, over the months leading up to our daughter’s birth, I had watched something develop between my wife and her doctor that I had not really thought much about at the time.</p><p>And looking back, it had influenced some fairly consequential decisions.</p><p>Including where our daughter was eventually born.</p><h3>We Didn’t Start With Her</h3><p>Our search for an obstetrician had not been particularly systematic.</p><p>Like many people navigating healthcare, we started with recommendations. We heard names. We asked people about their experiences. We tried practitioners.</p><p>Over the course of the pregnancy, we cycled through a couple of consultants before eventually meeting the doctor who would deliver our daughter.</p><p>She came highly recommended through word of mouth.</p><p>That mattered.</p><p>But a recommendation can only get someone through the door.</p><p>What happened afterwards mattered much more.</p><p>She was calm. She listened. She didn’t seem unnecessarily alarmist. She answered our questions without making us feel ridiculous for asking them.</p><p>My wife felt comfortable with her almost immediately.</p><p>Then came another appointment.</p><p>And another.</p><p>As the pregnancy progressed, familiarity became confidence, and confidence gradually became trust.</p><p>Without really noticing it happening, the way we made decisions began to change.</p><p>The question was no longer simply:</p><p><strong>Which hospital should we choose?</strong></p><p>It had become:</p><p><strong>Where can our doctor deliver the baby?</strong></p><p>That sounds like a small linguistic difference.</p><p>It wasn’t.</p><h3>We Had Already Chosen a Hospital</h3><p>Originally, we had planned to use a hospital covered by our employer-provided health insurance.</p><p>It seemed like the obvious choice.</p><p>Childbirth is expensive. We had insurance. The hospital was on the insurer’s panel. Using an empanelled hospital would mean a smaller upfront cash burden and a considerably simpler administrative process.</p><p>Then our consultant complicated the decision.</p><p>She practised at several hospitals, but there were practical considerations around where she was comfortable attending a delivery.</p><p>Distance mattered.</p><p>If something happened unexpectedly, she needed to be able to reach the hospital reasonably quickly.</p><p>She was also hesitant about one institution we had previously considered because of concerns she raised about staffing. Those concerns were subsequently echoed by friends who had recently had their own experience there.</p><p>Another hospital was one she was more comfortable with, but its location was less convenient for us.</p><p>Eventually, another institution emerged as the practical option.</p><p>It worked geographically.</p><p>Our doctor practised there.</p><p>She was comfortable attending the delivery there.</p><p>There was just one fairly significant problem.</p><p>It wasn’t on our insurance panel.</p><p>We could still submit eligible expenses for reimbursement afterwards, but we would first have to pay out of pocket.</p><p>That meant a larger upfront cash outlay, additional paperwork, reimbursement uncertainty and considerably more inconvenience.</p><p>We chose it anyway.</p><p>At the time, I don’t remember thinking of that decision as particularly remarkable.</p><p>Looking back, I think it tells us something important about what we were actually choosing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DqS6j_UkztNBC2F3zv1A-A.jpeg" /><figcaption><em>The hospital was the visible choice. The trusted relationship behind that choice was less visible — but more influential.</em></figcaption></figure><h3>What Were We Really Choosing?</h3><p>Healthcare decisions are often described as though patients choose between institutions.</p><p>One hospital has better facilities.</p><p>Another is closer.</p><p>One accepts your insurance.</p><p>Another has the stronger reputation.</p><p>Compare the alternatives, weigh the variables and choose.</p><p>Our experience was considerably messier.</p><p>The hospital mattered.</p><p>Insurance mattered.</p><p>Location mattered.</p><p>Staffing mattered.</p><p>Cost certainly mattered.</p><p>But by that stage, another variable had accumulated enough weight to alter how we treated all the others.</p><p>Trust.</p><p>We had the financially and administratively easier option.</p><p>We chose the harder one.</p><p>Not because we particularly enjoyed paying hospital bills upfront.</p><p>Because our doctor was there.</p><h3>How Does That Kind of Trust Develop?</h3><p>While thinking about this experience, I kept returning to an idea from David Maister, Charles Green and Robert Galford’s <em>The Trusted Advisor</em>.</p><p>The authors propose what they call the <strong>Trust Equation</strong>:</p><p><strong>Trustworthiness = (Credibility + Reliability + Intimacy) ÷ Self-Orientation</strong></p><p>I had encountered the framework in a professional context before.</p><p>I had never really thought about it while sitting in an obstetrician’s clinic.</p><p>Yet it described surprisingly well what I had watched happen.</p><p>There was <strong>credibility</strong>.</p><p>Our doctor came recommended, and her professional judgement gradually reinforced that initial reputation.</p><p>There was <strong>reliability</strong>.</p><p>Pregnancy gave the relationship something many healthcare encounters do not have: repetition. Appointment after appointment, the same person was there.</p><p>There was <strong>intimacy</strong> — not in the everyday sense of personal closeness, but in feeling safe placing something vulnerable in another person’s hands.</p><p>My wife could ask questions. She could express concerns. She felt listened to.</p><p>And then there was <strong>self-orientation</strong>: the extent to which a professional appears focused on their own interests rather than yours.</p><p>We could never know our doctor’s internal motivations. What we could observe was how her advice felt from our side.</p><p>When she discussed hospitals, she spoke candidly about the constraints. She told us where she was comfortable attending. She raised concerns where she had them. She suggested alternatives.</p><p>It felt less like being directed towards a transaction and more like being given professional judgement.</p><p>None of these interactions was particularly dramatic.</p><p>That may actually be the point.</p><p>Trust did not arrive during one grand moment.</p><p>It accumulated.</p><h3>When Trust Acquires a Price</h3><p>The Trust Equation is not an economic model.</p><p>But once trust begins changing behaviour, it starts producing economic consequences.</p><p>Our hospital decision made that unexpectedly visible.</p><p>We had an empanelled option that offered easier payment arrangements.</p><p>Following our doctor meant accepting a larger upfront cash-flow burden, reimbursement uncertainty and additional administrative friction.</p><p>We followed the doctor.</p><p>That does not tell us exactly how many rupees the relationship was worth.</p><p>But it does tell us something.</p><blockquote><strong><em>The value we placed on preserving trust had become greater than the additional financial and administrative friction required to preserve it.</em></strong></blockquote><p>Had someone asked us months earlier how much inconvenience we would accept to retain a particular obstetrician, I doubt we could have answered.</p><p>When confronted with the actual decision, our behaviour answered for us.</p><p>And that made me wonder whether something we normally describe as intangible might have very tangible effects on where patients ultimately go.</p><h3>When Trust Sits With a Person</h3><p>There is a parallel in professional services that I find useful.</p><p>Consulting firms sometimes have “star consultants”: people whom clients ask for by name and around whom particular relationships develop.</p><p>The client may technically be hiring the firm, but some of the trust associated with that firm can sit with an individual.</p><p>You discover how important that distinction is when the individual moves and clients want to follow.</p><p>Healthcare seems capable of producing something similar.</p><p>A hospital may contain hundreds of beds, operating theatres, diagnostic equipment, nurses, laboratories and enormous physical infrastructure.</p><p>Yet a single trusted clinician can influence which institution a patient ultimately chooses to enter.</p><p>That was essentially what happened to us.</p><p>The hospital provided the infrastructure we needed.</p><p>But our doctor provided something that was much more portable: a relationship we trusted.</p><blockquote><strong><em>Sometimes patients don’t choose an institution and then find a doctor. They choose a doctor, and that doctor changes which institutions they are willing to enter.</em></strong></blockquote><p>I have come to think of this as <strong>portable trust</strong>.</p><p>The institution may benefit from that trust, but the relationship generating it sits between patient and clinician.</p><p>And relationships can move.</p><p>When they do, patient choices can shift, and the demand for particular providers or services can shift with them.</p><p>Our own decision offered a small example.</p><p>Insurance was tied to a set of institutions.</p><p>Our trust was tied to a person.</p><p>When those two things pulled in different directions, the person won.</p><blockquote><strong><em>Hospitals own the infrastructure. Clinicians can carry some of the trust that determines which infrastructure patients choose to use.</em></strong></blockquote><h3>But the Hospital Still Has to Earn Its Own Trust</h3><p>There is an important limitation to this idea.</p><p>Choosing a trusted doctor did not mean every part of our subsequent hospital experience became excellent.</p><p>A hospital is a complex organisation.</p><p>There are nurses, radiologists, technicians, administrative staff, billing processes, rooms, waiting systems and dozens of other interactions that the consultant who brought the patient into the institution neither owns nor controls.</p><p>We would discover this ourselves.</p><p>Some interactions were excellent.</p><p>Others were frustrating.</p><p>And that exposed a distinction I had not really appreciated before:</p><p><strong>Trust in a clinician is not the same thing as trust in an institution.</strong></p><p>Our doctor’s relationship with us influenced which hospital we entered.</p><blockquote><strong><em>What happened once we walked through the doors belonged to the hospital.</em></strong></blockquote><p>A trusted clinician may bring a patient through those doors.</p><p>The institution still has to earn its part of the relationship.</p><p>That distinction would become much clearer to me over the days that followed.</p><p>But that is a story for another time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EAEz69ci1nK8Gkjed2hOng.jpeg" /><figcaption><em>A trusted clinician can bring a patient to the door. The institution still has to earn trust once the patient enters.</em></figcaption></figure><h3>What My Wife Was Actually Missing</h3><p>Which brings me back to breakfast.</p><p>After everything was over, my wife left her doctor a glowing review.</p><p>That didn’t particularly surprise me.</p><p>What surprised me was the attachment behind it.</p><p>She wasn’t simply reviewing someone who had successfully completed a medical procedure.</p><p>This was someone who had accompanied her through months of uncertainty.</p><p>Pregnancy had involved appointments, scans, questions, anxieties, physical changes, decisions and eventually one of the most demanding experiences of her life.</p><p>Through much of that journey, there had been one familiar person.</p><p>Someone who knew where she was in the story.</p><p>Someone whose calmness made uncertainty feel slightly more manageable.</p><p>Someone my wife expected to see again at the next appointment.</p><p>Then our daughter arrived.</p><p>The appointments stopped.</p><p>The relationship had served its clinical purpose.</p><p>And suddenly it was gone.</p><p>That morning, when my wife said she missed her doctor, I initially thought she was simply being nostalgic about pregnancy.</p><p>Now I think she was telling me something more interesting about healthcare.</p><p>We tend to organise healthcare around episodes.</p><p>Consultations.</p><p>Scans.</p><p>Procedures.</p><p>Admissions.</p><p>Deliveries.</p><p>Discharges.</p><p>But patients don’t necessarily experience healthcare that way.</p><p>They experience journeys.</p><p>And when those journeys involve uncertainty and vulnerability, perhaps what we are looking for is not only the best institution.</p><p>We are also looking for someone we trust to help us navigate it.</p><p>We thought we were choosing where our daughter would be born.</p><p>Looking back, the more important choice had happened much earlier.</p><blockquote><strong><em>We had chosen the person we wanted beside us when she arrived.</em></strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XPMDTVAspXB7LUUP08IDhQ.png" /><figcaption><em>Healthcare may be organised around episodes. Patients often remember the people who helped them through the journey.</em></figcaption></figure><p><strong>Author’s Note:</strong> <em>This article is a personal reflection drawn from my recent experience navigating healthcare as a patient’s family member. While healthcare is also part of my professional domain, the observations here come from experiencing the system from a more personal vantage point. They are not intended as medical advice or as an assessment of any particular healthcare professional or institution. Identifying details have been omitted because my interest is in the broader patterns around trust, choice and patient experience that the journey brought into view.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=09a29144621d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting a Job Has Become Like Joining an Exclusive Club]]></title>
            <link>https://medium.com/@adamkureshi.hr/getting-a-job-has-become-like-joining-an-exclusive-club-805ca0d3f973?source=rss-bc3ee0c84b4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/805ca0d3f973</guid>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Adam Kureshi]]></dc:creator>
            <pubDate>Tue, 08 Sep 2026 14:01:02 GMT</pubDate>
            <atom:updated>2026-09-08T14:01:02.915Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Your skills may qualify you for membership. They do not necessarily get you through the door.</em></p><p>I just finished watching <em>Suits</em>, and something about its highly stylised corporate world caught my attention.</p><p>It is, of course, television. The offices are immaculate, the confrontations perfectly timed, and everyone seems capable of producing a devastating argument while walking rapidly down a corridor.</p><p>But underneath all that corporate glamour sits an idea that feels remarkably familiar.</p><p><strong>Be good enough and you will rise.</strong></p><p>Harvey Specter commands influence because he delivers. Mike Ross, despite the rather significant problem at the centre of his employment, repeatedly survives because of an almost absurd level of ability.</p><p>Their world is political, competitive and ruthless, but competence remains a kind of ultimate currency.</p><p>It is a story many of us have absorbed in one form or another.</p><p>Work hard. Become good at something. Bring value to an organisation. Make yourself difficult to replace.</p><p>And your career, eventually, will take care of itself.</p><p>Perhaps that was always an incomplete description of how careers worked.</p><p>Because the closer I have watched recruitment, the more I have wondered whether we have confused <strong>being valuable with being recognised as valuable</strong>.</p><p>You can be capable without being visible.</p><p>You can be qualified without being trusted.</p><p>You can meet every requirement on a job description without having anyone inside the room willing to say your name.</p><p>And increasingly, that last distinction seems to matter.</p><blockquote><strong><em>The corporate world may still reward competence. But competence first has to gain admission.</em></strong></blockquote><h3>The Recruitment System We Are Told Exists</h3><p>On paper, recruitment is beautifully rational.</p><p>An organisation has a problem. It identifies the capabilities required to solve it, converts those capabilities into a job description, and invites people to demonstrate that they possess them.</p><p>Candidates submit their qualifications and experience.</p><p>HR screens them.</p><p>The strongest candidates are shortlisted.</p><p>Interviews assess suitability.</p><p>The best person gets the job.</p><p>Something roughly like:</p><p><strong>Qualifications + Experience + Skills → Selection</strong></p><p>It is an appealing system because it gives both sides a relatively clear contract.</p><p>The organisation gets talent.</p><p>The candidate gets rewarded for developing it.</p><p>And if you are unsuccessful, there is an obvious response:</p><p><em>Become better.</em></p><p>Get another qualification. Develop another skill. Gain more experience. Improve your CV. Learn how to interview better.</p><p>I believed this for a long time.</p><p>I am no longer sure the system is quite that simple.</p><p>Because there seems to be another recruitment system operating alongside the formal one.</p><p>Someone knows the hiring manager.</p><p>Someone previously worked with the director.</p><p>Someone calls somebody.</p><p>A CV arrives privately rather than through the recruitment portal.</p><p>A senior executive says, <em>“Have a look at this person.”</em></p><p>Sometimes it is more explicit:</p><p><em>This candidate comes highly recommended.</em></p><p>And occasionally there is the sentence that changes the meaning of everything that follows:</p><p><em>This is the person they want.</em></p><p>The vacancy may still be advertised.</p><p>Applications may still be collected.</p><p>Candidates may still be shortlisted.</p><p>Interviews may still take place.</p><p>Evaluation sheets may still be completed.</p><p>Yet everyone close enough to the process understands that one candidate has entered the competition carrying something that does not appear anywhere in the job description.</p><p><strong>Someone with influence has already said their name.</strong></p><p>At that point, recruitment begins to look less like an examination and more like admission to an exclusive club.</p><p>The published requirements tell you whether you are eligible for membership.</p><p>They do not necessarily tell you how membership is decided.</p><h3>The Four Currencies of a Career</h3><p>The more I thought about this, the less useful the simple distinction between <em>merit</em> and <em>connections</em> became.</p><p>Candidates seem to enter recruitment carrying at least four forms of professional capital.</p><h3>1. Capability Capital</h3><p>This is what we are traditionally told to accumulate.</p><p>Knowledge. Experience. Technical skill. Judgment. Problem-solving ability.</p><p><strong>Can you actually do the work?</strong></p><h3>2. Signal Capital</h3><p>This is how other people infer that capability.</p><p>Your university. Qualifications. Previous employers. Job titles. Certifications. Portfolio.</p><p>Even the language through which you describe your experience.</p><p>These things do not necessarily prove capability.</p><p>They make capability easier for someone else to recognise.</p><p><strong>Can other people recognise that you can do the work?</strong></p><h3>3. Social Capital</h3><p>This is about relationships and trust.</p><p>Who knows you?</p><p>Who has worked with you?</p><p>Who trusts your judgment?</p><p>Who would recommend you?</p><p>A former colleague saying,</p><p><em>“I’ve worked with her. She’s excellent,”</em></p><p>is transferring some of their trust to you.</p><p><strong>Who trusts you enough to say your name?</strong></p><h3>4. Political Capital</h3><p>This is different.</p><p>It is not simply about who trusts you.</p><p>It is about <strong>who possesses enough organisational power to influence what happens to you.</strong></p><p>A respected colleague saying,</p><p><em>“You should interview this person,”</em></p><p>is social capital.</p><p>A senior executive saying,</p><p><em>“This is the person I want,”</em></p><p>is political capital.</p><p>One transfers trust.</p><p>The other exercises power.</p><p><strong>Who can influence the decision?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dZrpQmwU0O7RjQmdsqL3wQ.jpeg" /></figure><p>These currencies interact, but they are not interchangeable.</p><p>Someone can possess enormous capability and little visibility.</p><p>Someone can have excellent credentials but few trusted relationships.</p><p>Someone can have an extensive network but limited technical depth.</p><p>And someone can carry the backing of a person powerful enough to change how the process treats them.</p><blockquote><strong><em>Perhaps candidates are competing in currencies that job descriptions barely acknowledge.</em></strong></blockquote><h3>A Different Way of Thinking About Networks</h3><p>This tension between capability and access reminded me of Jeffrey Pfeffer’s work on power and professional networks.</p><p>Pfeffer has used technology entrepreneur and venture capitalist Heidi Roizen as a case for examining how professional networks are built, maintained and used to create access to people across an organisation — including those in senior positions. Stanford Graduate School of Business still uses the Roizen case as part of Pfeffer’s <em>Paths to Power</em> material.</p><p>What interests me about this is not the usual instruction to <em>network more</em>.</p><p>It is something more structural:</p><blockquote><strong><em>Where you sit in a network changes who gets to observe what you can do.</em></strong></blockquote><p>That changes how I think about professional relationships.</p><p>Perhaps networks are not simply something we build <em>after</em> becoming competent.</p><p>They can be part of the mechanism through which competence becomes <strong>visible, trusted and eventually rewarded</strong>.</p><p>And once that process starts, something more interesting happens.</p><h3>Access Compounds</h3><p>Imagine two similarly capable people early in their careers.</p><p>One happens to work closely with a senior leader.</p><p>The senior leader sees their work and trusts them with an important assignment.</p><p>That assignment creates experience.</p><p>The experience strengthens their CV.</p><p>The project introduces them to other senior people.</p><p>Those people observe their work.</p><p>Their reputation grows.</p><p>The next time an opportunity appears, someone remembers them.</p><p>Another opportunity follows.</p><p>And then another.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tN3CfUzloR41JX5B4jhjTg.jpeg" /></figure><p>This is a reinforcing feedback loop.</p><p>And its significance goes beyond networking.</p><p>Because after enough cycles, <strong>access begins producing some of the things we subsequently interpret as merit</strong>.</p><p>Return to our two professionals five years later.</p><p>One now possesses more impressive projects.</p><p>Stronger references.</p><p>More recognisable experience.</p><p>A better title.</p><p>Perhaps experience managing a team.</p><p>Perhaps a relationship with an important client.</p><p>On paper, that person is now the stronger candidate.</p><p>Selecting them may look entirely meritocratic.</p><p>Perhaps, at that moment, it even is.</p><p>But the CV cannot show us the full history that produced the difference.</p><p>An earlier introduction created an opportunity.</p><p>The opportunity created experience.</p><p>The experience created credibility.</p><p>Credibility created another opportunity.</p><blockquote><strong><em>Access did not merely help one candidate compete on merit. Access helped create some of the evidence that would later be interpreted as merit.</em></strong></blockquote><p>That raises a much harder question than whether connections matter:</p><p><em>If access creates opportunities, opportunities create experience, and experience becomes evidence of merit, where exactly does merit end and accumulated advantage begin?</em></p><h3>Why Would a Rational System Behave This Way?</h3><p>It would be easy to turn this into a story about bad recruiters, nepotistic managers or organisational politics.</p><p>But that explanation feels incomplete.</p><p>A systems view asks a different question:</p><p><strong>What makes these behaviours useful to the people inside the system?</strong></p><p>Recruitment has a fundamental information problem.</p><p>An organisation is trying to predict future performance using incomplete information about people it often barely knows.</p><p>A degree cannot guarantee judgment.</p><p>Years of experience do not necessarily indicate quality.</p><p>A CV is curated.</p><p>An interview is artificial.</p><p>References are selective.</p><p>So organisations rely on proxies.</p><p><strong>Qualifications</strong> become proxies for knowledge.</p><p><strong>Experience</strong> becomes a proxy for capability.</p><p><strong>Previous employers</strong> become proxies for quality.</p><p><strong>Interview performance</strong> becomes a proxy for behaviour.</p><p><strong>References</strong> become proxies for reliability.</p><p><strong>Referrals</strong> become proxies for trust.</p><p>None is perfect.</p><p>But perfect evaluation would be enormously expensive.</p><p>Recruitment is therefore partly a problem of <strong>allocating scarce evaluation capacity under uncertainty</strong>.</p><p>And trusted relationships can be remarkably efficient shortcuts.</p><p>If someone whose judgment I respect tells me,</p><p><em>“I’ve worked with him. He’s excellent,”</em></p><p>I have received information that may genuinely be more useful than another page on his CV.</p><p>The candidate arrives carrying something valuable:</p><p><strong>borrowed trust.</strong></p><h3>The Complication: Referrals Can Actually Work</h3><p>This is where the story becomes less morally convenient.</p><p>A study published in <em>The Quarterly Journal of Economics</em> examined personnel data from nine large firms across call centres, trucking and high-tech. Referred applicants were more likely to be hired and more likely to accept offers even though referred and non-referred applicants had similar measured skill characteristics. Referred employees were also substantially less likely to quit. In the two industries where researchers could calculate worker-level profits, referred employees generated higher profits, driven by lower turnover and recruiting costs.</p><p>That matters.</p><p>Because it prevents us from reducing the system to:</p><p><em>connections = unfair.</em></p><p>A referral can contain information that an employer cannot easily obtain from an application or interview.</p><p>Someone who has actually worked with a candidate may know whether that person is reliable, capable and effective.</p><p>From the perspective of an individual hiring decision, using that information can be perfectly rational.</p><p>But systems produce effects beyond individual decisions.</p><p>If referrals repeatedly increase access for people already connected to trusted networks, those people receive more opportunities.</p><p>Those opportunities produce more experience.</p><p>And that experience strengthens their position in the next competition.</p><p><strong>A system can advantage insiders without being irrational.</strong></p><p>What is efficient for an organisation making one hiring decision may still shape how opportunity accumulates across entire careers.</p><h3>Sometimes the Safest Decision Is Not Necessarily the Best One</h3><p>There is another incentive worth considering.</p><p>Organisational researchers have studied what they call <strong>defensive decision-making</strong>: situations in which someone believes one option is best for the organisation but deliberately chooses another partly to protect themselves from possible negative consequences.</p><p>In one study of 950 managers in a large German public administration, <strong>80% reported at least one defensive decision among their ten most important decisions during the previous year</strong>. On average, 2.5 of those ten decisions were described as defensive.</p><p>The setting matters.</p><p>This was not a study of recruitment, nor should those percentages be generalised to hiring managers everywhere.</p><p>But the mechanism made me think differently about recruitment.</p><p>Imagine you are a hiring manager.</p><p>You select an unconventional candidate.</p><p>Their career path is unusual. Their previous employer is unfamiliar. Nobody senior recommended them.</p><p>Six months later, the hire fails.</p><p>Someone asks:</p><p><em>Why did you choose this person?</em></p><p>Now imagine you select someone from a respected competitor with conventional qualifications who came recommended by a trusted senior colleague.</p><p>They also fail.</p><p>The outcome is the same.</p><p>But is the second decision easier to defend?</p><p>If so, decision-makers may not only be asking:</p><p><strong>Who is most likely to succeed?</strong></p><p>They may also, consciously or otherwise, be influenced by:</p><p><strong>Which decision will be easiest to justify if I am wrong?</strong></p><p>Recognisable employers become safer.</p><p>Traditional career paths become safer.</p><p>Established qualifications become safer.</p><p>Trusted recommendations become safer.</p><p>The research does not establish that hiring managers routinely choose safer-looking candidates over better ones.</p><p>But the existence of defensive decision-making gives us reason to ask:</p><blockquote><strong><em>Does the safest candidate sometimes beat the potentially best candidate?</em></strong></blockquote><p>If so, organisations are not merely managing candidate risk.</p><p>The people making decisions may also be managing <strong>their own decision risk</strong>.</p><h3>The Recruitment Paradox</h3><p>Then there is scale.</p><p>Digital recruitment has made applying for jobs extraordinarily easy.</p><p>In principle, this should democratise access.</p><p>The front door has opened wider.</p><p>But opening the door creates another problem.</p><p><strong>Someone still has to evaluate everyone coming through it.</strong></p><p>Greenhouse’s 2026 recruiting benchmarks analysed data from more than <strong>6,000 companies and 640 million applications between 2022 and 2025</strong>.</p><p>The change is striking.</p><p>Applications per job increased from <strong>116 to 244</strong>.</p><p>That’s a <strong>111% increase</strong>.</p><p>The average number of recruiters per organisation in the dataset fell from <strong>10.43 to 4.62</strong>.</p><p>And perhaps the most revealing measure sits between those two trends:</p><p>Annual applications handled per recruiter increased from <strong>146 to 746</strong>.</p><p>A <strong>412% increase</strong>.</p><p>More candidates are entering recruitment systems while individual recruiters in these organisations are being asked to process dramatically more information.</p><p>That creates an evaluation problem.</p><p><em>As applications increase, recruiters have more candidates to assess within the same limited time and capacity. That increases the screening burden and reduces the attention available to examine each candidate in depth. The system therefore faces growing pressure to use faster, more efficient ways of deciding who deserves a closer look.</em></p><p>What happens next is a hypothesis.</p><p>The Greenhouse data does <strong>not</strong> demonstrate that increasing application volumes cause organisations to rely more heavily on referrals.</p><p>But it raises an interesting systems question.</p><p><em>When organisations cannot deeply investigate every candidate, do recognisable employers, qualifications, referrals and trusted recommendations become increasingly valuable as shortcuts?</em></p><p>Candidates are responding to the same system.</p><p>They optimise CVs.</p><p>They learn keywords.</p><p>They rehearse competency frameworks.</p><p>They use AI to tailor applications.</p><p>They learn the language employers expect.</p><p>As more candidates become better at producing the signals recruitment systems seek, those signals may themselves become less useful for distinguishing underlying capability.</p><p>And that could make trusted information increasingly valuable.</p><p>A known employer.</p><p>A respected reference.</p><p>Someone willing to say:</p><p><em>“I know this person. They’re good.”</em></p><p>Which produces a strange possibility:</p><blockquote><strong><em>The more accessible formal recruitment becomes, the more valuable private signals of trust may become.</em></strong></blockquote><p>The application portal may democratise the ability to enter the queue without necessarily democratising the ability to stand out from it.</p><h3>Where Does HR Actually Sit in This System?</h3><p>This brings me back to one of the questions that originally bothered me.</p><p><em>Has HR become ornamental?</em></p><p>I don’t think that is quite the right question.</p><p>There are two different issues hiding underneath it.</p><h3>Process Authority Is Not Decision Authority</h3><p>HR may own much of the visible recruitment process.</p><p>Publishing vacancies.</p><p>Screening applications.</p><p>Scheduling interviews.</p><p>Maintaining competency frameworks.</p><p>Documenting scores.</p><p>Checking compliance.</p><p>Managing offers and onboarding.</p><p>But that does not necessarily mean HR possesses equivalent influence over the final choice.</p><p>The hiring manager may have a preferred candidate.</p><p>A technical director may strongly recommend someone.</p><p>A senior executive may have already expressed a view.</p><p>So the more useful distinction is:</p><p><strong>Who owns the process?</strong></p><p>versus:</p><p><strong>Who controls the outcome?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hrxs2yVyjKayQYqbK0o01A.jpeg" /></figure><p>The two can coexist legitimately.</p><p>A hiring manager should influence who joins their team.</p><p>A technical specialist should assess technical competence.</p><p>A trusted recommendation can provide useful information.</p><p>The problem arises when the formal system suggests one distribution of decision-making power while the informal system operates through another.</p><h3>Evaluation Authority Is Not Technical Expertise</h3><p>There is a second issue.</p><p>Modern organisations recruit extraordinarily specialised professionals.</p><p>Engineers.</p><p>Data scientists.</p><p>Health specialists.</p><p>Business analysts.</p><p>Cybersecurity professionals.</p><p>Policy experts.</p><p>Transformation specialists.</p><p>Yet the first human gatekeeper may be someone who cannot reasonably possess deep expertise in every profession they recruit.</p><p>So how does the system assess capability it cannot directly evaluate?</p><p>Again, it turns toward what is observable.</p><p>Communication.</p><p>Confidence.</p><p>Structured answers.</p><p>Professional language.</p><p>Behavioural examples.</p><p>Cultural fit.</p><p>These things matter.</p><p>But they are easier to evaluate than deep technical judgment.</p><p>Imagine two candidates.</p><p>One possesses exceptional technical ability but interviews awkwardly.</p><p>The other possesses reasonable technical ability but understands recruitment extremely well.</p><p>They know how to structure stories.</p><p>They understand competency frameworks.</p><p>They know the expected vocabulary.</p><p>Who appears more competent?</p><p>Potentially the second candidate.</p><p>Because the ability to <strong>demonstrate competence during recruitment</strong> can become a proxy for the ability to <strong>perform competently after recruitment</strong>.</p><p>Those abilities may correlate.</p><p>They are not identical.</p><p>The challenge may therefore not be that HR is ornamental.</p><p>It may be that organisations sometimes ask HR to standardise and administer decisions involving expertise it cannot — and perhaps should not be expected to — evaluate alone.</p><h3>And Suits Quietly Gives the Game Away</h3><p>This brought me back to where I started.</p><p>Perhaps I was slightly unfair to <em>Suits</em>.</p><p>Because underneath its celebration of extraordinary competence, the show demonstrates the very system I have been describing.</p><p>Mike Ross is brilliant.</p><p>But brilliance alone does not put him inside Pearson Hardman.</p><p><strong>Harvey does.</strong></p><p>Someone with power sees his ability.</p><p>Someone with access decides that ability deserves an opportunity.</p><p>Someone already inside the institution opens a door Mike could not have opened through the formal process himself.</p><p>His capability matters enormously.</p><p>But capability and access arrive together.</p><p>Even this fictional world in which extraordinary talent seems destined to rise quietly acknowledges something more realistic:</p><blockquote><strong><em>Ability still needs to be seen by someone who can do something about it.</em></strong></blockquote><h3>So Should We Stop Building Skills?</h3><p>This is where the argument becomes personally uncomfortable.</p><p>If visibility, networks and access matter this much, perhaps we have been investing in the wrong things.</p><p>Suppose you have 100 hours available for professional development.</p><p>You could complete another certification.</p><p>Or you could spend those hours developing genuine professional relationships.</p><p>Helping colleagues.</p><p>Publishing useful thinking.</p><p>Participating in professional communities.</p><p>Meeting people in your industry.</p><p>Maintaining relationships with former coworkers.</p><p>Becoming someone whose name naturally occurs when an opportunity appears.</p><p>Which investment produces the greater career return?</p><p>The frustrating answer is:</p><p><strong>It depends on what is constraining you.</strong></p><p>If you cannot perform the work, your constraint is <strong>capability</strong>.</p><p>Build skills.</p><p>If you can perform the work but employers cannot understand how your experience translates, your constraint may be <strong>signalling</strong>.</p><p>Make your capability legible.</p><p>If people can recognise your capability but few trust you enough to recommend you, your constraint may be <strong>social capital</strong>.</p><p>Build genuine professional relationships.</p><p>And if access to certain opportunities depends heavily on sponsorship or institutional influence, you may be encountering <strong>political capital</strong>.</p><p>Another certification will not necessarily solve that problem.</p><p>Moving from incapable to competent has enormous value.</p><p>Moving from competent to highly capable still matters.</p><p>But moving from highly capable to highly capable <strong>plus one more certificate</strong> may produce surprisingly little career movement when the actual bottleneck lies somewhere else.</p><p>The lesson is not to stop developing skills.</p><p>It is to stop assuming that <strong>every career problem is a skills problem</strong>.</p><h3>Merit Still Matters. But It Does Not Operate Alone.</h3><p>Perhaps we were taught to think about careers too linearly.</p><p>Study.</p><p>Qualify.</p><p>Work hard.</p><p>Become good.</p><p>Create value.</p><p>Get noticed.</p><p>Move up.</p><p>But careers do not develop in isolation from the systems through which opportunities are distributed.</p><p>And once opportunity begins compounding, separating individual merit from accumulated access becomes increasingly difficult.</p><p>So perhaps when our careers stop moving, the first question should not automatically be:</p><p><em>What qualification am I missing?</em></p><p>We might ask instead:</p><p><em>Can I actually do the work?</em></p><p><em>Can other people recognise that I can do it?</em></p><p><em>Have enough people seen me do it to trust me?</em></p><p><em>Do the people controlling access know that I exist?</em></p><p>And perhaps the most uncomfortable question of all:</p><p><em>Is there anyone inside the room willing to say my name when I am not there?</em></p><p>Those are different problems.</p><p>They require different investments.</p><p><strong>Creating value and capturing the career benefits of that value are two different problems.</strong></p><p>You still need to become good enough to belong in the room.</p><p>Sometimes, someone still has to open the door.</p><h3>Author’s Note</h3><p><em>This article reflects personal observations and a systems-thinking interpretation of recruitment and career progression, supported where relevant by published research and industry data. It is not intended to suggest that all organisations, HR functions, hiring managers, or recruitment processes operate in the same way. The examples and mechanisms discussed are intended to explore patterns and questions rather than make universal claims about individual hiring decisions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=805ca0d3f973" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Institutions Become Personalities]]></title>
            <link>https://medium.com/@adamkureshi.hr/when-institutions-become-personalities-f93ebaa3bfb4?source=rss-bc3ee0c84b4f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f93ebaa3bfb4</guid>
            <category><![CDATA[organizational-behavior]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Adam Kureshi]]></dc:creator>
            <pubDate>Wed, 12 Aug 2026 14:31:01 GMT</pubDate>
            <atom:updated>2026-08-12T14:31:01.411Z</atom:updated>
            <content:encoded><![CDATA[<h4>Why organizations gradually stop following principles and start anticipating people</h4><p>Some organizations remain remarkably consistent regardless of who occupies the corner office.</p><p>Others seem to change personality every time leadership changes.</p><p>The policies remain largely the same.</p><p>The organizational charts remain largely the same.</p><p>Committees continue meeting.</p><p>Reporting structures remain intact.</p><p>Yet something subtle changes.</p><p>Projects that once moved forward quietly stall.</p><p>Certain conversations disappear.</p><p>Ideas begin to be rewritten before they are ever presented.</p><p>Employees adjust how they communicate, who they involve, and even which proposals they choose to pursue.</p><p>Eventually, an important question changes.</p><p>Instead of asking,</p><p><em>“What does the institution require?”</em></p><p>people begin asking,</p><p><em>“What is leadership likely to want?”</em></p><p>That shift is easy to overlook.</p><p>Yet it may be one of the earliest signs that an institution has begun changing in a far more fundamental way.</p><h3>Institutions Were Designed to Outlast Individuals</h3><p>Every institution is built upon a simple promise.</p><p>People are temporary.</p><p>Institutions should not be.</p><p>Policies replace personal preference.</p><p>Governance replaces memory.</p><p>Committees distribute authority.</p><p>Documented processes create continuity.</p><p>These mechanisms exist for one reason: to reduce unnecessary dependence on any single individual.</p><p>Leadership has always been essential.</p><p>But institutions were never intended to become extensions of individual personalities.</p><p>Their purpose is continuity.</p><p>The strongest institutions are those whose identity survives changes in leadership.</p><h3>When Behaviour Quietly Changes</h3><p>One of the most fascinating aspects of organizational life is that behaviour often changes long before formal structures do.</p><p>The policy manual remains untouched.</p><p>Governance arrangements remain intact.</p><p>Reporting lines stay exactly the same.</p><p>Yet employees gradually begin behaving differently.</p><p>Why?</p><p>Because human beings naturally seek to reduce uncertainty.</p><p>When outcomes become increasingly associated with one person’s preferences, people begin learning those preferences.</p><p>Psychologists describe this as <strong>adaptive learning</strong>.</p><p>We observe repeated outcomes, identify patterns, and adjust our behaviour accordingly.</p><p>Organizations are no different.</p><p>Repeated leadership signals become expectations.</p><p>Expectations become habits.</p><p>Habits become unwritten norms.</p><p>Eventually, people stop optimizing around institutional processes and begin optimizing around anticipated reactions.</p><p>No policy required this shift.</p><p>No committee voted for it.</p><p>The system simply adapted.</p><p>In other words, institutions do not drift because policies suddenly change.</p><p><strong>They drift because people adapt first, and institutions gradually absorb those adaptations.</strong></p><h3>Institutional Personality Drift</h3><p>Recent organizational research has explored how institutions can gradually change through the normalization of small deviations from established practices — a process described as <strong>institutional drift</strong>.</p><p>This article focuses on one specific pathway through which that broader process may occur.</p><p>Throughout this article, I use the term <strong>Institutional Personality Drift</strong> to describe the gradual process through which an organization’s decisions become increasingly shaped by the anticipated preferences, habits, beliefs, and leadership style of influential individuals rather than by its formal governance structures.</p><p>The word <em>gradual</em> is important.</p><p>Institutions rarely become personality-driven overnight.</p><p>They adapt one interaction at a time.</p><p>Until eventually, institutional principles remain documented while day-to-day organizational behaviour becomes increasingly personalized.</p><p>The framework does not argue that strong leadership is problematic.</p><p>It argues that organizations become vulnerable when <strong>leadership influence gradually becomes leadership dependence</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_63i1xe8YpK7QeMqXxheeg.png" /><figcaption><em>One pathway through institutional drift: the gradual shift from principle-based governance toward personality-based decision-making.</em></figcaption></figure><h4>A Simple Diagnostic</h4><p>Ask yourself one question:</p><p><em>If the current leader left tomorrow, how much of the organization’s decision-making would remain unchanged?</em></p><p>If the honest answer is <em>very little</em>, the organization may be experiencing Institutional Personality Drift.</p><p>That single question often reveals more about an institution than dozens of organizational charts.</p><p><em>The moment people begin navigating personalities instead of institutions, Institutional Personality Drift has begun.</em></p><h3>Recognizing the Pattern</h3><p>As one possible pathway through institutional drift, <strong>Institutional Personality Drift</strong> is not unique to one sector.</p><p>It can emerge wherever organizations gradually become more responsive to individuals than to their own governing principles.</p><h4>Public Administration</h4><p>A government department possesses established governance structures, committees, and decision-making processes.</p><p>Over time, staff become increasingly reluctant to advance certain proposals — not because they conflict with policy, but because they believe senior leadership is unlikely to support them.</p><p>Gradually, discussions shift from <em>“Does this align with our mandate?”</em> to <em>“How do you think leadership will respond?”</em></p><p>The institution’s formal architecture remains unchanged.</p><p>Its behavioural architecture does not.</p><h4>Corporate Organizations</h4><p>A newly appointed CEO champions innovation and experimentation.</p><p>Managers quickly begin redesigning presentations, strategic plans, and investment proposals around the CEO’s stated priorities.</p><p>Innovation appears to flourish.</p><p>Yet after the CEO departs, many of those behaviours disappear.</p><p>The organization encouraged innovation.</p><p>It never embedded innovation into its institutional architecture.</p><h4>Universities</h4><p>A university launches an ambitious interdisciplinary strategy.</p><p>Departments increasingly pursue initiatives they believe the Vice-Chancellor personally values.</p><p>Although the strategic plan remains unchanged, academic behaviour gradually aligns more closely with executive preferences than institutional priorities.</p><h4>Healthcare</h4><p>A hospital establishes robust governance processes for quality improvement.</p><p>Yet department heads increasingly delay proposals until they understand the Chief Executive’s likely position.</p><p>Committees continue meeting.</p><p>Formal governance remains.</p><p>But the practical pathway through the system has quietly changed.</p><p>Across all four examples, the organizations appear different.</p><p>The behavioural pattern is remarkably similar.</p><p>Employees are no longer navigating institutions alone.</p><p>They are navigating anticipated personalities.</p><h3>From Institutional Drift to Institutional Personality Drift</h3><p>More than a century ago, the sociologist <strong>Max Weber</strong> argued that one of bureaucracy’s defining strengths was <strong>impersonal authority</strong> — the principle that decisions should derive from the office and its responsibilities rather than from the personality of the individual occupying it.</p><p>More recently, organizational scholars have explored how institutions gradually change through the normalization of small deviations from established practices — a process described as <strong>institutional drift</strong>.</p><p>The framework presented here builds upon these ideas by examining one specific behavioural pathway through which institutional drift can emerge.</p><p>Rather than focusing on changing routines alone, it examines how repeated adaptation to leadership preferences can gradually personalize institutional decision-making without any formal change to governance structures.</p><p>The policies remain.</p><p>The committees remain.</p><p>The reporting lines remain.</p><p><strong>Yet the behaviour changes.</strong></p><p>From the outside, very little appears different.</p><p>From the inside, everything feels different.</p><h3>The Unwritten Operating System</h3><p>Every organization possesses two operating systems.</p><p>The first is documented:</p><ul><li>Policies</li><li>Standard operating procedures</li><li>Governance arrangements</li><li>Delegations of authority</li></ul><p>The second is learned through experience.</p><p><em>“Don’t raise that issue in this meeting.”</em></p><p><em>“Wait until leadership returns.”</em></p><p><em>“Speak to this person first.”</em></p><p><em>“That proposal probably won’t succeed.”</em></p><p>These informal rules rarely begin as dysfunction.</p><p>They begin as adaptation.</p><p>People seek predictability.</p><p>They reduce uncertainty.</p><p>They share successful strategies with one another.</p><p>Over time, those strategies become institutional folklore.</p><p>New employees inherit them.</p><p>Eventually, organizations begin operating through two systems:</p><p>The one they officially describe.</p><p>And the one employees actually navigate.</p><p><em>Organizations eventually develop two operating systems: the one they document and the one employees actually navigate.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dIIpJUPvc7faEjo-GmdGRw.png" /><figcaption><em>How repeated leadership signals evolve into informal norms that shape organizational behaviour.</em></figcaption></figure><h3>The Personality Paradox</h3><p>Perhaps the greatest paradox is this:</p><p><em>The stronger a personality becomes inside an institution, the weaker the institution often becomes without that personality.</em></p><p>This does not diminish exceptional leadership.</p><p>It highlights the difference between influence and dependence.</p><p>Strong leaders build capability.</p><p>Personality-dependent systems build reliance.</p><p>The distinction often remains invisible until leadership changes.</p><p>Only then does the institution discover whether it has been strengthening itself — or merely borrowing strength from one individual.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cw0AsTG0kvFYADl3DC7gYQ.png" /><figcaption><em>The stronger a personality becomes inside an institution, the weaker the institution often becomes without that personality.</em></figcaption></figure><h4>Why It Matters</h4><p>Institutional Personality Drift is not simply an organizational curiosity.</p><p>It has practical consequences.</p><p>As decision-making becomes increasingly personalized, organizations often become less resilient to leadership transitions, less capable of constructive disagreement, and less able to preserve institutional knowledge over time.</p><p>Ironically, the strongest personalities can unintentionally create the weakest institutions if organizational capability becomes concentrated around them rather than embedded within the systems they lead.</p><h3>Diagnosing Institutional Personality Drift</h3><p>Organizations can begin assessing themselves with a few simple questions.</p><ul><li>Do people consult institutional principles before trying to predict leadership preferences?</li><li>Would priorities remain largely unchanged if senior leadership changed tomorrow?</li><li>Have informal rules become more influential than documented processes?</li><li>Are proposals rewritten primarily to align with anticipated personal preferences?</li><li>Has constructive disagreement become less common because people are uncertain how it will be received?</li><li>Could the institution continue making significant decisions without one particular individual?</li></ul><p>These questions do not diagnose individuals.</p><p>They help identify whether organizational decision-making has become increasingly personalized.</p><p>They diagnose organizational dependence.</p><h3>Building Institutional Resilience</h3><p>If <strong>Institutional Personality Drift</strong> describes one end of the spectrum, <strong>Institutional Resilience</strong> describes the other.</p><p>Resilient institutions preserve continuity while allowing leaders to shape direction.</p><p>They distribute meaningful authority.</p><p>Document not only decisions, but the reasoning behind them.</p><p>Encourage constructive disagreement.</p><p>Protect institutional memory.</p><p>Invest in succession rather than replacement.</p><p>Most importantly, they create environments where principles remain more predictable than personalities.</p><p><em>The greatest leaders build institutions that no longer depend on them.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M1ggttaDxpB5hCFPL5VDDA.png" /><figcaption>The organizational capabilities that enable institutions to remain effective beyond individual leaders.</figcaption></figure><h3>Final Reflection</h3><p>Every leader eventually leaves.</p><p>Some retire.</p><p>Some are promoted.</p><p>Some resign.</p><p>Some simply move on.</p><p>Institutions are expected to remain.</p><p>Not because leaders are unimportant.</p><p>But because leaders are temporary.</p><p>The greatest achievement of leadership is therefore not becoming indispensable.</p><p>It is building an institution that continues to make thoughtful decisions, uphold its principles, and serve its purpose long after the leader’s signature is no longer required.</p><p>Institutions become most resilient not when they reflect the personalities of those who lead them.</p><p><strong>They become resilient when they preserve the principles that outlive them.</strong></p><h3>Author’s Note</h3><p><em>Institutional Personality Drift</em> is presented as a conceptual framework that builds upon existing discussions in organizational behaviour, institutional theory, and leadership. Rather than proposing a new theory of institutional change, it explores one specific behavioural pathway through which institutional drift may emerge: the gradual personalization of organizational decision-making around influential leaders.</p><p>The illustrative examples are generalized composites based on recurring organizational patterns across multiple sectors and are intended to demonstrate the framework rather than describe any specific individual, institution, or leadership context.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f93ebaa3bfb4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>