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.
But that kind of success takes TONS of work. Between the coordinating, pivoting & maneuvering involved, I promise you…it almost doesn’t matter if this is your first implementation or your fifth. Things are bound to crop up regardless, and if there’s one thing I’ve learned, it’s that you’ve got to get comfortable thinking on your toes.
Which brings us to this list. From my personal experience, here are 11 truths you’ll need to get onboard with before moving forward with that system.
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 NOPE, then this one’s for you. Let’s get into it.
When we talk about doing mission-driven work, we hardly ever 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 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.