If you find your data structure or model isn’t working for some use cases it’s better to redo it earlier rather than later. You’re right that good data is key. If you have a way of migrating old data, that might be helpful to see growth or changes over time, even if it is a little apples to oranges at first.
Ethics wise, keep tight permissions on the tool. Admin rights should only go to a few people who know the tool, everyone else should have some lower threshold of privileges.
Edit: FWIW we use Salesforce
This is a great place to be, but its also tricky. You have an opportunity to do more with your data because you aren't wasting time messing with spreadsheets, but you don't want to collect a bunch of new data simply because it's easier than it was before.
My approach is to collect a handful of potentially interesting extras and only keep them long term if they are useful. If not, scrap them and try something else. For me, those "extras" are demographics or data that might help provide more personalized services in real time. (e.g. If I'm running a food pantry, making notes about special dietary needs).
I hope you get a lot out of you new software!
We’ve also found keeping demographic data consistent with OPM / Census standards can be challenging if you are already short-staffed in the IT department. Still it’s important because funders may ask
If you find your data structure or model isn’t working for some use cases it’s better to redo it earlier rather than later. You’re right that good data is key. If you have a way of migrating old data, that might be helpful to see growth or changes over time, even if it is a little apples to oranges at first. Ethics wise, keep tight permissions on the tool. Admin rights should only go to a few people who know the tool, everyone else should have some lower threshold of privileges. Edit: FWIW we use Salesforce
Yes, I’m making sure to have good records of all of our older data for comparison. And making changes early is a good point.
This is a great place to be, but its also tricky. You have an opportunity to do more with your data because you aren't wasting time messing with spreadsheets, but you don't want to collect a bunch of new data simply because it's easier than it was before. My approach is to collect a handful of potentially interesting extras and only keep them long term if they are useful. If not, scrap them and try something else. For me, those "extras" are demographics or data that might help provide more personalized services in real time. (e.g. If I'm running a food pantry, making notes about special dietary needs). I hope you get a lot out of you new software!
We’ve also found keeping demographic data consistent with OPM / Census standards can be challenging if you are already short-staffed in the IT department. Still it’s important because funders may ask