The Pre-Work Chronicles: A Comedic Journey Through Salesforce Project Prep ??

If you've read any of my former articles, I am definitely a measure twice and cut once type of person. And I get it, Salesforce makes it so easy to build on the fly. Trust me, early in my career I might have built and broken a few things in production. Experience is definitely the best teacher! ???? This is why I know extoll the virtues of doing your homework. Especially with the additional complexity in the platform and our customers processes. Doing the upfront work definitely takes a lot of the risk out of an implementation, so I've documented a few of my best practices.

Starting a new Salesforce project? Congratulations! ?? You already know that you need to assemble your dream team and get ready to dive into the world of cloud-based CRM wizardry. But wait! Before you start customizing dashboards and automating workflows, there's that little thing we like to call "pre-work." ??

Yes, I know, you're all about to check out and stop reading, BUT WAIT! Stay with me a bit.

Pre-work is that magical phase of the project where you do everything except the actual project. It's the appetizer to your Salesforce feast ???, the stretch before the marathon ??, the trailer to the blockbuster ??. And just like those trailers, sometimes it feels longer than the movie itself. Here's a humorous look at the five stages of Salesforce project pre-work, because if we don’t laugh, we might just cry. ??

Stage 1: The Kickoff Optimism ??

Ah, the kickoff meeting. The air is thick with excitement and the smell of fresh coffee ?. Your client is eager, your team is pumped ??, and everyone is speaking in that optimistic tone that suggests everything is going to be a breeze.

“Let’s just start with a simple data migration,” someone says, blissfully unaware that "simple" and "data migration" have never appeared in the same sentence outside of the kickoff meeting. You nod along, because, hey, how hard can it be? ??

Stage 2: The Discovery (of Infinite Requirements) ???

Next up is discovery. Or as it’s often called, “Opening Pandora’s Box.” ?? This is when you find out that the client’s idea of “simple” is a bit like calling Mount Everest a “small hill.” ???

You ask about their current processes, and suddenly you’re bombarded with a list of requirements so long it would make Tolstoy’s War and Peace blush. ?? There are integrations with systems that haven’t been updated since the 90s, custom objects for tracking something called “super-leads,” and, of course, the ever-present request for “just a little bit of AI.” ??

Stage 3: The Great Expectation Setting ??

After the discovery phase, you’re ready to set some expectations. This is the part where you gently inform the client that their desire to launch a fully customized, AI-driven Salesforce instance in three weeks might be a tad ambitious. ??

You explain that while Salesforce is powerful, it’s not quite powerful enough to bend the space-time continuum. ??? The client nods, understandingly, but you can’t shake the feeling that they still believe in magic. ?

Stage 4: The Scope Creep Defense ???

Now that the project plan is in place, it’s time to guard it like a hawk. ?? Because no matter how well-defined your scope is, scope creep is always lurking around the corner like that one coworker who always shows up uninvited to the lunch table. ???

“Can we just add this one more field?” asks the client, innocently. You smile and add it to the list, but inside you know that “just one more field” is the gateway to chaos. ?? Pretty soon, you’re creating custom Lightning components, building out entire new modules, and contemplating a new career as a goat farmer. ??

Stage 5: The “Ready” to Start Feeling ??

Finally, after weeks of meetings, emails, and more whiteboard diagrams than you can count, you’re ready to start the actual work. Or at least, you think you are. The client has signed off on the requirements, the team is prepped, and everyone’s calendar is booked for the next three months. ??

But there’s that nagging feeling in the back of your mind that you’ve forgotten something. ?? You double-check the project plan, triple-check the user stories, and quintuple-check your caffeine supply. Everything seems in order. You take a deep breath and dive in. ??

The Conclusion: Embrace the Chaos ???

Pre-work for a Salesforce project is like preparing for a road trip with a car full of kids. It’s hectic, it’s unpredictable, and just when you think you’re ready to hit the road, someone needs to use the bathroom. ?? But it’s all part of the journey.

So, the next time you’re in the throes of project pre-work, remember to embrace the chaos, laugh at the absurdity, and maybe—just maybe—hide a stash of snacks in your desk drawer and replenish your Starbucks gift card. ???? You’re going to need it. ??

Reach out if you want to discuss homework strategies, need additional help or just need a shoulder to cry on when you're in the throes of chaos. Always looking for new tips and tricks on pre-work for successful implementations!

#Salesforce #ProjectManagement #TechHumor #CRM #PreWork #Delivery #Discovery