Strategy and knowledge

Layers

Layers build on each other and each one works on its own: turn on the next layer when you want it, turn it off when you don't. Turning off deletes no data.

1. Base

   “Let me keep my list in order.”

   Knowledge records and files

   • Documents are kept as knowledge artifacts with type, owner and version, moving from draft to in review, published and archived
   • Each artifact carries a confidentiality level: standard, restricted or confidential

2. Tracking

   “Let me not miss what happens when.”

   Objectives and key results, demands and decisions

   • Strategic themes, objectives and key results; progress is the current value over the target, capped at 100%
   • An objective's action opens as a work item that stays linked to it
   • Requests of 7 types from 4 channels become demands; a demand is approved, rejected or deferred, and every decision is kept
   • An approved demand is committed, with its business case, as an initiative of work

3. Process

   “Let the work follow a rule.”

   Prioritisation models, reviews and lessons

   • Gate reviews with a decision for code, design and quality; period reviews with lessons for sprints, retrospectives and post-implementation
   • Lessons learned in 4 types, with a recommendation and an owner; open, applied or archived
   • Prioritisation models are kept with their criteria and weights; each assessment score names the model it followed

4. Control

   “Let me manage it and account for it.”

   Value management and metric catalogue

   • Value propositions aimed at a stakeholder segment: hypothesis, validated, active and retired
   • Financial, operational, strategic or social benefits tracked from projected to realising and realised, with the value realised
   • Metric definitions of 8 types with aggregation and frequency; each measurement is marked measured, estimated or interpolated