For a blog that’s about nonprofit productivity, I have a bit of a confession. And if you read my last post, you probably caught it – in the section where I talk about how I manage my work tasks.
Or more specifically, the fact that I don‘t. 😞 I know. Don’t judge me, gang.
It’s not for lack of trying! I’ve stopped and started many a system – spreadsheets, Salesforce, even written planners. Once I reach a point where using the system feels like more work than help, I cut it out of my life.
But now that the demands on my job are increasing, my current “system” of inbox to calendar to memory isn’t cutting it. It’s time for this gal to change her ways.
If you’ve noticed I’ve been MIA the past 2 weeks…here’s the scoop.
I am neck-deep in a system migration right now, thanks to the shutdown of our online ticketing system. (If the phrase “Desk to Service Cloud” means anything to you, reach out. You’re likely a Salesforce admin doing the same thing, so we can commiserate together! 😅)
Any database manager will tell you that when it comes to implementing a new system, seamless-ness is next to godliness . If no one complains on launch day, then youknocked it out of the park. That’s my goal.
Anyone who regularly works with spreadsheets knows the anguish of screwing up said spreadsheets.
It usually goes like this. You’re powering through – filtering, sorting, formulating – until you notice that one row of data looks off. After frantically checking a few more rows, it hits you. Something went wrong in your manipulations, and now you need to start from scratch.
Spreadsheets are great, but they have also destroyed many a nonprofit worker’s day. Fortunately, we can do things to reduce the chance of this happening…and keep calm when it inevitably does.
Don’t worry – nothing actually offensive took place on my part. My job isn’t in jeopardy, I’m not on probation, or anything like that! But I had an exchange with one of my directors, and as far as I’m concerned, I’ve definitely made a mistake in my role. Let’s dive in.
Anyone who manages a database knows that the job has it’s less-than-glamorous moments. Not that anyone would call this work glamorous…which is precisely why I love it.