Why the need of System Collaboration?
Do you feel that you have too many problems or impediments within your organization, like; too many meetings, wrong culture or values, problems despite following the recipe, transformations that take too long time, too many transformation coaches, people not included in the transformation, efficiency problems, decreasing long-term planning, lost Big Picture, etc.? Or you just have a nagging unease, accumulated over time, from all the permanent and increasing number of problems; "is this new way of working really going to work for us? For anyone?"
Then, System Collaboration is for you.
System Collaboration is totally focusing on making a flourishing organization, by eliminating all organizational problems found within a way of working. This is possible since all the deductions done in System Collaboration, have science as its foundation, for all of its content. Up until today, it consists of three different methods, where no one is more prescriptive than needed, only to the point that the needed science is fulfilled:
SPPA - Systemic Problem Picture Analysis
SPPA collects all the different problems all over the organization, connects them, and finds their root causes. SPPA can be used in any context (which automatically also means for any domain).
SOSD - Systemic Organizational Systems Design
SOSD is a method that eliminates the found problems. This indirectly means a re-design of the existing way of working, so that is fulfilling all the needed science, and by that is free from root causes. SOSD is valid for any context, but focus is mainly on the complex and complicated context of product development and any domain therein.
TDSD for software - Test-Driven Systems Design for software
TDSD is a truly scalable method for big software development.
Below is a clickable picture of System Collaboration. The presentational order of System Collaboration is the science at the bottom, followed by the deductions from them, right above, which means all the WHY. Over that we have all available methods, the HOW. For all of you that like details, there are many links; the WHY is dissected more and more, also backed up by many examples. For even more overview of System Collaboration and how it is started, click here.
© 2018-2022 Karl Rehbinder
The material can be shared, as long as
I am named as the copyright holder.