We often go through complex IT systems implementations to optimize our processes, secure our data and accelerate collaboration.
But after this complex implementation, we sometimes realize that our situation is more complex than it was before using the new system. Yes, our processes are optimized, but we still dont have the complete picture that would have helped us to see whats happening in the organization.
One of the main promises of IT systems is to let you get control over your always growing data. Hence, you should always put data traceability at the center of any IT project.
But what is data traceability? A few examples would be:
So, I would have the following advice for you If you cant easily trace your data at any point in time in the system, its probably time to shred some functionality out of your project and to push it to a subsequent phase. Take this saved time to add traceability features.
If you push traceability to the end of your project, youll always feel that its your system thats controlling you. If you implement a traceable system, youll always stay in love with it.
At last, also remember that legally, you have the responsibility to always explain the lifecycle of your data and documents. If a customer sues you and you cant prove the integrity of his data from point A to Z, it will end up costing you a lot more money than if you had thought of it from the beginning.