Imagine you have a database of contacts - names, surnames, and phone numbers - linked to your projects as a list to choose from.
Excel (and any other data holders) encourages us to keep our data highly granulated, like this:
A1: Kevin
B1: McCallister
C1: +1 555 8954 7624
This type of data organization only makes sense if you need the data separately, that most probably is not your intention. Otherwise, if Kevin's surname and phone number do not change from project to project, it would be more logical to keep them together:
A1: Kevin McCallister / +1 555 8954 7624
By doing that, you can avoid the risk of data shifting and mixing, and enhance the simplicity of data processing.
At #DataEnq we deal with more intricate scenarios, though the effective data handling remains a fundamental aspect of all our solutions.
Comments