Implementation Archaeology: When Finding Business Logic Becomes an Easter Egg Hunt

Picture this: The monthly performance report has just been received, but it’s missing some data. No errors were generated, yet the blank section on the output indicates something went wrong. The analyst sends a message to IT to report the error, and this starts the Easter egg hunt for the issue.

How many times has this happened to you or your colleagues? Whether you rely on a large single vendor, multi-purpose platform or multiple integrated systems, I’d be willing to speculate it’s a common occurrence. Beyond tracking down today’s Easter egg, how can we avoid the problem in the future or remedy our existing platforms?

by Christopher D. Sadala, Senior Consultant

Read Full Article
Skip to content