I’ve signed up. I decided to take the week1 test straight away. A couple of informed guesses, but I got 10/10 :-) Which is not to say it’s easy, it looks worthwhile.
Yes.
And… cross-linking to why true commons don’t fall prey to the ‘tragedy’ https://model.report/s/hllarb/elinor_ostrom_s_eight_design_principles_and_the_tragedy_of_the_commons
I introduced Barrys Ideas to the Lunchtime systems group, and they helped write the workshops, so a group effort. They also helped run the workshops adding examples and explanations where required.
I followed a similar narrative to the blog post, apart from (over 2 or 3 workshops)
1) Ask at the start what people would like to get from a workshop about working together
2) Set up a space for people to talk openly
3) Law of two feet if they really don’t like something
4) Run through the blog post and have breaks for
5) An interactive session where each table gets a list of Balcony or basement behaviours from one of the conditions. They need to sort them into balcony or basement, and then talk to the group about what they found.
6) Encourage discussion of home / work examples, seeding with a few examples.
7) I’ve had the idea of some role play cards where we have a imaginary project and everyone gets a role - eg basement customer for the project, and everyone just has a chat, and needs to guess the role someone has…
Follow up a week or 2 later with a refresher. People turned up for this, and found it really useful - running through the conditions and example behaviours.
sad to say, it looks like they haven’t really. It covers systems dynamics plus Donella Meadows' leverage points and a couple of the good youtube clips of Russ Ackoff. It talks about insight (‘surface vs substance’), mental models, and intervention in a system, Theories of Change (umm…) So I’d say it’s a nice thing, but doesn’t really hint at the whole wide world of systems thinking (or, indeed, Design…)
It’s all by this lady: https://www.leylaacaroglu.com Seems interesting (I’ve never come across her before,,,)
Wow! Wowowowowowow! This is new! Brain ‘splode!
Goodness gracious me. This explains why not only you shouldn’t codify method - you can’t.
This could be used to convince whichever designation of people you choose to consider hard-headed dunderheads of the reason why a step-by-step approach is meaningless. It explains why complex problems, why multiple perspectives, metaphor, recursion an ting! Why patterns solve, and why patterns deceive.
Very cool - who is this person?
I read this while listening to this: https://overcast.fm/+R2IzSaFg
A quite calm rational and applied podcast about ‘systems thinking’ and how one perspective on IT process improvement is likely to fail. It’s a nice contrast.
Thinkpurpose posts are often a source of good discussions at work. Colleagues regularly point our versions of the problems in the post. It’s good to hear from someone else living through it.
Is slide 64 on the first link an actual manifesto that is out there? It’s a good one. Can you get it down to five ;-)
Interesting. The robots are fragile in that they are unable to adapt to change in terms of their role on the production line. But it looks as though the architects have built yet more fragility into the factory spaces themselves, by assuming that automation in the production process will increase and there will be a continued reduction of involvement of humans in that process.
I wonder how much of the requirements for customisation was driven by their own marketing department?
Thanks for sharing this.
I also recently wrote a piece on why models are wrong and still useful.
Here it is
https://mihirsmusings.wordpress.com/2016/01/09/why-models-are-wrong-and-still-useful/
It seems that knowing you are using a model and understanding what that means is important for decision making and communication. There seems to be a lot of ‘One true Model’ people about, and for them it’s not a model.
I love his idea for the amazon shopping cart : “People who ordered <your book> have never ordered <these> books”…
So <people who think like this> have never considered thinking <like this> :-)
I’ve just realized how closely this fits in with John Peel. I’m sure he was thinking “I bet these records have never, and will never again, be played back to back….”
Very systemic! Dr. Myers treats patterns, not symptoms; people, not injuries; and his comment about evidence and prevention was wonderful. Thanks, Mike!
It’s great isn’t it. I wasn’t sure about posting it, but it’s a type of thinking everyone can benefit from. The video was posted by http://www.functionalpatterns.com/ if you’re interested in systemic fitness ideas inspired by Dr Myers.
I like this site. The number of members didn’t appear on my success criteria. I often find useful things here. I guess it depends on how much work Scott needs to do to keep the members happy?