<?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 Jen Briselli on Medium]]></title>
        <description><![CDATA[Stories by Jen Briselli on Medium]]></description>
        <link>https://medium.com/@jbriselli?source=rss-e34fb3b7cd78------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5npNAZ98B1sQrbbVOmqwBQ.png</url>
            <title>Stories by Jen Briselli on Medium</title>
            <link>https://medium.com/@jbriselli?source=rss-e34fb3b7cd78------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:50:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jbriselli/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[What We Love When We Love Complexity]]></title>
            <link>https://medium.com/topology-insight/what-we-love-when-we-love-complexity-98d8e543d04c?source=rss-e34fb3b7cd78------2</link>
            <guid isPermaLink="false">https://medium.com/p/98d8e543d04c</guid>
            <category><![CDATA[anarchism]]></category>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Jen Briselli]]></dc:creator>
            <pubDate>Tue, 20 Oct 2026 01:09:05 GMT</pubDate>
            <atom:updated>2026-11-07T18:05:53.522Z</atom:updated>
            <content:encoded><![CDATA[<h4>Anarchism, complex systems, and the values we smuggle between science and practice</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pybOYLm0A9PTUjCy.jpeg" /></figure><p>The first time I encountered anarchism, I dismissed it.</p><p>I was a teenager, and I was really only reading an aesthetic, a caricature. The most annoying and performative kids at the punk shows I frequented. Black bloc actions that indiscriminately trashed local small businesses alongside the banks and corporate chain storefronts. Poorly written zines full of platitudes and out-of-context Emma Goldman quotes. A whole posture that seemed defined by what it was <em>against,</em> and conspicuously vague about what it was <em>for</em>.</p><p>The self-proclaimed anarchists I knew at seventeen were adolescent, and their anarchism was too. Testing boundaries, defining oneself in opposition to the nearest available authority. Which, to be fair, is how adolescence works. (It’s also how a lot of politics works.) It also hints at Bateson’s concept of <a href="https://en.wikipedia.org/wiki/Schismogenesis#In_anthropology"><em>schismogenesis</em></a>, the way two groups of people sharpen their edges against each other until opposition becomes your whole identity. David Graeber and David Wengrow highlighted examples of this dynamic throughout history in <a href="https://bookshop.org/p/books/the-dawn-of-everything-a-new-history-of-humanity-david-graeber/d53eae7a98f8c703?ean=9781250858801&amp;bkshp-astro=t&amp;utm_source=google&amp;utm_medium=cpc&amp;utm_campaign=dsa_nonbrand&amp;utm_content={adgroupname}&amp;utm_term=dsa-19959388920&amp;gad_source=1&amp;gad_campaignid=12440232635&amp;gbraid=0AAAAACfld40KadMpdqnHhbUiEblcjAVJq&amp;gclid=CjwKCAjw4dDTBhAqEiwAkHYmSl2CprNlg7ZwsOKwtiqoWB3DhrwHqKm4kaA6IoIz28Bh_z2_fwKhSxoCDiwQAvD_BwE"><em>The Dawn of Everything</em></a>; whole cultures defining themselves in escalating reaction against their neighbors or predecessors.</p><p>Yes, anarchism certainly has its schismogenic dimension. So did my initial dismissal of it.</p><p>The ethics behind the aesthetic, though, are not so adolescent, (nor schismogenic). That nuance took me a while to appreciate, but gradually I did, through various professional preoccupations that kept returning me to the same underlying tensions. Education, and what you learn about an institution from inside it while trying to do something it wasn’t built for. Design, and what happens when you follow the implications of use and care and power past the comfortable stopping point of ‘human-centered.’ Systems and complexity science, and what is revealed about human dynamics once your study takes you beyond the poetics of emergence into politically inconvenient territory, when you start taking entanglements of agency and justice seriously.</p><p>And, less professionally but not insignificantly, stewardship in underground DIY music scenes, independent arts, and collectively run community spaces, with all that you learn from the unglamorous work of keeping a small commons functional and answerable to its participants. At every turn, I encountered people whose paths traversed adjacent terrain: labor organizing, community kitchens, disaster response and mutual aid networks, harm reduction initiatives. They seemed to move naturally among worlds I was only beginning to understand were connected.</p><p>Maybe that’s how you come to these ideas in the first place: less often through epiphanies or crises of conscience than through the slowly accumulating evidence of something hiding in plain sight. The dawning recognition that coordination doesn’t necessarily require central authority or even permission. That change rarely follows instructions. That many of the stories we inherit about human flourishing leave out the very stuff that makes it possible.</p><p>You start to recognize questions that different vocabularies ask in common: When should decision making be <em>distributed,</em> and when does it need to be <em>centralized</em>? What can be <em>engineered</em> and what must <em>emerge</em>? Where do indirect <em>constraints</em> shape outcomes more effectively than direct <em>control</em>? Which activities are better guided by flexible <em>principles</em> and which by tightly followed <em>protocols? </em>What do <em>informal networks</em> and <em>formal hierarchies</em> each know that the other neglects? When does making something <em>legible</em> help us understand it, and when does it destroy the thing we mean to see? And <em>power</em>, underneath it all. Is our aim to wield power more benevolently, or make it harder to monopolize in the first place? People have been asking these questions for centuries, but I kept finding myself drawn to the anarchist lines of inquiry, in particular.</p><p>So by the time I began studying complexity science in earnest, a lot of what I encountered felt strangely familiar. Order emerging without an imposed design, knowledge distributed across a network rather than concentrated in a single source, small actions sometimes propagating into effects far larger than expected. Complexity science simply provided a deeper understanding of those dynamics, and why complex change so often resists prediction or a predefined path.</p><p>And for a while I was really intrigued by how much of complexity science and anarchist philosophy seemed to rhyme. Hardly a revelation; folks like Colin Ward were <a href="https://theanarchistlibrary.org/library/colin-ward-anarchism-as-a-theory-of-organization">drawing similar connections</a> between anarchism, cybernetics, and self organizing systems back in the 1960s, and plenty others have explored the relationship since. <a href="https://theanarchistlibrary.org/library/carlos-maldonado-and-nathalie-mezza-garcia-anarchy-and-complexity">One recent paper</a> goes so far as to argue that embracing complexity science ultimately leads toward accepting anarchism itself; (I’m not so convinced but, do let me know?)</p><p>But lately I’ve found myself less interested in simply cataloguing the resemblance than in what that resemblance might reveal about us. Complexity science is an interdisciplinary field with a wide range of ideas and applications. Why do some of them resonate so strongly with certain folks?</p><h4>There’s no ‘A’ in complexity</h4><p>There’s a familiar line that goes: <em>You don’t hate Mondays, you hate capitalism</em>. There might be a variation for complexity enthusiasts:</p><blockquote><strong><em>You don’t love complexity science.</em></strong></blockquote><blockquote><strong><em>You love anarchism.</em></strong></blockquote><p>Obviously, I don’t mean that literally. Maybe you <em>do</em> love complexity science. If nonlinear dynamics and network science and chaos theory make your heart beat faster, like mine, that’s cool. But maybe what you love about it isn’t <em>only</em> the science.</p><p>Some of what people in complexity and systems-oriented circles seem to find most <em>normatively</em> appealing about the science really aren’t normative claims made by the science at all. Obviously I’d never argue that science itself is pristinely value-free; every stage of inquiry from hypothesis to interpretation carries histories, biases, and blind spots. But complexity science does not, by itself, justify the typical normative conclusions so many people want to draw from it.</p><p>Self organization, for example, is just a phenomenon, not an ethical principle or moral virtue. Traffic jams self organize. Languages self organize. So do market dynamics, schools of fish, human crowds; plenty of the resulting patterns can be unpleasant, annoying, even exploitative. Complexity science helps us understand <em>how</em> coherent patterns of emergent behavior arise from local interactions without a central actor directing the whole. It doesn’t prove that people <em>ought</em> to have autonomy, or that democratic arrangements are ethically preferable to authoritarian regimes; you have to supply that conviction yourself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*geZNIqNqhQ1QS2h35oUpJg.png" /></figure><p>There’s a similar temptation with nonlinearity. Effects are not always proportional to causes; under the right conditions, small interventions can have far-reaching consequences no one could have engineered, while large interventions may produce surprisingly little change. But while it’s nice to know there are circumstances where significance isn’t necessarily reserved for whoever controls the biggest lever, complexity makes no promise that modest actions will always have consequential impact, let alone in ways we prefer.</p><p>Or take the concept of path dependence. What exists at present is rarely designed from a blank page. It is the accumulation of earlier choices, accidents, and mutual adaptation. The fact that something has become deeply entrenched does not mean it was the only way things <em>could have</em> turned out, nor that it remains the only way they <em>can evolve in the future</em>. But <em>could have been otherwise</em> doesn’t equate to <em>ought to be otherwise</em>. Recognizing an arrangement is contingent does not tell us whether it is unjust, or what should replace it.</p><p>And if you’re attuned to questions of participation and epistemic justice, complexity science offers plenty of pragmatic reasons to consider distributed sense making and decision making when knowledge is dispersed across a system rather than a single vantage point; but the belief that people ought to have meaningful agency in decisions that affect them is an ethical commitment we bring to the science, not the other way around.</p><p>The same observations about system behavior can support very different politics. Friedrich Hayek, for example, drew on those dynamics of dispersed knowledge and spontaneous order to argue against central economic planning in favor of competitive markets, private property rights, and limited government intervention. Those ideas have also informed right-libertarian and neoliberal arguments for privatization and deregulation that reinforce rather than challenge concentrations of private power.</p><p>Yet anarchists draw on many of the same system behaviors to argue instead for mutual aid, free association, and resistance to concentrated power, whether public or private. A market, after all, is not simply what remains when nobody shapes the conditions. Property, ownership, and contractual exchange are arrangements too; even choosing what gets described as a “free” market implies the choice of <em>which</em> constraints to leave in place.</p><p>All of this is to say: complexity science is politically undetermined; we are not. Some of what’s commonly attributed to complexity really belongs to us humans: belief in the possibility of a truly free democracy, that entrenched arrangements are neither permanent nor inevitable, that meaningful action need not wait for permission, that concentrated power and its potential for abuse always deserves scrutiny — whether in the state, the market, the workplace, or the interactions of everyday life.</p><h4>The A word</h4><p>Translated into the applied vocabulary of systems, none of this sounds terribly provocative. <em>Distributed decision making</em> is pragmatic. <em>Collective intelligence</em> is intriguing. <em>Participatory governance</em> sounds downright progressive. <em>Emergence </em>has appeared on enough LinkedIn slideshows by now to rival <em>complexity</em> itself.</p><p>Utter a word like <strong><em>anarchism</em></strong>, though, and it’s a proverbial record scratch. Now we’re somewhere between a dismissive eye roll and an uncomfortable silence.</p><p>That reaction is totally understandable, of course. <em>Anarchism</em> is heavily charged. My seventeen-year-old self certainly didn’t invent the caricature of a movement that mistakes contrarianism for a political philosophy, and its historical associations with violence and romanticized transgression haven’t helped. Those associations aren’t the whole story, but I understand why some anarchists are more comfortable calling themselves <em>libertarian socialists</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/520/0*DgGDPFcbJvhWXcOX.gif" /><figcaption>“I’m not anarchist, I’m libertarian socialist.”</figcaption></figure><p>Designers also know something about this problem, don’t we? Once <em>design</em> gets flattened into aesthetics or execution, we reach for <em>strategic </em>design, <em>systemic </em>design, <em>participatory </em>design, hoping one more qualifier might protect the practice from being misunderstood. Sometimes it helps, but not often; there are not enough adjectives in modern English to engineer a guaranteed connotation, and sometimes removing the difficult word removes something consequential along with it.</p><p><em>Anarchism</em> may be a terribly imperfect and potentially fraught word, but that freight also prevents questions of power, coercion, and mutual obligation from evaporating into the softer language of cooperation or participation.</p><p>I should acknowledge that much of the anarchist thinking I’m referencing here has developed within broader socialist traditions; similar questions run through feminist, Indigenous, abolitionist, and adjacent practices, with resonances well beyond western political thought in Buddhist and Daoist philosophy among others. I’m not claiming any of these ideas for anarchism; they’ve been discovered, practiced, forgotten, and rediscovered all over the world several times over. But anarchism gives those concerns an explicitly political form, asking how we might build and sustain shared worlds without making domination the price of collective life — and taking seriously the possibility that we can.</p><h4>Power sources</h4><p>Central to that project is the persistent scrutiny of power: where it comes from, what legitimizes it, and when it becomes coercive. But a critical stance isn’t the same as rejecting authority or expertise outright, as anarchism is so often accused of doing.</p><blockquote>Does it follow that I reject all authority? Far from me such a thought. In the matter of boots, I refer to the authority of the bootmaker; concerning houses, canals, or railroads, I consult that of the architect or engineer.</blockquote><blockquote><em>— </em><a href="https://theanarchistlibrary.org/library/michail-bakunin-god-and-the-state"><em>Mikhail Bakunin</em></a></blockquote><p>(There’s a familiar echo for students of <a href="https://thecynefin.co/about-us/about-cynefin-framework/?srsltid=AU7gw4XC-e2bKcJFf1G4P7TxIrYnJwXzrlDhy_gjHGCnkJHC9vXHxtnd">Cynefin</a> here: not everything is complex, and to suggest that expertise may not always be the appropriate basis for authority is not the same as claiming expertise has no place at all; sometimes you really should defer to the bootmaker.)</p><p>The same distinction applies at the level of institutions: rejecting centralized power is not the same as rejecting cooperation or governance outright. Nobel prize winning political scientist Elinor Ostrom <a href="https://www.sciencedirect.com/science/article/pii/S1925209924005436">challenged the supposed inevitability of the tragedy of the commons</a> by documenting how communities sustainably managed shared resources through locally determined rules and flexible mechanisms for monitoring, negotiating, and revising their arrangements.</p><p>Neither privatization nor centralized control is inevitable, nor the only possibilities. Ostrom’s work points instead to forms of governance that are neither structureless nor externally imposed, but made, maintained, and remade by the people living within them. For anarchists, the question is not an oft-stereotyped choice between order and chaos, but one of complexity: how arrangements are shaped and in what contexts, how authority remains accountable and revisable, and whether the people living within an arrangement retain meaningful capacity to change it.</p><p>But who gets to shape an arrangement is only part of the equation; how that arrangement becomes legible to those governing it matters too. In <a href="https://bookshop.org/p/books/seeing-like-a-state-how-certain-schemes-to-improve-the-human-condition-have-failed-james-c-scott/65403c6d4976ca3a"><em>Seeing Like a State</em></a>, (which has somehow become standard issue in the complexity practitioner’s starter pack), James C. Scott explores a familiar phenomenon: when institutions confront a messy living reality and simplify it into categories they can measure and administer. Forest becomes timber inventory, city becomes grid, human practice becomes performance rubrics and KPIs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ru2L6wP36GTR11l6" /></figure><p>The familiar lesson is that a view from above necessarily compresses (or suppresses) something. But Scott presses further: what (and whose) purposes does that legibility serve? It’s not merely about knowledge; by rendering selected aspects of a system measurable, it makes particular forms of intervention and control possible. Meanwhile, much of what actually keeps a system healthy remains stubbornly illegible: tacit knowledge, informal networks, practices that resist standardization. The danger comes when a schematic view is mistaken for the reality itself, and the world is reorganized around what can be seen from above. Interrogating legibility this way, asking not only what it reveals but what forms of power it enables, is characteristic of what Scott would later call his <em>anarchist squint.</em></p><blockquote>I am making a case for a sort of anarchist squint…if you put on anarchist glasses and look at the history of popular movements, revolutions, ordinary politics, and the state from that angle, certain insights will appear that are obscured from almost any other angle. It will also become apparent that anarchist principles are active in the aspirations and political action of people who have never heard of anarchism or anarchist philosophy.</blockquote><blockquote>— <a href="https://press.princeton.edu/books/paperback/9780691271781/two-cheers-for-anarchism?srsltid=AU7gw4Vj1ek2PyeLee2CpvJttpEwAir9s_40SkSV3TA-aE-mE1A74Jsd"><em>James C. Scott</em></a></blockquote><p>And a related dynamic appears when we think about affordances and constraints. One of the things I value most in complexity-informed practice is a shift away from the futility of engineering human behavior itself and toward the conditions from which behavior emerges. Instead of writing better or more persuasive instructions, we attend to the affordances and interactions that influence what is possible and probable.</p><p>But there is nothing inherently liberatory about shaping conditions as a means of influencing behavior. Casinos are excellent at it. So are online social platforms, along with some of the most manipulative and exploitative institutions in human history. Design is an obvious exercise in power here: someone draws the boundary, frames the question, changes the environment so that some actions become effortless, others costly, and still others difficult to imagine at all. Moving from direct intervention to indirect influence and ever more oblique theories of change does not dissolve questions of power. It simply changes where power resides and how it is wielded.</p><p>One such example is in the distribution of contingency. Peter Marris <a href="https://bookshop.org/p/books/the-politics-of-uncertainty-attachment-in-private-and-public-life-peter-marris/2d186eecdae94a88?ean=9780415131728">describes</a> power, partly, as control over contingencies: the capacity to preserve one’s own room to maneuver under uncertainty, often while shifting more of that uncertainty onto people with fewer resources to absorb it. Flexibility for one part of a system can be volatility for another. Adaptive capacity looks rather different depending on whether you get to change direction on your own terms or are expected to absorb the consequences every time somebody else does.</p><p>Complexity science illustrates that uncertainty cannot be eliminated. It does not tell us how its burdens should be distributed, and I’m increasingly wary of the common story in which systems thinkers cast themselves as enlightened inhabitants of an organization while the <em>others </em>remain tragically committed to command-and-control. <em>If only the executives understood complexity.</em> It’s an ironically non-systemic diagnosis of human-system behavior.</p><p>Leaders aren’t empty conduits for systemic pressures; they bring aspirations, values, ambitions, fears, and often perfectly sincere and compassionate intentions of their own. But like all humans they exercise judgment within a web of internal and external influences — financial incentives, regulatory pressures, performance measures, cultural norms — and organizational behavior emerges from interactions among them all, rather than simply adding up to the intentions of the people inside it. That doesn’t make power irrelevant or evenly distributed, of course; some people have far greater opportunity than others to shape those conditions, but no individual simply determines what a system does.</p><p>So, replacing an ‘unenlightened leader’ with a better ‘systems thinker’ doesn’t necessarily change the arrangements producing the behavior or the material distribution of its benefits, burdens, and consequences. Anarchism directs attention toward the arrangement: not just who holds power, but how it arises in the first place. My teenage caricature of anarchism made it legible by flattening it into a posture of refusal, but it’s considerably richer to encounter the less glamorous work necessary for sustaining a living commons on the other side of that refusal.</p><h4>Unfinished business</h4><p>So what do anarchists actually <em>want</em> instead? Where’s the blueprint? What replaces the state? How does anything get decided or enforced? What does the anarchist ‘solution’ look like, exactly? There’s an irony even in the asking, given what complexity science tells us about the limits of specifying futures too confidently in advance. Though Peter Gelderloos does answer some of these questions, in language that could even pass for a modern complexity practitioner’s personal credo:</p><blockquote>We cannot tie down the contingencies of life in a blueprint, nor should we. In an anarchist society, we would have to invent entirely new solutions for wholly unpredictable problems. Should we earn the opportunity, we will do so with joy, getting our hands dirty in the complexities of life.</blockquote><blockquote><em>— </em><a href="https://theanarchistlibrary.org/library/peter-gelderloos-anarchy-works"><em>Peter Gelderloos</em></a></blockquote><p>But resisting the mirage of a blueprint is not the same as surrendering intention, and what emerges will not necessarily remain desirable without ongoing maintenance and calibration. In <a href="https://bookshop.org/p/books/dispossessed-the-50th-anniversary-edition-a-novel-ursula-k-le-guin/28facf9fd19f4a16"><em>The Dispossessed</em></a>, Ursula K. Le Guin complicates any fantasy that such a project would stay true to its founding ideals without conscious tending. <em>An Ambiguous Utopia, </em>indeed… Anarres is an anarchist society, but it’s definitely not a final answer. Its institutions acquire habits; coercion creeps in; arrangements created in the name of freedom begin constraining it. A free society must remain capable of arguing with itself and remaking itself.</p><p>The unfinishedness of anarchism can look like an invitation to disorder, but the idea that a society might never be finished organizing itself is less of a problem if we take complexity seriously. To wit, a society that has finally “arrived,” whose arrangements no longer need to be questioned or remade because we’ve somehow solved the problem of living together, once and for all, would be a very strange thing for a student of complexity science to wish for.</p><blockquote>There is never an end to the future. So it can have no final goal. I am an anarchist not because I believe anarchism is the final goal, but because I believe there is no such thing as a final goal. Freedom will lead us to continually wider and expanding understanding and to new social forms of life. To think that we have reached the end of our progress is to enchain ourselves in dogmas, and that always leads to tyranny.</blockquote><blockquote>— <a href="https://theanarchistlibrary.org/library/rudolf-rocker-the-london-years">Rudolph Rocker</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/0*odpB5xgl3fTpaIYp" /></figure><p>I probably owe at least a partial apology to the badly photocopied zines of my youth, as well as to <a href="https://theanarchistlibrary.org/library/emma-goldman-what-i-believe">Emma Goldman</a> herself, who did once say, with plenty of context:</p><blockquote>‘What I believe’ is a process rather than a finality. Finalities are for gods and governments, not for the human intellect…life is more than formulas.</blockquote><h4>No time like the present</h4><p>If there is no ideal future state (see what I did there?), what does intentional change look like? One anarchist answer is <a href="https://youtu.be/F4tRT8b5txQ?si=ggkapUa5XOCemcRp&amp;t=228">direct action</a>: acting directly on the present with what’s available to us, today. Rather than petitioning authority to make something possible on our behalf, we work with what is already possible from where we are. Direct action shifts the question from <em>who can we convince to give us permission?</em> to <em>what can we make possible ourselves?</em></p><p>This orientation invites a <em>prefigurative practice</em>: making some part of the future we desire more tangible in the present, however partial or provisional. Even without a fully specified future, we can live into the relationships and environments that invoke it — and invest in practices that help more of that future emerge. Graeber put it fairly succinctly: <a href="https://theanarchistlibrary.org/library/david-graeber-fragments-of-an-anarchist-anthropology#toc1">one’s means must be consonant with one’s ends</a>, while Gustav Landauer also applied that logic to the state itself:</p><blockquote>A table can be overturned and a window can be smashed. However, those who believe that the state is also a thing that can be overturned or smashed are sophists. The state is a social relationship; a certain way of people relating to one another. It can be destroyed by creating new social relationships; i.e., by people behaving to one another differently…not the invention of anything new, but the discovery of something actually present, of something that has grown…We are the state, and we shall continue to be the state until we have created the institutions that form a real community.</blockquote><blockquote><em>― </em><a href="https://theanarchistlibrary.org/library/gustav-landauer-weak-statesmen-weaker-people"><em>Gustav Landauer</em></a></blockquote><p>I don’t know about you but there’s a lot I recognize in that sentiment. Much of my professional practice involves helping people loosen their grip on ideal future states to <a href="https://medium.com/topology-insight/finding-the-next-right-moves-e52bb18e0b70">work instead with the evolutionary potential of the present</a>: acting on what is possible now, noticing what unfolds, and continually reorienting toward the aspirational.</p><p>Complexity gives us pragmatic reasons for working this way; direct action and prefigurative practice attach a more demanding ethical proposition: if we desire more humane and liberatory futures, then the interactions through which we pursue change are themselves among the sites where those futures begin taking shape. Even when we share only a general heading toward the future we want, some part of that future should already be reflected in how we travel there.</p><p>Speaking of travel, the Zapatistas have a phrase for moving this way: <em>preguntando caminamos. </em><strong>Asking, we walk.</strong> Not asking first and embarking with the answer in hand. Movement and inquiry happen together, recursively recalibrating each other along the way; <a href="https://www.poetryfoundation.org/poems/58815/traveler-your-footprints">the path is made by walking it</a>.</p><p>Younger me would have filed that under <em>see, they don’t even have a plan. </em>With a few extra years behind me, I can understand why an indeterminate future feels easier to embrace when it’s described by complexity science — and why some of what I now appreciate most about the field is the very stuff teenage me refused to hear when it was attached to anarchist language. What we find compelling in complexity science, or any kind of systems practice, can tell us as much about <em>what we value</em> as it does about the systems we study.</p><p>So… in conclusion,</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*YOQ9djyrSNsVqsl4oko2GQ.png" /></figure><p>Just kidding. I’m not really suggesting that an attraction to complexity makes anyone an anarchist. (Hell, you may not even be a socialist! You could just be using complexity to justify your <a href="https://doi.org/10.1177/07255136261487456">far-right techno-authoritarianism</a>.) But I <em>am</em> suggesting that what we find compelling in the science can reveal commitments that deserve to be acknowledged and examined in their own right, rather than attributed to the science itself. Studying complexity may help us figure out how to navigate without a fixed map, but it does not relieve us of our responsibility for the compass. The values we bring to the work shape which possibilities we notice, which futures we choose to cultivate, and whose expertise we allow to shape those futures.</p><p>So the point isn’t to pretend we can set aside those values in the name of objectivity, but to be more radically honest about them: to name them and put them into dialog with others, notice where the science complicates what we’d prefer to believe, acknowledge where our own choices fall short of aspirations, and keep those commitments open to challenge and revision as we learn our way forward together.</p><p>Complexity science can expand our sense of what is possible. It cannot decide which possibilities are worth pursuing or answer to the futures our choices bring into existence. <strong>That part belongs to us — and, importantly, not to any one of us alone.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*C5OjOHBP9N3btkTV" /></figure><p><strong><em>Jen</em></strong><em> is co-founder and principal at </em><a href="https://www.topologyinsight.com/"><em>Topology</em></a><em>. Find her on </em><a href="https://www.linkedin.com/in/jbriselli/"><em>LinkedIn</em></a><em> and </em><a href="https://www.youtube.com/@topologyinsight"><em>YouTube</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98d8e543d04c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/topology-insight/what-we-love-when-we-love-complexity-98d8e543d04c">What We Love When We Love Complexity</a> was originally published in <a href="https://medium.com/topology-insight">Topology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You Can’t Get There From Here]]></title>
            <link>https://medium.com/topology-insight/you-cant-get-there-from-here-abae8a61d46f?source=rss-e34fb3b7cd78------2</link>
            <guid isPermaLink="false">https://medium.com/p/abae8a61d46f</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jen Briselli]]></dc:creator>
            <pubDate>Mon, 18 May 2026 23:17:19 GMT</pubDate>
            <atom:updated>2026-05-31T15:38:30.729Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>Even with directions.</em></h4><p>So there I am, in the final stretch of a multi-day workshop, and because I am facilitating the encounter, I find myself taking stock of what this team of genuinely sharp and self-aware people have produced together: ideas they’ve surfaced, assumptions they interrogated, commitments they’ve now made.</p><p>One of them grabs a whiteboard marker and starts bullet pointing the would-be summary… and I have that cinematic vertigo moment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/0*c0L0Yz9mrzSrB3XE.gif" /></figure><p>You know the one? Where you’re both <em>in the scene</em> and <em>watching it unfold </em>at the same time? <em>Experiencing</em> and <em>observing</em>? <em>Of</em> and <em>about</em>?</p><p>On one level, we’re a group of people who have arrived at something really meaningful. You can feel it in the room: less performed alignment, more of an authentic recognition. The cohesion that comes from having worked your way through something together that didn’t have an obvious shape at the outset, still doesn’t have a totally clean shape at the end, but has evolved nonetheless. No team bonding theater, just shared sense making and direction setting. Beginning, not concluding.</p><p>On another level, I’m already anticipating what the material stuff, the “evidence” of this collaboration, will look like once it leaves the room. When the day’s <em>insights</em> or <em>next steps</em> or <em>commitments</em> get summarized, presented, forwarded, enacted over time. When the bullet points land in front of someone who wasn’t present for any of it. (Or, god forbid, if a senior exec popped in to see what’s written on the board right that moment…)</p><p>Because, dear reader, the list of big! important! takeaways! being outlined on the whiteboard might look something like this…</p><ul><li><em>Share more concrete examples of success for others to learn from, but ensure they’re abstracted enough that they don’t become context-free templates others feel obligated to copy.</em></li><li><em>Monitor sentiment across stakeholders, customers, and the internal team more consistently, keep a genuine read on how things are landing and evolving, but don’t let it turn into a reporting exercise.</em></li><li><em>Make our direction and thinking visible earlier, as perspective being shared rather than just decisions handed down, so people have something to contribute to and build on.</em></li><li><em>Better understand what our team members actually care about (e.g. their interests, their growth, what’s energizing and what isn’t), before assuming we already know and how to support.</em></li><li><em>Send a meeting agenda before each meeting. Yes, an actual agenda.</em></li></ul><p>If you encountered that list in isolation, say a forwarded email or secondhand retelling, you wouldn’t be wrong to think, <em>…that’s it…? </em>None of these items looks particularly novel to a high functioning organization. Hell, the last one is basic professional hygiene.</p><p>And yet.</p><p>In that room, these bullets weren’t captured as mundane reminders or remedial coaching. They emerged like discoveries. And certainly not because the team had never considered them before; in fact, their leader had likely been nudging them toward some version of these practices for months. They knew. Or at least, they knew <em>of</em>.</p><p>So what actually changed?</p><p>The lazy answer here would be something trite about <em>the journey itself being more important than the destination, </em>which, frankly, belongs on a coffee mug or a cubicle wall, but not in any honest reckoning with complex organizational dynamics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BDPQ3Ck8QlsfbspZSCcCsw.png" /></figure><h4>The long way is the only way</h4><p>There’s a folksy phrase you hear in parts of New England when someone asks for directions between two places that aren’t easy to travel between:</p><blockquote><em>“You can’t get there from here.”</em></blockquote><p>It’s not to imply the destination is literally inaccessible. <strong>It’s that the route you’re imagining — a direct, efficient route — simply isn’t available.</strong> You have to go around. Maybe reorient, maybe approach from a different direction. You might get as far as the next gas station before you ask for new directions. And then do it again a few miles down the road.</p><p>This phrase could probably describe most of the collaboration I find myself supporting these days. Many teams and communities already see what kinds of things could help them achieve their goals. It’s not typically hidden or particularly obscure. Sometimes a leader, a peer, occasionally an outside voice, has even tried to articulate it. And still, months (or years!) pass before anything actually shifts.</p><p>The team can’t quite <em>arrive</em> at what they’re already observing in a way that makes it actionable. Recognition is one thing; enacting is another. The route between them isn’t always straightforward, even when the stepping stones are there: local knowledge, private hunches, the stuff people work <em>around</em> because it isn’t quite safe or specific enough to work <em>with</em>. What’s missing is the <em>configuration</em> that enables those stepping stones to become a path the team can travel together.</p><p>To wit: that metaphorical ‘destination’ isn’t made inaccessible <em>by the current plan</em>; it’s inaccessible <em>from the current arrangement of relationships</em>, which can’t be reconfigured from the outside. It’s dispositional; not a guaranteed outcome, but a shift in what people are likely to notice, try, and sustain. The team has to travel the contours of the system themselves, finding the right granularity to distinguish signal from noise, developing a sense of entanglement and agency. None of that can be charted in advance by someone else on your behalf. <a href="https://www.poetryfoundation.org/poems/58815/traveler-your-footprints">You make the road by walking it</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fwww.youtube.com%2Fwatch%3Fv%3D6R86X4JN2Dg&amp;type=text%2Fhtml&amp;schema=google&amp;display_name=YouTube&amp;src=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fwww.youtube.com%2Fembed%2F6R86X4JN2Dg" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7f66edc31b08d791e16cc270925df62d/href">https://medium.com/media/7f66edc31b08d791e16cc270925df62d/href</a></iframe><h4>Attention is the cost of admission</h4><p>Which brings me back to that room and their bullet points. What got them to that point wasn’t especially mysterious, but it was pursued with attention and care. A combination of narrative sense making to surface what people were actually experiencing, affordance mapping to distinguish what could be changed from what could only be navigated, and a few other bits and pieces to identify where action was already possible or already unfolding under their radar. Then we translated those patterns into small, concrete commitments the team could actually pursue.</p><p>One team I’ve worked with leads emerging technology initiatives at a large tech company, the kind of work that puts you permanently at the edge of the knowable. Uncertainty isn’t something this group tolerates, so much as metabolizes. Which makes them, in some ways, an unusual group to work with. Most of the time, when I introduce the conceptual apparatus of complexity science and sense making traditions to leadership teams, there’s a translation tax — the metaphors are unfamiliar, and the instinct to convert everything into simple terms and concrete steps is quite strong. This group needed none of that. They were immediately at home in the abstract ideas; the metaphors didn’t need unpacking so much as extending and mixing.</p><p>In fact, our challenge ran the opposite direction. When it came time to downshift from the abstract understanding to concrete implications, the footing grew less sure. Not for lack of capability or commitment, mind you. Operating at the frontier of emerging technology simply rewards a particular kind of abstract and expansive thinking. Translating structural implications all the way down into specific, small scale bets and low stakes experiments requires a different muscle.</p><p>This is one of the under-appreciated things about systems-oriented methods like <a href="https://cynefin.io/wiki/Estuarine_framework">estuarine mapping</a> and <a href="https://www.youtube.com/watch?v=577_CXCfHMI">multiverse mapping</a>: they work in <strong><em>both</em></strong> directions. For teams too cozy with abstraction, the process brings things into sharper focus at the level where action is actually possible, with enough rigor that getting specific doesn’t feel like a betrayal of the complexity they’re grappling with. On the flip side, for teams too immersed in the operational, so deep in staffing crises, tech migrations, regulatory shifts, and day-to-day firefighting they barely have time to acknowledge the broader system they’re surviving, the same process widens the aperture. <em>Not</em> toward a view from above or outside the system, but toward a wider field of vision that makes legible how the parts they’re closest to connect to things further out, and where they actually have leverage.</p><p>Different starting points, same dynamic: finding the scale at which action becomes possible.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fwww.youtube.com%2Fembed%2F0fKBhvDjuy0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fwww.youtube.com%2Fwatch%3Fv%3D0fKBhvDjuy0&amp;image=https%3A%2F%2Ffd.xuwubk.eu.org%3A443%2Fhttps%2Fi.ytimg.com%2Fvi%2F0fKBhvDjuy0%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3eacda5d37cc371bbfdc04c42e2ca10d/href">https://medium.com/media/3eacda5d37cc371bbfdc04c42e2ca10d/href</a></iframe><p><a href="https://medium.com/topology-insight/finding-the-next-right-moves-e52bb18e0b70">I’ve written elsewhere</a> about some of my favorite approaches informed by complexity science, but the methods aren’t really the point. They’re just scaffolding for something the team has to do itself. Facilitation in this sense is not about designing, choreographing, or imposing a structure that produces pre-determined outcomes or well-timed epiphanies. It’s about <strong><em>attention</em></strong><em>, </em>and coordinating the conditions under which collective attention can do its work. Noticing what’s present but not yet accessible. At a certain point, the question shifts from <em>what should this group do?</em> to <em>what patterns are already unfolding and what’s enabling and constraining them?</em></p><p>Collaboration here isn’t just about producing better answers, feasible solutions, novel ideas. <em>It’s also the mechanism by which a group develops the capacity to recognize the signals worth acting on in the first place. </em>That capacity doesn’t show up in a summary document; there’s no bullet point for it. So, while that whiteboard list was meaningful to that particular team on that particular Thursday, its meaning isn’t carried in the words themselves.</p><h4>Storebought wisdom has no flavor</h4><p>If you hand a similar list of <a href="https://medium.com/topology-insight/best-practices-are-useless-in-complex-systems-f7797a12071">best practices</a> to a team without the collaboration that produces them, even well-articulated, evidence-backed principles gain little traction. Advice that arrives detached from the situation it’s meant to address tends to remain just that: advice. Easy to agree with. Easy to ignore.</p><p><strong><em>Share more examples. Check in on team sentiment. Send an agenda.</em></strong> Sensible, familiar, inert. The difference is between something you’ve been told and something you’ve worked out for yourself. Same words, different weight because the words are connected to something.</p><p>Take the first one in it’s full form: <em>Share concrete examples, </em><strong><em>but abstracted enough that they don’t become templates or checklists</em></strong><em>.</em> On the surface, that just sounds like “share success stories.” But through their work together, this team now sees exactly why copy-paste success transfer doesn’t work in their context — they’ve spent months traversing this territory, and the work brought that experience to bear. The caveat against turning examples into checklists isn’t just some decorative extra word count bolted onto conventional wisdom. It’s the whole point.</p><p>The same holds for all of it. This team now has a more precise sense of what <em>sentiment</em> actually looks like in their environment, what <em>making thinking visible</em> <em>earlier</em> does to the quality of participation, what something as pedestrian as an <em>agenda</em> changes about a conversation that was previously meandering or performative. What reads like extraneous qualifiers from the outside are doing most of the work on the inside.</p><p>The team didn’t <em>receive</em> these ideas. They <em>grew</em> them. Storebought versus homegrown, which often determines whether an insight becomes a living part of how a team operates, or joins the long list of good advice that everyone agreed with and no one acted on. But it had to unfold at their own pace, on their own terms.</p><h4>Against the compression instinct</h4><p>All of this runs counter to a lot of the pressure in organizations right now. Everything is being asked to move faster, more efficiently, more optimized. And in highly stable, predictable environments, that instinct serves us well. Automate what can be automated. Compress what can be compressed. There’s no virtue in taking the long way around a problem that has a clear, direct solution.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/408/0*HOnZSS8_1lGHh0QH.jpg" /><figcaption>Mona Lisa: Exec Summary</figcaption></figure><p>But in a lot of complex, dynamic environments, what you’re really working toward isn’t a procedure or a protocol. It’s a shift in how the situation and the people inside it stand in relation to each other: co-constituted through interaction, iteration, partial perspectives, reciprocal readjustments, imperfect continuous calibration. The very things efficiency and optimization efforts tend to strip away. Compress all of the human messiness too aggressively, and you don’t just save time, you separate the sense making from decision making. You’re left with well-intentioned platitudes and the kind of context-free garbage that gets turned into a Confluence page and never read again.</p><p>Which is why the outputs, at the end of it all, can look so obvious and embarrassingly simple. And why that simplicity is a red herring.</p><p>The shift you’re looking for doesn’t produce a clean output so much as a different <em>after </em>in which people notice different things, ask different questions, and find different actions available. Really, it’s a recursive series of afters that keep after-ing, shaping each other. What was already present becomes visible. What was already potential becomes available.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6hQdloQgpGvbCoSCPm3kPQ.png" /></figure><p>That whiteboard list is simply shorthand for what’s newly legible to the team that wrote it. Neither the team nor its individuals have been “transformed,” but the topology of relationships between the team and its situation may have shifted. And once a group has seen something together — really seen it, not just agreed with it — it’s difficult to unsee. The landscape of available action changes.</p><p>It’s also why watching something hard-won take the shape of something almost painfully obvious is worth the internal cringe. When something looks so obvious in retrospect, it’s not necessarily because it was trivial. Sometimes it simply means you’ve had to earn the view that makes it so.</p><p><strong><em>Jen</em></strong><em> is co-founder and principal at </em><a href="https://www.topologyinsight.com/"><em>Topology</em></a><em>. Find her on </em><a href="https://www.linkedin.com/in/jbriselli/"><em>LinkedIn</em></a><em> and </em><a href="https://www.youtube.com/@topologyinsight"><em>YouTube</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abae8a61d46f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/topology-insight/you-cant-get-there-from-here-abae8a61d46f">You Can’t Get There From Here</a> was originally published in <a href="https://medium.com/topology-insight">Topology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tolerating (Uncertainty) Intolerance]]></title>
            <link>https://medium.com/topology-insight/tolerating-uncertainty-intolerance-cb47adc36c94?source=rss-e34fb3b7cd78------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb47adc36c94</guid>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Jen Briselli]]></dc:creator>
            <pubDate>Wed, 18 Mar 2026 01:16:43 GMT</pubDate>
            <atom:updated>2026-08-01T20:22:11.353Z</atom:updated>
            <content:encoded><![CDATA[<h4>On mistaken identity and mislocated capacity</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*lCKt23nrA5OQJYi8" /><figcaption><a href="https://www.stephaniejung-photography.com/"><em>Stephanie Jung</em></a></figcaption></figure><p>A fact about me: I’m generally quite comfortable with uncertainty. Perhaps absurdly so. I’ve built a career around navigating ambiguity and people who know me well would probably describe my sense of ease with complexity and not-knowing as one of the more reliable parts of my personality.</p><p>So you can imagine the mild existential crisis that arose when I found myself, queen of ‘sense and respond’, uncharacteristically stressed about, of all things, a snowboarding trip.</p><p>The trip was booked for weeks in advance: drive up Monday afternoon, followed by two full days on the mountain. Then the weather forecasts started converging on a significant storm that same day: 2+ feet of snow, 70 mph winds, extensive power outages, whiteout conditions. And the closer we got to Monday, the more uncomfortable I became. Would we end up trapped at home? Should we try to leave Sunday instead? Could the AirBnB accommodate an early check-in? Could our sitter take the doggos a day early? Or wait it out (but wait for what, exactly)?</p><p>Monday afternoon would almost certainly be a no-go based on driving conditions. But the roads <em>could </em>possibly<em> </em>clear later that evening, or perhaps not until Tuesday morning, or later still. Driving up Tuesday meant sacrificing a day of riding but offered more confidence in the plan. Waiting to see how Monday night unfolded meant possibly salvaging the full trip, (or possibly just stewing in that uncertainty even longer with nothing gained).</p><p>And even if I could answer all of these questions, there was simply no “right” choice to make. The variables were too entangled, the tradeoffs too genuinely fuzzy, and the effectiveness of any decision couldn’t be known until <em>after</em> we’d made it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*lL1VKHk8cdzSjcyV.jpg" /></figure><p>Ironically, weather is one domain where we’ve gotten relatively good at predicting uncertain outcomes. As forecast models converge and the time horizon shrinks, our confidence increases. And this blizzard was, meteorologically, quite well understood by that point. Yet, my discomfort kept rising, not falling, because the uncertainty that mattered to me wasn’t meteorological. It was logistical, relational, practical: a tangle of interdependent decisions that couldn’t be resolved in sequence because they all simultaneously impacted each other.</p><p>The stakes weren’t high in any material sense; no one was in danger, nothing truly important hung in the balance. But they were real in the way that things you care about are real. My intense discomfort arose from the particular combination of my own emotional investment in the outcome and my genuine inability to know in advance whether I was making the right call. I had <em>just</em> enough agency to feel meaningfully implicated in whatever unfolded, and <em>not nearly </em>enough information to feel good about any particular option. And it wasn’t a random occurrence happening <em>to me, </em>such that I could abdicate deciding entirely <em>(cue Rush’s “Freewill”)</em>. It was something I had to actively navigate, with something I cared about waiting on the other side, yet no way to know if I was navigating it effectively. UGH.</p><p>So, we waited. Partly because leaving earlier wasn’t feasible anyway, but also because, intuitively, waiting felt right. Delay the decision, gather info about what was actually unfolding for as long as we could stand it, then act when action presented itself.</p><p>Monday came, it snowed <a href="https://en.wikipedia.org/wiki/February_2026_North_American_blizzard"><em>a lot</em></a>, and as it tapered off that evening, we decided we would attempt to shovel out, drop the dogs at the sitter’s house, and drive up late that night. The moment we committed, before we knew if we could get out of our driveway, or if the roads would be passable beyond our neighborhood, before we knew <em>if it would actually work</em>, I felt <em>immediately</em> more at ease. <strong>The uncertainty hadn’t been resolved, but the decision had.</strong></p><p>Happily, we made it to our cabin several hours later and enjoyed both days on the mountain as planned. Yet even though the uncertainty I’d been grappling with all week ultimately resolved into the outcome I’d wanted all along, the <em>relief had arrived hours earlier,</em> in the moment we’d simply decided to make the attempt.</p><p>And I’ve been thinking about it off and on since then, because it gets at something that conventional framing around uncertainty tolerance and comfort with ambiguity tend to miss entirely: what made the difference wasn’t my capacity to <em>endure or tolerate</em>, as much as the context and conditions that made a decision legible in the first place.</p><p><strong>Uncertainty tolerance </strong>has become something of a modern virtue. Leaders are expected to possess it. Teams are encouraged to cultivate it. Competency frameworks make it an explicit developmental goal, and it gets invoked (with a hint of derision) whenever someone seems to struggle with ambiguity or pause before acting without full information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QSGK6ZyE-uXsLOo2KPPKZQ.png" /></figure><p>On the surface, this makes sense. Of course we want people who can function without all the answers. Of course we want teams that don’t seize up when conditions shift. But in practice, uncertainty tolerance and its variations are becoming a convenient way to individualize what are often structural and relational dynamics — locating the problem in people rather than in patterns of interaction. And that instinct, well-intentioned as it may be, ends up doing more harm than good, because it carries the implicit assumption that people are somehow deficient, and that the right intervention will supply what’s missing. That’s not just theoretically imprecise, it’s the wrong starting point, and it tends to produce exactly the kind of external, top-down change efforts that are least likely to succeed.</p><p>When someone “struggles” with uncertainty, what’s actually happening is hardly a simple character defect. It’s a convergence of cognitive reflexes, social dynamics, emotional regulation, identity protection, and institutional incentives all folding into each other at once. The research across cognitive, systems, and decision sciences paints a much more textured picture. A few of the more common constructs here are worth a look, not as a definitive catalog, but because each one illuminates something the umbrella term flattens.</p><p>For starters, <a href="https://doi.org/10.1016/j.beth.2025.08.009"><em>intolerance of uncertainty</em></a>, widely studied in anxiety research, captures how prolonged not-knowing can trigger genuine physiological distress. It’s not a matter of mindset or willpower; it’s a nervous system response. When ambiguity registers as threat, expansive thinking becomes more difficult because your body and brain are managing a real internal state, not just choosing rigidity. The capacity to remain cognitively available while the body is under stress <em>can</em> be cultivated, but not through slogans about resilience or simply setting an intention to embrace serendipity.</p><p>Then there’s <a href="https://en.wikipedia.org/wiki/Closure_(psychology)"><em>need for closure</em></a><em>,</em> which describes our tendency to seek firm answers and to resolve ambiguity. Especially when time pressure, identity threats or other risks arise, we seize on the first plausible explanation and tend to freeze it in place. In stable, predictable environments, this reflex can be beneficial: fast convergence supports efficient coordination. But in complex, dynamic environments, premature closure is counterproductive and can reinforce brittle narratives that harden too quickly, blinding teams to what is still emerging.</p><p>Meanwhile<em>, </em><a href="https://en.wikipedia.org/wiki/Need_for_cognition"><em>need for cognition</em></a><em> </em>measures how much someone enjoys effortful, deep thinking. Some people tend to find extended sense making energizing; others find it exhausting and aversive. But even people who typically enjoy thinking deeply will curtail their inquiry in environments or cultures that reward speed and penalize hesitation. What looks like low tolerance for ambiguity often turns out to be quite rational calibration to incentive structures. The environment is doing a lot of the work, even when we’re blaming the individual.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yD2mwcXlcVUn0qMI.jpg" /><figcaption><em>I feel the need… the need for closure. Or cognition. Or both?!</em></figcaption></figure><p>Decision science adds a further distinction with <a href="https://en.wikipedia.org/wiki/Ambiguity_aversion"><em>ambiguity aversion</em></a>, the preference for known risks over unknown probabilities, (famously demonstrated in the <a href="https://en.wikipedia.org/wiki/Ellsberg_paradox">Ellsberg paradox</a>). Many people are quite comfortable managing risk but uneasy when probabilities themselves are unclear. You’ll hear it in requests to “just give me the numbers.” And yes, numbers will materialize, but those numbers are often provisional. Converting the unknown into something that feels calculable soothes anxiety, even at the cost of accuracy.</p><p>There’s also <a href="https://en.wikipedia.org/wiki/Self-efficacy"><em>self efficacy</em></a>, a belief in one’s own capacity to navigate a specific context (not, as it’s sometimes misunderstood, an overarching sense of self-confidence). It develops through accumulated experience acting without perfect information, muddling through uncertain outcomes, discovering that setbacks are survivable, and learning to regulate our responses under pressure.</p><p>The field of <a href="https://naturalisticdecisionmaking.org/">naturalistic decision making</a> enriches this notion: experienced decision makers don’t navigate uncertainty better because they’re more tolerant of it, but because experience over time has made more of it legible to them. Pattern recognition, built through repeated real-world exposure, does the work that tolerance alone cannot.</p><p>When you’ve repeatedly worked through ambiguity and lived to tell the tale, you develop something more useful than uncertainty tolerance. You develop deeper <em>trust in your own capacity to learn your way forward.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*Amq3sh0e_yveelfK.gif" /><figcaption>the patented Jen Briselli method for increasing uncertainty tolerance</figcaption></figure><p>What’s worth noting across all of these constructs is that even seemingly stable individual differences are actually quite responsive — to context, to history, to the conditions immediately surrounding them. None of them operate in a vacuum.</p><p>And there is always a power dimension at work. In <a href="https://books.google.com/books/about/The_Politics_of_Uncertainty.html?id=NaSFAgAAQBAJ"><em>The Politics of Uncertainty</em></a>, Peter Marris observes that uncertainty is never evenly distributed. Those with more power or social capital are often able to offload contingency and complexity onto others. Leaders experience ambiguity differently than frontline staff. Competitive systems tend to push volatility downward and structures that concentrate risk can erode reciprocity and trust among those with the fewest buffers.</p><p>Invoking “uncertainty tolerance” without examining how that uncertainty is socially constructed and materially distributed, (i.e. who bears its social, emotional, and professional costs), camouflages an asymmetry in developmental language and can easily become an expectation that those with less structural power simply absorb more volatility without support. It is always easier to remain open to uncertain outcomes when someone else carries the consequences of not knowing.</p><p>Meanwhile, some organizations have gotten quite good at <em>signaling</em> comfort with ambiguity while designing, or at least perpetuating, incentive structures that punish it. Leaders can speak eloquently about embracing ambiguity in the all-hands meetings and then visibly reward the people who project false certainty in the rooms that matter afterward. Teams learn quickly what the culture actually values, whatever the mission statements or competency frameworks say. This gap between the espoused and the enacted isn’t always deliberate, but it lands hardest on the people already carrying the most uncertainty.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vv9JrItfBwW1uWPu-2HFAQ.png" /></figure><p>To add a bit of poetic license, John Keats described a related but perhaps usefully distinct idea when he wrote about <a href="https://www.poetryfoundation.org/articles/69384/selections-from-keatss-letters"><em>negative capability</em></a> as the capacity to remain “<em>in uncertainties and doubts without any irritable reaching after fact and reason.”</em> While a generic sort of uncertainty tolerance might suggest someone can still function <em>despite not knowing</em>, negative capability suggests that someone can remain open <em>without needing to resolve the not knowing.</em> The difference is subtle but consequential: tolerance regulates anxiety; negative capability restrains premature interpretation.</p><p>All that said, negative capability isn’t the solution, and neither is some idealized state of high ambiguity tolerance and low need for closure.</p><p>Organizations need to make decisions. Teams need to converge on shared plans that enable action. At some point, staying open becomes its own kind of avoidance, perhaps even a form of spiritual bypassing. The real question isn’t whether closure is warranted, but what drives it: genuine readiness or simply the discomfort of waiting. Learning, or comfort?</p><p>And many well loved playbooks and methodologies, however sophisticated, are essentially closure-generating machines. They can help groups converge smartly and effectively, but in ambiguous environments they can also become anti-anxiety therapies; we reach for them less because the kairos is there and more because the uncertainty has become socially intolerable. If you’ve ever observed a group claim to embrace complexity and then immediately seize on the first plausible conceptual model or process map they can get their hands on, you’ve seen that dynamic in action. The posture looks like rigor but it’s often relief.</p><p>Of course, the concept of <a href="https://doi.org/10.1016/j.hrmr.2017.01.001"><em>psychological safety</em></a> is relevant here too. The ability to sit with not-knowing depends heavily on whether the social environment makes it safe to be visibly uncertain — to float a half-baked idea, to say “I don’t know,” or to change your mind publicly without consequence. But it tends to be misunderstood as something you design for rather than something that emerges. It accumulates across thousands of small interactions over time: who gets interrupted, whose uncertainty is met with curiosity rather than judgment. It can’t be engineered because it emerges from culture — and culture is something everyone in a system is continuously making and being made by, whether they’re aware of it or not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hFJDqjJRQWPL7IrBia-phA.png" /><figcaption>Just look at her uncertainty tolerance!</figcaption></figure><p>What happens if we flip things around and ask: <strong>where and how do people handle uncertainty well?</strong> Because most people do, somewhere. Think about how we engage uncertainty in games, sports, and creative play. Many people who find not-knowing genuinely intolerable in one setting will quite willingly enter uncertain conditions (<em>and enjoy them!</em>) in another. When the stakes aren’t too high, the environment feels safe, and feedback is immediate, the uncertainty can be generative rather than threatening.</p><p>The question, then, is not whether someone tolerates uncertainty in the abstract, but under what conditions they&#39;re expected to do so. Games and sports and play aren&#39;t just analogies. They&#39;re evidence that what might look like a personality trait is really an emergent capacity, present in most people but mediated by the constraints and affordances of whatever they&#39;re participating in. Which raises a more useful question than <em>&quot;how do we build tolerance?&quot; </em>— namely, <strong><em>how do we cultivate the conditions that make not-knowing more navigable than it is threatening?</em></strong></p><p>Taken together, what we colloquially call uncertainty tolerance isn’t a single psychological trait. It’s an emergent phenomenon that arises from the ongoing negotiation between nervous system, cognition, history, social norms, incentive structures, environmental affordances, and power dynamics. Not located in the person, not located in the system, but continuously constituted by the entanglement between them.</p><p>Which means if we want to authentically engage with ambiguity, to stay with a question long enough to actually learn something, the challenge is less about developing individuals and more about our own participation in the broader web of relations that make genuine not-knowing socially and materially acceptable. Helping each other notice and avoid premature convergence. Sharing and navigating uncertainty together rather than strategically redistributing it elsewhere. Less performed confidence and more actual not-knowing, changing what’s permissible for everyone around us.</p><p>And it means creating spaces where that ambiguity is affordable: where the stakes are calibrated to the team’s current capacity rather than fantasy aspirations, where healthy exploration can happen without strings attached, and where that practice becomes continuous enough to gradually shift what feels possible.</p><blockquote><em>In truly complex domains, the aim isn’t to achieve certainty about where you’re headed. It’s maintaining enough clarity about direction, and enough degrees of freedom, that the path becomes legible as you move through it — and that commitment never outpaces learning.</em></blockquote><p>Of course, none of this holds when the system itself is too compromised to support it. There are environments where volatility has exceeded capacity, where reciprocity has eroded beyond repair, where uncertainty loses its generative potential and becomes a cumulative load the system can no longer absorb. In those environments, introducing new practices or modeling not-knowing from the front of the room doesn’t help. The structure needs attention first: the collaboration patterns, the distribution of decision rights, the concentration of risk. Pretending otherwise, asking people to be more tolerant or more open, (or “<a href="https://www.chicagoreview.org/oli-mould-against-creativity/"><em>more creative</em></a><em>”</em>), doesn’t just miss the point. It moralizes resilience in ways that obscure structural failure.</p><p>Which brings us back to the individual, to consider where you already navigate uncertainty well, because the capacity is rarely absent, just contextually constrained. What makes not-knowing feel navigable to you in those contexts? Lower risk? Real-time feedback? A sense of play, or challenge, or flow? Confidence in your ability (and your support network) to recover from setbacks? Those aren’t personality quirks. They’re clues about what makes uncertainty manageable, and what it might take to extend those conditions into the places that currently feel intolerable.</p><p>And then there’s the outward-facing version of the same question. You yourself are part of the environment that <em>mediates</em> <em>someone else’s experience of uncertainty. </em>Not because you hold special authority over their experience or because you can coach them toward some heightened state of openness, but because conditions are co-created, continuously, through interactions you participate in. What you discreetly tolerate or openly celebrate, what you meet with curiosity rather than resistance; all of it shapes the landscape others navigate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*i0g5RAWxVm9-yxRY" /><figcaption>I’m not your context, you’re my context!</figcaption></figure><p>Underneath all of it, the neural systems that respond to threat are largely the same ones that activate with novelty and curiosity. Uncertainty can register as something to brace against, or as something worth moving toward. The difference isn’t a matter of character. It emerges from the relationship between trait and state, history and present moment, individual cognition and collective culture — and what the environment around you makes possible or forecloses.</p><p>That snowstorm wasn’t a pass/fail test of my uncertainty tolerance. It was just an example where all of these dynamics became briefly, uncomfortably tangible — the entanglement of stakes and agency and conditions, my nervous system doing its thing, the relief arriving not when the uncertainty cleared but when a decision finally became legible. An everyday illustration of a uniquely human phenomenon.</p><p>Uncertainty tolerance, as a trait to develop, is always a bit of a red herring. The question isn’t one of tolerance at all, but of our relationship with uncertainty. It’s a relationship we’re always negotiating, with ourselves, with each other, and with the world around us.</p><p><strong><em>Jen</em></strong><em> is co-founder and principal at </em><a href="https://www.topologyinsight.com/"><em>Topology</em></a><em>. Find her on </em><a href="https://www.linkedin.com/in/jbriselli/"><em>LinkedIn</em></a><em> and </em><a href="https://www.youtube.com/@topologyinsight"><em>YouTube</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb47adc36c94" width="1" height="1" alt=""><hr><p><a href="https://medium.com/topology-insight/tolerating-uncertainty-intolerance-cb47adc36c94">Tolerating (Uncertainty) Intolerance</a> was originally published in <a href="https://medium.com/topology-insight">Topology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Head Up, Feet Moving]]></title>
            <link>https://medium.com/topology-insight/head-up-feet-moving-b56e60867190?source=rss-e34fb3b7cd78------2</link>
            <guid isPermaLink="false">https://medium.com/p/b56e60867190</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Jen Briselli]]></dc:creator>
            <pubDate>Wed, 31 Dec 2025 01:07:04 GMT</pubDate>
            <atom:updated>2026-01-09T23:02:21.965Z</atom:updated>
            <content:encoded><![CDATA[<h4>Complexity isn’t a spectator sport.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*hhHpJ29MtK_tJn4S.jpeg" /></figure><p>I usually don’t like sports metaphors. Most of them flatten a highly nuanced field of improvisational human dynamics into reductive analogies or leadership tropes. And some are downright weaponized as business clichés.</p><p><em>Skate to where the puck is going, not where it’s been.</em></p><p>Ok. Thanks?</p><p>However, here’s where I disclose that I play ice hockey. And, because I love a good contradiction, I’ll also admit that I think quite a lot about how metaphorically generative the game of hockey really is (especially if you’re someone who also thinks a lot about complex human systems). Maybe it’s just ye olde apophenia, but I find so much about hockey echoes the very same dynamics we navigate in modern collaboration and decision making: <strong>uncertainty, adaptive capacity, distributed cognition, emergence.</strong></p><p>It’s not just that hockey can stand in as metaphor for complexity (a worthy contender if you need to give jazz ensembles and starling murmurations a break). It’s that it’s one of the most vivid and embodied ways I’ve personally experienced it.</p><p>If you look past the leadership tips in airport bookstore memoirs, ice hockey (<a href="https://www.routledge.com/Complexity-and-Control-in-Team-Sports-Dialectics-in-contesting-human-systems/Lebed-Bar-Eli/p/book/9781138833852">like many team sports</a>) is unmistakably a <a href="https://en.wikipedia.org/wiki/Complex_adaptive_system">complex adaptive system</a>. And like any complex system, it can’t be effectively understood by stepping back and analyzing it from a distance. You come to understand it, and influence it, from <em>within it</em>: by participating, noticing, and adjusting, in real time, in as many contexts and combinations of interactions as possible.</p><p>So, I’m less interested in hockey as analogy, and more intrigued by hockey as an everyday site of emergence and entanglement. Even if you don’t play or watch the game, hockey offers a surprisingly relatable glimpse into interdependence and collective intelligence. These aren’t just abstract concepts; they’re realities every player experiences, moment by moment.</p><h4>Skating on thin metaphors</h4><p>If we look more seriously at that quote about skating to where the puck is going, it actually carries a deceptively simple assumption: that you can predict the puck’s future location by reading the current conditions and extrapolating accordingly. But in real-time play, it’s rarely about predicting a sequential outcome or executing predefined best practices. Instead, you position yourself to respond to a range of possibilities, most of which you can’t fully anticipate until they begin to unfold.</p><p>It’s not about asking where the puck <em>will be</em>; it’s about reading the spaces where it <em>can</em> and <em>can’t</em> be, sensing how that space is shifting, and making decisions that shape those dynamics. Your actions aren’t just a reaction to the current situation, you’re co-creating it and are shaped by it in turn. The relationship is entangled and reciprocal.</p><p>This is one reason why some of the most productive hockey players aren’t necessarily the fastest or strongest individually. They’re just highly attuned to the game, able to sense what’s emerging, rather than merely reacting to what’s already occurring. Years of play have honed their attention to subtle cues: the angle of a teammate’s stick, a shift in an opponent’s weight, a change in rhythm around the play. Their body recognizes and responds to familiar configurations before their brain has time to clock it. It’s not a conscious calculation, just an intuitive response shaped by years of experience and pattern recognition.</p><p>The best players, and teams for that matter, are able to anticipate without overcommitting, staying agile enough to pivot when the play takes an unexpected turn. And whether they realize it or not, they’re enacting a kind of complexity-informed practice, engaging with a dynamic system they can’t control holistically but can influence locally by staying responsive to what’s unfolding.</p><p>Which is why the puck metaphor, for all its familiarity, doesn’t really illuminate much. But even people who <em>really</em> know hockey — players, coaches, analysts — still reach for pithy quotes because they’re easier to convey than the messier reality: constant micro-adjustments, distributed sensing, making choices that don’t just respond to patterns but participate in creating them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1td9p2pxowfPPN852JZ2uA.png" /></figure><p>Take another common piece of hockey wisdom: <em>“Keep your head up.”</em> It sounds like generic motivational advice to stay positive, don’t get discouraged. But on the ice, it means something very different: rather than looking down at the puck to monitor your own stickhandling (a natural instinct, especially for newer players), you’re trained to keep your gaze up, to stay aware of the play developing around you so you can sense where pressure is coming from, read your teammates’ positions, and avoid getting blindsided. The phrase gestures toward situational awareness and weak signal detection, but like most sports shorthand, it can’t quite capture the embodied, relational practice it’s actually describing.</p><p>Then there’s <em>“Keep your feet moving.” </em>Again, it sounds trite. But on the ice it means don’t plant yourself and wait for the play to come to you. Keep skating, even if you don’t have the puck, even if you’re not sure where the play is headed yet. Stay light, stay ready. Not to be in constant motion for its own sake, but maintaining agility so you can pivot more easily. Going from stop to start takes more energy than redirecting movement that’s already happening. Static players get caught out of position. Moving players can adapt.</p><p>If any of this sounds familiar to you, it should. The same habits that reduce hockey to <em>“skate where the puck is going”</em> are what reduce our understanding of complex systems into 2x2s and iceberg diagrams. These simplifications miss the point: you can’t engineer specific outcomes, but you can work with constraints and dispositions to influence what becomes possible.</p><h4>No playbook, no problem</h4><p>Some folks assume hockey works like football, with a literal playbook: pre-established formations, tightly scripted choreography, each player executing a defined role within a well-rehearsed plan. In some ways, it’s <a href="https://thecynefin.co/about-us/about-cynefin-framework/?srsltid=AfmBOoplqFkDxEaG-RdcZAB-Wp7BaMpbfUDF8Y0basYuiDsDtwbutBG1">complicated</a>, but ordered; you can break it down, assign parts, and rehearse accordingly. In football, you huddle, plan the next move, and try to execute it more or less as drawn up (until, of course, the defense, the weather, or plain old human instinct disrupt the play and force more improvisation).</p><p>But hockey doesn’t work that way. It’s less orchestrated and more fluid from the start. You train foundational skills and rehearse common patterns to build chemistry and muscle memory, but once the puck drops, you’re adapting. What structure does exist is context-responsive, essentially a shared fluency that allows for real-time coordination.</p><p>Football rewards executing the playbook, hockey rewards sensing the play. <strong>And that’s a much better analogy for how most complex human systems actually work.</strong></p><p>You’ve probably seen this in your own collaboration: people looking for the playbook, the process map, grasping for the solid object in places where there’s only fluid dynamics to be found. There’s no harm in wanting clarity, but they‘re applying a complicated-systems approach to a complex-systems reality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uwTOncGrgsWTBx9LrFmlwA.png" /></figure><p>In hockey, the dynamics shift constantly across 60 minutes of play. Even strength play works differently than a power play. Penalty kill dynamics are different again. 3-on-3 overtime adds new constraints, and new possibilities. Even within the span of a single shift, your individual role flexes depending on who you’re on the ice with, what zone you’re in, what just happened, and what might happen next.</p><p>Even the language of hockey reflects this fluidity. While teams may practice a few <em>set plays</em> for specific scenarios like faceoffs and penality kills, they’re far more likely to talk about <em>systems</em>: A 1–2–2 forecheck, a neutral zone trap, the cycle down low. These aren’t scripted sequences but flexible scaffolding that enable real time decision making without dictating outcomes in advance.</p><p>The structure is there, but it’s not static; it’s an evolving set of relational patterns. Like much of our day to day lives, hockey is both complicated and complex. The complicated parts can be trained. The complex parts must be sensed.</p><h4><strong>Come for the beer league, stay for the epistemology</strong></h4><p>Much of this has been made clearer for me because I came to the game late. Though I watched hockey as a fan, I didn’t grow up playing. I started skating in my late 20s, which means I don’t have the same muscle memory as people who’ve been on skates since toddlerhood. My stickhandling won’t turn heads, and my shots don’t challenge most goalies. But I do possess a fluency for the dynamics of the game and I know how to respond to whatever scenario I find myself in. I can track the shape of a play, notice when the energy shifts, sense when to step up and when to hang back.</p><p>Even when I’m one of the slower, smaller skaters surrounded by faster, larger men, my anticipatory positioning keeps the puck out of dangerous places. Despite my unremarkable skating, passing, and shooting skills, when I turn off my goal-oriented pre-meditative brain and rely instead on a visceral connection to what’s happening around me, I can often hold my own with players that are objectively more skilled. (It doesn’t hurt that we’re talking recreational beer league hockey here, but the principles hold true across any type of dynamic human environment.)</p><p>I include this shameless humblebrag because it highlights something important: in complex systems, technical skill doesn’t always translate directly into impact. The most consequential contributions aren’t necessarily <em>visible</em> in a highlight reel or <em>measurable</em> in the post-game stats. It’s also in the positioning that prevented a scoring chance, the pass that set up the pass that set up the goal, the timely read that kept your team in the zone. The same holds true in your organization; it’s not just the features you ship or the updates that appear in a status dashboard. It’s the <a href="https://medium.com/topology-insight/invisible-infrastructure-5314323a91cb">relational dynamics, the informal networks</a>, the <a href="https://www.amazon.com/Streetlights-Shadows-Searching-Adaptive-Decision/dp/0262516721/ref=asap_bc?ie=UTF8">experience driven decisions</a> about when to act or wait and see.</p><h4>Line change, phase change</h4><p>Good hockey doesn’t require a god’s-eye view of the system. In fact, if players skated with the omniscience of the broadcast booth, the game would suffer for it — less creative, less emergent, more like a video game than the real thing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/454/1*a2UG2LEt5njBlsST9605Ww.gif" /></figure><p>At ice level, you can’t see behind you without turning your head, but you can sense where players are, indirectly, based on the movement of others. When I’m skating, I don’t perceive everyone’s trajectories as literal vectors, but I do register them. The knowing is embodied and extended: distributed across my own positioning, my teammates’ actions, and the shared dynamics unfolding around us.</p><p>And the game does more than shift continuously, it <em>reconfigures</em> depending on context: spatial (which zone you’re in), temporal (first period vs. final exhausted minutes), or structural (full strength, power play, penalty kill). These phase shifts aren’t just a backdrop; they determine what’s possible and what’s required.</p><p>Roles, too, are context-dependent. Whether you’re “on offense” or “on defense” isn’t just about your formal position, it depends on puck possession, location, and timing. It’s more <a href="https://www.amazon.com/Obliquity-Goals-Best-Achieved-Indirectly/dp/0143120557">oblique</a> than simply <em>try to score</em> or <em>get the puck away from the other team</em>. On offense, you’re working to increase degrees of freedom: opening space, expanding options, creating possibility. On defense, it’s the opposite: collapsing space, reducing angles, limiting what the other team can do.</p><p>Critically, these phase shifts aren’t governed by explicit criteria or concrete protocols. You’re always sensing and adjusting with incomplete information, in motion, under pressure. This is what Ann Pendleton-Jullian and John Seely Brown <a href="https://www.desunbound.com/">call whitewater decision-making</a>: navigating conditions that are too dynamic to allow for detached analysis.</p><p>And sure, the individual skills matter, but only if applied at the right moment. A slick toe drag or powerful slapshot can change a game, but I’ve seen players with great hands struggle when things get physical or the typical structure dissolves. They might know how to execute a move they’ve drilled, but not how to navigate the chaos. Hockey punishes players who rely on ideal conditions, because ideal conditions are rare.</p><blockquote>The game demands that you see what’s happening, <em>not just what’s supposed to happen.</em></blockquote><h4>Statistical models don’t backcheck</h4><p>In a fashion surely familiar to students of complexity science, different vantage points reveal different patterns — and obscure them too. Casual spectators without deeper understanding of the game’s dynamics tend to reduce what they see to something simpler and more linear than what’s actually unfolding.</p><p>Watch any live game and you’ll hear a chorus of frustrated fans yelling <em>“just shoot!”</em> whenever a team cycles the puck during a power play. They’re not wrong, eventually someone needs to shoot, but they don’t see how the team is working to create space and disrupt defensive patterns to better identify when a shot is likely to succeed. This is what happens when people converge on a solution before understanding the dispositional state of the system.</p><p>Then there are the folks who love the game through stats, but stats can privilege what’s measurable over what’s relevant. You can track zone entries, passing sequences, shot probabilities. You can review plays in slow motion, map heat zones, calculate expected goals. For players, advanced analytics can offer new perspectives, highlight patterns or anomalies worth exploring. But the stats aren’t the game, and they can tempt us toward misplaced certainty, mistaking correlation for causation, modeling for prediction, insight for control.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hQ6u_tyujEh0LYxO.png" /><figcaption>You know what Korzybski would say…</figcaption></figure><p>The game can’t be won through algorithmic precision. What matters is how players assess their reality on the ice and adapt accordingly. This gap between what can be measured and what must be sensed isn’t a failure of analysis; it’s a fundamental property of complex adaptive systems. And it’s a reminder that if you want to operate with greater adaptive capacity, at some point you have to move beyond analysis and start participating.</p><h4>What’s in a game?</h4><p>Something else happens as you play across contexts: the illusion of clean boundaries dissolves. Where do you end and your team begin? Where do two-minute shifts become the game? Where is the edge between part and whole?</p><p><strong>Where’s the hockey? </strong>Is it in the puck? The players? The rules? The ice? The rivalries, the history, the daily practice, or annual draft?</p><p>It’s in all of them — and none of them.</p><p>Hockey emerges from the interactions, in the tension and timing and temporary configurations of elements that constrain and enable each other in context. A pass only means something in relation to who’s open, where the defense is positioned, what the score is. The same physical action in a different configuration creates entirely different possibilities. What each component <em>is</em> depends on its relation to everything else.</p><p>The answer is: it depends on context. It’s always: it emerges.</p><p>But don’t mistake the poetics of <em>emergence</em> for passivity. Recognizing that a system has emergent properties doesn’t absolve you of agency. As a player, you’re both of the system, and participant in it, simultaneously constrained by the dynamics around you and actively modulating those very constraints through your actions. You open up passing lanes or close them down. You create space or collapse it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*Ycnb_FEr8u5CXa1j.gif" /><figcaption>Even your absence changes the game.</figcaption></figure><p>You don’t control outcomes, but you shape the conditions that give rise to them. And if you’re paying attention, you see that influence in complex systems isn’t about prediction or precision — it’s about positioning. Staying agile on your feet and ready to act on what’s becoming possible.</p><p>Emergence isn’t permission to do nothing. It’s an invitation to engage more skillfully.</p><h4>Drop the gloves</h4><p>In addition to being damn fun to play, hockey is a vivid illustration of the complexity I’ve spent much of my career navigating. It’s also a good reminder that complexity is not just abstract theory about interdependence on zoomed-out scales and long timelines. It shows up in the unexpected rebound, in the moment you thought you were helping but ended up screening your own goalie, in the nonverbal signals you and your linemates pick up and respond to without speaking.</p><p>The question this raises for any practice, whether you’re working in formal organizations or informal communities, is not <em>“how do we see the whole system so we can fix it?”</em> but <em>“how do we develop the situated awareness and responsiveness to act wisely within it?”</em></p><p>And if you lead others, you’ll inevitably spend time in the analyst’s booth or behind the bench tracking stats, adjusting lines, making calls from above. But if you want teams to develop the adaptive capacity to effect desirable change, you have to create conditions where they can sense and respond for themselves, where they learn to work with affordances in real time rather than just follow a playbook.</p><p>We’re not talking innate gifts or inner work here. These capabilities develop through interaction and are distributed across networks more than centered in individuals. The implication for leadership is less about developing one’s ability to tolerate uncertainty or read a system holistically. It’s about creating environments where people have the necessary tools, information, and permission to experiment, the space to sense and adjust collaboratively, and the time to learn from what emerges, not just executing what’s prescribed.</p><p>You can (and <em>should!</em>) study <a href="https://medium.com/topology-insight/complexity-science-for-non-majors-18c0022ba8c1">complexity science</a>. Learn the concepts, read the papers. But at some point, whether you’re a third line rookie, a player coach, or tenured GM, if you want to work effectively in complex systems, you have to engage with the system as it actually plays out. Coaches adjust lines mid-game. GMs make trades mid-season. And players on the ice take the hit, miss the pass, re-calibrate for the next shift. Whatever your role, the same advice applies:</p><p><strong>Keep your head up. Keep your feet moving.</strong></p><p><strong><em>Jen</em></strong><em> is co-founder and principal at </em><a href="https://www.topologyinsight.com/"><em>Topology</em></a><em>. Find her on </em><a href="https://www.linkedin.com/in/jbriselli/"><em>LinkedIn</em></a><em> and </em><a href="https://www.youtube.com/@topologyinsight"><em>YouTube</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b56e60867190" width="1" height="1" alt=""><hr><p><a href="https://medium.com/topology-insight/head-up-feet-moving-b56e60867190">Head Up, Feet Moving</a> was originally published in <a href="https://medium.com/topology-insight">Topology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stasis Theory: An Ancient Tool for Modern Collaboration]]></title>
            <link>https://medium.com/topology-insight/stasis-theory-an-ancient-tool-for-modern-collaboration-e58c099ba12e?source=rss-e34fb3b7cd78------2</link>
            <guid isPermaLink="false">https://medium.com/p/e58c099ba12e</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Jen Briselli]]></dc:creator>
            <pubDate>Sat, 20 Sep 2025 11:44:10 GMT</pubDate>
            <atom:updated>2026-01-01T22:03:29.977Z</atom:updated>
            <content:encoded><![CDATA[<h4>Cicero loved this one weird trick for finding the crux of any issue.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_fy7eIi8m_xeymLtYorGYw.jpeg" /></figure><p>Difference is one of the most valuable raw materials in collective work. When contrasting experiences and perspectives intersect, they illuminate possibilities beyond a sum of parts aggregation of skills. Ensuring epistemic diversity widens the solution space, surfaces blind spots, and empowers adaptation, which is exactly what makes collaboration worth the effort. Of course, it’s often accompanied by other differences — in priorities, interpretations, and assumptions — that inevitably introduce friction and disagreement.</p><p>To wit, Gregory Bateson described information itself as <em>a difference which makes a difference, </em>and perception, he suggested, begins in contrasts: we notice change, not constancy. <em>“What we perceive easily is difference and change — and difference is a relationship.”</em> Seen this way, disagreement isn’t just conflict to be resolved. It’s information.</p><p>Sometimes, disagreement also masquerades as uncertainty. A team may feel stuck, unsure about what’s true, unable to prioritize or agree on what to do next… but it’s not necessarily because the facts, or future, are unclear. It may be that people are framing the problem differently, assessing implications differently, or weighing the stakes differently.</p><p>In many organizations, the instinctive response is to chase (or impose) alignment. Get everyone on the same page, following the same metrics, pursuing the same goals. But the mirage of alignment often lures us into oversimplifying, or outright steamrolling, the meaningful differences that actually serve us well.</p><p>The task, then, is to work with disagreement in ways that generate coherence: pursuing just enough shared meaning that enables us to act in coordination, <em>without flattening the different perspectives that give collaboration its value.</em></p><p>This is where I like to reach for an old idea from classical rhetoric. The Greeks called it <em>stasis</em>: where something stands still, the crux of a conflict, an impasse. Roman rhetoricians later systematized it into what we now call <em>stasis theory</em>.</p><h4>Rhetoric for the rest of us</h4><p>Stasis theory comes from a canon of classical rhetoric known as <a href="https://en.wikipedia.org/wiki/Inventio"><em>inventio</em></a>: the means of discovering arguments, (which in this context are lines of reasoning or ways of making sense, not quarrels). And, why yes, it <em>is</em> interesting to note the use of “invention” vs. “discovery” here. The latin root <strong><em>invenire</em></strong> meant <em>to find</em> or <em>come upon,</em> while <strong><em>discooperire</em></strong><em> </em>meant to <em>reveal</em> or <em>uncover, </em>neither of which imply creating something out of thin air.</p><blockquote>Rhetorical invention is the craft of uncovering possibilities that the situation itself already affords.</blockquote><p>At essence, stasis theory outlines a process by which one asks certain questions in order to clarify thinking, to deliberate central issues in a conflict, or to arrange an argument. It rests on a few distinct types of stasis:</p><ol><li><strong>Fact</strong>: Did this happen? Does the thing exist? What is observed?</li><li><strong>Definition</strong>: How should we classify it? What is it related to?</li><li><strong>Quality</strong>: Is it good or bad? Right or wrong? What’s the significance?</li><li><strong>Policy</strong>: What should we do? What interventions are possible, desirable?</li><li><em>Some variations include </em><strong>Jurisdiction: </strong>Who decides? Who acts?</li></ol><p>The basic idea is that people need to agree on what, exactly, they’re disagreeing about in order for an argument to progress toward productive outcomes. Classically, the stases are treated as a hierarchical sequence one moves through to resolve a legal case or win a debate:</p><p><strong><em>settle the facts → agree on definitions → evaluate meaning → decide what to do</em></strong></p><p>This structure makes sense in courtrooms, where the goal is resolution, but in everyday deliberative contexts like conference rooms, Zoom calls, or Miro boards, I find it more useful to think of stases as <em>sites</em>: vantage points from which various types of sense making unfold. One group of people might be conflicted over what has happened, (or is happening), while another is debating its significance, and a third is arguing about the best action.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/763/1*qjh72Mr3M8sSv7fGayRe0g.jpeg" /></figure><p>In complex domains, this plurality is the rule, not the exception, and if these groups don’t recognize how their counterparts are locating their respective deliberation, that friction (which could be quite generative) hardens into frustration. James Andreyo helps <a href="https://www.academia.edu/12158351/Classic_Theory_of_Stasis">make my point</a>:</p><blockquote>“Rather than viewing multiple stases as behaving temporally — occurring in a successive series — in the appropriate deliberative context a static episode may be viewed as a ‘complex’ composed of an indeterminate set of contentions focused around a primary stock question; or indeterminate pairs of opposing contentions creating several intertwined stases.”</blockquote><p>In other words, disagreements are less like rungs on a ladder to be climbed stasis by stasis, and more like landscapes of unresolved questions and conflicting perspectives, overlapping and interconnected.</p><p>Crucially, when people are operating at different stases it isn’t always marked by overt disagreement or interpersonal conflict. Often, we don’t even realize we’re making sense of an issue differently, working at different stases, until we’re prompted to consider it. So, the question really isn’t <em>“Where are we in the sequence?”</em> as much as <em>“Where is the crux of meaning making for each of us right now?”</em></p><p>Sometimes we don’t need to agree on the facts <em>first</em>, as long as we can still coordinate action around shared policies. Other times, coherence and collaboration absolutely depend on established facts and shared definitions <em>before</em> implications can be explored or decisions can be made. Knowing the difference isn’t just a matter for rhetoricians and laywers, but also one of collective diagnosis for teams trying to make complex decisions and take action together. It helps groups locate the friction so they can orient toward and navigate through it. In some ways, a stasis is less a blockage than a beacon — a signal where attention and understanding are most needed, and will provide the most leverage.</p><h4>Asking rhetorical questions</h4><p>So what’s this look like in practice? I consider it a frame, not a framework, and certainly not a structured process. When I sense that a team is struggling with inertia, or circling around an issue but talking past each other, I’ll often invite them to pause and locate where they feel the crux really sits. Typically, I’ll ask people to engage with the stases first personally, then socially, and always in a contextualized way, anchored in a specific goal, decision, or challenge they’re facing.</p><p><strong>Start with self: </strong>I begin by asking folks where they, individually, feel the tension or perceive the disagreement to be centered. <em>Where (which stasis) do you sense the crux of this issue currently resides? </em>Here, I’m asking for firsthand observations and experiences of stuckness, resistance, or inertia.</p><p><strong>Speculate about others:</strong> Next, I ask the same folks to share where they sense their peers, leaders, wider organization, or some aggregate of relevant “other people” might answer. <em>Where (which stasis) do you expect that the XYZ team / your leadership / the community at large, might answer?</em> This kind of speculation isn’t about guessing right, it’s about practicing perspective-taking, which is a critical component in the progression from shallow alignment to authentic, productive collaboration.</p><p><strong>See the whole</strong>: Finally, we’ll look at the results together as a group and discuss what emerges. I find this works best when the responses are visualized in some lightweight manner, which can be as simple as a gradient line or a series of bubbles (depending on whether a more linear or spatial metaphor will resonate for the group).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2OsFSZLADpkUXhop-Vnt8g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PtXlncGZfiRyhXzUpxvmnA.png" /></figure><p>It’s not about finding the “real stasis” or “one crux to rule them all.” It’s about expanding awareness of difference in the first place. Not because there’s a right answer, but because the exercise shifts our focus from individual (un)certainty to relational awareness. It surfaces not only how <em>I</em> see the issue, but how I think <em>others</em> might be making sense of it — which is often quite revealing. We’re <em>locating the crux/ces</em> and <em>cultivating perspective-taking</em> at the same time.</p><p>This can reveal interesting patterns: sometimes multiple obvious hotspots emerge, predictably or otherwise, and other times they don’t; an even distribution is an interesting result in its own right. Imagine the discussion that can follow from here.</p><p>It’s also worth noting this approach doesn’t depend on forced disclosure, it works obliquely. As <a href="https://journals.sagepub.com/doi/10.1177/0741088388005004002">Fahnestock &amp; Secor</a> put it:</p><blockquote>The stases <em>tell us ‘where to think,’ not ‘what to think.’</em></blockquote><p>They provide orientation without prescription — a way of locating productive inquiry rather than dictating conclusions. The responses can remain anonymous. Instead of demanding that people name their assumptions head-on, it surfaces them indirectly and reduces the social risk for participants, who can’t be attacked for having the wrong assumptions and can explore friction points together with curiosity.</p><h4>Crux connections</h4><p>As an aside, whenever I work with the stases, I’m reminded of how <a href="http://www.bruno-latour.fr/sites/default/files/89-CRITICAL-INQUIRY-GB.pdf">Bruno Latour distinguishes</a> between <em>matters of fact</em> (claims that can be verified, measured, falsified) and <em>matters of concern</em> (entangled with meaning, implication, responsibility). You could say the former maps onto the stasis of fact, while the latter spans the stases of definition, quality, and policy, where interpretation, evaluation, and prioritization happen.</p><p>I also hear echoes of Jürgen Habermas’s notions around <a href="https://en.wikipedia.org/wiki/The_Theory_of_Communicative_Action">communicative action</a> and the three types of<em> validity claims</em> that participants bring into discourse: claims to<em> truth, rightness,</em> and <em>sincerity</em>. When we speculate about where others might locate the crux of an issue, we’re acknowledging that different people enter a conversation with different claims about what is true, what is right, and what is meaningful.</p><p>Meanwhile, Vaughn Tan’s <a href="https://vaughntan.org/nksynthesis?utm_source=chatgpt.com">not-knowing synthesis</a> folds some very complementary ideas into the mix. He argues that much of what we call <em>not-knowing</em> isn’t risk, but four distinct types of not-knowing about what we can do (action), what could happen (outcomes), how actions cause outcomes (causation), and what those outcomes mean (value). If stasis theory diagnoses where we’re stuck, Tan’s framework considers why we’re stuck there.</p><p>I also find the rhetorical stases intersect with the concept of <a href="https://cynefin.io/wiki/Granularity">granularity</a> as it applies in complex systems. As Dave Snowden highlights the importance of <em>decomposing to the lowest level of granularity where coherence emerges </em>(i.e. breaking things into smaller, more descriptive pieces until people can work with them), and Tom Kerwin’s <a href="https://multiversemapping.com/">multiverse mapping</a> builds on a similar instinct, I find the rhetorical stases complementary by highlighting which questions need to be dialed in at finer or coarser levels of granularity.</p><p>And it would be irresponsible of me not to call on Richard Buchanan’s conception of <a href="https://www.researchgate.net/publication/236727898_Design_and_the_New_Rhetoric_Productive_Arts_in_the_Philosophy_of_Culture">design as a rhetorical art</a>. Like rhetoric, design deals less with fixed truths than with <em>contested possibilities.</em> And like rhetoric, its generative heart is found in a form of inventio, a process of surfacing what’s latent and prefiguring what’s possible, exploring what the context affords, what human needs and interpretations bring into play, what choices are possible, desirable, ethical. This grounds the craft of design not in problem solving but in discovering-inventing arguments of material, experiential, or relational form.</p><p>Taken together, these practices aren’t really about chasing alignment or resolving conflict. They’re about cultivating <strong>disagreement literacy</strong>: the capacity to recognize and navigate difference without rushing to erase it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ekhsm6agrk0cMTli0h7HDw.jpeg" /></figure><h4>The loose end</h4><p>I’ve used the word <em>crux</em> interchangeably with <em>stasis</em> a few times here, but it’s worth calling on another definition: in literary criticism, a crux is a passage so corrupted or ambiguous that scholars can’t easily resolve what it was meant to say. It’s the central knot of a text that must be untangled through close reading to reveal the work’s full meaning.</p><p>That definition fits organizational life perfectly: the moments where hidden assumptions collide, where something stalls, where the meaning of things hangs in suspended animation and reframing and invention are most needed.</p><p>Healthy organizations don’t suffer from disagreement — they depend on it. Understanding the stases can help us locate the knots worth tugging at, the sites where necessary disagreements can be surfaced and explored. And in many cases that’s what a solution really looks like. The root of <em>solution</em> is <strong><em>solvere</em></strong>: to <em>loosen, untie, dissolve</em>. Not pinning things down, but loosening them up.</p><p><strong><em>Jen</em></strong><em> is co-founder and principal at </em><a href="https://www.topologyinsight.com/"><em>Topology</em></a><em>. Find her on </em><a href="https://www.linkedin.com/in/jbriselli/"><em>LinkedIn</em></a><em> and </em><a href="https://www.youtube.com/@topologyinsight"><em>YouTube</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e58c099ba12e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/topology-insight/stasis-theory-an-ancient-tool-for-modern-collaboration-e58c099ba12e">Stasis Theory: An Ancient Tool for Modern Collaboration</a> was originally published in <a href="https://medium.com/topology-insight">Topology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Vernacular of Change]]></title>
            <link>https://medium.com/topology-insight/the-vernacular-of-change-662e12d57df2?source=rss-e34fb3b7cd78------2</link>
            <guid isPermaLink="false">https://medium.com/p/662e12d57df2</guid>
            <category><![CDATA[change]]></category>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[foresight]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jen Briselli]]></dc:creator>
            <pubDate>Thu, 31 Jul 2025 15:33:53 GMT</pubDate>
            <atom:updated>2026-01-01T22:04:52.143Z</atom:updated>
            <content:encoded><![CDATA[<h4>Not purple or pedantic but a secret third thing.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/814/1*UDlTLMy44I9K3IwkkN3sbg.png" /></figure><p>Hey friends.</p><p>We need to talk about…<em> </em><strong><em>how we talk.</em></strong></p><p>Don’t get me wrong. I love the poetic language of complexity, futures, and design as much as the next guy*. (<em>guy = symmathesy</em>). I’ve used words like emergence and entanglement in more articles and talks than I probably should. I’ve nodded emphatically along to reflections on hospicing modernity and mutual unfolding and network weaving, and I’ve diffracted my share of rhizome metaphors and field analogies through enough pattern languages to make the new materialists, and old cyberneticists, proud. Or cringe. (Probably both.)</p><p>And while we’re at it, let’s not forget this esoteric flavor of fluency flex: Are we making an ontological claim or taking an epistemological stance? Staking a paradigm shift or just partaking in paradigmatic drift? Does this framework reproduce anthropocentric teleologies or subvert them with posthuman cosmopolitics? The terms pile up: pluriversal aspirations toward postnormal frames of sociotechnical imaginaries… until the signal gets buried under the semiotics.</p><p>If you’re reading this, you probably see yourself in here somewhere too. I’m not criticizing the language per se. It’s often necessary to preserve the rigor of an idea, or to give it enough resonance to land with a given audience. But, as excited as I am to hear a certain type of linguistic chorus growing louder, there’s something else beneath all that reverb: the temptation to chase resonance for its own sake. In conference talks, LinkedIn content, (and, uh, Medium articles), it’s becoming standard fare: someone drops a compelling turn of phrase or mind-expanding koan, the audience hums in agreement. A feeling of understanding ripples about. People feel changed by the conversation.</p><p>But <em>what</em> exactly changed? Vocabulary, perhaps, (and with it often comes a well intentioned, if evangelical, desire to bring others into the conversation). But language is easier to change than practice.</p><p>Plus, too much resonance isn’t always a good thing. Sometimes it shakes a structure apart.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*l3kK-t3zEPovDypO.gif" /></figure><p>At some point, language doesn’t just open a door to new ideas; it becomes the whole room. We furnish it with metaphors, we admire its coherence, and we settle in. (And why wouldn’t we? It’s comforting to be understood by others fluent in the same poetics.) But language isn’t supposed to just be a comforting destination. It’s also supposed to move us, figuratively and literally, toward new ideas, new connections, new forms of attention — and action. When the aesthetic appreciation of complexity becomes a substitute for engaging with it, <em>talking about change</em> starts to feel more satisfying <em>than change itself</em>.</p><p>Of course, this dynamic isn’t unique to design, futures, or systems thinking; it’s part of a broader pattern across change-oriented work. And there’s a word for what gets displaced in the process:</p><blockquote><strong>Vernacular.</strong></blockquote><p>The term itself is borrowed from linguistics: <em>language particular to a time, place, or group.</em> Dante used it in the 14th century to advocate for more writing in the “vulgar tongue,” (i.e. everyday Italian rather than Latin), arguing it to be a legitimate medium for serious thought. Since then, the term has expanded beyond language to describe phenomena similarly grounded in place-based, socially embedded experience, from architecture shaped by local climate and custom or cultural practices (like music, cuisine, and rituals) rooted in local needs and norms, to knowledge that is passed down through apprenticeship and real world practice.</p><p>Ivan Illich later reclaimed <em>vernacular</em> to describe the realm of subsistence, care, and autonomy that exists outside the control of markets and institutions; a space where people shape their own lives with the tools, wisdom, and relationships at hand:</p><blockquote>“We need a simple adjective to name those acts of competence, lust, or concern that we want to defend from measurement or manipulation by Chicago Boys and Socialist Commissars. The term must be broad enough to fit the preparation of food and the shaping of language, childbirth, and recreation, without implying either a privatized activity akin to the housework of modern women, a hobby or an irrational and primitive procedure. Such an adjective is not at hand. But vernacular might serve. By speaking about vernacular language and the possibility of its recuperation, I am trying to bring into awareness and discussion the existence of a vernacular mode of being, doing, and making that in a desirable future society might again expand in all aspects of life.”</blockquote><p>Contemporary forms of that ‘vernacular mode of being, doing, and making’ carry their own rigor, honed through experience and shaped by real-world consequences. It’s neither arbitrary nor primitive, but it’s rarely encoded in the metrics or vocabularies we privilege in modern systems of expertise, policy, or design.</p><p>It’s the warehouse coordinator who knows from experience which delayed shipments will trigger a chain reaction of missed deadlines and vendor blowback, and which can be absorbed without consequence. The middle manager navigating a sea of abstract strategy decks, conflicting personalities, and risk-averse culture to make meaningful work possible for their team. The parent who translates school bureaucracy into advocacy through persistence and intuition to get their kid what they need. A teenager learning the tacit grammar of the road, not from the driving manual, but in reading a constantly shifting system of speed, intention, and unspoken agreements between strangers.</p><p>None of these folks are using phrases like autopoesis, intra-action, or strange attractors. Some might even be operating from fairly rigid and overly linear assumptions about the world. But their practical, vernacular wisdom is the kind of operational judgment that meaningful change is built on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/283/0*udJDx2d-GXjz1lSJ.png" /></figure><p>The concept of vernacular isn’t inherently liberatory; it can carry bias, blind spots, and harmful traditions too. But it possesses the potential to question and evolve itself through agency and mutual obligation, and Illich’s use of the term is especially meaningful in its reclamation of the vernacular as sovereign space, free from institutional dependence or control. The vernacular isn’t simply how people speak; it’s how they learn and collaborate in ways that don’t require permission, credentials, or institutionally conferred legitimacy.</p><p>He also had a phrase for what happens when this kind of knowledge is undermined or displaced: the<em>“war against subsistence.”</em> He described it as <em>“a pattern of displacing what people already know how to do with services and language they must purchase or be trained into.”</em></p><p>And, dear reader, despite our best intentions, we are all at times complicit in that dynamic. When we’re deeply committed to epistemic justice but we look past the systems literacy of those we find professionally or ideologically inconvenient (even when that literacy embodies precisely the adaptive capacity we need to cultivate). When we promote pluralism that nevertheless requires translation, expecting people to reshape their mindsets or mental models to the contours of our frameworks, sidelining the very perspectives that could enrich our own.</p><p>It’s deeply ironic: to advocate for an understanding of the world as interconnected and emergent, while (if inadvertently) making that understanding contingent on fluency in an esoteric vocabulary, process, or worldview. It redirects energy from action into linguistic performance. Change gets stuck in translation.</p><p>What’s more, this dynamic shows up not just in how we speak, but in how we frame personal development. In many change-oriented domains, there’s a growing emphasis on inner work: cultivating awareness, building uncertainty tolerance, evolving one’s consciousness. I’m certainly in support of practices that deepen one’s reflective habits of mind and widen our perspective on possible futures, but inner work too easily reduces to a kind of spiritual merit badge. If it becomes a prerequisite for being taken seriously in certain communities or conversations, it’s more exclusionary than developmental.</p><p>And more importantly: that’s not how change actually happens.</p><p>Studying systems science doesn’t itself dismantle structural injustice or reduce carbon emissions. Advancing from a “self-authoring” to “self-transcending” stage of development doesn’t redistribute power or improve someone’s material living conditions. Personal growth doesn’t enable change until it shows up in what we build, resist, or repair together, and when “doing the inner work” delays engagement with the mundane, it’s not preparation, it’s performance.</p><p>Listen: I’m not advocating for anti-intellectualism. And I live for a compelling metaphor. Hell, this piece hinges on plenty of its own analogies and borrowed terms. I truly believe language can expand our sense of possibility. But when fluency becomes the cost of entry, language becomes a proxy for legitimacy. And the vernacular offers legitimacy beyond the ornamental filigree and linguistic litmus tests of expert discourse.</p><p>The point is, you don’t need to read Deleuze or quote Nora Bateson for our collaboration to have impact. (<em>Though I wouldn’t complain if you do.)</em> What matters is whether we’re able to get our hands dirty and speak the local language of the team, the community, or the organization we’re working within. Change emerges through shared sense making, meaningful interactions, and action that evolves with feedback. Everything else is just intellectual window dressing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/0*6snw8C7RKtRC_w2D.gif" /><figcaption><a href="https://en.wikipedia.org/wiki/How_Buildings_Learn">You’re probably not building from scratch.</a></figcaption></figure><p>So, how do we refuse conscription into that war against subsistence? What does change look like as a vernacular activity when our work is embedded within the very institutions that wage it?</p><p>The first step is to stop asking “<em>How do I inspire people to change their mindset?” </em>or <em>“How can I convince folks to adopt this framework?” </em>and start asking “<em>What are people already doing — and what do they already know — that we can build with?”</em></p><p>Put differently:<strong> we need to learn to speak the vernacular of the challenges we’re working on and the spaces we’re working in.</strong></p><p>Which in turn means understanding that context shapes language as much as the other way around. Illich once observed about his friend,<em>“the goldsmith in Timbuktu, speaks Songhay at home, listens to Bambara on the radio, devotedly and with some understanding says his prayers five times a day in Arabic, gets along in two trade languages on the Souk, converses in passable French that he picked up in the army — and none of these languages was formally taught him. He did not set out to learn these tongues; each is one style in which he remembers a peculiar set of experiences that fits into the frame of that language.”</em></p><p>Meanwhile the design strategist in Boston speaks Eastern New England English at home, listens to guttural death metal on the radio, devotedly and with some sarcasm prays in the language of complexity science, gets along in multiple industry dialects and acronyms, converses in passable hockey shorthand she picked up in the locker room — and none of these languages was formally taught her. She did not set out to learn these tongues; each is one style in which she remembers a peculiar set of experiences that fits into the frame of that language.</p><p>We learn by immersion, by tuning into what matters in each setting. Language doesn’t shift thinking — meaning does. And meaning comes from the interaction between context and narrative, not just the words we use.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/257/0*oJXNdbb_7DkCfAHw.png" /></figure><p>So, instead of introducing complexity science to the procurement team, learn how they already talk about vendor friction, cascading delays, and shifting constraints. Instead of teaching customer service reps about human centered design, listen to how they already diagnose issues, create workarounds, and share knowledge with each other in real time. (If they <em>want</em> to learn the language of <em>your</em> esoteric craft, they will, on their terms, through meaningful c<em>ollaboration with you</em>.)</p><p>And to be clear, vernacular isn’t limited to the language of <em>what is</em>; it also carries the capacity to imagine what <em>could be</em>, (though perhaps not always in terms designers or futurists are trained to recognize). To assume vernacular thinking can’t generate radical change is to mistake polish for imagination. People have always dreamed up new worlds using the language closest at hand.</p><p>When we begin from what’s already functional, however improvisational or incomplete, it shifts the posture of change. Less evangelizing (or imposing) new tools or models, more opportunities to support the self-organizing and generative capacity that’s already at play. What unionizing workers have always known, what mutual aid makes visible, what vernacular knowledge enables: that change is something enacted, not merely described or declared.</p><p>Naturally, this shift can be disorienting (or downright threatening, especially if you’ve built your credibility on offering <em>new</em> language, <em>new</em> methods, <em>new</em> mindsets). But it calls for something different: instead of persuading or teaching people to see differently, learning to see what <em>they</em> already see, and take it (and its evolutionary potential) seriously.</p><p>To that end, here are the kinds of things I ask myself to keep in touch with that <em>“vernacular mode of being, doing, and making.”</em></p><ul><li><strong>Are we speaking to communicate an idea, to signal belonging, to perform expertise, or something else?</strong></li><li><strong>Are we listening for others’ meaning in their language, or waiting to hear our own reflected back?</strong></li><li><strong>What knowledge already exists here that doesn’t actually need translation?</strong></li><li><strong>Who’s already doing the work we’re presently theorizing about?</strong></li><li><strong>What are the unspoken rules for being taken seriously in this room?</strong></li></ul><p>We can be rigorous. We can be reflective. But let’s also be <em>real</em>.</p><p>The world was complex long before we had words for it. Change doesn’t need special vocabulary — it needs participation. And it happens in the language people already speak.</p><p><strong><em>Jen</em></strong><em> is co-founder and principal at </em><a href="https://www.topologyinsight.com/"><em>Topology</em></a><em>. Find her on </em><a href="https://www.linkedin.com/in/jbriselli/"><em>LinkedIn</em></a><em> and </em><a href="https://www.youtube.com/@topologyinsight"><em>YouTube</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=662e12d57df2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/topology-insight/the-vernacular-of-change-662e12d57df2">The Vernacular of Change</a> was originally published in <a href="https://medium.com/topology-insight">Topology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Finding the Next Right Moves]]></title>
            <link>https://medium.com/topology-insight/finding-the-next-right-moves-e52bb18e0b70?source=rss-e34fb3b7cd78------2</link>
            <guid isPermaLink="false">https://medium.com/p/e52bb18e0b70</guid>
            <category><![CDATA[futures-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Jen Briselli]]></dc:creator>
            <pubDate>Tue, 17 Jun 2025 18:43:20 GMT</pubDate>
            <atom:updated>2026-01-01T22:05:03.206Z</atom:updated>
            <content:encoded><![CDATA[<h4>A complexity informed strategy sprint with the MITx SCM team</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uFZneF2Rq8-FbphY" /></figure><p><em>Sound familiar? </em>A team full of smart people, a strong mission, compelling vision… yet the strategy remains fuzzy, because the environment around you is always changing. It’s not poor planning, it’s that conditions aren’t stable enough, (or sometimes simply visible enough), to map a straight line forward.</p><p>We see it in all types of organizations, from education to healthcare to financial services, and tech. When the landscape is complex, you can’t engineer a future state and work backwards. You’ll end up with ideal visions, or worse, empty gestures, that simply don’t survive contact with reality.</p><p>You have to start from <em>where you are</em>, notice what’s changing, and identify the moves that are possible <em>now</em>.</p><p>That’s exactly what a cross-functional team at MIT’s Center for Transportation &amp; Logistics set out to do during their recent MITx team gathering. While their domain is online education, the challenges they’re navigating would surely be familiar to anyone working with legacy processes, evolving tech, complex regulations, or shifting customer expectations, (where the usual design thinking or product roadmapping exercises don’t stick).</p><p>As part of their virtual offsite, they invited Topology to help, and to their great credit, they leaned in when I suggested a different kind of workshop. The goal wasn’t to produce a two year roadmap; it was to see the terrain of the present more clearly, notice where currents are moving already, and choose the next most useful steps possible today.</p><p>What follows is a look at the process we facilitated to help them do exactly that, drawing on methods from the Cynefin ecosystem and other complexity informed approaches. Consider it a glimpse at how adaptive strategy actually unfolds in practice.</p><h3>Familiar Challenge, Different Response</h3><p>The MITx MicroMasters Program in Supply Chain Management has been a global leader in scalable, high quality online learning since its launch in 2015. But like many high performing teams, they find themselves at a juncture where legacy programs, platform constraints, and rapidly changing learner needs, (<em>and</em> <em>behaviors</em>, <em>cough</em> ChatGPT <em>cough</em>) make it tough to read the horizon, let alone plan for it.</p><p>We had previously facilitated a collaborative session on human centered design and learner experience, so the team returned with a new ask: not to generate ideas or empathy, but to create shared clarity and converge on a few actionable next steps that could be pursued with real momentum and minimal risk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gZ6EqNH__0TvwS0DCZuT7g.png" /><figcaption>“start where you are”</figcaption></figure><p>We typically begin by situating the team in relation to whatever complexity they face, acknowledging that in such environments, outcomes can be unpredictable and causality is muddy at best. Rather than chasing ideal future states, we focus on how the team might shift the system in desirable directions based on what’s feasible for them right now.</p><p>To support that, I like to introduce an idea called <a href="https://cynefin.io/wiki/Vector_theory_of_change">vector theory of change</a>: a way of thinking that prioritizes direction and momentum over fixed goals and endpoints. In complex systems, you don’t get to engineer the future; you have to interact with the present and observe what propagates.</p><p>Then, we collect narrative data. Sometimes we do it together, live during a session, other times we do it beforehand via survey, or a tool like <a href="https://thecynefin.co/about-sensemaker/">SenseMaker</a>. In this instance, prior to the workshop sessions, we asked MIT team members to share stories about the current state: moments of pride, frustration, transformation, stagnation. For example:</p><p><em>“Seeing our content getting old and our numbers go down makes me sad, but also frustrates me a little because it’s not 100% under our control.”</em></p><p><em>“Watching someone complete the MicroMasters and then present their thesis at MIT reminded me of how transformative this program can be. Not just for learners, but for us.”</em></p><p>These anecdotes aren’t elicited for mere reflection, they’re a form of evidence. They form patterns, and the patterns reveal affordances. That gives us something to work with.</p><p>We then pulled these stories into a simple exercise called “More Like This / Less Like This” that draws out directional intent without forcing consensus. Together, groups review the stories and sort them: Which ones represent the kind of thing we want to see more of in the future? Which ones reflect dynamics we’d prefer to move away from?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7kh2y7cXE1DAFMkEMQPTmQ.png" /></figure><p>Rather than debating abstract goals or getting mired in the details of metrics, it allows the group to work with grounded examples of what’s desirable and what’s not, surfacing a shared sense of direction without overspecifying it. In this case, the team noticed themes like:</p><ul><li><em>Desire for more visibility and momentum, especially when internal efforts deliver real impact</em></li><li><em>Frustration with slow institutional change and persistent platform limitations</em></li><li><em>Tension around academic integrity efforts; highly valued, but hard to scale and often yielding uncertain results</em></li><li><em>Drive to preserve and extend learner impact, especially where the program is clearly already transformative</em></li></ul><p>These aren’t binary judgments about individual stories; they’re indicators of where the team sees potential energy and possibility already accumulating.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*-r3hy6IfE_IIpTXr" /><figcaption>Complexity metaphor alert: estuaries are dynamic transition zones where freshwater rivers meet saltwater sea, full of mixing currents, shifting boundaries, and tidal change. (<a href="https://oceanservice.noaa.gov/facts/estuary.html"><em>Kachemak Bay, Alaska; NOAA</em></a><em>)</em></figcaption></figure><p>From there, we turned to a process called <a href="https://www.youtube.com/watch?v=-SITXkTFHVw">estuarine mapping</a><strong>: </strong>a conceptual way to make the system’s current constraints, opportunities, and tensions visible. Developed within the broader Cynefin ecosystem, and drawing on <a href="https://en.wikipedia.org/wiki/Actor%E2%80%93network_theory">actor-network theory</a> and <a href="https://en.wikipedia.org/wiki/Constructor_theory">constructor theory</a> among others, the <a href="https://cynefin.io/wiki/Estuarine_framework">estuarine framework</a> helps teams navigate complex change not by charting ideal end states, but by identifying what’s possible given the current conditions. It’s a way to understand where change might happen, where it likely won’t, and which actions might shift the system in a desirable direction.</p><p>At this point I should mention, depending on the team, its appetite for theory and/or its familiarity with the notion of an estuary, I don’t always use the metaphor or specific language of the framework itself. Instead of an <em>estuary</em>, I will sometimes refer to weather patterns, construction sites or alternative metaphors where some elements are stable, some shift quickly, forecasting might be common, but certainty is limited, and interventions are more about readiness and timing than determinism and control. Similarly, instead of <em>actants</em>, (which in this framework consist of <em>actors, constraints,</em> and <em>constructors)</em>, I will sometimes refer more generally to affordances, components, or influencing elements. Instead of <em>energy gradients</em>, we can think of topography: steep uphills vs. gentle downslopes, smooth asphalt roads vs. patches of quicksand.</p><p>But, in all of these cases, it’s crucial to maintain the rigor of the underlying logic that recognizes potential for actants that are both human <em>and</em> non-human, tangible <em>and</em> intangible, to shape the behavior of the system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VawcUQ62Ej4xX7RUIzbdzQ.png" /><figcaption>shaping the behavior of the system</figcaption></figure><p>So we start by identifying those actants. As part of the pre-workshop assignment, team members identified several such elements: people, communities, tools, artifacts, internal dynamics, external forces, relational links, cultural norms, technical constraints, institutional policies. They were prompted to consider not just who or what plays a role, but especially who or what connects, contains, transforms, or stabilizes.</p><p>Some of the actants the team uncovered included: <em>specific individuals, specific roles (such as learner and instructor), specific partner institutions, governing bodies, a particular tech platform, certain policies, course content, the value of a credential, the MIT brand, the global economy… </em>and on.</p><p>Once together in the session, groups reviewed, revised, and added to the collection of actants, and then plotted each actant against two axes:</p><blockquote>How much energy would it take to change?</blockquote><blockquote>How much time would it take to change?</blockquote><p>Two questions tend to emerge at this stage that I try to preempt. First, the axes are <em>not</em> quantified, because they are meant to be <em>relative, not absolute. </em>The mapping process itself reveals what’s relevant in this sense. Second, each group’s evaluation of the energy and time required for change is <em>from its own vantage point. </em>Often, teams with different information, access, or leverage will generate very different maps and this alone can be quite illuminating.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*C52M91hHmPVNZ6KF99JJEw.png" /></figure><p>As they work together, teams will inevitably encounter overlap, disagreement, or multiple interpretations as they assess where each actant belongs on the grid. In those moments, groups are encouraged to adjust the granularity: revising or “breaking things into smaller parts” until they reach a shared understanding they can work with. Our goal isn’t perfect precision or total consensus, but functional coherence: a level of detail everyone can live with.</p><p>The next step is to identify counterfactual, liminal, and volatile boundaries. In other words, the team identifies things that are <em>clearly out of reach, </em>like global government policy, macroeconomic conditions, and the acceleration of generative AI technologies. Others are <em>within reach, but only indirectly, through collaboration or permission, </em>like platform-related workarounds, partner organizations, or the dynamics between learner trust and academic integrity. And a few things seem to change <em>almost too easily</em>, like communication channels, which often raise good questions around whether that’s a risk vs. an opportunity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1016/1*9g92GNFm77CRV2bZOT6DoA.png" /></figure><p>The map itself doesn’t resolve these tensions, it just makes them visible and negotiable. It reveals a field of intervention possibilities: not an abstract canvas or blank slate for wishful thinking, but a realistic snapshot of the evolutionary potential of the present, tied directly to the team’s practical sphere of influence.</p><p>At this point, I like to give groups a chance to look at each other’s maps if they haven’t already, either via gallery walk (in person) or in rotating break out rooms (virtually) with active listening baked in. We consider what is similar, different, and surprising across the various white boards. In this case, we were then able to break for the afternoon, giving everyone’s brain a welcome chance to marinate in everything we had explored for the evening, before resuming the following morning.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S7WFxURcVIx3CCcfrsWtWQ.jpeg" /><figcaption>By the way, in a pinch, power cords make fine boundaries.</figcaption></figure><p>On Day 2, our task was to generate a portfolio of potential actions by integrating the Day 1 activities: having identified a <em>desirable direction of change </em>and the <em>affordances of the current situation</em>. After reviewing and reorienting to the previous day’s work, we continued by introducing a simple typology of action types to help the team identify where and how to engage in the system they’ve just mapped. For example, where do we want to act directly, nudge indirectly, or simply wait and watch? The goal is not to constrain ideas to this typology as an action classification system, but simply to provide helpful scaffolding for ideation. For example, we might consider:</p><p><strong>Creating</strong> something new in the system, like an initiative, role, channel, or artifact that shifts how things work</p><p><strong>Destroying</strong> an element that’s blocking progress or no longer serving a purpose</p><p><strong>Stabilizing</strong> what’s already present and needs to be protected or reinforced</p><p><strong>Monitoring</strong> a hard-to-reach element to detect early signs of change</p><p><strong>Triggering</strong> action when conditions are ready and the next step is clear</p><p><strong>Conditional</strong> actions that unlock or enable other changes</p><p><strong>Research</strong> to answer key questions, surface new options, or sense how things are evolving</p><p><strong>Requesting</strong> permission, collaboration, or support from others</p><p><strong>Interaction</strong> actions that change relationships: building, strengthening, weakening, or rerouting connections</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qVKnQUHmdae9hwSa.png" /><figcaption>Looks just like that photo of <em>Kachemak Bay, doesn’t it?</em></figcaption></figure><p>With that frame in place, the MIT team generated a context-specific set of actions, including things like:</p><ul><li><strong><em>Stabilize</em></strong><em> what’s working but at risk (e.g. Maintain momentum around exam cycles that are already delivering value)</em></li><li><strong><em>Research</em></strong><em> to learn more (e.g. Test short-form videos cut from live events to see how well they boost outreach and engagement)</em></li><li><strong><em>Monitor</em></strong><em> what’s out of reach (e.g. Track academic integrity practices at peer institutions and changes in AI-driven cheating)</em></li><li><strong><em>Create</em></strong><em> new affordances (e.g. Launch a small working group or ambassador role to connect with partner universities)</em></li><li><strong><em>Request </em></strong><em>permission and resources (e.g. Create protected time for teams to co-design and test new ideas, adding slack to enable innovation)</em></li></ul><p>Rather than collapsing these into a sequential roadmap, the team now had a collection of realistic interventions that can be initiated in parallel, each linked to specific affordances, each contributing to the directional intent they established on Day 1.</p><p>From here, teams carry the work forward in whatever manner makes sense, based on the interventions they’ve identified. We’ll sometimes extend the process here, facilitating various means of assessing and enhancing an idea’s resilience through activities like <a href="https://cynefin.io/wiki/Ritual_dissent">ritual dissent</a>, stress-testing dependencies and assumptions without needing to articulate them explicitly. And, for potential actions that require coordination, cooperation, or collaboration (<em>which is most of them</em>), I often introduce a version of the <a href="https://medium.com/@bill.bannear/the-new-zeitgeist-relationships-and-emergence-e8359b934e0">four voices framework adapted by Bill Bannear</a> as a simple but powerful way to think about what kind of, (and whose), collaboration is needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OcG1g0QWglx1-f7gXvpW1w.png" /><figcaption>“Next steps” can take a lot of forms.</figcaption></figure><p>What often strikes me about this process isn’t the content of the sticky notes but the subtle perspective shift I usually observe. Teams move from seeing their environment as a list of problems to fix or avoid, toward recognizing a system to engage with.</p><p>By the end of the session, the MIT team had some clarity on a focused set of pursuits. Rather than a detailed master plan, what emerged was a coherent portfolio of small, coordinated actions. They converted a list of disparate frustrations and individual aspirations into shared direction and a bit more alignment where it counts. Alongside the more tangible outputs, the session also introduced a subtle reframe on strategic planning: less about blueprinting long-term goals, more about staying responsive to emerging conditions.</p><p>Of course, nothing we do together on a white board can guarantee “success.” This collaboration simply cultivates the conditions <em>where thoughtful action is more likely to succeed, (</em>and where adaptation becomes possible even if it doesn’t). For this team, it’s easy to imagine repeating this process every time they gather for their team offsite, and to notice what has shifted, and what new aspirations become available, as a result of their experiments in the interim. Ideally, this session serves as the first phase of a continuous learning process; not a single planning event, but a repeatable rhythm of sense making and action.</p><p>And of course, you don’t have to work at MIT, or even in education, for this to be relevant.</p><p>If you’re navigating legacy systems, emerging technologies, and shifting expectations, the landscape probably looks familiar. You’re being asked to do more, without the kind of certainty traditional strategic planning methods tend to assume.</p><p>This kind of process offers an alternative: it’s not about finding <em>the</em> answer or charting <em>the</em> roadmap. It’s about surfacing diverse perspectives, making the system a little more visible, and identifying realistic, context-sensitive actions that can actually move things in the right direction in a sustainable and adaptive manner.</p><p>It’s a way of “doing strategy” that doesn’t treat the future as a puzzle to solve, but as a living landscape shaped by our collective action and feedback.</p><p><em>Curious what this might look like in your context? Let’s talk.</em></p><p>P.S. For a little more background on the rationale behind much of this process, see Dave Snowden’s open access book chapter in <em>Handbook of Futures Studies: </em><a href="https://doi.org/10.4337/9781035301607.00011">As through a glass darkly: a complex systems approach to futures</a>.</p><p>And for some additional perspectives on estuarine mapping specifically, check out these bits and pieces from: <a href="https://triggerstrategy.substack.com/p/a-trip-into-the-estuary">Tom Kerwin</a>, <a href="https://www.viktorcessan.com/my-experiences-with-estuarine-mapping/">Viktor Cessan</a>, <a href="https://mattiheino.com/2024/08/28/childrens-party/">Matti Heino</a>, and <a href="https://www.productquestpodcast.com/e/episode-79-navigating-complexity-in-healthcare-with-steven-weissenburger/">Steven Weissenburger</a>.</p><p><strong><em>Jen</em></strong><em> is co-founder and principal at </em><a href="https://www.topologyinsight.com/"><em>Topology</em></a><em>. Find her on </em><a href="https://www.linkedin.com/in/jbriselli/"><em>LinkedIn</em></a><em> and </em><a href="https://www.youtube.com/@topologyinsight"><em>YouTube</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e52bb18e0b70" width="1" height="1" alt=""><hr><p><a href="https://medium.com/topology-insight/finding-the-next-right-moves-e52bb18e0b70">Finding the Next Right Moves</a> was originally published in <a href="https://medium.com/topology-insight">Topology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Invisible Infrastructure]]></title>
            <link>https://medium.com/topology-insight/invisible-infrastructure-5314323a91cb?source=rss-e34fb3b7cd78------2</link>
            <guid isPermaLink="false">https://medium.com/p/5314323a91cb</guid>
            <category><![CDATA[organization]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Jen Briselli]]></dc:creator>
            <pubDate>Thu, 01 May 2025 12:31:32 GMT</pubDate>
            <atom:updated>2026-11-16T21:44:35.429Z</atom:updated>
            <content:encoded><![CDATA[<p><em>What makes an organization adaptive isn’t in the org chart. Or on the roadmap.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SBsPs9JmUWmmD3uC.jpg" /></figure><p>Looking back over the last couple years, I’ve noticed a theme running through almost every one of Topology’s engagements. Whether it’s been framed as strategy, research, design, or… (<em>I know</em>) transformation, it’s all been driven indirectly by the practice of <strong>facilitation</strong>: helping client teams see each other more clearly, think together more effectively, and make sense of complexity in ways that feel grounded and doable. And what keeps showing up, subtly but consistently, is the significance of an organization’s <strong>connective tissue</strong>: the informal relationships, back channels, and small acts of trust that make the formal systems <em>actually work.</em></p><p>Most organizations are built around familiar, visible structures: roles, work flows, metrics. These do matter. But when policy or technology shifts cascade faster than process can catch up, or when teams face ambiguity that none of their playbooks address, it’s not the structure that saves you. It’s the glue.</p><p>The <em>informal</em> glue. The colleague you call before replying to an exec email. The side chat where someone admits, “This isn’t working, is it?” The underground layer, or ‘<a href="https://b-m-institute.com/wp-content/uploads/2019/10/Shaw_1997.pdf">shadow system</a>’ of relationships, conversations, and improvisations that shape how things <em>really</em> get done. The ‘<a href="https://www.routledge.com/Complex-Responsive-Processes-in-Organizations-Learning-and-Knowledge-Creation/Stacey/p/book/9780415249195?srsltid=AfmBOoocIVb42Ytzi5aa2uTCNuxboURxzkwyq0pchE6Xjt_A0gYXW2W8">complex responsive processes</a>’ that define an organization or community’s behavior. It’s a kind of <strong>invisible infrastructure. </strong>And it’s often what makes the difference between a rigid organization and a resilient one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1oZe3rZyOE8odcYx.jpg" /></figure><p>We’ve worked with teams facing everything from tectonic shifts in regulatory complexity, to intense cross-functional gridlock, to the garden variety friction teams face when their day-to-day work feels unmoored from a guiding strategy. On paper, things often look connected: shared goals, regular meetings, well defined work streams. But underneath, people feel out of sync. Obviously, no one in these environments ever thinks, <em>“Shucks, we just need some facilitation!”</em> But, they’re usually missing exactly what good facilitation makes possible: the (literal <em>and</em> figurative) space to think, connect, and adjust course together.</p><p>Indeed, when organizations create the conditions for more open and sustainable dialogue across roles, departments, and initiatives, we see a different kind of coordination take shape: Less of the formal alignment around KPIs or mission statements, and more of a highly functional organizational coherence that helps people respond in mutually reinforcing ways, even when things are uncertain. Beyond mere ‘responsibility for deliverables,’ toward accountability rooted in mutual insight. And perhaps most importantly, the emergence of informal coalitions who surface enterprise interdependencies: the dynamics that rarely show up in strategic planning decks, but nonetheless determine whether initiatives succeed or stall.</p><p>Informal networks are often dismissed as lucky accidents or distracting inefficiencies. But in reality they are decentralized carriers of context: alive with nuance, history, and relational intelligence. And in complex systems (i.e. the domains most of us work within), where <a href="https://youtu.be/HzEjYp59H2o?si=e-xqiYZft2cnfkQd">cause and effect don’t follow an obvious straight line</a>, outcomes emerge through tangled relationships, shifting incentives, and evolving constraints. Healthy informal networks can help people navigate that complex terrain by:</p><ul><li><strong>Surfacing weak signals</strong> and identifying issues before they escalate</li><li><strong>Bridging silos </strong>and translating meaning across team boundaries</li><li><strong>Circulating nuance</strong> that can’t be captured in a status report or dashboard</li><li><strong>Providing safe spaces</strong> for skepticism, play, and experimentation</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zZmAuTTdf-RTBM3jOvQh5A.jpeg" /></figure><p>Informal networks are also where some of the most meaningful learning happens: not in isolation, but in context. <a href="https://medium.com/topology-insight/apprenticeship-is-dead-long-live-apprenticeship-1ddb789705ce">In the field, with others.</a> In this sense, learning is not an event or outcome; it’s a relational capacity for adaptation, woven through dialogue, shared noticing, and reflective practice.</p><p>Sometimes it looks like a <em>community of practice</em>, in the<a href="https://www.wenger-trayner.com/introduction-to-communities-of-practice/"> sense described by Etienne Wenger</a>, where learning is situated, social, and shaped by participation. Other times, it’s simply a constellation of casual rituals that enable trust and insight to accumulate across roles. Either way, the real work is infrastructural: scaffolding spaces for people to share and experiment in a way that informs their work and collaboration with others.</p><p>These dynamics make alignment possible, though not always in ways we usually think about it. We hear a lot about organizational <em>alignment</em> in a literal sense: agreement and compliance. But what we truly need to look for is <em>coherence</em>: shared understanding in motion. While alignment is directed from above, coherence emerges from within and between. It’s contextual, discovered through <a href="https://www.amazon.com/Sensemaking-Organizations-Foundations-Organizational-Science/dp/080397177X">shared sensemaking</a>, not shared slide decks. It unfolds in the hallway debriefs after the all-hands meeting, and the Slack channels that address what the presentation didn’t.</p><p>Truly, organizations don’t necessarily need alignment; we need just enough shared understanding to move together. In fact, total agreement and lockstep tactics can actually be a liability in complex domains because it tends to flatten diverse perspectives, stifle constructive dissent, and give the illusion of certainty when what’s needed is curiosity and responsiveness. In the <a href="https://thecynefin.co/tests-for-coherence/">words of Dave Snowden</a>, <em>“the value of coherence is that it allows for contingent truth, a determination that, while we don’t know everything, we are at least going in the right direction.</em>“</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JqU0WKx2R8ZVEwJT" /></figure><p>Of course, many leaders don’t need convincing on any of this. You see these dynamics. You believe in the value of cross-boundary trust, distributed decision making, and ad hoc collaboration. But you’re also under pressure: too many meetings, too few windows for reflection or perspective sharing, and too much inertia in the formal systems around you.</p><blockquote><strong><em>You’re not alone.</em></strong></blockquote><p>And let’s be honest: even when you <em>do</em> see what’s needed, it can feel like there’s no room to act until something breaks. Some leaders tell us they believe in this work, but feel like they have to wait for a major disruption, an unlikely budget shift, or a full-blown crisis before they can justify investing in it. (As if sustaining a healthy organizational ecosystem were only justifiable <em>after</em> the chaos, and not the very investment that prevents the worst of it in the first place... but I digress.)</p><p>Adaptation and innovation don’t emerge from a reactionary posture, even if its an efficient one. They arise from proactive, continuous learning and experimenting. The most adaptive teams we’ve worked with didn’t wait for things to be on fire; they find (sneak?) small ways to build their capacity to notice smoke ahead of time, and act on curiosities before they ever become concerns.</p><p>The challenge isn’t usually a lack of insight, it’s a lack of healthy slack in the system. Working around formal structures can require more time, energy and attention than you have. And nurturing informal networks can feel like a luxury you just can’t afford. Truly, most of our collaborators and clients don’t need another idealistic blueprint, but simply a scaffold: something lightweight, practical, and flexible enough to support the trust and shared instincts already trying to get established in their organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ABvkfpcYmvdo8gNN.jpg" /></figure><p>Realistically, informal networks can’t be launched on command or engineered into existence. But they <em>can</em> be nurtured. Your role is to shape the conditions that help them thrive. That might look like:</p><ul><li><strong>Amplifying what’s already working.</strong> For example, we sometimes use a blend of narrative inquiry, participatory and generative design methods, and light network sensing to help clients recognize where a current trickle of what’s desirable exists, and could potentially grow into a stronger current.</li><li><strong>Providing space and tools for distributed sensemaking.</strong> This might include listening sessions and learning programs, rituals for reflective practice, or strategy deep dives and collaborative workshops: not to align people to a message, but to invite deeper attention to the signals they can already act on.</li><li><strong>Offering air cover.</strong> Informal collaboration often needs protection from the bright lights of attention, over-sponsorship, or premature KPIs. We’ve helped leaders find organizationally savvy ways to legitimize these efforts without smothering them under scrutiny and expectations.</li><li><strong>Rewarding connection, not just completion.</strong> Much of our recent work has helped clients make relational efforts more visible and valued, so that efforts toward building trust, bridging silos, and supporting peers are recognized as essential to learning and decision making, not just appreciated on the sidelines.</li></ul><p>These aren’t one-size-fits-all fixes. They require interaction, often across cultural silos and unspoken tensions. They require the skilled, <em>enabling-not-directing</em> style of facilitation that creates space without controlling the output, invites dissent without derailing progress, and helps a group stay in the discomfort of inquiry long enough for something useful to emerge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p7MznuKS4iOohBdE.jpg" /></figure><p>Of course, not every attempt to nurture that connective tissue succeeds. We’ve seen organizations try to sustain it by creating new councils, steering committees, or cross-functional forums. Too often, they revert to familiar habits: slide templates, ceremonial updates, alignment theater. The organic connections that made things work in the first place get buried under formality, and the energy dissipates.</p><p>What was emergent becomes performative. What might have been a live inquiry becomes a reporting mechanism. The potential dissolves into process. Even popular models like <a href="https://www.amazon.com/Team-Teams-Rules-Engagement-Complex/dp/1591847486">Team of Teams</a> and <a href="https://www.amazon.com/X-teams-Build-Teams-Innovate-Succeed/dp/1591396921">X-Teams</a>, which can offer useful structures for distributed coordination and boundary-spanning innovation, aren’t much more than stylized diagrams without the invisible scaffolding of trust, shared context, and informal learning loops.</p><p>It’s not a failure of intent, just a predictable reversion to the mean. That’s why we emphasize the importance of internally distributed sensemaking, to notice when structure is starting to stifle instead of support, and enabling practices that don’t just <em>look</em> collaborative, but actually <em>are: </em>messy, human, and unpredictable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zy8Q4qafxUBCNa_9.jpg" /></figure><p>In the end, across systems and sectors, we see these dynamics play out:</p><blockquote><em>When people have shared language, space to notice, permission to experiment, and capacity to think out loud among a web of trusted colleagues, they adapt faster.</em></blockquote><blockquote><em>When these things are missing, even well-designed strategies and tactical alignment can stall.</em></blockquote><p>And these dynamics aren’t just common — they’re consequential. Over time, we’ve seen the same disconnects surface in many different ways, shaped uniquely by context but strikingly familiar in form. These tensions often go unspoken, not for lack of awareness, but because even the leaders who believe in distributed collaboration are stretched thin, working within systems that make it hard to act on what they know.</p><p>In environments like these, innovative ideas tend to be normalized by the gravity of business-as-usual, absorbed into formal structures before they ever have a chance to shift them. If you’re someone who sees these dynamics but feels stuck inside structures that are too sluggish to support what you know matters, remember this: the answer isn’t necessarily to push harder, or even to “fix the structure” at all. Often, it’s simply to shift your attention: notice where good things are happening, where interactions are crossing formal boundaries, however subtly, or even subversively, and ask what is needed to keep them going.</p><p>One helpful practice is learning to name what’s really at play. Not just what’s in the plan, but what’s making things work behind the scenes. The rosetta stone below offers a potential reframing; it’s a side-by-side look at how some of the more common corporate ambitions rely on informal networks to function, and how the language we use might obscure the infrastructure we <em>actually</em> depend on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_XAiNaVA9D8Tp0dXIawHkw.png" /><figcaption>Corporate Speak vs. <em>Real</em> Talk</figcaption></figure><p>The good news is, you don’t need to overhaul your org chart or reinvent your operating model to grow your collective capacity for adaptation, or to get things unstuck. You just need to notice where informal networks already exist, and actively enable them to grow denser and stronger, so they can carry ideas, capabilities, and trust farther and faster than formal channels alone. Look for the relationships that enable shared ownership. Look for the quiet collaborations that span functions and reveal interdependencies your formal structures don’t acknowledge. These are the places where insight and innovation already live.</p><p>Start small. Ask where trust already exists, where people share information freely, or where informal collaboration is making things work better than conventional measures would suggest. Then find a way to protect it, nurture it, or amplify it. The goal isn’t to formalize what’s working; just start by <em>not</em> discouraging it. Sometimes, that’s all it takes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_sPCNdTJi-5WTXYI.jpg" /></figure><p><strong><em>Jen</em></strong><em> is co-founder and principal at </em><a href="https://www.topologyinsight.com/"><em>Topology</em></a><em>. Find her on </em><a href="https://www.linkedin.com/in/jbriselli/"><em>LinkedIn</em></a><em> and </em><a href="https://www.youtube.com/@topologyinsight"><em>YouTube</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5314323a91cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/topology-insight/invisible-infrastructure-5314323a91cb">Invisible Infrastructure</a> was originally published in <a href="https://medium.com/topology-insight">Topology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Letter to a Young Systems Thinker]]></title>
            <link>https://medium.com/topology-insight/letter-to-a-young-systems-thinker-13ab8e1d6108?source=rss-e34fb3b7cd78------2</link>
            <guid isPermaLink="false">https://medium.com/p/13ab8e1d6108</guid>
            <category><![CDATA[systems-change]]></category>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[strategic-design]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Jen Briselli]]></dc:creator>
            <pubDate>Wed, 16 Apr 2025 19:39:28 GMT</pubDate>
            <atom:updated>2026-01-01T22:05:22.675Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Have patience with everything unresolved in your heart and to try to love the questions themselves as if they were locked rooms or books written in a very foreign language. Don’t search for the answers, which could not be given to you now, because you would not be able to live them. And the point is, to live everything. Live the questions now.</blockquote><blockquote><em>Rainer Maria Rilke, </em>Letters to a Young Poet</blockquote><p>Dear ________,</p><p>If you’re drawn to systems thinking, I imagine you’re also attracted to the elegance of its abstractions: captivating webs of causal loops, the seductive search for leverage points, the allure of models and maps and mechanisms. Indeed, the tidy logic of a carefully designed system diagram can offer an intellectual refuge from a reality that feels chaotic. It makes the world feel <em>just</em> within reach of being figured out, maybe even optimized. Many of us come to systems work carrying this kind of engineer’s optimism.</p><p>But some systems don’t sit still for diagrams, (especially the complex human systems you’re probably most interested in). And if you stay with systems work long enough, committed to curiosity and reflection, sooner or later you realize the point isn’t to model, map, or master the system, but to be in conversation with it.</p><p>If you can learn to listen carefully, you find that systems speak. Not in words, but in patterns and anomalies: beacons that light up the places where an experiment or intervention can teach us more about a system’s behavior and the path to desirable change. They show us where we can enter into active ongoing dialogue with a system, rather than steer it.</p><blockquote>Your role is not to command the system, but to commune with it.</blockquote><p>Though — this isn’t mysticism. It’s not detached observation nor a passive meditation. Systems oriented practice is active and relational. It means sensing where the system is malleable, where small shifts might propagate into meaningful change. It means actively modulating constraints, seeding new patterns, and prefiguring more livable futures.</p><p>And of course, zooming out will always have its value. A macro view can help you interrogate assumptions and gain perspective. But zoom out too far, for too long, and you’re left staring at a picture of the entire universe: a beautifully intricate constellation so vast it becomes inert. The paradox is that the more complexity you try to hold, the harder it becomes to know where to act. Systems strategy isn’t just about grasping the full picture; it requires you to engage — locally, attentively, and iteratively.</p><p>Systems don’t shift through comprehension alone, but through active participation. Which means our work is often anything <em>but </em>elegant; it’s more often clumsy, itchy, and messy. It feels less like solving, and more like muddling through, with blurry vision and dirt under your nails.</p><p>These are the textures that deepen our attention and ground our work in the world as it exists — so we can better co-create the world that could be.</p><figure><img alt="MC Escher: Rippled Surface" src="https://cdn-images-1.medium.com/max/1024/0*SPKdKL1_DbH69a_i.jpg" /></figure><h3>Blurry</h3><p>Critical to our participation is the capacity to work within a particular frame of reference, without becoming confined by it. To do this, we need what Donald Schön so eloquently <a href="https://www.amazon.com/Reflective-Practitioner-Professionals-Think-Action/dp/0465068782">calls double vision</a>:</p><blockquote>At the same time that the inquirer tries to shape the situation to his frame, he must hold himself open to the situation’s back-talk. He must be willing to enter into new confusions and uncertainties. Hence, he must adopt a kind of double vision. He must act in accordance with the view he has adopted, but he must recognize that he can always break it open later, indeed, must break it open later in order to make new sense of his transaction with the situation. This becomes more difficult to do as the process continues. His choices become more committing; his moves, more nearly irreversible. As the risk of uncertainty increases, so does the temptation to treat the view as the reality. Nevertheless, if the inquirer maintains his double vision, even while deepening his commitment to a chosen frame, he increases his chances of arriving at a deeper and broader coherence of artifact and idea.</blockquote><blockquote>His ability to do this depends on certain relatively constant elements that he may bring to a situation otherwise in flux: an overarching theory, an appreciative system, and a stance of reflection-in-action which can become, in some practitioners, an ethic for inquiry.</blockquote><p>Maintaining an intentional sort of double vision keeps our conversation with a system alive and evolving: noticing when the boundaries we’ve drawn, or the framing we apply, begin to limit more than they clarify, and having the humility to adjust our perspective when they do. It invites us to entertain multiple interpretations, allowing contradictions to remain unresolved long enough for shared meaning and a viable path to emerge.</p><figure><img alt="MC Escher: Eight Heads" src="https://cdn-images-1.medium.com/max/583/0*w5Ji5m0N0JCG-zGk.jpg" /></figure><h3>Noisy</h3><p>This work invites multiple voices, which can be tough to accommodate, especially when they contradict each other. We have to <em>host</em> that noisy conversation, rather than resolve it. That means valuing not just multiple disciplines, but multiple epistemologies. Not just expertise, but experience; less focus on gathering inputs to improve a solution and more on widening the aperture of what counts as knowledge. Miranda Fricker suggests:</p><blockquote>Perhaps we should think of the ideal hearer as someone for whom correcting for familiar prejudices has become second nature, while the requisite alertness to the influence of less familiar prejudices remains a matter of ongoing active critical reflection.</blockquote><p>This is also where <em>cognitive diversity</em> becomes more than a buzzword. It enables collective sensemaking. Each perspective we incorporate expands the capacity to notice what’s emerging, what’s missing, what’s possible. And in a world of persistent structural inequity, <a href="https://www.amazon.com/Epistemic-Injustice-Power-Ethics-Knowing/dp/0199570523">epistemic justice</a> becomes a critical aspect of the work: Who gets to speak? Who gets believed? Whose discomfort do we minimize, and whose do we design around?</p><p>The goal isn’t consensus, but coherence. Not agreement, but understanding of the shared stakes, and a willingness to advance the dialogue rather than win it.</p><figure><img alt="MC Escher: Cycle" src="https://cdn-images-1.medium.com/max/350/0*xoHaDqXwFbY6YBaA.jpg" /></figure><h3>Clumsy</h3><p>Once we look past the mirage of a tidy conclusion, what emerges instead are <a href="https://www.amazon.com/Clumsy-Solutions-Complex-World-Perceptions/dp/0230002307">clumsy solutions</a>: messy, contradictory, plural and imperfect. And yet, they are often the most resilient. As Marco Verweij writes:</p><blockquote>It is important that all the ways of life be taken account of in the policy process. And that, for all its simplicity, is the essence of clumsiness: all the ‘voices’ heard, and responded to by the others.</blockquote><p>Clumsy solutions are implemented with the recognition that no single perspective holds the whole truth and make space for conflicting needs and imperfect compromises. Rather than trying to impose alignment or control, they work with the system’s inherent tensions.</p><p>Designing for desirable futures with this kind of clumsiness takes practice. It asks us to hold pluralism without paralysis, to let multiple logics sit side by side, even when our ideas and experiments feel messy because of it. This messiness is not a flaw; it’s the grounding for creative possibility, as Arthur Koestler describes in the <a href="https://www.amazon.com/Act-Creation-Arthur-Koestler/dp/1939438985">Act of Creation</a>:</p><blockquote>The creative act is not a sudden inspiration but a collision of frames of reference that generates something new.</blockquote><p>Koestler called this process <a href="https://www.themarginalian.org/2013/05/20/arthur-koestler-creativity-bisociation/"><em>bisociation</em></a>: the ability to hold and integrate seemingly unrelated ideas in a way that leads to creative insight. Rather than forcing complete synthesis, creative breakthroughs often emerge when we stay with the tension long enough for the friction to generate a spark.</p><figure><img alt="MC Escher: Flatworms" src="https://cdn-images-1.medium.com/max/588/0*KDbXnM1s41vGW0wV.jpg" /></figure><h3>Itchy</h3><p>Talking to a system means hearing things that unsettle us, and resisting the urge to draw premature conclusions around what the system hasn’t finished saying. To not scratch the itch.</p><p>It demands what John Keats called <em>negative capability</em>:</p><blockquote>When man is capable of being in uncertainties, mysteries, doubts, without any irritable reaching after fact and reason.</blockquote><p>It’s uncomfortable. The urge to resolve contradiction is strong. But as Theodor Adorno reminds us, perfect synthesis is not always our goal:</p><blockquote>Dialectics serves the end of reconciliation… but a reconciliation that does not level differences.</blockquote><p>Adorno’s concept of <em>negative dialectics</em> invites us to remain in the discomfort of contradictions rather than forcing resolution. It asks us to resist premature convergence and stay open to difference, recognizing that concrete next steps are often made viable not by simplifying complexity, but by inhabiting it fully.</p><blockquote>The need to let suffering speak is a condition of all truth.</blockquote><p>In systems work, this means holding space for paradox, ambiguity, and discomfort — not as a failure of insight, but as a precondition for it.</p><p>And this should be noted not as a shrugging concession to postmodern cultural relativism, but a rigorous ethic of attention and commitment to presence. As Donna Haraway puts it, the bravest and most ethical move is often to <em>“</em><a href="https://www.dukeupress.edu/staying-with-the-trouble"><em>stay with the trouble</em></a><em>.”</em></p><figure><img alt="MC EScher: Encounter" src="https://cdn-images-1.medium.com/max/1024/0*kjIbLmPhS5tc1M9U" /></figure><h3>Bruising</h3><p>Some parts of a system only speak on impact: when you touch it, bump into it, crash through it. You can’t learn everything from a map. You can still trip over the rocks at your feet.</p><p>Deep knowing emerges when action and reflection collide, when ideas get tested against lived complexity, and when our models fall apart just enough to let something else poke through.</p><p>Consider this a form of <em>gnosis: </em>the type of knowing that arises not from detached observation, but from our own direct, lived experience. Unlike abstract knowledge (<em>episteme</em>) or belief (<em>doxa</em>), <em>gnosis</em> is intimate, situated, and relational.</p><blockquote>The world reveals itself to those who travel on foot. — <em>Werner Herzog</em></blockquote><p>To know a system through gnosis is to enter the dialogue through participation and give credibility to intuition. It requires that we feel our way forward, and let our assumptions be reshaped in real time. This kind of knowing cannot be abstracted or outsourced. It is slow, iterative, and deeply personal. And it changes not just what we know, but how we identify the future outcomes we want to amplify.</p><figure><img alt="MC Escher: Bond of Union" src="https://cdn-images-1.medium.com/max/600/0*1D3RtoBILRo4CJaM.jpg" /></figure><h3>Entangled</h3><p>At some point, the conversation stops feeling like a collection of separate parties. We’re no longer talking <em>to</em> the system; we’re all just… in communion. Systems work demands reflexivity: the ability to recognize ourselves not just as observers or designers, but as participants in the very systems we’re trying to make sense of. It invites us to ask,</p><p><em>How am I shaping the dynamics I’m trying to understand?</em></p><p><em>What assumptions am I carrying?</em></p><p><em>And what is this system revealing about me in return?</em></p><p>This kind of entanglement is not metaphorical, it’s ontological. Karen Barad’s <a href="https://www.amazon.com/Meeting-Universe-Halfway-Quantum-Entanglement/dp/082233917X">concept of <em>intra-action</em></a> holds that we and the system we’re part of co-emerge through our mutual participation. Agency is not something we possess or exert; it is <em>enacted</em> in the spaces between, and surrounding, ourselves and others:</p><blockquote>The very nature of materiality is an entanglement. Matter itself is always already open to, or rather entangled with, the “Other.” The intra-actively emergent “parts” of phenomena are co-constituted. Not only subjects, but also objects, are permeated through and through with their entangled kin; the other is not just in one’s skin, but in one’s bones, in one’s belly, in one’s heart, in one’s nucleus, in one’s past and future. This is as true for electrons as it is for brittlestars as it is for the differentially constituted human…What is on the other side of the agential cut is not separate from us — agential separability is not individuation. Ethics is therefore not about right response to a radically exterior/ized other, but about responsibility and accountability for the lively relationalities of becoming of which we are a part.</blockquote><figure><img alt="MC Escher: Puddle" src="https://cdn-images-1.medium.com/max/1024/0*CRscIJUBR7Nz4eYB.jpg" /></figure><h3>Mucky</h3><p>So, we have a choice.</p><p>If talking to a system means mutually unfolding, unfinished dialogue, then we must also choose <em>where</em> we’re willing to have that conversation. Not all terrain is equal. We call again on Donald Schön:</p><blockquote>In the varied topography of professional practice, there is a high, hard ground where practitioners can make effective use of research-based theory and technique, and there is a swampy lowland where situations are confusing ‘messes’ incapable of technical solution. The difficulty is that the problems of the high ground, however great their technical interest, are often relatively unimportant to clients or to the larger society, while in the swamp are the problems of greatest human concern. Shall the practitioner stay on the high, hard ground where he can practice rigorously, as he understands rigor, but where he is constrained to deal with problems of relatively little social importance? Or shall he descend to the swamp where he can engage the most important and challenging problems if he is willing to forsake technical rigor?</blockquote><blockquote>There are those who choose the swampy lowlands. They deliberately involve themselves in messy but crucially important problems and, when asked to describe their methods of inquiry, they speak of experience, trial and error, intuition, and muddling through.</blockquote><p>The swamp is where the system doesn’t echo back cleanly; messages get swallowed, warped, or rerouted through the mud. It’s where our tools break, our maps get dirty, the work gets more ambiguous, and maybe even weird. But it’s where we belong.</p><figure><img alt="MC Escher: Three Worlds" src="https://cdn-images-1.medium.com/max/490/0*_thXGGvgkeFqs8_i" /></figure><h3>Alive</h3><p>For all its discomforts, this work is anything but sterile. Nora Bateson offers <a href="https://www.amazon.com/Small-Arcs-Larger-Circles-Patterns/dp/1909470961">a beautiful term</a> for the notion of systems learning through mutual influence, where no element is isolated and nothing stays still:</p><blockquote>Symmathesy is not a static thing; it’s a conversation. And conversations are alive, unpredictable, full of feedback and missteps and grace.</blockquote><p>That said, you will encounter fellow systems enthusiasts who speak the machine language of feedback, control, and signal. The models are attractive: reliable loops that balance or reinforce, structures that encourage stability or optimization. It will feel like understanding, and sometimes, it is.</p><p>But be careful. These ways of seeing can quietly become ways of believing, and before long, a living system starts to look like like a lifeless machine waiting to be tuned. What matters most in living systems is not information in the abstract, but meaning in context.</p><blockquote>The more a thing tends to be permanent, the more it tends to be lifeless. ― <strong>Alan Watts</strong></blockquote><p>Despite whatever notions may have drawn you toward systems thinking in the first place, this is not lesser work, though it’s often slower, and sometimes stranger.</p><p>But it <em>is</em> more alive.</p><p>Signed,<br><strong>A Fellow </strong>(Swamp) <strong>Traveller</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SR4dx9UN-X9nfcLV.jpg" /></figure><p><strong><em>Jen</em></strong><em> is co-founder and principal at </em><a href="https://www.topologyinsight.com/"><em>Topology</em></a><em> and was previously Chief Design Strategy Officer at Mad*Pow. Find her on </em><a href="https://www.linkedin.com/in/jbriselli/"><em>LinkedIn</em></a><em> and </em><a href="https://www.youtube.com/@topologyinsight"><em>YouTube</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13ab8e1d6108" width="1" height="1" alt=""><hr><p><a href="https://medium.com/topology-insight/letter-to-a-young-systems-thinker-13ab8e1d6108">Letter to a Young Systems Thinker</a> was originally published in <a href="https://medium.com/topology-insight">Topology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Apprenticeship Is Dead. Long Live Apprenticeship.]]></title>
            <link>https://medium.com/topology-insight/apprenticeship-is-dead-long-live-apprenticeship-1ddb789705ce?source=rss-e34fb3b7cd78------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ddb789705ce</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[knowledge]]></category>
            <category><![CDATA[coaching]]></category>
            <dc:creator><![CDATA[Jen Briselli]]></dc:creator>
            <pubDate>Tue, 18 Mar 2025 20:36:28 GMT</pubDate>
            <atom:updated>2026-01-01T22:05:49.703Z</atom:updated>
            <content:encoded><![CDATA[<h4>Expertise is a group project.</h4><figure><img alt="Image of several LinkedIn posts announcing coaching services" src="https://cdn-images-1.medium.com/max/1024/0*PoXFUMXYAdOG7E2i" /><figcaption><em>“Nobody wants to work anymore.”</em></figcaption></figure><p>If your LinkedIn feed looks anything like mine, perhaps you’ve noticed a recent uptick in the frequency of folks announcing their participation in mentorship matchmaking platforms, or the growing chorus of voices excited to share they <em>now offer coaching, </em>either as supplement to their current roles, or as a pivot following layoffs. Or, perhaps you, yourself, have felt called to become, or turned in desperation to seek, a [leadership / career / life] <em>coach</em>.</p><p>It’s not our imagination; coaching programs and credentials <a href="https://coachingfederation.org/blog/professional-coaching-continues-global-expansion#:~:text=As%20a%20result%2C%20coaching%20now,increase%20since%20ICF&#39;s%202020%20study.">are surging</a>. Online mentorship platforms like ADPList are seeing <a href="https://blog.adplist.org/post/celebrating-100-million-minutes-on-adplist">exponential growth</a>. And while the rise of coaching is intriguing, even more interesting is that it’s emerging not on the job but as an <em>extracurricular</em>. It raises a question:</p><blockquote><strong><em>Is coaching a canary in our professional coal mine?</em></strong></blockquote><p>There are plenty of explanations for this coaching boom, from pandemic and polycrisis inspired soul searching, to the <em>now what?</em> that follows a Great Resignation, Great Re-Org, or Great Layoff, to garden variety burnout intermixed with the existential threat of AI.</p><p>It’s no surprise that many displaced (yet highly experienced) professionals are turning to adjacent practices like coaching and mentorship, which have relatively low barriers to entry. But I’d like to be more generous than conclude a low barrier to entry is the primary impetus. Plus, we see the complementary sentiment among early career folks and those making mid-career transitions: employees who <a href="https://blog.adobe.com/en/publish/2023/09/27/adobe-future-workforce-study-what-us-employers-need-know-about-gen-z-workplace">crave</a> and <a href="https://fortune.com/2024/07/31/employees-want-coaching-at-work-managers-fall-short/">lament a lack of</a> workplace mentorship and career path guidance.</p><p>Why, despite employers’ efforts to meet these needs with mentorship programs and management training, are so many folks looking for each other <em>outside of the workplace?</em></p><p>I believe the lure of coaching (more generally, and yes, VC-owned for-profit mentorship platforms more specifically) is scratching at an itch that is deeper than career advancement, something more fundamental:</p><blockquote><strong>Learning</strong>.</blockquote><p>Humans are hardwired for learning. And we do it best in situated, social settings. People <em>seek</em> coaching where they feel insecure, uncertain, and eager to learn. And people <em>offer</em> coaching where they have confidence, experience, and wisdom to impart.</p><p>As adaptive organisms, we’re shaped by evolution (and our own social structures) to thrive on both sides of this learning equation. But, our professional environments, which have historically been the primary post-school home for both of these instincts, are changing in ways that make it much, much harder.</p><figure><img alt="Animated gif of Mickey Mouse from the Fantasia short called The Sorceror’s Apprentice, where Mickey has donned the sorceror’s hat and powers without permission or guidance." src="https://cdn-images-1.medium.com/max/528/0*O81cGe0xbJPCg0Ld.gif" /><figcaption>“We expect new hires to hit the ground running.”</figcaption></figure><p>This reciprocal learning dynamic has a name: <em>Apprenticeship.</em></p><p>Apprenticeship, at essence, is contextual learning — one of the most effective strategies humans have developed to share knowledge and grow expertise. We can trace it from the ancient Romans through medieval craft and merchant guilds, to modern trade unions, internships, cartels… and yes, your company’s corporate mentorship program.</p><p>It can take many forms, from highly structured training programs with prescriptive assignments and pre-arranged partnerships, to more casual, spontaneous learning opportunities that emerge and dissolve naturally as work projects and relationships evolve over time.</p><p>It’s the latter form of learning that is most relevant here, and <em>most at risk.</em> The <strong>informal apprenticeships</strong> that emerge organically, around the edges and spaces in between formal programs and organizational hierarchies, now struggle to survive amid asynchronous and increasingly mechanized knowledge work.</p><p>Many of today’s work environments, shaped by remote arrangements, assembly-line hiring strategies, and efficiency-obsessed management philosophies, have systematically dismantled the infrastructure that once supported apprenticeship relationships. Add to this mix the <a href="https://www.forbes.com/sites/lizelting/2024/08/06/companies-are-slashing-management-roles-is-unbossing-a-career-killer/">myriad layoffs and re-orgs</a> that shuffle us into ever more individualized, disconnected, and output-focused work.</p><blockquote>We’ve optimized for individual productivity and efficiency at the expense of collective learning.</blockquote><p>We see the consequences of a fractured system: new professionals struggle with a lack of guidance, space to grow, or both… while senior experts become disconnected from meaningful ways to share their hard-won wisdom. When we treat expertise as disposable, we end up with a lot of dispossessed experts.</p><p>And many will misdiagnose their frustration. Junior employees can blame a lack of advancement opportunities or unclear expectations, but transparent competency models and promotion rubrics don’t replace the confidence and intuition they would build working alongside experienced mentors. Senior professionals can chase a ‘seat at the table’ in search of agency and influence, but when climbing the hierarchy proves unfulfilling, they may abandon it all together.</p><p>Companies, sensing this gap, (or concerned about <a href="https://www.mckinsey.com/featured-insights/sustainable-inclusive-growth/charts/the-cost-of-unhappy-workers">bottom lines</a>), roll out formal mentorship programs and train managers to be ‘more like coaches,’ but these efforts often fall flat.</p><p>Why? Because we can’t formalize serendipity. We can’t schedule the kind of learning that happens when people work closely together over time. When apprenticeship is treated like a machine with interchangeable parts, we sever the very relationships that sustain it. And if we reduce learning to a transactional, mechanized process, we strip it of its power. No wonder so many now seek it outside the workplace.</p><figure><img alt="A shoemaker and his apprentice, 1914 painting by Emile Adan" src="https://cdn-images-1.medium.com/max/1024/0*RaqockGzxgnIA2gI.jpg" /><figcaption>the weekly 1-on-1</figcaption></figure><p>Thankfully, we don’t need over-engineered corporate initiatives or expensive mentorship platforms to facilitate learning and growth. We just need to recognize our work as <em>craft. </em>A synthesis of both theoretical knowledge and practical experience.</p><p>Yes, <em>craft</em>: everyone’s favorite buzzword. And yes, the term has connotations of material artifacts and hands-on trades, much like <em>apprenticeship</em>. But if you’ll indulge a broader interpretation (and a little ancient greek), consider that craft can be <em>more</em> than what Aristotle called <em>techné</em> (the skilled execution of a task). It’s also <em>poiesis: </em>the act of bringing something into being. That “something” includes relationships, ideas, and shared vision. In this sense, craft applies as much to the art of developing a compelling argument, or navigating a complex human social system, as it does to woodworking or interface design. It encompasses not only the deliberate refinement of skills, but also the nuanced and often invisible ways we <a href="https://us.sagepub.com/en-us/nam/the-dynamics-of-social-practice/book235021">engage in, and shape, social practice</a>.</p><p>For example, observation is central to apprenticeship, but we don’t have to imagine an apprentice watching a master carpenter build a piece of furniture or an electrician wiring a junction. Consider instead a junior designer learning by watching how their senior colleague navigates a tense client conversation, or how a respected peer adapts their communication when engaging with different stakeholders. In these moments, the <em>practice</em> of expertise isn’t just producing artifacts — it’s the interplay of experience, judgment, and fluid social fabric of work itself.</p><p>Of course, in cognitive work, much of the “doing” happens in the mind and out of sight, which adds a wrinkle.</p><figure><img alt="Son Of Man, painting by Magritte depicting a man with face obscured by an apple" src="https://cdn-images-1.medium.com/max/1024/1*_Wis_W_61o0geQA1CkcZtA.png" /><figcaption>out of sight, in the mind</figcaption></figure><p>This is where an instructional framework known as <a href="https://www.semanticscholar.org/paper/COGNITIVE-APPRENTICESHIP%3A-MAKING-THINKING-VISIBLE-Collins-Brown/712a1b8a88040d80db28f2751288b5a45d702014?utm_source=direct_link">cognitive apprenticeship</a> can be useful. Grounded in educational research and cognitive science, it makes implicit thought processes visible, and embeds learning in real-world contexts. The framework highlights six types of activity:</p><p><strong>Modeling:</strong> Making invisible thought processes visible <em>(*a caveat on this below), </em>so others can see how complex challenges are approached and navigated in practice.</p><p><strong>Coaching:</strong> Providing timely guidance, feedback, and support in a way that helps others refine their thinking and actions while maintaining autonomy.</p><p><strong>Scaffolding:</strong> Structuring interactions and environments to offer <em>just enough</em> support to enable progress, and then gradually scaling back as confidence and capability grow.</p><p><strong>Reflection:</strong> Creating space to examine and <a href="https://commoncog.com/the-hard-thing-about-learning-from-experience/">reinterpret past experiences</a>, surface insights, and refine approaches — individually or collectively — to improve future outcomes.</p><p><strong>Articulation:</strong> Encouraging metacognition and open discussion of reasoning, choices, and intuitions, helping teams and individuals clarify understanding and gain coherence.</p><p><strong>Exploration:</strong> Supporting curiosity, experimentation, and independent problem-solving to foster adaptability and continuous learning in fluid situations.</p><p>Crucially, it’s not just about <em>how</em> learning happens, but also <em>where</em> and <em>with whom</em>. Expertise isn’t merely a personal trait; it’s embedded in relationships and shared experiences. And, that distributed expertise is developed particularly well within <a href="https://www.wenger-trayner.com/introduction-to-communities-of-practice/"><em>communities of practice</em></a>:<em> </em>groups of people who share and refine knowledge collectively over time. Within such communities, knowledge flows naturally between experienced practitioners and newcomers through an ongoing process of collective sense-making and problem-solving.</p><p>This means that beyond structured techniques like modeling and coaching, social and environmental factors such as collaboration, shared goals, and cultural norms deeply shape how expertise develops. Healthy communities of practice are generally marked by:</p><p><strong>Situated Learning</strong>: Learning is most powerful in real-world contexts, where knowledge refined through ongoing practice rather than isolated training or abstract discussion.</p><p><strong>Meaningful Peripheral Participation</strong>: Newcomers contribute in small but meaningful ways, gradually increasing responsibility and expertise through guided experience within the community.</p><p><strong>Continuously Evolving Meaning: </strong>The community collectively adapts to emergent goals and challenges, shaping the direction of its learning and development through ongoing dialogue and evolving shared narratives.</p><p>This contextual layer helps explain why some organizations seem to cultivate talent and innovation more easily than others. Knowledge work, like any craft, thrives when there are opportunities for informal learning, peer exchange, and gradual deepening of expertise through real engagement with the work itself.</p><figure><img alt="Screen from the end of classic NES video game Bubble Bobble that says “try again with your friend.”" src="https://cdn-images-1.medium.com/max/411/0*Ll7c240D8AUqvMOX.jpg" /><figcaption>Take a cue from Bubble Bobble. It’s better in multiplayer.</figcaption></figure><p>Of course, many aspects of expertise emerge through intuition, serendipity, and indirect experience, meaning that more oblique, less goal-directed learning plays a crucial role that cannot be neglected. Apprenticeship isn’t simply a matter of transferring knowledge from one person to another, and much of what makes someone effective in their field, like professional judgment, situational awareness, and creative problem-solving, emerges through immersion, observation, and experience rather than direct instruction.</p><p>So, while externalizing our knowledge via modeling and other think-aloud methods are useful, frameworks like cognitive apprenticeship cannot seek to make <em>all</em> <em>tacit knowledge explicit</em>; they just help us surface the invisible but otherwise accessible aspects of expertise — emotions, questions, and our messy interior monologues. It’s only one valuable tool among many for developing expertise, but not all knowledge can, or should, be codified.</p><p>To better understand the tension between tacit and explicit knowledge (and to avoid the <a href="https://thecynefin.co/the-tyranny-of-the-explicit-2/?srsltid=AfmBOoqqFFNJHEx3y3LSJpIhrt-sQaM0dubydJg51kp6twJgop4R2X8a"><em>tyranny of the explicit</em></a><em>), </em>it helps to draw on another framework: Boisot’s <em>I-Space. </em>Instead of treating learning as an additive process like 3D printing, the I-space maps the <em>flow</em> of information: how it is shared, transformed, and internalized within a community or organization. It illustrates <a href="https://www.amazon.com/Explorations-Information-Space-Knowledge-Organization/dp/0199250871">how knowledge moves through different states as it becomes structured, generalized, and diffused</a>.</p><figure><img alt="Image a cube depicting the I-space framework described below." src="https://cdn-images-1.medium.com/max/1024/1*9Fn-Zo-VdXRsOGKExl1O6w.png" /><figcaption>The I-Space; from <a href="https://www.amazon.com/Collisions-Collaboration-Organization-Learning-Experiment/dp/0199567921">Collisions and Collaboration</a></figcaption></figure><p>The I-Space visualizes knowledge as it exists along three key dimensions:</p><p><strong>Codification</strong>: How structured or formalized knowledge is (e.g. explicit instructions vs. tacit know-how)</p><p><strong>Abstraction</strong>: The degree to which knowledge is generalized or contextualized (e.g. universal principles vs. situational practices)</p><p><strong>Diffusion</strong>: The extent to which knowledge is shared across a network or community (e.g. widely accessible open-source resources vs. specialized expertise within a small group).</p><p>Within this framework, we can see how knowledge evolves from individual learning to collective understanding and, ultimately, to shared practice through a <strong>social learning cycle</strong>. This social learning cycle can be envisioned as a path through the I-Space:</p><p>scanning → codification → abstraction → diffusion → absorption → impacting</p><figure><img alt="Image of cube depicting the social learning cycle described below." src="https://cdn-images-1.medium.com/max/1024/1*SrP9PeSQJ2VV0mgtOMxxKg.png" /><figcaption><em>The social learning cycle: Wheeeeeeee…</em></figcaption></figure><p>Apprenticeship, whether formal or informal, is an incredibly effective and adaptive means of facilitating this cycle. While it sounds abstract, in practice, it unfolds in a familiar progression:</p><p><strong>1. Learning By Watching and Doing: </strong>A novice observes a more experienced colleague, absorbing tacit knowledge that is difficult to articulate. As they copy key aspects of the colleague’s work, they start to recognize patterns.</p><p><strong>2.</strong> <strong>Making Sense of It: </strong>Over time, the novice moves beyond passive observation and begins putting what they’ve learned into their own words. They develop guiding principles, shifting from imitation to deeper understanding.</p><p><strong>3.</strong> <strong>Sharing and Improving: </strong>As they grow more confident, they experiment with new approaches and their refined understanding diffuses through interactions with peers, influencing the craft and enriching the broader community.</p><p>For example, imagine a junior employee shadowing a senior colleague as they facilitate a client workshop. At first, the junior employee focuses on the mechanics, noticing how their senior colleague plans the agenda and navigates competing interests among stakeholders. They observe subtle ways the facilitator reads the room, adapts the agenda in real time, and manages challenging group dynamics. Over time, the junior employee takes on small responsibilities, such as running breakout sessions, capturing insights, or leading a brief exercise. As they gain confidence, they start co-facilitating, experimenting with different approaches and refining their ability to guide productive conversations. Eventually, they lead their own sessions, adapting their approach based on experience and reflection. In doing so, they not only refine their own skills but also contribute new ideas that evolve their team’s shared practice. Of course, for this to be possible, <em>they must first be included… even before they’re ready to “add value.”</em></p><p>Apprenticeship here is not just a mechanism for skill-building. It is the bridge between the abstract and concrete, explicit and tacit, individual and collective. It is an essential process by which knowledge stays alive — reshaped and reinterpreted through every interaction, over days, years, and generations.</p><figure><img alt="Image of water flowing into an estuary or shoreline, by Aaron Doucett on Unsplash." src="https://cdn-images-1.medium.com/max/1024/1*Vh7tVcYHYXiIMUsE7_Vu7g.jpeg" /><figcaption>knowing stuff</figcaption></figure><p>Boisot’s framework also highlights a critical tension: while the social learning cycle models a theoretical “flow of knowledge,” in reality, knowledge does not follow a predictable, linear sequence. The process is far messier, shaped by complex relationships and the unpredictable influence of experience on understanding. And knowledge itself really isn’t a <em>something</em> that <em>flows</em> at all, unless we confuse it with information. Knowledge, or better yet, <em>knowing</em>, is not a passive object, but an emergent and active process of connecting. Learning isn’t a cycle so much as a complex ecology of cycles.</p><p>Meanwhile, codification and abstraction, useful as they are in some domains, can be totally ineffective in complex systems. Not all knowledge can be neatly extracted, stored, and reapplied. Tacit knowledge, by its nature, defies articulation, and formalized diffusion necessarily sacrifices the nuances of context-sensitive, real-world application.</p><p>What’s more, both expert and apprentice are shaped by their interactions, co-evolving as they engage within a distributed learning network. And as apprentices observe and participate, they imitate not just their mentors but also their peers, integrating experiments and adjustments along the way.</p><p>Taken together, these dynamics keep knowledge alive — not merely preserved, but continuously evolving. It’s what makes apprenticeship so powerful, and why its absence leaves such a void. When we neglect the human instinct for learning in our organizations, this evolution stalls.</p><p>Sustaining it requires the right conditions. Experiential and social learning have a deeper impact than direct instruction alone, and the <em>informal apprenticeships</em> that reinforce it best will emerge most naturally within <strong>informal networks</strong>: the webs of trust, shared curiosity, and mutual investment, (<em>not</em> process diagrams or mission statements). These networks can’t be forced into existence, nor can they be precision engineered through corporate initiatives. But they <em>can</em> be enabled and encouraged — obliquely, with intention.</p><p>Informal networks function as the connective tissue of an organization. They are the hallway conversations, the Slack DMs, the spontaneous collaborations that arise when people trust and relate to each other. Unlike formal organizational structures, informal networks are fluid and self-sustaining, growing stronger as people invest in relationships rather than in protocols. Recognizing and fostering these networks — without over-engineering them — can help restore the natural learning pathways that many workplaces have lost. For a lot of organizations, it looks like:</p><p><strong>Sustained Collaboration</strong> — Creating opportunities for small, diverse groups to work together over extended periods. Learning deepens when people build familiarity and trust over time.</p><p><strong>Synchronous Learning Spaces</strong> — Prioritizing real-time problem-solving and interaction, rather than relegating apprenticeship to a scheduled quarterly meeting.</p><p><strong>Reflection and Dialogue</strong> — Making space for discussion alongside task completion, so that experience turns into understanding.</p><figure><img alt="Moss growing between bricks, by Tom Dils on Unsplash" src="https://cdn-images-1.medium.com/max/1024/1*konZ2F_Ki8rf5TrsWgfesA.jpeg" /><figcaption>there’s a lot about informal learning we can lichen to moss</figcaption></figure><p>So, where do <strong><em>you</em></strong> fit into all of this?</p><blockquote>Where, when, and with whom do you consider yourself an apprentice vs. a master?</blockquote><p>Of course, the roles are fluid. It’s context-dependent. Each of us is an expert and an apprentice in different contexts, in relation to different people, with different forms of knowledge. What remains constant is the need for spaces where learning isn’t a transaction, but a shared pursuit. Apprenticeship isn’t something that happens to you. It’s something you actively co-construct. The question isn’t just what you need to learn, but how you create the conditions for it in the first place.</p><h4><strong>When you’re the apprentice:</strong></h4><p>Mentorship and knowledge are everywhere, but you have to take notice and be open to receiving. Cultivate a practice of noticing, inquiring, and reflecting. Seek out people and environments that intrigue and challenge you; curiosity doesn’t shine a spotlight on your ignorance so much as lights up the path to discovery. Figure out how to absorb knowledge from observation as easily as direct instruction. Learning isn’t passive; take ownership of your growth by applying what you learn, experimenting, and refining your understanding in the open where others can contribute.</p><blockquote>Knowledge isn’t free. You have to pay attention.</blockquote><blockquote><em>— Richard Feyman</em></blockquote><h4><strong>When you’re the mentor:</strong></h4><p>Don’t wait for permission to collaborate or for requests to share. Be generous with your knowledge and experience. Remember that when you explain something, you’re only scratching the surface; below your explicit explanations are a depth of tacit wisdom that others can better access by working and playing alongside<em> </em>you. Recognize apprenticeship is not a one-way street. Every conversation, challenge, and question evolves your own understanding. Teaching sharpens thinking, and sharing what you’ve learned doesn’t just help others — it expands your own mastery.</p><blockquote>Whoever teaches learns in the act of teaching, and whoever learns teaches in the act of learning.</blockquote><blockquote><em>— Paulo Friere</em></blockquote><h4><strong>When you have power or influence in a community or organization:</strong></h4><p>Support learning, but don’t try to control it. Mentorship and growth don’t thrive under rigid structures — they flourish in environments where curiosity and connection are encouraged. Resist the urge to formalize or incentivize mentorship; imposed structures can distort the relationships that make learning meaningful. Instead, cultivate conditions where informal learning networks and communities of practice emerge naturally. Pay attention to the signals of organic apprenticeship unfolding, nurture its growth, and protect the time and energy it needs to thrive. Leadership’s role isn’t to drive the learning — it’s to make room for it.</p><p>Experiment with ideas like <a href="https://www.wenger-trayner.com/systems-convening-book/">systems convening</a>, <a href="https://cynefin.io/wiki/Social_network_stimulation">social network stimulation</a>, <a href="https://www.microsolidarity.cc/">microsolidarity</a>, <a href="https://www.liberatingstructures.com/">liberating structures</a>, <a href="https://batesoninstitute.org/warm-data/">warm data</a>, and the <a href="https://cdn.cognitive-edge.com/wp-content/uploads/sites/2/2020/11/16123947/52-Bramble-Bushes-in-a-Thicket-1.pdf">role of narrative in learning networks</a>.</p><blockquote>Effective learning environments are those that reflect the way people naturally learn — through relationships, experience, and shared inquiry.</blockquote><blockquote><em>— Ivan Illich</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LUPT_17PMk-dvFhKMYQ4NA.jpeg" /></figure><p>If we want to build resilient, adaptive, and thriving professional communities, we need to rethink the way we cultivate expertise. Apprenticeship — organic, informal, and deeply human — has always been the backbone of knowledge sharing. Yet, in the pursuit of efficiency, we’ve neglected the environments that make it possible.</p><p>The challenge isn’t just one of individual growth but the collective survival of expertise itself. Whether in families, communities, or across industries, knowledge that isn’t actively shared, refined, and reinterpreted fades into obscurity. What type of wisdom matters most to you? What role will you play in keeping it alive ?</p><p><strong><em>Jen</em></strong><em> is co-founder and principal at </em><a href="https://www.topologyinsight.com/"><em>Topology</em></a><em> and was previously Chief Design Strategy Officer at Mad*Pow. Find her on </em><a href="https://www.linkedin.com/in/jbriselli/"><em>LinkedIn</em></a><em> and </em><a href="https://www.youtube.com/@topologyinsight"><em>YouTube</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ddb789705ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/topology-insight/apprenticeship-is-dead-long-live-apprenticeship-1ddb789705ce">Apprenticeship Is Dead. Long Live Apprenticeship.</a> was originally published in <a href="https://medium.com/topology-insight">Topology</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>