“Hey doc, I have this painy chest right here. I think I need a stent. When can you schedule that in for me?”
🚩🚩🚩 😱😱😱
What would you do if you were the doctor?
Would you:
A) Trust them that they know what they’re talking about and do the operation as suggested?
B) Run your own diagnosis and tests to figure out what’s happening before suggesting a plan of action?
I reckon most would go for (B) whether you’re the patient or doctor.
So if you’re a #SalesforcePartner, why would you not want to run a Discovery to understand the situation before diving head first into implementation? 🤔
🍩 Client won’t pay for it
🍩 Takes too much time
🍩 Sounds “straightforward” and “easy” so it should be ok🫤
🍩 A previous partner has already done one so we can trust the finding 😬
🍩 Client already did one two years ago so they don’t want to do it again 😶
These bullet points merit a whole post each but maybe another day…
So unless you’re talking about a simple greenfield 5-6 day implementation for a small org with limited number of users and you want to just Agile the whole thing and get on a journey with the client which may change directions a few times before they settle on the final system… Your project could get incredibly bumpy without a Discovery. 🤕
It needn’t be big or formal but it needs to be done so you know what you’re dealing with.
Unless you’re a masochist.
Or if you enjoy stepping into stinky sticky smelly poo. 💩🤢
Personally I’d rather wrestle with a porcupine than jump into a project without discovery 🦔 😅
How about you?
What animal would you wrestle in lieu of doing a project sans discovery?? 😁
—
Get your copy of Salesforce Discovery 101 at your nearest Amazon store and keep sprog 3 supplied with her boba addiction 🧋😆
