Change Methodology
Change is one of the areas where the articulation of content commons can bring enormous social savings.
The Public knowledge for the #2030Agenda - #2030library is an institutional measure to enable us to achieve those savings.
We aim to transform the Collective Regulative Bundle (CRB) which includes the Regulative Cycles of all.
Multiple stakeholders must start using the tools of collaborative planning at the three levels of transformation of Dr. Shingo [6]:
- Principle-driven: embedding principles into culture;
- System-driven: structuring tools into a systems context;
- Tool-driven: using specific methods to create point solutions.
Regulative Cycle
Originating in psychological practice, the regulative cycle [1] has been extensively applied as a methodology of (clinical) practice, geared towards the "interested" regulation of the behaviour of groups or organizations in the desired direction. The cycle includes the activities evaluation (of work system operations with respect to an instrument or via benchmarking), problem identification (selection from a problem mess), diagnosis (of the problem situation – analysis), plan of action (design), and intervention (implementation).
Rio Principles
The principles that we want to embed into society are the Rio Principles.
Internet and social media systems
The systems context for collaboration on a massive scale includes the internet, social media platforms and libraries.
Collaborative planning
A Collaborative planning (CPM) methodology builds upon a facility for sharing programme and project artefacts in a group. Such a group can be small, for example the workers on a farm, or big, for example all inhabitants of a country, or all living members of mankind.
Change by all in the group builds upon the mobilization of resources for the group's common causes. A practical mini-guide on resource mobilization for educational research in West and Central Africa has been compiled by ERNWACA [2].
Pretext Vulnerabilities
Preparing for change in a group is not only knowledge intensive. The justification for allocating the resources mobilized for causes of the group is prone to misrepresentation in the diagnostics-therapeutics chain: what are the problems in the mess, what are their causal chains, and what design is going to resolve these problems (with a minimum of undesirable impacts).
Abuse (by privileged individuals) is motivated as they may see opportunities to use for their own (a small group's) advantage, the resources that have been pooled and mobilized for the group at large.
Pretexts are facilitated in situations with a confused common cause-and-effect picture, where knowledge pertinent to change remains or gets dissipated, fragmented and reworded in innumerable documents and texts. The communications and knowledge management practices are non-transparent.
The weakest link in the chain reality makes that the vulnerability is very likely to be exploited, with a polarizing impact on the resource mobilization: on the one hand, member's commitment erodes quickly as the common value for effort reduces, on the other hand, easy pretexts and institutionalized powers feed a leader's motivation to maintain the status quo.
Transparency & shared diagnostics-therapeutics chains
Checks and balances in change by all in a group are necessary to avoid or mitigate the resource-abuse risks caused by the pooling of resources and claims1.
Transparency2, collaborative diagnostics capability and collaborative therapeutics skills, and shared diagnostics-therapeutics chains offer possible controls for the risks to sustainable and equitable development induced by poor communications and knowledge management practices.
A collaborative planning methodology emphasizes systematized open content as reusable programme and project artefacts. Published and maintained on the web, these artefacts can enable programme and project practices such as those advocated by the UK Office of Government Commerce [3], but for a much smaller overall cost and effort.
Moreover in cases where the group's interactions are ICT-reliant[4], these programme and project artefacts can feed (system) development approaches that leverage the formal approach to systems modeling and enterprise architecture tools[5].