Purpose

Initiative Management …

According to the Strategy Execution Barometer^tm [1] initiative management is the weakest link in the (strategy) execution chain.

If this is the case within organisations, where the Strategy Execution database sources its data, how strong would initiative management then be in multi-stakeholder initiatives?

.. linking the hypothetical and the real

In De Flander's [1] 8 Strategy Execution Framework, initiative management is the common building block where the organisation level cycle (Update Strategy, Communicate & Cascade, Manage Initiatives, and Compare and Learn) and the individual level cycle (Set Objectives, Monitor & Coach, Evaluate Performance) meet. In the organisation level share of the strategy execution, the focus is on translating and progressively aligning overall hypotheses to local hypotheses that articulate objectives for the individual level operations.

Bringing this *8* framework to a polycentric arena or theatre, different stakeholders with hypothetical and real focus, will need to align their objectives (as much as intra-organisation stakeholders need to do this). Alignment is facilitated by aiming for MECE Mutually Exclusive and Collectively Exhaustive for the baseline, blueprints, initiatives and objectives across all actor's cycles.

.. achieving MECE in multi-stakeholder theatres

Assume a theatre with multiple stakeholders, and assume that the participation of each stakeholder in identified initiatives can be expressed using the RACI four key responsibilities:

Background

The Partnerships Database [2] that is part of the Resources collection provided by the UN Division for Sustainable Development [3] comes close to the Initiative Atlas proposition.

The Partnerships Database lists "Voluntary multi-stakeholder initiatives contributing to the implementation of Agenda 21, RIO+5 and the Johannesburg Plan of Implementation (JPOI)."

A major distinction is the decomposition for "lean programming" purposes of the initiative (partnership) data. This is explained below.

Moreover, data on partners would be included in the Actor Atlas.

Also details on Agreements and Conventions [4] (Contracts) would be part of the Actor Atlas, with elementary constraints listed in the Constraint Dictionary (where cumulativity and consistency could be confirmed).

Where initiatives originate from, or are related to, mandates, in particular those of the UN General Assembly, the Economic and Social Council, and the Security Council[5] such relationships could be described in the initiative's mandate ( http://initiativenode.wikidot.com/initiative-mandate ).

Vice versa, the initiative atlas (suitably implemented) will facilitate the fact finding in support of reviews. For example, for the Annual Ministerial Review (AMR) that was mandated by Heads of State and Government at the 2005 World Summit [6].

Founding Lean Programmes

The initiative atlas facilitates content sharing and reuse across the initiatives that various stakeholders may launch for a given area of interest, for instance a community, a country, or a sector.

Various initiative nodes, supporting the CRB, and implemented as wikis, constitute a collective portfolio that is set up according to a collective decision and action methodology and is harmonized across actors, worksystems and operations, tactic and strategic theatres.

Scope

An initiative atlas includes three kinds of nodes, each of which supports a particular kind of initiative. By distinguising three kinds of activities one can reconcile the benefits of sharing resources with a certain autonomy of the proponents and participants in change initiatives.

Baseline Initiative

A baseline initiative has the main purpose of providing a high-quality map of an area of concern. Periodically, for instance quarterly, the baseline should be updated to reflect the changes that have been successfully implemented in the area.

From a collaborative perspective, the provide of accurate open "state of affairs" descriptions that can be used for multiple purposes is currently neglected.

In many initiatives one does not explicitly describe the area of concern for which the initiative is intended. In cases where the area of concern is described, this is usually done in dedicated document chapters, with poor support for reuse (and repackaging) outside the initiative context.

Even though data and facts for making proper and valid baseline descriptions are known to many people, the open baselines are missing. This gap must be addressed urgently.

The recommended content elements of a baseline node are at: http://baselinenode.wikidot.com/

The baseline node for the CEN Focus Group eSME's is being developed at: http://baseline.fg-esmes.info/overview . It features support for engagement of stakeholders using 23 languages spoken in the European Union.

Blueprint Initiative

A blueprint initiative has the main purpose of agreeing a shared vision for a certain area of concern.
Periodically, for instance yearly, the blueprint should be updated to reflect the changes in the vision that have been provoked by the events during the past year.

For the pattern, and its justification, see: http://blueprintnode.wikidot.com/

Change Initiative

A change initiative aims to implement change. It could do this by using the regulative cycle methodology, or any comparable methodology that can allow the use of shared content provided by the knowledge commons.

For the pattern, its justification, and how several initiative nodes can meaningfully relate to a shared baseline and blueprint, see: http://initiativenode.wikidot.com/

Content

A link to the atlas (forthcoming).

Maintenance

See http://www.pragmetaknowledgeclout.be/global-agreement#toc1