Its always important to keep an eye on the details of your processes. This is especially important when changes are requested or issues have been detected.
David Ayiku found this very important after a recent incident. A client was reviewing data for past customer activity. Some of the customer information was missing.
During the review we noted that the client had asked that a filter be created to exclude customer information from searches if the customer had not been active in their system within the past 18 months.
Sadly the developer slipped the logic into the code and no further notes were made.
It only took us 4-5 hours to determine why this was happening.
Once we found the logic excluding the customer information, we were then able to approach the client and have him make a decision on the next steps.
Needless to say, reviewing the details was great in this instance by not only helping us determine the issue but also we were able to gather additional information on the process.
When performance expectations are set at near-impossible levels, previous techniques, frameworks and routines won’t do. Creative approaches and new ways of learning are required. This can take companies to new heights or shake them out of a rut.
ReplyDelete