Chapter for in Images of Organizations by Morgan focuses on oranizations as brains, learning organizations. There were several things in this chapter that I really enjoyed. For the sake of brevity I'll just focus on two.
First of which was the idea expressed on page 108 of requisite variety meaning "the internal diversity of any self-regulating system must match the variety and complexity of its environment." This seems to suggest that extremely complex environments and organizations will have more internal diversity and variety.
An idea which is counter to the reliance of bureaucracy and red-tape for mechanistic organizations, where the workers had firm rules and guidelines to follow to help maintain order and interchangeability.
Secondly there was the idea of error elimination on page 82. I like the idea that we don't pick things up, rather we fail to not pick them up and by failing to not pick it up actually pick the object up. This was not something I had considered as fully as I had once I read it. Both of these tend to, it seems to me, provide opportunities for organizations that behave like brains to find ways to self-organize or to learn how to learn.
By having ever-growing diversity of opinion and variety of working and leadership styles, an organization led by self-organization and learning can help to find the best possible route to success. By failing, new procedures and policies can be created that help others not to fail, and by not failing succeed. I regularly cite to my teams how although Steve Jobs has been well known for his successes with Apple, in many ways his success came by way of his failures. "Lisa stands forgotten in the shadow of the Macintosh, but its abject failure (the first model only sold 10,000 units) taught great lessons–especially to Lisa’s original project lead, Steve Jobs, who was kicked off and put on another project: the Macintosh," (Lumb, 2015). It's through failures that we, even as organizations, can figure out what best not to do again.
I think back on my life and the major "Lisa" moment for me was when I wanted to create an app called "PopQuiz Password" (see
here). I know, horrible name, but it was a working title. Basically, it was designed for parents to ensure that their kiddos got some learning in while they gamed. It was a project I developed when getting my MBA back in 2004. Before a kiddo could play a computer game they had to complete a grade appropriate quiz. They were rewarded time to play based on how they scored. 100%? 30 minutes of play time. 50%? Then just 5 or 10 minutes of game time. Also we created modules like Texas History, or Boy Scouts and Bible History, to try and make it appealing to parents and more relevant for kids. Additionally we came up with the idea of creating teacher interactions, whereby teachers could upload their own class specific questions and have them load onto the kiddos quizzes.
We started a proof of concept, but then the project died off. There were a multitude of reasons for it dying off, but I've always wondered if that was my Lisa moment. What if I had created PopQuiz Password and it had been a rousing failure like Lisa? What would I have learned? How might I have developed other microlearning opportunities before microlearning took off?
I am far to safety oriented to have a Lisa moment. Any whiff of failure and I'll look for another option instead of face the failure. Maybe Lisa moments are what entrepreneurs need to be successful ultimately?
References
Lumb, D. (2015, January 22). Remember Apple’s Lisa, the computer that cost Steve Jobs A gig? Kevin Costner does! Fastcompany.Com; Fast Company. https://www.fastcompany.com/3041272/remember-apples-lisa-the-computer-that-cost-steve-jobs-a-gig-kevin-costner-d (Links to an external site.)
Morgan, G. (2006). Images of Organization (Updated Edition). Thousand Oaks, CA: Sage Publications.