Techniques for Making Better Nonprogrammed Decisions

Step 5: Implementing the Selected Alternative

After selecting an alternative, you must implement it. This may seem too obvious to even mention, but implementation can sometimes be a challenge, particularly if the decision is going to create conflict or dissatisfaction among some stakeholders. Sometimes we know what we need to do but still try to avoid actually doing it because we know others in the organization will be upset - even if it's the best solution. Follow-through is a necessity, however, to be effective as a manager. If you are not willing to implement a decision, it's a good idea to engage in some self-reflection to understand why. If you know that the decision is going to create conflict, try to think about how you'll address that conflict in a productive way. It's also possible that we feel that there is no good alternative, or we are feeling pressured to make a decision that we know deep down is not right from an ethical perspective. These can be among the most difficult of decisions. You should always strive to make decisions that you feel good about - which means doing the right thing, even in the face of pressures to do wrong.

Callback before_footer in local_aigrade component should be migrated to new hook callback for core\hook\output\before_footer_html_generation
  • line 7225 of /lib/moodlelib.php: call to debugging()
  • line 7292 of /lib/moodlelib.php: call to {closure}()
  • line 71 of /lib/classes/hook/output/before_footer_html_generation.php: call to get_plugins_with_function()
  • line 987 of /lib/classes/output/core_renderer.php: call to core\hook\output\before_footer_html_generation->process_legacy_callbacks()
  • line 154 of /mod/book/view.php: call to core\output\core_renderer->footer()