One question to ask yourself when you have to choose a method to accomplish something at work is, "How easy will this be to fix
For instance, a coworker recently had to update 100 records in a program that has an Access database backend. Had it been my project, I would have gotten the identifiers for the 100 records, put them into Excel, put the new field values next to them, imported the spreadsheet into Access, and then run a query to update them. What she did instead was to open each record individually in the program, and do each update. This would make me crazy to begin with, but it also had the unfortunate result that, once she realized she had made a mistake, she had to do it all over again. If you make a mistake in my plan, you can easily just correct the Excel spreadsheet and reimport it, or fix the import query, or whatever is required. The data is entered once and it's stable.
This kind of technique is important to me because I make a lot of mistakes. I bet other people do too.
The second question to ask yourself is, "How easy will this be to change when they want me to change it?"
I try never to change something such that I can't pretty easily change it back, since "Put it back the way it was" is such a common request. I make new data rather than overwrite old data where appropriate. And I try to keep my changes somewhat modular, so that if they want to keep some changes and discard others, that too is possible. In your specific job, you probably know what types of changes are commonly desired, so you can set yourself up to make those as easy as possible in advance. It saves a lot of frustration and grumbling (on your part) later if you can treat changes as expected rather than aberrant.
Some common ways of making changes easier include making sure there are backups of old files, storing intermediate results, and using notes and/or naming conventions to keep things clear. You will definitely not remember, three months from now, how you generated this file or what you did to it, so make sure you give your future self a way to recover that information.
Here ends installment eleventy-seven in the Tam's Obvious Work Advice series.