GOTOKRs Global Overall Team Objectives & Key Results

Matrices
  1. 1*1 = 1
  2. 2*2 = 4
  3. 10*10 = 100
  4. 18*18 = 324
  5. 30*30 = 900
  6. 1*1 = 1

Group Factors Records

Mission-originating goal-setting

Portfolio-originating decision-making

Vision-originating problem-solving


Easy
Use Case, Reward Effect
  • Role 1/2/3.1/etc.
  • Role 1/2/3.2/etc.
  • Role 1/2/3.3/etc.
  • Role 1/2/3.4/etc.
Artefact Technique Product
Composite Structure, Risk Cause Object, Risk Cause Component, Risk Cause
  • Role 1.1
  • Role 1.2
  • Role 1.3
  • Role 1.4
  • Role 2.1
  • Role 2.2
  • Role 2.3
  • Role 2.4
  • Role 3.1
  • Role 3.2
  • Role 3.3
  • Role 3.4
Drive Project Model
Timing, Reward Effect Deployment, Risk Cause Class, Risk Cause
  • Role 1.5
  • Role 1.6
  • Role 1.7
  • Role 1.8
  • Role 2.5
  • Role 2.6
  • Role 2.7
  • Role 2.8
  • Role 3.5
  • Role 3.6
  • Role 3.7
  • Role 3.8
Process Process Process
Communication, Reward Effect State Machine, Reward Effect Sequence, Reward Effect
  • Role 1.9
  • Role 1.10
  • Role 1.11
  • Role 1.12
  • Role 2.9
  • Role 2.10
  • Role 2.11
  • Role 2.12
  • Role 3.9
  • Role 3.10
  • Role 3.11
  • Role 3.12
Pipeline Proposal System
Activity, Reward Effect Interaction Overview, Reward Effect Package, Risk Cause
  • Role 1.13
  • Role 1.14
  • Role 1.15
  • Role 1.16
  • Role 2.13
  • Role 2.14
  • Role 2.15
  • Role 2.16
  • Role 3.13
  • Role 3.14
  • Role 3.15
  • Role 3.16
Hard
Profile, Risk Cause
  • Role 1/2/3.5/etc.
  • Role 1/2/3.6/etc.
  • Role 1/2/3.7/etc.
  • Role 1/2/3.8/etc.

1430 symmetrify through: the 1430 cause vs. 1430 effect sides being in some diagrams.

3 primial/secundial/tertial centers dealing with entities & headers vs. primial center dealing with relationships & multiplicities vs. secundial center dealing with attributes & methods vs. tertial center dealing with visibility & types; below, since you must choose 3 rows per personality, there are 20 possibilities of row selection effectively creating possible ERD as per each unique element/phase diagram.

  1. 1st row is any
  2. 2nd row is 9, 3, 6
  3. 3rd row is 8, 2, 5
  4. 4th row is 1, 4, 7
  5. 5th row is any
  6. 6th row is any
Rudimentary Mockup

Say that the permutation 863195274 has to go with some role - this use case would not assign each part of the enneagram any location more specific, not even the elements/phases would need to be assigned to specific enneagrams due to the neutrality -, other permutations go other roles...? A TRPG analogy for the roles would be something like club/warrior -> diamond/expert -> heart/adept -> spade/aristocrat, which can surprisingly when used properly convert cultural tropes to control groups at most strict. You can track momentum by observing whether things tend to go back or constant or forth regarding centers, it appears that 86 is back, 63 is back, 31 is back, 19 is constant, 95 is forth, 52 is back, 27 is forth, 74 is back(, 48 is back). To mind branching out pain-journey-gain via cause-occurence-effect matrix... e.g. "ERD" Users w/ outline of MVC or as such! Selection's modernish overall. Achieving domain-driven data design involving stack productivity = cloud-native {MySQL, PHP, JS} or self-hosted {OS, Server, &c.}

Enneagram HEXACO 6Styles