5.Looking to the situation from a perspective of complex responsive processes of relating. When I reflect on what has happened, I realize that the way I implement software like FLOW MPM is based on assumptions about rational or formative causality. In rational causality, knowledge, competence and technology are all thought to develop as a result of rational choices made by inventors, scientists, investors or leaders. In other words, it is assumed that individuals choose, manipulate and control the technological development (Stacey et al., 2000). In addition to this rational causality, however, also a formative causality is implied. Resources, knowledge and technology are all thought of as designed systems, and this means that they must unfold the design already enfolded in them by their designers, like an acorn is always developing into an oak. We do not exactly know how it will be shaped, but it will definitely be an oak. In other words, the cause of technological development is the formative process of the operation of the system (Johannessen & Stacey, 2005). We as developers design the system and force people to work accordingly to achieve the predicted results over time. But as my narratives show the results are not predictable at all. The systemic approach, which is based on rational or formative causality, is not what I experience in my work with clients.