Let’s talk about impostor syndrome, gang. Because although this blog is constantly offering advice about how to do well….like most, your girl suffers with this one from time to time!
Impostor syndrome, for those who don’t know, is a phenomenon driven by feelings of failure, inadequacy or incompetence. Psychology Today describes it as “a pattern of behavior where people doubt their accomplishments and have a persistent, often internalized fear of being exposed as a fraud.”
What makes impostor syndrome different from your average unconfidence (inconfidence? disconfidence?) is that it even happens to folks with a track record of awesomeness. Imagine the smartest person you know confessing they feel like a fake, and you get the idea.
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?
Have you ever spent unnecessary time on a request, all because you & your colleagues weren’t on the same page? *raises hand*
It’s not a great feeling! But that’s what happens when you don’t organize requests early on. If you write content for your org, create reports, build lists, or do anything that requires even the slightest bit of niche expertise….let’s chat.
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.
Gang, let’s talk about unconferences. Because I’ve got a lot of mixed feelings.
First, if you’ve never heard of an unconference, let’s start there. An unconference is a “participant-led” learning experience. It rebels against the typical conference structure, in that there’s no preset agenda.
Yep, you read me correctly.
There is no agenda for this conference, until you show up to make it. The idea is that the audience –the people who this whole thing is designed to benefit– put forth the topics they want to discuss. Hence, the ‘un’.