How long does it take before a newly implemented, empty database becomes useful?
The Empty Kitchen: A Story
Most of us accumulate and stock our kitchens slowly over time as we move away from our parents’ houses and launch ourselves into adulthood. Herbs and spices, canned goods and pasta, refrigerated staples, and seasonings and sauces are typically collected over time, often taking months or years.
Imagine what it would be like to encounter an entirely empty kitchen…!
After living in Switzerland for two years, we returned to our home in California. The folks renting our house had moved out a few weeks before our arrival and, as previously agreed, they had completely removed all food from the premises. The fridge was totally empty: There were no sauces, no jams, no jars, no food of any kind. The shelves were equally bare. Even the spices and herbs were all gone.
Without any food, our kitchen, while complete in terms of appliances, pots, pans, tools, and utensils, was effectively useless. It had potential, but that potential could only be realized once we had re-stocked it.
Our first few uses were simply reheating restaurant leftovers and take-out meals. It took several trips to our local markets to put food on the shelves, literally! And it was only once a set of basics was accumulated that we were able to really use our kitchen to prepare meals. That represented a breakeven point: cooking in our kitchen vs going to restaurants and buying take-out meals. Several weeks went by before things were back to our pre-Switzerland inventory.
It was a significant event in our lives that holds strong memories!
The Challenge: Starved for Data
Empty databases are like that empty kitchen. Lots of potential, but without food to cook you’re going to have unfilled stomachs! Similarly, an empty database leaves your customers starved for data...
You’ll find the balance of this article here. Enjoy!
No comments:
Post a Comment