Know more
There are no side effects, only effects
Daniel Goleman quotes a principle from systems thinking. In a system there are no side effects, just effects, anticipated or not. The phrase side effects suggests something minor and accidental. However, from the system’s point of view, every result is simply a consequence of how it works.
Medicine offers a clear example. A drug may lower blood pressure and also cause fatigue. We call the fatigue a side effect, but the body does not make that distinction. Both outcomes come from the same chemistry. Calling one secondary is a human choice about what we wanted, not a fact about the system.
Planning for side effects in advance
Business is full of these surprises. A sales bonus may increase revenue and, at the same time, encourage aggressive discounts. A new app feature may boost engagement and also overload customer support. Therefore, before launching a change, list the effects you hope for and the ones you fear. Treat both as real outcomes.
One helpful method is the pre-mortem. Imagine the project failed a year from now, then ask why. This exercise often reveals hidden side effects that optimism ignored. For example, a team may realise that a cheaper supplier could damage delivery times and, eventually, brand trust.
Goleman’s point is ultimately about responsibility. If every result is an effect, then we cannot dismiss unpleasant consequences as accidents. We own them too. That mindset makes decisions slower at first. Yet it leads to fewer nasty surprises and more resilient systems over time.
Moreover, reviewing past projects helps. Look at a launch from last year and list every outcome, wanted or not. As a result, you will start to see patterns, and those patterns will make your next plan more realistic and robust.
