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.
If you won the lottery and left your job tomorrow, could your org pick up where you left off?
If you’re thinking NOPE, then this one’s for you. Let’s get into it.
When we talk about doing mission-driven work, we hardlyever talk about documenting it al. That’s cause when you’re already so busy, this can be a drag! Documentation is the grunt work of event-planning with all the thrill of watching paint dry.
Writing this post, I was skeptical this would even make for an interesting topic.
But we can’t just ignore this topic! Drudgery aside, documentation is key to how we make a lasting impact at work. Plus I’m in documentation purgatory right now. …so I can personally attest, this task is so worth your while to do early. 😇
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?