Category: Systems Thinking

  • Self-Preserving Geese and Humans

    Clarke Ching on the TOC Thinkers blog has republished an article by Tony Rizzo. Rizzo takes us through a beautiful explanation of how we adapt to the contexts we exist in, and how those adaptations can be seen in how we behave. Just like we can learn about the rules of flying by observing how geese fly in v-formations, Rizzo explains, we can learn about the rules of an organization by watching how people in it behave. It’s a nice analogy. We behave like we do for a reason, and that reason is not to be found only within ourselves, but in the systems we live in.

    I like to invoke systems thinker Russell Ackoff’s advice when it comes to observing behavior: whenever you observe something that seems remarkable, incomprehensible or just plain weird to you, ask yourself what would have to be true for that behavior to be useful to the person exhibiting it. That’s how you can start building understanding for the other person’s reality.

    Of course, the reasons you come up with are only your wild speculations, so to really do something useful, you need to go ahead and follow the advice of another systems thinker, Jerry Weinberg: you need to check it out. You need to go ahead and describe your observations and how you interpret them to the one you observed, and ask if you are correct. Why, well, many things can go wrong when observing, so let’s just say you need some error correction, just to be safe. Learn more about Virginia Satir’s interaction model for a way to observe your own observations and interactions.

  • Books That Have Influenced Me

    Henrik Mårtensson has published a list of business books that have influenced him. He also encouraged us readers to create our own lists. So here’s my list, in no particular order, not complete (I’ll add to it as I come to think of more books), and as of now without any motivation of why a particular book was included.

    * The Blind Men and the Elephant, David Schmaltz
    * Becoming a Technical Leader, Gerald Weinberg
    * The Fifth Discipline, Peter Senge
    * Secrets of Consulting (and More Secrets of Consulting), Gerald Weinberg
    * The Art of Problem Solving, Russell Ackoff
    * Agile Software Development with Scrum, Ken Schwaber
    * Are Your Lights on?, Gerald Weinberg and Don Gause
    * A Guide to Rational Living, Albert Ellis and Robert Harper
    * An Introduction to General Systems Thinking, Gerald Weinberg

    And a great article:

    * Resistance as a Resource, Dale Emery

  • Amplifying Your Effectiveness

    Last friday, I found myself sitting alone on the patio of the Embassy Suites hotel in northern Phoenix, looking out over an expansive pool area filling up with families most likely in town for the upcoming Nascar races.

    I, on the other hand, was just about to fly back home to Sweden, had no interest in race cars, and was feeling lonely for the first time in several days. No wonder, after having attended a five day conference that was actually mostly about me.

    Since it’s start in 2000, the Amplifying Your Effectiveness conference has attracted people interested in working with themselves to become more effective in and out of the workplace. Most participants seem to hail from the software industry, which is also the industry in which the conference’s ur-host, Jerry Weinberg, is known, frankly, as an icon. With more than thirty books (among the bestsellers: “Secrets of Consulting”), hundreds of articles published, and numerous well-known immersive workshops conducted, his reputation is well deserved.

    Not all participants work with testing, coding or managing software however. One runs a plumbing business, another is a painter. As for geographical origin, people have come from all over the U.S. There’s also a fair number of Canadians and a few Europeans, like yours truly.

    The varied backgrounds are important, because AYE is all about the people. Highly intelligent and very humble people, willing to meet, share, learn and have fun doing it, or letting it be emotionally challenging when that’s what’s needed.

    Driving home the point that the people should be in the center, the AYE is run as a guaranteed Powerpoint(TM)-free event. Guaranteed. You won’t see a single presentation slide for the duration of the conference. Given the prevalence of presentation slides in every other setting, one of AYE’s claims to fame could be that it may be the only way to avoid Powerpoint(TM) for almost a week.

    Instead of talking heads and bullet points, AYE has stories that stick and dialogue that engages. Instead of rows of chairs, AYE has circles. This lays the ground for something else that the conference has: the ability to forge new friendships. I arrived at the conference knowing not a single person. I left only after having hugged and shaken hands with a whole bunch of new acquaintances from all over the world.

    Making friends is also made easier by the fact that many participants go out dining together in the evenings. Phoenix is huge, so finding a place that serves food you like is not hard. If by finding you mean locating on Google Maps, that is. Driving to the actual place can be a different story altogether. We temporarily lost a whole car one night, but it contained a complete group, so no one should have had to eat alone.

    While very outspoken and easy going, most of the participants seemed to identify themselves as introverts on the Myers-Briggs scale. This is in accordance with what I learned in one of the sessions however – our preferences say little about how we will actually behave. On a related note, I can imagine that if you took almost anyone from this conference and put them in a Swedish setting, that person would surely stand out as the most outspoken in the group. It might be a cultural thing, but it’s probably a safety issue as well. Most participants seemed to consider it safe to speak their minds at AYE.

    I also managed to find the time to sit down and talk one on one with Jerry Weinberg for a while, which was rewarding. The only thing more extensive than his experience is his repository of stories, from which he frequently pulls one (often funny!) out to teach an important lesson.

    Content-wise, this years’ conference had three parallel tracks, and selecting a session was not always easy, since interesting topics often collided. A pleasant problem for me of course, but possibly frustrating for the hosts.

    Given that all hosts of the conference are students of Jerry Weinberg, who is himself a student of family therapist Virginia Satir and the topic of general systems thinking, it isn’t strange that a few core concepts pop up again and again throughout the conference.

    To give new participants an opportunity to catch up, a full day pre-conference tutorial run by hosts Don Gray and Steve Smith works through the basics of Satir’s teachings and also lets participants try on a kind of Myers-Briggs-based preference test. I came up as an ENTP, which surprised me, since I certainly don’t think of myself as extraverted. Whichever it is, it was certainly food for thought for me, and the source of an aha-feeling when I thought back on recent conflicts at work.

    In summary, the AYE conference was a fabulously useful experience for me, but make no mistake: it might not be for you. Because the conference is highly experiential, some exercises may touch on things you did not expect. At more than one occasion, emotions ran high. Thankfully, the hosts have a very responsible philosophy (“leave no bodies behind”). Things that bubble up in exercises are taken care of in an appropriate manner. Also, one of the first tips given during Sunday’s tutorial was to take care of yourself, which could mean to opt out from exercises or just get up and get some water when needed. All in all very comforting things to know about a conference that managed to aim my searchlights back onto how I myself can be the best tool for improving my own effectiveness.

  • Code as Design

    When I first read it a number of years ago, I immediately found Jack Reeves’ article “What Is Software Design?” useful, intelligent and correct.

    In the article, Reeves presents his arguments for why the source code is the artefact that constitutes the ultimate design of software. Apparently, this article resurfaced with the publishing of Robert C Martin’s book on Agile Software Development, after having led a quiet life in hibernation since its first publication in 1992. It is now often referenced in the agile community.

    Why is this important? It is because our perception of what source code is influences our perception of what programming is. If the source code is the design, then programming is designing. If programming is designing, it becomes natural not to accept the opinion that programming should be like factory work. Of course, people who insist that other people’s work should be more factory-like will continue to insist on this until the end of time, but at least knowing there’s a solid argument saying that they’re wrong makes you feel good.

    Sadly, outside the circle of agile aficionados, few attitudes seems to have changed. When I talk to people from mainstream organizations that live far from the current agile trends, the word “design” is still associated with the creation of UML diagrams, and the task of “design” is sometimes thought best performed by seasoned specialists. This of course, will be followed by mechanical implementation of said design by monkeys with keyboards.

    This is truly a sad example of how easily we settle into inefficient and creativity-strangling stovepipes. A programmer without the mandate to design will either have to fail or break the rules. Luckily, many choose to break the rules, but this has the side effect of creating completely unneeded psychological stress. We all deserve to be able to do our best without having to bend stupid rules. Wouldn’t that be a great world to live in?

    If you have not already read the article, do so now.

  • Russell Ackoff on Systems Thinking

    UPDATE, JAN 11, 2009 Three short clips with Russell Ackoff have been posted to YouTube.

    UPDATE, OCT 26, 2008: Kevin, who first pointed out to me that the video links in this post were broken, have managed to get in touch with Chicago-Kent. He received the direct links to the missing Ackoff lectures, and passed them on to me. Here they are:

    UPDATE: Russell Ackoff’s talks on Girls Link seem to have been taken down. Readers Kevin and Lennart have asked me if there is a way to get hold of them again. I have not yet found such a way. I have, though, tried to get some more info on this via email, but without luck so far. If I find out more about this, I’ll post about it here. Check back here or/and post a comment if you want to know if I find a way to see them again.

    UPDATE 2: Over on Anders Vesterberg’s blog, reader Eric posted links to the Girls Link talks in the comments section. The link’s go to cached content at Web Archive. I’m not able to access the talks, but some seem to be, so go ahead and give it a try.

    UPDATE 2: I’ll be adding links to Ackoff material on this page as I come across it on the web.

    Original post:

    Oh my, oh my! Is this sweet or what? A full set of videos with systems thinker Russell Ackoff. Russell Ackoff can argue like no other for the idea that we are in the middle of a paradigm shift, in which we are moving away from the old Newtonian, or mechanistic, way of looking at the world, towards something else – something based on the realization of the importance of synthetic thinking.

    Ackoff explains how analytical thinking can help us understand how something works, but it cannot help us understand why that same thing works the way it does. To understand the why, we need to look outside of that which we are inspecting – we need to look at its context.

    For more on Russell Ackoff and systems thinking, check out these previous posts.

  • Disagreement on Common Sense Caused by Change of Age?

    Why do some people see agile methods as common sense, while others see them as senseless? Why is it so natural for some people that development processes need to be broken down into stepwise descriptions of each step to take to arrive at a solution, while others say that this approach does not make sense?

    In a speech at the “Systems Thinking in Action” conference in 1993, Russell Ackoff makes the case that we have entered a change of age – a paradigm shift. For Ackoff, this change is about a switch from a Machine Age to a Systems Age. Such a change of age is brought about when we discover enough problems that cannot be solved by the current mode of thinking.

    When we start to notice this, we start to challenge the current world view. Gradually, the current view on the world is replaced by a new one, more suited to solve the problems of our time.

    Maybe this is why agile methods seem obvious to some, and crazy to others? Maybe this is why we cannot agree on what constitutes common sense? If we have radically different views on the world, we’re bound to disagree like this.

    Ackoff presents his argument using a beautiful tour through the history of the world, from the renaissance to today. Follow along in this transcript of his speech (PDF), which I highly recommend to anyone interested in agile methods and systems thinking.

  • Thinking Tools

    In the article pointed to in my last post, Pascal van Cauwenberghe used the “Evaporating Cloud” technique to attack a dilemma. Frank Patrick writes more about this and other thinking tools.

  • Is it the people or the process?

    Pascal Van Cauwenberghe writes on how the characterization of problems as having to do with either people or process is a false dichotomy, and explores how we can sneak a liberating third option into this dilemma: http://blog.nayima.be/blog/Entry20060121.html.

  • Rusell Ackoff om system

    Systemtänkande är ett ofattbart spännande ämne, tycker jag. Rusell Ackoff presenterar i det här videoklippet ämnet på det engagerade sätt det förtjänar.