<?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 Johann Richard on Medium]]></title>
        <description><![CDATA[Stories by Johann Richard on Medium]]></description>
        <link>https://medium.com/@johannrichard?source=rss-1ec4d4028acb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Hd11Up-2XZQt3gnH.jpeg</url>
            <title>Stories by Johann Richard on Medium</title>
            <link>https://medium.com/@johannrichard?source=rss-1ec4d4028acb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 14:46:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@johannrichard/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[Of things, small and inconspicuous]]></title>
            <link>https://medium.com/@johannrichard/of-things-small-and-innocuous-254aa7fd3f94?source=rss-1ec4d4028acb------2</link>
            <guid isPermaLink="false">https://medium.com/p/254aa7fd3f94</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[legacy]]></category>
            <category><![CDATA[eulogy]]></category>
            <category><![CDATA[details]]></category>
            <category><![CDATA[reality]]></category>
            <dc:creator><![CDATA[Johann Richard]]></dc:creator>
            <pubDate>Sun, 19 Jul 2020 22:46:30 GMT</pubDate>
            <atom:updated>2020-07-22T06:59:41.201Z</atom:updated>
            <content:encoded><![CDATA[<h4>Eulogy for my dad (1931–2017)</h4><p>Three years ago, in August 2017, my dad passed away. He died in peace, and in the presence of his beloved wife. In his own words, and also from my point-of-view, he passed away after what can be called a <em>fulfilled</em> <em>life</em> of almost 86 years. We had just visited him the day before his death with our kids, and we were hiking in his beloved, beautiful Swiss Mountains when he passed away. It was, and still is, a loss one can not really fathom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xGoBvpYU5bmebcp8Ou2rwA.jpeg" /></figure><p>The months, even years before, as his body became weaker an weaker after a seemingly small and silly injury from the pinch of a car door, he used to tell my mother, and my siblings and me, that “<em>he had lived his live, had not too many big regrets. That he was ready to go.</em>” And as painful as this affirmation was on the one hand, it was at the same time reassuring to know that he was truly at peace with his — not always easy — life. Luckily, his mind was clear until the end, and while we saw the physical decline, we could indeed share a few more years with him, revelling in memories, and expressing our appreciation and gratitude for the years we’d shared.</p><p>Despite my intention to offer an eulogy at his funeral, I backed off in the few days after his dead — despite the fact that I had collected and thought a lot about the things I would want him to be remembered for by others and particularly myself. Somehow, it did not feel right.</p><p>This all changed, though, when recently, I came across <a href="http://johnsalvatier.org/blog/2017/reality-has-a-surprising-amount-of-detail">an article</a> by John Salvatier titled “Reality has a surprising amount of detail”. Incidentally, John had written it only three months before my dad’s passing. And reading it was the trigger for something that had waited too long to be written by myself and delivered. But finally, here it is. An eulogy for my dad, and a testament to his legacy.</p><h4>Of things, small and inconspicuous</h4><p>My father was a modest, unassuming man. Because he was barred from the opportunity to study, he learned the profession of a gardener and, after some years of travel and work abroad, he, together with my mother, raised a family somewhere in the Swiss countryside. By all measures, their life (and so ours) was anything but spectacular.</p><figure><img alt="My Mom and Dad, the day of their wedding" src="https://cdn-images-1.medium.com/max/1024/1*msW3wnlS5RZSmPHlGSLcXg.jpeg" /><figcaption>Mom and Dad, the day of their wedding, anno 1969</figcaption></figure><p>During his professional and personal life, he not only acquired an incredible knowledge of botany, including the Latin names of flowers, shrubs and other plants known and unknown to me, but also of the fauna and geology. What he pursued, he pursued silently, but with much dedication and love. Although he usually worked long hours rather far from home, he shared his passions with us kids as much as he could, especially when gardening at home, when hiking in the mountains or when sharing anecdotes about his time abroad.</p><p>Unfortunately, the only passions I truly share with him are a love for the violin, for travel, foreign countries and cultures, and for reading: I have not yet become interested in botany as much as he did. And although I enjoy and cherish the wilderness of the mountains and Switzerland’s breathtaking views, or the intricate details of fern or the wild tenderness of orchids, I have yet to develop the same dedication and passion for flora and fauna as he did.</p><p>And yet: in the last years of his degrading health, when I was trying to boil down what I cherished most about the things I learned from him (and told him so), one thing consistently came to mind: my dad’s peculiar attention to the seemingly inconspicuous, almost unimportant, details of life and reality around him.</p><p>Often, when we came across a plant or an animal (mostly birds) or some seemingly random stone, he would share an anecdote or a bite of knowledge with us, or he would point out something small he’d noticed along the way. Sometimes, we couldn’t understand his excitement. And his almost childlike curiosity to perceive more of the reality around him seemed almost boundless.</p><p>Yet somehow, he’d passed this curiosity, this love for inconspicuous, seemingly unimportant detail on to me. For a long time, I was not aware of this, but later I found myself noticing the odd snail on the road, a pattern of clouds nobody else seemed to care about, or a funny coincidence of two events that I’d noticed. And when I eventually did realize I’d inherited this “<em>urge</em>” to notice small, unimportant things, I was at times struggling with it — especially as others would see this urge as slightly, if not outright, annoying and distracting from “<em>important things</em>”.</p><p>But there it was, and it would not go away. And the more I became aware of it, the more I thought about it, and the less I finally managed to care what others thought about it, the more I somehow sensed that this urge to notice <em>small</em>, <em>unimportant</em> things about reality <em>was</em> probably one of the lasting legacies my father had left with me.</p><p>Only that it was a nebulous, almost an anecdotal legacy: I somehow could never really pinpoint “<em>why</em>” it was important.</p><p>Until I came across John’s <a href="http://johnsalvatier.org/blog/2017/reality-has-a-surprising-amount-of-detail">article</a> and the following passages:</p><blockquote>[If you wish to not get stuck], seek detail you would not normally notice about the world. When you go for a walk, notice the unexpected detail in a flower or what the seams in the road imply about how the road was built.</blockquote><blockquote>If you wish to not get stuck, seek to perceive what you have not yet perceived.</blockquote><p>This instantly struck a whole violin of chords with me¹. Finally I can not only subtly sense the legacy— but see through it, and, more importantly name it:</p><blockquote>What my father taught me is this: to relentlessly seek detail I would not normally notice about the world. To notice the unexpected and to perceive what I have not yet perceived.</blockquote><p>And while I will continue to annoy the people around me with my stubborn, relentless curiosity about the “<em>unimportant”</em> details of reality and life, I will now do so with an even deeper appreciation for the legacy my father left me.</p><p><em>In loving memory of my dad, Werner Richard, 1931–2017. I will forever be grateful for his presence in my life.</em></p><h4>Epilogue: “Reality has a surprising amount of detail”</h4><p>In “<a href="http://johnsalvatier.org/blog/2017/reality-has-a-surprising-amount-of-detail">Reality has a surprising amount of detail</a>”, <a href="https://twitter.com/johnsalvatier">@johnsalvatier</a> writes about the stunning amount of detail we have to care about in solving any reasonably complex problem:</p><p><em>“The more difficult your mission, the more details there will be that are critical to understand for success.”</em></p><p>Yet, despite their importance, we often don’t perceive these important details as the critical element they are, as “<em>[important] details aren’t automatically visible, even when you’re directly running up against them.</em>”</p><p>So, how to avoid getting stuck because of details we can’t yet see?</p><p>“<em>This problem is not easy to fix, but it’s not impossible either. […] The direction for improvement is clear: seek detail you would not normally notice about the world. […] As you learn, notice which details actually change how you think.</em>”</p><p>Today, I still notice details about the occasional snail, or a pattern of light, a surprising coincidence of events — and I enjoy each and every one of these discoveries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*gLv_5tGHqs0xkf2TdgDyUQ@2x.jpeg" /></figure><p>But more and more, I also realize how this helps me tremendously with my work, and personal life:</p><ul><li>The ways a colleague works and processes information,</li><li>The ways she reacts when information does <em>pique</em> her interest — and her reasons for her reaction,</li><li>Details in a negotiation which, if noticed, can open a door to a compromise — or break the deal if they are not seen,</li><li>Small changes in language of partners which hint at upcoming changes in policy or strategy,</li><li>Small, but consistent patterns of behavior of colleagues, friends, and family which can hint at underlying unease, or communications problems,</li></ul><p>If I can seek these patterns and details consistently, my work, and my interactions with the human beings around me become much more effective, but also more appreciative, empathic and kind.</p><p>I think this alone is worth being the “<em>odd guy</em>” who notices things no one else cares about.</p><p>¹: The violin is the instrument both my dad and I love/d and play/ed. Another passion we shared.</p><p><em>21.7.2020: Edited for some linguistical clarifications</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=254aa7fd3f94" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simon Parker on the future of government: Complex problems, systems thinking, and a reframing of…]]></title>
            <link>https://medium.com/@johannrichard/why-good-policies-create-places-worth-living-in-416e1fe0d625?source=rss-1ec4d4028acb------2</link>
            <guid isPermaLink="false">https://medium.com/p/416e1fe0d625</guid>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[policy-making]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Johann Richard]]></dc:creator>
            <pubDate>Wed, 15 Jul 2020 18:28:23 GMT</pubDate>
            <atom:updated>2020-07-16T07:17:26.079Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc/4.0/</cc:license>
            <content:encoded><![CDATA[<h3><a href="https://medium.com/u/773ba0fdc802">Simon Parker</a> on the future of government: Complex problems, systems thinking, and a reframing of the purpose of government</h3><h4>Or: why — and how — good policies create “places” worth living in</h4><p>Today, the <a href="https://twitter.com/staatslabor">@staatslabor</a> shared <a href="https://medium.com/@SimonFParker/conservative-anarchism-self-organisation-and-the-future-of-government-2ef5447b7f02">an article</a> by <a href="https://medium.com/u/773ba0fdc802">Simon Parker</a>. As they wrote: <a href="https://us14.campaign-archive.com/?u=7b20cde35ddc978526642606a&amp;id=13233be337&amp;e=a8f9f0ded1"><em>Read Simon’s essay. Really. It’s good</em>.</a> I trust them (really!) and so I jumped right into reading it (bye-bye productivity!) And indeed: What Simon wrote instantly struck a chord (well, <em>four</em>) with me.</p><p>In fact, it was so good, it sent me down a rabbit hole and prompted me to write this post, theorizing on the following<em>:</em></p><blockquote><em>“Good policies create “places” worth living in.”</em></blockquote><p>So, here are some ideas on how to approach policy design with insights from architecture and systems thinking, and how this might lead to better policies.</p><h4>Public service is about highly complex problems</h4><p>In his article, when talking about agile and design thinking in government, Simon sums up nicely what I somehow always felt but never could articulate, and definitely not so succinctly:</p><blockquote>A lot of <strong>people have gotten stuck [when applying agile and design thinking in government]</strong>. They […] discover powerful ways to create human-centred services, but then cannot understand why the world isn’t changing. <strong>The answer is simple: public service isn’t really about services, but about highly complex problems.</strong></blockquote><p>Once you look at it this way, you can recognize that many innovation initiatives in government stop exactly there: With new innovation methods, agile project management. Of course, I’ve been guilty of that innovation frenzy too, and mileage certainly varies wildly across initiatives. You need tools — methods and management practices — that help civil servants and their organizations break out of old habits, that help them redesign services that work and appeal to citizens. But these are not enough.</p><p>So how can public service approach these highly complex problems? What would public service have to look like?</p><h4>A new purpose for public service?</h4><p>In the article, Simon does an excellent job in describing many of the changes we are about to witness, and why systems thinking concepts might be a natural next step after agile and design thinking. And he outlines a proposal for a new purpose for future government:</p><blockquote>“Government should aim to maximise self-organisation.”</blockquote><p>This struck a second chord: Here in Switzerland, policy and governance are generally understood to be about creating good (excellent) boundary conditions — and to let the people and organisations then fill the space that these boundary conditions create with life; to use it for their goals and ambitions (or needs). “<em>Adult-adult mode</em>”, as Simon also calls it.</p><p>(N.B.: I have yet to hear someone argue that the public management approach in Switzerland “<em>maximises self-organisation</em>”, but there is something to that idea — some similarities, but also some differences. I won’t go into these today.)</p><p>I also couldn’t agree more with Simon that the <a href="http://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/">12 leverage points of Donella H. Meadows</a> provide a lot of food for thought to think about the “<em>Where</em>” to intervene in the system.</p><p>Yet, both the concept of systems thinking <em>and </em>the idea of leverage points say little about “<em>How</em>” governments could aim to maximise self-organisation.</p><p>Where agile and design thinking are both practical methods, systems thinking is obviously a concept, a school of thinking and a way to look at the world — and so it needs its own practical language, methods and heuristics when applied to a system like a government or the “results” this government produces through its policymaking.</p><h4>How to support people and organisations in self-organisation</h4><p>This is where Simon’s article struck the third chord with me: Assuming there is some consensus on the “<em>Why</em>” — that governments should aim to maximise self-organisation — the question we then must ask is the following:</p><blockquote><em>How </em>can governments (or civil servants, to be precise) design policies and policy interventions in a way that optimally support people and organizations in maximising their respective amount of self-organisation?</blockquote><p>I don’t have much of an answer yet to this “<em>How</em>” (and I am looking for any hints and inspiration and <em>food for thought</em>), but my fascination with architecture — and its approach to design — has recently led me down a rabbit hole of thought, which I already <a href="https://medium.com/@johannrichard/of-patterns-and-dancing-architecting-ecosystems-and-bureaucracies-4da01b587238">wrote about</a> elsewhere.</p><p>There, I argued that architectural patterns and theory of architectural design might serve as inspiration for tackling policy design and the kind of complex problems public service deals with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*TfguqzNWKEi6jdprzyTLuQ.png" /><figcaption>15 fundamental properties (From The Nature of Order, Christopher Alexander)</figcaption></figure><p>In a nutshell, I think that Alexander’s 15 <em>fundamental properties</em> of well-architected systems are a high-level pattern language that we can use when working on policy design. And so we can apply them when thinking about <em>how</em><strong><em> </em></strong>governments can optimally support the aim of maximising self-organisation — both within the public service (the bureaucracy) and when the public service is designing policies and policy interventions.</p><blockquote>I am deeply convinced that precise, well-crafted language has the power to transform systems at large, even defying strategy, structure and even culture.</blockquote><p>By using the <em>fundamental properties </em>as such a shared and precise language — by defining carefully what the language means when used in policymaking — we might have a very powerful instrument at our disposal, one that can help with better policy and systems design.</p><h4>But what can we do now?</h4><p>To this point, we have, together with <a href="https://medium.com/u/773ba0fdc802">Simon</a>, been looking at a potential “<em>Why</em>” of future governments — the proposed aim to maximise self-organisation; and we have had a peek at “<em>How</em>” this could be achieved, potentially, by using the pattern language of Christopher Alexander’s fundamental properties as a new tool in our design of policies.</p><p>What we haven’t answered yet is the “<em>What</em>” that inevitably follows these two questions: <em>What</em> could we do now?</p><p>A natural answer (one, I must admit, that I’ve entertained as well in the past) could be <em>to disrupt the state</em>, to <em>tear bureaucracies apart</em> <em>— </em>or, as Schumpeter declared for economics: to<em> transform the state through </em><a href="https://en.wikipedia.org/wiki/Creative_destruction"><em>creative destruction</em></a><em>.</em></p><p>But is it a good answer? <a href="https://medium.com/u/d132d950256a">Rainer Kattel</a> (among others) doesn’t think so, and personally, I concur.</p><p>In <a href="https://medium.com/iipp-blog/what-makes-states-entrepreneurial-7dd397d1fc70">his article on the Entrepreneurial State</a>, Kattel outlined that for the state to become more agile or <em>innovative, </em>it is indeed popular to call for the disruption of said state. But also, that this is indeed not a new idea:</p><blockquote>“<em>Today’s popular call to disrupt the government through innovation is, to say the least, as old a hat as that on the head of a Renaissance soldier of fortune in an Uccello painting.</em>”</blockquote><p>But ultimately, he <a href="https://medium.com/iipp-blog/what-makes-states-entrepreneurial-7dd397d1fc70">concludes that</a></p><blockquote><em>“Capacity for innovation in bureaucracy is about having the space — skills, networks, organisations — for </em><strong><em>both agility and stability.</em></strong>”</blockquote><p>And this nicely resonates with <a href="https://medium.com/u/773ba0fdc802">Simon</a> again and the take-way from his debates with <a href="https://enspiral.com/">Enspiral</a>:</p><blockquote>“[Y]ou should not and cannot strive for structurelessness in organisations and society. The attempt to dismantle hierarchy often leads to new, secretive hierarchies emerging behind the scenes. The state <strong><em>is </em></strong>a hierarchy and there are some good reasons for that. <strong>Let’s not try to deny its essential nature</strong>.”</blockquote><p>Fourth chord. But: no answer yet on how can we achieve this agility <em>and </em>stability. No answer how can we honour these essential structures of the organisations we’re working with <em>and </em>bring meaningful change to them.</p><h4>Structure-preserving transformation</h4><p>I would propose that one approach is to again look at Alexander’s work, specifically at his concept of “<em>structure-preserving transformations</em>” that he offers in “The Nature of Order”.</p><p>Nikos A. Salingaros, in <em>Design for a Living Planet[1], </em>writes the following about this approach to design:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vGaNIvWuFHDJTBkGW9IhcQ.png" /><figcaption>Structure-preserving and -destroying transformations (own illustration)</figcaption></figure><p><em>“This idea of design — as “transformation” using an adaptive process — is very much at the heart of […] Christopher Alexander’s work. Through that adaptive process, we generate a form that achieves our “preferred” state. But at each step of this transformation, Alexander says, we are dealing with a whole system — not an assembly of bits.”</em></p><p><em>(Design for a Living Planet, </em><a href="https://patterns.architexturez.net/doc/az-cf-172573"><em>Chapter 20</em></a><em>)</em></p><p>Besides building on the <em>fundamental properties</em>, I think that Alexander’s adaptive approach of “<em>structure-preserving transformations</em>” offers a real answer to the <em>what</em> we can and shall do when thinking about <em>optimising self-organisation </em>through the lens of the <em>fundamental properties</em>: to start with a (simple) system and change it in a way that <em>preserves the structure of the previous step.</em></p><blockquote>“Complex systems do not spring into existence fully formed, but rather through a series of small, incremental changes.</blockquote><blockquote>The process begins with a simple system and incrementally changes that system such that each change preserves the structure of the previous step.” (from Wikipedia: <a href="https://en.wikipedia.org/wiki/The_Nature_of_Order">The Nature or Order</a>)</blockquote><h4><em>Agility and stability</em></h4><p>I think the works of people like Christopher Alexander and Donella H. Meadows can offer us great insights and concepts on how to think about the systems and policies we design and interact with, and how we implement our policies.</p><p>Personally, I find the idea intriguing of a practical approach using their concepts and language intriguing. From the dancing with the system (Meadows) to the algorithms of “structure-preserving transformation” and the “language” of the fundamental properties we use as the programming language of these algorithms (both Alexander): I think their work can offer a compelling — and surprisingly precise — framework for those working in the public service, for those tasked with creating better policies or working to innovate their bureaucracies.</p><p>In the end, a policy can be seen as a blueprint for a “place” of sorts. And this place — with its shape and function, with its deficiencies and strengths — is intricately linked to the way its blueprint was created, to the way the policy was designed (A bit like <a href="http://melconway.com/Home/Conways_Law.html">Conway’s Law</a>, but with an architectural/spatial twist, if you want. But I digress).</p><p>Once the policy is implemented (when the new “place” is finally brought into existence), people and organizations will start inhabiting the place which the policy created.</p><p>If the policy embodies the idea of “structure-preserving transformations”, if it is built on sound principles of architectural design, then this policy will equally honour the past <em>and </em>prepare for the future. The place this creates will offer us both: agility and stability.</p><p>A place that is brought into existence through such a well-designed policy will presumably be filled with brimming life, <em>self-organised</em> by its “inhabitants”.</p><blockquote><em>And a system transformed in such a way will indeed become a place worth living in</em>.</blockquote><p><em>The writing here is an attempt to give some much-needed structure to my thinking and solely represents my own views. I look forward to exploring these thoughts and threads even more and would love to hear your comments about that!</em></p><p><em>This post is a result of the </em><a href="https://jarche.com/pkm/pkm-workshop/"><em>excellent Personal Knowledge Mastery Workshop</em></a><em> by </em><a href="https://twitter.com/hjarche"><em>Harold Jarche</em></a><em> which I highly recommend to everybody interested in better managing their personal knowledge mastery.</em></p><h4>References</h4><p>[1]: <a href="https://patterns.architexturez.net/doc/az-cf-172573"><em>“Ch 20. Alexander’s “Wholeness-Generating” Technology</em></a>.” In <em>Design for a Living Planet: Settlement, Science, &amp; the Human Future</em>, 198–208. Design for a Living Planet: Settlement, Science, &amp; the Human Future. Levellers/Sustasis Press and Vajra Publications, 2015. <em>(Original Publication: </em>Metropolis Mag, 24 Oct 2011)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=416e1fe0d625" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Of patterns and dancing: architecting ecosystems and bureaucracies]]></title>
            <link>https://medium.com/@johannrichard/of-patterns-and-dancing-architecting-ecosystems-and-bureaucracies-4da01b587238?source=rss-1ec4d4028acb------2</link>
            <guid isPermaLink="false">https://medium.com/p/4da01b587238</guid>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[architecting]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[pkm]]></category>
            <dc:creator><![CDATA[Johann Richard]]></dc:creator>
            <pubDate>Sun, 12 Jul 2020 15:52:40 GMT</pubDate>
            <atom:updated>2020-07-15T07:23:09.382Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>What happens if we apply (design) patterns to how we architect ecosystems and bureaucracies?</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*kiuRgwRBXsBO4f1U5g7ReQ.jpeg" /><figcaption>“A Pattern Language” by Christopher Alexander, Sara Ishikawa and Murray Silverstein</figcaption></figure><blockquote>“<em>Defy the disciplines. In spite of what you majored in, or what the textbooks say, or what you think you’re an expert at, </em><strong><em>follow a system wherever it leads</em></strong><em>.</em>” — <a href="https://thesystemsthinker.com/dancing-with-systems/">Donella H. Meadows</a></blockquote><p>When browsing my books, I came across my copy of “A Pattern Language” by Christopher Alexander, Sara Ishikawa and Murray Silverstein, as well as a short german summary of Alexander’s complete work on patterns and of his ideas in “The Nature of Order”— and it struck me that there seems to be an obvious connection between Alexanders work and “Thinking in Systems” by Donella H. Meadows (and <a href="https://medium.com/@johannrichard/on-being-a-systems-dancer-af53c6105cbb">the dance with systems </a>that she so beautifully elicits).</p><p>And at the same time, it struck me how little I find of either one’s thinking in the two main fields I am usually working in — <a href="https://www.sciencedirect.com/science/article/pii/S0166497218303870">innovation ecosystems</a> and <a href="https://medium.com/iipp-blog/good-bureaucracy-max-weber-on-the-100th-anniversary-of-his-death-c3dc6846d6be">bureaucracies</a>.</p><p>I have yet to come across literature that either combines Alexander’s work with “Thinking in Systems”, let alone applies both of them to the architecting of (innovation) ecosystems or bureaucracies. And yet I think there’s something about bringing these together. Let me explain why.</p><h3>“The Nature of Order”: fundamental properties for architecting systems</h3><p>While “A Pattern Language” has its focus on over 200 patterns used to architect towns, buildings and to be applied to construction in general, Alexander’s work, especially the four-volume “The Nature of Order”, also goes into great lengths to outline general principles of “architecting systems”. Most prominently, this has been through his recent work on 15 fundamental properties of Wholeness (or good architecture) (See for example [1],[2] and [3] for a few introductions).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/719/1*T4CHMlzt9eO3okHSqke5Zw.png" /><figcaption>15 fundamental properties (The Nature of Order, Christopher Alexander)</figcaption></figure><p>Alexander’s approach to “architecting” (as a general discipline) but also the 15 principles can be applied in a much broader sense than just “Towns, Buildings and Construction”, and I am by far not the first one to make this observation.</p><p>But what I have not yet seen so far is “A Pattern Language” or the fundamental principles appear in the literature about innovation ecosystems, nor on bureaucracies and their reforms.</p><blockquote>“Why are the 15 fundamental properties not applied to the design of innovation ecosystems or reforms of bureaucracies?”</blockquote><p>I wonder why: If you look at the 15 fundamental properties in the context of <a href="https://www.sciencedirect.com/science/article/pii/S0166497218303870">innovation ecosystems</a> or bureaucracies (which in itself are also very fascinating systems), you might instantly see how these properties could be applied to the design of either one and probably with a lot of added value.</p><p>So let’s first have a short look at the list of 15 properties:</p><ol><li>Levels of scale.</li><li>Strong centres.</li><li>Boundaries.</li><li>Alternating repetition.</li><li>Positive space.</li><li>Good shape.</li><li>Local symmetries.</li><li>Deep interlock and ambiguity.</li><li>Contrast.</li><li>Gradients.</li><li>Roughness.</li><li>Echoes.</li><li>The Void.</li><li>Simplicity and Inner Calm.</li><li>Not-separateness.</li></ol><p>Of course, “wholeness” or “gradients” or “local symmetries” are not the language of bureaucrats, nor do they necessarily “ring a bell” with the language of innovation people who are more likely to talk about business impact, the economy and investments, or technology, impact and strategy.</p><p>But yet: there is a quality to the language of these fundamental properties that rings a bell with me. And as <a href="https://medium.com/@johannrichard/on-being-a-systems-dancer-af53c6105cbb">I recently summarised</a>: “<em>Language eats strategy, structure, and culture for breakfast</em>”.</p><p>Let me illustrate this. On “Gradients”, <a href="https://patterns.architexturez.net/doc/az-cf-172521">Salingaros</a>, in his “Unified Architectural Theory”[1] <a href="https://patterns.architexturez.net/doc/az-cf-172521">writes</a> :</p><blockquote>“<strong>Gradients represent controlled transitions</strong>. They provide a method of getting away from uniformity, because that is a non-adaptive state.”</blockquote><p>Although a spatial principle, it can easily be applied to the design of a programme aimed at transforming an ecosystem, for example by deliberately applying the idea of a “funding gradient” to a programme, or by designing “interaction gradients” into the governance of the various elements of an ecosystem. And by doing so, our system will gain in resilience, will become more adaptive and less uniform.</p><p>The same goes for “Levels of scale” or “Echoes.” And we have not even thought about how “Deep interlock and ambiguity” could lead to stronger, more resilient ecosystems if “built-in” from the outset. Again Salingaros:</p><blockquote><strong>“Deep interlock and ambiguity are other strong ways of connecting</strong>. Forms interpenetrate to link together.[…] Two regions can interpenetrate […] which enables a transition from one region to another.”</blockquote><p>Applied to policies governing such an innovation ecosystem, or a bureaucracy, this could mean to deliberately create a certain ambiguity and deep interlocks with goals and objectives, or structures— and thus naturally force the actors of these systems to go beyond their siloes, reach out into the ambiguity and the interlock, creating stronger connections in the process.</p><blockquote>“Maybe <strong>deep interlock and ambiguity applied to bureaucracies and their was of working could create strong connections between siloes?</strong>”</blockquote><p>One could argue — and maybe even rightly so — that sound design of bureaucracies or innovation ecosystems will also take care of siloes, of uniformity or agility. But is it really possible, and at what price? Resilience can not be prescribed — nor can we impose our will upon a bureaucracy of silos without forcing our will upon the humans inside these siloes. But we can work with, and transform systems in ways that offer more opportunities for resilience building or cross-silo collaboration.</p><p>Says <a href="https://thesystemsthinker.com/dancing-with-systems/">Donella H. Meadows</a>:</p><blockquote>“We can listen to what the system tells us, and discover how its properties and our values can work together to bring forth something much better than could ever be produced by our will alone. […] <br>We can’t control systems or figure them out. But we can dance with them”</blockquote><h3>Dancing in patterns — dancing with systems?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5B-4UPn9UgkAGDZkI0ddjQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@aoddeh?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ahmad Odeh</a> on <a href="https://unsplash.com/s/photos/dancing?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Although Christopher Alexander would not necessarily approve of this, I think that the 15 fundamental properties in itself are kind of a high-level pattern language — one that can be applied when we “dance with systems”.</p><blockquote>Alexander’s 15 fundamental properties are a high-level pattern language that we can apply when ‘dancing with systems.’</blockquote><p>And this is where I think we can bring the three worlds together. In an <a href="https://medium.com/iipp-blog/what-makes-states-entrepreneurial-7dd397d1fc70">older article</a> on the entrepreneurial state, <a href="https://medium.com/u/d132d950256a">Rainer Kattel</a> once wrote:</p><blockquote>As weird as it may sound, successful governments — entrepreneurial states — manage precisely that: they are able to create space for agility (taking risks and experimenting, responding to new challenges) and providing stability (minimising long-term risks and uncertainty).</blockquote><p>and</p><blockquote><strong>Capacity</strong> for innovation in bureaucracy is about having the space — skills, <strong>networks</strong>, organisations — for both <strong>agility</strong> and <strong>stability</strong>.</blockquote><p>This is “systems language” in its fullest.</p><p>Here’s a thought: what happens if we start to apply Alexander’s fundamental properties as <em>patterns </em>when we design and transformation innovation ecosystems or bureaucracies? Could it help us in designing better versions of these systems, versions that are more resilient, systems that have a higher carrying capacity or more diversity?</p><p>At least for me, this is a very intriguing thought.</p><h4>References</h4><p>[1]: “<a href="https://patterns.architexturez.net/doc/az-cf-172521"><em>ch. 11 (19). Christopher Alexander’s 15 Fundamental Properties</em></a>.” In <em>Unified Architectural Theory: Form, Language, Complexity — a Companion to Christopher Alexander’s “The Phenomenon of Life: the Nature of Order, Book 1”</em>, 125–130. Portland, Oregon and Kathmandu, Nepal: Sustasis Foundation and Vajra Books, 2013.</p><p>[2]: The Fifteen Properties Are the Glue which Binds Wholeness Together<strong>, </strong><a href="http://www.livingneighborhoods.org/ht-0/fifteen.htm">http://www.livingneighborhoods.org/ht-0/fifteen.htm</a> (Accessed 12 July 2020)</p><p>[3]: The 15 Properties of Pattern Language, <a href="http://www.inverde.net/patterns.html">http://www.inverde.net/patterns.html</a> (Accessed 12 July 2020)</p><p><em>Edited for clarity and augmented with some additional material.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4da01b587238" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On being a systems dancer]]></title>
            <link>https://medium.com/@johannrichard/on-being-a-systems-dancer-af53c6105cbb?source=rss-1ec4d4028acb------2</link>
            <guid isPermaLink="false">https://medium.com/p/af53c6105cbb</guid>
            <category><![CDATA[personal-knowledge-system]]></category>
            <category><![CDATA[pkm]]></category>
            <category><![CDATA[personal-knowledge]]></category>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Johann Richard]]></dc:creator>
            <pubDate>Sun, 12 Jul 2020 12:53:21 GMT</pubDate>
            <atom:updated>2020-07-12T14:50:36.622Z</atom:updated>
            <content:encoded><![CDATA[<p>(Originally published <a href="https://mycvs.org/post/623360294435061760/on-being-a-systems-dancer">here</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fmTTha6CJbqfTEPLMbirjQ.jpeg" /><figcaption>“Thinking in Systems”, Donella H. Meadows</figcaption></figure><blockquote>“Language eats strategy, structure, and culture for breakfast.”</blockquote><p>Here’s a few of the take-aways from the last chapter of “Thinking in Systems” (Donella H. Meadows) (Which is largely equal to <a href="https://t.umblr.com/redirect?z=https%3A%2F%2Fthesystemsthinker.com%2Fdancing-with-systems%2F&amp;t=OTg1ZDM4MzBiNDc2N2IzYjJlMzAxM2VkYzI4YjZlMTc5NjEyZWU0MixKZ3VhUzJLYw%3D%3D&amp;b=t%3A4JGU03qeJMFCNGF-niefPA&amp;p=https%3A%2F%2Fmycvs.org%2Fpost%2F623360294435061760%2Fon-being-a-systems-dancer&amp;m=0">the linked article</a>):</p><ul><li>“We can’t control systems. But we can dance with them”, and so we could &amp; should aspire to become better “systems dancers”</li><li>Information is key, and should be honoured and treated with respect (and distributed generously) Language is more primordial than strategy, structure or culture — in other words: Language eats strategy, structure, and culture for breakfast.</li><li>Concepts (and thus the terms) like a system’s “carrying capacity”, its diversity and structure are often underestimated or not seen, especially in bureaucracies which do not tend to think of themselves as “systems” in the broader sense</li><li>Whatever we build: we should go to great lengths and take great care to include sound feedback policies into these systems, and add these from the beginning — this designs <em>learning</em> into the system</li><li>Resilience, stability, growth or sustainability (in its broadest sense) are more “systems” word to be used bountiful</li><li>Stay humble, stay foolish — and stay a lifelong learner full of curiosity</li><li>Celebrate complexity, welcome it and don’t shy away from it. In fact, once you accept complexity, the only option to deal with it is probably in fact by <em>dancing</em> with the underlying system. And the dance won’t be a well-timed, strict choreography and not even one of the standard dances with it’s toolbox of dancing steps, but more likely something like <em>improv</em> dance.</li></ul><p><a href="https://t.umblr.com/redirect?z=https%3A%2F%2Fthesystemsthinker.com%2Fdancing-with-systems%2F&amp;t=OTg1ZDM4MzBiNDc2N2IzYjJlMzAxM2VkYzI4YjZlMTc5NjEyZWU0MixKZ3VhUzJLYw%3D%3D&amp;b=t%3A4JGU03qeJMFCNGF-niefPA&amp;p=https%3A%2F%2Fmycvs.org%2Fpost%2F623360294435061760%2Fon-being-a-systems-dancer&amp;m=0">Dancing with Systems</a></p><p><em>This post is part of my #PKMastery journey</em></p><p>(Edit: Now with the Oxford comma.)</p><p><em>Originally published at </em><a href="https://mycvs.org/post/623360294435061760/on-being-a-systems-dancer"><em>https://mycvs.org</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af53c6105cbb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>