Strategy Maps allow organisations to drill down through Planning Hierarchy while seeing performance of individual nodes, actions and KPIs linked to the strategic plan. Furthermore, it provides the ability to view details of each node along with the filtering options on various dimensions. The essential goal of Strategy Map is to provide the user a bird’s eye view of the Planning Hierarchy with an enhanced user experience.
...
Workspace > Strategy Map OR.
Easy access menu option.
...
At the time end user gets into Strategy Map, by default, Goal 1 > Outcome 1 > Strategy 1>Task 1> Sub Task 1 path is collapsed. Other paths can be collapsed once after user clicks on a particular Goal within the map itself. By default, Strategy Map's content is filtered against last close period. Therefore, all the performance figures will be filtered out to last closed period unless it's changed from filtration area.
...
I. Trend in terms of the KPI count (based on Strategy Map Configurations).
IF for last closed period (e.g. 30 Sept) or corresponding previous period (e.g. 31 Aug) there is at least 1 ON TRACK KPI, then compare ON TRACK count between the two periods and show arrow (e.g. as of 30 Aug there is 3 ON TRACK KPIs, and 30 Sept here is 4 ON TRACK KPIs, then green UP arrow);
ELSE IF for last closed period (e.g. 30 Sept) or corresponding previous period (e.g. 31 Aug) there is at least 1 OFF TRACK KPI, then compare OFF TRACK count and show arrow (use reverse logic, if count has reduced then green UP, if count has increased then red DOWN).
ELSE sideways orange arrow.
II. Trend in terms of average KPI performance (based on Strategy Map Configurations).
Compare average performance values between last closed period and corresponding previous period and show arrow as per the standard business rules. If cannot compare numerically (e.g. all KPIs have no target set in either period or both periods), then always display sideways arrow.
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
If All ON TRACK, OFF TRACK and MONITOR count is 0, then node is N/A. If majority is ON TRACK, then node is ON TRACK. If majority is OFF TRACK, then node is OFF TRACK. If majority is MONITOR, then node is MONITOR. If ALL is N/A, then node is N/A. |
| Info |
|---|
Note:
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
If majority is ON TRACK or OFF TRACK and are equal, then MONITOR If majority is ON TRACK or MONITOR and are equal, then MONITOR If majority is ON TRACK or N/A and are equal, then ON TRACK If majority is OFF TRACK or MONITOR and are equal, then MONITOR If majority is OFF TRACK or N/A and are equal, then OFF TRACK If majority is MONITOR or N/A and are equal, then MONITOR If majority is ON TRACK or OFF TRACK or MONITOR and are equal, then MONITOR If majority is ON TRACK or OFF OFF TRACK or N/A and are equal, then MONITOR If majority is ON TRACK or MONITOR or N/A and are equal, then MONITOR If majority is OFF TRACK or MONITOR or Nis OFF TRACK or MONITOR or N/A and are equal, then MONITORthen MONITOR If All are equal ON TRACK and OFF TRACK and MONITOR and N/A then MONITOR
|
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Monthly – previous period would be 'a month back' compared to last closed period. I.e. if last closed period is December-17, previous period would be November-17. Quarterly – previous period would be '3 months back' compared to last closed period. I.e. if last closed period is December-17, previous period would ne October -17. Yearly – previous period would be '12 months back' compared to last closed period. I.e. if last closed period is June-17, previous period would ne July-16. |
...