I’m working backwards. I started this entry on defining change. Then I realized change can’t exist without systems. So, what is a system? I like the following (heavily inspired by Systems Thinking Basics: From Concepts to Causal Loops)

Causal Loop Diagrams (CLDs) share several things with books: they both tell stories, they can be fact or fiction, and they’re both easier to read than write. Keep reading to learn how to write CLDs. The Buddy System The first step in creating CLDs: find a buddy, friend or coworker with whom to share the diagram. When I started working with CLDs, I didn’t pay attention to this. It’s come to my attention lately that I add something to every diagram that comes my way,

Causal Loop Diagrams (CLDs) can help us understand complex interactions and events by revealing system structure. Unlike buildings, most systems don’t have visible structure. We notice systems by observing events. When the events form a pattern (usually over time), there’s indication that a system is working. We use CLDs to diagram the system and reveal the interactions that lead to events. In “Learning to Change”, I used Casual Loop Diagrams (CLD) to show interrelationships involved in my learning process. Causal Loop Anatomy Causal Loop Diagrams

In Changing Quicker we looked at reducing or removing system delays to reduce the time delay between realizing a change needs to be made, and when the change’s effects occur. Another way to change quicker involves learning to change. Learning is a process that depends on experience and leads to long term changes in behavior potential.

“Don, the software’s locked up again! Can you come up here tomorrow and fix it?” George was on the other end of the conversation. George and I had started working together when his employer moved a production line from Florida to Virginia.

I’m not surprised when the first words I hear are “Something’s wrong, can you come and take a look?” What did surprise me was Saturday and at home.

Sharkey, the sales VP of UberDenke Software Products, firmly believes he needs to have the next release of the UDCRM product in three months. Engelbert, the software engineering VP, estimates a minimum of twice that long – six months – to implement all the new features. During the discussion, Sharkey drops some thinly veiled threats: