I’ll be in Australia in February, as Chief Exec of the Public Service Transformation Academy (www.publicservicetransformation.org), speaking at the launch events for the new Australasian Transformation Academy – public service reimagined (powered by PPB Advisory), at breakfast sessions 20 February in Sydney and 21 February in Melbourne.
I’m taking the opportunity to help great folk over there – principally Robert Lamb in Melbourne (the instigator!) and Stefan Norrvall in Sydney – with our shared ambition to launch Australian chapters of SCiO (www.scio.org.uk – the systems practitioners’ network). These events take place in Sydney on 19 February (evening – thanks to the Leading in Complex Adaptive Systems Meetup Group) and in Melbourne on 21 February (pm – thanks to Club Blac and probably evening – thanks to the Agility Collective).
If you’re interested in attending, or would just like to grab a coffee or a chat about these or related subjects (I’m also talking about RedQuadrant’s ground-breaking Leading Transformation blended learning), just give me a shout – benjamin.taylor@redquadrant.com
And if you’d like to refer someone who would be interested, just let me know!
links below – a bit about me first by way of introduction – this is a one-off
Way, way back on 27/7/2014, I got an invitation to join a site with the unprepossessing name of model.report. The brainchild of Scott Fortmann-Roe (http://scott.fortmann-roe.com) and Gene Bellinger (https://www.linkedin.com/in/systemswiki/ and all over the place), the site was a simple discussion and link sharing forum which owed something to Stack Exchange, based on the Lobsters platform.
‘Great!’ I thought – a place to build a repository of the whole of systems thinking. I’ll start with what I know (my first post was an open day for www.scio.org.uk, and I did Beer’s Viable Systems Model and Barry Oshry’s power+systems approach in short order), and go on from there. I set myself a nice aspirational target of getting 100 ‘upvotes’ in the first six months. Model.report began with much active discussion and settled down over the years to about twelve active contributors, pretty much following the 1% rule (https://en.wikipedia.org/wiki/1%25_rule_(Internet_culture)).
A few things happened over the years:
somehow, I stayed /hyper/active – partly because there’s just quite a lot of systems thinking out there, and partly because, every time I thought I had got a rough sketch of the known universe in hand, I turned a corner… and there was a whole unexplored galaxy! And my jobs relates at least more than a bit, so I can kid myself I’m doing something really valuable 🙂
it turned out there was an active – and much larger – community of readers. And some of them were really appreciative and nice, and doing great things in the world
Gene, as is his wont, decided it wasn’t working for him and left (in the process deleting all his posts and comments – sad)
And, eventually, Scott (now doing great things with Google), realised he couldn’t commit to maintaining the site.
So, we moved over here – thanks to David Ing’s kind offices – to an open-licence, wordpress-based site, which is now a kind of partnership effort between me and him, thanks to going splitsies on a miniscule annual server fee (he’s the technical expert, I’m certainly not). But, while the originally will, slowly or abruptly, fork itself, degrade, and fall out of graveyard orbit, a full archive of model.report (all content available, functions mostly not) is preserved ‘forever’ at https://syscoi.com/model.report/model.report/newest.html
I resolved to continue collecting systems thinking links, events, an’ ting – how could I not? – but also to experiment with not posting *every single* link as a new item.
So, and so. Here is a MEGA, rather overstuffed, link digest for January 2018 (and some time before). It leans quite a bit on the wonderful Rachel Sinha’s wonderful Systems Studio newsletter (http://rachelsinha.com/ and http://thesystemstudio.com/), which you can broadly see because their link tagging is in many of the links clipped from there.
Rest of content, model’s own – I source from google alerts, nuzzel.com, twitter, the LinkedIn systems thinking network (30,000+ members – https://www.linkedin.com/groups/2639211), the systems thinking facebook groups at https://www.facebook.com/groups/774241602654986 (4,500+ members) and https://www.facebook.com/groups/2391509563 (2,000+ members), and also quite often from podcasts https://docs.google.com/document/d/1vRh25RO40r8LK4psqqGWfMAJOAFh5nyc3-UOx34-8GQ/edit and other newsletters. Basically, I’m Johnny Five 🙂
Ooh, and Rachel allowed me to do this very self-flattering blog about ‘me and systems thinking’:
http://thesystemstudio.com/new-blog/2017/7/26/interview-systems-change-network-builders-ctpjw
I can see several advantages of this ‘compendium’ format: one email not a spam email with every post (as was before), more to chew on, easier to scan and see what you like. And several disadvantages: no automatic fetching of canonical links, no automatic identification of duplicates (which will be many), no automatic grabbing of page headlines (so more work to edit), and much harder to start a discussion on an individual link (I suggest that, if something piques, your interest, you start a discussion in a separate posting here). And, definitely, this one is too long. I can’t promise what I’ll do in future but I do welcome feedback, and will definitely aim for shorter compendia and, where time allows, a little more structure/commentary.
Cheers
Benjamin
about me:
www.bentaylor.com
SCiO – non-exec director – www.scio.org.uk
RedQuadrant – network consultancy UK, Aus and NZ public sector – www.redquadrant.com
Quadrant Resourcing – excellent interim change people – www.quadrantresourcing.com
The Public Service Transformation Academy – Chief Executive – www.publicservicetransformation.org
Other online stuff I am involved in: https://docs.google.com/document/d/19ji4L38JVVJiWj9EiSglY–q_rn_fr6a7G4MjnuDYK0
I tweet at www.twitter.com/antlerboy
Sign up for our newsletter www.redquadrant.com/newsletter
Please connect to me at www.linkedin.com/in/antlerboy
Tools for Systems Thinkers: 7 Steps to Move from Insights to Interventions – Medium View at Medium.com
Chaire Edgar Morin de la Complexité – key links:
https://sites.google.com/a/essec.edu/chaire-complexite/recherche-enseignement
https://sites.google.com/a/essec.edu/chaire-complexite/activites
https://sites.google.com/a/essec.edu/chaire-complexite/contacts
https://sites.google.com/a/essec.edu/chaire-complexite/home
Audio file of Churchman at 1975 conference: https://soundcloud.com/portland-state-library/pdx-lsta-hs-1547-access
“Cognition as computing a reality” – a few notes from this Heinz von Forster talk:
Using systems thinking to return city streets to the community – Arab News
http://www.arabnews.com/node/1226591/corporate-news
Systems Thinking for Safety [HUM-SYS]
http://trainingzone.eurocontrol.int/ilp/pages/coursedescription.jsf%3Bilp_JSESSIONID=EC62BF173F3D7B8DD3696F1771186257?courseId=5083310
Systems thinking is the Defining Feature of Sustainable Design
http://newdeal.blog/systems-thinking-is-the-defining-feature-of-sustainable-design-68bb7ccf8772
Continuous Improvement as seen through the lens of Systems Thinking – Bram.us
Systems thinking: Why it is important
http://www.ejinsight.com/20180119-systems-thinking-why-it-is-important/
Toronto Museum Educators For Climate Justice Workshop – How We Learned to Stop Worrying and Love Systems Thinking
http://coalitionofmuseumsforclimatejustice.wordpress.com/2018/01/24/toronto-museum-educators-for-climate-justice-workshop-how-we-learned-to-stop-worrying-and-love-systems-thinking/
From systems building to systems thinking – McGee’s Musings
Seeing and Sensing Wholeness in Nature and Organisations https://transitionconsciousness.wordpress.com/2018/01/28/seeing-and-sensing-wholeness-in-nature-and-organisations/
Systems Thinking, Critical Realism and Philosophy
https://newbooksnetwork.com/john-mingers-systems-thinking-critical-realism-and-philosophy-a-confluence-of-ideas-routledge-2014/
From an isolated laboratory to a world where “context is everything”
https://www.linkedin.com/pulse/from-isolated-laboratory-world-where-context-marco-valente/
Advances in Cybernetics Provide a Foundation for the Future
Making Systems Thinking More Than a Slogan
https://nbs.net/p/making-systems-thinking-more-than-a-slogan-ad50eb4b-7a55-48c9-bb10-4e71d69b38ff
The challenge of systems leadership
https://blog.kumu.io/the-challenge-of-systems-leadership-d98cc9b9a114
Why embrace complexity to create systemic change?
http://mailchi.mp/ccba5675d1db/2018-complex-system-leadership-program-expression-of-interest-now-open-377969
The NCP Fantasy Systems Thinking Team – Forrester and Meadows
https://newcommunityparadigms.blogspot.co.uk/2018/01/the-ncp-fantasy-systems-thinking-team.html
Learning how to understand complexity and deal with sustainability challenges – A framework for a comprehensive approach and its application in university education
Autopsy of a Failed Holacracy: Lessons in Justice, Equity, and Self-Management
https://nonprofitquarterly.org/2018/01/09/autopsy-failed-holacracy-lessons-justice-equity-self-management/
She Ji: The Journal of Design, Economics and Innovation
https://www.sciencedirect.com/journal/she-ji-the-journal-of-design-economics-and-innovation/vol/3/issue/3
Capitalizing on Paradox: The Role of Language in Transforming Organizational Identities
https://pubsonline.informs.org/doi/pdf/10.1287/orsc.13.6.653.502
Langton’s ant
https://en.wikipedia.org/wiki/Langton%27s_ant
Bouricius, Terry and Schecter, David. (2013). An Idealized Design for the Legislative Branch of government. Systems Thinking World Journal: Reflection in Action. [Online Journal]. 2(1). [Referred 2013-01-22]. Available: http://stwj.systemswiki.org . ISSN-L 2242-8577 ISSN 2242-8577
Bouricius, Terry and Schecter, David. (2014). An Idealized Design for Government. Part 2: Executive Branch Accountability. Systems Thinking World Journal: Reflection in Action. [Online Journal]. 2. [Referred 2014-11-5]. Available: http://stwj.systemswiki.org . ISSN-L 2242-8577 ISSN 2242-8577
Read the story of SiG ( Social Innovation Generation) in Canada in this new book:
https://www.thesigstory.ca/?ct=t(The_Systems_Studio_Newsletter_7_11_2017)
useful resources on systems practice, shared by Lorna Prescott, curator of CoLab Dudley: View at Medium.com
a useful video describing system change using love as an example:
a blog from Jen Morgan on aging and system change:
an article on the challenges of integrating startups into parent organizations.
https://www.linkedin.com/pulse/beyond-innovation-labs-integrating-startups-parent-eric-ries/?ct=t(The_Systems_Studio_Newsletter_7_11_2017)
MaFi, the community for systems changers working in international development, announce a shift to focus on the art of facilitation:
an insightful overview of systems change in 2017 from Otto Scharmer, including Big Tech Turned Evil:
https://www.huffingtonpost.com/entry/2018-moving-beyond-trumprebuilding-our-civilizations_us_5a480ba1e4b0d86c803c7735?ncid=engmodushpmg00000003&ct=t(The_Systems_Studio_Newsletter_7_11_2017)
some useful Maps of Frameworks on the field of system change:
systems failure and the four reasons Philanthropy keeps losing the battle against equality:
https://www.insidephilanthropy.com/home/2018/1/10/systemic-failure-four-reasons-philanthropy-keeps-losing-the-battle-against-inequality?ct=t(The_Systems_Studio_Newsletter_7_11_2017)
Six steps to circular systems design from Leyla Acaroglu: https://medium.com/disruptive-design/six-steps-to-circular-systems-design-1b0c8ae9f60e?ct=t(The_Systems_Studio_Newsletter_7_11_2017)
useful resources on teachers trying to build systems thinking into their syllabus systems literacy: https://ca.pbslearningmedia.org/collection/systemsliteracy/?ct=t(The_Systems_Studio_Newsletter_7_11_2017)#.WnHq4Khl_IW
a report from Newcastle University and Collaborate a whole new world funding and commissioning in complexity: https://collaboratecic.com/a-whole-new-world-funding-and-commissioning-in-complexity-12b6bdc2abd8?ct=t(The_Systems_Studio_Newsletter_7_11_2017)&gi=709be6a9f011
Toolkit from Ashoka on forming innovative alliances: https://www.ashokachangemakeralliances.org/toolkit?ct=t(The_Systems_Studio_Newsletter_7_11_2017)
Interesting article delving into what role you were born to play in social media change:
https://www.opendemocracy.net/transformation/george-lakey/what-role-were-you-born-to-play-in-social-change?ct=t(The_Systems_Studio_Newsletter_7_11_2017)
Events/training
Read all about the launch of Rachel Sinha’s new program for system entrepreneurs https://medium.com/@RachelmSinha/launching-a-new-program-for-system-entrepreneurs-who-are-halfway-through-7d6e5c534689?ct=t(The_Systems_Studio_Newsletter_7_11_2017)
Capra Course Masterclass: How to Engage Organisations with Systems Thinking
http://transitionconsciousness.wordpress.com/2018/01/21/capra-course-masterclass-how-to-engage-organisations-with-systems-thinking/
The brilliant school of system change kicks off on February 20 in New York City and later on the West Coast – Applications are open now. https://www.forumforthefuture.org/school-system-change-basecamp-2?ct=t(The_Systems_Studio_Newsletter_7_11_2017)
Online courses – self-taught and instructor-led https://strategydynamics.com/courses/
Training on the Art of Participatory leadership in Athens – apply by February 15: https://mailchi.mp/108598068856/art-of-hosting-athens-training-23-25-february-374387?e=69430fe607&ct=t(The_Systems_Studio_Newsletter_7_11_2017)
Marketing Systems Symposium 2018 is taking place from April 24 – 26 in Cape Town, South Africa:
https://www.marketsystemssymposium.org/?ct=t(The_Systems_Studio_Newsletter_7_11_2017)
CDRA is organizing a training on how to design and facilitate Writeshops in Johannesburg:
http://www.cdra.org.za/facilitating-writeshops.html?ct=t(The_Systems_Studio_Newsletter_7_11_2017)
If you have read Adam Kahane’s newest book collaborating with the enemy join this free online webinar on March 28th and ask Adam everything you want to know on the link below:
https://zoom.us/webinar/register/WN_ieLsULV0S9GD5V0kRkKXcQ?ct=t(The_Systems_Studio_Newsletter_7_11_2017)
Skoll Centre at Oxford launch a competition to encourage University/College students to think systematically about social problems through map the system:
http://mapthesystem.sbs.ox.ac.uk/?ct=t(The_Systems_Studio_Newsletter_7_11_2017)
Calls for papers
Call for Papers – Reconceiving Cognition – Antwerp June 27-29
Deepening the systems thinking in pattern language calls for a multiparadigm approach.
What if a pattern language was opened up to contemporaneous research into wicked problems, the systems approach, ecological epistemology, hierarchy theory, and interactive value? This 30-minute presentation at Purplsoc 2017 last October aimed to provide a broader context to a social change community focused on works of Christopher Alexander.
The content from syscoi.com/stream from December 2017 has been moved to stream.syscoi.com. The syscoi.com/stream experiment will gradually be quiesced.
Benjamin P. Taylor ( @antlerboy ) has moved over to model.report (based on the lobste.rs platform) at the end of 2015, after the community on LinkedIn was threatened with a shutdown. The model.report site accumulated a community. In early January 2018, the technical administrator for model.report told Benjamin that he would be unable to continue to support the community, and would help them to move elsewhere.
In addition, the community has accepted my invitation move over to syscoi.com. In doing so, I suggested to Benjamin that the partnership should move over onto a fully-supported WordPress.com infrastructure, so all of the feature of the O2 project (e.g. @reply) would become available. Migrating the content from syscoi.com/stream to stream.syscoi.com has been relatively easy, although registration processes and menus are changing a bit.
So, everyone who registered on syscoi.com/stream should soon be receiving an invitation to become an author on stream.syscoi.com. If anyone happens across this message, and wants to join the community over at stream.syscoi.com , it will be a two-step process. First become a follower, and then request the permission to become an author. We are taking this precaution in an effort to reduce potential spam, as SysCoI has always been designed as a platform where e-mail subscription is a good option.
Thanks to everyone who contributed to the syscoi.com/stream experiment! Welcome to stream.syscoi.com.
Here is the abridged writing by James Martin, dated Dec. 29, 2017:
— begin paste —
Here is a bit of useful wisdom with respect to the question of “what is systems science?” Gerald has given me permission to post this on our Sys Sci discussion list. He was responding to the proposal from Gary Smith to conduct a workshop at the IFSR Conversation in April to address this question
Here are his key points. His full message is enclosed at the end of this email.
First, don’t ever be under the illusion that you can break systems science down into its constituent components, agree on them all, and therefore gain agreement on the whole. That’s approaching systems science through reductionist analysis, and it won’t work.
Second, … do not expect that achieving consensus in a small group will generalise to a wider community without (a) a strong message of utility and (b) co-ordinated and strategic action to connect to what matters to other people.
Third, and linked to the above, be aware that ideas gain currency, not because they are truthful and beautiful in themselves, but because of their utility (the value of the inferences that can be made from them).
Fourth, and this is probably the hardest thing of all for Systems Scientists to hear – it means that the Systems Science that is of relevance to Systems Engineering might be different from the Systems Science of relevance to systems biology, politics and family therapy.
A foundational idea in Systems Science is that we can define some generic theory that is relevant across the board.
I still do think that this is the case, in the sense that there are some concepts (like how parts combine in systems to create emergent properties from the perspectives of observer-participants) that can be defined independently from the receiving discipline.
However, these relatively abstract conceptualizations, because they are not communicated in the context that the receiving discipline understands, may appear to the engineer to involve too much work for too little value.
Fifth, … the interactions with the problems of Systems Engineering will change the theory.
It may be that Systems Science explains some things, but not others, so there is a need for integration with other theory;
or it could even be that the particularities of Systems Engineering contexts lead people to conclude that an evolution of systems theory is needed in a new direction.
Systems Engineers can learn a lot from both the science of whole systems (Systems Science) AND thinking through the use of systems concepts that have been abstracted from their original theoretical context (Systems Thinking).
Best Regards, James
— end paste —
Here is the original e-mail from Gerald Midgely addressed to Gary Smith, dated Nov. 20, 2017.
— begin paste —
Hi Gary, Jennifer et al,
Thanks for looping me into this conversation. I know this is a long email, but I really hope it is a helpful one that can prevent the group going down some blind alleys. Below are some suggestions, purely based on my own understanding and experience, having seen people aiming for and failing to achieve a consensual definition of systems science for as long as I have been in the systems community (my first ISSS conference was 1989).
First, don’t ever be under the illusion that you can break systems science down into its constituent components, agree on them all, and therefore gain agreement on the whole. That’s approaching systems science through reductionist analysis, and it won’t work. Jennifer Wilby will remember a workshop at an ISSS conference back in the early 90s where people sought to define common terms. They started with ‘hierarchy’, because they thought it would be the easiest, and 3 hours later they abandoned the attempt, as there were so many different perspectives. The exercise didn’t even get past the first concept because the part (in this case hierarchy) was connected in so many ways to different systems philosophies, and the meaning was subtly different in each case.
Second, and this is really important in the context of a group pursuit exercise such as the one you are planning, do not expect that achieving consensus in a small group will generalise to a wider community without (a) a strong message of utility and (b) co-ordinated and strategic action to connect to what matters to other people. The systems community (along with every other scientific community) is full of groups suffering from “the tragedy of enlightenment” – saying, “we have done so much work to get this far, so why won’t anyone listen to us?” There is a neat little idea called Relevance Theory from the discipline of linguistics that explains why. Relevance to others is a function of the value of the inferences that those others can make from the new idea (i.e., its utility) minus the amount of work it takes to integrate that idea into their conceptual framework. Therefore, ideas may fail to disseminate because they generate a “so what?” reaction (which can be because they really don’t offer much added value to others, even though they do to you, or because they do not connect sufficiently with the worldviews of those you want to influence). They may also fail because they are too complex, and if it means internalising 50 new concepts, and understanding the contributions of 100 researchers over 70 years, people will see the mountain of work as enormous and will not yet have experienced the value of it, so will be dismissive. I used to get really angry when the Systems wheel got reinvented every generation or so (see, for instance, how complexity theory and systems biology failed to acknowledge their roots in GST), but now I realize that insistence on acknowledging the history of ideas actually prevents access to them. That’s hard for us to hear, but remember we are the affictionados who already see the value, so for us the work is worth it – others haven’t got to that point.
Third, and linked to the above, be aware that ideas gain currency, not because they are truthful and beautiful in themselves, but because of their utility (the value of the inferences that can be made from them). Therefore, for your project, the connection with Systems Engineering is actually more important than Systems Science itself! Again, for systems scientists this might be hard to hear – our tendency is first to work out what Systems Science is, and then to look at how Systems Engineers can gain inferences from it. However, the huge risk of doing this is the construction of a fine-tuned and intricately self-referencing and self-reinforcing set of concepts (Systems Science) that obstructs take-up in three ways: (1) it offers inferences that are relevant to systems theorists in domains other than engineering, and neglects the inferences that will be of value for Systems Engineers; (2) it does not dovetail with the language of Systems Engineers, so the value is not immediately obvious, and (3) it takes too much work to learn the subtlety. If it does any of these things, it risks failure.
Fourth, and this is probably the hardest thing of all for Systems Scientists to hear – it means that the Systems Science that is of relevance to Systems Engineering might be different from the Systems Science of relevance to systems biology, politics and family therapy. A foundational idea in Systems Science is that we can define some generic theory that is relevant across the board. I still do think that this is the case, in the sense that there are some concepts (like how parts combine in systems to create emergent properties from the perspectives of observer-participants) that can be defined independently from the receiving discipline. However, these relatively abstract conceptualizations, because they are not communicated in the context that the receiving discipline understands, may appear to the engineer to involve too much work for too little value. Again, the connection with the discipline matters more than Systems Science itself (how many times have you heard that the connections between the parts are as important, or even more so, than the parts themselves?), and the way Systems Science gets presented (the emphasis on some concepts rather than others, with particular examples) will be different from the Systems Science that gets presented to another audience, even if there are some common reference concepts.
Fifth, and this will also be hard to hear – the interactions with the problems of Systems Engineering will change the theory. It may be that Systems Science explains some things, but not others, so there is a need for integration with other theory; or it could even be that the particularities of Systems Engineering contexts lead people to conclude that an evolution of systems theory is needed in a new direction. If Systems Scientists then resist this, because it is a breach of the ideal of generality, then there will be a split in the research community, and the consensus you started out with will be broken. Here I am reminded of Kurt Richardson’s insightful complexity theory of language: as conceptual formations meet new contexts, bifurcations of meaning happen. This is why there is so much variety in systems theory in the first place. Disciplines narrow the contexts of meaning that their theory is designed to address, and therefore they can maintain more coherence and consensus than Systems Science, which self-consciously seeks to address ALL contexts. I actually did my PhD on this problem (1988 to 1992), and argued that we need a theory to EXPLAIN the pluralism (thus giving a different kind of coherence than a single systems theory), not a once-and-for-all theory to eliminate it. In this situation, we should expect diversity, not rebel against it and try to reduce it. The task of the Systems Scientist is therefore not to produce the best possible, fully worked-out systems theory, which will (of course) be relevant to systems scientists and nobody else! Rather, our task is to define the leanest possible theory, or set of concepts, which maximises value by being easily translatable into multiple, diverse contexts (such as Systems Engineering), while causing the people in those contexts very little work to internalise the concepts. This can be done with the Systems Engineering link (and other links) in mind, so the desire for purity is always countered by the need for communication with others.
Just one other thing I would like to add, which is not an outcome of the above reasoning, but also important. I think some clarity is needed about the difference and connections between Systems Science and Systems Thinking in this context. It seems to me that Systems Engineers can learn a lot from both the science of whole systems (Systems Science) AND thinking through the use of systems concepts that have been abstracted from their original theoretical context (Systems Thinking). If you are in any doubt about the difference, think about how ‘boundary’ is used in Systems Science as a reference to the edge of a real-world system (seen from the perspective of an observer, of course). However, when the boundary concept is moved into the domain of Systems Thinking, we can suddenly talk about boundaries defining what OUGHT to happen, etc. The concept has been abstracted from its original meaning and is deployed more widely. I am pointing this out, not to state the obvious, but to make it clear that defining Systems Science for use in Systems Engineering is only part of what the systems community can offer the engineering world. There are three risks here: (1) failing to notice Systems Thinking, and the Systems Engineering community getting confused between two competing claims of benefit (it is too much work for Engineers to sort this out, and both Systems Science and Systems Thinking will fail to deliver); (2) imperialistically presenting Systems Science as if it is both Systems Science and Systems Thinking, which will spark a paradigm war in our own research community; and (3) saying that Systems Science is right and Systems Thinking wrong, or a pale immitation, which risks both a paradigm war in our own community AND failure to deliver because we are expecting engineers to discriminate between competing claims! Please can we build clarity on the science/thinking distinction into our offering, without saying that either is less worthy than the other?
Thanks for listening, if I have not caused you too much work and you have read this far!
Best wishes, Gerald
— end paste —
These responses may not satisfy those looking for “simple answers”
Systems Community of Inquiry 