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.
If you won the lottery and left your job tomorrow, would your org be able to pick up where you left off?
If you’re thinking HECK NOPE, then this one’s for you. Let’s get into it.
Whenever we talk about doing mission-driven, passion-fueled work, we never talk about documenting it. That’s cause when you’re already so busy, this can be a drag! To some, documentation is the grunt work of event-planning with all the thrill of watching paint dry.
Writing this post, I was skeptical that this could even make for an interesting topic.
But as a blog centered on nonprofit worker productivity, we can’t not talk about it! Documentation is key to how we make a lasting impact at work, drudgery and all.
What’s one thing that development staff, volunteer coordinators, operations managers, HR and Program people all have in common?
At any time, we can become our org’s database admin, too.
“Accidental admin” is the term we’ve lovingly coined to all the database managers who never signed up for this. Typically the consequence of multiple-hat syndrome, these are the nonprofit professionals who were standing closest to the system at the time when their org desperately needed an admin.