Fundraising & data peeps! This is where our worlds collide.
Your fundraiser is one of the most pivotal events of the year. Yes it’s an experience, a way to bring supporters in and tell the story of why we do this work.
But that doesn’t mean it isn’t stressful AF. Plus, we’ve got those deliverables to worry about.
What I love about fundraisers is how the back-end stuff often tells its own story. There are valuable lessons for us all – fundraisers, EDs, marketing & data wizards – on what drives supporters & how best to make these events replicable. We just need the right metrics.
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.
How do you organize your work requests? Have you got your system down?
I’ll be honest: when it comes to task management, I’ve started, abandoned and restarted systems. It’s easy to let ourselves get disorganized when things get chaotic!
But for requests that involve staff (or other constituents), it’s never a good idea to let this slide. You need to proactively capture those needs, stakeholders, and project updates. Otherwise, details slip through the cracks and communication breaks down across teams.
A good process keeps us covered here. We know how to build a framework that guides us in executing requests. We’ve also figured out how our colleagues should reach out to us. Now it’s accountability time: how do we document and manage that process from start to finish?