You ever find yourself trying to explain something technical to someone, and feeling as if you’re speaking another language?
Good. So it’s not just me.
Being in a technical role, and the only person who understands some parts of that tech, means I get the job of explaining to people why things work the way they do. I’m a nerd about bringing people into my work, so I’m happy to do it.
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, 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. 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. 😇