The Changeability Score and removing `weaknesses` ordered by the highest to lowest frequency
Step 21: Comparing Modification Time of “Weaknesses” with “Goals/ Purposes” “Time of Achievement” and Categorizing by Traffic Lights Colors In this step, we will analyze table 22. By first looking at the column 3 of table 21 (21- 3), you will be able to see the highest frequency of weakness has occurred in certain period. You can then compare all columns 3 of table 22 (22-3) and column 3 of table 21 (21-3). See whether the “weakness” is related to a “goal/purpose”. Also make effort to ensure the problem/barrier is solvable within a particular time chosen to achieve the “goal/purpose” ¾ Definitely Solvable “Weakness” with High Score If the related “weakness” to a “goals/purpose” is solvable within “time of achievement” to get that “goals/purpose”, then you should score it over 50 and specify it with green color of traffic light. For example, since being hasty in table 21 has the highest frequency among long-term goals (21-3- 5(2)) and in table 21 the needed time for modification is 10 months. (22-3-2) so, cell 22-1-2 should be specified with green color. In table 12 as there are many versions of it for all individual “goals/purposes” and “achievement barriers” so through all pages wherever we see “weakness” of being hasty it should be green. ¾ Lower Scored “Weaknesses” If the “weakness” related to a “goals/purpose” is not solvable within “time of achievement” you have considered to that “goals/purpose”, but is still scored over and does approach 50 but is not solvable easily. These “weaknesses” should be specified with yellow color of traffic lights. For example, “Weakness” of being distracted in table 21 has the highest frequency among short-term goals (under 1 year) (21-3-3(1)) and in table 22 the required time for modifying it is 18 months (22-3-1) so, cell 22-1-1 is specified with yellow. Again refer back to table 12 and wherever you see distracted “weakness”, it should be specified with yellow color. In other words, yellow “weaknesses” are “weaknesses” which are time taking and the needed time for resolving them doesn’t adapt the required time for achieving relevant “goals/purposes, but their solvability score does approach 50.
is this right?
Shared by `S***********i` on Mar 27, 2025