Models are like kitchen utensils. You need a variety of them, and you should know when and how to use them. They should be useful for more than a single task.

My name is Don, and I have a problem. I’m trying to make sense of my world. Sometime ago I asked myself the question, “What is the earliest indicator that something is going wrong?” And of course, I’m not happy with just a single problem, I’m looking for the answer for the base problem class, which all other problems inherit. What would you expect from an ENTP?

People working with systems know the interactions between the system and its environment create a tremendous opportunity for success or failure. In computer systems the interfaces between components, utilities, other systems, and the user often contain the most initial defects.

Re-reading my blog titles occasionally leads to interesting thoughts. Many titles mention change, and most entries have something to do with change. But after all these entries no one has asked me, “Don, what do you mean ‘change’?”. Until recently, I haven’t asked me either.

Can knowing how one system works help you understand how other similar systems work? Do software, project and physical health have much in common?

Engineers make the darndest assumptions. I made one such assumption in “Change and Stable Systems”. The unstated assumption involved starting with a stable system. But what do you do if your system (as in team, project, company) is unstable?

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

Will reorganizing every two weeks lead to stable software processes? What conditions would enable this to happen? When should we schedule the next change?

Several years ago I found out that I was not really in charge of everything, or in control of very much. This lead me to

Don’s Dismal Dilemma: How will I achieve my goals, when I’m not in charge or control?