Applying Systems Thinking in Teams.pptx
•Télécharger en tant que PPTX, PDF•
0 j'aime•35 vues
Systems Thinking is a way of looking at the whole system, rather than just the parts. This workshop linked Systems Thinking to Team Dynamics in Software Teams
Recommandé
Contenu connexe
Dernier
Dernier (11)
En vedette
En vedette (20)
Applying Systems Thinking in Teams.pptx
- 1. Applying System Thinking in Teams “Systems thinking is a discipline for seeing wholes” Peter Senge
- 4. Systems Thinking is a discipline for seeing wholes rather than parts, patterns of change rather than static snapshots, for understanding the subtle interconnectedness that gives living systems their unique character. Peter Senge
- 5. ELEMENTS Easy to identify parts of a system CONNECTIONS Physical flows, information flows PURPOSE Observe how the system behaves over time
- 8. Causal Loop Diagrams Hunger Food - + B
- 9. Savings Acc Interest + + R Money Causal Loop Diagrams
- 10. Causal Loop Diagrams Fishing Fish Population - - R
- 11. Feedback Loop Cards Each card has a small challenge Take a card, identify increasing and decreasing effects, and what kind of loop or loops you have ±1 min each for a card
- 12. Inflows, Outflows and Stocks Ground Coffee Filter Papers Boiling Water Coffee to drink Used filters Heat Loss Evaporation Stale Grounds
- 14. Shifting our thinking to PEOPLE Try it! Examples of Team Stocks
- 15. Can we store it? What creates the stock? What depletes it?
- 16. Code as a Stock Can we store it? Working Code Business value Is understood by Team Can be modified
- 17. Code Value is tied to Team Knowledge
- 18. Exercise: What creates it? What depletes it? Image from Vincent Déniel Code as a Stock
- 19. Boundaries
- 24. KRS Case Study
- 25. Offer more guidance Wanted buy-in Recognise all roles Support diversity Career Path Framework
- 26. R B + + + -
- 27. Imagine, Research, Act Purpose & Vision
- 29. A managers job is to manage the system not the people
- 30. Sketch your ideal High Performing Team
- 31. Systems always behave exactly as they are designed, just not always as they are intended.
- 33. Thinking in Systems – Donella Meadows https://donellameadows.org/archives/envisioning- video/ Intuition vs Analysis Boundaries constrain the problem (simplification) More Great Systems Thinkers: W Edwards Deming Gerald Weinberg Dr Russel Ackhoff Peter Senge
Notes de l'éditeur
- Lor: Morning, ready for the day? Who has some background in ST? We’ll explain as we go, and we’ve got lots of exercises for you to practice ST
- Lor; From CT, very windy, founder of a mid-sized software co, work closely with our various teams Ayesha: CT, 1ST AMS, People focused – ST LENS to support KRS, MOM
- AB – YOUR TURN GAME to get to KNOW EACH OTHER At your TABLE in GROUPS – 5 MINS FIND things in COMMON, like PINEAPPLE on pizza, CATS or DOGS AVOID the obvious Share interesting feedback – chocs for most interesting feedback
- Lor – how many devs in the room? Devs tend to be detailed people, and ST challenges us to look up and see the bigger picture To see patterns, and to see connections
- Lor – a system is defined not by its parts but by its purpose
- Lor - Bring variables back to a desired state – self correcting, stable
- Lor - Change is compounded to cause more change – instability, exponential growth, unstable
- Ayesha – Simple balancing loop – Hunger increases, eat, hunger decreases, back in balance
- Ayesha – Extra money, put in savings account, earn interest, get more money – Positive reinforcing loop
- Ayesha – Fishing, over fish, decreases the fishing population, which decreases the amount of fish available, this is a negative reinforcing loop.
- Ayesha – to be discussed in teams Take a card explain the variables and verbs Variable= Element Verb = Shows Action Idenitify loops
- Lor - Inflow outflow explanation with Team examples
- Lor
- Lor – Flipchart. What kind of stocks could a team need, or be? 2-3 Peppermint crisps
- Lor
- Lor
- Lor 1st gen developers have full mental models When the model breaks, you start to hack out pieces of the hedge to get anywhere!
- Lor Exercise for group 1st gen developers, library dependence, upgrades, mental models
- Ayesha: A conceptual line that divides the system you want to study from everything else A system can exist inside of a bigger system. Different systems within the body.
- Ayesha Example: Learning to swim: Pool defined edges, shallow side Ocean: Vast, can be overwhelming, the ocean is often end goal, As you build your systems mindset, start with a defined system boundary
- Ayesha conditions that influence the problem? issues, people or systems are working together to create what is seen above the water? ripple effects might be created by our solutions?
- Ayesha Able to wide your aperture, NOT just zoom in Maintain firm view of the landscape Balance holistic and reductionist thinking Move through these scales, shifting of perspectives to build a 3D worldview.
- Ayesha Conditioned - linear thinking, “cause-effect” thinking. Recognize relationships and interdependencies between parts. Look to feedback structure to understand why problems persist despite our best efforts. Seek to change the structure of the system by adding or removing feedback loops; strengthening or weakening loops.
- Lor we've been dealing with a concern around growing and developing people in our teams. We take on a lot of interns, and remote work has made it harder to help these developers grow. Even our seniors seem to be in a comfort zone, and not growing as we need. So we could blame the people, but Systems Thinking says we should look at how our systems support or hinder our people's growth.
- Ayesha – Leadership team realised we need something to guide our careers, but not impose a very rigid framework Glue roles Diversity
- Ayesha
- Ayesha – SIMPLISTIC VIEW Does this REALLY support our goal of increased AUTONOMY? INCREASE STRESS – Salary bands, demotions, do I MEET the NEEDS at my LEVEL? No BUY-IN – How can we do this a BETTER way? Any IDEAS?
- Lor – Donella Meadows says that Vision should start with imagining your ideal scenario, research what is possible and then acting We jump to act and skip first 2 steps
- Lor – people are scared to think about ideal scenarios (Naive, neg words) What would be a great work environment, it's not pipe slides in the office (apologies to Lego) Let's imagine - What’s your idea of a great working environment? Arrive at desk, greet colleagues, happy? Type of work
- Lor - W Edwards Deming says a Bad System will beat a Good person every time
- Lor 2 part: 10 mins to discuss ideal team, 10 mins to discuss how systems prevent us reaching those ideals
- AB – beautiful COASTLINE, a common WALKING spot. These trees have been MOULDED by the wind we experience. Let's think about THAT when we are creating SYSTEMS. At its HEART, seeing things through a WIDE LENS, RECOGNISING how INTERCONNECTED we are, and ACTING with EMPATHY and INNOVATION.
- Thank you for your time, we will open the floor for any questions, insights or comments. Feel free to share personal stories or struggles you're having?