planning:warnings_and_oversight
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| planning:warnings_and_oversight [2019/10/16 22:07] – Scott Cunliffe | planning:warnings_and_oversight [2025/01/21 22:07] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 11: | Line 11: | ||
| Although this is exactly the reason why people license TapeTrack, the culture shock that is created when operations staff start being warned of mistakes should not be underestimated. | Although this is exactly the reason why people license TapeTrack, the culture shock that is created when operations staff start being warned of mistakes should not be underestimated. | ||
| - | This culture shock can result in staff becoming upset, and in extreme circumstances result in the staff looking for ways to compromise the checks and balances that TapeTrack enables. Examples of this behavior include disabling | + | This culture shock can result in staff becoming upset, and in extreme circumstances result in the staff looking for ways to compromise the checks and balances that TapeTrack enables. Examples of this behavior include disabling |
| <note tip>Care should be taken to ensure that operations staff understand the importance of using TapeTrack, sign-off on their training, and have viable support channels to ask operational questions and request the repair of hardware.</ | <note tip>Care should be taken to ensure that operations staff understand the importance of using TapeTrack, sign-off on their training, and have viable support channels to ask operational questions and request the repair of hardware.</ | ||
planning/warnings_and_oversight.1571263641.txt.gz · Last modified: 2025/01/21 22:07 (external edit)