Appreciating Systems

Appreciating Systems for Genuine Efficiency
Home » Posts tagged 'complexity'

#Permaculture as a form of #governance: initial ideas

I’ve been circling (!) into governance ideas (Holacracy, Sociocracy and Sociocracy 3.0) and Permaculture, recently. My takes on these are:

  • Holacracy is well structured but quite complicated to implement
  • Sociocracy is way simpler but leaves initial practitioner with a blank page syndrom making them needing to reinvent most of their work
  • Sociocracy 3.0 is modulable but complex to start with

And then I pondered recently on permaculture and management, and then onto governance and sociocracy, and discovered that you could use permaculture for governance (with bits of consent and circles inside, and double-linking and elections without candidates being nice additions). I still haven’t had the time to detail my ideas, but it mostly goes like this:

  • planning could use the OBREDIM (observation, borders, resources, evaluation, design, implementation, maintenance) permaculture design approach to structure issues
  • the circles (and sub-circles) are thought along the line of permaculture zoning like below. This also goes for analyzing issues and ensuring they’re properly contributing to the organizational ecosystem they belong to:

    • 0 = you,
    • 1 = the circle
    • 2 = the community/organization
    • 3 = the wider environment/ecosystem/bioregion where the organization resides
    • 4 = the nation
    • 5 = the world/Earth
  • governance could benefit from the seven levels, with the following correspondance :
    1. canopy: strategy definition
    2. low trees: roadmaps, tactics, policies
    3. shrubs: operational stuff: projects and actions
    4. herbaceous: nutrients: what are the recurring resources that will feed the circle?
    5. rhizosphere (roots): digestion: how can learning be reinjected into the organizational culture?
    6. soil surface (ground cover): protection: how can we maintain and preserve our culture (all the while nourishing it)?
    7. vertical layer (vines): interconnections with other levels and circles
  • and synchronization meetings (triage in Holacracy) or action planning benefit from the 12 principles to ensure the actions contribute the most effectively to the organization (do you create no waste? do you tap into renewable energy from people (ie in their strengths, not aside from then, etc. See my other posts on that)

That’s mostly it! When decisions need to be taken, you resort to consent after having clarified the issue using OBREDIM at all relevant levels (plants don’t achieve consensus, their behaviors mostly resemble consent to me). Elections are without candidates (plants don’t propose themselves, they each interact and structural coupling make some stand up given the local conditions). Circles are double-linked because it increases the communication channel variety through which complexity can express itself (the complexity is at most that of the communication channel). And of course a circle is the local ecosystem around a specific topic.

That way of organizing stuff also embeds elements from Stafford Beer’s Viable System Model. But I’ll let that proof as an exercise for the reader ūüėČ

What the #ebola pandemic reveals (again) about the world systemic vulnerabilities – #systemsthinking #vsm #labso

Out of a discussion on LinkedIn, I wrote the following:

Regarding the Ebola pandemic, at first we,¬†the outsiders of Africa, didn’t notice, then we didn’t believe, then we didn’t invest, then we weren’t prepared, then we’re stuck by the huge implications of what might happen, then bounded rationality kicked in and we blinded ourselves to what ought to be done.

Sounds like a reinforcing loop (the epidemic archetype) running faster then the structural adaptation of the minds (cf. works of Maturana & Varela) getting progressively (though exponentially) involved in the system at play.

It seems to be our modern living habits (cheap international travels – flights, trains, cars), dense inhabiting zones, etc have created systems into which both information and viruses spread faster than the speed at which we can think, adapt and react.

This conclusion, for me, supports the idea that we need to change the way we address that high-speed complexity (high interconnectedness). More than ever, we don’t have the requisite variety¬†to tackle it, whether static or, now, dynamic.¬† More than ever we need skills in facilitation of big groups to achieve collective intelligence. This is what we’ve tried to do by creating the Labso, Laboratory of Social Technologies: showing people how easy it is to tap into the power of the crowd and social networks by uncovering what works and why and making more of it, if not co-creating something bigger.

I hereby also predicts that this won’t be enough in the near future, on two accounts:

  • connectivity will continue increase both in the number of connections and in the speed (because of technology)
  • AND because by going to mass facilitation, we’re just solving a short term problem and contributing to the acceleration as well.

My personal solution to the near future (or present situation for some problems) is to accelerate further by sticking close to the geographical area, trust it to handle the local situation properly, and only signal/ask for help “upwards” when the need arises.

Sounds like a global Viable System Model to me, don’t you think?

How I moved beyond #SystemsThinking methods…

This, I posted on the Systems Thinking World LinkedIn group:

I feel like I moved beyond ST methods (the one I cited in a previous blogpost). I was swallowed by Complexity and Ashby‘s law of requisite variety was the crack through which I came on the other side of the mirror.

What this means is: I recognize the complexity of the world and our (recent) capacity to acknowledge it. I recognize my own limitation to understand that complexity in a decent (short time) way: I simply acknowledged that I don’t have the requisite variety.

I also do recognize that people are structurally coupled to their own conditions and their own understanding of them, far better than I will ever be capable of.

So, my own ST way of approaching life is now to help people weave their own mental models with that of others (when they’re supposed to interact successfully) so they can co-build (ie, influence each other) a new one that work for both of them.

In any situation, the best strengths to use and the one of the people inside that very situation. So I help people weave themselves and make their co-intelligence emerge and address the situation.

The generic term for that is “strength-based approaches to change”, but, to me, it goes way beyond just identifying people skills and traits and using them…

A proposal for a new #Complexity- and #Strength- based #PDCA (for #Lean or else)

Thinking during commute the other day (should I have to live nearer my work, I’d be much more dumb!) I pondered how a better strength-based Plan Do Check Act loop could look like.

I find the current version of PDCA to be a bit too deficit-based and tainted of Command & Control. All too often we see managers or project managers deciding on a plan in their offices and rolling it over employees, without much consideration about what would work for them (they’re the ones with their two feet in the daily work, so they should know best). Sure, if you’re doing¬†nemawashi, this doesn’t concern you. But not everybody does it, yet.

So, since we’re speaking more and more about complexity (hmmm, Google Trends on complexity is making me a liar it seems – a construction of mine?)… anyway, I came up with the following new version:

  • Connect ideas of different people: who are they? what are their strengths? What ideas do they have? Aspirations? Opportunities they see? Results they expect?
  • Select ideas that you (collectively) would think are the more interesting to try?
  • Effect these ideas: go to the gemba and put them to the test of work. Measure heavily what happens of course (People side: does it enhance the work experience? Quality? Delays? Costs?)
  • Reflect on what happened: what did you learn? What new opportunities do you now see? What hopes does this give you? What else?

PS: well, at least the¬†Cynefin ¬†framework is trending more ūüėČ

#Lean management & #Complexity: what does it mean and why it works

Cynefin framework

Cynefin framework

Simple times

In the good ol’ days of manufacturing (or service industry), the world was seen as rather simple: you had clients that wanted widgets that you built. For different needs you built different widgets. That’s the simple¬†domain of the Cynefin framework as pictured on the right: you Sensed¬†what the client wanted, you Categorized¬†his need and then Responded to it.

Craft industry was at best for this kind of environment. Few thinking was necessary at that time in order to best serve clients.

Complicated times

Then, progress made clients wanting more (in quality and in diversity). In that realm of Complicated¬†environment, the clients’ requests had to be Sensed, then Analyzed¬†before being Responded¬†to.

In an effort to optimize costs, it’s been decided that making “lots of brainpower” was the way to go and that was the gold days of¬†Taylor: some people were paid to think while others were paid to build the widgets. The best way to build was being thought by brains dedicated to that purpose.

See how thinking is included in the Cynefin framework through the “Analyze” step? Brain power was necessary to efficiently design the methods of work, yet, having it all in one place was enough (in Lean, we would say that there were batches of brainpower, instead of an on-demand usage of brainpower…)

Today: complex times

Today, with such variety in the wild, the world has become Complex¬†because clients can easily connect to a world of other opportunities and their needs reflect that complexity of the world (indeed, they’re trying to match their environment variety to survive, just like our companies). From a Systems Thinking point of view, it means that each client contact is different and there’s so much variation in it that one brain power only cannot feature the requisite variety to properly serve the client. To survive in a Complex world, one has to probe¬†the client’s environment to be able to¬†Sense¬†what’s really needed and only then Respond¬†to the (hopefully correctly understood) need.

One can see here that the thinking¬†has disappeared of the framework, being replaced by a probe and a sense (isn’t it what genchi genbutsu¬†is all about?). That’s where Lean came as a force because:

  • the client needs are really taken seriously, further than just analysis, by being probed and sensed by going to the client’s gemba.
  • to respond to that richly “analysis” of the client needs, the organization needs to be able to quickly respond to it, and that means to be able to quickly adapt to the requisite variety of the client’s environment.

How to you achieve that fast-moving organization? By removing all that is either unnecessary or hindering it from performing as requested by the variety of the client demands. In Lean terms, we speak of removing muda from processes.

Connecting also to Complexity principles, it means making the organization more of an opened system (Lean talks of “extended company”) than a closed one. Closed systems fail prey of the 2nd law of thermodynamics which postulates an increase of entropy, which means more disorder hence less efficiency.

A corollary to the preceding is also that if one wants to maintain order (or even further organize / increase efficiency) and to adapt to the client’s requisite variety, one needs to bring energy to the system, thus reducing entropy.

Continuous improvement doesn’t occur by chance, one has to constantly dedicate resources to it. In a finite world of resources, that means deciding upon which resources are allocated to “work as usual” and resources allocated to improvement (fight against entropy to keep it low).

Biology of Business : a Farrow Partnership presentation (#complexity #systhnk)

I found that slideware on the field of complexity adapted to business and what it means in terms of things to stop doing and things to start doing. Ideas are said to come from Complex Adaptive Systems which I yet have to investigate in detail.

Indeed, there are 11 new things one should start doing to be more efficient:

  1. Pursue agility and resilience
  2. Consciously learn from daily experience
  3. Allow solutions to emerge
  4. Pull, don’t push
  5. Seek healthy mixtures
  6. Rely on vision and boundaries
  7. Appreciate the messy phases
  8. Expect non-linear progress
  9. Cooperate to create abundance
  10. Promote grassroots initiatives
  11. Work in a place designed for humans

Reading this list, I see that I must have been deeply impressed by all of complexity and systems thinking readings since that’s what I’m tending to do these days. My natural inclination toward these have been reinforced by the justifications I’ve found in my readings.

Lean seeks to achieve perfect agility and resilience, with learning and nurture solutions from people. Do I need to talk about pull/push ? Appreciative Inquiry deals with mix of people and points of views, helps build a strong Vision and strive to messy moments (brainstorming, exchanges…)

The complete slide show along with details for each of the 11 steps is available here.

Mail List

Join the mailing list

Check your email and confirm the subscription