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.
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. 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 making a lasting impact at work. Plus I’m in documentation purgatory right now. …so I can attest, this task is so worth your while to do early. 😇