For a Consulting Partner, selecting a methodology is like swiping on Tinder.
If you don’t know what makes for a great relationship, then … trouble.
Being a software company or working with an end-user project team for internal customers is like being in a monogamous relationship.
You know what works. You know the routines and protocols. Agile, Xtreme, TDD, RAD, or Spiral. Vanilla, kinky, safe, or adventurous.
If everyone is on the same page, things work. Birds sing, the sun shines.
On the other hand, a Consulting Partner is more like a serial-relationship-person.
Just like relationships, entering a new engagement with a client should be done with the objective of knowing how best to navigate the journey by understanding each other as best as you can.
Don’t Agile a conventional Waterfall company.
Don’t suggest a casual relationship to someone who has a tight deadline for marriage, kids and dog.
You don’t want to get here:
“I want to have a baby by Easter!”*
“Uhhh what? You haven’t decided what kind of house you want, or even how many times you want sex.”
It sure is a recipe for tears 😕
It looks like I’m aiming for world record in mixed and mangled metaphors 😁 but what I’m trying to say is that a Consulting Partner needs to be able to rock the different styles of working with their clients.
That’s because they are non-monogamous by nature, and will need to be highly adaptable to survive and thrive.
They should also be able to dance with the client, in whatever style suits them.💃
OK I had to shoehorn that in as I couldn’t find an easy way to depict different relationship types in my doodles. Sorry. 😁
Basically, Consulting Partners are (B).
If that sort of thing rocks your boat, then hit them up for a job. 😊
—
* note that this is non gender-specific imaginary statement from the client/romantic partner
#SalesforceConsulting
#SalesforcePartners
#OnThePeiroll
