- Detect that change has occurred
- Estimate the need to counter or react to the change
- Choose a desirable outcome
- Identify actions to achieve the outcome
- Do the necessary action
- Evaluate the effects of the action
It suffers a bit from being a backronym, and I don't know anyone who explicitly applies it "in real life," but I do emphasize the last item with students because it's so often overlooked. A lot of people will see a need for a change, do something to make the change, and then fail to notice that the desired outcome wasn't achieved.
I see this omission in software systems a lot too, which manifests as a lack of monitoring, control, verification, and/or alerting. An ETL process that doesn't verify the correctness of its output, for example.
I see this omission in software systems a lot too, which manifests as a lack of monitoring, control, verification, and/or alerting. An ETL process that doesn't verify the correctness of its output, for example.