Showing posts with label contribution. Show all posts
Showing posts with label contribution. Show all posts

Friday, 22 November 2013

What quality is my initiative at?

Often I get asked "why is my initiative not on", or "why is my initiative giving the wrong level of quality?"

Lets use the following model to consider why that would be.
 

Why is my initiative not on? 


If we set this model to none, intermediate and optimal in the optimise window we will get no outcome performance.

This may seem odd, but the reason is that in Realisor you don't force Initiative performance, but request it.  When you set an initiative to a quality it asks the capability linked to that quality to turn on.  As such, any quality is considered active whenever the capabilities behind it are turned on.

As such if we change the model to


We get the expected

Why is my quality / outcome at the wrong value?

The next mistake people make is chaining capabilities.  As discussed before we ask capabilities behind the quality to turn on, and the highest quality with it's capabilities fulfilled is the working quality.  Lets see an example.
 
This seems right?

But then doesn't...
 
Why is this?
Setting I1 to optimal sets the chain behind it to on.  This activates cap 5 as it is chained behind Cap-1, which in turn means that although the intermediate quality of I-2 was requested there is sufficient capability to activate the optimal quality of I-2, so you get 100% quality from I-2.

Why don't we fix this bug?

It isn't a bug.  What this does is allow you to model shared wins.  If we consider
This tells us that if we set our top initiative to optimal we automatically get the intermediate quality on the bottom Initiative (or intermediate on the bottom automatically gives us optimal on the top).  There is no extra cost to this, and could show a shared facility etc.

However there is a danger, and that is chaining capabilities where one sits behind another.  This must not happen, otherwise the calculations are strange, so always avoid

Tuesday, 9 April 2013

Contribution Scores and Show Value Flow

Contribution Scores

Within the Map View tab of the Model function, there is a visibility option called 'Show Contribution'. This button toggles on and off on the display of contribution scores which if on displays the percentage each and every ancestor Objective/ Outcome/ Initiative contributes to it.
When this is selected, a box for a percentage appears over Outcome, Objective and Initiative nodes.

When 'Show Contribution' is turned on, you are able to right click on an Outcome or Objective node and select Calculate Contribution Scores from the right click menu. This will show 100% appear as text on the node selected. The immediate ancestor nodes will have their contribution scores calculated and displayed on the node. For each of their ancestors this will be calculated and so on.
 
Showing Contribution scores acts like a sense check on the weightings of the links. When any weighting is adjusted or link added to the node, the contribution scores will automatically re-calculate and show the updated contribution scores.

Show Value Flow

Show value flow is enabled through selecting the 'Show Value Flow' button within the Map View tab. This displays a box between the node ID and node Title on Outcome and Objective nodes that you are able to enter a numerical value into.

When a value is entered into the value flow box (in this example 100 into Obj-2), the value flow is calculated back through the nodes connected to it. You can see through following this example that using the weightings on the links, the value of 100 is calculated back through the nodes.

Showing value flow acts like a sense check on the weightings of the links. When any weighting is adjusted or link added to the node, the value flow will automatically re-calculate and show the updated figures in the text boxes.